Hi everyone
I want to do a "Official" Update for my HTC One (M7) that i rooted a while ago...
I allready read this topic : http://forum.xda-developers.com/showthread.php?t=2748547 And i found that the first and most important think is to have a Stock recovery
Unfortenantly i Have a custom recovery (TWRP) and the bootloader is "Unlocked"
What's the most secure and efficient way to be able to update my phone Offcially ?
Thnk's for help
Flash a stock recovery... You'll probably find one in the thread you got your custom one from.
Then just relock bootloader with the command
fastboot oem lock
You can now update with no issues.
AmineOne said:
Hi everyone
I want to do a "Official" Update for my HTC One (M7) that i rooted a while ago...
I allready read this topic : http://forum.xda-developers.com/showthread.php?t=2748547 And i found that the first and most important think is to have a Stock recovery
Unfortenantly i Have a custom recovery (TWRP) and the bootloader is "Unlocked"
What's the most secure and efficient way to be able to update my phone Offcially ?
Thnk's for help
Click to expand...
Click to collapse
if you have unlocked your bootloader and rooted the phone, you'll probably have issue installing the update even if you restore the stock recovery, Like I said in the post you have linked, when you unlock bootloader, /data/preload get wiped. You need this folder and its content back in place to install ota updates. Also, if rooting or anything else you did, modified some /system files, the ota will not install. However, flash you stock recovery back and try the ota, if the ota fails with an image of a red triangle and an exclamation mark inside, then you'll need to restore some files (either /system files or /data/preload files) You have to flash the stock recovery version that match your current version. If you can post the output of fastboot getvar all (minus imei and serialno) we could help you find the recovery you need.
and btw, no need to relock bootloader like said above. Better to leave it unlocked so you'll not have to unlock it again and wipe /data/preload again
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
@alray I tried the update after flashing the stock recovery and relock the bootloader, and as you mentioned it shows the exclamation red mark... I will past the info getvar soon, big thanks
AmineOne said:
@alray I tried the update after flashing the stock recovery and relock the bootloader, and as you mentioned it shows the exclamation red mark... I will past the info getvar soon, big thanks
Click to expand...
Click to collapse
relocking bootloader was not required, better to re-unlock it now, or you'll have the same problem with the next ota.
try to reapply the update. when the phone boot in stock recovery and start to flash the ota, press and hold vol+ then power and release both. You'll see some command lines and you'll be able to know which file is causing the ota to abort.
look for something like: unexpected content or no such file or directory)
also post the getvar all
Hello again
This is the getvar :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
@alray
I applied what you told me, (apply the update and look after errors)
her are what i get after that :
Finding update package...
Opening update package...
Verifing update package...
Installing update...
assert failed: check_cid(getprop("ro.cid"), "00000000" , "11111111" , "22222222" , "33333333" , "44444444" , "55555555" , "66666666" , "77777777" , "88888888" , "99999999" , "ORANG309") == "t"
Installation aborted.
I:Write host_mode:0 done
Is any body out there ?
Where did you get the update?
SaHiLzZ said:
Where did you get the update?
Click to expand...
Click to collapse
Download from Setting>Update
No more help
AmineOne said:
No more help
Click to expand...
Click to collapse
you can't manually install an OTA if you are S-ON, you need to "download and install" on the phone directly.
nkk71 said:
you can't manually install an OTA if you are S-ON, you need to "download and install" on the phone directly.
Click to expand...
Click to collapse
I do so ! as i told befor i download using automatic update on setting (with my phone)
AmineOne said:
I do so ! as i told befor i download using automatic update on setting (with my phone)
Click to expand...
Click to collapse
hmm, in that case I don't have any ideas.
some users say they had to relock bootloader, though i don't think that's necessary, as the US Dev Edition comes bootloader unlocked by default, and still receives OTAs just fine.
I guess you could try that.
AmineOne said:
Hi everyone
I want to do a "Official" Update for my HTC One (M7) that i rooted a while ago...
I allready read this topic : http://forum.xda-developers.com/showthread.php?t=2748547 And i found that the first and most important think is to have a Stock recovery
Unfortenantly i Have a custom recovery (TWRP) and the bootloader is "Unlocked"
What's the most secure and efficient way to be able to update my phone Offcially ?
Thnk's for help
Click to expand...
Click to collapse
The easy way is to use a RUU to get you phone back to Stock
then download and flash the update.
the more complicated way is to restore stock recovery and the missing files from unlocking the bootloader and then download the update.
Depending on your phones CID / MID some are able to just flash a Guru Reset and choose to install the stock recovery and say no to root and then take the OTA update.
As you already have TWRP why not just install the Stock unrooted 6.xx.xxx.x Rom ? >> http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
@nkk71
Thank you any way
Yes as alray told befor it's not necessary to lock the bootloader, my probleme I think is bigger cuz my version is Orange Spanish
Hope some one will help me soon
AmineOne said:
@nkk71
Thank you any way
Yes as alray told befor it's not necessary to lock the bootloader, my probleme I think is bigger cuz my version is Orange Spanish
Hope some one will help me soon
Click to expand...
Click to collapse
well, you could always go s-off and make things easier on yourself, but a question, what stock recovery are you using and where did you get it?
nkk71 said:
well, you could always go s-off and make things easier on yourself, but a question, what stock recovery are you using and where did you get it?
Click to expand...
Click to collapse
This one : Stock M7 GPE Recovery (i got it frome another web site i don't know if it's permitted to put external links in the Forum ?! )
AmineOne said:
This one : Stock M7 GPE Recovery (i got it frome another web site i don't know if it's permitted to put external links in the Forum ?! )
Click to expand...
Click to collapse
okay, that will not work, a GPE recovery, you need one for your phone. the easiest would be to extract it from the OTA
nkk71 said:
okay, that will not work, a GPE recovery, you need one for your phone. the easiest would be to extract it from the OTA
Click to expand...
Click to collapse
And how can i do that ? (i'm still novice don't know much)
Related
Hello.
I just got my One, upgraded from the One X
I am very skilled regarding rooting, flashing custom roms, recoveries, etc. I just have a quick question.
Is it possible to install custom rom, custom recovery and turn the phone S-OFF - WITHOUT getting the tampered message?
- If no, tell me that
- If yes, read on
Second case: Does this RRU match my M7?
First of all, what have i done myself:
- Unlocked bootloader
- Installed TWRP
- Made a nandroid backup
- Relocked bootloader because i want to flash [ROM] Android Revolution HD 3.2 Google Edition | High Quality & Performance | Android 4.3 Jelly Bean | 2.14.1700.15
- Flashed latest firmware for my phone - 2.24.401.1 (the thread above states that its not needed but recommended)
- Got the TAMPERED message and wants to get rid of that (and return from HBOOT 1.54 to original HBOOT 1.44)
In order to get rid of that message, this guide state i must use "method 2", and as part of that method 2, i must find the correct RRU.
The following is the output of getvar all before firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3980mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.043s
Click to expand...
Click to collapse
And this is getvar all after firmware update:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REMOVED
(bootloader) imei: REMOVED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4010mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
Click to expand...
Click to collapse
Will this RRU be for my phone: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
- I found it here: http://www.androidruu.com/index.php?developer=M7
I chose it as its the RRU for the M7 Europe model that gets closest to my original main version (1.29.401.16 vs 1.28.401.7), also the radio in that RRU is just a tad older than my own original radio.
Also, is it possible to downgrade like that (im quite certain it is, just want to be sure).
Kind Regards
TwinAdk
Wait, you was in 1.44 hboot and now you're on 1.54?
If yes, you can't get the s-off.
The tools for the S-OFF are working only in 1.44 hboot, and, i if read right, now you have the 1.54 and you can do nothing...
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
TwinAdk said:
****, you are kidding me, right? And RUU downgrade is not an option? That will downgrade my RUU too.
Aside from S-OFF being down the toilet, are there any other downsides to Hboot 1.54?
Click to expand...
Click to collapse
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Guich said:
You can't downgrade with any ruu if you don't have the S-OFF...
Nope, but now you can't remove the ****Tampered**** line and you can't get the S-OFF...
Click to expand...
Click to collapse
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
TwinAdk said:
God dammit.. Well, are there any downsides regarding custom roms, to having the 1.54 hboot? Also, is it likely S-OFF will ever be avail. with 1.54?
Click to expand...
Click to collapse
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Guich said:
No, you can flash all rom, kernel, mod, theme that you want.
For the S-OFF, no, devs said that they will work on the tool for the S-OFF when the new update form htc will come with the 1.55 hboot
Click to expand...
Click to collapse
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
TwinAdk said:
So when 1.55 hboot arrives, work will start for S-OFF for that HBOOT? Any ETA on 1.55?
Click to expand...
Click to collapse
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Guich said:
Atm there are some leaks of android 4.3 and new hboot 1.55, but this isn't the update that we will get.
For the question, yes
Click to expand...
Click to collapse
Okay, thanks
Now that i booted the phone, my storage is not available and wifi does not turn on (it says enabling, but thats all) - great start! Any idea why?
Ill look into it tomorrow my self, im off to bed now... Guess the One X will be in service for a few more days...
EDIT: Im on a firmware thats NOT for the android version i have, i think thats the problem. I guess ill have to sideload the custom rom running 4.3, and get it running that way.
Freaking hell, no S-OFF!
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Guich said:
You relocked your bootloader after the flash of the rom?
If yes, you have to unlock this, reflash the rom and the kernel, and do a wipe of cache and dalvik-cache...
Click to expand...
Click to collapse
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
TwinAdk said:
I cannot flash the rom as my SD is unavail... Is it an option to sideload the ROM?
Click to expand...
Click to collapse
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Guich said:
Flash the stock recovery and then do a factory reset in bootloader, this will fix your sd.
After flash a custom recovery and try to use the sideload
Click to expand...
Click to collapse
Hello.
I flashed the stock recovery, and factory reset the phone. It rebooted during factory reset (of course), and booted normally afterwards. Wifi and storage did however still not work.. From within android im told that the storage is "Unavailable" (ill post screenshots later) - and from TWRP, i am told that i have "Internal storage" of 28xxx mb available (not sure about the excact size, around 28 gb) - but i cannot mount it and make it available from windows.
I can see the phone in windows, as a HTC media unit, and browse the content (storage -> legacy -> more folders -> root of SD card with folders like "downloaded" etc - default folders). But when i get there i cannot create folders or files, i can only view the content.....?
1. I cannot downgrade with RRU, since im S-ON
2. My Wifi and storage SEEMS broke (i suspect its because i flashed the firmware mentioned earlier, and my android version is not happy with that firmware - someone with more insight are welcome to comment on my guessing here)
3. Sideloading the rom i want to use (based on android 4.3) seems to be the only option - but can i sideload when my SD is not available in recovery?
Starting to worry a bit here
And thank you for all your help so far :good: I didnt get to say that last evening.. Appriciate!
Kind Regards
Hello sir,
first of all, let me say you screwed up already when not researching XDA before doing an update. Since i have done so myself numerous times, let me advise you to make it a habit, when buying a new phone to specifically research downsides of updates before accepting any.
Particularly in the HTC world, it has become a common thing to only gain S-OFF while the phone is in early software states and loose this ability towards later releases. Until now, many HTC phones i have had to deal with, had issues with disabling security on later firmwares.
Then, the storage problem you describe could possibly be related to something i have seen a fair few times. What Guich told you to do is usually the ultimate trick to get it back working. But let me ask this first: were you able to access storage from windows normally before the update? Or could you also face a driver issue?
OK. Guich's comment did not help. You flashed the stock recovery from the firmware you run. Then you ran Factory Reset from within Bootloader? Or from within android? If the latter, try the first...
I will be putting up stock recoveries from different RUU's soon on my thread here: http://forum.xda-developers.com/showthread.php?t=2316726 but you also find them on the forum already by searching. Try different stock recoveries and factory reset from Bootloader.
Then, if that doesn't help, try to run the OTA 2.24 (which already runs on your phone!) again by booting into bootloader, then picking "Fastboot" there (use volume down and up to navigate and power to confirm) and then going to your adb/fastboot with a command window. Oh, connect phone to PC of course
Lets say you have adb and fastboot plus the dll files in C:\Android. Open a CMD window and do "CD C:\Android" to go there.
there, run "fastboot oem rebootRUU" (type exactly as i do here, omit the quotes though).
then, copy and paste the OTA file (obtain HERE) to the same folder (C:\Android).
For easier typing in CMD, rename the OTA to something short and simple like test.zip or whatever.
then go back to your CMD Window and type in "fastboot flash zip test.zip"
Since its the same hboot and firmware in the OTA like you have on phone and since this package is official and signed, your phone ---should--- accept the flash. If not (maybe because you got the wrong model ID or wrong CID) i wouldn't really know how to proceed. But you DID accept that OTA before so it MUST be for your phone or else it wouldn't have flashed in the first place.
If it flashes fine, boot your phone up and check if it fixed everything.
If not, run the check for software update in Settings/Info/ and see if there is already an official OTA for your phone available that brings you past the 2.24. If not, download one of the inofficial OTA's and --- hope --- that you can flash it. Like 3.18 or 3.22. The first is for Asia/Taiwan though and will almost certainly NOT flash on your phone and the second is BrightstarUS and for the DEV edition and will also almost certainly not flash. But its worth a try.
beyond that, i have no more valuable tips. Only thing I would try is to flash CWM and do a clear storage, wipe data, wipe everything there. But be sure to have your nandroid ready if you do that. CWM uses a slightly different formatting method so it could possibly correct issues. In the past, i have read about screwed up SDcards related to CWM formatting more often than those that got screwed up by TWRP though. So its not exactly ideal to play with CWM on a phone that has already issues with its partition. But if i was desperate, i would do it anyway.
If that doesnt help or make it worse, do the very same thing on TWRP, pick the "wipe Data" option which prompts you to type "yes" into an input line. This will once again format your SD with a different method. It could possible correct this problem.
DO NOT attempt to screw around with the SD Partition using tools like MiniTool or EASUS if you can access the sd from them at all!
The SD Card is an EXT4 file system and cannot be formatted with FAT or NTFS from windows. If you do that, the phone wont work at all anymore. The exact parameters to format the partition externally are not known to me and i doubt you can address the partition from within windows at all. Maybe it works under linux...
Sorry. Cant be much help here. If that all doesnt work, just flash stock recovery back and restore your stock nandroid and send it in for repair. Them service dudes will have the right RUU and fix it for you.
[EDIT]
Oh and before i forget: if you can fix it with these tips, you owe me one
You have to flash Team Venom's ViperOne then instead of ARHD! :laugh:
Aroma installer is running now!! So excited to see the result! I sideloaded the zip, via adb sideload Nice short article on it here: http://teamw.in/ADBSideload
Will return with outcome :highfive::fingers-crossed::fingers-crossed::fingers-crossed:
EDIT: Its back! Running custom rom with sd card avail and wifi working! Pew, saved by adb sideload, increddible!
Hi everybody,
I already checked a lot of threads in xda but it didn't solve my problem so I do it by myself...
Just got a HTC One and when I wanted to install the Google Edition ROM by bigxie with mini SDK, ADB and TWRP... I just messed up:
- OK to unlock bootloader
- S-OFF didn't work
- I accidentaly wiped everything: the OS...
I tried push a ROM with adb push rom.zip /sdcard/rom.zip but it didn't help:
- S-ON didn't allow me to install custom ROMs
- I couldn't turn my phone S-OFF because my PC didn't recognise it anymore + have no OS
- adb devices command didn't see my phone
Then I tried to relock it to install an official RUU from HTC but:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
I guess it comes from my HBOOT-1.54, I red we have to be in 1.44 but one more time I can't downgrade my HBOOT because I'm not S-OFF.
Now my HTC One M7_UL is :
* TAMPERED *
* RELOCKED *
*** Security Warning ***
- S-ON
- HBOOT-1.54.0000
Checkmate ?
Thanks in advance...
can you unlock your phone using HTCdev? get a new token and try.
---------- Post added at 06:29 PM ---------- Previous post was at 06:20 PM ----------
samih7 said:
Hi everybody,
I already checked a lot of threads in xda but it didn't solve my problem so I do it by myself...
Just got a HTC One and when I wanted to install the Google Edition ROM by bigxie with mini SDK, ADB and TWRP... I just messed up:
- OK to unlock bootloader
- S-OFF didn't work
- I accidentaly wiped everything: the OS...
I tried push a ROM with adb push rom.zip /sdcard/rom.zip but it didn't help:
- S-ON didn't allow me to install custom ROMs
- I couldn't turn my phone S-OFF because my PC didn't recognise it anymore + have no OS
- adb devices command didn't see my phone
Then I tried to relock it to install an official RUU from HTC but:
"(bootloader) signature checking...
FAILED (remote: signature verify fail)"
I guess it comes from my HBOOT-1.54, I red we have to be in 1.44 but one more time I can't downgrade my HBOOT because I'm not S-OFF.
Now my HTC One M7_UL is :
* TAMPERED *
* RELOCKED *
*** Security Warning ***
- S-ON
- HBOOT-1.54.0000
Checkmate ?
Thanks in advance...
Click to expand...
Click to collapse
Do you still have a custom recovery installed?
nkk71 said:
can you unlock your phone using HTCdev? get a new token and try.
Click to expand...
Click to collapse
Thanks for your answer.
Yes, I can. Should I install TWRP or CWM afterwards ?
samih7 said:
Thanks for your answer.
Yes, I can. Should I install TWRP or CWM afterwards ?
Click to expand...
Click to collapse
doesnt matter, either will do. choose the one you prefer.
were you able to unlock bootloader?
nkk71 said:
doesnt matter, either will do. choose the one you prefer.
were you able to unlock bootloader?
Click to expand...
Click to collapse
Yes, it's now unlocked and I installed TWRP.
samih7 said:
Yes, it's now unlocked and I installed TWRP.
Click to expand...
Click to collapse
ok, can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
nkk71 said:
ok, can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Here it is :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxx
(bootloader) imei: xxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
(bootloader) battery-status: good
(bootloader) battery-voltage: 4286mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.039s
samih7 said:
Here it is :
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANGB10
finished. total time: 0.039s
Click to expand...
Click to collapse
another missing version-main , this is really getting weird.
are you still looking to go s-off? if so you're on hboot 1.54, which means a 2.24.xxx.? ROM, so download and try rumrunner with this
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-1-zip/
and/or
http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
select WIPE, select ROOT, unselect "stock recovery"
nkk71 said:
another missing version-main , this is really getting weird.
are you still looking to go s-off? if so you're on hboot 1.54, which means a 2.24.xxx.? ROM, so download and try rumrunner with this
and/or
select WIPE, select ROOT, unselect "stock recovery"
Click to expand...
Click to collapse
If version main is the version of the OS, I don't have one. :-S
Yes I'm still looking for it and install the Google Edition ROM...
Ok I'll try it, it's downloading, I hope it'll recognise the phone.
samih7 said:
If version main is the version of the OS, I don't have one. :-S
Yes I'm still looking for it and install the Google Edition ROM...
Ok I'll try it, it's downloading, I hope it'll recognise the phone.
Click to expand...
Click to collapse
version-main is the firmware version of the phone, just seems it's disappearing a lot last couple of days.
hboot 1.54 has firmware 2.24.xxx.x, so one of the roms I linked will hopefully get you s-off using rumrunner
nkk71 said:
version-main is the firmware version of the phone, just seems it's disappearing a lot last couple of days.
hboot 1.54 has firmware 2.24.xxx.x, so one of the roms I linked will hopefully get you s-off using rumrunner
Click to expand...
Click to collapse
Ok.
So I need to push and flash the ROM on TRWP, boot on it and a screen will appear with "WIPE" then "ROOT" and unselect stock recovery ?
Thanks.
NB: When I try to do a Factory Reset in TRWP, it fails with an "Unable to mount cache" error message.
NB1: Can't flash the ROM you gave me. Since I did an "Format Data" wich removes datas & encryption on internal storage, I can't flash anything...
NB2: OK I can't mount /data, /sdcard either...
samih7 said:
Ok.
So I need to push and flash the ROM on TRWP, boot on it and a screen will appear with "WIPE" then "ROOT" and unselect stock recovery ?
Thanks.
NB: When I try to do a Factory Reset in TRWP, it fails with an "Unable to mount cache" error message.
NB1: Can't flash the ROM you gave me. Since I did an "Format Data" wich removes datas & encryption on internal storage, I can't flash anything...
Click to expand...
Click to collapse
say what?
unable to mount cache is OK, probably because of the fastboot erase cache
if push dosn't work , sideload it: http://forum.xda-developers.com/showthread.php?t=2317986
nkk71 said:
say what?
unable to mount cache is OK, probably because of the fastboot erase cache
if push dosn't work , sideload it: http://forum.xda-developers.com/showthread.php?t=2317986
Click to expand...
Click to collapse
It's ok, I found an issue by formatting /data in CWM (I deleted TWRP)
The .8 ROM is installed but the fingertouch screen wasn't usable during the installation, I don't know if it means that's not a good version ?
--
Damn man you made my day, the ROM is installed and I can use my HTC again !
Is it the official RUU ?
But unfortunately it's still S-ON.
Thanks a lot
samih7 said:
It's ok, I found an issue by formatting /data in CMW (I deleted TRPW)
The .8 ROM is installed but the fingertouch screen wasn't usable during the installation, I don't know if it means that's not a good version ?
--
Damn man you made my day, the ROM is installed and I can use my HTC again !
Is it the official RUU ?
Click to expand...
Click to collapse
touchscreen wasnt working because you probably used 6.0.3.1, get the latest from here: http://forum.xda-developers.com/showthread.php?t=2173863 (though that one takes VERY long to backup/restore nandroids), so either get 6.0.3.2 or TWRP if you do nandroids frequently.
It's getting late for me, so have to sign off in a bit, and now that your phone is up and running, we can pick this up tomorrow....
you can try rumrunner now to get yourself s-off.
I'll check back tomorrow....
You can still hit the thanks button on my posts if i helped
nkk71 said:
touchscreen wasnt working because you probably used 6.0.3.1, get the latest from here: http://forum.xda-developers.com/showthread.php?t=2173863 (though that one takes VERY long to backup/restore nandroids), so either get 6.0.3.2 or TWRP if you do nandroids frequently.
It's getting late for me, so have to sign off in a bit, and now that your phone is up and running, we can pick this up tomorrow....
you can try rumrunner now to get yourself s-off.
I'll check back tomorrow....
You can still hit the thanks button on my posts if i helped
Click to expand...
Click to collapse
No problem, take your time. Thank you for helping me !!
I hit the "thanks" but it doesn't appear anything, is it normal ?
--
I red I didn't need to get myself S-OFF to install a Custom Rom, is it true ?
I'm trying to get the Google Edition ROM again... Without success.
I flash boot.img in fastboot (& make clear cache) + flash the ROM normally (wipe cache + dalvik cache) via TWRP but my device enter in a boot loop when I reboot after installation (I just see the Google language selection, just to make me more frustrated lol...). Same with CyanogenMod.
Root Checker says "Congratulations ! This device has root access" and I unlocked the bootloader so I don't understand...
Maybe because of the CID of my phone is from Orange Poland (ORANGB10) ? I maybe should get S-OFF & Debrand ?
Thanks for your answer.
Definitely do s-off if you can. It may save you if things go south..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
However you need unlocked bootloader + custom recovery to install custom ROMs. Not S-off.
SaHiLzZ said:
Definitely do s-off if you can. It may save you if things go south..
---------- Post added at 12:02 AM ---------- Previous post was at 12:01 AM ----------
However you need unlocked bootloader + custom recovery to install custom ROMs. Not S-off.
Click to expand...
Click to collapse
I finally got S-OFF and achieved to install the stock Google Edition 4.4 ROM with this thread : http://forum.xda-developers.com/showthread.php?t=2358781
I had to SuperCID (fastboot eom writecid 11111111) because changing the android-info.txt didn't work.
Could you tell me in which case is it useful to flash stock recovery (he says it's for future OTA's) ?
Does it mean I could do updates via Software Update in Android the menu ?
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Thank you.
samih7 said:
I finally got S-OFF and achieved to install the stock Google Edition 4.4 ROM with this thread : http://forum.xda-developers.com/showthread.php?t=2358781
I had to SuperCID (fastboot eom writecid 11111111) because changing the android-info.txt didn't work.
Could you tell me in which case is it useful to flash stock recovery (he says it's for future OTA's) ?
Does it mean I could do updates via Software Update in Android the menu ?
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Thank you.
Click to expand...
Click to collapse
NB: In the best case, I would like to get the updates via Android interface and have the most "official" Google Edition ROM (I don't want to change it, sooner or later).
Click to expand...
Click to collapse
I wouldn't , but that's your choice :laugh:
Anyway, I didn't read the thread you linked, but to get OTAs, you need "odexed stock rom", and "stock recovery" for OTAs to work properly,
you also need to change your CID (and possibly MID) to GPe
I think GPE CID is "GOOGL001" and MID is "PN0712000" (I THINK)
So if you're stock rom + stock recovery + correct CID & MID, you'll receive future OTAs just fine,
remember to keep S-Off.
if all good, would you mind editing the main thread title to include [SOLVED]. thanks
nkk71 said:
I wouldn't , but that's your choice :laugh:
Anyway, I didn't read the thread you linked, but to get OTAs, you need "odexed stock rom", and "stock recovery" for OTAs to work properly,
you also need to change your CID (and possibly MID) to GPe
I think GPE CID is "GOOGL001" and MID is "PN0712000" (I THINK)
So if you're stock rom + stock recovery + correct CID & MID, you'll receive future OTAs just fine,
remember to keep S-Off.
if all good, would you mind editing the main thread title to include [SOLVED]. thanks
Click to expand...
Click to collapse
Why wouldn't you ? :laugh: I like Google's refinement, don't you ?
How could I verify I'm in stock recovery ?
I flashed it, and now when I click on RECOVERY in BOOT LOADER, it doesn't enter in recovery anymore: get that little Android green toy down with a red triangle.
Ok fine.
samih7 said:
Why wouldn't you ? :laugh: I like Google's refinement, don't you ?
How could I verify I'm in stock recovery ?
I flashed it, and now when I click on RECOVERY in BOOT LOADER, it doesn't enter in recovery anymore: get that little Android green toy down with a red triangle.
Ok fine.
Click to expand...
Click to collapse
"get that little Android green toy down with a red triangle" -> yep, that's stock recovery :good::good:
if you simultaneously and briefly press POWER + VOLUP + VOLDOWN, you'll get to the stock recovery menu (really tiny font). you'll have to try a couple of times to get the timing correctly.
Hello everyone,
I'm pretty new to whole rooting and stuff so excuse me for my probably noob and dumb questions..
I own a HTC One for a year now I believe, and I wanted to give the rooting thing a try.
So I unlocked my One, and installed a custom recovery (TWRP).
I didn't do alot with it, had a stock version af android with sense, no custom roms or anything, only used root acces for the cerberus app.
The other day HTC released a new version af the stock software, I believe 4.19.401.11.
Since I'm not doing anything with the unlocked phone I want to get it back to stock again.
I am on android 4.4 with sense 5.5 now, android version 4.19.401.9, hboot 1.56
My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:-
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I found this guide to get back to stock: http://www.htc1guru.com/guides/return-stock-guide/
There it works with S-off, with rumrunner to get s-off but I read that rumrunner wont work with hboot 1.56, sadly I have 1.56..
In that guide you have to get s-off, downgrade to another hboot (1.44) and use a RUU with android version 1.28 or 1.29 to go to stock again.
But, in another topic I found this:
herwegan said:
@crushalot hey mate did you realize that there are now 4.19.xxx RUU's available on http://androidruu.com/?developer=M7# ?
for those who are interested: here's the link to the WWE 4.19.401.9 RUU
http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe
Click to expand...
Click to collapse
That is an RUU for exactly my phone I believe.
So now my question: Can I run that RUU, in the way that is written in the htc1guru return to stock guide (via fastboot) and go back to stock again? With a (re)locked bootloader, and receive OTA updates again?
I hope my question and all the information I have given is clear! If not feel free to ask me below!
Greetings.
N3Gruj1989 said:
Hello everyone,
I'm pretty new to whole rooting and stuff so excuse me for my probably noob and dumb questions..
I own a HTC One for a year now I believe, and I wanted to give the rooting thing a try.
So I unlocked my One, and installed a custom recovery (TWRP).
I didn't do alot with it, had a stock version af android with sense, no custom roms or anything, only used root acces for the cerberus app.
The other day HTC released a new version af the stock software, I believe 4.19.401.11.
Since I'm not doing anything with the unlocked phone I want to get it back to stock again.
I am on android 4.4 with sense 5.5 now, android version 4.19.401.9, hboot 1.56
My fastboot getvar all:
I found this guide to get back to stock: http://www.htc1guru.com/guides/return-stock-guide/
There it works with S-off, with rumrunner to get s-off but I read that rumrunner wont work with hboot 1.56, sadly I have 1.56..
In that guide you have to get s-off, downgrade to another hboot (1.44) and use a RUU with android version 1.28 or 1.29 to go to stock again.
But, in another topic I found this:
That is an RUU for exactly my phone I believe.
So now my question: Can I run that RUU, in the way that is written in the htc1guru return to stock guide (via fastboot) and go back to stock again? With a (re)locked bootloader, and receive OTA updates again?
I hope my question and all the information I have given is clear! If not feel free to ask me below!
Greetings.
Click to expand...
Click to collapse
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
mb_guy said:
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
Click to expand...
Click to collapse
Hi mb_guy, i have a twrp backup which i can restore, which could allow me to return to stock with superuser root access.
If i flash a stock recovery, will it remove my root access and receive future OTA? (if i am not mistaken, i tried flashing the stock recovery, and relocked the bootloader, but i just can't remove the superuser app :crying: )
Thanks.
below are my phone informations :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
mb_guy said:
You are still essentially stock, you will only need to flash the stock recovery from 4.19.401.9 , unfortunately I did a quick google and couldn't fine one. If you have the OTA or ruu you can extract the recovery.img to use. unlocked bootloader and root is fine. Then when the version .11 is released by your carrier you will be able to install.
Click to expand...
Click to collapse
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
N3Gruj1989 said:
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
Click to expand...
Click to collapse
You don't want rom.zip you want recovery.img it's likely in the firmware folder. You should be able to unroot from twrp. You can re lock the boot loader, but it will say relocked, I would just leave it unlocked.
N3Gruj1989 said:
I have found the RUU of 4.19.401.9 (it is in the link i posted in my opening post, from androidruu).
(http://androidruu.com/getdownload.p...10.38r.1157.04L_release_353069_signed_2-1.exe)
I found a guide to extract the rom.zip from a RUU file, but it wont work for me. Can someone extract the rom.zip file for me and upload it here?
Only flashing the recovery file sounds like loads easyer than the entire guide i found by htc1guru.
And what if i want to re-lock the bootloader and get rid of root? Can i do that too?
Click to expand...
Click to collapse
Ok it's easy
Retry run that ruu exe file goto temp folder in c-Windows- user- app data - local - temp find in some folders you will get it but it's not worth it as it's encrypted so next time you will ask how to decrypt it
So better Google HTC One stock recovery download it flash it
2 if you want unroot mostly super user or rooting apps have methods in their settings try them
3 locking boot loader is last step after recovery flash
Unlocked bootloader not prevent future OTA
So no need for relock bootloader
OTA need stock recovery + unmodified system
HTC One 1.56 S-Off MaximusHD 33
mb_guy said:
You don't want rom.zip you want recovery.img it's likely in the firmware folder. You should be able to unroot from twrp. You can re lock the boot loader, but it will say relocked, I would just leave it unlocked.
Click to expand...
Click to collapse
But the recovery.img file is in the rom.zip file correct?
So i have to extract the rom.zip file out of the RUU first to get the recovery.img out of the rom.zip file.
Or can it be done a much easyer way?
yatin kumar said:
Ok it's easy
Retry run that ruu exe file goto temp folder in c-Windows- user- app data - local - temp find in some folders you will get it but it's not worth it as it's encrypted so next time you will ask how to decrypt it
So better Google HTC One stock recovery download it flash it
2 if you want unroot mostly super user or rooting apps have methods in their settings try them
3 locking boot loader is last step after recovery flash
Unlocked bootloader not prevent future OTA
So no need for relock bootloader
OTA need stock recovery + unmodified system
HTC One 1.56 S-Off MaximusHD 33
Click to expand...
Click to collapse
I googled HTC One stock recovery, but i didn't find a recovery for my HTC One build version, or are all the recovery.img the same?
Because I need a recovery.img for the 4.19.401.9 HTC_E11 (NL) version.
N3Gruj1989 said:
But the recovery.img file is in the rom.zip file correct?
So i have to extract the rom.zip file out of the RUU first to get the recovery.img out of the rom.zip file.
Or can it be done a much easyer way?
Click to expand...
Click to collapse
You can't get the recovery from the rom.zip as the zip is encrypted.
I downloaded the 4.19.401.9 firmware.zip and extracted the recovery from it.
Here is the recovery : http://sourceforge.net/projects/htcone/files/Recovery/4.19.401.9/recovery.img/download
Now you have two options:
With the RUU that you have
1. relocked the bootloader
2. run the RUU to go back to stock
3. do the OTA
With the recovery only
1. fastboot flash the recovery
2. not necessary to remove the SuperSU (but you will lose root after OTA)
3. or remove root (open the SuperSU app, - settings - scroll down - select Full unroot if you think it's better to remove it before OTA
4. do the OTA
Remove root by flashing stock firmware
Hi guys, i did some searching and found this thread http://forum.xda-developers.com/showthread.php?t=1773659
according to this thread if i flash in stock firmware it will remove the root?
So my question is, if i restore my phone to the rooted stock state > relock the bootloader > flash in the stock firmware, in theory it should return the phone to stock state right? just to confirm if the above thread works for the HTC One
Thanks.
ckpv5 said:
You can't get the recovery from the rom.zip as the zip is encrypted.
I downloaded the 4.19.401.9 firmware.zip and extracted the recovery from it.
Here is the recovery : http://sourceforge.net/projects/htcone/files/Recovery/4.19.401.9/recovery.img/download
Now you have two options:
With the RUU that you have
1. relocked the bootloader
2. run the RUU to go back to stock
3. do the OTA
With the recovery only
1. fastboot flash the recovery
2. not necessary to remove the SuperSU (but you will lose root after OTA)
3. or remove root (open the SuperSU app, - settings - scroll down - select Full unroot if you think it's better to remove it before OTA
4. do the OTA
Click to expand...
Click to collapse
Thank you very much!
When I unlocked, rooted and installed the TWRP recovery I lost the stock flashlight app and calculator app and some others.
With the RUU i will get them back i think, with the other option, flashing recovery it wont return right? And after the OTA?
Is there any risk in running that RUU?
N3Gruj1989 said:
Thank you very much!
When I unlocked, rooted and installed the TWRP recovery I lost the stock flashlight app and calculator app and some others.
With the RUU i will get them back i think, with the other option, flashing recovery it wont return right? And after the OTA?
Is there any risk in running that RUU?
Click to expand...
Click to collapse
You should have said this earlier. When you lost the some apps that reside in data/preload folder means you don't already have a proper stock, OTA most probably will be a fail attempt.
Flashing the recovery alone cannot guarantee a successful OTA update due to those missing apps.
The best option that you have is run the RUU unless you can find any nandroid backup for the current ROM.
For me, I will choose to run the RUU as that is always the best option when it is the right RUU for your device.
Make a backup to PC all your storage content in case you lose them by running the RUU (but unlikely you will lose them)
With the RUU ... the procedure is :
1- in fastboot mode - relock the bootloader : run command fastboot oem lock
2- in fastboot mode - flash/run/double click the RUU; follow the updater instruction - next,update,bla,bla,bla until it finish
---------- Post added at 07:16 PM ---------- Previous post was at 07:13 PM ----------
SiaoNang said:
Hi guys, i did some searching and found this thread http://forum.xda-developers.com/showthread.php?t=1773659
according to this thread if i flash in stock firmware it will remove the root?
So my question is, if i restore my phone to the rooted stock state > relock the bootloader > flash in the stock firmware, in theory it should return the phone to stock state right? just to confirm if the above thread works for the HTC One
Thanks.
Click to expand...
Click to collapse
If it is the firmware.zip alone, no .. it won't remove your root app.
When people say stock firmware it is always mean stock ROM.
To remove root, just simply select Full unroot in SuperSU settings. (asumming your rooting app is SuperSU as shown in that thread).
Thanks everyone for their help!
Everything worked fine, I'm back to stock now and just updated the OTA !
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Torcidas1950 said:
PLEASE RESPOND
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
+ you need stock recovery, ota update will not flash using a custom recovery.
PLEASE SEARCH
Click to expand...
Click to collapse
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery. And how do I do that?
Torcidas1950 said:
So if I got you right, only thing that matters is that I have stock recovery instead of custom recovery.
Click to expand...
Click to collapse
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
And how do I do that?
Click to expand...
Click to collapse
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
iElvis said:
You should be fully stock, including recovery, before taking an OTA, except that you can (and should) stay s-off and unlocked. You may not even get the OTA otherwise.
Click to expand...
Click to collapse
alray said:
Well yes and no, it depend what you did with your phone, read the link I have posted above, will not write all again
flash stock recovery the same way you have flashed a custom one
Code:
fastboot flash recovery name_of_recovery.img
you need the recovery that match your present firmware #
Click to expand...
Click to collapse
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Torcidas1950 said:
So I think I have found the stock recovery needed for my device. Now there is a small problem, I have 2 stock recovery files for my device and I do not know wich one to choose because when I typed "fastboot getvar all" I didn't find any information at "version main", just blank space. How should I know wich one to pick?
Click to expand...
Click to collapse
post your "fastboot getvar all" (excluding IMEI and s/n)
nkk71 said:
post your "fastboot getvar all" (excluding IMEI and s/n)
Click to expand...
Click to collapse
Here it is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3894mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Torcidas1950 said:
Here it is:
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
nkk71 said:
did you change radio?
hboot 1.55 + MID + CID would indicate you are on 3.xx.502.x version
so i guess: http://d-h.st/D8F or http://d-h.st/6bH would be a suitable recovery, but you need to have your phone's ROM 100% stock
Click to expand...
Click to collapse
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
1- If you are 100% stock then Settings -> About should also show your correct version number
2- you rooted the phone, so that may or may not have changed some system files, so OTA may not work
3- once S-Off stay S-Off, my personal opinion
In my humble opinion, three choices really, when it comes to "modding" or not your phone:
A) stay stock and don't mess with it to get OTAs
B) you cannot achieve S-OFF (due to newer hboots, or device problems) -> fine live with an unlocked bootloader, and accept the fact that you cannot install OTAs .... you can however "download and install later" the OTA, then pull it to your phone, and use the signed firmware.zip in it
C) you can achieve S-OFF and want to mod your phone -> then do it, get S-Off and enjoy the freedom (but don't flash things not meant for your phone!! this goes for S-On too)
Of course you're going to say that "but S-Off is dangerous", it's a double edged sword... sometimes you are able save your phone thanks to S-Off, and sometimes you can brick it completely.
But then again, you can easily brick an S-On phone too (especially one that is modded), and much more difficult to save than an S-Off phone.
^^ All that is my personal opinion, and I'm not suggesting you S-Off, but if you want to mod your phone (whether S-On or S-Off), you need to be aware of what may, or may not, go wrong, and have done some reading and research
Good Luck
Well, its not worth it. I wont risk bricking my phone again
Torcidas1950 said:
Hi,
I have an HTC One PN07120. It is unlocked, tampered S-ON, has custom recovery installed, and is running AT&T 4.3 JellyBean stock.
In a few days Sense 6.0 OTA update will become available for my device, so I was wondering if I can just normally run the setup and update my system or I have to relock my device or something?
PLEASE RESPOND
Click to expand...
Click to collapse
Torcidas1950 said:
Well, the guy who fixed my phone from a bootloop and bricked state said he has done the s-off, found a suitable stock RUU and installed, then he put S-ON back and unlocked bootloader if I decide to do any mods in the future.
Click to expand...
Click to collapse
Torcidas1950 said:
Well, its not worth it. I wont risk bricking my phone again
Click to expand...
Click to collapse
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
nkk71 said:
Those are completely rhetorical highlights, so you can disregard :cyclops:
Good luck, enjoy, and let us know how the OTA update goes
Click to expand...
Click to collapse
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Torcidas1950 said:
I will if I eventualy decide to do it, so one last question: can I damage my phone in any way if I try flashing stock reckovery?
Thank you so much for all the information you have given me
Click to expand...
Click to collapse
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
nkk71 said:
That's a tough one... cause even if you manage to pull out the cable, at exactly the right (ie wrong) moment while flashing recovery, it wouldn't affect bootloader... and with a good bootloader (hboot, and some other variables) you should be able to revive your phone.... now mess with hboot, and that's a whole different story!!
As I said, this is my personal opinion, so maybe get some second opinions on the subject... I can only answer on what i've done, seen, experienced, fixed, not fixed, etc.
Maybe someone wiser will add his/her opinion to this
Click to expand...
Click to collapse
Well, I am not planing to unplug the cable haha.. well if someone else knows please tell, the update is coming soon so I would like to know, but if its risky, there is no way I'm doing it
Torcidas1950 said:
but if its risky, there is no way I'm doing it
Click to expand...
Click to collapse
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
nkk71 said:
I hope you have a sense of humour, so no offense meant, but... why did the chicken cross the street (and was it risky?)
Wish you all the best
nkk71
Click to expand...
Click to collapse
So, yesterday the OTA was finally released, and today I have flashed stock recovery... Now waiting for the OTA notification to come
Sent from my HTC One using XDA Free mobile app
hello guys,
i did a deep search, but nothing found about it, or found but did not understood, so i will ask you. if in my stock recovery it also says (TAMPER), will be possibly to instal OTA?
L.E. - rest is like the title of the topic - Unlocked, S-ON, tampered..
Last night I got a notification for a System Update to version 6.12.161.5.
Has anyone tried this yet? And any problems found?
With the last two updates over the last 3-4 months I have had major problems:
1. When VodaFone forced the Rich Communication Suite / Service upon us; abysmal battery performance and terrible instability problem with phone frequently crashing on incoming calls and texts - which I 'solved' by Disabling RCS.
2. When VodaFone pushed the next update that greyed out the box to Disable RCS (they appeared to fix the instability and battery drain problem, but now I don't even have the option to disable RCS).
After lots of self-help and web searching I now have a stable phone with decent battery life again, and given those past painful experiences I am somewhat reluctant to blindly update.
Has anyone tried this Update yet, and can you comment after a few days of usage, particuarly on stability and battery usage?
Thanks
David
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Pilch2k said:
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Click to expand...
Click to collapse
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
daveingram said:
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
Click to expand...
Click to collapse
To be honest i've not noticed any issues yet, or any changes!
needed Ota file 6.12.161.8
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Seymour2002 said:
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Click to expand...
Click to collapse
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Flash firmware from OTA...
alray said:
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Click to expand...
Click to collapse
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823; but probably I'm wrong...
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Seymour2002 said:
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823;
Click to expand...
Click to collapse
Dont know what you are referring to.
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Click to expand...
Click to collapse
Unfortunately, there is not much files for that CID.
I don't understand what you want to attempt with an OTA file. Firmware included in OTA are not complete, it only contain files to be updated in an incremental way. If you manually flash a firmware from an OTA updates and you do it over the wrong version (currently installed on your phone) this could end with a bricked phone (hardbrick)
Flashing the entire OTA zip file will not help either. OTA files are patches that must be installed over a working rom and proper rom version. It also must be flashed using the "software update" option within the OS (unless the phone is s-off)
what you should do imo, is to start over fresh, flash twrp recovery 2.6.3.3 and flash a "close to stock" rom
Flash firmware from OTA...
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37WW904203
(bootloader) imei: 357864057367987
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Seymour2002 said:
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Click to expand...
Click to collapse
how did you manage s-on + locked bootloader + no recovery ?
was this phone converted to DE or GPE at one time ?
Flash firmware from OTA...
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Seymour2002 said:
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Click to expand...
Click to collapse
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ?
followed by fastboot reboot-bootloader ?
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Flash firmware from OTA...
clsA said:
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ? Yes, several times...
followed by fastboot reboot-bootloader ? Yes....
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Click to expand...
Click to collapse
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Seymour2002 said:
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Click to expand...
Click to collapse
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Flash firmware from OTA...
clsA said:
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Click to expand...
Click to collapse
Once I select recovery from the bootloader menu and I press power button the phone reboots the bootloader...
SOLVED! Unbrikked THC ONE M/!!!!!
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Seymour2002 said:
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
Glad you got your phone revived :good:
since a phone is S-On there's no risk to flash a wrong firmware
Click to expand...
Click to collapse
The risk is there, if you flash a firmware patch (ota firmware) over the wrong version (i.e 5.xx.xxx.x over 3.xx.xxx.x), this could brick. Happened many times that's why its mentioned in some threads. There is no risk flashing the same version like you did