Hello There, Guest! Register
Enjoy our site and services? You may donate to help fund server and domain costs. Donate Here for special benefits. You have donated $

Thread Rating:
  • 2 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Tutorial] - Fixing a bricked system
#61
I'll do it on more time and now i get an writing error:
Code:
dd: writing '/dev/system': No space left on device

My device is full  Huh


Code:
Filesystem                Size      Used Available Use% Mounted on
tmpfs                    64.0K     64.0K         0 100% /dev
tmpfs                   256.0K         0    256.0K   0% /dev/shm
/dev/sdcarda8           185.0M    185.0M         0 100% /vp_mnt/Bundle
/dev/sdcardb1            29.3G     82.6M     29.2G   0% /media/sdcardb1
/dev/sdcarda6            26.4M     26.4M         0 100% /system

Is it a good idea to make "rm /system/*"
Reply
#62
No rm /system is not needed. I am not sure why it is saying no space left. Maybe Mick can help further.. I am at a loss.
Reply
#63
Hi Deak Phreak,
i bought a new SD card and will test it now with this one.
Reply
#64
Hi,
You cant dd to /system as it's a read-only file system.
I can see your problem, its appdestroyer is not working because of the corrupt filesystem.

Please extract appdestroyer to your SD card from a firmware image or such.
I'm not 100% if you can run it from the sd card, or if you will need to copy it to /tmp then chmod 755 appdestroyer.x
and then run it.

But the problem looking from your last posts is that after you DD the image, fastboot is not being cleared because of the error, and you end up with the same problem.

Mick
Reply
#65
We are active in chat right now, not sure if you noticed and can help you real-time. If you copy the file from the firmware, remember to do it all in linux. You may even be able to do it right on the tablet via putty.
Reply
#66
(03-09-2016, 12:05 PM)is0-mick Wrote: Hi,
You cant dd to /system as it's a read-only file system.
I can see your problem, its appdestroyer is not working because of the corrupt filesystem.

Please extract appdestroyer to your SD card from a firmware image or such.
I'm not 100% if you can run it from the sd card, or if you will need to copy it to /tmp then chmod 755 appdestroyer.x
and then run it.

But the problem looking from your last posts is that after you DD the image, fastboot is not being cleared because of the error, and you end up with the same problem.

Mick

Thanks, that worked - device is starting again!
Reply
#67
Hi Deak Phreak,

i tested my games and ebooks - all working. But my cartridges not read.
So i make a new MOD with the last update DE-74.50312 (without my mistake between linux and windows) and would patch with the installer. It says that the device is already patched and restarts. I read somewhere that i must edit a Run~ file or something. But can't find it.
Can you help? Thanks!

EDIT:
Find it in the FAQ for patching but not understand where the script for the check is.

"b) Flash the firmware by modding one of the flashing scripts (you could just rename your file that of the hacked firmware, and remove the check in the script that looks for RunApp~ and says the firmware has already been patched)"
Reply
#68
It seems strange that it would say it has already been patched if you flashed your backup to restore it unless it wasn't really a clean backup. I wonder if your firmware files got all shuffled when trying to debug the device. You can just flash it directly via putty like you did when you restored so you don't have the "installer" check. Or like the FAQ says, you would just edit the my_run file or whatever it is called and find the code about the RunApp~ part.
Reply
#69
Hi!
I did it - the device can read the cartridges now. I have flash it one more time via putty. The Warning in bootup of the kernal.bin/system.bin is well away.

Thanks for your time and help, thanks spiffyhacks!

P.S. the app_destroyer command shows the error again, but copy the app_destoyer.x file to /tmp and execute it from there.
Reply
#70
Great to hear!
Reply


Forum Jump: