Develop Bugs

[Q] [SOLVED] Phone does not load new Roms, Nandroid recovery gives white screen

Hi guys, sorry to say I'm back with another problem.
I have a Desire Z, rooted and S-off. Rooted with the wiki method (downgrade version, adb, gfree).
Using clockworkmod recovery 3.0.2.4, and have made a backup of my first 1.32 boot.
However, I tried flashing a new rom, but recovery just won't take it. It will say Can't open /sdcard/rom.zip (Bad) installation aborted, with every rom I tried. And I've tried more than 10.
So I thought, no biggie, I have a nandroid backup. So I run the restore, which works fine. But upon booting the device, it gets stuck on the white HTC loading screen. I have tried this multiple times, deleting cache/data etc fully. Also I used the FULL-WIPE-VISION.zip for this purpose to no avail.
I have followed the semi-brick guide which said I had to go get a stock rom with root, so I did. But I can't load it through clockwork restore, because I get the same Bad rom error.
What's left to try?
Additional info I should give according to the semi-brick thread (http://forum.xda-developers.com/showthread.php?t=842495):
The last and only Rom I had was the stock 1.32.4xx to which I had to downgrade before I got perm root. This rom is my nandroid recovery.
The command adb devices recognizes my device.
adb remount is succesful
adb shell gives me root
I have /data and /system mounted when trying most roms (but I get the same error when I don't have it mounted)
After booting and waiting a minute when it's stuck in white screen, adb devices will not recognize my device anymore, adb remount and shell also say that the device is not found.
Thanks a lot for helping out!
TL;DR: Clockworkmod recovery does not load roms, nand restore gives WSOD. How come?
EDIT: Problem was due to my budget 32GB microSDHC. Operations were successfull using the original 8GB card. Apologies for the spamtopic.

Noboo said:
EDIT: Problem was due to my budget 32GB microSDHC. Operations were successfull using the original 8GB card. Apologies for the spamtopic.
Click to expand...
Click to collapse
This isn't spam, and no need to apologize. Your post may be of benefit to others. If somebody has a similar issue, they may find your post, and from it find out how to fix it.
If nothing else, you should add [SOLVED] to the thread title.

[Q] Error in /sdcard/update.zip (Status 7)

Hi,
I got my wife a 1st gen Kindle fire for Easter and she asked me to flash it so that she could get to her Google apps. So I used the KFU v0.9.8+ and with some luck and a lot of driver conflicts was able to get it rooted. The device has intermittent charging issues and needs to be returned. Every time I try to revert back to the stock rom or any version I can find, I get the error:
E:Error in /sdcard/update.zip
(Status 7)
Error flashing zip '/sdcard/update.zip'
I know this is a common error as it happens on many devices. I also have searched for 6 hours on the forums and other various sites trying to find a solution. I have also downloaded and re-downloaded update-kindle-6.3.2_D01E_4110520.bin and update-kindle-6.3.1 and renamed them to update.zip and deleted the old one to see of the download was bad, but to no avail. I even added the raw bin file to the amazon update folder and tried to push it with the update, inside the OS, but still no success.
Can anyone point me into the right direction? Do I need to change the fastboot from 4000 to 4002? Would that make a difference? I have to send this thing back to Amazon and I know that after I flash a stock rom to eliminate root, I have to manually delete all of the twrp files with ES file explorer.
I would really appreciate the help.
Batt

Update or downgrade your version of TWRP or install COTR

soupmagnet said:
Update or downgrade your version of TWRP or install COTR
Click to expand...
Click to collapse
Man, thank you for the quick response and I have to say you are quite the resource on XDA! I have seen your signature what seems to be a thousand times! Now I don't mean to sound noobish and I have to be honest, when it comes to the Kindle I most certainly am, but, what are you referring to when you say COTR, you mean Cannibal recovery right? Would that be less painless than reverting to a prior version of TWRP, and is there an option inside of TWRP to revert like there is in CWM?
Batt

HDBattery said:
Man, thank you for the quick response and I have to say you are quite the resource on XDA! I have seen your signature what seems to be a thousand times! Now I don't mean to sound noobish and I have to be honest, when it comes to the Kindle I most certainly am, but, what are you referring to when you say COTR, you mean Cannibal recovery right? Would that be less painless than reverting to a prior version of TWRP, and is there an option inside of TWRP to revert like there is in CWM?
Batt
Click to expand...
Click to collapse
There may or may not be a recovery flashable version of COTR available, but I'm not sure. The new version of KFU is supposed to include COTR as an option, but I'm not sure if it has been released just yet. I love TWRP and use it all the time, but I couldn't say for sure what version(s) had the (status 7) issue when reverting to stock. You could try rebooting the device into recovery to see if that helps (it has for me a couple of times) but I think your best bet, to avoid the hassle, is to install COTR.
There are several ways you can go about installing it...
1) You can download and rename it to twrp.img and replace the twrp.img in KFU to install it.
2) You can install it via fastboot:
Code:
fastboot flash recovery <filename>
3) In recovery, you can use ADB to transfer it to your sdcard and run the following command:
Code:
adb shell dd if=/sdcard/<filename> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
4) Or you can scour the COTR XDA forum thread for a user-posted recovery flashable ".zip" and flash it in recovery.
Of course, the same goes for (mostly) any version of recovery you want installed.
Just remember to factory reset if you're reverting to stock or you may have to get a factory cable to fix the resulting problem.

