Develop Bugs

No space left on device

Afternoon all,
Last night I left my Desire charging as normal, having recently installed the Remote Media App. I suspect it used up all my storage with some sort of indexing process, as I returned to the phone this morning to find it perpetually showing the glinting HTC logo.
A reboot failed to clear it, and booting into recovery mode reveals"E:Error in DATA:data/recovery/log, (No space left on device)"
I've tried connecting to it with adb, but I get the following error
- exec '/system/bin/sh' failed: No such file or directory (2) -
Is there any way out of this bind? I had/have ClockWorkMod recovery installed in order to use ROM Manager, but I'm not terribly clued up on what else is out there on offer.
Any advice would be greatly appreciated.
Kyle

Try rebooting the phone into recovery mode and wipe/factory reset and see if this fixes it?
(Although you will loose all your apps/settings/scenes, though)
This should resolve the problem though.

hehe, there is always that option. I was hoping not to lose texts, settings, etc though this time round. Sadly my backup is more than a few days old.
I was mistaken in thinking I had ClockWorkMods recovery image installed, it appears to have gone back to the default image. I've just discovered a modified recovery ROM from JesusFreke here http://forum.xda-developers.com/showthread.php?t=443041 which may be of use.
Having to wipe and start from scratch again is a disgustingly appaling out of space failure mode. >:-/

bin the phone and use a pineapple

That recovery image is for G1! Don't even think about flashing it.
Even if you have stock recovery, you should still be able to clear storage from HBOOT.
Regards,
Dave

One other thing that might be worth trying is booting the device in safe mode.
Whilst the phone is power down, hold down the menu button and then power on - keep menu held down until the phone is fully booted.
I doubt that it will help in this situation, since clearly /data is completely full, but there's always a slim chance it work.
Regards,
Dave

munkehman said:
bin the phone and use a pineapple
Click to expand...
Click to collapse
Thanks for the advice m, I'll be sure to kick you in the nads next time you cross the border

Sadly Safe Mode fails too. The HTC logo appears and glints for a while, and then briefly vanishes just to reappear again. My thumb got sore after 5 minutes of holding the button down
I realised that was a G1 ROM shortly after reading more about it! I see there may be a more suitable recovery ROM at http://forum.xda-developers.com/showthread.php?t=709146 that I can flash. Failing that, then I'll clear storage and consign myself to failure

Wahey! It's sorted! Well, it was sorted a couple of hours ago, but a meeting got in the way
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!

kylegordon said:
Wrote up some of the details here - http://lodge.glasgownet.com/2010/08/31/recovering-a-htc-desire/ if anyone is interested!
Click to expand...
Click to collapse
Sorry to dig up an OLD OLD thread, but your "guide" helped me out last night.
In addition to looking for "big" items in the data partition, I also moved some of the Google updates (5meg Maps.apk anyone ?) from /data/app to /system/app ... renaming to overwrite the original version from my Rom.
Thanks Again.

Soft Bricked - Unable to Sideload OTA

Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?

SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.

The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.

SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.

bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.

SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.

Stuck in setup wizard after factory reset

