im getting this issue where i cannot flash another recovery after i flashed twrp 2.5....im trying to flash roms and its not working without an error, and its telling me i have no OS so im not sure what to do or what options i have, ive tried flashing boot.img first but still no OS or rom is being flashed
How are you trying to flash the recovery?
bananagranola said:
How are you trying to flash the recovery?
Click to expand...
Click to collapse
through fastboot, i flashed clockwork, trying to get rid of twrp and now its like i have two recoveries...? like i flashed the rom and now im sitting on the boot screen...i followed the guide, im just not sure why i can access both recoveries and now flash the rom properly
i cannot get into the OS only recovery
What command? Is your phone in fastboot? Do you volume keys work?
bananagranola said:
What command? Is your phone in fastboot? Do you volume keys work?
Click to expand...
Click to collapse
Well, I followed everything correctly...buts it's like I have two recoveries now...clockwork and twrp, idk why, but sometimes one will show and sometimes the other will...but when clockwork comes up, I can now flash custom roms
Sent from my EVO using xda app-developers app
Rocklee99 said:
Well, I followed everything correctly...buts it's like I have two recoveries now...clockwork and twrp, idk why, but sometimes one will show and sometimes the other will...but when clockwork comes up, I can now flash custom roms
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
You didn't answer a single one of my questions...but I guess your problem is somewhat solved anyway.
bananagranola said:
You didn't answer a single one of my questions...but I guess your problem is somewhat solved anyway.
Click to expand...
Click to collapse
I'm sorry, yes, I think it's solved, I don't remember exactly what was going on, it was really late when I was working on it, sorry for the ignorance when it comes to these things,but ty for the help
Sent from my EVO using xda app-developers app
Related
what are the differences between the two and what are the disadvantages and advantages?
Thanks
Sent from my LG-P999 using XDA App
moshe22 said:
what are the differences between the two and what are the disadvantages and advantages?
Thanks
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
i think you mean nvflash vs. rom manager?
moshe22 said:
what are the differences between the two and what are the disadvantages and advantages?
Thanks
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
With nvflash if your phone gets caught in a bootloop you will be able to boot into recovery and save it. If you just have clockwork intalled through RM your SOL.
crazythunder said:
i think you mean nvflash vs. rom manager?
Click to expand...
Click to collapse
Yeah I meant rom manager
Just edited title.
Sent from my LG-P999 using XDA App
moshe22 said:
what are the differences between the two and what are the disadvantages and advantages?
Thanks
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
NVFlash method truely replaces your old Recovery
Rom Manager method simply runs update.zip to simulate a custom recovery. The issue with the G2x is there is no true "stock recovery". Instead it simply reformats your phone. What this means, basically, is that the only way to get to this custom recovery is through the OS.
This doesn't mean that the Rom Manager method won't improve over time. I actually suspect it will. However, for now NVFlash is the only way to go.
MWBehr said:
NVFlash method truely replaces your old Recovery
Rom Manager method simply runs update.zip to simulate a custom recovery. The issue with the G2x is there is no true "stock recovery". Instead it simply reformats your phone. What this means, basically, is that the only way to get to this custom recovery is through the OS.
This doesn't mean that the Rom Manager method won't improve over time. I actually suspect it will. However, for now NVFlash is the only way to go.
Click to expand...
Click to collapse
I actually got to what seemed like a stock recovery... it had blue font and said something like android recovery...
I got into it by deleting my rom manager cwm and then told it to boot into recovery
Not sure if it means anything tho... maybe it would make it easier to flash a custom recovery without nvflash?? don't think so tho.... I haven't use android since the mytouch 3g and we used to flash through fastboot right on the phone...looks like we can't do that anymore?
*** At least I think it was through fastboot ***
hypmatize said:
I actually got to what seemed like a stock recovery... it had blue font and said something like android recovery...
I got into it by deleting my rom manager cwm and then told it to boot into recovery
Not sure if it means anything tho... maybe it would make it easier to flash a custom recovery without nvflash?? don't think so tho.... I haven't use android since the mytouch 3g and we used to flash through fastboot right on the phone...looks like we can't do that anymore?
Click to expand...
Click to collapse
Sorry, didn't entirely mean to say that there is no stock recovery. It's just that there's no hardware way (that anyone knows of) to access it. Then, since you can't access the stock recovery through hardware, you can't access the custom recovery through hardware either....at least I wasn't able to. Now that I have NVFlash, I can't really test any further either
So how would you reboot into recovery after using the NVflash method?
andonnguyen said:
So how would you reboot into recovery after using the NVflash method?
Click to expand...
Click to collapse
nvflashing clockword mod remaps vol. down and power to cwm recovery
This is my first Android phone and while I am familiar with CWR thru my rooted Nook Color, this is the first I have heard of NVFlash Recovery. Is there a tutorial or (noob) guide?
Thanks in advance.
crazythunder said:
nvflashing clockword mod remaps vol. down and power to cwm recovery
Click to expand...
Click to collapse
That same function gets you in to the factory recovery as well, when not rooted, its the first thing I tried when I got my G2x.. holding power and vol. down until the LG screen pops up then the little android with the box comes up.. from there i believe i either pushed vol. up or down.. I'm betting it was down.. and you get in to factory recovery. The only thing is when I exited the factory recovery, the phone did a factory reset on reboot.
Hey guys..
I just today rooted my lovely Nexus S, 9023 or what its called (non branded or nothing)
But i cant load recovery.. went fine when i rooted it, but now that i want to load an custom rom it fails.. i followed this guide to root: http://forum.xda-developers.com/showthread.php?t=883032
Anyone have some ideas??
I just get a android logo and triangle + ! in it.. as error.. (
Best regrads
n0ta
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
n0ta said:
Just tested with ROM Mananger, it can backup just fine.. as soon i choose a ROM to install it loads recovery and fails, just like when you do it manually.
Click to expand...
Click to collapse
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
I have had this happen on my NS4G. I know they are a little different, but it seems like you are having the same thing happen that I did and to solve it, I open Windows command prompt(or terminal depending on you OS) and fastboot flash recovery (insert recovery.img name here) and reflashed the recovery partition with clockwork. Very easy fix. Just make sure you boot straight into recovery after flashing and flash the Rom you want to flash before booting back into stock(also make a nandroid before that). After that you shouldn't have any more problems unless you unroot. There must be a small glitch somewhere when flashing the clockwork doesn't fully erase stock recovery partition.
krohnjw said:
Sounds like stock recovery installed itself. If you are rooted remove/rename /etc/install-recovery.sh then reflash cwm manually or through rom manager.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
Works now thanks all to both of you.
n0ta said:
Works now thanks all to both of you.
Click to expand...
Click to collapse
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
bender_123 said:
Pretty common lately...Android for Nexus S recovers its recovery if it is changes...
"You dawg, we heard you like recovering your recoveries, so we made recovery recover in recovery." and all that...
Click to expand...
Click to collapse
The Nexus one did the same thing. Most OTAs verify / replace this file. It's easy enough to deal with if you're unlocked and rooted.
Sent from my Nexus S 4G using XDA Premium App
This is about the third or fourth time this question has come up over the past week...
bender_123 said:
This is about the third or fourth time this question has come up over the past week...
Click to expand...
Click to collapse
I assure you it won't be the last.
Sent from my Nexus S 4G using XDA Premium App
Just installed victoryrom v1.1 and after a reboot, I noticed that I no longer boot into CWM. Do I need to redo the bootstrap recovery?
squid4 said:
Just installed victoryrom v1.1 and after a reboot, I noticed that I no longer boot into CWM. Do I need to redo the bootstrap recovery?
Click to expand...
Click to collapse
No, you need to flash CWM on boot.
Im sorry, but what do you mean by flashing it on boot?
squid4 said:
Im sorry, but what do you mean by flashing it on boot?
Click to expand...
Click to collapse
Maybe I misunderstood what you were trying to do.....
I was under the impression that you expected your phone to reboot into CWM when you reboot your phone. Otherwise, what you need to do is open the Atrix 2 bootstrap app and click "boot recovery" and it'll reboot into recovery.
Yeah I want my phone to boot into CWM every time I reboot. I'm just not sure what you mean by flashing CWM on boot. Thanks for the quick replies.
squid4 said:
Yeah I want my phone to boot into CWM every time I reboot. I'm just not sure what you mean by flashing CWM on boot. Thanks for the quick replies.
Click to expand...
Click to collapse
Did it do that before? How did you get it to do that? The only way I know of is by flashing a mod called CWM on boot.....but u sounded like u didnt know what i was talking about when i suggested you flash it.
Sent from my MB865 using XDA App
Check development forum
The development forum has the link for the Atrix2 bootsrapper. Here is the link below.
http://forum.xda-developers.com/showthread.php?t=1346977. I have used this to help with a bootloader issue I had. The developers and people on these forums are helpful. This will give you the CWM make sure you give it root access this will help with booting into recovery.
thethird84 said:
The development forum has the link for the Atrix2 bootsrapper. Here is the link below.
http://forum.xda-developers.com/showthread.php?t=1346977. I have used this to help with a bootloader issue I had. The developers and people on these forums are helpful. This will give you the CWM make sure you give it root access this will help with booting into recovery.
Click to expand...
Click to collapse
Having the bootstrapper installed wont boot him right into cwm upon reboot though. Besides, doesnt the rom he installed come prerooted?
Sent from my MB865 using XDA App
I redid the bootstrapper app and flashed the Razr cwm by JY Daddy again. It seems to be working just fine.
squid4 said:
I redid the bootstrapper app and flashed the Razr cwm by JY Daddy again. It seems to be working just fine.
Click to expand...
Click to collapse
Glad you worked it out
squid4 said:
I redid the bootstrapper app and flashed the Razr cwm by JY Daddy again. It seems to be working just fine.
Click to expand...
Click to collapse
Don't forget cwm on boot generally wrecks GPS.... if you want it back you have to get rid of can on boot.... you can flash it out with a zip same place u got cwm on boot....
daavvis said:
Don't forget cwm on boot generally wrecks GPS.... if you want it back you have to get rid of can on boot.... you can flash it out with a zip same place u got cwm on boot....
Click to expand...
Click to collapse
Yeah, if you're having an issue with GPS this is likely the culprit....but I've used RebelROM and now VictoryROM with CWM on boot and GPS worked fine.
916x10 said:
Yeah, if you're having an issue with GPS this is likely the culprit....but I've used RebelROM and now VictoryROM with CWM on boot and GPS worked fine.
Click to expand...
Click to collapse
Cool I didn't know anyone figured it out
Sent from my MB865 using XDA
i had 5.8.2.7 and i flashed to 5.8.4.0 and now when i try to boot into recovery it just sits at the HTC screen for a while and then reboots
Use twrp instead. Clockwork isn't officially supported on our phone. Twrp is.
That or just fast boot into recovery. Is that way not working either?
Sent from my HTC One X using xda premium
The only way I've had any success getting into Recovery with CWM is to go into Rom Manager and boot into recovery from there.
rushwal said:
The only way I've had any success getting into Recovery with CWM is to go into Rom Manager and boot into recovery from there.
Click to expand...
Click to collapse
I had exactly the same problem, the only thing that ended up working for me was installing Goomanager and doing it from there.
Menu > Install OpenRecoveryScript. This will install TWRP, and worked a treat for me.
I've noticed that when you first do the fastboot flash recovery that when you adb reboot into recovery, or even manually boot into recovery, it won't boot into it the first time. It will after you try again though. This has happened on 3 One X's so I know it's not a single phone specific thing.
Use TWRP, but don't be lazy and do it from the app, it didn't work for me, and just doesn't feel as reliable as my trusty adb commands. If you need help on what commands, PM me. Only three I used, without a hitch.
I used goomanager to install TWRP and it worked just fine.
theking_13 said:
Use TWRP, but don't be lazy and do it from the app, it didn't work for me, and just doesn't feel as reliable as my trusty adb commands. If you need help on what commands, PM me. Only three I used, without a hitch.
Click to expand...
Click to collapse
Flashing a recovery from fastboot is not being lazy. There's actually more work involved than installing from an app. I think you have it the other way around.
SkizzMcNizz said:
Flashing a recovery from fastboot is not being lazy. There's actually more work involved than installing from an app. I think you have it the other way around.
Click to expand...
Click to collapse
Uhmmm, wanna reread what I said, I clearly said NOT to do it from the app. Here's the first sentence in case you somehow missed it.
"Use TWRP, but DON'T be lazy and do it from the APP, it didn't work for me, and just doesn't feel as RELIABLE as my trusty ADB COMMANDS."
Any more questions/inquiries?
Sent from my HTC One X using Tapatalk 2
gunnyman said:
Use twrp instead. Clockwork isn't officially supported on our phone. Twrp is.
Click to expand...
Click to collapse
Are both recoveries able to install the same roms? or are some roms only able to be installed through CWM or TWRP?
i'm assuming they both install the same way, so all roms should work regardless. It's just that rom threads say "install using clockwork", but i guess that's just a common phrase now..
SkizzMcNizz said:
I've noticed that when you first do the fastboot flash recovery that when you adb reboot into recovery, or even manually boot into recovery, it won't boot into it the first time. It will after you try again though. This has happened on 3 One X's so I know it's not a single phone specific thing.
Click to expand...
Click to collapse
that used to happen on my HTC Desire too...
zoltrix said:
Are both recoveries able to install the same roms? or are some roms only able to be installed through CWM or TWRP?
i'm assuming they both install the same way, so all roms should work regardless. It's just that rom threads say "install using clockwork", but i guess that's just a common phrase now..
that used to happen on my HTC Desire too...
Click to expand...
Click to collapse
yeah install using clockwork is common language for use recovery, since cwm is the more well known one.
Just as an opinion, TWRP looks better to me, because its not all just clicks and such, TWRP you slide to confirm, you can flash multiple .zips one after the other (Useful for AOSP roms where you need GAPPS, and if you change the kernel like I do) etc.
Also, as stated before, its an official recovery on our devices, so we get full support should bugs arise.
Sent from my HTC One X using Tapatalk 2
theking_13 said:
Uhmmm, wanna reread what I said, I clearly said NOT to do it from the app. Here's the first sentence in case you somehow missed it.
"Use TWRP, but DON'T be lazy and do it from the APP, it didn't work for me, and just doesn't feel as RELIABLE as my trusty ADB COMMANDS."
Any more questions/inquiries?
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Sorry. I took it as you saying not to be lazy and to do it from the app instead. Like, Don't be lazy. Do it from the app. See what I'm saying?
Sent from my HTC One X using XDA
OneDeagz said:
i had 5.8.2.7 and i flashed to 5.8.4.0 and now when i try to boot into recovery it just sits at the HTC screen for a while and then reboots
Click to expand...
Click to collapse
Did you turn off "Fast Boot" in "Power settings" before you tried to reboot into recovery?
That Recovery is for the International HOX (tegra 3) not for out AT&T HOX (S4).
Does anyone have a link to up to date instructions on flashing twrp to my phone. i have the ATT version not the international
SkizzMcNizz said:
Sorry. I took it as you saying not to be lazy and to do it from the app instead. Like, Don't be lazy. Do it from the app. See what I'm saying?
Sent from my HTC One X using XDA
Click to expand...
Click to collapse
Oh no worries bro, sounds different in my head but I see what you're saying.
Hi all,
Got mine today, tried to install a ROM and it got stuck in bootloop.
I did a number of stupid things not to mention wiping the SD and im in serious trouble.
I can get into bootloader and CWM but thats it.
Ive heard restoring a RUU can cure it but I have a MAC and cant find anything to help.
Can anyone help? Im gutted....and fell like an idiot.
Ive got an S4 on the three network.
Thanks
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Hi,
It enters into bootloader but then what?
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
blackcell1 said:
Follow the guide here from how to flash custom rom
http://forum.xda-developers.com/showthread.php?p=24478083
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Its sent and wrote the recovery file but what now?
mikejasonsmith said:
Its sent and wrote the recovery file but what now?
Click to expand...
Click to collapse
Specifically you'll have to flash the ROM zip file from the recovery and then use fastboot flash boot boot.img.
You can find boot.img inside the ROM zip file
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
mikejasonsmith said:
Tried flashing ROM zip but no joy...when should i flash boot img? before or after recovery?
Click to expand...
Click to collapse
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
mikejasonsmith said:
ok managed to get the sd mounted...phew...but how do i get a rom on when it wont boot?
Click to expand...
Click to collapse
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
mikejasonsmith said:
Ive used TRW to get the sd mounted but it wont boot beyond that. i restored the stock recovery but what do i do next?
At the moment i have a phone which has CWM working but nothing else?
Thanks for your help
Click to expand...
Click to collapse
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
mikejasonsmith said:
ok so ive tried flashing ruu and keep getting error 155 which is a cid issue i believe - which RUU do i use for a device locked to '3'?
Thanks
oh and can you point me in the direction of it...thanks
Click to expand...
Click to collapse
so ive managed to get the h3g rom and flashed rom and boot.img.
locked bootloader and run RUU but i keep getting error 155???
Somebody please help me before this thing goes out of the window.....:crying:
Search adb push
Sent from my HTC One S using Tapatalk 2
danevianta said:
Search adb push
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Finally seem to have done it and managed to RUU
The phone is locked to 3 but as a noob I spent 2 days flashing a generic euro ROM.
When i realised i need a ROM to match CID i downloaded 1.53. Tried this a number of times with no joy.
Just tried 1.78 and it seems to be working
Thanks to everyone for your help - us noobs must be sooooooo annoying.
Htc One S bricked
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
FaLLeN_BtB said:
Hi im relatively new at rooting and am currently experiencing issues with a bricked device.
i have two htc one s devices
my personal one is running cm10 ville with clockwork touch recovery and is working perfectly
however the second one i was using the same exact files.
this one is bricked
its in a constant bootloop.
i can get back to my recovery just fine and get to the fastboot in the phone fine
i cleared my cache
wiped my data and wiped the dalvik cache all perfectly fine when i try to flash the cm10 official rom back on it cannot mount the sd card
i would try to install a different recovery and try again maybe using viper one s
but i cannot get the phone to power on
it doesnt showup on the computer when it is plugged in while in fastboot
when i try the cmd fastboot flash recovery it says waiting for device
any advice. this is not my own phone so i need it repaired pretty quickly.
any helpful information would be much appreciated.
Click to expand...
Click to collapse
Bootloop does not mean your bricked...means you need to fastboot flash boot.img
Sent from my HTC One S using xda premium
blackcell1 said:
Hold down the power button for 10 seconds then after the touch buttons stop flashing, just hold the volume button and see if ot enters the bootloader.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
This little post just pulled me out of missery. Love ya man!
all you guys getting sorted
make a nandroid and sdcard bu NOW and put them on pc,
obviously leave a copy of nandroid on phone also
makes it a lot easier if you get in trouble again
and you/we will
Mounts and Storage --> Format everything --> Now Mount USB Drive --> Put Gapps and ROM
Flash it, erase cache & and Dalvik...Blah blah blah. Flash boot.img in fastboot, and there you go.
Everybody, please remember this and there won't be noob q&a anymore...
TWRP v 2.2.2.1 I can't flash Jelly Bean 4.2.2 .zip on HTC one s (s3)
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
mikebryant2807 said:
HI, my device is an HTC ONE S (s3)... I've already unlocked the bootloader and rooted it... it's ok... For recovery mode I installed TWRP v 2.2.2.1.... I've wiped the cache and made a factory reset... BUT when I try to flash the zip which contains the jelly bean 4.2.2 I get a message saying: FAILED when i was trying to install it... PLEASE I NEED YOUR HELP CUZ I THINK I CAN'T DO TOO MUCH WITHOUT AN OS ON MY DEVICE... I'M NOW JUST IN TWRP... HELP PLEASE........
Click to expand...
Click to collapse
See other reply.