Thank you so much! This error have been driving me crazy for the past few days, no mater what rom i get this same error. Just flash COTR and all is good THANKS!

Help!
Hello! I have a big problem. I wan't to flash my P700 device whith CM11 and I have this error :
http://forum.xda-developers.com/attachment.php?attachmentid=2595602&stc=1&d=1393142285
Please help me!!!!!!!

[Q] (Help) HTC One M8 Wiped System files / no recovery / no OS

Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.

nOOb HTC Guy said:
Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.
Click to expand...
Click to collapse
are you using the all in one tool kit to do all of this?

skinsfanbdh said:
are you using the all in one tool kit to do all of this?
Click to expand...
Click to collapse
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.

nOOb HTC Guy said:
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.
Click to expand...
Click to collapse
So you managed to unlock your bootloader again as well?

try using the all in one program to sideload a rom

Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.

nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
A ruu.exe is executed from the pc and not from the phone. Its useless to sideload it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.

BerndM14 said:
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.
Click to expand...
Click to collapse
Okay so I tried sideloading with your instructions, which came up "failed" but actually had put "sideload.zip" in the directory, but when I tried to flash it I got the same old "error flashing zip"
Next I tried to push file, which comes up with terminal message "error: closed".
It seems that the phone will not flash ANYTHING atall........

OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S

nOOb HTC Guy said:
OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S
Click to expand...
Click to collapse
I'll be back in around 2 hours or so, off to work now. At least a breakthrough of some sorts, will check on this thread later, hopefully you don't have to wait so long for your device to be fixed :fingers-crossed:
:victory:

if your using a different recovery or a different version of the same recovery your backups may not work unless you flash the recovery you made the backups with

Guys, Im still stuck with cyanogen mod, nothing else will flash or sideload successfully. Also, what I thought was the ruu for my phone was not, can anyone find the correct ruu for mine? Htc one m8 on vodafone uk, cant find an ruu anywhere
Also, cannot obtain s-off since I get "permission denied" message when trying to adb shell and "su" through terminal..... Dont know if I require s-off to flash roms or ruu? thanks.

Ok it doesnt look there is an ruu for mine yet. So maybe I should focus on trying to get my own stock backup to restore, but nothing works! Its always the system bit that fails, boot data cache all restore successfully, any ideas? Would be absolutely amazing if I could just restore to the backup successfully! :good:

success!
YES YES YES YES YES!!!!! NOOOOOBBB POOWWWEERRR!!!!! Sorted it finally!!!!
For anyone else who has had problems restoring from backups, try restoring with files on phone memory and not sd card! Thats what worked for me.
Guys, thankyou all so much for your help I am eternally grateful and more relieved than you can imagine. Finally have a phone again

