Root [International] [how to] get a rom to your sd card if your phone wont boot

[scotty85]

current recoveries are no longer supporing "mount usb storage" to transfer files(Exactly why,im not sure)

if you find yourself in a predicament where you need to flash a rom on a non booting phone,you have a couple of options:
1)push with adb

2)install via adb sideload

i personally used cw to test these,ill have to check twrp later.

push to sd card via adb
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check connectivity:
adb devices
(should return serial number)
4)push rom to sd card:
adb push romname.zip /sdcard/ (where romname is your actual zip file name)
5)you should then be able to simply wipe and flash the rom as you normally would.

*if you can find a nandroid for your particular build,you should be able to push that,with:
adb push nandroidname /sdcard/clockworkmod/backup/nandroidname/
(again,using cw. ill update if i can determine this to work for twrp)
be patient,the nandroid is a big file,so this will take some time.

2)install from adb sideload
1)place rom into adb/fastboot folder
2)boot to recovery
3)open cmd,check for connectivity
adb devices
(should return serial number)
4)select "install from sideload" from the recovery menu
5)in cmd,enter:
adb sideload romname.zip (where romname is your actual rom's name)
you should see it installing on the phones screen

hope this helps some folks,ill refine it later as i learn more about it. i did successfully sideload superSU,and pushed nandroids to clockwork/bckup and zip files to sd card.

again, the above was done with clockwork touch recovery

we will have to verify the processes with twrp

 

[Nimitz87]

appreciate you making this thread scotty.

ok I have adb running and see my device for the first time (using CWM and not TWRP)

when I go and try to adb push Nocturnal_1.27.531.7_Odex_unrooted.zip after pressing enter I get this error.

C:\Users\BAMF PC>adb devices
List of devices attached
FA35PW905487 recovery


C:\Users\BAMF PC>adb push Nocturnal_1.27.531.7_Odex_unrooted.zip /sdcard/
cannot stat 'Nocturnal_1.27.531.7_Odex_unrooted.zip': No such file or directory

C:\Users\BAMF PC>

ROM is placed in the adb/fastboot folder im so close!


edit: when I try the sideload method I get a "cannot read sideload" error.

 

[scotty85]

the errors your getting indicate the pc cant find the rom.i actually got the same error when i forgot to type inthe ".zip" file extension.

off the top of my head:
-you could have the name slightly off
-the file may be a different type(not a .zip)
-you could be in a different directory. if you have the sdk in your path,try cd:\ing to the actual folder where youve put the file
-maybe a name issue? i dont think your name should have any impact,but you might try shortening/simplifying the name.
-you also may try a different rom


ill ponder it some more the rest of the afternoon,im usually home around 8ish EST

 

[Nimitz87]

ok so I tried a different ROM, and after a few mins it pushed successfully! I flashed ARD and all is working, went ahead and made a backup

thanks so much for the help

 

[scotty85]

Awsome! Glad you are sorted

 

[Nimitz87]

well that didn't last long...I think something is actually wrong with my phone doesn't matter what ROM AOSP, AOKP, Sense, etc. i'll have random freezes and hard reboots which normally means I have to full wipe and install again.

well it happened earlier went to boot into recovery and no recovery boots, it freezes on the splash screen with "entering recovery"

at this point I just want the phone to work

 

[Nimitz87]

got cwm to boot after reflashing it via fasboot, however it froze in recovery and started boot looping....I rebooted and tried to get to recovery with it freezing on the splash screen again.

 

[scotty85]

got cwm to boot after reflashing it via fasboot, however it froze in recovery and started boot looping....I rebooted and tried to get to recovery with it freezing on the splash screen again.

Hmmm are you using the gsm image? Are you s on,or s off?

Have you changed kernels,overclocked,or made any other mods?

Changed cid or mid?

 

[Nimitz87]

Hmmm are you using the gsm image? Are you s on,or s off?

Have you changed kernels,overclocked,or made any other mods?

Changed cid or mid?

s-on, haven't changed cid or mid, the kernel has changed depending on some of the ROM's yes.

gsm image?

what other info can I provide?

 

[Nimitz87]

I could definitely use some help, right now I can't access adb thru fastboot/hboot for some reason at all.

right now my phone is a paper weight

 

[scotty85]

I could definitely use some help, right now I can't access adb thru fastboot/hboot for some reason at all.

right now my phone is a paper weight

you cannot access adb via hboot or fastboot,period. adb commands are used in recovery or the booted OS,fastboot commands are used with the phone in fastboot.

best bet is to flash a recovery,then do a full wipe and try and restore a backup or flash a stock rom. assuming you are able to flash a matching kernel run the phone a few days without flashing a rom or making mods and see what happens.

 

[Nimitz87]

you cannot access adb via hboot or fastboot,period. adb commands are used in recovery or the booted OS,fastboot commands are used with the phone in fastboot.

best bet is to flash a recovery,then do a full wipe and try and restore a backup or flash a stock rom. assuming you are able to flash a matching kernel run the phone a few days without flashing a rom or making mods and see what happens.

I can't flash a recovery, it just hangs on the "entering recovery screen" for about a minute then goes black and reboots.

 

[scotty85]

I can't flash a recovery, it just hangs on the "entering recovery screen" for about a minute then goes black and reboots.

Are you using the same image you've used before,and been able to boot to?

What is its md5?

 

[Nimitz87]

you cannot access adb via hboot or fastboot,period. adb commands are used in recovery or the booted OS,fastboot commands are used with the phone in fastboot.

best bet is to flash a recovery,then do a full wipe and try and restore a backup or flash a stock rom. assuming you are able to flash a matching kernel run the phone a few days without flashing a rom or making mods and see what happens.

Are you using the same image you've used before,and been able to boot to?

What is its md5?

yes sir, same clockwork I flashed the first time you recommended me to switch.

0a683c405219eef212016246d591eee8

 

[clsA]

did this get sorted or are you still stuck ?

 

[scotty85]

did this get sorted or are you still stuck ?

im under the impression he was sorted,now is stuck again.

yes sir, same clockwork I flashed the first time you recommended me to switch.

0a683c405219eef212016246d591eee8

is that the md5 you are actually getting? or just the one listed?

if thats not the one youre actually getting, check it and make sure. a bad download could easily casue the symtoms youre having.

once youve verified the md5,have you tried booting it directly to phone memory? use a imilar command:

fastboot boot imagename.img

that should boot it directly into phone memory. if that works,try restoring your working nandroid at that time,or flashing a rom.

try flashing as matching boot image,to be on the safe side,and let me know if there are any errors.

if the phone still wont boot,trry booting the boot image,just like with the recovery,just use the boot image name instead of the recovery image name.(example fastboot boot boot.img)

 

[Nimitz87]

did this get sorted or are you still stuck ?

was fixed, however a random reboot broke it again it seems.

im under the impression he was sorted,now is stuck again.


is that the md5 you are actually getting? or just the one listed?

if thats not the one youre actually getting, check it and make sure. a bad download could easily casue the symtoms youre having.

once youve verified the md5,have you tried booting it directly to phone memory? use a imilar command:

fastboot boot imagename.img

that should boot it directly into phone memory. if that works,try restoring your working nandroid at that time,or flashing a rom.

try flashing as matching boot image,to be on the safe side,and let me know if there are any errors.

if the phone still wont boot,try booting the boot image,just like with the recovery,just use the boot image name instead of the recovery image name.(example fastboot boot boot.img)

sorry, yes it is the correct md5 and checked with a hasher.

I also tried the touch/standard versions just for the hell of it.

I just tried the

fastboot boot imagename.img

when I do this the phone reboots, but not into recovery, if I vol down + power and try to reboot into recovery the same thing happens, hangs on entering recovery, and then reboots into a boot loop.

try flashing as matching boot image,to be on the safe side,and let me know if there are any errors.

if the phone still wont boot,try booting the boot image,just like with the recovery,just use the boot image name instead of the recovery image name.(example fastboot boot boot.img)

I'm not sure I follow what you mean by flashing a matching boot image.

where do I get the boot.img from? extract it from one of the ROM's?

sorry for such long delayed reply's, I work the third shift :/

I appreciate any and all feedback

 

[Nimitz87]

found this thread which seems somewhat similar problem

http://androidforums.com/t-mobile-o...ne-know-where-find-htc-one-m7-ruu-tmob-2.html

I have the same adb issues where it works and sometimes doesn't (very very frustrating)

I saw you asked for his getvar so here is mine

C:\android-sdk\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4331mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.047s

tried to flash the file you dumped and got this

C:\android-sdk\fastboot>fastboot devices
FAXXXXXXXXXX fastboot

C:\android-sdk\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.400s]
finished. total time: 0.400s

