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.

boot loop after flashing latest manhatten project rom

Ok have been running foxhound 1.1,tried a couple of other roms,kernels,etc and no problem. But now all of a sudden tried to flash manhatten and endless boot loop. I have tried to wipe from cwm several times but no luck. I dont want to lose my pictures from virtual sdcard. I have no access to adb but cwm and fastboot of course. I'm using linux so is there any way to use fastboot to erase everything but keep virtual sdcard. If that can you point me to instructions on how to from fastboot. I have the GSM version

Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot

Samsuck said:
Did you even bother installing another ROM prior to freaking out?
Wipe data
Wipe cache
Wipe dalvik
Format System
install ROM from sd card (please don't tell me you only kept one ROM on there)
your phone should now boot
Click to expand...
Click to collapse
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????

tman7510 said:
I have wiped several times reflashed foxhound 1.1 even reinstalled cwm recovery touch version but no go. Not sure what happened but why would going back to stock fix it??? I dont want to lose my pictures but if that is the only way. What the hell is causing the boot loop????
Click to expand...
Click to collapse
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.

9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk

Samsuck said:
You keep saying that you wiped but you're being vague.
Can you specify if you have WIPED DATA, CACHE, DALVIK, FORMATTED SYSTEM, and FORMATTED CAHCHE? If you have not, do that and THEN re-flash Foxhound
This does NOT wipe your internal SD card.
Click to expand...
Click to collapse
I have formatted everything but davik cache but when I do that I get" E:unknown volume for path /sd-ext Dalvik Cache Wiped " then reflash foxhound and now I am back to the boot loop all I get is Google with unlock symbol at the bottom and it just loops. There has to be a way to get info off my virtual sdcard..I dont care how hard it is

demon2112 said:
9 out of 10 times its human error when bootloop shows up..... go to the thread of the rom you flashing maybe you missed a important step
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
I didn't use the gapps but the rom should still boot without that gapp version. Also shouldn't I be able to flash another rom without having this issue??? All I did was flash from clockworkmod. maybe the zip file I downloaded got corrupted but I am unable to fix the problem. I had installed the manhatten rom yesterday but went back to foxhound because lack of performance/undervolting settings that apperently are on the rom. just want it to work again..I'm unable to use adb becasue it wont boot. all I have is fastboot and cwm recovery

That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA

Samsuck said:
That error is normal as we don't have an "sd-ext" .
Are you wiping in the correct order? You're wiping all of that first, and then installing ROM correct?
Do you have a back up?
---------- Post added at 05:37 PM ---------- Previous post was at 05:35 PM ----------
If you have ADB installed, or can get to a computer with it.
You can pull your files from the SD card as our fake SD card is actually /DATA/MEDIA
Click to expand...
Click to collapse
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???

"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"

tman7510 said:
how do I get adb to work if the phone will not boot into android???in fastboot mode if I type adb devices it lists nothing?? if I try adb in cwm recovery I get a bunch of questionmarks followed by no permissions....this is in linux. I can use windows if the toolkit can use adb while in clockworkmod recovery. I'll need detailed instructions becasue I have wiped in every order imaginable and nothing but boot loop???
Click to expand...
Click to collapse
You can use ADB in CWM Recovery. I do it all the time in Windows.

El Daddy said:
"adb devices" will return nothing in fastboot.
The correct command is "fastboot devices"
Click to expand...
Click to collapse
yes I know and I have no problem using what little I know of fastboot commands but is there a way to use fastboot to copy my virtual sdcard to my pc?????

Be sure to "mount data" in Recovery
adb shell
type su for superuser.
then ls to list the dirs
and cd to change
You might have to pull files one by one. I'm not sure if there's a way to pull the entire contents of it.

Samsuck said:
You can use ADB in CWM Recovery. I do it all the time in Windows.
Click to expand...
Click to collapse
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!

Actually, do this.
Once you have the drivers installed for Windows, and your phone is being recognized "adb devices"
Run
adb pull /data/media/DCIM C:Urname\example\blah
Replace the C:Urname\example\blah with an actual directory of the Windows PC
It might take some time but that should drag your pictures and stuff.

Here's the link with instructions to return to stock. http://forum.xda-developers.com/showthread.php?t=1366806

tman7510 said:
so how do I mount or do I just use the toolkit because it seems to tell me in bright green letters that I must be in android to use adb?? I guess that is a limitation of the toolkit. I'll try installing the android sdk to windows and see how that works. I will let you know how it goes thank you. Also do you have a link on how to restore it to a stock rom but not have to go through the whole rooting and unlocking process??? Thank you again for your help so far!!
Click to expand...
Click to collapse
Hit, Install SDK on the toolkit. It will do it very quick and easy for you.
Since the SD Card on our Nexus is actually /data/media, like I said earlier, just mount data.

Gnex toolkit is a great tool. I'm wondering why I have permission issues with adb in cwm recovery in Linux. not complaining but I wish there was a kit like that for us linux users

any body know why in cwm recovery if run ./adb device in linux you get
devices listed
?????????? no permissions
any linux users out there? I'm saving my files thanks to a windows program gnex tookkit by mskip.
Special thanks to Samsuck for all his help and the rest of the forum

[Q] CWM Bootloop w/ v5.8.2.0

Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.

Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?

Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.

ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro

edit: re-ran superoneclick for run and it worked! I should be good from here

Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.

So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...

I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA

lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?

Tokie the dropbox links are not working

reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys

cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.

when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one

dd: can't open sdcard\boot.img : no such file or directory

i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it

Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.

drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image

I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.

If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol

Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol

No ROM installed, stuck in recovery.

I was getting random reboots and I tried to delete everything. I thought "clean to install new ROM" would just do a thorough cleaning.
When I try to boot it stays on the white HTC screen.
I can boot into the recovery and Squabbi's HTC One M8 toolkit reads it.
However, I have no idea what files to flash or even HOW to flash them so I can get an OS back on my phone. Can somebody please help?
I have no ADB experience.

Copy a rom zip on external sd and flash it through recovery or use a nandroid backup if you have one, but as you want a clean install maybe you want to use the first method

lukes91 said:
Copy a rom zip on external sd and flash it through recovery or use a nandroid backup if you have one, but as you want a clean install maybe you want to use the first method
Click to expand...
Click to collapse
Thank you for your reply. I am currently in ADB i tried to do "adb sideload" but got an error "failed to write data 'protocol fault (no status)'
I am going to try "adb push" right now and see if that works.
In the meantime, is it possible for me to recover using RUU in my current state of being stuck in recovery mode? Thanks again. I'll make sure to hit that donation button.

decko5 said:
Thank you for your reply. I am currently in ADB i tried to do "adb sideload" but got an error "failed to write data 'protocol fault (no status)'
I am going to try "adb push" right now and see if that works.
In the meantime, is it possible for me to recover using RUU in my current state of being stuck in recovery mode? Thanks again. I'll make sure to hit that donation button.
Click to expand...
Click to collapse
Well, the error might be a recovery issue, a cable issue (use stock htc one) or a driver issue... Unfortunately no RUU is available, so search for a nandroid backup in mr hofs' thread, copy it on the external sd card and recover it... Use the same recovery the backup was taken with (should be noted near the backup)... Let me know if you need further help dude

lukes91 said:
Well, the error might be a recovery issue, a cable issue (use stock htc one) or a driver issue... Unfortunately no RUU is available, so search for a nandroid backup in mr hofs' thread, copy it on the external sd card and recover it... Use the same recovery the backup was taken with (should be noted near the backup)... Let me know if you need further help dude
Click to expand...
Click to collapse
Ok so i found my nandroid backup and i am currently i am in adb. how do i push the backup to the TWRP backup directory?

decko5 said:
Ok so i found my nandroid backup and i am currently i am in adb. how do i push the backup to the TWRP backup directory?
Click to expand...
Click to collapse
It's easier to mount the storage in twrp, so you can browse it with the computer and copy paste the file inside... Then unplug the phone and restore the nandroid...
Edit: in this thread
http://forum.xda-developers.com/showthread.php?t=2318497
there are very useful infos for you, and there is the adb push command you are looking for (path should be the same)... Let me know if you recover everything or if you need more help

lukes91 said:
It's easier to mount the storage in twrp, so you can browse it with the computer and copy paste the file inside... Then unplug the phone and restore the nandroid...
Edit: in this thread
http://forum.xda-developers.com/showthread.php?t=2318497
there are very useful infos for you, and there is the adb push command you are looking for (path should be the same)... Let me know if you recover everything or if you need more help
Click to expand...
Click to collapse
I flashed TWRP via fastboot. then i pushed a nandroid backup hosted on this site to the /sdcard/TWRP/backsups/<a directory i made here> finally got everything working. Thanks again for everything. I just hope the random rebooting doesn't come back.
I think it was rebooting because I disabled some bloatware apps via an app called App Master, which requires root. And when i restarted the phone, all those apps tried to run again but there was a conflict with App Master.

decko5 said:
I flashed TWRP via fastboot. then i pushed a nandroid backup hosted on this site to the /sdcard/TWRP/backsups/<a directory i made here> finally got everything working. Thanks again for everything. I just hope the random rebooting doesn't come back.
I think it was rebooting because I disabled some bloatware apps via an app called App Master, which requires root. And when i restarted the phone, all those apps tried to run again but there was a conflict with App Master.
Click to expand...
Click to collapse
Well, you can try to reinstall the rom without removing the bloatware... If it's stable you found the culprit

Problem Pixel don´t boot into ROM

Hi guys,
I was using latest version of TWRP + DU. I want to try CM13 ROM I did a backup, make a factory reset and install ROM, but it stucks at the end of the flashing process (more details here with 1 screenshoot: http://forum.xda-developers.com/pix...unofficial-t3393765/post67334545#post67334545 ) and when I try to restore my backup I get this error message "Failed to unmount `/system `(Device or resource busy)" and after that I can´t boot in to ROM.
I think that I have some problem with system partition, I try a lot of things and always there is a problem with /system, what can I do? Can I post some kind of log? What other relevant info/log/details can I provide for you?
Thanks in advance guys.

Istvan_86 said:
Hi guys,
I was using latest version of TWRP + DU. I want to try CM13 ROM I did a backup, make a factory reset and install ROM, but it stucks at the end of the flashing process (more details here with 1 screenshoot: http://forum.xda-developers.com/pix...unofficial-t3393765/post67334545#post67334545 ) and when I try to restore my backup I get this error message "Failed to unmount `/system `(Device or resource busy)" and after that I can´t boot in to ROM.
I think that I have some problem with system partition, I try a lot of things and always there is a problem with /system, what can I do? Can I post some kind of log? What other relevant info/log/details can I provide for you?
Thanks in advance guys.
Click to expand...
Click to collapse
You can try using ADB sideload to install an OTA image (not factory image). However, I think it might wipe your internal. I forget.

YevOmega said:
You can try using ADB sideload to install an OTA image (not factory image). However, I think it might wipe your internal. I forget.
Click to expand...
Click to collapse
Hi,
I´m very busy in the work, sorry for the delay of my answer. Can you give me a bit more information on what you mean?
Thanks in advance.

Istvan_86 said:
Hi,
I´m very busy in the work, sorry for the delay of my answer. Can you give me a bit more information on what you mean?
Thanks in advance.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/ota#fugu
Get the latest Ryu image from the link above, set up adb on your computer. There are guides all over XDA. Boot into TWRP - - > Advanced - - > ADB Sideload, then open terminal, with your pixel C connected to your computer. Run the command adb devices to check that your computer sees it, if it does, then adb sideload filename, where the file is the image you downloaded. Make sure you get the OTA image, not the factory image.

YevOmega said:
https://developers.google.com/android/nexus/ota#fugu
Get the latest Ryu image from the link above, set up adb on your computer. There are guides all over XDA. Boot into TWRP - - > Advanced - - > ADB Sideload, then open terminal, with your pixel C connected to your computer. Run the command adb devices to check that your computer sees it, if it does, then adb sideload filename, where the file is the image you downloaded. Make sure you get the OTA image, not the factory image.
Click to expand...
Click to collapse
Hi again,
I have adb and fastboot minimal package installed this is enough? also I´m downloading the 3 OTA from the link that you provided me but i can´t see what is the latest, they don´t have release date...
I´m afraid of losing my internal storage MTP doesn´t works for me and if I lost my sdcard I can´t transfer again the files for flashing things and try to repair my Pixel.
Thanks again mate.

Istvan_86 said:
Hi again,
I have adb and fastboot minimal package installed this is enough? also I´m downloading the 3 OTA from the link that you provided me but i can´t see what is the latest, they don´t have release date...
I´m afraid of losing my internal storage MTP doesn´t works for me and if I lost my sdcard I can´t transfer again the files for flashing things and try to repair my Pixel.
Thanks again mate.
Click to expand...
Click to collapse
MTP doesn't work in TWRP? That's a TWRP issue. Just try going to adb sideload and doing what I said. Also, I think the latest OTA is the H file.

YevOmega said:
MTP doesn't work in TWRP? That's a TWRP issue. Just try going to adb sideload and doing what I said. Also, I think the latest OTA is the H file.
Click to expand...
Click to collapse
When I run adb devices adb recognices my Pixel C. I´m going to sideload as you said, I post result in few minutes.
Really thanks for all your help.

Sorry I forget to swipe on recovery to start sideload but I get the error message: "CAn´t install this package over newer build - Updater process ended with ERROR: 7
Maybe I should try another package?

Hey YevOmega,
Finally I decide to use Nexus Root Toolkit and my Pixel C is fine again, I think I lost everything except recovery, but who cares?? xD
Now I just need to flash again Dirty Unicorns.
Really thanks for all your help mate.

Istvan_86 said:
Sorry I forget to swipe on recovery to start sideload but I get the error message: "CAn´t install this package over newer build - Updater process ended with ERROR: 7
Maybe I should try another package?
Click to expand...
Click to collapse
Istvan_86 said:
Hey YevOmega,
Finally I decide to use Nexus Root Toolkit and my Pixel C is fine again, I think I lost everything except recovery, but who cares?? xD
Now I just need to flash again Dirty Unicorns.
Really thanks for all your help mate.
Click to expand...
Click to collapse
You should have wiped /system and cache before trying to sideload, and it would have probably worked. Glad you're back in business though.

YevOmega said:
You should have wiped /system and cache before trying to sideload, and it would have probably worked. Glad you're back in business though.
Click to expand...
Click to collapse
Hehe, I take note of your advice for the next time. Now I´m running DU without any kind of problems.
Really thanks again for all your help.