Related
I just got a HTC vivid from a friend .first thing I did is unlock bootloader flash recovery s-off root . Phone is running gb . Here is where I need your help.I try to.flash jb Rom and it would boot. And when I touch screen phone would freeze and reboot.so I restore. What do I have to do to run jellybean ?
Sent from my HTC PH39100 using xda app-developers app
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
ZeRo2o9 said:
please read the stickies in the dev forum. in order to flash ics or jb you must flash the RUU if you are running gb. just flash the ics RUU and flash whatever jb rom you want after
Click to expand...
Click to collapse
thanks!!
I'm having a similar problem, but i just dont find the right ICS RUU to flash it seems.
I live in austria, have the htc velocity 4g, with 2.3.7 gingerbread.
Bootloader tells me:
*** UNLOCKED ***
HOLIDAY PVT SHIP S-ON RL
HBOOT-1.85.0023
eMMC-boot
Feb 1 2012,01:02:37
what i did for now:
i unlocked the bootloader (with htcdev), put on the twrp-recovery (2.4.4.0) (with hasoons-tool) and also tried wcxrecovery.img (for BoRKed)
wiped it clear, installed the cm10 [cm-10-20130310-NIGHTLY-holiday] and gapps / later BoRKed
since i am s-on i ran the "fastboot flash boot boot.img" command.
And the result is the reboot-cycle (cyanogenmod10 - with freezing short after the pin-code / permanently rebooting with BoRKed).
I read through the forums and found out that i need a newer hboot (ICS) to be able to install Jellybean ROMS.
as mentioned before, i think that i should lock my bootload and flash the right ICS RUU like told in the vivid-developers-forum.
i tried out the htc_vivid_att_RUU_3.26.502.56_US.exe but it told me [error130] wrong model, so i couldnt finish the RUU.
the wire-trick for s-off is a little bit scary to me, so i didnt try that for the time being.
so, for the time being i am a little bit out of clues and would be very glad if somebody could help me out with the right version of the RUU i should flash (and where i could get it) or am i completely off track here?
thnx, joe
Don't you flash the boot.IMG before you flash the ROM?
HTC_Vivid said:
Don't you flash the boot.IMG before you flash the ROM?
Click to expand...
Click to collapse
the step-by-step written guide from hasoon2000 (link) tells me to do it after i installed the ROM.
Now go back and press install. Go to the folder where the ROM you downloaded, is located in. Select the ROM and slide the screen to flash it. After it flashes, press the back button. Press Reboot and Reboot into bootloader. Open the ROM you downloaded from your computer. You should see boot.img. Extract it to your computer. Open my toolkit and press Flash a Kernel. Locate the boot.img and it will flash it.
After it flashes, press reboot from the phone.
Congrats! Enjoy your fully working or borked ROM! Remember, DO NOT ASK FOR ETAs, DO NOT BUG/PM A DEV ABOUT UPDATES, and BE RESPECTFUL TO THE DEVELOPERS!
Click to expand...
Click to collapse
Don't use twrp 2.4.4...
Switch to 2.4.2.0
Sent from my Vivid 4G using Tapatalk 2
oh, but right now i found it just the other way around.... in the
[SUPERGUIDE] ICS-Root-Flash-Stock
(Optional) Flash a custom Kernel/Recovery (Three options, I suggest the THIRD)
*ATTENTION* IF FLASHING A KERNEL FOR A NEW ROM YOU WANT, YOU MUST FLASH THE ROM IMMEDIATELY AFTER FLASHING THE KERNEL WITHOUT BOOTING UP, THE KERNEL COMES FIRST. OTHERWISE, YOU MIGHT BOOT LOOP.
Click to expand...
Click to collapse
i will give it a try, thanks!
--
edit:
will switch to 2.4.2.0
kernel flash first and then rom (with trwp-2420 recovery) led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Joehittn said:
kernel flash first and then rom with trwp-2420 recovery led to the same boot - freeze - cycle with cyanogenmod10 as described before...
i still think that i have to flash to an ICS RUU first, but i just need a working one (without the 130 model-id error)
Click to expand...
Click to collapse
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
homeslice976 said:
The model id error is because you're trying to flash a Vivid RUU to a Velocity. You'll either need to s-off and super CID, then you can run whatever RUU you want, or you need to get the correct RUU for your device. I was pretty sure that 1.85.0023 and 1.85.0025 were bootloaders that came with ICS though. Maybe I'm remembering wrong about that, but I thought that the first ATT leak had .0023 and the official release had .0025
please run this (from fastboot USB) and reply back with the return
fastboot getvar mainver
(I have the Telstra ICS RUU uploading now if that's what you'll need)
Edit: Here is RUU_HOLIDAY_ICS_35_S_Telstra_WWE_3.25.841.4_Radio_3.02.4740.09_34.20.701040.19_release_246698_signed
Also - if you'd like to try this before any of that, it may work as well (others have had success). From fastboot USB:
fastboot erase cache
Now flash recovery, ROM, boot.img (from my experience, it doesn't matter if the boot.img is flashed before or after the ROM, as long as it's flashed BEFORE trying to actually boot the ROM)
(note that if the problem is your bootloader version, this won't work.)
Click to expand...
Click to collapse
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
mainver: (shows nothing...)
CID: VODAP120
i gave the telstra ruu you uploaded (thank you very much) a try, but it also gave me the model-id-error.
do i have to flash the recovery back (where do i find the stock-recovery? in the backup?), i am always using the twrp242-recovery now.
i tried the steps you wrote down with the same result (boot-cycle).
i think i will have to give the "s-off and super CID" as u mentioned before a try and then use the telstra-ruu. i read that this worked out for some guys in germany. i will do this on saturday, i need to be fully concentrated to do that, not next to work...
thank you very much for now!
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
homeslice976 said:
One other thing.. you are relocking your bootloader before trying to run the ruu, and you're trying to run the ruu from fastboot?
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
yes, always relocked.
first i ran the RUU (telstra) from the gb-2.3.7 screen, now i tried it from fastboot.
same result - error 130 (model-id)
---------- Post added at 01:36 PM ---------- Previous post was at 01:16 PM ----------
XxSHaDoWxSLaYeRxX said:
Camo has a ruu index too.. I think in dev thread
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
I think you mean this thread [Collection] Stock Roms [3/25/13] but i cant find my provider (austria / a1 [telekom]) there. also there has been no OTA ICS launched in austria...
seems that i have to postpone the s-off, cant find the time to do it right now...
i will revive the thread when i finally went through it.
thanks for your help till now.
cyas
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
robot1000 said:
I've currently got Android Revolution HD 12.1 installed, however I need to return the phone to Vodafone UK Stock, due to returning the phone.
I found this link, which seems to give instructions on restoring the HTC ONE, however apart from downloading the OTA_M7_UL_JB_50_Vodafone_UK.......zip file from here, I'm really not sure which method to follow.
This is the information I have from the Software Information on my phone:
Android version: 4.2.2
Kernel version: 3.4.10-g445d072
Baseband version: 4A.14.3250.13_10.33.1150.01L
Build number: 2.24.401.1.CL211355
I would really appreciate some assistance
Click to expand...
Click to collapse
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
gee2012 said:
Here is a link to all RUU`s, zips and CWM/TWRP recovery rom`s http://forum.xda-developers.com/showthread.php?t=2207874. You`ll need S-Off however to downgrade the Hboot. If you`re not S-Off you cannot Flasha RUU with a older Hboot. Guess you`re on HBoot 1.54.000 now. Till the revone devs find a way to modify the S-Off exploit you`re stuck, link http://forum.xda-developers.com/showthread.php?t=2314582.
Click to expand...
Click to collapse
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
robot1000 said:
Thanks for responding
I've already downloaded the OTA's: Vodafone UK file from that link, however I'm really not sure what I should be doing with it
Edit
Just curious, if my phone is S-ON, how have I been able to install a custom ROM and recovery?
Click to expand...
Click to collapse
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik. You can`t do anything with the OTA atm, not even flash a Vodafone CWM recovery i`am afraid.
gee2012 said:
If the bootloader is unlocked but you`re S-On you can flash a custom recovery and roms, you however cannot downgrade or flash a newer Hboot afaik.
Click to expand...
Click to collapse
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
robot1000 said:
With regards to the Vodafone zip file, is it possible to flash that somehow and give the impression that's in factory state?
Click to expand...
Click to collapse
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
gee2012 said:
No mate, you don`t have a Vodafone rom, you have a custom recovery and you would need to lock the bootloader. It is not possible atm, stick with the rom you`re on for now and do not lock bootloader. Wait for revone to modify the bootloader xploit to get S-Off.
Click to expand...
Click to collapse
I've just gone into Bootloader and it's showing Hboot as 1.44.0000 !!
Would you mind giving me a brief outline on what I should be doing to get my phone back to vodafone stock?y
Many Thanks
Would flashing the Vodafone OTA zip file in recovery be safe or do I need to S-Off the device?
Please can someone advise
Thanks
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
robot1000 said:
Thanks for you response
I'm now S-Off, however what I can't get my head around is the RUU part. The Vodafone ROM that I require seems to be an OTA zip update, however I'm unsure on how to flash this as it doesn't seem to be RUU
Click to expand...
Click to collapse
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
postfatal said:
Wow, you have quite the adventure in front of you my friend if you want to return your phone to a pure stock state. I'll outline the steps and you can do some work and find the guides to complete them. Assuming you're on hboot 1.44 you'll need to go ahead and s-off, you can then remove the tampered flag. After you're s-off you're then going to need to double check you're using a stock unmodified hboot (you should be) and flash the pertinent RUU based on your phone - there are plenty of guides on how to select this. You'll then need to s-on again, google the command "fastboot oem writesecureflag 3" to find some information on how to do that.
Basically you've got your work cut out mate, sorry I can't be more help but the process I've mentioned aren't as simple or as safe as unlocking the bootloader. You'll need to put some effort and most importantly care as any one of them can brick your phone. Once you're s-off you've opened up very sensitive partitions which if changed or written to wrongly can instantly brick your phone. As such I'd do a lot of research before you undertake any of these steps, this is just off the top of my head to give you some guidance so I'd also check them, you really can't be too careful when playing around with £500 worth of tech. Good luck!
Click to expand...
Click to collapse
rider5512 said:
You cannot do it with an OTA zip... you need a full RUU but unfortunately there doesn't seem to be one available for Vodafone UK.
This one seems to be the closest one for you.... it's stock HTC Europe. I don't think at this time that returning to stock Vodafone is a possibility.
If you're sending it back for repair or replacement you could take a chance on sending it as it is.
Click to expand...
Click to collapse
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
robot1000 said:
Thank you for replying.
I've run that RUU from the link you provided and it stated that it's updating from 1.29.161.11 to 1.28.401.7, however an Error [131] message appeared stating 'Customer ID Error'.
Any ideas?
Click to expand...
Click to collapse
Ok... you need to change that ID in the phone.
Reboot the phone to bootloader then fastboot and connect to pc then from your ADB directory on PC issue the command "fastboot oem writecid HTC__001" this will then give you the right ID for the RUU.
Note it's HTC__001.... 2 underscores !
Hello all...
I recently got an HTC One and decided to root it but now I am unable to get the 4.2.2 update.
Ive tried to find a way to revert back to stock but so far no luck.
I've only been able to get it back via a factory reset but the Team Win Recovery Project
and bootloader is still present and halts the 4.2.2 update.
phone details are...
Android version : 4.1.2
HTC Sense Version : 5.0
Software Version : 1.29.206.16 CL175272
HTC SDK API Level : 5.12
baseband 4a.14.3250.13_10.33.1150.01L
CID is o2__001
Is there an RUU I can use to revert it back to stock?
Ive looked around but couldn't find an appropriate RUU
Only thing I have found is the OTA_M7_UL_JB_50_O2_UK_1.29.206.11-1.27.206.1_P_release_315484
Would using this in TWRP get me back to stock so I can get the 4.2.2 update?
ANY help would be hugely appreciated!!!
PhaZEtwOk13 said:
Hello all...
I recently got an HTC One and decided to root it but now I am unable to get the 4.2.2 update.
Ive tried to find a way to revert back to stock but so far no luck.
I've only been able to get it back via a factory reset but the Team Win Recovery Project
and bootloader is still present and halts the 4.2.2 update.
phone details are...
Android version : 4.1.2
HTC Sense Version : 5.0
Software Version : 1.29.206.16 CL175272
HTC SDK API Level : 5.12
baseband 4a.14.3250.13_10.33.1150.01L
CID is o2__001
Is there an RUU I can use to revert it back to stock?
Ive looked around but couldn't find an appropriate RUU
Only thing I have found is the OTA_M7_UL_JB_50_O2_UK_1.29.206.11-1.27.206.1_P_release_315484
Would using this in TWRP get me back to stock so I can get the 4.2.2 update?
ANY help would be hugely appreciated!!!
Click to expand...
Click to collapse
I don't know if this would work but...
I have a nandroid backup of my O2 UK One.
This was taken prior to upgrading via OTA to 4.2.2.
Upgrading to 4.2.2 meant my hboot became 1.54.
I now find that if I restore my backup that the touchscreen is completely unresponsive - as far as I can tell because of the hboot upgrade - as any 4.2.2 roms work fine - and a nandroid for O2_002 (Germany) which was prior to 4.2.2 exhibited the same behaviour.
What I'm suggesting is, if you haven't yet upgraded to 4.2.2 yet - then you may be able to use my backup to restore your phone to a state ready to receive the OTA and upgrade to 4.2.2.
Yup - I'm not too sure it would work either! WE could both do with someone with a little more experience to advise us here!
However - I'm willing to provide the backup - but I would ask one favour.
If it works - please, please, make a nandroid backup of the completed update (i.e. O2_001 4.2.2) and let me (and probably quite a few people here) get their hands on it!
As you've probably noticed - O2 variants are not well catered for either here - or indeed anywhere on the net.
If you want to give it a try PM me - and I'll provide a link so you download it and try it out.
hmmm
Gandalf Greyhelm said:
I don't know if this would work but...
I have a nandroid backup of my O2 UK One.
This was taken prior to upgrading via OTA to 4.2.2.
Upgrading to 4.2.2 meant my hboot became 1.54.
I now find that if I restore my backup that the touchscreen is completely unresponsive - as far as I can tell because of the hboot upgrade - as any 4.2.2 roms work fine - and a nandroid for O2_002 (Germany) which was prior to 4.2.2 exhibited the same behaviour.
What I'm suggesting is, if you haven't yet upgraded to 4.2.2 yet - then you may be able to use my backup to restore your phone to a state ready to receive the OTA and upgrade to 4.2.2.
Yup - I'm not too sure it would work either! WE could both do with someone with a little more experience to advise us here!
However - I'm willing to provide the backup - but I would ask one favour.
If it works - please, please, make a nandroid backup of the completed update (i.e. O2_001 4.2.2) and let me (and probably quite a few people here) get their hands on it!
As you've probably noticed - O2 variants are not well catered for either here - or indeed anywhere on the net.
If you want to give it a try PM me - and I'll provide a link so you download it and try it out.
Click to expand...
Click to collapse
Well I'm back on O2 (thanks for that Gandalf) instead of the Euro ROM+SuperSID I was using before but still can't get it to update to 4.2.2
Just can't seem to get back the stock bootloader..
even when unrooted, locked(relocked)
played about with various recovery.img like has been suggested, no joy
Is there a way to manually update?
I'm absolute newbie at all this hehehe
PhaZEtwOk13 said:
Well I'm back on O2 (thanks for that Gandalf) instead of the Euro ROM+SuperSID I was using before but still can't get it to update to 4.2.2
Just can't seem to get back the stock bootloader..
even when unrooted, locked(relocked)
played about with various recovery.img like has been suggested, no joy
Is there a way to manually update?
I'm absolute newbie at all this hehehe
Click to expand...
Click to collapse
You need to be unlocked to flash recovery.
The image supplied contains the original stock recovery.
ADB fastboot flash recovery recovery.img
Also - probably flash the boot image
ADB fastboot flash boot boot.img
Relock - OTAs require that.
Also - have you reverted to your original CID?
Keep trying!
Sent from my HTC One using xda premium
Now I've woken up!
1) Make sure you're unlocked and S-Off
2) Change your CID to O2___001 ( that's 3x "_") - fastboot oem writecid xxxxxxxx
3) Extract boot.img and recovery.img from backup provided.
4) Place these files in the folder on your PC containing your fastboot file.
5) Connect the phone in fastboot usb mode
6) fastboot flash boot boot.img
7) Restart in recovery mode
7a) Personally I'd wipe everything here - data cache etc.
8) Restore backup
9) Restart to bootloader usb mode
10) fastboot flash recovery recovery.img
11) fastboot flash oem lock
12) Reboot
You should now hopefully have an HTC One running 4.2.1 with a locked bootloader and the correct CID - OTA should work now.
If anyone reading this knows different or can point out any mistakes or best practises please do so!
well no joy so far
Given up on going back to stock at the moment, having too much fun with modded roms etc.
Tried multiple ways to get back to stock recovery and the strange thing is I can flash between various recover.img/boot.img and swap between the clockworkmod and TWRP but the stock recovery.img seems to not over write during the flash.
Each time it reverts back to the custom recovery with the
"entering recovery... this build is for development...
(I put the superCID back to default but would it be because it detects the S-off ?
from what I've read I didn't think that would matter tbh)
BUT..
I can now swap between the various custom ROMS/Nandroid backups with ease using clockworkmod, Rom manager and CWM Backup manager.
fun times!!!
From what ive learnt, 4.2.2 has a different method of saving backups to a hidden file that hasn't been showing up when ive tried to transfer the back-up to my computer. Even CWM backup manager has failed to pull the hidden backup across and show it as a visual file in pc that I can transfer across..
Maybe this is because of the lack of dev options in the Android Revolution HD-One 2.0 GE ??
and having to just use the HTC One as a "Media device MTP" rather than the usb with debugging ??
(or am i just missing something here?)
But.. have found Android Commander for the pc which has helped a lot with this
and now I'm learning a bit more about the file structuring in Android..
Anyway onwards, upwards and outwards ..
just scraping the surface of the Android os so far...
PhaZEtwOk13 said:
Given up on going back to stock at the moment, having too much fun with modded roms etc.
Tried multiple ways to get back to stock recovery and the strange thing is I can flash between various recover.img/boot.img and swap between the clockworkmod and TWRP but the stock recovery.img seems to not over write during the flash.
Each time it reverts back to the custom recovery with the
"entering recovery... this build is for development...
(I put the superCID back to default but would it be because it detects the S-off ?
from what I've read I didn't think that would matter tbh)
BUT..
I can now swap between the various custom ROMS/Nandroid backups with ease using clockworkmod, Rom manager and CWM Backup manager.
fun times!!!
From what ive learnt, 4.2.2 has a different method of saving backups to a hidden file that hasn't been showing up when ive tried to transfer the back-up to my computer. Even CWM backup manager has failed to pull the hidden backup across and show it as a visual file in pc that I can transfer across..
Maybe this is because of the lack of dev options in the Android Revolution HD-One 2.0 GE ??
and having to just use the HTC One as a "Media device MTP" rather than the usb with debugging ??
(or am i just missing something here?)
But.. have found Android Commander for the pc which has helped a lot with this
and now I'm learning a bit more about the file structuring in Android..
Anyway onwards, upwards and outwards ..
just scraping the surface of the Android os so far...
Click to expand...
Click to collapse
As I understand it the "dev purposes only" is because you don't have a signed boot.img.
The boot.img I supplied with the backup should be signed - did you copy it from the backup and place in your adb folder to flash prior to restoring the backup? Though, saying that, I thought if you were s-off that the boot.img would be restored as part of the backup. I'm at a loss as to why it doesn't work.
Likewise with the recovery.img.
As regards backup - try reading http://forum.xda-developers.com/showthread.php?p=34116836 or alternatively use 6.0.3.1 as that older version allows for transfer/restore to/from external sd card via OTG cable - slowly tedious but it works.
Ah well - have fun - I'll have to wait until the devs fix revone to allow s-off with 1.54 so I can revert my hboot and restore my backup in order to achieve stock O2 rom and OTA .
Gandalf Greyhelm said:
restore my backup in order to achieve stock O2 rom and OTA .
Click to expand...
Click to collapse
Im actually glad to get rid of the O2 rubbish
Thanks for the info and Nandroid.img appreciated man !!!
PhaZEtwOk13 said:
Im actually glad to get rid of the O2 rubbish
Thanks for the info and Nandroid.img appreciated man !!!
Click to expand...
Click to collapse
You're welcome.
The reason I want to be able to restore to pure stock is to cover my ass if the phone ever needs to be returned under warranty.
Because of the 1.54 hboot update a lot of people are frustrated because they can't s-off and choose what they wish to do with their phone.
Fortunately - as I still have that nandroid I'll be able to downgrade my hboot, s-off and restore back to prior OTA - as soon as revone is updated.
Guys a little help here as well
I am lost tbh I have android version 4.1.2 software no. 1.29.206.16...bought it from O2 UK. I feel so helpless cz I am new with this stuff and I have no clue how to remove the stupid TWRP thing and unroot my htc one and update it to 4.2.2. Can any one pleasee tell me how to do it...as step by step guide please :'(
I'm stuck...
Hi guys, ive just purchased a rooted UK O2 phone running google play software and was wondering if you had the stock Nandroid or any kind of way to put my phone back to stock?
Ive tried to flash some different boot and recovery .img but now i think i have soft bricked it as the HTC quietly brillant screen appears and then the phone shuts off again
I am new to this so any pointers would be helpful too
Heres the phone's Info:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: O2___001
Thanks in advance!
New to HTC
!!
CWM or TWRP
Hi,
which recovery did you use to root your htc one O2?
if u used CWM, then what type? i mean did you downloaded CWM for htc one ( International)?
Gandalf, do you have the back up file still? I would be very grateful if I could have a copy.
Thanks
furiannn said:
Gandalf, do you have the back up file still? I would be very grateful if I could have a copy.
Thanks
Click to expand...
Click to collapse
What to you need exactly? What's your CID, MID, and S-On or S-Off? and Why?
nkk71 said:
What to you need exactly? What's your CID, MID, and S-On or S-Off? and Why?
Click to expand...
Click to collapse
Hi,
I have an O2 HTC One. CID is 002 I think. I have S-On at the moment, but I am in the process of trying to get S-Off so that I can remove the ***Tampered*** and relocked signs.
I dropped the damn thing down the toilet and need to send it in for repair so I just wanted to make sure they dont get funny about repairing it when I have installed custom rom, because the reason for me sending it back is not due to that!
I have been searching the forums a bit and have found a nandroid backup of O2 rom, so will try that. The Android Rev 51 rom I have at the moment will not let me gain S-Off with rumrunner - always gives me an error. Going to try stock and see what happens.
furiannn said:
Hi,
I have an O2 HTC One. CID is 002 I think. I have S-On at the moment, but I am in the process of trying to get S-Off so that I can remove the ***Tampered*** and relocked signs.
I dropped the damn thing down the toilet and need to send it in for repair so I just wanted to make sure they dont get funny about repairing it when I have installed custom rom, because the reason for me sending it back is not due to that!
I have been searching the forums a bit and have found a nandroid backup of O2 rom, so will try that. The Android Rev 51 rom I have at the moment will not let me gain S-Off with rumrunner - always gives me an error. Going to try stock and see what happens.
Click to expand...
Click to collapse
Follow my guide to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
you can use:
Code:
nandroid [B]O2___102 1.27.206.1[/B]: ro.aa.modelid=PN0710000
ro.aa.cidlist=O2___001,O2___102
if it matches your "fastboot getvar all" (MID & CID)
but first you need to S-Off.
nkk71 said:
Follow my guide to return to stock: http://forum.xda-developers.com/showthread.php?t=2541082
you can use:
Code:
nandroid [B]O2___102 1.27.206.1[/B]: ro.aa.modelid=PN0710000
ro.aa.cidlist=O2___001,O2___102
if it matches your "fastboot getvar all" (MID & CID)
but first you need to S-Off.
Click to expand...
Click to collapse
Those are my exact numbers, thanks very much
furiannn said:
Those are my exact numbers, thanks very much
Click to expand...
Click to collapse
sure no problem, so first s-off, then follow the guide, you'll be 100% stock.
Let me know if you have any questions.
Cheers
nkk71 said:
sure no problem, so first s-off, then follow the guide, you'll be 100% stock.
Let me know if you have any questions.
Cheers
Click to expand...
Click to collapse
I checked your guide and gained S-OFF with firewater, much quicker and smoother and more importantly, actually successful as opposed to rumrunner!
One more question, the downloads for the backups are fairly slow and Im halfway done downloading M7 CWM Nandroid Backup CID O2 102 3.62.206.1.
Is this version just an updated one vs the 1.27.206.1 2013-03-30 ?
Which should I use?
Thanks
Hello All,
Here's my dilemma. I successfully rooted my HTC One (AT&T), and was recently attempting to unroot it. I followed this one here http://forum.xda-developers.com/showthread.php?t=2182823. Since I have the AT&T version, I downloaded the first one the list found there, however it wouldn't verify. Next I downloaded the AT&T AIO here http://forum.xda-developers.com/showthread.php?t=2242635. I was able to use that to figure out according to the info it displayed that I actually needed the Google Edition one from the previous link. I thought that was weird since I dont have the google edition one. But when I fast booted that one, everything appeared to go through with a hitch.....Until it restarted.
After it restarted, I only have a black screen. No start up. I restarted the phone and went into the bootloader and to my surprise, the bootloader was black instead of the normal white.
I've tried several RUUs found here http://www.androidruu.com/index.php?developer=M7
I've tried both the exe and flashing the zip.
I have no clue what to try next. Please XDA, your my only hope.
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
iElvis said:
Are you s-off? I would assume so if you've been able to run multiple RUUs and are getting weird signature results. What mods/roms did you do to your phone before you started all this?
If you can get to bootloader, you're not bricked. You're on the 3.06 GE hboot, but it's not clear why you can't boot up.
Click to expand...
Click to collapse
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Tylegn said:
----From the top of bootloader down----
***Tampered***
***Relocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSO-V31.120.274.0617
(in red) OS-3.03.1700.10 (3.06.1700.10)
eMMC-boot 2048MB
Aug 1 2013, 18:48:40.0
Does that help at all?
Click to expand...
Click to collapse
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
iElvis said:
Were you ever s-off? You should not have been able to run that GE RUU on an s-on AT&T phone.
Click to expand...
Click to collapse
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Tylegn said:
I hate to say.... I have no clue if I was before or not. I just relocked it like the directions told me. Is there any saving me? Also, thank you for your quick responses.
Click to expand...
Click to collapse
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
iElvis said:
You bought it new? Not used from someone else? If so, it was always s-on.
You're on GE firmware somehow. It's possible you have a conflict with your model or carrier ID. Can you run through the exact steps you took when you started trying to unroot? Exactly which files you used and how you ran them?
Click to expand...
Click to collapse
I received the phone directly from HTC through a sell to earn contest.
Not sure if it matters much but I unlocked the bootloader through HTC Dev.
To unroot,
1) Put phone in bootloader with fastboot
2) Relocked bootloader
3) fastboot oem rebootRUU
4) fastboot flash zip 2.24.401.1.zip (failed)
Used one of the AIOs that stated I had modelid: PN0712000 and cidnum: CWS__001. That when I grabbed the GE version.
5) fastboot flash zip 3.06.1700.10.zip
6) Phone finished, rebooted to a black screen
7) Rebooted into bootloader (Which is now black instead of white)
8) Sad ever since....
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
ageldea consider
iElvis said:
Where did you get that GE zip? I'm not sure why the AIO toolkit told you that you were GE but I'd like to check the file.
I suspect the problem is that you have 4.3 GE firmware but a 4.1 OS. Flashing a 4.2 or 4.3 rom might fix.
Click to expand...
Click to collapse
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Tylegn said:
This is where I got:
http://forum.xda-developers.com/showthread.php?t=2182823
I'll need a step by step from you if you can because, I'm having a h3ll of a time trying to get anything to flash.
Click to expand...
Click to collapse
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
iElvis said:
:facepalm: Just realized the issue.
Your bootloader is locked and you still have custom recovery installed, I'm guessing. Can you select Recovery in bootloader and see what happens? If you're still with TWRP or CWM, that's the issue; you can't boot locked on custom recovery.
You have to unlock again or flash the stock recovery in fastboot. Unlocking will wipe your phone, unfortunately.
Flashing recovery in fastboot is easy if you have the stock recovery file.
fastboot flash recovery [filename].img
Click to expand...
Click to collapse
Found the stock recovery. Attempted to flash it and got this:
sending 'recovery' <16303 KB>...
OKAY [ 1.786s]
writing 'recovery'...
<bootloader> signature checking...
FAILED <remote: 12 signature verify fail>
finished. total time: 3.178s
Is there a different way I should be doing it.
HTC One has the Gray HTC logo chilling on the screen...
Also tried in normal fastboot mode...
Tylegn said:
You are right about having the recovery option in the bootloader but when I try to select that option, Android shows up with the spinning blue thing in it's stomach, then it dies with a red triangle.
I'll try flashing the recovery again. After I find a stock recovery img. LOL
Thanks again!!!
I'll post what's going on as I do it.
Click to expand...
Click to collapse
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
iElvis said:
Actually, I think that red triangle is stock recovery. I think to get to the recovery options you press power+vol up on that screen. But it doesn't matter because clearly you're not on custom recovery.
I don't see that 3.06 firmware package in the OP of that thread. Can you find the post you found it attached to?
Click to expand...
Click to collapse
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
ADD: I just successfully flashed the stock recovery.... Too scared to muck something up so I'll waif for your superior guidance!
Thanks again
Tylegn said:
If you click on the download link in that post for the GE it downloads as that 3.06 firmware..
Also, not sure if it was smart or not but I unlocked the bootloader again to see if it would fix the conflicts you mentioned before. Haven't tried flashing anything yet...
Click to expand...
Click to collapse
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
iElvis said:
I forgot Mike updated that link.
Okay, I see what you did now. You've essentially upgraded your phone to a GE because the android-info.txt in this official firmware matched your MID and CID; that allowed it to run. The problem is that you can't go back now because you're s-on. Your phone won't boot because you have the GE kernel installed but I assume a Sense rom.
This should be easy to fix. You can flash custom recovery now that you've unlocked, then flash a custom rom. This will get your kernel and rom consistent again and you should be able to boot.
Unrooting is a different story. You can't go back to the stock configuration you had when you got the phone without s-off, which you can't get on 1.54 hboot. I'm afraid you're stuck until AT&T releases 4.3 and you can run a RUU.
Click to expand...
Click to collapse
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Tylegn said:
So no getting my white bootloader back till next release? That's ok.
However, how do I flash the custom ROM. I got the customer recovery going but I don't know how to get the ROM on there.... Flashing isn't working, still getting signature failures.
Sorry
Click to expand...
Click to collapse
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
iElvis said:
You can only run a later firmware. When the signed 4.3 Sense firmware is released (it may be there now), you should be able to run that and get back the stock HTC bootloader.
You need to adb push the rom file onto your phone. There is a tutorial for doing it here: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
Thank you so much! I believe I can take it from here.....Until I brick my phone when the signed 4.3 comes out. LOL
Until next time. Thanks iElivis you are a BADA$$!:good::good::good:
i am currently on cm.10.1 and i want to go back to stock so i can S-off the device
i don't have a backup of the original firmware , and i've found the RUU for the phone but i don't think i can just use that right ?
i have to find a zip file of the stock rom correct ? and then lock the bootloader and then S-off the phone correct ?
then i can put the RUU on the SD card and go back to original stock ?
can anyone point me to the correct answer ? i just finished putting the Rezound my girlfriend has back to stock , but i was able to find a .zip of the global rom they have for it
anyone wanna help me out ? i was on the ICS rom last
Hboot 1.85.0025
unlocked and S-on
goal is S-off , but i don't know how the method would be on the vivid
for the rezound i had a global rom Zip i flashed with amon-ra and then i was able to S-off and then run a RUU and everything worked out
dust906 said:
i am currently on cm.10.1 and i want to go back to stock so i can S-off the device
i don't have a backup of the original firmware , and i've found the RUU for the phone but i don't think i can just use that right ?
i have to find a zip file of the stock rom correct ? and then lock the bootloader and then S-off the phone correct ?
then i can put the RUU on the SD card and go back to original stock ?
can anyone point me to the correct answer ? i just finished putting the Rezound my girlfriend has back to stock , but i was able to find a .zip of the global rom they have for it
anyone wanna help me out ? i was on the ICS rom last
Hboot 1.85.0025
unlocked and S-on
goal is S-off , but i don't know how the method would be on the vivid
for the rezound i had a global rom Zip i flashed with amon-ra and then i was able to S-off and then run a RUU and everything worked out
Click to expand...
Click to collapse
Use the search function.. This has been answered way too many times
bilibox said:
Use the search function.. This has been answered way too many times
Click to expand...
Click to collapse
and most of the answers are for people already S-off
i am S-on , and there was only one thread i found a rooted Stock rom zip file , and i was just hoping someone around here had all the things i need sitting around
im trying the rom located here to try and S-off
http://bionicgeeks.the-talk.net/t14-stock-rom-att-ics-de-odexed-zip-aligned-rooted-bloated
this one ok ? or is there one i should use over it
dust906 said:
and most of the answers are for people already S-off
i am S-on , and there was only one thread i found a rooted Stock rom zip file , and i was just hoping someone around here had all the things i need sitting around
im trying the rom located here to try and S-off
http://bionicgeeks.the-talk.net/t14-stock-rom-att-ics-de-odexed-zip-aligned-rooted-bloated
this one ok ? or is there one i should use over it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1416836
Second post and it was the top threads on the development page... As I said... Use the search function
bilibox said:
http://forum.xda-developers.com/showthread.php?t=1416836
Second post and it was the top threads on the development page... As I said... Use the search function
Click to expand...
Click to collapse
yea im having problems.........i relocked the bootloader
now i can't boot into any rom , and im trying to flash the stock rom zip via hboot and it is not going through
i tried it on the computer , and it says i can update and it will start the process and go into the boot loader , then it says failed and wants to start a recovery process
any help is appreciated , and i have been reading every post i can find on the issue , as i just did this to my girlfriends phone last night..... this is slighty different as many links are dead , and im having trouble finding everything i need
i was on TWRP recovery , but now the bootloader is locked so i have no recovery at all , im going to try and flash the zip with a locked bootloader now , but i don't anticipate it working
ive pulled the factory RUU's from multiple threads , and i can't get them to install
i've been looking for a zip of the stock rom that i can try and flash on a unlocked bootloader so i can S-off , but i haven't found one i can get to boot
like i said , i tried this one
http://bionicgeeks.the-talk.net/t14-stock-rom-att-ics-de-odexed-zip-aligned-rooted-bloated
i flashed the boot.img from the zip , and then tried to flash the zip file via TWRP and it would not boot at all.... hung at the screen after the beats splash screen
do i need to flash the stock recovery ? i don't have it if so ........ any advice what to try next ?
Ruu allows me to initiate update ...... starts sending to phone then says sending forever
....failed
any help
all the Ruu's i download send for a long time and then fail
i was not on a stock rom before trying any of this
i relocked the bootloader and then i have been trying to run the RUU
no other steps need to be taken ?
i have been searching for a working RUU all day....... none of them will actually install the firmware.... any ideas from anyone on what i should do
maybe some personal help ? im willing to try anything at this point
OK slick.... First... Slow down...
You screwed yourself badly here by just running off the handle...
First... Where in the world is your phone now...
Bootloader status...
Recovery...
Last kernel you fastbooted...
And I swear to whatever you call holy... If you ask what fastboot is...
You can find a working RUU on goo.im
Sent from my Vivid 4G using Tapatalk 4
found a zip i was able to flash of the stock rom finally worked from hboot with a locked bootloader
now i can get to s-off
I don't know why you would have such a hard time finding the right RUU. It's still on HTC's website for God's sake.