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.
Related
i have a rezound that i have unlock and rooted..
i have been trying to flash roms on the phone but it gets stuck at the white htc screen.. i have been reading some of the threads and im not sure if i understand if im doing something wrong.. when i try to flash a rom i get into recovery the clear factory reset,clear cache,clear dalvtik.... install the the rom from the external sd card. once its done i get into fastboot and install the PH89IMG.ZIP. onces thats done i reboot and thats when i get stuck... im very new to this... i have tried to install clockworkmod on the phone .. the only why that i get into recovery is using the rezound tool kit 2.0. i dont think that,that has anything to do with it but i could be wrong... somebody please help me....
bakerboy81 said:
i have a rezound that i have unlock and rooted..
i have been trying to flash roms on the phone but it gets stuck at the white htc screen.. i have been reading some of the threads and im not sure if i understand if im doing something wrong.. when i try to flash a rom i get into recovery the clear factory reset,clear cache,clear dalvtik.... install the the rom from the external sd card. once its done i get into fastboot and install the PH89IMG.ZIP. onces thats done i reboot and thats when i get stuck... im very new to this... i have tried to install clockworkmod on the phone .. the only why that i get into recovery is using the rezound tool kit 2.0. i dont think that,that has anything to do with it but i could be wrong... somebody please help me....
Click to expand...
Click to collapse
don't use clockwork, use the amon recovery.
Use among ra recovery. Other that, how long have you let it sit at that screen? Sometimes it takes several minutes, just be patient.
Also, what rom, and are you on the new leaked firmware?
I could remote into team viewer on your computer and flash amon ra recovery on your phone and walk you through installing a Rom and kernel for you if you want.
But to properly wipe, it should be data, cache, dalvic cache, and system
Sent from my ADR6425LVW using xda premium
http://forum.xda-developers.com/showthread.php?t=1425091
that thread helped me alot, do lots of reading before you flash anything. also make sure you have the correct kernel for the rom your using.
i have tried using amon recovery and i get the same result.... i have let it sit for about 10 mins and nothing happens... im trying to flash scottsrom ics.. the latest one....
bakerboy81 said:
i have tried using amon recovery and i get the same result.... i have let it sit for about 10 mins and nothing happens... im trying to flash scottsrom ics.. the latest one....
Click to expand...
Click to collapse
Have you ran the leaked ruu and have the new firmware?
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
ijustwantmydock said:
Have you ran the leaked ruu and have the new firmware?
Sent from my ADR6425LVW using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
he doesn't need to be on the leaked ruu to use the ics roms. he can flash the old firmware patch too.
I have tried to find the leak ruu but I don't know where to find it and how to install it. I was reading about it earlier but I'm still a little iffy on how to do it ..
Sent from my ADR6425LVW using XDA
bakerboy81 said:
I have tried to find the leak ruu but I don't know where to find it and how to install it. I was reading about it earlier but I'm still a little iffy on how to do it ..
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
just be aware if you use it, your hboot will say "tampered" and you cannot roll back to GB firmware. if your new to this, id do alot of reading before attempting it. if you want a good GB based rom look into chingy's rom.
http://forum.xda-developers.com/showthread.php?t=1420513
mighty_markus12 said:
he doesn't need to be on the leaked ruu to use the ics roms. he can flash the old firmware patch too.
Click to expand...
Click to collapse
He can so that but its not supported by Scott so if he has any problems he wont get help.
Just because you are against flashing the leaked firmware doesn't make it bad.
To the OP, if you are uncomfortable with relocking your phone to flash the new firmware I would try one of the gb roms. The update for ICS should be anyday now.
Sent from my Rezound using Tapatalk
nrfitchett4 said:
He can so that but its not supported by Scott so if he has any problems he wont get help.
Just because you are against flashing the leaked firmware doesn't make it bad.
To the OP, if you are uncomfortable with relocking your phone to flash the new firmware I would try one of the gb roms. The update for ICS should be anyday now.
Sent from my Rezound using Tapatalk
Click to expand...
Click to collapse
he can also use rezrom which supports the old firmware with a patch. and we have no clue when the ota will be out. i never told him not to flash the ruu but if he doesn't know what he is doing i recommend he reads up alot. stop trying to contradict everything i say in every thread, it's getting annoying.
OP i sent you a pm.
are u sure that your kernel is being flashed in Fastboot? because thats what usually causes freeze ups
yojoe600 said:
are u sure that your kernel is being flashed in Fastboot? because thats what usually causes freeze ups
Click to expand...
Click to collapse
+1 to this
Need to get my ten post over with so I don't need to do image verifications
I flashed midnight ROM. put the AOSP theme over it. Flashed the newest MAC Kernel, and that's when it started happening.
I decided to factory reset and flash the ROM again, tried to restart. same thing.
restored a backup (after factory restting), no dice.
Wiped boot/data/system, factory resetted, wiped both caches and reflashed midnight ROM. Still nothing.
Tried to flash CM9 (after factory resetting and stuff) and it still won't go past the HTC screen no matter how long I wait.
What's wrong? Am I half bricked?
I'm using the Evo V with S OFF on downgraded HBOOT.
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
You need to downgrade your radios as well to flash aosp roms. Run an older RUU, which will set you back to stock, flash your recovery and then flash midnight again
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
RedDeadDorito said:
I've flashed all these ROMs with no problems before. I already have my radios upgraded (I basically turned my phone into a Evo 3D).
Click to expand...
Click to collapse
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
beneath-a-burning-turtle said:
Gotta go in the opposite direction with radios, downgrade. It'll make older roms compatible again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
So basically, upgrade my HBOOT (since stock is on a upgraded one) again and flash a stock ROM then downgrade again?
I was thinking of doing this, but why did this problem come up in the first place?
I can't do it because I don't have an extra SD card around. If I put the hboot upgrade on my SD card, the bootloader won't start up because it gives you the option to install it or not install and either way, it turns the phone off.
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
RedDeadDorito said:
Got it figured out. When I flashed a different kernel, it broke the other kernel or something. I had to flash the ROM's kernel separately. I don't know why.
I'm not sure why, but it did. Anyways, it seems to be working now!
Click to expand...
Click to collapse
Glad that you got a solution and that you were also detailed in your response. Perhaps someone in the future that sets aside the time to research and read will be able to either get themselves out of a mess - or - possible avoid one. Cheers!
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
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
twrp recovery..
kenohki88 said:
the other day i tried restoring a back up via TWRP but it didnt work until i fastboot flashed boot.img...Alright so i updated my TWRP via goomanager app to the latest version (whatever is on there via goomanager) as in the TWRP forum discussions it was stated that previous versions were not working properly wihen restoring. So today i flashed a new ROM (NOS ROM) but that didnt work so i decided what better time than now to try restoring again, no dice didnt work and i had to fastboot flash the boot img for the restore file to take and boot up just fine again...ok peeps what am doing wrong??? again im fairly new at this flashing ROMS scene but i thought witht he TWRP update i would be good to go. Am i missing some settings ticks/options/checks? i saw a check box that said "recovery" i think in the restore or back up process dont remember which process. i tried going onto the TWRP discussion but it is locked down and states that there will no longer be any support for it...should i just switch to CWM?? thanks in advance to whom ever replies
Click to expand...
Click to collapse
What did you have checked while making the backup? data? recovery? cache? system? and did you rename the back up?
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
System, data and boot are checked...I didn't mess with the options just hit restore and let it do it's thing...should I change something or check the other 2 boxes (one of them being "recovery" forgot what the other option was)?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
---------- Post added at 12:42 PM ---------- Previous post was at 12:34 PM ----------
canemaxx said:
I would check recovery as well and try again.....also make sure to wipe everything before flashing anything
Click to expand...
Click to collapse
also some roms are picky about which recovery is used to install/backup. I can say I have had no issues backing up stock or custom roms with twrp on my DNA
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Alright sounds good maybe later on tonight when I'm at my computer just in case thank you for the tips I as well haven't had much trouble flashing ROMS with TWRP, albeit I've only tried flashing 2 or 3 been very happy with ViperDNA just wanted to check out different ones and easily restore back to viper
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Check out NOS its a great rom
canemaxx said:
Check out NOS its a great rom
Click to expand...
Click to collapse
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
That's exactly what I was trying when all this happened...I flashed it via flash gui app like I've been doing but for some reason it didn't work...when I went to unlock screen it would pull up HTC splash screen and just stay stuck there... I'm not S-off yet so would that have something to do with NOS ROM not functioning?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
no thats how that rom boots....leave it alone for about 5-10 minutes youlll see the notificatiion light come on and your =e good to go
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Let me rephrase that...it boots up, screen comes on silver background from butterfly then I go pull ring to unlock and it pulls up the HTC splash screen once I unlock and will not move from there...so that's when I reset and went back to viper...???
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
kenohki88 said:
Haven't tried it since I posted this, but ok I'll give it another spin/attempt this weekend thanks for the tip
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I may have misread but did you wipe everything before loading nos? I saw what was checked for backup but not about wiping. You should wipe everything-system, then cache, then delvik cache-not exactly in that order (make SURE there IS a backup just in case). Load the rom AND flash the correct image file with adb. Also, many roms when FIRST loading up sit a long time before they start up, not sure if nos does this or not-I have been jumpy about the time sitting with a few roms when waiting was all I needed to do. I have had different Viper versions on a few times and moving to another rom was quirky each time I did so, not sure why.
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
NOS did that to me too. Just wait....it will load into the setup wizard. I think being s-on, which I still am...twrp isn't able to back up and restore your roms boot.img. just a guess but I to failed to restore a backup when an install went awry. Makes sense to be being that you can't install a kernel from recovery either.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
rootntootn said:
I looked at the install instructions for nos, if you are s-on you need to do one extra step. You have to extract the rom into a folder somewhere to get the image file, copy the image file from it. Flash that image file using adb on your pc and THEN install the rom from your phone with goomanager. Without the image file loaded, I don't think it would work. If you are s-off this step is not needed.
Click to expand...
Click to collapse
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Ajj915 said:
I get that. I'm purely talking about after a full while that I'm not sure if twrp will restore the boot.img from a nandroid. S-On of course.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
Click to expand...
Click to collapse
Oh yeah, and I restored my back up and that works just fine
rootntootn said:
I believe it will, if it had the image from the get go. I believe that the back up has everything it needs. At least my back ups have never needed an image file. I decided I should try NOS myself and must say it would not go for me (S-off) it kept rebooting into recovery. I was going to try and also flash the boot image but have not done so yet.
---------- Post added at 10:10 AM ---------- Previous post was at 10:08 AM ----------
Oh yeah, and I restored my back up and that works just fine
Click to expand...
Click to collapse
Its the kernel in NOS. Flash NOS and then flash cpalmers kernel. Then reboot and do the setup and if you want to change to the zarboz kernel you need to delete system/bin/thermald or rename it to thermald_old.bak
Sent from my HTC6435LVW using Xparent Red Tapatalk 2
Hmmm well I did everything via my cell (been the way I've been flashing ROMS unless something goes wrong then I use ADB on computer) and everything when properly done works fine using Flash GUI APP love that app! I've flashed super charged hatka 320 (used that for a couple weeks) then switched over to viper...both using Flash GUI I tried using NOS but yes no dice loaded up but when I pull the unlock ring for whatever reason the splash screen comes up and it won't budge from there....and as for my original question haha TWRP did not work for me when restoring it tripped out like if it was missing the boot image (done that before so I'm familiar with that behavior haha)
Oh and I'm still S-on
Sent from my HTC6435LVW using xda app-developers app
CharliesTheMan said:
Flash the new Nos build, and flash cpalmers kernel after the Rom install and then reboot.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
canemaxx said:
That's what mine does too......just wait til the notification light turns orange and you will be all set......be patient.
Click to expand...
Click to collapse
Really? After it boots up? That's odd but ok I'll give it a shot again but probably tomorrow will post here again if it doesn't work....thanks everyone for responding. I'm out at the moment and need cell to be functioning hahaha just in case
Sent from my HTC6435LVW using xda app-developers app
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