Morning all, yesterday, i was having problems with my phone, so i relocked it, and put the Stock O2 Uk Ruu file back on it, it then prompted me for a software update, which I accepted to do.
Anyway, all was going fine, decided to re-flash my phone, and try the modded rom again, unfortunatley the Rom seemed corrupt for some reason, i did make a nandroid back up of the New stock rom, just be on the safe side.
So i decided to re-lock the phone again and run the Stock RUU, but in the updating process, it gave me a error saying this is the wrong Ruu, i presume it was something to do with my Hboot also being updated ?
Is there anyway at all , i can downgrade the Hboot to the previous one, so i can run the Stock Ruu?
All is not lost as i am using the nandroid backup at the moment.
Thanks
Schumi 01 said:
Is there anyway at all , i can downgrade the Hboot to the previous one, so i can run the Stock Ruu?
Click to expand...
Click to collapse
you can't downgrade hboot
flash recovery, flash kernel, install rom. ready!
skdubg said:
you can't downgrade hboot
flash recovery, flash kernel, install rom. ready!
Click to expand...
Click to collapse
Damn that's a shame, maybe i will stick with my recovery image for now then, and hopefully there will be a new Ruu available in the future.
Thanks
Schumi 01 said:
Damn that's a shame, maybe i will stick with my recovery image for now then, and hopefully there will be a new Ruu available in the future.
Thanks
Click to expand...
Click to collapse
It's best to keep updated with the latest hboot anyway. There were users having issues with some custom roms, because they did not have the latest hboot.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
It's best to keep updated with the latest hboot anyway. There were users having issues with some custom roms, because they did not have the latest hboot.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Cheers Andro, going to do a fresh install tonight of the custom Rom, hopefully, i had a bad install, phone is working fine on the Nandroid back up, so no big problem really.
Schumi 01 said:
Cheers Andro, going to do a fresh install tonight of the custom Rom, hopefully, i had a bad install, phone is working fine on the Nandroid back up, so no big problem really.
Click to expand...
Click to collapse
Hopefully it was just a bad download. Do a "fastboot erase cache" after you flash the kernel, and do a full wipe in recovery (you can always flash the data.img from you nandroid if you really need too. Although if the rom is of a diffrent base to your nandroid it may cause issues) Hopefully that will stop your problems
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Hopefully it was just a bad download. Do a "fastboot erase cache" after you flash the kernel, and do a full wipe in recovery (you can always flash the data.img from you nandroid if you really need too. Although if the rom is of a diffrent base to your nandroid it may cause issues) Hopefully that will stop your problems
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Cheers Andro,
It seems to be working fine now, must have been a bad install.
Just one quick question say i did want to go back to Stock through a nandroid backup,
If i get the boot img, and the recovery img, from the stock nandroid,
is it a case of
flashing the stock img,
restore the nandroid backup
then flash the recovery
relock device and reboot ?
Thanks
Edit ignore the above, just read that the recovery image from the nandroid is not stock.
Schumi 01 said:
Cheers Andro,
It seems to be working fine now, must have been a bad install.
Just one quick question say i did want to go back to Stock through a nandroid backup,
If i get the boot img, and the recovery img, from the stock nandroid,
is it a case of
flashing the stock img,
restore the nandroid backup
then flash the recovery
relock device and reboot ?
Thanks
Edit ignore the above, just read that the recovery image from the nandroid is not stock.
Click to expand...
Click to collapse
Thats the general procedure. Don't worry about stock recovery. If you look in development. There are a few posts where people have posted stock recoveries.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Thats the general procedure. Don't worry about stock recovery. If you look in development. There are a few posts where people have posted stock recoveries.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Thanks again Andro, just one more thing if you dont mind, are stock recovery's different for different Hboots, and are all stock recoveries the same for any international roms.
Thanks
Schumi 01 said:
Thanks again Andro, just one more thing if you dont mind, are stock recovery's different for different Hboots, and are all stock recoveries the same for any international roms.
Thanks
Click to expand...
Click to collapse
No. As far as i know (and have tried) stock recoverys are the same no matter what hboot you have. Obviously at&t have a diffrent kernel. So we cnt use there recovery.
Sent from my HTC One X+ using Tapatalk 2
Related
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 recently bought a htc one x plus and as the person as i am, i quickly unlocked the bootloader, installed a custom recovery (ClockworkMod recovery) and kernel. But then i tried to flash a AOKP Jelly Bean 4.2.1 Custom ROM and after flashing it, it would just hang around the AOKP boot logo (a horse head with rotating rings around it). Then, without thinking, i relocked the bootloader (with a custom rom) to send it for warranty. Now, it would only go to the bootloader screen. After going through a few forums, i found out that this could be repaired by using the correct ruu for my device but they all say that i have to flash a stock recovery and boot.img before relocking the bootloader in order for the ruu to work. So my question is can i reunlock my bootloader to flash the stock recovery and boot.img without bricking the device and can flashing the correct ruu repair my phone. Please reply, i'm so desperate. The htc guys wanted me to pay $400 just to repair it and since i rooted the phone, warranty does not cover it.
Shaarven said:
I recently bought a htc one x plus and as the person as i am, i quickly unlocked the bootloader, installed a custom recovery (ClockworkMod recovery) and kernel. But then i tried to flash a AOKP Jelly Bean 4.2.1 Custom ROM and after flashing it, it would just hang around the AOKP boot logo (a horse head with rotating rings around it). Then, without thinking, i relocked the bootloader (with a custom rom) to send it for warranty. Now, it would only go to the bootloader screen. After going through a few forums, i found out that this could be repaired by using the correct ruu for my device but they all say that i have to flash a stock recovery and boot.img before relocking the bootloader in order for the ruu to work. So my question is can i reunlock my bootloader to flash the stock recovery and boot.img without bricking the device and can flashing the correct ruu repair my phone. Please reply, i'm so desperate. The htc guys wanted me to pay $400 just to repair it and since i rooted the phone, warranty does not cover it.
Click to expand...
Click to collapse
You can unlock the boot again if you kept the code you received when you did it the 1st time round. Once you have unlocked it you can then flash any Rom. Did you make a nand backup before installing the custom Rom? If you did you can reinstall the custom recovery and restore the phone to stock.
I currently run the viper 3.4.2 rom, you could also install this after installing the custom recovery.
Sent from my HTC One X using xda app-developers app
Hi Sharveen,
Please do youself a favor, and don't use the CWM Recovery, this Recovery is not adapted for this phone, I strongly suggest that you install TWRP Recovery, the latter is way more complete and rigorously tested on the HTC One X+.
TIP : Please read, read, read as much as you can before doing any changes to your phone, that can save you lots of problem.
First make sure your SDK tool (adb) is correctly installed and also the HTC's drivers. (There is a link for a tutorial in my signature.)
Download the correspondent recovery for your phone International OR AT&T/Telus (N.B. Links are available in the Sticky FAQ)
Flash the Recovery.
Clear Cache
Reboot in Recovery
DO A COMPLETE BACKUP OF YOUR ACTUAL ROM. BE SURE TO KEEP IT IN A SAFE PLACE
Install your correspondent version of any ROM.zip you want that is already on your storage. (Otherwise,Sideload a ROM to be able to flash one inRecovery)
Flash the boot.img of your desired ROM
Clear Cache Again
Reboot
Should work
Thank you soo much for replying and no, i did not make a nandroid backup when i tried to flash the rom. So can flashing a correct ruu repair my phone and hopefully get it back to stock rom...
Is your SDK/ADB tool correctly installed?
Shaarven said:
Thank you soo much for replying and no, i did not make a nandroid backup when i tried to flash the rom. So can flashing a correct ruu repair my phone and hopefully get it back to stock rom...
Click to expand...
Click to collapse
Yess ruu will bribg back your phone to stock....it will restore everythings
What is your software version?
Sent from my HTC One X+ using Tapatalk 2
If you want to flash a RUU you need to install the original Recovery then flashing the correspondent RUU. Just let us know what is your preference, but as far as I am concern, your original backup wasn't made too bad, but you can still install a modded ROM.
This is gonna be your call for the continuity.
Shaarven said:
Thank you soo much for replying and no, i did not make a nandroid backup when i tried to flash the rom. So can flashing a correct ruu repair my phone and hopefully get it back to stock rom...
Click to expand...
Click to collapse
You could try searching the forum to see if someone has a nand backup for your phone. Only problem with ruu's is they haven't released the more up to date ones, so if your phone had the latest ota I doubt you will be able to use the ruu method. Personally I would use a custom Rom until you can find a nand for your phone.
Sent from my HTC One X using xda app-developers app
anyen said:
Yess ruu will bribg back your phone to stock....it will restore everythings
What is your software version?
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
My software version is 3.1204.168.32 and i did find an ruu in android files with the exact version (x.xxxx.168.xx).
Lucky Thirteen said:
If you want to flash a RUU you need to install the original Recovery then flashing the correspondent RUU. Just let us know what is your preference, but as far as I am concern, your original backup wasn't made too bad, but you can still install a modded ROM.
This is gonna be your call for the continuity.
Click to expand...
Click to collapse
The original recovery will be contained in the %temp% folder created by the ruu when opened but do i have to flash the boot.img which is also contained in the folder and also most of the forums says that you have to flash the boot.img after flashing the recovery while some says that you could relock the bootloader and flash the ruu after flashing the recovery only. So in my situation, do i have to flash the boot.img or not.
One X Plus Stock Rom (RUU)
Please help me, I couldn't find a RUU for my HTC One X +
It s on relocked mode now.
ENRC2B_U PVT SHIP-SON RL
HBOOT-1.35.0000
CPLD-NONE
MICROP-NONE
RADIO-3.1204.168.32
eMMC-bootmode:disabled
CPU-bootmode:disabled
HW Secure bOOT:enabled
nihat38 said:
Please help me, I couldn't find a RUU for my HTC One X +
It s on relocked mode now.
Click to expand...
Click to collapse
if you unlock your phone, you can only "relock" it, it will not become "locked" forever, even use RUU program
Unread Storage
after flashing ViperX+ 1.1.0 with sense4+ on my HTC OneX+, the storage can't be read at all.. what's wrong with my hox+?
I prefer not to format it via my PC, coz I haven't backup my data
xidia said:
after flashing ViperX+ 1.1.0 with sense4+ on my HTC OneX+, the storage can't be read at all.. what's wrong with my hox+?
I prefer not to format it via my PC, coz I haven't backup my data
Click to expand...
Click to collapse
I guess you have flashed older version then your radio and unlit file..
Try to download latest version of the ROM.
Sent from my HTC One X+ using XDA Premium 4 mobile app
[email protected] said:
I guess you have flashed older version then your radio and unlit file..
Try to download latest version of the ROM.
Sent from my HTC One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I can just flash older ROM, without any radio and unlit file procurement.. *wanna experience once more the sexy older carousel home screen*
This is last resort. I've been at this for a while so please someone help out.
Got the phone.
Did the OTA update to Telus 1.20.661.1.
Unlocked and Rooted with AIO Toolkit.
Tryed to install a few roms to get rid of Sense (Venom XL+ 1.2.7). None worked and confirmed by others users with newer software.
Trying to get back to stock and can't do that either. Downloaded the "RUU_EVITARE_UL_JB_45_TELUS_WWE_1.15.661.11_Radio_1.09.55.17_18.20.95.55L_release_290307_signed" and get either USB or general errors 155/159
Can't figure out how to get back to an older firmware and stock rom/boot image.
Can someone please help?
HTC One X+ Telus unlocked
Soft. 1.20.661.1
kernel 3.1.10-g262c6aa
BB 2.14.55.11_18.21.95.55L
Build 1.20.661.1 CL164725
I have the same issues after the AT&T firmware update, I can't flash any ROM. The only one I can use is the stock nandroid backup.
I've tried everything with no avail.
I'll try with CWM recovery and let you know.
Sent from my HTC One X+ using Tapatalk 2
I was able to use CMW recovery and reinstall a backed up rom but since trying the RUU exe it worked just enough to wipe that so I don't have it anymore.
Where do I find a stock backup?
I'm reading in other threads that the RUU's don't work with hboot versions above 3.5. Not sure if that's why the RUU exe won't work for me or not.
Seems like very outdated files on HTCdev. Nice of them to break their last resort recovery tools and not bother updating them.
garmig said:
I have the same issues after the AT&T firmware update, I can't flash any ROM. The only one I can use is the stock nandroid backup.
I've tried everything with no avail.
I'll try with CWM recovery and let you know.
Sent from my HTC One X+ using Tapatalk 2
Click to expand...
Click to collapse
Did actually get it out of boot loop.
Had to catch it at a very specific position during start up to be detected long enough to flash the boot image.
Got it on the AT&T 1.19 rom now but really want to get rid of sense and get the Venom rom working. Wish I hadn't hit that upgrade button..
meboy said:
I was able to use CMW recovery and reinstall a backed up rom but since trying the RUU exe it worked just enough to wipe that so I don't have it anymore.
Where do I find a stock backup?
I'm reading in other threads that the RUU's don't work with hboot versions above 3.5. Not sure if that's why the RUU exe won't work for me or not.
Seems like very outdated files on HTCdev. Nice of them to break their last resort recovery tools and not bother updating them.
Click to expand...
Click to collapse
Because you have the new hboot, you cannot go back to an earlier rom. If you flash the rom from this thread http://forum.xda-developers.com/showthread.php?t=2235248 you should have updated stock. You will need to push the zip from the link to your phone with adb. You can then use TWRP or CWM to install rom and fastboot to flash the updated boot.img.
Thanks. I noticed others mention the hboot and RUU issue.
That's the rom I ended up getting to work. But it's stock only.
I haven't tried it yet but others are reporting that the AT&T 1.19 doesn't work with custom roms either.
artiemon said:
Because you have the new hboot, you cannot go back to an earlier rom. If you flash the rom from this thread http://forum.xda-developers.com/showthread.php?t=2235248 you should have updated stock. You will need to push the zip from the link to your phone with adb. You can then use TWRP or CWM to install rom and fastboot to flash the updated boot.img.
Click to expand...
Click to collapse
meboy said:
Thanks. I noticed others mention the hboot and RUU issue.
That's the rom I ended up getting to work. But it's stock only.
I haven't tried it yet but others are reporting that the AT&T 1.19 doesn't work with custom roms either.
Click to expand...
Click to collapse
HI, I've the AT&T's HOX+ with AT&T 1.19 boot, working with Viper+-v2.0.0; yes, with some lacks in the boot. I tested it with hxore_v1.0_ATnT.img (Kernel) and also with the embbeded in Viper, the Kernel boot-1.19.502.1, when the boot is sucess the device works fine ...
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