Stuck in a boot loop. Flashed drews latest ICS build. Was in Market when the phone just rebooted. It loops at the first HTC EVO 4G screen. Then it just keeps looping and restarting. I can load into bootloader. When I select Recovery, it just boot loops. I had Amon_RA installed. I tried flashing recovery again via fastboot but still nothing. Currently rooted with Revolutionary. help
Got it unrooted. Got S-On, going to try and flash the stock pc36img with the latest ota radio/recovery and all the good stuff.
the.emilio said:
Got it unrooted. Got S-On, going to try and flash the stock pc36img with the latest ota radio/recovery and all the good stuff.
Click to expand...
Click to collapse
I don't recommend flashing the latest OTA. That has the new HBOOT, which can't be rooted as easily as the previous versions. I would flash 4.54 or older, unlock with unrevoked or Revolutionary, and then you can update your radios, etc afterwards.
Dont Upgrade
I agree do not do the latest OTA.
I used to have a stock PC36IMG.zip that would fix that problem for you.
It has happened to me with a couple of Evo's at work.
If I find it I will post a link to it.
I personally wouldn't run an RUU I like flashing through bootloader better.
well still does the same thing. at least it is s-on now so I can just go to the sprint store.
Wow! Sorry to hear that. But I'll bet working with Cap'n you could get it up and running again without going to Sprint.
sent from AOKP heaven
went to the sprint store. they were unable to fix it so they will be ordering a new one. i am able to get into bootloader. since i flashd the latest ota when unrooting it, i went thru the steps to unlock it using htcdev.com. i now show it unlocked, flashed amon via fastboot, but when i select recovery, it still goes into bootloop. any other ideas? i really cant wait until wednesday to get a new phone.
When you select recovery it goes into a bootloop? Have you made sure the recovery md5 is good and then do the recovery as PC36IMG thru hboot/bootloader
sent from AOKP heaven
scottspa74 said:
When you select recovery it goes into a bootloop? Have you made sure the recovery md5 is good and then do the recovery as PC36IMG thru hboot/bootloader
sent from AOKP heaven
Click to expand...
Click to collapse
yeah. tried both amon and cwm. after they flash, i select recovery, it goes to the htc evo 4g white screen then just boot loops. i also saved it to the sd root as a pc36img and flashed thru hboot. says successful but same results. im stumped lol.
the.emilio said:
yeah. tried both amon and cwm. after they flash, i select recovery, it goes to the htc evo 4g white screen then just boot loops. i also saved it to the sd root as a pc36img and flashed thru hboot. says successful but same results. im stumped lol.
Click to expand...
Click to collapse
Try fastboot erase boot and fastboot erase data -w and user data then reflash your recovery(those will erase it). Then boot your recovery from pc cd. Format everything once more in recovery and try reflashing something I would recomend something stock/rooted.
Also if that build is based off new firmware which since it was ics it probably was it could of corrupted one of your partitions if you were still on old firmware.
Missed the part that you were s on now those commands might not work anymore.
Sent from my PG86100 using XDA App
mteezey said:
Try fastboot erase boot and fastboot erase data -w and user data then reflash your recovery(those will erase it). Then boot your recovery from pc cd. Format everything once more in recovery and try reflashing something I would recomend something stock/rooted.
Also if that build is based off new firmware which since it was ics it probably was it could of corrupted one of your partitions if you were still on old firmware.
Missed the part that you were s on now those commands might not work anymore.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Fastboot erase is not possible since it is no longer rooted. When i try to use this command, i get an error that it cannot be done. Can you elaborate more on the booting recovery from pc cd? If I can get recovery, I can unroot the device completely and flash a new rom and format everything.
Edit: C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: -0.000s
C:\android-sdk\platform-tools>fastboot erase data -w
erasing 'data'...
FAILED (remote: not allowed)
finished. total time: 0.001s
That is what happens when I run the commands mentioned.
If you used HTC unlock method to do what your doing now there should be a disc image of the recovery you wanna use. (Sorry im not using my og anymore haven't looked at recoveries in a minute). But if you take the recovery img put it in your platform tools folder. Then send command fastboot boot recovery.img(name it that to make it easy). You can flash it that way too fastboot flash recovery recovery.img Since you have s on now the fastboot erase boot is not gonna work unless u achieve s-off again. However you can try to flash the boot/kernel via fasfboot and then boot to recovery and flash the ROM.
Sent from my PG86100 using XDA App
mteezey said:
If you used HTC unlock method to do what your doing now there should be a disc image of the recovery you wanna use. (Sorry im not using my og anymore haven't looked at recoveries in a minute). But if you take the recovery img put it in your platform tools folder. Then send command fastboot boot recovery.img(name it that to make it easy). You can flash it that way too fastboot flash recovery recovery.img Since you have s on now the fastboot erase boot is not gonna work unless u achieve s-off again. However you can try to flash the boot/kernel via fasfboot and then boot to recovery and flash the ROM.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
That is how I was flashing it. I went thru the htc steps to unlock the bootloader, when I get to the step to flash the recovery, i downloaded the recovery provided in the steps on this site, flashed via fastboot but still a boot loop. I confirmed the MD5 matched. Also tried the pc3img file available, saved to root but still a no-go. Might just be a lost cause. I read somewhere else that everything tried still resulted in a boot loop. Just gonna file a claim and pay $100 for the Evo 3D
the.emilio said:
That is how I was flashing it. I went thru the htc steps to unlock the bootloader, when I get to the step to flash the recovery, i downloaded the recovery provided in the steps on this site, flashed via fastboot but still a boot loop. I confirmed the MD5 matched. Also tried the pc3img file available, saved to root but still a no-go. Might just be a lost cause. I read somewhere else that everything tried still resulted in a boot loop. Just gonna file a claim and pay $100 for the Evo 3D
Click to expand...
Click to collapse
You can't really go wrong there. It's well worth the money to upgrade. As far as the commands go you may have been able to save it if you were able to keep s-off and tried formatting thebpartitions that way. I had a similiar issue on an EVO 3d. Have you tried to RUU?
Sent from my PG86100 using XDA App
mteezey said:
You can't really go wrong there. It's well worth the money to upgrade. As far as the commands go you may have been able to save it if you were able to keep s-off and tried formatting thebpartitions that way. I had a similiar issue on an EVO 3d. Have you tried to RUU?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Yeah. Tried the last 2 4.54 OTA and the latest OTA. That is why I had to resort to the htc root attempt. I had ran those commands when i was still s-off, but a no go. Just gonna consider it a loss. Thanks anyways.
the.emilio said:
Yeah. Tried the last 2 4.54 OTA and the latest OTA. That is why I had to resort to the htc root attempt. I had ran those commands when i was still s-off, but a no go. Just gonna consider it a loss. Thanks anyways.
Click to expand...
Click to collapse
Yea I've been there. I feel for ya figured I'd try to throw some ideas out there. One last question did you flash the ota from the bootloader? Or ruu from pc?
Sent from my PG86100 using XDA App
mteezey said:
Yea I've been there. I feel for ya figured I'd try to throw some ideas out there. One last question did you flash the ota from the bootloader? Or ruu from pc?
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
From bootloader. Saved it as PC36IMG to my sdcard root, it recognized it, flashed it and said OK on all items (radio, recovery, and so on) then when asked to reboot, I select yes but goes into boot loop. Gonna file a claim tomorrow and hope that E3D offer is still going on from the insurance company for $100.
the.emilio said:
From bootloader. Saved it as PC36IMG to my sdcard root, it recognized it, flashed it and said OK on all items (radio, recovery, and so on) then when asked to reboot, I select yes but goes into boot loop. Gonna file a claim tomorrow and hope that E3D offer is still going on from the insurance company for $100.
Click to expand...
Click to collapse
The ROM update utility will probably fix it. I thought that was how you ended up with s-on. The ruu will format ALL the partitions in particular the ones you can't touch now. That's definatly the way to go. I hate to say it cause this is probably driving you nuts now. But I'm almost positive that will fix it and if it doesn't your phone had some sort of hardware failure and it was its time anyway. Ps with the 3vo cross your fingers and toes and hope you get hboot 1.4 or 1.3
Sent from my PG86100 using XDA App
Related
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
MobileWon said:
Please help me. I just got it yesterday. My girlfriend was already complaining about me spending the money on it. Now when she gets home...oh boy. I was trying to change the color of the status bar. I went into system/framework, restarted and now it's stuck at the T-Mobile screen.
I just rooted it with adb. I don't have the Clock recovery installed. I don't have alot of time either. Please tell me my options. Here is my hboot screen.
VISION PVT SHIP S-OFF
H-BOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Click to expand...
Click to collapse
Every phone i have had from the g1, mytouch 3g, vibrant, and now g2 it never fails to amaze me how people who dont know what they are doing manage to brick their phone in under a day. PROTIP READ learn what you are doing before you go in doing it so you dont screw yourself.
If you have the hboot menu and you seem to have s-off so you can restore official htc rom or a custom rom
Sent from my HTC Vision using XDA App
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Hot_Hands said:
Yeah. Best bet would be to flash a custom recovery through fastboot and then reinstall the stock rooted rom or install a custom ROM.
And hopefully not make things worse botching the recovery flash
Click to expand...
Click to collapse
Yup, exacly what he said.. also, I don't think editing the statusbar from a stock is possible because its odexed, correct me if I am wrong though.. unless you really know what you're doing.. so now after flashing recovery, try again with a nandroid if you have yours if not with fastludeh's stock odex or deodex rom if you want to keep it stock.
Sent from my HTC Vision
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Hot_Hands said:
You'll need to download this to your android-sdk tools folder:
http://koush.tandtgaming.com/recoveries/recovery-clockwork-2.5.1.2-vision.img
Then go into fastboot and type
fastboot erase recovery
followed by
fastboot flash recovery recovery-clockwork-2.5.1.2-vision.img
From there you should put a custom ROM (probably CM6 or enomthers) or rooted stock as advised above on your SD card, boot into clockwork, wipe system/data and install the ROM (and gapps if you do CM6).
And please remember: nandroids are your friend
Click to expand...
Click to collapse
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
Nope. Just put it on your SD and flash from recovery.
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
No, you do not need to rename it.
Sent from my HTC Vision using XDA App
MobileWon said:
Thanks, I,m gonna go with the enomthers rom. Do I need to rename it before flashing?
Click to expand...
Click to collapse
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
EDIT: Oh wait, it says SHIP S-OFF, shouldn't it say ENG S-OFF if you had the ENG boot loader? Did you even flash the new HBOOT?
KoolKidsKlub said:
And just so you know, your lucky that you flashed the ENG HBOOT, without that, you would have been screwed.
Click to expand...
Click to collapse
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
ianmcquinn said:
Wait, does he have engineering HBOOT installed? The HBOOT screen he listed says SHIP. Without the ENG HBOOT, he won't be able to fastboot the ClockworkMod Recovery.
To the OP, you probably will have to flash back to the official HTC ROM. See this thread: http://forum.xda-developers.com/showthread.php?t=788489.
And yes, as others have stated, you should make a nandroid backup prior to messing with system files. You cannot edit the framework without DEODEX-ing the system first.
Click to expand...
Click to collapse
Yeah I just noticed that and edited my post about 1-2 minutes ago.
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
MobileWon said:
Ok, I entering these commands in cmd window right? Just like I did for rooting, right? If so, it said failed, not allowed when I input fastboot erase recovery.
Click to expand...
Click to collapse
Yeah ummm you might be screwed, we assumed that you flashed the engineering HBOOT, and only with the engineering HBOOT can you use fastboot to save your self and it seems like you don't have it. I'm not sure what to do now, I think some one said that you might have to flash the stock ROM but I'm not sure how. Wait around for some other guys to help you out, they know more than me with this stuff.
Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Ok, I have the stock rom already. How do I flash a RUU? Or can you give me a link?
Hot_Hands said:
The guys above were right. I saw s-off and assumed you had the eng-hboot. Sorry. At this point you're going to have to flash an RUU and go back to stock and then try again.
Click to expand...
Click to collapse
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
EDIT: And if you do have to flash an RUU, could you please explain how? I would like to know how just in case I screw something up(which I probably won't because I have been on my computer searching the forum, asking for help and to double check that what I have learned is correct and what to do if something bad happens for the past week or two) and I can also use the information to help other users.
KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
That was a warning because if you had S-Off and root it would put S-On and remove root. It was an issue because for a while it was impossible to root the DZ's 1.72 RUU but this has since been worked around and doesn't apply to the G2.
Ok, guys Im not an idiot. I previously had a HD2 and had no problems...just rushing to get my phone right before I go out of town for the weekend. So, whatever I have to do to get it right.
KoolKidsKlub said:
Are you sure he can do that? Because theres like a sticky in the dev section of the forums saying NOT to do that unless you know what your doing or only if you flash the EXACT same ROM that came shipped with your phone, or something like that.
Click to expand...
Click to collapse
You might be right.
Ok,... So you have gone into your Hboot screen, select fastboot, then it says Fastboot on the screen yeah? Do:
fastboot devices
in cmd, do you get anything?
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
xIC-MACIx said:
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
Click to expand...
Click to collapse
the development section. only dev question ? ok
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
If you have the factory image, from Google (and nowhere else), just run the flash-all.bat file. You "may" have to unlock your bootloader prior to running it if you haven't already, and you'll need to have the device in fastboot mode prior to running the batch file too, but once those 2 simple tasks are done, the batch file takes care of the rest.
If your using a toolkit or some other method for flashing a factory image, I suggest stopping, and just doing the above.
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
craigacgomez said:
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
Click to expand...
Click to collapse
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
lKBZl said:
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
Click to expand...
Click to collapse
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
dboftlp said:
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
There is... i've seen a post in google + from a guy that links you to a google page with n10 4.2.1 img.
sikagoon7 said:
Nexus 10 hasn't gotten the (JOP40D) images yet which means the only way to get the 4.2.1 update is to get an OTA. I think the OTA link is floating around AndroidPolice and AndroidCentral somewhere but you'll have to look. Whatever images for 4.2.1 on the Nexus 10 are fake because Google hasn't even released them yet.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
dboftlp said:
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
lKBZl said:
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
Click to expand...
Click to collapse
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Watcher64 said:
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Click to expand...
Click to collapse
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
lKBZl said:
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
Click to expand...
Click to collapse
I don't see how that would matter, I used the aosp browser as well, and all I did was put stock recovery back on ..
hmmmm
Maybe you should just flash one of the updated stock/rooted roms in the dev section.
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
EDIT: when I get the no command "fallen android" when i select recovery from the bootloader on pressing power+vol up does give me acces to the stock recovery. But even on using wug's 1.6.6 root kit I'm unable to root the device and install a custom recovery
Vikas Rao said:
I was running TWRP with the franco kernel and stock rom on my nexus 4 4.2.2. When I got my OTA update notification, I did the needful and reverted back to stock rom and un rooted the phone using wugs root kit. Like wise the update was successful and I went about restoring all the backup's i created using wugs root kit 1.6.4.
Now the issue is after all this when I went about rooting the thus phone, I faced horrors for which I couldn't find exact answers on this forum. I want to flash TWRP 2.6 and to do that I went into fastboot and tried to flash it, but i keep getting an error saying "cannot load recovery.img: No error. And when I do try into get into the stock recovery then I get an image of fallen droid with a red exclamation mark and a message saying "No Command". Can anyone tell me what is the issue and how can i fix/workaround it..
Thank You:good:
Click to expand...
Click to collapse
Have you tried redownloading twrp seems like a bad download?
yamani.m said:
Have you tried redownloading twrp seems like a bad download?
Click to expand...
Click to collapse
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Vikas Rao said:
Tried Twrp, CWM and stock recovery too!! No luck, Still can't access recovery!
PS I tried to flash recovery buy using wug nrt which has not still been updated for JB 4.3 to begin with that is, later used fastboot
Click to expand...
Click to collapse
I would try to flash the full stock google image with fastboot and see what happens ?
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
I also did it this morning, works fine
EddyOS said:
Using fastboot to flash the recovery definitely works as I've done it, just have to make sure you use the right command:
fastboot flash recovery recovery.img
Make sure you're using the correct filename of the recovery image you have, I prefer to rename mine recovery.img so I can't get it wrong. Also make sure you're not putting recovery.img.img - sounds silly but people do do it!
Click to expand...
Click to collapse
Nope did the same thing! gives me the cannot load error, I just copy pasted the filename so can't go wrong there. And a stock rom flash is an option but the thing is i don't have a custom recovery nor root access for titanium backup don't wanna spend time again personalizing. I'm sure there is a simpler way.
Ok, so I unlocked my Nexus 7 (2013). Then I was trying to root it and after booting it into the bootloader, I typed:
"fastboot flash boot twrp.img" I was supposed to type "fastboot flash recovery twrp.img"
PLEASE HELP! My device boots into TWRP EXCLUSIVELY!
How do I get my os back? Is it gone? Can this be easily fixed?
I will be eternally in your debt if you can help me out, I feel so stupid, this is the first time I've bricked something and I've been unlocking, rooting, flashing android devices since my G1, then my Nexus One, which I even repartitioned the system partition so it could fit 4.2.2 Cm 10. I also unlocked, my touch pad and flashed cm dual booting with web os. Unlocking/rooting/flashingcustomrecovery on my Nexus 4 was a one click though so I guess I was rusty.
Edit: messed up a bracket in the title... Great...
I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app
Coronado is dead said:
I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't have a rom image on my device though? How can I get one on there when I can only get into the bootloader or recovery...
Thanks for responding! I hope I can get this fixed...
In TWRP I think there is a way to mount USB and transfer it over. Maybe under advanced?
Sent from my Nexus 7 using xda app-developers app
Hmm maybe someone could make a .zip file to flash the boot loader in twrp
And there is always the option of getting the factory image from Google and using it over USB with fastboot on. Clean slate.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:54 AM ---------- Previous post was at 12:53 AM ----------
How to factory image restore:
http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using xda app-developers app
Flash any custom kernel, as it stands as "boot" partition.
Or just flash the boot image manually from the factory image:
Code:
fastboot flash boot boot.img
Then flash TWRP like normally you did before:
Code:
fastboot flash recovery recovery.img
Sent from my Galaxy S3 i9300
If you can go to bootloader or TWP, then you have many choices to fix your Nexus.
1. Download a factory image from Google, boot to bootloader and flash the whole thing. And remember to download the right factory image for Nexus 7(2013) (flo or razor). Check MD5 after downloading to make sure everything is OK. If you dont know how to flash a factory image, there is a couple topics in General and Q&A to assist you.
2. Or you can download a custom kernel in the Original Development area. THen boot to TWRP, use ADB to push the custom kernel file to your device, then install it by TWRP.
3. You can use a toolkit which I dont recommend.
Ok, so in my frantic attempts to fix this, I was trying to get adb sideload to work and was told to try and do a factory reset and wipe system and internal storage. I did this and still can't figure out how to get sideloading to work, I'm trying adb sideload rom.zip, and adb push rom.zip /sdcard which is what I read from another thread, but have not been able to get the factory image over.
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>
OH GOD!
Download the Factory Image of Android 4.3 for ‘razor’ Nexus 7 tablet from here.
> this download contains the full system, bootloader, recovery and kernel boot img files.
Extract the ‘tgz’ factory image archive and place all contents into a single folder.
Next, you will need to edit a file so that your data will not be wiped. If you want to wipe data then you should skip this step.
> so, edit the ‘flash-all.bat’ for Windows or ‘flash-all.sh’ for Mac / Linux using a text editing tool:
- you will need to edit the ‘fastboot update’ command so that it will transform from ‘fastboot -w update image-razor-jss15j.zip’ into ‘fastboot update image-razor-jss15j.zip’. You will basically need to delete the ‘-w’ text, which is the command that tells fastboot to wipe data from your device.
- continue to the next step when you’re sure that the ‘-w’ text has been removed.
Now, power off your Nexus 7 2013 tablet.
Boot it into Bootloader Mode.
Connect it with your computer via USB cable.
Run the ‘flash-all’ script and wait for the factory image to be successfully installed.
Ok, so I did this, I downloaded the factory image, and ran the flash all command and that failed and now it's hard bricked! here is a screenshot of what the flash-all command output...
I will seriously pay someone to help me fix this at this point! I'm freaking out!
http://imgur.com/XsAJ4FV
mattj7 said:
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>
Click to expand...
Click to collapse
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.
Never mind, the problem had been solved.
sfhub said:
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.
Click to expand...
Click to collapse
Yes, it was the factory image for the first nexus 7, I just ran the flash all on the right one and now I can boot just fine
WHEW
Ok guys, great job everyone!
Now I'm going to figure out if the custom recovery is still there, it probably isn't, and I can just flash it with fastboot now.
slamdunksaliby said:
Hmm maybe someone could make a .zip file to flash the boot loader in twrp
Click to expand...
Click to collapse
The only way is by the fastboot way, because it's an .img file
And don't forget that you can find all files that you need to this thread => [Index] REPO for all you need for your nexus 7 FLO (2013)
philos64 said:
The only way is by the fastboot way, because it's an .img file
]
Click to expand...
Click to collapse
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:
Nburnes said:
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:
Click to expand...
Click to collapse
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.
philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).
sfhub said:
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.
Click to expand...
Click to collapse
Nburnes said:
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).
Click to expand...
Click to collapse
No problem
But as I said, almost users don't flashed by the way of the partitions.
It would be better to say the easiest way
Sent from my HTC One using Tapatalk 4 between sky and earth
I had to do a complete wipe from the computer and flashed clockwork mod recovery. Since it was likely an old version I had the double 0 partition problem which I fixed by manually moving the files. I tried to update the recovery to twrp, but it won't flash using goomanager. It downloads and says it's flashed but it's not there.
I also seem to have a weird problem where I have to push the power button to get it to boot past the Google screen. If I don't push power it gets stuck there forever.
Any ideas?
Sent from my Galaxy Nexus using Tapatalk 4
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
SlowCobra96 said:
Follow the sticky at the top that says flashing a factory ROM using fastboot/return to stock. Start from scratch, get it working, and then flash whatever you want.
Sent from my Nexus 7(2012) that has zero issues.
Click to expand...
Click to collapse
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
T-Keith said:
That's what I did, that's why I'm stuck on the old recovery.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
This might be an odd question, but have you tried just updating CWM first, and THEN flashing TWRP? Sometimes the flash won't go smoothly with an older version of one recovery to a newer version of a different recovery- not sure why, but that's just been my experience. I would update CWM first then try flashing TWRP.
Also, if goo is not working for you, you could try Rom Manager to update CWM and then flash TWRP. It can flash either. (If you really want to flash via the device).
Otherwise, (me personally) I'd just use adb fastboot to flash a new recovery.
Hope that helps
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Thanks I will try that.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
No problem. Let us know how it works out for you.
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
T-Keith said:
Tried flashing with fastboot, now it won't boot into recovery, just hangs at the Google logo.
Still needs a bump from the power button to get it to boot normally.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Ahh, that sucks! How are you *attempting to* access recovery... via reboot menu, via adb, or via 3-button press? It shouldn't matter, but you could try all three methods to see if any way will give you recovery access. Then, if/when you manage to get in, you could reflash again straight from recovery. I'm going to do some digging to see if I can find a better solution. I KNOW I've read about the same issue before, I know there's a solution... I just have to find it again.
Worse comes to worse, you might have to reflash stock recovery then reflash custom recovery. Might be a corrupt recovery img, but I will check and try some things out and let you know what I find.
Edited to add:
Yes. there was a bug in the older bootloader that bypassed/refused access to recovery... so since you restored stock, you probably need to update your bootloader to at least to version 4.18 (via fastboot). THEN you should be able to access recovery. I can't add links, but I can give you a text link once I find just the IMG file instead of the full firmware. Honestly, I never do backups so I don't have the file on hand. However, I may do one backup at least so I can extract my boot img and give it to you.
OK, so I found the info I was looking for.
From Elsewhere:
Steps:
Install latest nexus 7 bootloader.
This fixes the boot loader bug and now you can enter recovery from the bootloader screen.
Update the bootloader to at least 3.18. Make sure NOT TO DELETE THE BOOTLOADER!!!!!!!!!!!!!
I cannot emphasize this enough!!!!!!!!!!! I bricked my first one this way.
Use
fastboot flash bootloader C:\>>>>>>\bootloader-grouper-3.18.IMG***
Click to expand...
Click to collapse
Do NOT erase bootloader before you flash the new one. And after you have flashed the new one type;
fastboot reboot bootloader
Click to expand...
Click to collapse
and check the bootloader version to make sure you succeeded.
Click to expand...
Click to collapse
***Or whatever you name the boot img file!***
https://dl.dropboxusercontent.com/u/19608328/boot.img.zip --> This is from MY Nexus 7. It's Bootloader version 4.23, and works with JB 4.2.2- it does NOT have the recovery access bug.
https://dl.dropboxusercontent.com/u/19608328/recovery.img.zip --> This is a copy of MY CWM, which I just updated to 6.0.3.6 yesterday.
I'd flash the bootloader, then flash your recovery of choice. Not being able to access recovery is a bootloader issue, not a recovery issue. The fact that you restored/reverted an older full firmware put you on an older bootloader that would not allow users to access recovery.
Try the new(er) bootloader, it should work. My device is a 16gb grouper Nexus 7 running 4.2.2. Before that, it ran 4.1.2 without any issues, so it should work to resolve the problem you're having.