Hi
I have been trying for a day now to try and recover my device after trying to get it back to stock (having had it rooted, s-off, custom rom etc)
The phone is currently stuck on the grey dotted screen when I reboot the device holding either volume key. Without holding down the volume buttons, the device is not recognized by windows and shows as QHUSB_DLOAD.
The fastboot getvar-all command gives me the following:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.206.11
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: FAXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3822mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The last thing I was able to do (perhaps a bad idea?) was follow the guide on this thread as I was trying to change the version to match an OTA I had downloaded. http://forum.xda-developers.com/showthread.php?t=2322820
I think that if I could find an RUU for 1.29.206.11 (O2 UK), that might run. I did try running an RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe) and it seemed to fail on the version number.
Any advice anyone can give me on how to recover this appreciated. The annoying thing is that the device had a fault (microphone) and I thought, having figured my way through rooting and installing custom roms on multiple Samsung and HTC devices, that I could get the device back to factory to avoid any questions on the warranty....and this is the first time I am having to admit defeat and think I may well have completely bricked the device!
Many thanks in advance!
Gavin
In order to run a different RUU, you would need to change CID to 11111111, AND fastboot oem lock - to relock the bootloader. I don't know the correct RUU for your carrier or country, but changing cid and relocking bootloader does have to happen first
Sent from my HTC One using XDA Premium 4 mobile app
Just whatever you do, DO NOT switch to S-on until your completely sure you have finished the revert. You probably will brick it at that point.
You mention the grey screen, have you followed the instructions on that thread pertaining to the grey screen?
Sent from my Nexus 10 using Tapatalk 4
born_fisherman said:
In order to run a different RUU, you would need to change CID to 11111111, AND fastboot oem lock - to relock the bootloader. I don't know the correct RUU for your carrier or country, but changing cid and relocking bootloader does have to happen first
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi
I have made some progress with the RUU file I have which seemed to restore a few things but ultimately failed to restore the phone. I now have the regular bootloader screen back, and also have managed to flash a recovery image (although cannot see the phone from my PC to push an rom out to it).
I am now not sure of the best way to make progress from here - if I change the CID to 11111111 and relock the bootloader, can I install an RUU with a different version number? I had tried using the method I used previously to upload a zip file (with the same CID as it's correct already) but just changing the version number but I am getting an android 24 fail when I try to 'fastboot oem reboot ruu' then 'fastboot flash zip xxxxx.zip'.
Many thanks again for the help....maybe there's some light at the end of the tunnel here!
Cheers,
Gavin
Flashboot oem rebootRUU (no space between reboot and RUU)
Yes changing CID and relock bootloader will allow you to flash a different RUU (but try to find the closest matching to your carrier/country)
What is the reason you are doing 'fastboot flash zip'? For firmware? I wouldn't change firmware at this time
Sent from my HTC One using XDA Premium 4 mobile app
altimax98 said:
Just whatever you do, DO NOT switch to S-on until your completely sure you have finished the revert. You probably will brick it at that point.
You mention the grey screen, have you followed the instructions on that thread pertaining to the grey screen?
Sent from my Nexus 10 using Tapatalk 4
Click to expand...
Click to collapse
Hi - definitely staying away from any changes related to S-OFF!
On the instructions related to grey screen, it said that was normal and just to issue the commands then run the RUU file. That's my missing piece here I think - the lack of an RUU with the right version number (unless I am missing something).
born_fisherman said:
Flashboot oem rebootRUU (no space between reboot and RUU)
Yes changing CID and relock bootloader will allow you to flash a different RUU (but try to find the closest matching to your carrier/country)
What is the reason you are doing 'fastboot flash zip'? For firmware? I wouldn't change firmware at this time
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi - I was following the first few steps on this thread (http://forum.xda-developers.com/showthread.php?t=2322820) which allow the change of CID and MID, as well as the mainver (which was the variable I thought needed changed so I could run the RUU I had), by uploading the zip. I'm trying the RUU again but will first change CID and relock the bootloader. Thanks
I would look at this guide http://forum.xda-developers.com/showthread.php?t=2281365
for restoring to stock - there is another thread titled 'easily go back to stock 100%' or something like that that is helpful as well
Sent from my HTC One using XDA Premium 4 mobile app
born_fisherman said:
I would look at this guide http://forum.xda-developers.com/showthread.php?t=2281365
for restoring to stock - there is another thread titled 'easily go back to stock 100%' or something like that that is helpful as well
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am running into error code 155 on the ruu utility having changed the CID and relocked the bootloader. Any advice here appreciated!
Thanks again for the help - giving up for tonight!
When in hboot, it says 'locked' at the top?
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:36 PM ----------
I'm wondering if the bootloader is corrupt. After looking at the OP, I remember seeing that drive recognition elsewhere (qhusb_dload)
Sent from my HTC One using XDA Premium 4 mobile app
born_fisherman said:
When in hboot, it says 'locked' at the top?
Sent from my HTC One using XDA Premium 4 mobile app
---------- Post added at 07:58 PM ---------- Previous post was at 07:36 PM ----------
I'm wondering if the bootloader is corrupt. After looking at the OP, I remember seeing that drive recognition elsewhere (qhusb_dload)
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
In HBOOT it says relocked.
And I believe the qhusb issue is resolved. When I run the RUU, the ROM is sent across to the device successfully. The bootloader and recovery I believe were successfully written. The RUU seems to be crashing when waiting for the device to restart after that. I have tried manually restarting which worked the first time the RUU is trying to restart the phone, but seem to have not much time to do this before the install fails.
One suggestion a guy at work had was that I sideload a zip file in recovery.
Would that work? And although I know I can find complete custom roms in a zip format, I'm keen to get the phone to stock format but guessing the sideloading of an OTA file wont work (and dont think I can do much with an RUU file). Am I best to get any custom rom across then follow the guide suggested earlier in this thread to return to stock, or should I be doing something else?
Again, really appreciate any help here!
Can you get to recovery?
Sent from my HTC One using XDA Premium 4 mobile app
Hi
I am able to get into recovery and was able to sideload a custom ROM. Based on the this thread (http://forum.xda-developers.com/showthread.php?t=2425143) I was really hopeful that I did not actually have a hardware issue and that upgrading to 4.3 would resolve the issue that was described identically to my original issue.
So I have a fully functioning phone which I am going to follow the suggested guide to restore to stock, then return to the store.
Many thanks for the help in getting this issue resolved!
Gavin
Glad to hear it's working now!
Sent from my HTC One using XDA Premium 4 mobile app
Related
Hi,
I am on Vodafone Germany. I have to send my Phone for repair. I need to unroot and get rid sign of TAMPERED.
I have read that i need to install RUU at the end. I have not able to find VODA Fone CID VODAP102 RUU.
I have install CWM and the back of CWM Nandroid Backup / CID VODAP102 / 1.29.161.7 but I am not able to get rid of TAMPERED message.
Kindly help and point me to right RUU.
Regards
Zeeshan
any body`? any idea ?
Tampered means you have a custom recovery installed. If you install the stock HTC One recovery, that tampered sign is supposed to go away.
http://forum.xda-developers.com/showthread.php?p=38504123
Just flash the stock recovery in fastboot and update us with the result.
All the RUUs available are found here:
http://forum.xda-developers.com/showthread.php?t=2207874
I'd be lying if I said I know which one you're supposed to install, sorry.
do s-off with supercid and you can install any ruu then you can relock bootloader and s-on and it wont say relocked on bootloader screen just dont mess with h-boot and s-on you will brick
Even after installing Stock Recovery, it still says TEMPERED.
If lock the bootloader it say Relocked otherwise unlocked.
If i change CID then It will be no longer Vodp102 ??
What to do next
That is more info
(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.161.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35EW902807
(bootloader) imei: 354436052324686
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4046mV
(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.049s
you can change cid back. just use a ruu that has the same version that is available for your phone now
(bootloader) version-main: 1.29.161.16 this is what you should look for as far as the ruu
skinsfanbdh said:
you can change cid back. just use a ruu that has the same version that is available for your phone now
(bootloader) version-main: 1.29.161.16 this is what you should look for as far as the ruu
Click to expand...
Click to collapse
So if i get you correctly,
I Change CID to SUPERCID
then I can install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
and then after installation my phone will be like complete FACTORY RESET with everything like not TEMPERED or RELOCKED etc ??
After that without root, i can still change CID ??
herzlich said:
So if i get you correctly,
I Change CID to SUPERCID
then I can install this RUU
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13. 3231.27_10.31.1131.05_release_310878_signed.exe
and then after installation my phone will be like complete FACTORY RESET with everything like not TEMPERED or RELOCKED etc ??
After that without root, i can still change CID ??
Click to expand...
Click to collapse
you will still be s-off so yes you can change cid back and yes you can use commands to lock bootloader and it will say locked and same thing for tampered.
skinsfanbdh said:
you can change cid back. just use a ruu that has the same version that is available for your phone now
(bootloader) version-main: 1.29.161.16 this is what you should look for as far as the ruu
Click to expand...
Click to collapse
As I was now trying to download RUU but there is none for 1.29.161.16 .
Any idea now ?
herzlich said:
As I was now trying to download RUU but there is none for 1.29.161.16 .
Any idea now ?
Click to expand...
Click to collapse
just download the closest one if there isnt one for your carrier then thats the best you can do. unless you can find a nandriod from vadafone or whatever carrier you have
You could try to install a Nandroid back up of a Vodafone Germany Firmware
http://www.handy-faq.de/forum/htc_o...rom_wiederherstellen_via_nandroid_backup.html
Scrolling down a little there is a link to the Vodafone Nandroid Back Up 1.29.....
You find all Info you need, German Forum with several active xda members there.
After that you can flash the stock recovery, lock the bootliader and then S-on, if I am not mistaken.
Good luck
Sent from my HTC One using xda premium
hardstuffmuc said:
You could try to install a Nandroid back up of a Vodafone Germany Firmware.
http://www.handy-faq.de/forum/showthread.php?t=
Here you find all Info you need, German Forum with several active xda members there.
After that you can flash the stock recovery, lock the bootliader and then S-on, if I am not mistaken.
Good luck
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
im pretty sure that will work. why exactly are you going back to stock. if you dont mind me asking
I just had to change the link to the correct thread in that forum, sorry for confusion.
Correct one again:
http://www.handy-faq.de/forum/htc_o...rom_wiederherstellen_via_nandroid_backup.html
Sent from my HTC One using xda premium
skinsfanbdh said:
im pretty sure that will work. why exactly are you going back to stock. if you dont mind me asking
Click to expand...
Click to collapse
I am having HISSING sound on 3G/UMTS/4G connections. on GPRS or GSM it works fine.
Vodafone will replace the set. For that I need to undo all these stuff.
I have tried that backup with CWM. I will try from German Forum now , let see.
herzlich said:
I am having HISSING sound on 3G/UMTS/4G connections. on GPRS or GSM it works fine.
Vodafone will replace the set. For that I need to undo all these stuff.
I have tried that backup with CWM. I will try from German Forum now , let see.
Click to expand...
Click to collapse
what rom are you on?
skinsfanbdh said:
what rom are you on?
Click to expand...
Click to collapse
I am not using any custom rom. I just rooted my phone and CWM touch recovery rest everything is default. So it is Stock customized version of Vodafone.
Then you should try first with a Custom ROM. See if that takes care of the hissing.
Try for example InsertCoin 1.0.8
http://forum.xda-developers.com/showthread.php?t=2279766
Do first Nandroid Backup of your current rooted stock Vodafone ROM, then flash IC 1.0.8 (that definitely has no hissing and is also based on 1.29 so no hassle with SDcard backing up and moving stuff around which you have to do with a ROM based on 2.17)
Then you know for sure!
Sent from my HTC One using xda premium
hardstuffmuc said:
Then you should try first with a Custom ROM. See if that takes care of the hissing.
Try for example InsertCoin 1.0.8
http://forum.xda-developers.com/showthread.php?t=2279766
Do first Nandroid Backup of your current rooted stock Vodafone ROM, then flash IC 1.0.8 (that definitely has no hissing and is also based on 1.29 so no hassle with SDcard backing up and moving stuff around which you have to do with a ROM based on 2.17)
Then you know for sure!
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Is there an easy way to do Nandroid backup other then this
http://forum.xda-developers.com/showthread.php?t=1818321 ???
I want to try the ROM you suggested.
Yes, of course!
Have the .zip of the InsertCoin 1.0.8 on your SDcard.
Boot up into your recovery, either CWM or TWRP, and select BackUp, then let it run, takes a few minutes.
Then do a factory reset/wipe cache, select then Install zip from SDcard, choose InsertCoin.zip and follow the instructions.
Use vol +/- and Power Buttons in Aroma Installer rather than touchscreen as Aroma freezing issues. Then finally boot up and see if you still have the hissing.
Sent from my HTC One using xda premium
---------- Post added at 06:57 AM ---------- Previous post was at 06:52 AM ----------
herzlich said:
Is there an easy way to do Nandroid backup other then this
http://forum.xda-developers.com/showthread.php?t=1818321 ???
I want to try the ROM you suggested.
Click to expand...
Click to collapse
Just a Nandroid on your fone within your recovery is fine. The instructions in that thread there needs some adb knowledge.
After you did a nandroid (= back up) you can copy it to your computer. Takes only a few moments
Sent from my HTC One using xda premium
Can someone please tell me how to get there safely?(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.26.502.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT35ZW900606
(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: 3901mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.096s
I don't see any stickies. i'm sure I can search, but i'm scared to death of following the wrong one and bricking this phone.
Bump?
Sent from my HTC One using xda app-developers app
spark plugs. said:
Bump?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Here are all available RUU`s, OTA`s and CWM/TWRP firmwares http://forum.xda-developers.com/showthread.php?t=2207874. Hope you find something there. You have a AT&T device? Here is a TWRP flashable backup http://bugsylawson.com/files/file/1829-m7-twrp-nandroid-backup-cid-cws-001-12950210/.
Please remove imei from first post!
gee2012 said:
Here are all available RUU`s, OTA`s and CWM/TWRP firmwares http://forum.xda-developers.com/showthread.php?t=2207874. Hope you find something there. You have a AT&T device? Here is a TWRP flashable backup http://bugsylawson.com/files/file/1829-m7-twrp-nandroid-backup-cid-cws-001-12950210/.
Click to expand...
Click to collapse
Thanks. The last time i tried, it failed. I was told the error was due to model id mismatch. Should I be editing my phone's Model ID and CID or should I just edit the android.txt file?
gee2012 said:
Here are all available RUU`s, OTA`s and CWM/TWRP firmwares http://forum.xda-developers.com/showthread.php?t=2207874. Hope you find something there. You have a AT&T device? Here is a TWRP flashable backup http://bugsylawson.com/files/file/1829-m7-twrp-nandroid-backup-cid-cws-001-12950210/.
Click to expand...
Click to collapse
also, with the TWRP flashable backup, you're saying I could flash that then do OTA updates? would i have to re-lock bootloader? will I have to go s-on?
spark plugs. said:
also, with the TWRP flashable backup, you're saying I could flash that then do OTA updates? would i have to re-lock bootloader? will I have to go s-on?
Click to expand...
Click to collapse
After the flash you would have to flash the stock recovery for that RUU and do a factory reset afterwards to get OTA`s. Your phone will stil be flagged as a test device if you have S-Off and/or a unlocked bootloader (maybe there is a fix for that so look on XDA/Google for that).
I don't necessarily need OTA, just want the latest firmware
Sent from my HTC One using xda app-developers app
Bump for more info
Sent from my HTC One using xda app-developers app
spark plugs. said:
Bump for more info
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
What do you need to know?
To install the latest firmware, do I need stock RUU or can I just change CID to supercid?
Which firmware can I install with supercid?
What's the process for installing?
Sent from my HTC One using xda app-developers app
spark plugs. said:
To install the latest firmware, do I need stock RUU or can I just change CID to supercid?
Which firmware can I install with supercid?
What's the process for installing?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
1. Read this thread for unlocking the bootloader and getting S-Off http://forum.xda-developers.com/showthread.php?t=2314582.
2. Read this thread for writing supercid (11111111) http://forum.xda-developers.com/showthread.php?t=2317536
3. Choose a RUU from here and download it (do not extract it) http://forum.xda-developers.com/showthread.php?t=2207874 and flash the file by opening it as administrator and your phone usb connected in fastboot mode.
This is great. I'm s-off already. I don't need to change mid do I?
Sent from my HTC One using xda app-developers app
spark plugs. said:
This is great. I'm s-off already. I don't need to change mid do I?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, you don`t have to change the model ID.
great success. s-off, changed CID to 11111111, flashed firmware with this guide:
http://forum.xda-developers.com/showpost.php?p=42586614&postcount=25330
switched CID back. all is well.
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fastboot getvar all
(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: SH397
(bootloader) imei: 35585
(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: 4016mV
(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.045s
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>
Is there something wrong with my phone? anything missing i cant seem to find my (bootloader) version-main: in order to flash back stock rom. im s-on
and which RUU can i download?
http://www.androidruu.com/index.php?developer=M7
Judging by your CID your phone belongs to the WWE region. For the moment you can't flash any RUU.
If you still want to run an RUU do the following:
1.HTC-dev boot loader unlock
2.s-off
3.Downgrade hboot to 1.44.
4.Download 1.28.401.7 RUU and run it while on fastboot.
You can also lock the bootloader after you gain s-off
Sent from my HTC One using Tapatalk
Ivanovic said:
Judging by your CID your phone belongs to the WWE region. For the moment you can't flash any RUU.
If you still want to run an RUU do the following:
1.HTC-dev boot loader unlock
2.s-off
3.Downgrade hboot to 1.44.
4.Download 1.28.401.7 RUU and run it while on fastboot.
You can also lock the bootloader after you gain s-off
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. I cant seem to s-off using rumrunner for some reason, im pretty sure my fastboot works. I am able to flash custom recovery. However, it appears not to work error:adb. check usb debug. My usb debudding is on though.
Windows 7 or 8? Maybe you should try and install some other drivers!
P.S are you on custom Rom?
Sent from my HTC One using Tapatalk
Ivanovic said:
Windows 7 or 8? Maybe you should try and install some other drivers!
P.S are you on custom Rom?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
windows 8! I am able to flash custom recovery so my connection should be fine right?
I guess so. Btw I was wrong before. Just saw that your MID is not European and most probably is for the Australian variant. In that case 1.29.980.2 is for you
Sent from my HTC One using Tapatalk
Ivanovic said:
I guess so. Btw I was wrong before. Just saw that your MID is not European and most probably is for the Australian variant. In that case 1.29.980.2 is for you
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I'm not sure which variant. Its a singapore bought phone
Here is the correct RUU http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
Now for the adb thing. Try to reinstall drivers from the android development subforum just in case and try again. Are you using the command on fastboot or while the phone is in normal mode?
If this is not working then I guess it's better to flash a close to stock Rom like ARHD
Sent from my HTC One using Tapatalk
Ivanovic said:
Here is the correct RUU http://www.htc1guru.com/dld/ruu_m7_...0-13_10-33-1150-01_release_311678_signed-exe/
Now for the adb thing. Try to reinstall drivers from the android development subforum just in case and try again. Are you using the command on fastboot or while the phone is in normal mode?
If this is not working then I guess it's better to flash a close to stock Rom like ARHD
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i tried it in fastboot! alright i'll try downloading the ruu and see how it goes! thank you so much. Any idea why theres no main firmware version showing up?
From what i heard its not possible to flash a ruu while my phone is s-on is that true? If only i can get it to s-off arhhh.
Which Rom are you using ?
Sent from my HTC One using Tapatalk
Ivanovic said:
Which Rom are you using ?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
currently running sinless gpe 4.3.1. thought of going back to stock to update to latest firmware and all via ota first since i cant seem to be able to s-off.
For the s-off procedure it's better to flash a close to stock Rom like ARHD 31.0.
I believe that after that you will be able to s-off just fine!
Sent from my HTC One using Tapatalk
i've tried it twice last night :/ flashed arhd 31.6. Couldnt get rumrunner to work. turned off all security stuff,
http://www.htc1guru.com/downloads/stock-rom-downloads/
any idea which one i might be able to try flash? thank you
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
ERROR: run rumrunner again and READ (no adb connection to device. Debugging on?
Drivers?)
Press ENTER to exit
Try this http://d-h.st/23V and let me know.
Sent from my HTC One using Tapatalk
Ivanovic said:
Try this http://d-h.st/23V and let me know.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
I am running a windows 8 OS. Do i still try that?
Edit* tried it same results. I am able to get SH****** when i key in fastboot devices
Have the device in normal mode, open a command window and run "adb shell"
What do you get?
Sent from my HTC One using Tapatalk
Ivanovic said:
Have the device in normal mode, open a command window and run "adb shell"
What do you get?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>adb shell
error: device offline
D:\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>
o wait i had to accept something on my phone.
edit*
[email protected]:/ $
Try once again with a stockish Rom. It must work. There must be something broken regarding adb in that Rom you are using
Sent from my HTC One using Tapatalk
Ivanovic said:
Try once again with a stockish Rom. It must work. There must be something broken regarding adb in that Rom you are using
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
alright i'll reflash arhd 31.6 now and try adb shell again?
is there a reason why my phone doesnt display a main firmware?
Hello,
I have been posting in the AT&T HTC One area, but was directed to this area. My previous post is here: http://forum.xda-developers.com/showthread.php?t=2637302
My issue, it seems, is that my firmware and CID do not match, but my device is S-ON and relocked. Unfortunately, I cannot use the HTC method of unlocking my phone, since all I can get into is bootloader/fastboot. Is there any chance of getting this thing back to stock?
Have you tried fastboot oem unlock ?
SaHiLzZ said:
Have you tried fastboot oem unlock ?
Click to expand...
Click to collapse
Yes that simply yields the following message:
Code:
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.001s]
finished. total time: 0.001s
How did you unlock the first time around? This page says the unlock procedure is different for AT&T devices than the other HTC Ones.
fenstre said:
How did you unlock the first time around? This page says the unlock procedure is different for AT&T devices than the other HTC Ones.
Click to expand...
Click to collapse
When I originally unlocked it, I used the HTC official method, and it worked fine.
@codejunkie83 - In the original thread you mention converting to GPE which would be 3.62.1700.1, but your current firmware is 4.06.1540.2 dev edition. How did you get onto this firmware?
There is no 4.06.1540.2 RUU, but there is a 3.22.1540.1 to 4.06.1540.2 OTA that has signed firmware you should be able to flash in RUU mode with S-ON and locked bootloader. This might get things straightened out so that you'll be able to unlock bootloader. CID CWS__001 will work with this firmware.
Is it correct there is no OS loaded in /system ?
@cschmitt - I initially tried loading one of the guru reset roms, but I did not have touch screen capabilities. So, I found the 4.06.1540.2 firmware and flashed that - I think in error a site had that listed as AT&T, or I may have just misread. At any rate, I did not load an OS before turning S-ON and relocking - something I will definitely never forget to do again.
Do you have a link for that firmware? I will definitely give it a shot once I get home from work today.
The OTA is linked in this post. Open the OTA zip, and firmware.zip is there.
I'm not sure it will help, but won't hurt anything to try.
You might be stuck waiting for the AT&T KK update, they usually link an RUU on the HTC support site and if the version > 4.06 it should work.
Might also try contacting HTC and see if they can get you a 4.06.1540.2 RUU. There is an RUU, because they use it during repairs to refurbish devices, it's just not publicly released.
cschmitt said:
The OTA is linked in this post. Open the OTA zip, and firmware.zip is there.
I'm not sure it will help, but won't hurt anything to try.
You might be stuck waiting for the AT&T KK update, they usually link an RUU on the HTC support site and if the version > 4.06 it should work.
Might also try contacting HTC and see if they can get you a 4.06.1540.2 RUU. There is an RUU, because they use it during repairs to refurbish devices, it's just not publicly released.
Click to expand...
Click to collapse
Okay, thanks for the link. I'll give it a shot this afternoon, and if that doesn't work I'll just wait on the AT&T KK release - I believe that it is supposed to be out sometime soon. In the meanwhile I may attempt to contact HTC for that RUU. Thank you for your assistance - I'll report back my findings.
Okay, the firmware flashed correctly, but unfortunately I'm still in the same boat. I have sent an email to HTC, but I am not holding out much hope for that. I'll just keep waiting for a 4.06 RUU to magically appear.
So, a quick update on this (in case it helps anyone else in the same boat). I've spent the past few weeks going back and forth with HTC, who have been very responsive and helpful. Unfortunately, we came to the conclusion that I would need to send my phone in for repair. However, this was before the AT&T update was released.
So, along with this update, does anyone think flashing the AT&T firmware for 4.18 would help my situation, since I am currently on 4.06.1540.2? I think that it would flash ok, but not sure if I would be able to proceed at all after that, since I have no android installed.
codejunkie83 said:
So, a quick update on this (in case it helps anyone else in the same boat). I've spent the past few weeks going back and forth with HTC, who have been very responsive and helpful. Unfortunately, we came to the conclusion that I would need to send my phone in for repair. However, this was before the AT&T update was released.
So, along with this update, does anyone think flashing the AT&T firmware for 4.18 would help my situation, since I am currently on 4.06.1540.2? I think that it would flash ok, but not sure if I would be able to proceed at all after that, since I have no android installed.
Click to expand...
Click to collapse
Looks like someone tried it already. http://forum.xda-developers.com/showpost.php?p=50598383&postcount=71
Did not work for this user, unfortunately, you are welcome to try. You would need to download the ATT OTA for 4.4.2, extract firmware.zip and then run the following commands:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip (second time)
fastboot reboot-bootloader
and then unlock using HTC Dev..
Okay I will give it a shot when I get home, see what kind of results I get. Thanks!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Do post back your results!
---------- Post added at 04:44 PM ---------- Previous post was at 04:44 PM ----------
codejunkie83 said:
Okay I will give it a shot when I get home, see what kind of results I get. Thanks!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Do post back your results!
SaHiLzZ said:
Do post back your results!
---------- Post added at 04:44 PM ---------- Previous post was at 04:44 PM ----------
Do post back your results!
Click to expand...
Click to collapse
Alright, so quick update - I think I'm making progress! I downloaded the OTA file from this thread http://forum.xda-developers.com/showthread.php?t=2659374 and extracted the firmware.zip from it. I flashed that, and am finally back on an AT&T base version (4.18.502.7). So, from here, I am going to attempt to unlock again and get a custom recovery on it. Will update as I progress - if anything else comes to mind, let me know!
Also., for giggles/information, here is my getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(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: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
EDIT 2:
Okay, well, seems I'm still in the same boat - just on AT&T's version instead of dev edition. I'm still in contact with HTC, so hopefully I can get something worked out with them.
So htc Dev unlock didn't work?
Like @SaHiLzZ says, use the htcdev, there is a tuturial http://forum.xda-developers.com/showthread.php?t=1432199
spider84a said:
Like @SaHiLzZ says, use the htcdev, there is a tuturial http://forum.xda-developers.com/showthread.php?t=1432199
Click to expand...
Click to collapse
Unfortunately, it does not work. I get a successful message, but nothing happens on the phone. The next command I run on the phone (no matter what it is) gives an error message that custom splash could not be shown.
codejunkie83 said:
Unfortunately, it does not work. I get a successful message, but nothing happens on the phone. The next command I run on the phone (no matter what it is) gives an error message that custom splash could not be shown.
Click to expand...
Click to collapse
If you flashed the GPE Conversion RUU you will never be able to unlock via HTC Dev because that RUU writes sp1.img to mmcblk0p13 where the custom splash screen is stored and it's not the correct one for non-GPE devices such as AT&T, TMO, or the Developer Edition.
For these devices that have been converted to GPE they will always show something like:
Code:
[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read error!
when attempting to unlock the bootloader by flashing the unlock token.
Unfortunately, even flashing the correct firmware.zip for the device (such as the 4.18.502.7 firmware from the OTA) won't fix it because firmware zips generally do not include the splash screen files sp1.img or splash1.nb0; these are only included in a full RUU.
Only hope is to wait for a 4.18.502.7 signed RUU from HTC.
cschmitt said:
If you flashed the GPE Conversion RUU you will never be able to unlock via HTC Dev because that RUU writes sp1.img to mmcblk0p13 where the custom splash screen is stored and it's not the correct one for non-GPE devices such as AT&T, TMO, or the Developer Edition.
For these devices that have been converted to GPE they will always show something like:
Code:
[DISPLAY_ERR] sp_custom partition: sp_custom_img_hd read error!
when attempting to unlock the bootloader by flashing the unlock token.
Unfortunately, even flashing the correct firmware.zip for the device (such as the 4.18.502.7 firmware from the OTA) won't fix it because firmware zips generally do not include the splash screen files sp1.img or splash1.nb0; these are only included in a full RUU.
Only hope is to wait for a 4.18.502.7 signed RUU from HTC.
Click to expand...
Click to collapse
This totally makes sense, and answers a few of the questions I had in the back of my mind. I knew there had to be one little thing I was missing.
Funny that HTC never mentioned this, but then again...tech support, so yeah.
I'll just hang on for the RUU - thanks @cschmitt !
Hey there, I flashed a ROM and apparently it messed up my M7 Sprint I can't call or receive SMS, also I can't install apps even from OTG cable, I think this ROM is broken. Not sure if this is a hardware or software issue, I hope it's the latter. I can use the camera, WI-FI and play media files.
I have HBOOT 1.44 and my bootloader says TAMPERED and UNLOCKED.
How can I get back to stock from this stage? I'm super noob every bit of help will be appreciated
Dani84 said:
Hey there, I flashed a ROM and apparently it messed up my M7 Sprint I can't call or receive SMS, also I can't install apps even from OTG cable, I think this ROM is broken. Not sure if this is a hardware or software issue, I hope it's the latter. I can use the camera, WI-FI and play media files.
I have HBOOT 1.44 and my bootloader says TAMPERED and UNLOCKED.
How can I get back to stock from this stage? I'm super noob every bit of help will be appreciated
Click to expand...
Click to collapse
Ok so sounds like your having a rough time. I will try my best for you .
First of all some more information please. Boot you phone into the bootloader and connect fastbootusb. Then in your Fastboot command line type.
Code:
fastboot getvar all
And post the output here. Please edit out your serial no. And imei no.
what Rom did you flash and which recovery are you using? Did you clean flash i.e perform a full wipe before flashing, or Dirty flash i.e flash the Rom without wiping anything?
If the phones booting it can't of done anything to serious so let's hope this is an easy fix
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
uhm nothing, seems adb/fastboot is not working.
Im using Ubuntu 14.04... 64 bit.
p.s. in Windows 8.1 i connected it through this (Nocturnal ADB tool):
http://forum.xda-developers.com/showthread.php?t=2646453
I open the CMD and type adb devices and there it is HT35xxxxxxx. But when I type fastboot getvar all, it says waiting for device and is stuck there for 5+ minutes and nothing.
Dani84 said:
uhm nothing, seems adb/fastboot is not working.
Im using Ubuntu 14.04... 64 bit.
p.s. in Windows 8.1 i connected it through this (Nocturnal ADB tool):
http://forum.xda-developers.com/showthread.php?t=2646453
I open the CMD and type adb devices and there it is HT35xxxxxxx. But when I type fastboot getvar all, it says waiting for device and is stuck there for 5+ minutes and nothing.
Click to expand...
Click to collapse
Ah hA a Linux user nice to use Fastboot in linux all command must start sudo. So
sudo fastboot devices
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
Ah hA a Linux user nice to use Fastboot in linux all command must start sudo. So
sudo fastboot devices
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
Oh true!!! :victory:
[email protected]:~$ sudo fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3xxxxxx
(bootloader) imei: 35xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.042s
Dani84 said:
Oh true!!! :victory:
[email protected]:~$ sudo fastboot getvar all
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT3xxxxxx
(bootloader) imei: 35xxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.042s
Click to expand...
Click to collapse
Your phone does not appear to be a Sprint m7. As they have product I'd m7wls
Yours has m7_ul so it is international version. If you flashed a Sprint Rom that would certainly explain your problem. Luckily your s-on so shouldn't have done to much damage.
What Rom did you flash and which recovery are you using?
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
my recovery is TWRP 2.7.1.1
and the ROM is LiquidSmooth but it is horrible LOL and I can't flash new ROMs apparently.
how do I know if my ONE is sprint or at&t? I always assumed it was sprint as Im from Spain.
Dani84 said:
my recovery is TWRP 2.7.1.1
and the ROM is LiquidSmooth but it is horrible LOL and I can't flash new ROMs apparently.
how do I know if my ONE is sprint or at&t? I always assumed it was sprint as Im from Spain.
Click to expand...
Click to collapse
your phone is not Sprint or AT&T
you have
product: m7_ul <- this is a GSM with LTE
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP304 <- this says it's from Vodafone
So your looking for a RUU with VODAP in the CID ... all I see are some OTA files seems theirs no RUU
Dani84 said:
my recovery is TWRP 2.7.1.1
and the ROM is LiquidSmooth but it is horrible LOL and I can't flash new ROMs apparently.
how do I know if my ONE is sprint or at&t? I always assumed it was sprint as Im from Spain.
Click to expand...
Click to collapse
Your firmware also appears to be very old there is a reset zip i think will do the trick.
http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
This reset zip should return you to stock so you take ota updates, then you can update to official kitkat Rom and firmware.
Reroot the phone and install a international based Rom. Stay away from TWRP 2.7.1.1 though you'll notice in your getvar version main is blank. That's caused by TWRP 2.7.1.1. Stick with TWRP 2.6.3.3 to avoid this happening again.
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
Your firmware also appears to be very old there is a reset zip i think will do the trick.
Link to follow
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
k thanks so what to do? what link?
Dani84 said:
k thanks so what to do? what link?
Click to expand...
Click to collapse
See my edited post above
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
See my edited post above
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
downloading time = 2hours LOL, no problem I have time.
so I can flash that even when bootloader says TAMPERED and UNLOCKED? i want to be sure im not bricking my phone haha.
Dani84 said:
downloading time = 2hours LOL, no problem I have time.
so I can flash that even when bootloader says TAMPERED and UNLOCKED? i want to be sure im not bricking my phone haha.
Click to expand...
Click to collapse
Yes just flashes like a normal Rom from TWRP recovery, it will replace your custom recovery with stock and your Rom.
I think your firmware is probably still older than this reset.zip though. I'm not sure if that will cause a problem.
So you could also download this OTA extract the firmware from it and flash it manually to bring your firmware in line with the reset.zip
http://www.htc1guru.com/dld/ota_m7_..._p_release_325133_signedlqk8p6c09r7kmir2-zip/
That will require relocking the bootloader though but you can always unlock again after.
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Dani84 said:
downloading time = 2hours LOL, no problem I have time.
so I can flash that even when bootloader says TAMPERED and UNLOCKED? i want to be sure im not bricking my phone haha.
Click to expand...
Click to collapse
yeah the Guru_Reset requires unlocked bootloader and TWRP 2.6.3.3 custom recovery.
To take the over the air updates it's Important that you choose to install
stock recovery and say no to root in the guru reset Aroma installer.
Good luck !!
Thanks guys, both of you have been very kind and helpful I will try this and tell you tomorrow (its night in Spain).
@clsA do you know about the firmware will he need to update it to match the reset or will it still update ok as is ?
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Danny201281 said:
@clsA do you know about the firmware will he need to update it to match the reset or will it still update ok as is ?
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
Click to expand...
Click to collapse
The firmware may indeed need updated but I'm not positive
Dani84 said:
Thanks guys, both of you have been very kind and helpful I will try this and tell you tomorrow (its night in Spain).
Click to expand...
Click to collapse
clsA said:
The firmware may indeed need updated but I'm not positive
Click to expand...
Click to collapse
Probably best to do it then in that case, better safe than sorry thanks.
Ok so hopefully this will tell you everything you need.
Download the ota file as well. Then open it on your pc and extract the firmware.zip from it and place it in your Fastboot folder. Then follow this small guide I put together.
Ok so the plan is to upgrade your software to complete Stock 2.24.161.1, Rom, recovery and firmware will all be on the same os version and unmolested stock condition. After which you will be able to update you phone with official ota updates.
Prepare the files, your pc and phone for the procedure. Rename the 2.24.161.1.zip to firmware.zip and place it in your Fastboot folder on your pc. Connect your phone to mass storage with usb and copy the reset.zip to your internal storage/sdcard.
Ok let's get started. Reboot your phone into recovery. And flash the reset.zip just like installing a custom Rom. Select install and choose the reset.zip. Once it's done your Rom, recovery and radio will be back to stock. (if you choose to install the radio, it's optional at this stage as it will be done with the firmware anyway.
Now we need to upgrade the firmware since the OTA update will expect to find version 2.24.161.1 but your firmware is older than that so the OTA may fail to install.
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
Code:
fastboot oem lock
Code:
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
<--- case sensitive.
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
You should now see your new firmware version 2.24.161.1 in the bootloader. And that's it
Reboot the phone and complete the Rom setup. You should start getting notifications for OTA updates almost immediately. If not just go to settings>about and check for updates to force it. Take all the OTA's up to the latest and you're done
Completely stock software. If you decide to reroot make a nandroid of the Stock Rom before you root it. And copy it to your pc. This way you can return to stock easily for future OTA updates
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk
It worked!!!!!!
Now im running my stock HTC One again. Such a lame Vodafone ROM with tons of bloatware but at least the phone is alive and Im happy with that.
tbh Im now scared of flashing a new ROM, i would like the android revolution or one of those flashy roms but I think im gonna wait some days before making a decission lol. Thanks everyone
Dani84 said:
It worked!!!!!!
Now im running my stock HTC One again. Such a lame Vodafone ROM with tons of bloatware but at least the phone is alive and Im happy with that.
tbh Im now scared of flashing a new ROM, i would like the android revolution or one of those flashy roms but I think im gonna wait some days before making a decission lol. Thanks everyone
Click to expand...
Click to collapse
Well done m8, glad you got it sorted. You shouldn't be scared of flashing a new Rom though. The only thing that went wrong last time was you flashed a Rom for a different version of the M7.
As long as you stick with m7_ul roms you'll be fine but it's understandable you would want to take some time to process what happened. It's never fun thinking you bricked an expensive device such as the HTC one.
If you ever decide you want to try a Rom feel free to pm me for some guidance. For now relax and enjoy your working phone :highfive:
---------- Post added at 05:22 PM ---------- Previous post was at 05:01 PM ----------
@Dani84 Hi m8 just seen your PM. Yeah ARHD is a good place to start, it's quite close to stock but with xposed support and sense 6 toolbox.
Very smooth reliable Rom with no major bugs that I know of. I've been using ARHD since version 43 and I just love it. Version 80.0 is on the Horizon (Android 4.4.3).
I think I warned you already about twrp but just incase make sure to flash twrp 2.6.3.3 to preserve your os information.
Download the Rom and drop it on your sd card. Reboot to recovery and flash the Rom from the install menu in twrp. Make sure to do a full data wipe in the aroma installer as your changing from stock to custom Rom.
Sent from my HTC One M7 ARHD 71.1 (Minus Purple tint) using TapaTalk