I need help, not sure which I have done wrong. Last night I rooted and put TWRP on my phone. Tried to flash a rom and it just errored out. Tried multiple roms. So I got it s-off. Same issue.
I have tried last 2 versions of TWRP. Then I put latest Philz on and still can't install. I ended up wiping everything to test but now i'm stuck with a phone and no OS. I've been able to use the adb sideload method but can't get them to install.
Tried 3 roms. Phone was latest OTA before I tried anything. I saw something about it having a separate partition but the latest Philz was supposed to account for that. HBoot is 2.09
Is there a certain version of recover I am supposed to be on? Or any other suggestions? Thank you
jasin said:
I need help, not sure which I have done wrong. Last night I rooted and put TWRP on my phone. Tried to flash a rom and it just errored out. Tried multiple roms. So I got it s-off. Same issue.
I have tried last 2 versions of TWRP. Then I put latest Philz on and still can't install. I ended up wiping everything to test but now i'm stuck with a phone and no OS. I've been able to use the adb sideload method but can't get them to install.
Tried 3 roms. Phone was latest OTA before I tried anything. I saw something about it having a separate partition but the latest Philz was supposed to account for that. HBoot is 2.09
Is there a certain version of recover I am supposed to be on? Or any other suggestions? Thank you
Click to expand...
Click to collapse
First, you should be a bit more specific about which Roms you're trying to flash and which version of TWRP you are trying. If your hboot is 2.09, you can't flash any Roms built for the new partition. But without more specific information, I doubt anyone can offer much help.
Evolution_Freak said:
First, you should be a bit more specific about which Roms you're trying to flash and which version of TWRP you are trying. If your hboot is 2.09, you can't flash any Roms built for the new partition. But without more specific information, I doubt anyone can offer much help.
Click to expand...
Click to collapse
You most likely answered my issue. I thought I was on latest but I did see there is an hboot 2.10. So I am downloading the latest RUU to update me. It was the latest PAC. I thought since the phone said no updates available i was good to go.
jasin said:
You most likely answered my issue. I thought I was on latest but I did see there is an hboot 2.10. So I am downloading the latest RUU to update me. It was the latest PAC. I thought since the phone said no updates available i was good to go.
Click to expand...
Click to collapse
Good luck. To run the RUU, your bootloader must be relocked. You will remain S-off. Just unlock your bootloader afterwards at htcdev.com and install the TWRP built for the new partition. [emoji3]
Sent from my LGLS990 using Tapatalk
jasin said:
You most likely answered my issue. I thought I was on latest but I did see there is an hboot 2.10. So I am downloading the latest RUU to update me. It was the latest PAC. I thought since the phone said no updates available i was good to go.
Click to expand...
Click to collapse
The latest update wasn't released as a over-the-air update, hence the lack of a notification. Make sure you back up your internal storage, as the RUU will wipe it clean. Make sure you use Captain Throwbacks's TWRP 2.7.1.0b. Other versions of TWRP will not work properly with the new partition layout. Might want to look over the first few posts in the thread below for more info.
http://forum.xda-developers.com/showthread.php?t=2639180
Evolution_Freak said:
Good luck. To run the RUU, your bootloader must be relocked. You will remain S-off. Just unlock your bootloader afterwards at htcdev.com and install the TWRP built for the new partition. [emoji3]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
No need to relock if S-off. Only applicable for devices that are S-on.
Magnum_Enforcer said:
No need to relock if S-off. Only applicable for devices that are S-on.
Click to expand...
Click to collapse
Sorry, its been a while. [emoji45]
Sent from my LGLS990 using Tapatalk
Evolution_Freak said:
Sorry, its been a while. [emoji45]
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
No it hasn't You just forgot everything when you bought your G3.
Thanks guy. I am up and running with latest cm11. I could not get adb side load to work with that twrp. Finally found an old SD card. Could have been the Roms I was trying but it was latest PAC nightly. Anyways it's perfect now.
Sent from my Nexus 7 using Tapatalk
jasin said:
Thanks guy. I am up and running with latest cm11. I could not get adb side load to work with that twrp. Finally found an old SD card. Could have been the Roms I was trying but it was latest PAC nightly. Anyways it's perfect now.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Glad to hear you're up and running.
Can anybody help me?I installed InsertCoin Sense 6 Rom(i have TWRP v2.7.1.0b and unlock throught HTCdev.com)and i cant get throught boot image(which says HTC One and beatsaudio).That can I do?
If you're S-on you may need to fastboot flash the kernel. Hit the top link in my sig & scroll down to the section about S-on kernel flashing.
Related
I've been (at least trying to) patiently wait for Deck to post full install instructions for CM10 but the CM10 op is still bare as bones. Has anyone else posted an install guide or instructions yet?
I'm currently rooted with RegawMod and running MeanRom 2.1 and it's really terribly laggy and frustrating, I can't wait any longer for CM10. Do I need S-off to install CM10 or do I just wipe, flash, and go?
Thanks for any help or links!
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Its been my daily for 3 weeks.
Sent from my EVO using Tapatalk 2
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Sent from my EVO using xda app-developers app
corcgaigh said:
You don't need s-off. You will however have to flash the boot IMG separately by using fastboot or the app flash image GUI and a full wipe is definitely required. There is a helpful thread in Q&A called "don't panic" that will answer all your questions
Good luck
Click to expand...
Click to collapse
Dont use flash image gui unless you know how to do it manually through fastboot. You are just asking for issues
Instructions:
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-a.html
Rxpert said:
If you are on hboot 1.15 or higher you have to fast boot flash the kernel.
Other than that its just like a normal aosp install. Wipe flash rom flash gapps.
Click to expand...
Click to collapse
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Yes hboot 1.12 allows for access to the boot partition
Also luuuuucckkyyyyyy...
EdhyMonker said:
I'm on hboot 1.12, so does that mean I can just flash normally?
edit - From what I can tell from reading, hboot 1.12 doesn't have the same restrictions that 1.15+ do, so I think I'm OK but I would like verification.
Thanks for the help everyone.
Click to expand...
Click to collapse
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Bit off topic, anyone check to see if you can push a new splash, right now I'm too lazy to start my PC just to fastboot one measly splash
Rxpert said:
If you are on Hboot 1.12 I'd strongly suggest looking into getting S-OFF. Theres really no reason not to.
Up to you though, its not required
Click to expand...
Click to collapse
The S-OFF guide was way over my head so I just let it be. If there's not a real good reason for doing it, and I can still run CM10, then I'd rather not.
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
om4 said:
It allows you to directly flash new firmware like radios to fix any problems a device might be having. If you have Son and want the latest firmware you have to revert back to stock and accept ota, then unlock reflash recovery and reflash custom ROM or rooted stock, you could also just flash root installer if you want to just root stock
Click to expand...
Click to collapse
No, S-ON people with 1.12 H-boot can flash radios and firmware from recovery. They can do whatever they please in recovery just like S-OFF. S-OFF users can flash things from bootloader and even change the appearance of their h-boot to read S-ON and **locked** even though they are S-OFF
To the OP, this is the best rooting guide I've seen. It really explains everything step by step. http://androidforums.com/evo-4g-lte...panda-s-htc-dev-ltevo-root-dummies-guide.html Its recommended to have Linux at least bootable, because in the small chance the phone gets bricked... the unbricker program requires linux.
I ran it in windows before the unbricker was available, no issues here
You basically just hook the phone up to it and run the program like you do for most other root programs. All 1-click
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
om4 said:
Ah yeah forgot to mention that, most everyone is on 1.15 or 1.19 sorry
Click to expand...
Click to collapse
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
You don't have to flash any firmware updates. There are a few users with issues although they may be related to the ROM update and not necessarily the firmware included. I haven't really checked since I'm s on. If you want to update the radios there's an update zip here somewhere, be sure to read through everything carefully. Radios are more risky then every day flashing
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
EdhyMonker said:
Alright everyone now I need some help!
I flashed CM10 after s-off, was on stocked 1.13 rooted rom.
Now when CM10 boots up I am faced with a phone activation screen. It says something like "you will not be able to place calls or access the mobile network until the device is activated". I am unable to make calls or receive calls or access the internet. I have tried reflashing cm10 and the problem persists.
In the mean time, I will try flashing a nand backup and see where that gets me. I appreciate any and all help, and I have found no posts in the CM10 thread with a similar issue.
Update: I wiped and restored a back-up, MeanRom 2.1. Upon boot, hands-free activation ran and activated the phone and downloaded a PRL update. Everything is working fine now. Not sure if I should try CM10 again or what? Any advice?
Click to expand...
Click to collapse
ive only ever seen this issue with cyanogenmod and the old htc vogues, still great phones for what they were
EdhyMonker said:
Alright, I got S-Off using Lazy Panda and it went better than expected!
Do I need to flash updated firmware / radios separately from CM10, or does CM10 include latest firmware?
Sorry to ask dumb questions, but I do hope this thread will also be a good resource for others like me.
Click to expand...
Click to collapse
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Rxpert said:
Yes, you should be flashing the upgraded firmware. You'll see the full firmware as the very first downloadable link. Flash that
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
Rename the file to "PJ75IMG.zip", place on root of SD card, and boot into HBOOT to flash. Check the md5 to make sure its right. With radios you want to make sure its the correct file.
Welcome to S-OFF my friend
Click to expand...
Click to collapse
Thanks, but I tried this and it says "no image or wrong image" when trying to flash the PJ75IMG.zip file.
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
joebarkho said:
Did you type in PJ75IMG.zip or PJ75IMG and kept it a zip file...you should do the 2nd.
Click to expand...
Click to collapse
I thought that might've been the issue so I tried it both ways, didn't work either way. I'll take another shot at it tomorrow.
Just flashed my first ROM (newest CM 10.1 nightly) with TWRP and everything seemed to have gone well but when I hit "Reboot" the HTC logo flashed for a second and then the screen went black and it's not doing anything. Been like this for 10 minutes.
I already rebooted back into recovery and reset the phone and cleared the caches and flashed the ROM again. Same thing.
Anyone know what's going on?
rdtmk said:
Just flashed my first ROM (newest CM 10.1 nightly) with TWRP and everything seemed to have gone well but when I hit "Reboot" the HTC logo flashed for a second and then the screen went black and it's not doing anything. Been like this for 10 minutes.
I already rebooted back into recovery and reset the phone and cleared the caches and flashed the ROM again. Same thing.
Anyone know what's going on?
Click to expand...
Click to collapse
Are you S-OFF? If not, you need to flash the boot.img separately.
exSD said:
Are you S-OFF? If not, you need to flash the boot.img separately.
Click to expand...
Click to collapse
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
rdtmk said:
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
Click to expand...
Click to collapse
There are 2 S-off methods in the original development threads.
Sent from my EVO using Tapatalk 2
rdtmk said:
No i'm not. Are there instructions anywhere on how to do that? Thanks for the help :good:
Click to expand...
Click to collapse
Look in the thread. If the author has posted the boot.img you can do it fairly easily.
mulhiny said:
There are 2 S-off methods in the original development threads.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Figured it out. Flashed it manually with Fastboot method and it boots into CM10.1 now but my touchscreen appears to not be working
You most likely need newest firmware if I'm not mistaken. You really need to s-off your phone. Then you won't have all the difficulty your having. Otherwise, you need newest firm ware...
Sent from my EVO using Tapatalk 2
rdtmk said:
Figured it out. Flashed it manually with Fastboot method and it boots into CM10.1 now but my touchscreen appears to not be working
Click to expand...
Click to collapse
This is because you have the newest touch panel firmware. It only works with roms based off of 3.16...currently no aosp Rom will work for you unless you s-off and downgrade to the 3.15 panel firmware. This is my understanding anyway. Flash a 3.16 sense Rom (viper, meanbean, etc) and you'll be back in business.
Sent from my EVO using Tapatalk 2
mulhiny said:
This is because you have the newest touch panel firmware. It only works with roms based off of 3.16...currently no aosp Rom will work for you unless you s-off and downgrade to the 3.15 panel firmware. This is my understanding anyway. Flash a 3.16 sense Rom (viper, meanbean, etc) and you'll be back in business.
Sent from my EVO using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the help everyone. So without touch I wasn't able to turn on USB debugging mode so that I could get superCID so that I could S-Off so I tried to recover with the backup I made in TWRP but it just boot loops.
How can I copy a ROM onto my phone without actually being able to boot into a ROM?
rdtmk said:
Thanks for the help everyone. So without touch I wasn't able to turn on USB debugging mode so that I could get superCID so that I could S-Off so I tried to recover with the backup I made in TWRP but it just boot loops.
How can I copy a ROM onto my phone without actually being able to boot into a ROM?
Click to expand...
Click to collapse
Flash the ROM through fastboot.
fastboot flash zip nameofrom.zip
exSD said:
Flash the ROM through fastboot.
fastboot flash zip nameofrom.zip
Click to expand...
Click to collapse
says:
"writing 'zip' ... FAILED (remote: not allowed)"
Try getting a copy of cwm (not the touch version) and flash it via the fast boot method. Use the volume rockers to move, camera to select, power to go back.
It'd be easier to just ruu back to stock and start at square 1. Doesn't take that long to root and s-off anymore. Dirty racun would probably still work too.
Sent from my EVO using xda premium
Yeah, if you wanna run ANYTHING other than a sense 3.16 ROM, you're gonna HAVE TO S-off so you can downgrade that damn touch panel that came with the 3.16 update (thanks HTC :banghead
I thought the latest twrp was compatible with the updated TP now, though. What TWRP version you using? If not, as stated above, finding non-touch CWM recovery sounds like only/best solution. That was a good idea. Last I heard (long ago), CWM for this device breaks your /misc partition. Viperboy used to have it posted in the old viper thread so you could repair /misc. Not sure if it's still there.
Good luck.
From my Evo LTE, yup.
scottspa74 said:
Yeah, if you wanna run ANYTHING other than a sense 3.16 ROM, you're gonna HAVE TO S-off so you can downgrade that damn touch panel that came with the 3.16 update (thanks HTC :banghead
I thought the latest twrp was compatible with the updated TP now, though. What TWRP version you using? If not, as stated above, finding non-touch CWM recovery sounds like only/best solution. That was a good idea. Last I heard (long ago), CWM for this device breaks your /misc partition. Viperboy used to have it posted in the old viper thread so you could repair /misc. Not sure if it's still there.
Good luck.
From my Evo LTE, yup.
Click to expand...
Click to collapse
Twrp 2.4.x.x is compatible with 3.16 +TP
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
cdboss said:
I think I've done it this time. I was able to unlock the bootloader and also able to put TWRP recovery onto the phone. The mistake I made was trying to flash MIUI to the phone without backing anything up, so here I am and have been for the last 4 hours trying to figure out how to get my phone to boot into a ROM of any sort to try and S-OFF using the FacePalm method.
I honestly don't know what I should do at this point. I can still enter recovery and flash ROMs. Just, none of them actually load. The only time I can get any of them to load is when I flash it via recovery, then flash the boot.img via fastboot. However, when I do it this way, my touch screen within the ROM no longer works. So I can't press or do anything, to give my phone super user permissions. I'm really frustrated and just want to fix my phone. Can anyone offer some help or advice so I can try and fix this sometime between now and my death?
Thank you in advance.
Click to expand...
Click to collapse
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
certain putesbi
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Edit: I'm going to go with your suggestion of flashing a ROM that's made for 3.16, and see if my touch panel works so I can S-OFF and flash whatever I want. I'll let you know how that goes.
cdboss said:
Thank you for your reply and help.
I'm running HBOOT 2.09 to be exact. I'm also running TWRP 2.5, so I'm good there as well. Right now I can't boot into a ROM appropriately to achieve S-OFF. I tried creating a Ubuntu Live CD and the Kernel got messed up I guess when putting it on the disc. That was another frustration of mine, lol. I can't achieve the FacePalm method because I can't boot into a ROM to adb shell as super user, since it physically needs to be accepted on the phone.
I'm going to read what you suggested, though, perhaps that will give me the answer.
Click to expand...
Click to collapse
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
FinZ28 said:
What ROM are you trying to run? If it isn't based on software version 3.16 it WON'T WORK.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
cdboss said:
Just edited my post. I'm an idiot and didn't completely read your post. My apologies. I'm in the process of getting Viper4G at the moment, to try and achieve S-OFF.
Click to expand...
Click to collapse
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
cdboss said:
I was able to get into Viper, tried doing the FacePalm S-OFF and it wasn't successful, for whatever reason. However, at least I'm better off than I was before. Any suggestions from here? I really want to get MIUI on this and not really feeling up to installing Ubuntu tonight.
If not, I really want to thank you. At least I'm able to use my phone again, lol.
Click to expand...
Click to collapse
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
FinZ28 said:
You're going to have to go the Dirty Racun route, unfortunately
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Guess I'll have to try and make another Live CD. I have no interest in dual booting a copy of Ubuntu at the moment, lol.
Thanks for the help.
FinZ28 said:
Relax
Check the link in my sig. Should answer most of your questions regarding your issues.
You are S-on, most likely on Hboot 1.15 or newer. You have to flash the kernel separately from the ROM for the ROM to boot when you are S-on. This is why fastboot flashing the kernel (boot.img) worked.
Regarding your other issue, it sounds like you have the updated touch panel driver that came with the most recent OTA. You need to use TWRP 2.4+ and you can only run ROM's that are software version 3.16. Once you get S-off you can downgrade the driver and run whatever ROM you want
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
cdboss said:
I now was able to get S-OFF. What exactly do I do to downgrade those drivers and flash a ROM that I want?
Click to expand...
Click to collapse
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
FinZ28 said:
If you want to downgrade your touch panel, check out this thread:
http://forum.xda-developers.com/showthread.php?t=1704612
The above thread links to here:
http://themikmik.com/showthread.php...dio-Collection&p=220556&viewfull=1#post220556
The touch panel you want to downgrade to is located under the 3.15 firmware, so just follow the directions posted in order to downgrade.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
cdboss said:
Awesome, thank you. I was able to get the ROM I wanted on here and looks like everything is good to go. Appreciate the help, FinZ28.
Click to expand...
Click to collapse
You're welcome
Sent from my EVO using xda premium
So I usually just flash my stock att Rom, flash stock recovery , then update. Once I finish I flash twrp back , backup the newly updated stock Rom, then restore my custom Rom backup. This way at least I am benefiting from an updated radio etc.
Now, with this update I understand there is a new hboot. Is that only going to affect my ability to s off in the future ?
And also will twrp work with this new hboot that comes with the 4.3 ota update ? I'm not worried about s off. I just want to be able to flash custom kernels and roms.
So basically my question boils down to will twrp work with the new hboot? Am I safe to restore stock Rom, flash stock recovery , Ota and then flash twrp back ?
Any input would be greatly appreciated.
Regards
Sent from my HTC One using Tapatalk 2
yah00z said:
So I usually just flash my stock att Rom, flash stock recovery , then update. Once I finish I flash twrp back , backup the newly updated stock Rom, then restore my custom Rom backup. This way at least I am benefiting from an updated radio etc.
Now, with this update I understand there is a new hboot. Is that only going to affect my ability to s off in the future ?
And also will twrp work with this new hboot that comes with the 4.3 ota update ? I'm not worried about s off. I just want to be able to flash custom kernels and roms.
So basically my question boils down to will twrp work with the new hboot? Am I safe to restore stock Rom, flash stock recovery , Ota and then flash twrp back ?
Any input would be greatly appreciated.
Regards
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
You will be unable to S-Off after the update (I would highly recommend you s-off, you can always s-on after the update. Advantages of s-off are being able to "lock" the bootloader if you ever needed to return it to the manufacturer. Without s-off, you would only be able to "relock" your device and they can tell that you unlocked the bootloader)
As for TWRP, it will still work.
chenchen399 said:
You will be unable to S-Off after the update (I would highly recommend you s-off, you can always s-on after the update. Advantages of s-off are being able to "lock" the bootloader if you ever needed to return it to the manufacturer. Without s-off, you would only be able to "relock" your device and they can tell that you unlocked the bootloader)
As for TWRP, it will still work.
Click to expand...
Click to collapse
Thanks for the response. Yeah I'll go ahead and s off. I realize the advantages. Revone still the best method ?
Sent from my HTC One using Tapatalk 2
yah00z said:
Thanks for the response. Yeah I'll go ahead and s off. I realize the advantages. Revone still the best method ?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Yep!
chenchen399 said:
Yep!
Click to expand...
Click to collapse
Any issue with using Revone with arhd 21 which is a sense 5 android 4.3 rom? Or should I do it under a stock Rom that's rooted ?
Sent from my HTC One using Tapatalk 2
yah00z said:
Any issue with using Revone with arhd 21 which is a sense 5 android 4.3 rom? Or should I do it under a stock Rom that's rooted ?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
I believe that people have the most success on a 4.1.2 stock rom but don't quote me on that. You can always try on arhd but ymmv
chenchen399 said:
I believe that people have the most success on a 4.1.2 stock rom but don't quote me on that. You can always try on arhd but ymmv
Click to expand...
Click to collapse
Yeah it's not like it's that big of a deal to backup and restore my stock Rom. Root it and then s off. Probably the safest route.
Sent from my HTC One using Tapatalk 2
yah00z said:
So basically my question boils down to will twrp work with the new hboot? Am I safe to restore stock Rom, flash stock recovery , Ota and then flash twrp back ?
Click to expand...
Click to collapse
Hey, I just created a headache for myself trying this. I was unlocked and rooted (not S-off) until last night. I flashed the GuruReset ROM, did nothing but hook up wifi and did the 4.3 OTA. So afterwards the bootloader still showed unlocked and tampered.
I tried using Goo mgr to get twrp (only old 2.6.01 there) it wouldn't take, tried SuperSU from the PlayStore - no go. Went to HTCDev and the token created today is different than what I got this spring. Tried the Unlock_code and it won't take. I've got the original code I unlocked with but I'm thinking that would bork my 1 if I tried it now. I'll have more time later to mess with this later.
So NO I don't think you would get TWRP to work with hboot1.55.
swapgut said:
Hey, I just created a headache for myself trying this. I was unlocked and rooted (not S-off) until last night. I flashed the GuruReset ROM, did nothing but hook up wifi and did the 4.3 OTA. So afterwards the bootloader still showed unlocked and tampered.
I tried using Goo mgr to get twrp (only old 2.6.01 there) it wouldn't take, tried SuperSU from the PlayStore - no go. Went to HTCDev and the token created today is different than what I got this spring. Tried the Unlock_code and it won't take. I've got the original code I unlocked with but I'm thinking that would bork my 1 if I tried it now. I'll have more time later to mess with this later.
So NO I don't think you would get TWRP to work with hboot1.55.
Click to expand...
Click to collapse
Well I go about it a little different than you do it seems.
I restore my stock Rom. Then use fastboot to flash the stock recovery.
Then do the Ota.
Sent from my HTC One using Tapatalk 2
Yea it is technically different.
But if it works out well..... you won't have the headache I've got right now!
Good Luck & let us know.
*All's Good Here:good: I'd forgotten about twrp.img files http://www.teamw.in/project/twrp2/164
Just flash it in fastboot. It even re-rooted for me. Apparently didn't need to unlock again that's why HTCDev didn't work.
I am looking to use moonshine to achieve s-off. I currently have S-ON and SuperCID. I need to update firmware first, so I need to switch back to stock. I am planning on using this method to do so.
Do I need to un-SuperCID, if so, how?
If I leave SupeCID, and run RUU what happens? No OTAs, or something worse?
Excuse my noob questions.
no noob questions here man thats why we help and as far as updating firmware are you planing on using a custom rom and kernel or just wanting s-off for a custom kernel on 2.07 firmware?
supercid does not need to be changed you only have extra steps if you are s-off which then you would need to relock the bootloader first
t1gartist said:
no noob questions here man thats why we help and as far as updating firmware are you planing on using a custom rom and kernel or just wanting s-off for a custom kernel on 2.07 firmware?
supercid does not need to be changed you only have extra steps if you are s-off which then you would need to relock the bootloader first
Click to expand...
Click to collapse
Well my plan was to go back to stock to ota to the 2.07 then load custom rom, vipers new one actually, after doing moonshine to achieve s-off
I thought leaving supercid was going to prevent me from successful ota. I can always flash the zip instead of ota though, right?
Also I made a more detailed thread in the development section on what I am going to work on doing, with steps that I think are correct, here is the link. I was finally able to post in that section
http://forum.xda-developers.com/showthread.php?t=2531701
d3fiance said:
Well my plan was to go back to stock to ota to the 2.07 then load custom rom after doing moonshine to achieve s-off
I thought leaving supercid was going to prevent me from successful ota. I can always flash the zip instead of ota though, right?
Also I made a more detailed thread in the development section on what I am going to work on doing, with steps that I think are correct, here is the link. I was finally able to post in that section
http://forum.xda-developers.com/showthread.php?t=2531701
Click to expand...
Click to collapse
Since you have super cid you don't need use moonshine. Find the face palm method and enjoy
Sent from my DLX using xda app-developers app
thats right phaded.. im sorry defiance i forgot about facepalm method been so long since my first device all the others are already updated
t1gartist said:
thats right phaded.. im sorry defiance i forgot about facepalm method been so long since my first device all the others are already updated
Click to expand...
Click to collapse
I wonder why I got stuck on moonshine? Face off seems so much easier, for me anyways. No need to go back to stock... So as far as Firmware, after s off I just go in and flash the zip through adb?
d3fiance said:
I wonder why I got stuck on moonshine? Face off seems so much easier, for me anyways. No need to go back to stock... So as far as Firmware, after s off I just go in and flash the zip through adb?
Click to expand...
Click to collapse
After s-off, flash a recovery through fastboot and then whatever Rom you want
Sent from my DLX using xda app-developers app
Phaded said:
After s-off, flash a recovery through fastboot and then whatever Rom you want
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
I am happy to announce I am now S-OFF after facepalm! I actually found your thread about customer recovery. Will be doing that shortly.
One thing that is left to figure out is the tampered flag. I am not able to find any information on how to actually reset it. I found something on a different website about issuing a -t command. But that was after the s-off was achieved using revone. After further research, apparently all I need to do is flash another hboot to get rid of that flag?
P.S
This thread looks like a winner http://forum.xda-developers.com/showthread.php?t=2156713 am I on a correct path here?
yes thats correct
You can ignore that flag. If and when you return the phone to complete stock that will taken care of.
Sent from my DLX using xda app-developers app
t1gartist said:
yes thats correct
Click to expand...
Click to collapse
Phaded said:
You can ignore that flag. If and when you return the phone to complete stock that will taken care of.
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
New problem. Flashed 2.6 twrp, erased system, cache and internal storage. Went to sideload mode, keeps saying starting. Issue a command in and to load a Rom, nothing happens, cmd return a list of all the commands. Twrp still states starting sideload. Restart the phone to recovery, still the same problem. Flash older version of twrp?
Also twrp keeps telling me I am not rooted.
Thoughts?
Why did you wipe internal storage? Easiest way is to load the ROM onto internal and flash.
Rebooting twrp will install su binaries.
Try older twrp or cwm
Sent from my DLX using xda app-developers app
Phaded said:
Why did you wipe internal storage? Easiest way is to load the ROM onto internal and flash.
Rebooting twrp will install su binaries.
Try older twrp or cwm
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
Well Viper Sense 5 rom needed a full wipe, so, I wiped everything. Are you saying I do not have to wipe internal storage, just clear everything else, then flash the rom?
The problem was that I have a bad habit of putting spaces when renaming zip files. Once I renamed the zip adb worked just fine. :facepalm:
d3fiance said:
Well Viper Sense 5 rom needed a full wipe, so, I wiped everything. Are you saying I do not have to wipe internal storage, just clear everything else, then flash the rom?
The problem was that I have a bad habit of putting spaces when renaming zip files. Once I renamed the zip adb worked just fine. :facepalm:
Click to expand...
Click to collapse
Exactly, you don't need to wipe your internal storage. You lose pictures, videos, etc
Sent from my DLX using xda app-developers app
yeah with twrp 2.4.4.0 and later it is preselected for you so you dont wipe everything on your device just whats needed so lesson learned and in about a week you will be graduated to advanced droid dna room any hour lol
Phaded said:
Exactly, you don't need to wipe your internal storage. You lose pictures, videos, etc
Sent from my DLX using xda app-developers app
Click to expand...
Click to collapse
t1gartist said:
yeah with twrp 2.4.4.0 and later it is preselected for you so you dont wipe everything on your device just whats needed so lesson learned and in about a week you will be graduated to advanced droid dna room any hour lol
Click to expand...
Click to collapse
I am still learning as I go. Thanks for sticking around guys. But yay for graduation haha! :victory:
I have been flashing roms for the past 8 hours. Looking for the perfect sense 5. Every rom has issues with data on my phone. Tried 5 . Google play store will not download anything, Or it starts downloading at dial up speeds. 2 roms I actually had to reflash twice because they kept hanging u at at the initial start.
5 roms doing the same thing? I was starting to think something happened to the phone, so I reflashed the original UKB DNA 1.3 rom that I have been running all this time, and it does the same thing.
Any ideas?
flash a dead stock rom one by mircomod777 see how it runs should be last 4.1 version
t1gartist said:
flash a dead stock rom one by mircomod777 see how it runs should be last 4.1 version
Click to expand...
Click to collapse
So my phone went completely nuts last night. I decided to flash another back up that was working perfectly before going with your recommended rom. Kept failing in TWRP. So after 3 attempts I just decided to reload another rom. Rom installed, phone rebooted, went through initial setup. Once I finished with the initial setup my phone was running sense5 with all of the information from the backup. Needless to say I nuke everything, flash original TWRP (2.4.0.0 beta) that worked for me prior to 2.6. Do a clean install of Viper Sense5 rom and voila! Running perfect right now, no complaints. Fingers crossed. I guess I am done flashing roms for right now and sticking to Vipers. At least until KitKat comes.
good deal