Can't find anything like it anywhere else (bootloop)

So I made a post in the general help thread and nobody has replied (although I've only waited a few days so I could probably wait a bit longer) but still I feel like my phone's issues are "unique" compared to other bootloops, I can't find anyone else having the same symptoms on their phone. I'll repost what I said in the general help thread and then give a brief overview of everything because I simply cannot comprehend why I'm unable to get out of bootloop with this damn phone.
So I just recently picked up an old Zenfone 2 (ZE500CL) off of my father who didn't really need it anymore and it was an upgrade from my old ****ty phone, so of course I wanted to root it and after using it for a few hours I wanted to install a custom rom by unlocking the bootloader. Well, I tried that, and something must have gone wrong because I got a bootloop and was only really able to boot into recovery mode.
Now, I didn't backup because I'm dumb for one and two I generally have a good idea of where to start if something does go wrong. The thing is, the methods I've looked up and tried have all failed. First, reflashing the stock rom of my ZE500CL (I've tried four different firmwares from the official website, and I know it's ZE500CL because that's what recovery mode is telling me) does not work. Adb hits 47% in the command prompt, the phone stays at 25% until then, and it goes:
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted
Not sure why it doesn't work, I looked it up and tried various things and it just isn't resolving itself.
So I tried simply running commands like the following:
fastboot flash recovery recovery.img
Using files from the stock firmwares themselves, and that gives me a flash_cmds error. I've tried deleting all of the userdata, the system, the cache, and a factory reset through recovery mode but none of that works. I'd really appreciate any help anyone could offer, this is a pickle and I'd really like to get this phone back up so that I can just run it as a rooted phone.
Click to expand...
Click to collapse
Now, I'll go over the issues quickly:
I'm stuck in bootloop but I can get into recovery mode
Trying to flash any rom, including multiple stock roms from the asus website, results in an installation aborted message at 47% in either ADB or microSD attempt at flashing the rom.
Attempting to run commands like fastboot flash recovery recovery.img ends up giving me a flash_cmds error which I cannot find anywhere else for the Zenfone 2e
Deleting the cache, userdata, system, or factory resetting the phone does not remove the bootloop
Unlocking and relocking the bootloader does nothing
I would really appreciate any help, feels like my phone is a lost cause even when it's not hard bricked.

Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...

