VOTE! Which custom recovery are you guys using on your Rezound?
188 Views, 6 Votes, including mine.
I like to rearrange data and free up space a lot of the time I'm in recovery mode as well. TWRP's UI serves that purpose best. It is also has better support from apps like TiBu than Amon Ra does.
javaguy216 said:
VOTE! Which custom recovery are you guys using on your Rezound?
Click to expand...
Click to collapse
Amon Ra 3.16, better nandroids, can wipe boot.
My name's Harold and I'm a flashaholic.....
hgoldner said:
Amon Ra 3.16, better nandroids, can wipe boot.
My name's Harold and I'm a flashaholic.....
Click to expand...
Click to collapse
wipe boot breaks some kernel installs.... Just sayin
I use CWM
Flyhalf205 said:
wipe boot breaks some kernel installs.... Just sayin
I use CWM
Click to expand...
Click to collapse
I tried all 3. I really like the touch option. The only option I couldn't find in CWM is a way to boot back to bootloader, like the other 2 recoveries offer.
Sent from my Rezound using Tapatalk 2
Flyhalf205 said:
wipe boot breaks some kernel installs.... Just sayin
I use CWM
Click to expand...
Click to collapse
I wonder if this is what happened to me lately. Got a replacement device last week, wiped boot and been having all kinds of problems. Sending back for another replacement tomorrow. Phone has been running hot and not charging correctly and battery has been discharging fast.
Sent from my ADR6425LVW using xda app-developers app
ryryrocco said:
I wonder if this is what happened to me lately. Got a replacement device last week, wiped boot and been having all kinds of problems. Sending back for another replacement tomorrow. Phone has been running hot and not charging correctly and battery has been discharging fast.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Some kernels won't install at all unless there is an existing kernel. We extract the ramdisk from the existing kernel rather than bundling our own, so if the kernel is not there, that part will fail and the system won't boot. Doing it that way ensures the widest possible compatibility with different ROMs and makes sure that we don't overwrite any ramdisk customizations the ROM dev made.
Sent from my SCH-I605 using Tapatalk 2
Related
Is it an app I can download that will put me in recovery. I love flashing ,just getting aggravating to keep taking back off and pulling battery.
Sent from my ADR6425LVW using Tapatalk
Sent from my ADR6425LVW using Tapatalk
Just dissable fastboot and you won't need to pull the battery
Sent from my ADR6425LVW using XDA App
Download "Quick Boot" from the market, that's what I use.
It will let you boot into
Recovery or Bootloader
Sent from my ADR6425LVW using Tapatalk
There are a couple apps that will take you into recovery. I'm assuming you are rooted so you could use the app called Quick Boot (its in the market ). Its pretty simple and gives you the options to power down, fast boot, boot into recovery etc.
Sent from my ADR6425LVW using XDA App
app called reboot manager works great. just hit recovery and it will take you strate into recovery with nothing else to do.
if you install this app, it will install a quick setting by long pressing the serch button or you can put a widget on your screen with every power/reboot option
gadget! said:
Download "Quick Boot" from the market, that's what I use.
It will let you boot into
Recovery or Bootloader
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
I am so glad someone created this and found this. It has made my flashing abilities so much easier!!
+1 for Quick Boot. Was the first app I loaded after rooting.
krelvinaz said:
+1 for Quick Boot. Was the first app I loaded after rooting.
Click to expand...
Click to collapse
has no one had any issues with quick boot? the first time i used it, i used it to boot into recovery (amon ra) and wipe cache/dalvik and then flashed a kernal. well, it didn't work, and i ended up having to nandroid restore. couldve been the kernal, though i have used the same kernal/rom combo countless times with no issues. that being said, i really think quick boot did something to corrupt some data. any ideas or experience with this? (evo 4g running mikg v3/anthrax kernal)
atljatl said:
has no one had any issues with quick boot? the first time i used it, i used it to boot into recovery (amon ra) and wipe cache/dalvik and then flashed a kernal. well, it didn't work, and i ended up having to nandroid restore. couldve been the kernal, though i have used the same kernal/rom combo countless times with no issues. that being said, i really think quick boot did something to corrupt some data. any ideas or experience with this? (evo 4g running mikg v3/anthrax kernal)
Click to expand...
Click to collapse
how would the reboot app have any effect on the kernel?
atljatl said:
has no one had any issues with quick boot? the first time i used it, i used it to boot into recovery (amon ra) and wipe cache/dalvik and then flashed a kernal. well, it didn't work, and i ended up having to nandroid restore. couldve been the kernal, though i have used the same kernal/rom combo countless times with no issues. that being said, i really think quick boot did something to corrupt some data. any ideas or experience with this? (evo 4g running mikg v3/anthrax kernal)
Click to expand...
Click to collapse
The app just does the equivalent of you doing an "adb reboot recovery" or choosing recovery from hboot, or anything else.
Once you're booted up running on your recovery partition, the quick settings apk file on your phone /data directory on it's phone partition aren't responsible for anything that happens.
I can assure you the issue was elsewhere!
pkopalek said:
I can assure you the issue was elsewhere!
Click to expand...
Click to collapse
Thanks. That's very reassuring.
Sent from my PC36100 using Tapatalk
I am S-ON, unlocked, and rooted. I made a backup in TWRP, and flashed the latest lenoob's CM9, then flashed gapps. Upon reboot, it hangs at the white HTC screen. So i read a little and see that i need to extract the boot.img from lenoob's image, and zip it on its own as PH98IMG.zip and place it on the root of the sd card. Great, so i did that, booted into HBOOT, it saw the PH98IMG.zip, said parsing, then never gave me an option to push UP to flash or reboot. Just puts me at the HBOOT menu.
Am i missing a step here?
Aha- i bet its because I'm still unlocked. fffffff i'm at work and can't relock :-/
I could be wrong because I'm still new, but being unlocked shouldn't have anything to do with it, I think you need to be unlocked to flash Roms. I don't have experience with TWRP but if your s-on you could also use fast boot to flash the boot.Img after flashing the rom itself
Sent from my Adrenalized Rezound
Extract the boot.img place it where you have adb on you computer then flash Rom gapps boot back to bootloader and use command fastboot flash boot boot.img, you have to be unlocked to flash roms if s-on.
Sent from my ADR6425LVW using xda app-developers app
Dogbone737 said:
I could be wrong because I'm still new, but being unlocked shouldn't have anything to do with it, I think you need to be unlocked to flash Roms. I don't have experience with TWRP but if your s-on you could also use fast boot to flash the boot.Img after flashing the rom itself
Sent from my Adrenalized Rezound
Click to expand...
Click to collapse
I could have sworn i read somewhere that i can flash stuff in TWRP, but not the boot image. Thought the boot image had to be flashed in HBOOT and for HBOOT to actually flash the image, the phone needs to be locked or relocked. I'm new too so i could have lots of bad information :fingers-crossed:
Also don't forget to wipe first.
Sent from my ADR6425LVW using xda app-developers app
molson8045 said:
Extract the boot.img place it where you have adb on you computer then flash Rom gapps boot back to bootloader and use command fastboot flash boot boot.img, you have to be unlocked to flash roms if s-on.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Gotcha. I will give this a go when i get home tonight. Thanks!
Aaaaaand success. LOVING CM9. This is what i want out of a phone. And google now is pretty slick too.
sshaar said:
Aaaaaand success. LOVING CM9. This is what i want out of a phone. And google now is pretty slick too.
Click to expand...
Click to collapse
And we just released a new build.
GrayTheWolf said:
And we just released a new build.
Click to expand...
Click to collapse
And so far, this build is impeccable, the only things I'm seeing problems with is some atypical choppiness.. which is to be expected. However, it's the battery life that I'm interested in, today will be the test for me. Lets see how it does.
xFonzie said:
And so far, this build is impeccable, the only things I'm seeing problems with is some atypical choppiness.. which is to be expected. However, it's the battery life that I'm interested in, today will be the test for me. Lets see how it does.
Click to expand...
Click to collapse
Read through the OP of the cm9 thread and you will see it says "enable GPU rendering in developer options to remove keyboard lag". This should help with overall lag.
you tizante
GrayTheWolf said:
Read through the OP of the cm9 thread and you will see it says "enable GPU rendering in developer options to remove keyboard lag". This should help with overall lag.
Click to expand...
Click to collapse
Oh, it's not keyboard lag, it's just some choppiness in some spots, not too big a deal. I am well aware of the enable GPU rendering deal.. all together, pretty darn good so far, I'm quite happy with the CM9 builds as it is.
GrayTheWolf said:
And we just released a new build.
Click to expand...
Click to collapse
GAH! After I got it all set up last night haha
So far I love everything on the 9/10 build, but i remember something closing or locking up. Obviously not a big deal since i can't even remember what it was now haha.
Wow... were at about 4 hours now.. and my battery is at 91% .. so far color me impressed..
Sent from my ADR6425LVW using xda app-developers app
I used my phone for about 2 hours this morning with some web browsing and playing around with google now, and text messaging, and i was down to 79%. So thats good enough for me on a stock battery.
sshaar said:
I am S-ON, unlocked, and rooted. I made a backup in TWRP, and flashed the latest lenoob's CM9, then flashed gapps. Upon reboot, it hangs at the white HTC screen. So i read a little and see that i need to extract the boot.img from lenoob's image, and zip it on its own as PH98IMG.zip and place it on the root of the sd card. Great, so i did that, booted into HBOOT, it saw the PH98IMG.zip, said parsing, then never gave me an option to push UP to flash or reboot. Just puts me at the HBOOT menu.
Am i missing a step here?
Click to expand...
Click to collapse
I have a question. phone is S-ON, unlocked, and rooted. I have never flashed a rom before. I am extreme newb at that.
I can understand the flashing of the PH98IMG.zip.
If you could help me understand what gapps is? Is this just some google apps? And if so when you say you flashed gapps, do you flash it in the same way you would the boot image?
Thanks in advance for help.
Gapps are simply Google apps.. play store... Gmail.. YouTube.. and so forth.
Sent from my ADR6425LVW using xda app-developers app
xFonzie said:
Gapps are simply Google apps.. play store... Gmail.. YouTube.. and so forth.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Do you flash them like you would the boot.img?
As in fastboot flash gapps?
Also do I need to worry about the kernel?
Sax1031 said:
Do you flash them like you would the boot.img?
As in fastboot flash gapps?
Also do I need to worry about the kernel?
Click to expand...
Click to collapse
Nope flash them as you would the rom
Sent from my ADR6425LVW using xda premium
Self explanatory.. this is daily use for me..
Sent from my ADR6425LVW using xda app-developers app
Whenever my phone dies, it boots to recovery or better known, cwm when I plug it in. Not sure why, I don't mind it. But I'm wondering why, I have the latest touch recovery from cwm. And I do want to switch to 4ext but I have a question.
1. Can it flash any rom that cwm can flash?
Thanks guys.
Sent from my ADR6400L using xda app-developers app
Gad74 said:
Whenever my phone dies, it boots to recovery or better known, cwm when I plug it in. Not sure why, I don't mind it. But I'm wondering why, I have the latest touch recovery from cwm. And I do want to switch to 4ext but I have a question.
1. Can it flash any rom that cwm can flash?
Thanks guys.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
4ext can flash every rom that CWM can and then some.
The reason your phone turns on like that is because you are using CWM Recovery.
But I've used it before. It didn't used to do this until I flashed touch or because ics. I updated and rooted so not sure.
Is 4ext really worth it?
Is it really worth putting the effort into it?
I need to flash a radio and it says 4ext recommended.
Sent from my ADR6400L using xda app-developers app
Gad74 said:
But I've used it before. It didn't used to do this until I flashed touch or because ics. I updated and rooted so not sure.
Is 4ext really worth it?
Is it really worth putting the effort into it?
I need to flash a radio and it says 4ext recommended.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
It doesn't require much effort and is well worth it yes.
CWM is garbage and it is a bug in the Touch version that does it.
Has nothing to do with rooting the phone.
You never had CWM before you rooted and non touch versions didn't have the bug.
It's actually about as painless as can be to switch to 4ext and is miles better in every way.
Yes you need to flash new radios for the ICS roms.
Read the Op in my thread like I said in the PM and you will find it is all very simple to do and well worth the short time it takes to do. Or not.
Your call, but you have been told many times to ditch CWM and I pretty much require it or TWRP for my roms which are currently the only recent ones you will even find for the Bolt.
Install the free app I linked you before and flash the recovery, takes maybe 3 minutes.
Thank you. Your the only one who told me if it was better. I'm switching now. And true, don't think any Better roms are going to come out.
Sent from my ADR6400L using xda app-developers app
Going to re-root again and probably ROM again, debating between TWRP and Amon Ra, is one any better than the other?
Probably going to ROM with Infection or XenonHD, is either one preferred with those ROMs?
Twrp is more updated and in newer ROMs there may be an update system included and to have the update automatically install for you when you click update, the recovery needs to support something called "open script" I believe that's what its called. And amon ra doesn't support that but twrp and cwm do, I actually switched from amon ra to twrp and I like it way better and the open script comes in handy when you don't want to manually install zips or updates.
Sent from my ADR6425LVW using xda app-developers app
Awesome, sounds like a good enough reason for me to give TWRP a shot. Thanks.
I was using TWRP for a while with no issue and liked it. Then for some reason it started having an issue with not restoring new backups. Didn't try to reinstall but moved to CWM Touch. I like it but backups are not compatible between the two and TWRP does have more features.
Sent from my Infected Rezound using xda premium
Quick question, can twrp be flashed over amon ra? And to Ace, if you look in the Infection thread I believe Neo recommends flashing with amon ra.
tholmes8291 said:
I was using TWRP for a while with no issue and liked it. Then for some reason it started having an issue with not restoring new backups. Didn't try to reinstall but moved to CWM Touch. I like it but backups are not compatible between the two and TWRP does have more features.
Sent from my Infected Rezound using xda premium
Click to expand...
Click to collapse
Doesn't CWM Touch have the dead battery bug where it won't let the battery charge if it goes completely dead? Or has that been fixed, it would be real deal breaker for me...
JBS976 said:
Quick question, can twrp be flashed over amon ra? And to Ace, if you look in the Infection thread I believe Neo recommends flashing with amon ra.
Click to expand...
Click to collapse
Yes. I prefer twrp but occasionally run into a rom/kernel that won't flash. I keep amon ra to flash on those occasions then reinstall twrp with the goomanager app
acejavelin said:
Doesn't CWM Touch have the dead battery bug where it won't let the battery charge if it goes completely dead? Or has that been fixed, it would be real deal breaker for me...
Click to expand...
Click to collapse
That was fixed a while back.
Sent from my Infected Rezound using xda premium
I've never had problems with twrp on backups or installs. I've only used and been on the latest 2.5.0.0 version though
So idk if you we're on a older version or something
And you should be able to flash a recovery on top of another it just replaces the recovery.img and ROM performance shouldn't be effected by the recovery. That doesn't really make sense so use the one you want
Sent from my ADR6425LVW using xda app-developers app
Ever since the new partition layout i cant run any kit kat roms. I did throwbacks process and i am s-off so i have had 4.17 on this phone. also running the latest recovery from throwbacks post .8b. I dont know what it is or what im doing wrong but after flashing a 4.4 rom it will stay on the boot screen and the charge light comes on if its plugged it but will not boot. All of the sense 5.5 roms flash and boot up. Any ideas?
First of all make sure you're flashing ROMs compatible with the new partition layout.
Sent from my Nexus 5 using Tapatalk
numel007 said:
First of all make sure you're flashing ROMs compatible with the new partition layout.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried flashing slimkat and CM11 both are compatible with the new layout.
theshrimp said:
I have tried flashing slimkat and CM11 both are compatible with the new layout.
Click to expand...
Click to collapse
The commit for the new partitions are not merged into cm repo. If you're flashing stock builds, there is no way it'll work. Are you using SlimKat posted in Android Developemt?
Sent from my Nexus 5 using Tapatalk
numel007 said:
The commit for the new partitions are not merged into cm repo. If you're flashing stock builds, there is no way it'll work. Are you using SlimKat posted in Android Developemt?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I tried a CM11 that somebody had updated, and yes the one by tots
theshrimp said:
I tried a CM11 that somebody had updated, and yes the one by tots
Click to expand...
Click to collapse
Can't think of anything off the top of my head. I'll reply if I come up with anything. My knowledge of updates on this device has dwindled since I got my n5. Sorry 'bout that.
Sent from my Nexus 5 using Tapatalk
numel007 said:
Can't think of anything off the top of my head. I'll reply if I come up with anything. My knowledge of updates on this device has dwindled since I got my n5. Sorry 'bout that.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the quick reply. I hope i can figure this out! i have been flashing roms since my samsung moment so i dont think its something im doing unless the process changed with the new layout.
theshrimp said:
Thanks for the quick reply. I hope i can figure this out! i have been flashing roms since my samsung moment so i dont think its something im doing unless the process changed with the new layout.
Click to expand...
Click to collapse
Are you using any wipe scripts like superwipe?
Sent from my Nexus 5 using Tapatalk
Check the thread in the link below if you haven't already done so.
http://forum.xda-developers.com/showthread.php?t=2654590
Sent from my HTC device
FinZ28 said:
Check the thread in the link below if you haven't already done so.
http://forum.xda-developers.com/showthread.php?t=2654590
Sent from my HTC device
Click to expand...
Click to collapse
That was the thread i got the CM11 build from.
numel007 said:
Are you using any wipe scripts like superwipe?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I usually wipe cache, dalvik, internal, and system. Then i reboot to bootloader and flash the boot img from the rom, reboot back to recovery and flash the rom with gapps.
theshrimp said:
That was the thread i got the CM11 build from.
I usually wipe cache, dalvik, internal, and system. Then i reboot to bootloader and flash the boot img from the rom, reboot back to recovery and flash the rom with gapps.
Click to expand...
Click to collapse
Maybe I'm out of recent times, but I've personally never flashed boot.IMG separately. I just wipe, flash ROM, flash kernel, wipe caches, reboot. Is this a new thing that updated partitions needs?
Sent from my Nexus 5 using Tapatalk
numel007 said:
Maybe I'm out of recent times, but I've personally never flashed boot.IMG separately. I just wipe, flash ROM, flash kernel, wipe caches, reboot. Is this a new thing that updated partitions needs?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
No change on the new setup. If you're S-on you have to flash the boot.img separately. For S-off, you don't.
Sent from my HTC device
FinZ28 said:
No change on the new setup. If you're S-on you have to flash the boot.img separately. For S-off, you don't.
Sent from my HTC device
Click to expand...
Click to collapse
He is s-off, so technically he shouldn't need to do that. Shouldn't make a difference though.
Sent from my Nexus 5 using Tapatalk
If i remember right people who were S-ON still had to do it that way and i only recently gained S-OFF so i still do it that way. im not sure if there is a different way for S-OFF people?
theshrimp said:
If i remember right people who were S-ON still had to do it that way and i only recently gained S-OFF so i still do it that way. im not sure if there is a different way for S-OFF people?
Click to expand...
Click to collapse
You said in your original post that you're S-off, so you just need to flash the ROM zip. No need to boot to the bootloader and flash the boot.img separately.
Sent from my HTC device
FinZ28 said:
You said in your original post that you're S-off, so you just need to flash the ROM zip. No need to boot to the bootloader and flash the boot.img separately.
Sent from my HTC device
Click to expand...
Click to collapse
So just went and wiped everything and re flashed without going into the bootloader, and still no go. Its stuck on boot screen and the charge light still comes on so its not boot looping right?
theshrimp said:
So just went and wiped everything and re flashed without going into the bootloader, and still no go. Its stuck on boot screen and the charge light still comes on so its not boot looping right?
Click to expand...
Click to collapse
How long are you waiting for it to boot up? Remember it takes several minutes for a ROM to boot after a flash, so give it a bit and see what happens.
Sent from my HTC device
FinZ28 said:
How long are you waiting for it to boot up? Remember it takes several minutes for a ROM to boot after a flash, so give it a bit and see what happens.
Sent from my HTC device
Click to expand...
Click to collapse
Before i re wiped it i let it sit for 30+ minutes. Its been going for about 5 or so minutes.
Maybe ill just have to stick with boring old sense 5 haha. i seriously have no idea why its doing this.
Did you unlock bootloader with htc utility? What did you use to gain s-off?
What version is your H-BOOT?
Some roms I was flashing checked for 2.10.0000 and rejected anything else, so when I upgraded to 2.10.5555, most of the kit kat rooms took a poop on me.
Not sure if this is still an issue though. I would imagine those errors were caused by the person compiling the Roms, but may have been resolved since.