Alright, hello everyone,
I'm having a pretty weird issue here. I've flashed my DUK-L09 and the C432B183 EU Firmware, everything was running fine.
I couldn't make a backup of the /data/ partition though, someone told me to wipe the data to decrypt it, but nothing came good after this.
So I tried to flash back the old recovery image by extracting it, flashing it via fastboot, as I would normally do; enter the factory reset, run it.
Everything is good, it goes up to 100% pretty fast, less than 2 minutes. I then enter the setup wizard the NFC is acting weird. It keeps activating
and deactivating illogically. So, ignoring this issue, I kept up configuring the phone then once I'm logged in Google and sync'd, pops a Huawei ID
logging page really really fast then goes back to the EMUI menu at the beginning of the Setup, in an infinite loop.
Useful information to let you help me better:
- Many firmwares. Currently trying to flash back to B120a and NoCheck from OldDroid and Morph. (Edit: Didn't work)
- Phone unlocked, TWRP accessible.
- Getting a weird "Error 9" when trying to run Update.zip from TWRP.
- Sideload working, but not transferring anything.
- Cannot find any B182 or B130 stock firmware. Everything seems to be gone from Huawei's servers.
- The loading logo isn't Honor anymore but Android, for a reason I can't yet understand.
- Restoring a clean backup (without /data/, since I couldn't back it up) did not fix the problem.
- Trying to update with the 3 buttons do not work, even with the right firmware (C432B183) (Software install failed)
- Factory reset works with the right ROM, but gets me to the setup loop issue.
- The loop occurs when I am supposed to see the Huawei ID setup page. If I do not put any SIM card, or WiFi
I am prompted to choose which way to restore data; if I skip this step, it blinks and doesn't do anything.
- I tried to restore via WiFi (Google's cloud stored data from my account), but it does the same thing as mentioned
earlier. It blinks multiple times rapidly the "Huawei ID" setup page then goes back to the first Setup screen w/o
me being able to do anything about that.
I'll be glad if you knew the answer to this, because I'm all lost right now.
Greetings, Kameyuu.

UP !
After many tries and a LOT of hard work, and spent an entire night (was about to spend the second night on this), I found the culprit and now I know what the issue is, it sounds completely legitimate.
So here are the reason and the solution to this issue:
Actually, my CUST was somehow broken. I never flashed it back because no one told me to flash the CUST.img back. They told me to flash BOOT, SYSTEM, and RECOVERY only.
So, after I downloaded a software called HUAWEI Multi-Tool (From hwmt.ru) I noticed they were also asking for the CUST.img and USERDATA.img (<- this one was apparently optional)
So, trying my luck I flashed it. Did a factory reset, and all, it acted weird and failed, then I tried again and it succeeded. So, with all my hope I booted the phone to the system, started configuring... And it worked !
I was able to set up the phone. For a -yet- unknown reason, some apps look missing and the NFC is still blinking on and off repeatedly and randomly, but I'm investigating that.
If you have any question on the precise steps feel free to send me a PM or ask in the thread directly I'll be glad to sort your issue out.

[EDIT]
Sorry, double post I don't know why my message was posted twice. Feel free to delete this message @moderators

Help -- phone won't boot and I need to get photos off

My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.

jerrytaff said:
My daughter has been using this phone, but never backed her photos up. Now it won't boot and she is worried they are lost forever. I've been trying to help, but only seem to make things worse.
1. She never enabled USB debugging, or rooted it
2. She could not tell me whether she had allowed the OTA upgrades.
3. It got into a reboot loop a few days ago. It would start to boot, then say it was optimising a random number of apps (anything between 90 and 158) and then start over. Wileyfox tech support told me that this was due to an incompatibility between Cyanogen and the latest Facebook Update.
4. They sent me a link to the FOTA files with instructions how to progressively upgrade to Android 7 (TOS111B)
5. They couldn't tell me how to determine whether it was running CM12 or CM13 (I now realise that I could have looked at the log files in the recovery partition)
6. I therefore assumed that it was running CM12. I used their instructions to go into recovery and manually update from SD card to ZNH0EAS2NH from there to ZNH2KAS7EB and then to TOS111B
7. Fatally I did not reboot between updates. At the end I had the Wileyfox splash screen black on white, and then got an animation with it red on white. It then got stuck.
8. I then tried using fastboot to go back to the original version of the OS so I could start over. I found the fastboot image and I flashed the boot and system partitions.
9. Now on boot it either gets stuck on the black on white boot screen, or it displays it for a second and then turns off.
Can anyone help me? - I think my daughter will have a nervous breakdown if I don't find a way of recovering her photos. Recovering the photos is more important than unbricking the phone.
Click to expand...
Click to collapse
Since posting this I have had a partial success. A more complete set of fastboot flashing using the TOS111B fastboot images has got me to a phone that boots. Many of the apps work. However...
a) I get an "unfortunately the process com.android.phone has stopped" appearing almost as fast as I can close the app making it very difficult to get anything off the phone. However, I did manage to set up a google sync to upload the photos.
b) my daughter now tells me that her SMS's are vital.... and the messaging app says " getting message" then closes down
c) I cannot enable developer setting to enable usb debug mode. I can get into the phone status page under settings. Repeated tapping on the android version brings up the nougat splash screen, but the 7 taps (or 700 for that matter) on build number does nothing whatsoever.
Does anyone have any ideas how to recover to a fully working system without doing a factory reset?
I suspect that the sms database would have gone when the cache was cleared. Can anyone confirm that to be the case before I spend any more time trying to recover them?

Hi Jerry ,
Exactly the same problem here. Could you tell me where you've found the TOS111B fastboot images?
Thx!

Have you tried booting into safe mode?
I think you do that by pressing and holding the volume down down button during reboot.
If you can manage that you may be able to dissable the apps that are causing the crash.

mi a2 lite crashes and freezes since December 2019 pie update. (benchmark logs)

Hi
Since installing the December 2018 update to Android Pie last week my phone has become unusable. It freezes for 5-10s period all the time while using. Sometime, when it wakes back up again, there is a message on the lock screen that says 'you need to unlock using pattern after reboot' which makes me think the phone is crashing and rebooting itself while the screen stays frozen.
I have done a factory reset twice. In fact, directly after the December 2018 update, the phone got stuck in a boot loop and I had to factory reset then, as well.
Anyway I did some research on here and have run Androbench as people seem to be blaming poor write performance. See image.
Please - what can I do? Roll back to an earlier version of Android? The phone has worked perfectly for months until last week.
Many thanks.