C:\android-sdk\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.040s

C:\android-sdk\fastboot>fastboot flash zip 1.29.1540.3miniruu_tmoible_.zip
sending 'zip' (951927 KB)...
OKAY [ 42.140s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 42.380s

C:\android-sdk\fastboot>

 

[clsA]

you have to relock the bootloader to run RUU
did you skip this step ?

and you also have to have the stock recovery installed

Not sure how much of this applies to you but it's worth reading up on how to get back to stock >> http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html

 

[Nimitz87]

you have to relock the bootloader to run RUU
did you skip this step ?

and you also have to have the stock recovery installed

Not sure how much of this applies to you but it's worth reading up on how to get back to stock >> http://androidforums.com/internatio...-return-100-stock-revone-moonshine-s-off.html

uh in the other thread, Scotty states the bootloader must be UN-locked, I'm not trying to restore to stock, I'm trying to get the phone in a state where it can boot any OS, not even running an RUU (since there isn't one for tmob) its just the RUU flash screen I believe.

also I can't flash a recovery, tried numerous times, hence stock recovery.

 

[clsA]

uh in the other thread, Scotty states the bootloader must be UN-locked, I'm not trying to restore to stock, I'm trying to get the phone in a state where it can boot any OS, not even running an RUU (since there isn't one for tmob) its just the RUU flash screen I believe.

also I can't flash a recovery, tried numerous times, hence stock recovery.

Humm.. I know it's stressful time but you need to take things slow.
You said earlier you flashed a rom from CWM
so you do have custom recovery.
does the phone boot to CWM now or no ? when you use power + volume down ?

 

[Nimitz87]

Humm.. I know it's stressful time but you need to take things slow.
You said earlier you flashed a rom from CWM
so you do have custom recovery.
does the phone boot to CWM now or no ? when you use power + volume down ?

sorry for the confusion but the thread was made for a different issue which scotty resolved. the current problem is from post #6-7

however I had a random freeze/reboot IN recovery and now I can't access recovery at all (boot loops) and flashing it fastboot shows it successful but does nothing when rebooted into recovery.

right now the only thing I can access is the RUU flash screen and Hboot/fastboot.

 

[clsA]

sorry for the confusion but the thread was made for a different issue which scotty resolved. the current problem is from post #6-7

however I had a random freeze/reboot IN recovery and now I can't access recovery at all (boot loops) and flashing it fastboot shows it successful but does nothing when rebooted into recovery.

right now the only thing I can access is the RUU flash screen and Hboot/fastboot.

the fastboot erase cache should stop the bootloop
then fastboot reboot and hold down on the volume should get you back to bootloader.

in bootloader go to recovery hit power you should be back in CWM

 

[Nimitz87]

the fastboot erase cache should stop the bootloop
then fastboot reboot and hold down on the volume should get you back to bootloader.

in bootloader go to recovery hit power you should be back in CWM

yeah thats a no go, hangs on boot into recovery screen, then screen goes dark, and reboots about 20 seconds later and boot loops from there.

 

[clsA]

yeah thats a no go, hangs on boot into recovery screen, then screen goes dark, and reboots about 20 seconds later and boot loops from there.

guess your returning it to T-mo then it's screwed