So I was attempting to try a new rom - Android Revolution HD 3.0.0 -. I downloaded the rom, and super wipe script and booted into CWM recovery.
Ran the Super Wipe script and now it just hangs on reboot. I can still get into fastboot but I can't get into Android or Recovery. Whenever I try to boot into Recovery I get Andy with the spinning sphere. The blue loading bar hangs about 1/5 of the way across. Eventually the phone reboots and repeats.
I've tried gnex toolkit v5.6. I tried flashing a new recovery via the toolkit and I tried option 7(1-click for all). Both say they successfully installed the recovery but I still can't boot.
Any ideas?
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
zephiK said:
and this is why you dont use toolkits because you dont have a full understanding of what you're doing and relying on a program.
fastboot flash google stock images OR fastboot flash clockwork recovery in bootloader mode and then proceed to go into recovery mode and wipe factory(data)/cache/dalvik and flash a rom
i advise doing the second that i suggested. if all else fails, flash google images as a last resort
Click to expand...
Click to collapse
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
AverageCanadian said:
Thanks for the quick reply. I just assumed the toolkit would be a quicker way of doing the commands manually. That being said even fastboot flash recovery recovery-clockwork-5.5.0.2-maguro.img nets me the exact same results, so it looks like I'm off to google stock images
Click to expand...
Click to collapse
It is quicker in a sense. But with every short cut that you take, you're losing knowledge. Sure, you're rooting and doing all that fancy stuff. But you're not realizing what you're doing so when you have a problem.. you're unable to diagnosis it because you aren't aware of what that toolkit just did.
Okay. Then just flash google stock images.. after it boots into Android, just fastboot flash recovery again and then wipe and then flash your ROM.
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
AverageCanadian said:
back on stock rom for now . Will have to flash custom recovery later but for now I have a working phone again which is nice.
Click to expand...
Click to collapse
Glad to hear it was happy to see that you didn't panic and claim your phone being 'bricked.' Definitely weird how the superwipe script caused that problem on your phone. Personally not a fan of "superwipe" that's just me. Manually wiping factory(data)/cache/dalvik is good enough for me.
Same happened to me trying to install HD 3.0. I also had to go back to flashing Google stock after getting the boot loop you described. Would it have anything to do with that script trying to format partitions to ext3??
Sent from my Galaxy Nexus using XDA
Related
Hi,
i found a simliar thread that was talking about a similar subject, but didn't answer my question. i have lost it and cant find that same thread for help.
rooted -flashed bad rom - everything keeps closing(apps, Google sync)--- cant get int to recovery mode because of error
****I unlocked bootloader and rooted my GalaxyNex. then installed ROM maneger. i flashed CWM,then backed up my ROM. i tested it by flashing my backed up ROM, after i had messed around and my phone went back to normal. i was feeling safe. i noticed that i was having trouble getting into the recovery mode because of the belly open with exclamation Point. i read that it is because CWM was losing permission? i found that i just had to re-flash CWM every time right before i go into recover mode. i flashed a ROM from ROM maneger and everything worked until i turned the phone on. i cant sync Google account, and basically all apps close immediately (no key board too). I cant get into recovery mode and i cant down load ROM maneger to try to re-flash CMW to restore from older ROM.
I am sorry if this is already been answered i have try to find my situation but i couldn't.
I tried to re-flash the clock work recover image through the terminal of my mac but it says permission denied... i guessing i need to find a way to re flash to stock from fastboot is this possible ?
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
joshnichols189 said:
Pull the battery and hold power + volume and get into fast boot. Flash stock images from here
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Thanks I got really lucky i was able to re flash Clock work recovery in fast boot with the command
./fastboot flash recovery recovery-clockwork-5.5.0.4-toro.img
then i was able to get into the proper recovery mode and re flash my backed up image.
if i wanted to re flash a original image would the terminal command look like this
./fastboot flash recovery "Imagename" ? i might have just got lucky but i am guessing thats how you re-flash something to your phone?
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Glad your good! Hate to see these threads but we all go through it sooner or later
Sent from my Galaxy Nexus using xda premium
billycurtis said:
now that i have gotten back to the beginning, why is it that i have to re flash CMW every time to get in correct recovery mode? or how do i stop it from giving me the recovery error when trying to get to the correct recovery mode?
thanks again
Click to expand...
Click to collapse
After you fastboot flash the CWM image, use ADB, a terminal, or a file explore to remove or rename the file /system/recovery-from-boot.p
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
5.to flash a custom Rom just flash a custom recovery in the fastboot
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Edit: (credits to cpv5 for this info)Make sure you don't go to recovery when you're on stock recovery as it will wipe everything on your phone & virtual sdcard and you will be back to setup screen again.
gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
I've done that now, ta for that.
Sent from my HTC One X using XDA Premium HD app
gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
even better is that once you have done the OTA update to 1.28 you get the new Hboot which can boot properly so you never have to replace the stock recovery. just fastboot boot recovery.img if you need to change rom or nandroid
I dont think that the 1.28 Hboot has fixed the fastboot boot commands...
You can fastboot boot a recovery? not just a boot.img?
broncogr said:
I dont think that the 1.28 Hboot has fixed the fastboot boot commands...
Click to expand...
Click to collapse
it has because i have used it
flakz0r said:
You can fastboot boot a recovery? not just a boot.img?
Click to expand...
Click to collapse
and yes, you can boot a recovery aswell as a boot.img
bagofcrap24 said:
it has because i have used it
Click to expand...
Click to collapse
Very interesting, seems to be working for recoveries here as well (s-on unlocked hboot 0.94).
I'm really interested if this works properly for zImages as well. I thought PaulOBrein was working with htc for a solution for this "fastboot boot" though? Maybe some parts ain't working?
This is a great tip, thanks!
and is it just me, or does adb work when fastboot booting clockwork with the stock recovery flashed?!
bagofcrap24 said:
it has because i have used it
and yes, you can boot a recovery aswell as a boot.img
Click to expand...
Click to collapse
Are you using windows to fastboot boot or linux?
broncogr said:
Are you using windows to fastboot boot or linux?
Click to expand...
Click to collapse
Just tested it here, works on both host-machine types
It also lead to a nice find: http://forum.xda-developers.com/showthread.php?t=1594819&page=21
gunswordx said:
as i have seen many threads stating that in the custom recovery one cannot charge the phone, so i thought why not use the stock recovery after flashing the rom!!
1. i flashed a custom rom in the custom recovery
2. after the first boot, i went to the hboot and flashed the stock recovery
3.restarted the phone and booted back to the custom rom, no reboots, no hangs what so ever, rom booted normally
4. switched my phone off from the bootloader to check if it works and voila it is charging !!!!
i do know that you have to flash a recovery every time you flash a custom rom but till a proper fix is found it is better to do this than depend on your luck
Click to expand...
Click to collapse
I just add further note on your question here
See the edit part.
Thanks a ton ckpv5
Has a question here, how do we flash stock recovery in hboot? I only know the way of flashing stock recovery via fastboot with the command of "fastboot flash recovery [recovery name].img*
Is my way wrong or there is some other way?
Where do I get stock recovery from? Tempted to do this until cwm supports charging....
Sent from my HTC One X using Tapatalk 2
landwomble said:
Where do I get stock recovery from? Tempted to do this until cwm supports charging....
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You can get it from the link below
http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Btw bro, wanna ask if you are able to guide me on flashing the stock recovery? Is it the same way as flashing custom recovery?
williamyi said:
You can get it from the link below
http://forum.xda-developers.com/showpost.php?p=24738635&postcount=1
Btw bro, wanna ask if you are able to guide me on flashing the stock recovery? Is it the same way as flashing custom recovery?
Click to expand...
Click to collapse
yes same thing. not a single change except from the name
fastboot flash recovery (stock name).img
gunswordx said:
Edit: (credits to cpv5 for this info)Make sure you don't go to recovery when you're on stock recovery as it will wipe everything on your phone & virtual sdcard and you will be back to setup screen again.
Click to expand...
Click to collapse
ok so...when you mean this, you are saying that by simply going to hboot and afterwards "recovery", it will wipe it all?! wtf?!
any reason for it?
casca said:
ok so...when you mean this, you are saying that by simply going to hboot and afterwards "recovery", it will wipe it all?! wtf?!
any reason for it?
Click to expand...
Click to collapse
Because the stock recovery doesn't have menu like the CWM recovery, so once you choose recovery, the recovery process will run. Not like the CWM recovery, you need to choose which function to run.
So two things can happens when you go to recovery when you're on stock recovery:
1) the recovery will runs and wipe everything on your phone (I tested this)
2) the recovery will runs and there is error where you see the phone logo with red triangle, then you need to shutdown and restart to your current ROM.
ckpv5 said:
Because the stock recovery doesn't have menu like the CWM recovery, so once you choose recovery, the recovery process will run. Not like the CWM recovery, you need to choose which function to run.
So two things can happens when you go to recovery when you're on stock recovery:
1) the recovery will runs and wipe everything on your phone (I tested this)
2) the recovery will runs and there is error where you see the phone logo with red triangle, then you need to shutdown and restart to your current ROM.
Click to expand...
Click to collapse
ok, tks for explaining mate
What is the meaning of the error where you see the phone logo with red triangle
Dear All
yes, I am new and I feel exactly as the intro-video when registering was referring to ("noob", "loser",...)
After half a year, thought it was time to root my galaxy nexus. Used the Gnexus Toolkit. Everything worked fine.
So, I wanted to take things a bit further and as I've read interesting things on the franco.kernel, I tried to flash a new kernel using the app's automatic flash tool.
Device restarted, stuck at the Google logo.
I went inro recovery mode and followed some guidelines I found here and on other fora telling me to wipe data, wipe cache, wipe dalvik cache, format data,....
First tried to restore the "recovery"-thing clockworkmod creates for you when first using it. Didn't work.
Tried to wipe/format once again... Nothing helps and now I've even lost the "recovery"-thing.
only option seems to adb sideload... but I do not seem to get that working.
Well... hm. Here I am then. Having no idea to continue...
And, yes,... I have to repeat... I feel exactly as the intro-video of xda is suggesting I should feel
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
joooe said:
Install GNex TOOLKIT in the PC, download a custom rom and push the file to the phone with adb in fastmode. With this toolkit you can also flash recovery (CWM for example) again.
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
Thanks: I was indeed able to start in fastboot and used the Gnex Toolkit. I installed the stock image (4.0, then it updated to 4.2.1 later).
Pfffew, everything now works. hehe.
Thanks.
:good: Good result then.
joooe said:
I would probably start all over again.
Download latest version of ClockworkMod Recovery, go to fastboot mode, flash it.
Download rom, push it to the "sdcard" with adb, then go to CWM recovery and flash the rom.
Click to expand...
Click to collapse
That's indeed what I wanted to do.
Need to get some work done now. Will try it in the weekend. Thanks for the help.
I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
thetinyjesus said:
Hi guys I am trying to get my phone in some sort of working order. I have CWM Recovery 6.0.5.1 for some reason no matter what I do to change the recovery it stays the same. I've tried installing lower CWM and also tried installing TWRP which again it says it was installed but when i go to recovery it still shows the CWM recovery. I installed CM11 and it worked fine, when I installed gapps is when the problems started. I've tried install multiple roms now, and it just doesn't want to take anything
Click to expand...
Click to collapse
try restoring a stock nandroid backup. if you dont have one then download one from general thread. and also make a nandroid backup of your current rom. not so sure what your problem is but maybe returning to pure stock will help.
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Install/flash via fastboot the official cwm 6.0.51 that you had. then try again. if your lucky then it might work.
thetinyjesus said:
I am trying to load the nandroid but I cannot get this recovery to work right. I've tried installing openrecovery-twrp to install the nandroid but i cant get the CWM to remove. I really dont mind what bootloader is on there but anything just to install any rom
Click to expand...
Click to collapse
Get TWRP Manager from the play store. Hit the three line menu thingy on the top left of the app, and pick install TWRP. Super easy.
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
thetinyjesus said:
Ok guys ive tried reinstalling the same CWM version and reinstalling CM11 with no luck. I cannot change the bootloader to TWRP because it appears to be stuck on the CWM. The problem started for me when I installed the gapps through CWM, as soon as I did that when the phone went to boot it now says please enter the password for android, then says it was the right password but data is corrupt and cant use phone.
Is there a way to attempt to just format the entire phone including partition size and start from scratch again?
Click to expand...
Click to collapse
How are you trying to flash these recoveries (they're not called bootloaders, that is something totally separate)?
Have you tried using TWRP Manager as I suggested earlier, or are you using ADB? And If you are using ADB and trying to flash it that way, what fastboot commands are you giving?
There is no way that your should be "stuck" with CWM.
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Also when i try the command fastboot oemRUU or whatever the command is it reboots the phone shows CM logo and boots till asking for android pw
thetinyjesus said:
Okay what i have to do is fastboot its the only thing i can get to work. Not at my computer but yeah i fastboot the recovery img via cmd in windows. Fastboot flash recovey i use ane it successfully does. Doesnt matter what img or recovery i use when i boot into recovery it still uses cwm. Also only way i can put a rom on is adb sideload but now thats even failing with status 7 error
Click to expand...
Click to collapse
The status 7 error is because of an outdated recovery. Not much help, I know.
It's strange that the TWRP Manager doesn't work. I've helped others with problems flashing recovery, and it has worked for them.
You could also try ROM Toolbox to update your CWM, or ROM Manager, but ROM Toolbox is better/more complete. It has everything ROM Manager has plus some.
The other option that you may not want to take is to do a COMPLETE wipe of your phone. That always sucks.
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
@thetinyjesus You could also try this app. No PC necessary.
Thanks but cannot use the app i cannot get the phone to boot. Do you have directions for a full wipe
thetinyjesus said:
Going to try those programs. Thank you btw and how do i perform the full wipe i was about to throw the phone out lol.
Click to expand...
Click to collapse
Actually, you full wipe in recovery. lol
If you haven't tried TWRP Manager yet, that would be my first choice.
Damn that didnt work than i tried all those format options in the bunked recovery with no luck it sucks
If you're using the command prompt to flash the recovery, provide a screenshot of your desktop so that we can see what you're doing and what "it's" doing.
Starting to think that it's more of an "operator" fault and not anything to do with the device that doesn't want to play along.
Okay once im back home ill show the output
Here is the output from flashing the recovery. Once again when I went to recovery it loaded with CWM.
Also here is the output from sideloading the cm file again (same error no matter what rom I try)
Windows CMD: C:\Users\Jimmy\Desktop\platform-tool>adb sideload cm.zip
sending: 'cm.zip' 100%
Phone: Installing update...
set_perm_recursive: "/system" not a valid uid
E: Error in /tmp/update.zip
(Status 7)
Installation aborted
Anyone?