ponnuvelpandian said:
Try ASUS Flashtool with a .RAW Firmware...
Find on This Thread...
Click to expand...
Click to collapse
Thanks, I haven't seen this. I've got the Intel and xFSTK drivers all up and running but my phone isn't being recognized constantly by my computer under Intel Soc in my Driver Manager, and it's not being recognized as MOOREFIELD but rather as CLOVERVIEW PLUS, and only for a second in-between boots on my phone. Can't get the files to be downloaded through xFSTK, so I've hit a snag here unless someone knows the solution to this.
I'll try just running the flash tool and using a raw firmware, then, since I can't do any of the other stuff.
EDIT: Looks like the issue I was having before is stopping me from running the tool, seems that the computer needs to recognize my phone through the Intel drivers at all time (which it doesn't) in order to run the tool. Also I can't get the tool to view the raw file, it only seems to read zip files (so I put the raw into an empty zip, thinking that could maybe work but I don't know for sure). Damnit, I don't know why this is so difficult.
EDIT 2: All right! Looks like I got it working. The process was relatively simple, actually. It involved booting into TWRP but I wasn't able to most of the time for some reason, it would just never do it. But, I was able to using the CWM Zenfone 2 bat file located here: http://forum.xda-developers.com/zenfone2/help/ze500cl-rooting-related-stuff-t3163528/
Then, I needed the stock rom for my ZE550CL placed onto an external sd card which can be found here: http://forum.xda-developers.com/zenfone2/help/ze550cl-factory-reset-return-to-stock-t3141513
So I would download the CWM Zenfone 2, replace the recovery file as the post states, then run the file. After that, I would run T4 since T1 and T2 didn't work (never tried T3), only T4 would seem to boot me into TWRP. From there, I went to Install, left Zip Verification unchecked, and let the damn thing run. It was the only thing that would run for me, even when doing it with ADB it wouldn't work with the stock rom. Then, I just rebooted and now I'm back on my phone. Hopefully this helps anyone else having this troubling issue, it was terrible!

Question Fastboot + ADB difficulties on my 9Pro

So my 9Pro ran fine on LOS for a few months, then it needed to go in for RMA so I returned it back to stock and sent it off... I got it back a couple of days ago and I just cant get fastboot+ADB to play nice with my device...
I use Platform Tools for Windows (mainly) and ADB works fine in System, I can get into fastboot no problems, I can even run "fastboot/adb devices" and it works fine, however when it comes to booting or flashing certain files it has none of it.
Some examples:
In LOS recovery (which boots fine) I'll try to sideload the copy partitions zip and get;
"failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory
emulated failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory"
or in fastboot mode I'll try to flash a magisk boot img or a twrp img and get;
Sending 'boot.img' (98304 KB) OKAY [ 2.143s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I also tried to sideload LOS thru twrp and get a different error;
"timed out waiting for fuse to be ready"
There were a couple of other errors along the way to (been trying to sort it for nearly 2 days!) I've (so far) always been able to get MSM to take me back to stock without issue and have done this several times, I've tried updating to latest OOS, not updating OOS, Lineage Recovery + TWRP, I've tried not encrypting my phone with a passcode, Ive tried lots of reboots along the way.... I've followed guide to the letter and also tried to mix it up a bit (silly but I have MSM).
But I'm at the end of my tether, I just cant get it to do it!
Any help or advice would be great I have the EU Model 9 Pro no carrier... Im gonna MSM back to 2.2 OOS one more time now and hope someone knows how to get it working... Happy to carry out any testing needed, I'm not a noob but far from expert either...
Cheers!

Same phone, same issue, did you figure this out?

557953 said:
So my 9Pro ran fine on LOS for a few months, then it needed to go in for RMA so I returned it back to stock and sent it off... I got it back a couple of days ago and I just cant get fastboot+ADB to play nice with my device...
I use Platform Tools for Windows (mainly) and ADB works fine in System, I can get into fastboot no problems, I can even run "fastboot/adb devices" and it works fine, however when it comes to booting or flashing certain files it has none of it.
Some examples:
In LOS recovery (which boots fine) I'll try to sideload the copy partitions zip and get;
"failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory
emulated failed to bind mount /mnt/staging/emulated/media/0 to /storage/emulated: No such file or directory"
or in fastboot mode I'll try to flash a magisk boot img or a twrp img and get;
Sending 'boot.img' (98304 KB) OKAY [ 2.143s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I also tried to sideload LOS thru twrp and get a different error;
"timed out waiting for fuse to be ready"
There were a couple of other errors along the way to (been trying to sort it for nearly 2 days!) I've (so far) always been able to get MSM to take me back to stock without issue and have done this several times, I've tried updating to latest OOS, not updating OOS, Lineage Recovery + TWRP, I've tried not encrypting my phone with a passcode, Ive tried lots of reboots along the way.... I've followed guide to the letter and also tried to mix it up a bit (silly but I have MSM).
But I'm at the end of my tether, I just cant get it to do it!
Any help or advice would be great I have the EU Model 9 Pro no carrier... Im gonna MSM back to 2.2 OOS one more time now and hope someone knows how to get it working... Happy to carry out any testing needed, I'm not a noob but far from expert either...
Cheers!
Click to expand...
Click to collapse
The issue was pretty much the same than yours (same error, but on a different phone and release of Lineage OS), it seems that a restoration to stock ROM solved it. MSM should be helping you, then. Have you already gave it a try?
https://www.reddit.com/r/LineageOS/comments/g4vext