you could try to reflash the latest pie rom with miflashtool. if you tick "flash all expect storage" you wont 't lose any data

download the latest rom from website, extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg . This will completely flash the whole phone without relocking the bootloader. I had exact same issue after using twrp to make a nand, its had something to do with accessing firmware while making backup, i think this will sort your phone out, dont use miflashtool its a total mess. Dont mess with flash order, ppl may say it doesnt matter what order its done, but it does matter. Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.

Brilliant - thanks for the reply. What you suggest is probably on the limit of my skills and experience, so I have a few questions if that is OK:
boe323 said:
download the latest rom from website,
Click to expand...
Click to collapse
So, this? https://en.miui.com/download-354.html
boe323 said:
extract the image folder with contents inside and add this flashall.bat to the image folder contents, https://1drv.ms/u/s!AqlJY73bUA7rhokx5kWL6MAtXYDRTg .
Click to expand...
Click to collapse
I assume just copy & paste this file into the main folder?
boe323 said:
Instructions are, assuming you have adbtools, to use admin cmd prompt to the image folder and type flashall.bat, you need to add adb platformtools to windows system variables path.
Click to expand...
Click to collapse
Thanks, I will check that platform tools is in the system variables path. Maybe it will become clear, but I can't remember if the rom image needs to be stored on the phone or PC before I start?
Thanks

After fixing itself last time (with a factory reset), my phone's performance has gone absolutely again since the September update. It hangs constantly, takes 10 mins to turn on, and is generally unusable. Memory logs below.
This time nothing I have tried will fix it, I have tried: factory reset from bootloader, miflash to latest rom, using fastboot to flash latest rom, using the modified flash_all.bat from boe323 (thanks for your help last time).
Still the performance is dreadful.
Is there anything else I can try before I throw this phone away?
Thanks anyone for helping

Flash lastest stock (10.0.13.0) with no flash but use: fastboot oem edl , u can search in you tube how to do is easy

Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks

yeahdisk said:
Hi, thanks for idea, I did this last night (new memory logs attached)
Still I get the same issues. system UI hangs and crashes basically make the device slow and unusable, especially in Chrome.
Any ideas on what I could do next?
Ideas gratefully received
Thanks
Click to expand...
Click to collapse
If nothing helps , just use MiFlash , and don't use clear all , use clear all_lock.Relock your bootloader and test if everything is working ok. If it doesn't - then I hope you have warranty. Relocking and unlocking the bootloader is so easy , so you don't have to be worried about nothing. Then you will be sure , if the problem presists with totally stock firnware , then you have only one choice.

thanks - trying this now

Downloaded your app and tested it on my perfectly working device. No problems at all, no hangs, fluid, etc.
I attached the results.
If you flashed stock ROM and the speeds are that horrible... you should check if any apps are causing the hangs. Reboot in SafeMode and check the speeds. If the phone behaves normally in SafeMode, than something you installed/configured is causing the said problems.
The last solution would be... checking the NAND chip, I don't quite know if there are apps that could check the sectors in the NAND memory. Maybe you are experiencing a bad nand/multiple bad sectors slowing down everything... But from my knowledge this shouldn't be a problem in current technology, since Android has auto-trim and bad sectors should be ignored, not affecting performance.
From my experience August update fixed the problems and September brought a system speed-up. I feel the phone even more snappy now.

Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help

yeahdisk said:
Thank you for this. My phone is fine in Safe Mode! I didn't think of this, as when I was relfashing the Rom I wasn't installing any additional apps - just the Androbench to check performance (always after checking that the problem was happening).
So, what to do? Does this mean that one of the Stock ROM apps? is causing the issue? How to fix?
Many thanks for your help
Click to expand...
Click to collapse
Get an app like System Panel 2. Set it to monitor all apps/system activity and check where the hangs comes from. Maybe even AndroBench is the culprit in your case.
Anyway, get a system monitor app that can log all app activity individually and see which app has the most cpu usage and which app has the most disk usage.
But by the fact that your phone is running extremely slow after reflash, I suspect the back-up/restore system. Maybe it downloads some corrupt data and hangs the system. If that is the case, a new Google Account may fix the problem. Start fresh.

OMG I took the memory card out and everything is working fantastic again

yeahdisk said:
OMG I took the memory card out and everything is working fantastic again
Click to expand...
Click to collapse
If the SD was your problem, check out the solution I found here: https://forum.xda-developers.com/showpost.php?p=80172348&postcount=19