Custom image for a 7590 with DECT chip removed.

[saronno76]

Hi,
I have this bricked 7590 I bought from ebay. I found it's an hardware problem: sc14446 was faulty. I tought removing the chip could be enough to avoid bootlooping but this is not the case since it's still boot looping without the chip. Since this it the DECT chip I tought a custom image could solve this problem. So I create a freetz-ng image with remove DECT patch applied. But it still boot-looping. Any idea?

[saronno76]

This is the log.
https://pastebin.com/MmcehYbq

[aus-sua]

--->
https://www.ip-phone-forum.de/threads/7590-in-bootloop-i-can-recover-it-with-the-avm-program-but-still-bootloop.320934/post-2587122

I think, in principle, first switch off watchdog in the menuconfig...
[x] Disable AVM watchdog - DEVELOPER

The patch "remove_telephony" only works up to firmware 06.5x, but I think, the 7590 was already
delivered with firmware 06.83.
You could try to activate the selects patches manually and, for test only, the old firmware 06.83.

I also think, you are in good hands with PeterPawn...

[saronno76]

I made a try with firmware 7.59 (modding the patches.in) but it s11-piglet is still there. I will try with 6.83 tomorrow ...

[fda77]

Maybe the remove patch does not fit the new fos version.
Try to remove manually things. In the log is a "modprobe", you could remove the kernel module or change the script where it es loaded
Also "disable (avm) watchdog" could help to stop rebooting, only availabel on developer level

[saronno76]

I tried to add this to fwmod right before the packing process ..

rm ~/freetz-ng/build/modified/filesystem/usr/bin/faxd
rm ~/freetz-ng/build/modified/filesystem/lib/modules/c55fw.hex
rm ~/freetz-ng/build/modified/filesystem/etc/init.d/S17-tam
rm ~/freetz-ng/build/modified/filesystem/etc/init.d/S17-isdn
rm ~/freetz-ng/build/modified/filesystem/etc/init.d/S11-piglet

I check the filesystem image created and it works, but, I have a problem once the firmware is pushed ...

5.471753] 0100           30000 ram0 [    5.475355]  (driver?)
[    5.477761] 1f00            8192 mtdblock0 [    5.481654]  (driver?)
[    5.483976] 1f01            1024 mtdblock1 [    5.488006]  (driver?)
[    5.490417] 1f02            4096 mtdblock2 [    5.494325]  (driver?)
[    5.496666] 1f03            8192 mtdblock3 [    5.500655]  (driver?)
[    5.502987] 1f04          502784 mtdblock4 [    5.506989]  (driver?)
[    5.509341] 1f05           45108 mtdblock5 [    5.513327]  (driver?)
[    5.515660] 1f06           45108 mtdblock6 [    5.519665]  (driver?)
[    5.522014] 1f07            2268 mtdblock7 [    5.526002]  (driver?)
[    5.528334] 1f08          391356 mtdblock8 [    5.532338]  (driver?)
[    5.534684] No filesystem could mount root, tried: [    5.539373]  ext3
[    5.541282]  ext2[    5.543000]  ext4
[    5.544926]  squashfs[    5.546993]  antfs
[    5.549007]  fuseblk[    5.550986]
[    5.552469] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,6)

[fda77]

You did something wront, ont know.
I dont understandy why you bought a broken device "for fun"

[saronno76]

I buy a lot of broken stuff from ebay. I am an electronic engineer, I like to fix stuff for fun and , of course, also to have all the electronics I need almost for free. In my house over 90% of electronics I own and use was bought as faulty.

[saronno76]

It seems I did it. The error wasn't about my firmware, but some error about push_firmware. Uploading with evatools works fine. Now the boot works, no bootloop. I just rewrite S11-Piglet (now is empty, no kernel module loaded).
The only thing is .... leds doesn't work.

[aus-sua]

The error wasn't about my firmware, but some error about push_firmware.

Could you describe this in more detail?
Are there any error messages/logs from the push_firmware?

[saronno76]

This is what happens when I try to upload the firmware with push_firmware ...

https://pastebin.com/4GSEn7rg

These are the ftp messages ..

`

• Reading 'env' file to /tmp/freetz_env_lVB
  Connected to 192.168.178.1.
  220 ADAM2 FTP Server ready
  331 Password required for adam2
  230 User adam2 successfully logged in
  Remote system type is AVM.
  Debugging on (debug=1).
  ---> TYPE I
  200 Type set to BINARY
  ---> SYST
  215 AVM EVA Version 1.3258 0x0 0x46409
  ---> MEDIA SDRAM
  200 Media set to MEDIA_SDRAM
  local: /tmp/freetz_env_lVB remote: env
  ---> PASV
  227 Entering Passive Mode (192,168,178,1,12,9)
  ---> RETR env
  150 Opening BINARY data connection
  Timeout!!!!!!!!!!!!!!!!!!
  ProductID: Fritz_Box_HW226
  HWRevision: 226
  HWSubRevision: 4
  memsize: 0x08000000
  linux_fs_start: 1

• MAPSTART=0x80000000

• FULLSIZE=0x0D000000 (208 MB)

• MAPLIMIT=0x8d000000

• FILESIZE=0x023fd900 (~35 MB)

• ALIBYTES=0x00000000 (~0 kB)

• FREESIZE=0x0ac02700 (~172 MB)

• MTDSTART=0x8ac02700

• Detected linux_fs_start: '1'

• Designated linux_fs_start: 0

• Box is back up again, initiating transfer.

Connected to 192.168.178.1.
220 ADAM2 FTP Server ready
331 Password required for adam2
230 User adam2 successfully logged in
Remote system type is AVM.
Debugging on (debug=1).
---> TYPE I
200 Type set to BINARY
---> MEDIA SDRAM
200 Media set to MEDIA_SDRAM
---> SETENV memsize 0x0ac02700
200 SETENV command successful
---> SETENV kernel_args_tmp mtdram1=0x8ac02700,0x8d000000
200 SETENV command successful
local: /tmp/freetz_Xi6/ramboot.flash remote: 0x8ac02700 0x8d000000
---> PASV
227 Entering Passive Mode (192,168,178,1,12,9)
---> STOR 0x8ac02700 0x8d000000
150 Opening BINARY data connection
226 Transfer complete
37738752 bytes sent in 7.29 secs (4.9395 MB/s)
---> SETENV linux_fs_start 0
200 SETENV command successful
---> QUIT
221 Thank you for using the FTP service on ADAM2

done

`

No issue with evatools.

[fda77]

There is a cat /proc/sys/urlader/reboot_status variable. If you flash an image by webif it get something like "reboot for update".
I dont know what avm does with this value, maybe disables flashing sometimes