I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
bavman said:
I used to have a custom rom on my phone but I tried to wipe it and im not sure what happened but I don't think there's an OS on there anymore. It gets stuck on the HTC white screen. I am able to access fastboot and I have TWRP recovery installed that I'm able to access, but I believe it's an older version. I tried just downloading another rom and flashing it but it still wont boot. I'm not sure what I need to get it working again.
Click to expand...
Click to collapse
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
DavidYouKnow? said:
First, what ROM you tried to install?
Tell me your current Firmware Version and CID (look in Bootloader).
Click to expand...
Click to collapse
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup: https://mega.nz/#!mYxDWApA!JbdLZAhYkz8fas5MpPfOQqGScikCLCmG21KBsjRJKQQ
Then use latest twrp recovery 3.0.2-0: https://dl.twrp.me/m8/twrp-3.0.2-0-m8.img.html and install it.
Here is the Stock Recovery that you need later: https://mega.nz/#!SUATBBbQ!-IUlr_tqnpkYFUM0bedRSRH3w__nCZjEAYls-5zncX4.
Then do this taken from this page: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860.
The basic idea is : fastboot flash recovery NameOfRecovery.img
2. Download TWRP backup - link in post #2 & post #3
3. Download stock recovery - link in post #4
4. Extract the downloaded x.xx.xxx.x_ckpv5.zip on PC
5. Boot to TWRP recovery and make a backup of boot only, this is to see where the backup goes on your device.
6(a). Reboot, connect device to PC then
open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
open SD Card - TWRP/BACKUPS/SerialNo./ (if backup is set to MicroSD)
6(b). For those with no OS, connect device to PC. In TWRP recovery go to mount, make sure MTP is enabled.
Then you can open Internal Storage - TWRP/BACKUPS/SerialNo./ (if backup is set to internal storage)
7. Transfer the extracted x.xx.xxx.x folder (not x.xx.xxx.x_ckpv5 folder) and its content to the backup path on your device, so it looks like this :
TWRP/BACKUPS/SerialNo./x.xx.xxx.x
8. Reboot to TWRP, wipe your device - in TWRP go to wipe - advance - select dalvik cache, cache, data, system (only these)
9. Restore the transferred backup - make sure all boot, data & system are ticked - swipe to restore
10. In reboot menu select bootloader (when TWRP asks whether you want to root your device, select do not install)
11. fastboot flash stock recovery that you downloaded - command fastboot flash recovery x.xxx.xx.x_recovery.img
12. reboot - check for OTA, download, install
13. you may have multiple OTA when your device currently on a lower version
14. done
If you want to flash TWRP again, use the latest TWRP after last OTA
NOTE : There is no need to relock bootloader when doing the nandroid way to revert to stock and do OTA.
Click to expand...
Click to collapse
..............................................................................
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
First download this TWRP Stock Nandroid Backup:
********
And then install the twrp recovery and your custom ROM, tell me what ROM you want to install ?
Click to expand...
Click to collapse
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
bavman said:
CID is T-MOB010
I don't know how to get my firmware #. Is it the version-main? Because that's empty.
Here is my getvar all if that is helpfull:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.14.21331931.LA02_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B13000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 0a41237a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
DavidYouKnow? said:
Yes your Firmware is the version-main and its empty, thats crappy.
Click to expand...
Click to collapse
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
redpoint73 said:
Hboot 3.16 means OP is on 1.xx firmware.
Which also means the nandroid and stock recovery you suggested are off by 3 versions (4.xx). Are you guessing at the version number?
ckpv5 has the best route. RUU will update the firmware, and get the phone back up and running.
Click to expand...
Click to collapse
No i didnt guessing at the version number, i thought that he have a higher Firmware version. Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
ckpv5 said:
These won't work for his device because his current firmware is too low.
---------- Post added at 05:45 PM ---------- Previous post was at 05:31 PM ----------
You won't be able to run current ROMs because your firmware is too low version.
What you can do is run the latest RUU to get back to stock at Marshmallow firmware then reinstall TWRP to install any custom ROM that you like
1. You need these drivers - http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
2. You need to relock bootloader because your device is S-On, use command
fastboot oem lock
fastboot reboot-bootloader
3. You need to install htc signed 6.20.531.5 firmware
Download :
https://mega.nz/#!yIhBTRKJ!5rZldUEzCaFqYUhomn4mO_IgA_-nW6-gV9HX5LCzT5Y
run commands
fastboot oem rebootRUU
fastboot flash zip fw_6.20.531.5.zip
you'll see error : FAILED
repeat fastboot flash zip fw_6.20.531.5.zip
fastboot reboot-bootloader
4. You need to install the latest 6.20.531.5 RUU
Download : http://www.htc.com/us/support/htc-one-m8-t-mobile/news/
right click the RUU.exe and select run as administrator, follow the instructions - agree/accept, next,next,update,blablabla until it finish.
Now you'll have a out of the box state device.
You can unlock the bootloader again with the unlock_code.bin
Re install TWRP - use the latest TWRP 3.0.2-0
You can install any custom ROM that you like.
All the above procedure require you to put the device on bootloader/fastboot mode and connect to PC.
The above procedure will wipe everything in your device including internal storage data/files (if you want to backup first, install TWRP 2.8.1.0 and in recovery you can enable MTP after connect to PC to copy out files from Internal storage)
All these require you to have a Windows PC with USB2.0
Click to expand...
Click to collapse
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
bavman said:
Thanks for this information. I had tried to revert back to stock using that exact RUU from the HTC website but it would keep failing and I didn't know why. Using the stock firmware steps you included got it work. I appreciate the help.
Click to expand...
Click to collapse
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
---------- Post added at 09:43 AM ---------- Previous post was at 09:38 AM ----------
DavidYouKnow? said:
Im so sorry, i had the problem earlier also on my M7 and yes then i have taken a RUU too, but that was off by 1 version And i haven't the Problem on my M7 with a clear os display in bootloader.
Click to expand...
Click to collapse
Restoring by RUU versus nandroid are two completely different things, and you should be careful not to confuse the two:
RUU re-writes all partitions, including firmware, so there is no chance of a mismatch between firmware and ROM. Therefore, you don't need to match the RUU version to firmware, as long as the RUU is equal or greater number than the current firmware on the phone (no "downgrading" with s-on). And with s-off, this requirement is removed entirely, so you can run any version RUU that matches your CID, MID.
Restoring by nandroid is a completely different animal. Nandroid just contains the ROM and kernel. It needs to match the firmware on the phone, otherwise it won't work properly.
redpoint73 said:
If you had posted the RUU failure symptoms (Error number and message, if there was one; specific behavior and results, etc.) we could have helped there (and still be happy to, if you are at all curious about getting RUU to work). But it looks like you sorted it without RUU, anyway.
Click to expand...
Click to collapse
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
ckpv5 said:
I understand his post differently .. he managed to run RUU after firmware is flashed, a step his missed before (a needed step to run a MM RUU on lower firmware, but never told earlier).
Click to expand...
Click to collapse
Now I understand. Its confusing, since the 2 methods (both of which have you to credit) to return to stock are both referenced in this thread (another user references the nandroid method); and folks often use the term "firmware" incorrectly to refer to the ROM.
It also means that the user did not follow your instructions in Post #5 in the proper sequence. So RUU failing was inevitable, and easily avoidable; if they had followed your instructions in the proper order.
Related
Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.
redmapleleaf said:
Hi All,
I attempted to restore to the stock rom when I ran into this problem where my phone would only boot into recovery mode.
Currently I have S-on and the OS wiped out after a fail attempt at installing the zip file One_5.11.401.10_deodexed.zip
I thought that I might be able to recover it by running one of the RUU exe files but so far I have not been successful. I always got the error 155 returned. Also I am really unsure if this method would work and what RUU file is right for my device? Here is the information I got on my device, may be someone can point out what RUU I might need:
$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.27.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW54321
(bootloader) imei: 1234567890
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4174mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e02a9046
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.041s
I know that my phone is GSM, unlocked, and work with tmobile. However I am uncertain as to weather it was originally a tmobile phone or an ATT phone, or else.
Thank you for your help.
Click to expand...
Click to collapse
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.
Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
redmapleleaf said:
Update: I had an all nighter hellish time trying to recover the seeming bricked phone. At last the following procedure worked for me. I like to post it here just in case someone else got into the same problem. Note that I was using TWPR recovery.
1. I sideloaded superuser.zip
2. I side loaded revone to /sdcard/ directory
3. from the pc:
adb shell
cd /sdcard/
chmod 755 revone
./revone -s 0 -u
exit
4. reboot into fastboot and I got S-OFF
Next I was still having problem installing RUU zip file. The only thing that worked for me was this:
1. I changed the CID to 11111111, (not sure if this is necessary)
2. download Guru Reset M7 3.62.401.1.zip file from htc1guru.com
3. adb sideloaded Guru Reset M7 3.62.401.1.zip to /sdcard/ directory
4. using TWPR install zip to install Guru Reset M7 3.62.401.1.zip
5. the phone reboot and came back working.
At this point I still have S-OFF. The new ROM is of an older version so software update tried to download and install a newer version. However it wasn't able to install. There was a message telling me that it has detected an "variant version of the firmware was installed so update cannot continue". So I still have the following tasks to do before the phone is truly unrooted:
1. change CID from 11111111 back to what it was before
2. update to the latest stock firmware
3. change S-OFF to S-ON
the HTC boot is already in "locked" state so I don't need to lock it again. Still not sure how I can update to the latest stock firmware though. I would appreciate any information in this regard. Thanks.
Click to expand...
Click to collapse
Update: all problems are fixed, the phone is returned to its stock state completely. Here is what I did.
1. Change the CID to T-MOB010 by using "fastboot oem writecid T-MOB010
2. with CID=T-MOB010 and model number MID=PN0713000 I look up the RUU exe that support those two parameters and download it from htc1guru.com
3. down grade my hboot from 1.54 to 1.44 by flashing a hboot.zip file
4. put the phone in fastboot mode and run the RUU exe . After it is done the phone is back to stock rom.
That's it. Hope these steps could help some sorry soul out there. This HTC root/unroot is NOT FUN at all! If you happen to read this HTC, please make your bootloader idiot proof. Otherwise we will just go with your competitor whoever has a better bootloader.
redmapleleaf said:
Update: ok, I finally able to get the software update working without getting the ‘Variant System Version’ message. It worked after I change the CID back to Googl001 from 11111111. I did it with the fastboot command "fastboot oem writecid googl001" .
It seems that the only thing that I need to do now to return it to the original stock product is to change S-OFF to S-ON. Or may be not.
I am still not sure if I got the stock firmware or not though. This is because I saw that the phone has a "SuperSU Installer" app running. This app allow me to root the device. It would be odd if HTC would ship the phone with this app included.
So if you know for sure how I could return this phone to completely stock image, please let me know.
Thank you.
Click to expand...
Click to collapse
Hello everyone! glad to be a new member of this amazing community! I am a new member with a tough problem, would love if I get ideas on how to solve it.
So After flashing stock unrooted GPe rom as per the most common methods circulating around (changing CID, MID, S-Off, etc), I was thrilled to see the boot splash screen change into google's except that it keeps booting into the bootloader; for some reason I could not get into recovery either (but I flashed TWRP again and it works now)
So as it stands now I have the following:
S-Off
Unlocked
Software status: Official
Working TWRP (which keeps saying NO OS IS INSTALLED)
Unable to mount /data (whatever that means) + "error: closed" when attempting to sideload the RUU roms via ADB
I did not install any firmware or kernels
and whenever I try to boot the OS I get put back in bootloader over and over.
As far as im concerned this phone seems bricked for me, but im also new so I wouldn't know, having said that, I am open for the most radical of options and procedures to get this working.
Thank you all in advance!
Flash it again via adb, the flashing command must be executed twice.
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Megaliths said:
I get an error "E:Unable to mount '/Data'" as soon as I open up the sideload option. when attempting to sideload I get "error: closed". I am starting to sense I have a problem with my storage. what to do next?
Thank you so much for your reply!
Click to expand...
Click to collapse
That unrooted GPE was for dual sim? I see you have a dual sim.
Make a screenshot.
Details about the ROM would help.
Do a fastboot getvar all command also.
Actually I don't know if the Rom is for dual sim or not, I figured as long as I get CID and MID right it should fit? pardon my ignorance on the matter. ill post a screenshot as soon as possible!
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid:
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Megaliths said:
Getvar all:
C:\Users\Megalith\Desktop\One_M8_All-In-One_Kit_v\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.11.1700.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_dugl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B17000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c88f4560
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Click to expand...
Click to collapse
Delete the IMEI.
OP - Do you want it back to Sense?
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
EddyOS said:
OP - Do you want it back to Sense?
Click to expand...
Click to collapse
Come to think about it now, I'd rather go to stock now if it all possible.
Megaliths said:
I really prefer to get GPE working but sense is better than a bricked phone.
Also, thanks for the replies!
Click to expand...
Click to collapse
Megaliths said:
Come to think about it now, I'd rather go to stock now if it all possible.
Click to expand...
Click to collapse
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
EddyOS said:
OK. First things first, did the GPe ROM ever work? The reason I ask it was designed for the single-SIM M8 so don't know if it worked with the dual-SIM version. If not, we should be OK to get back to stock...
Click to expand...
Click to collapse
It never booted up correctly no. I'd love if you can help me go to stock with such a messed up state my phone had gotten into.
We should be able to sort things out, but I'll need to get to a proper PC and get links together
EddyOS said:
We should be able to sort things out, but I'll need to get to a proper PC and get links together
Click to expand...
Click to collapse
Thank you so much!
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
EddyOS said:
OK, this isn't particularly straight forward but should hopefully work...
Download the following files and place in your fastboot folder:
- Dual-SIM RUU - https://drive.google.com/file/d/0B17smFr95pleaW9iTFBiSUE2OVE/view?usp=sharing (rename to anything you want but I'd recommend ruu.zip, not ruu.zip.zip obviously!)
- htc_fastboot - https://www.androidfilehost.com/?fid=95897840722646249
- Sense FW - https://www.androidfilehost.com/?fid=23329332407589439 (again, rename to anything but I'd recommend firmware.zip)
1. First things first, boot into fastboot and set your CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader and confirm it's done - fastboot reboot-bootloader
3. Assuming it's done, boot the phone into RUU mode - fastboot oem rebootRUU
4. Once in RUU mode, flash the firmware package - fastboot flash zip firmware.zip
5. It'll fail the first time and reboot. Do the exact same command again once back in RUU mode - fastboot flash zip firmware.zip
6. Once finished, reboot back to the bootloader to confirm it's on the white 'Sense' version - fastboot reboot-bootloader
7. Assuming it's done, reboot into RUU mode again - fastboot oem rebootRUU
8. Now flash the RUU using the HTC fastboot version - htc_fastboot flash zip ruu.zip
9. This will go through a few passes but once finished reboot to the bootloader - fastboot reboot-bootloader
10. Once back at the bootloader, disconnect the phone and go into stock recovery
11. Once in stock recovery, hold power and press volume up and once the menu appears do a factory reset
12. Once complete, reboot the phone
It should now boot back into the normal Sense ROM. Now if you changed your MID to the GPe one you'll need to re-root your phone and change it back using the guide by @scotty1223 HERE but if you didn't change it then you're good to go!
Click to expand...
Click to collapse
That is amazing thank you, ill try it and get back to you asap.
I have two questions:
Will I still get OTAs even if I don't have the original CID and MID? (I remember the original CID which is J15 but I can't remember the mid).
Also, I am currently on custom recovery and in your guide above I do not see anything about flashing stock recovery, should I do that first?
Thank you again!
The RUU flashes everything stock, so it'll overwrite it all
I'd change the CID back to stock once it's all working again but the MID I'm not sure on so I'll see if I can find out for you
At step 8 I get an error "DNS server not authoritative for zone", how to resolve that?
Nvm I resolved the DNS thin, but now I get error 41 model id check fail. It is probably because of bad MID isn't it?
Thank you again for helping me, I hope it is not much trouble.
Guys please help me i just bought my phone and i am without OS already what a stupid i am i messed it up by using twrp and i didn't back up my stock rom dam it (( (((
my phone is boot unlocked and carrier unlocked ( i guess cos i am in cyprus and i got it from hong kong ) or maybe carrier is GSM ? how do i find this out
could you please someone give me a link to a pure HT C stock rom so i can update it to 5.0.1 ?
i found this on here but i can't see the link or there is no link
http://forum.xda-developers.com/showthread.php?t=2694994
please help me
than you so much in advance
post fastboot getvar all result (minus serial no & imei no)
then people will know which ROM version is yours.
I have managed to delete everything ( i think ) from my phone. Below is my data. I am S-ON , unlock bootloader. If i flashed custom bootloader , it tells me that i don t have OS installed.
How can i recover that ?
Thank in advanced.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
dotexe said:
I have managed to delete everything ( i think ) from my phone. Below is my data. I am S-ON , unlock bootloader. If i flashed custom bootloader , it tells me that i don t have OS installed.
How can i recover that ?
Thank in advanced.
Click to expand...
Click to collapse
First ... remove the serial no. & imei no in your post as they are sensitive info.
You have 3 options :
1. Restore 4.16.401.10 TWRP backup - http://forum.xda-developers.com/showpost.php?p=60147089&postcount=5104
It read as WWE 4.20.401.10 TWRP Backup but that's typo error .. it should read as WWE 4.19.401.10 TWRP Backup
or
2. Relock your bootloader and install 4.16.401.10 RUU.exe - http://forum.xda-developers.com/showpost.php?p=56140330&postcount=1
(make backup of your internal storage important data as this will wipe everything)
or
3. Relock your bootloader and fastboot flash the 4.16.401.10 RUU.zip - http://forum.xda-developers.com/showthread.php?t=2735235
(make backup of your internal storage important data as this will wipe everything and also note you need htc_fastboot instead of normal fastboot)
thanks for your fast response.
adb restore <file name> ?
4.16.401.10_HTC__001_TWRP.7z
It is 7zip . This should be repacked as a normal ZIP ?
edit
d:\htc\One\Data>adb restore 4.16.401.10_HTC__001_TWRP.ZIP
adb: unable to connect for backup
dotexe said:
thanks for your fast response.
adb restore <file name> ?
4.16.401.10_HTC__001_TWRP.7z
It is 7zip . This should be repacked as a normal ZIP ?
edit
d:\htc\One\Data>adb restore 4.16.401.10_HTC__001_TWRP.ZIP
adb: unable to connect for backup
Click to expand...
Click to collapse
Read the thread linked in my signature on how to restore a TWRP backup.
You need to extract it with 7-zip and put those files in your backup folder not to ADB it nor fastboot it.
hi guys
I have similar problem.
i flashed stock recovery and ran OTA update 4.16.401.13 (i think) on modified, unlocked, rooted, S-ON HTC One M8 in South Africa, and now stuck on boot logo or black screen.
This is my details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
software number was 4.16.401.10 before OTA update.
can i also use the files above to try to fix the phone?
Thank you. restore is in progress.
After restore i will flash back stock recovery and then relock the bootloader.
If i do that, my top line in bootloader will disappear ? right now is : "Software status: Modified "
Herschelle said:
hi guys
I have similar problem.
i flashed stock recovery and ran OTA update 4.16.401.13 (i think) on modified, unlocked, rooted, S-ON HTC One M8 in South Africa, and now stuck on boot logo or black screen.
software number was 4.16.401.10 before OTA update.
can i also use the files above to try to fix the phone?
Click to expand...
Click to collapse
Yes .. you can use them.
I just put up a link in my thread for my own 4.16.401.10 TWRP backup.
Check : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 10:54 PM ---------- Previous post was at 10:51 PM ----------
dotexe said:
Thank you. restore is in progress.
After restore i will flash back stock recovery and then relock the bootloader.
If i do that, my top line in bootloader will disappear ? right now is : "Software status: Modified "
Click to expand...
Click to collapse
No need to relock bootloader.
Only when running RUU.exe or RUU.zip you need to relock bootloader when S-On.
Using a backup no need to relock bootloader. Just flash stock recovery then do OTA.
If that backup fails (as I'm not sure whether that's fully stock or not), I put up my own stock backup in my thread .. you can try that later if current one fails.
Restore successfully completed. Now, in order not to have problems with latest OTA , i have to restore stock recovery, right ?
dotexe said:
Restore successfully completed. Now, in order not to have problems with latest OTA , i have to restore stock recovery, right ?
Click to expand...
Click to collapse
Yes .. 4.16.401.10 stock recovery
Herschelle said:
hi guys
I have similar problem.
i flashed stock recovery and ran OTA update 4.16.401.13 (i think) on modified, unlocked, rooted, S-ON HTC One M8 in South Africa, and now stuck on boot logo or black screen.
Click to expand...
Click to collapse
Are you sure that you started installing OTA after flashing stock recovery ?
dotexe said:
Are you sure that you started installing OTA after flashing stock recovery ?
Click to expand...
Click to collapse
Yes. OTA downloaded and I tried twice to install, but all it did was restart phone into bootloader.
After flashing stock recovery, I rebooted phone, ran OTA and update started.
After update completed, phone rebooted to white start screen with HTC logo and froze there.
I have read that this is probably because I ran OTA on rooted device.
So now i am stuck with no OS and hope these files will help.
Thanks ckpv5 for help and link.
stock nandroid restore worked. got my phone back
flashed stock recovery and running OTA again now. fingers crossed.
but whatever happens, just wanna say thanks again guys. much appreciated.
Please update us
dotexe said:
Please update us
Click to expand...
Click to collapse
YAY!
can confirm above files and files/procedure in signature link worked.
OTA worked and now updated to 4.16.401.13
thanks very much guys.
now to flash custom TWRP recovery and re-root.
if I may ask, what is the safest method to run OTA in future?
i dont really know. Anyway , how about your free space. i dont know what happened because now i have less that 1 GB free space.
Herschelle said:
YAY!
can confirm above files and files/procedure in signature link worked.
OTA worked and now updated to 4.16.401.13
thanks very much guys.
now to flash custom TWRP recovery and re-root.
if I may ask, what is the safest method to run OTA in future?
Click to expand...
Click to collapse
Boot the custom recovery and make a pure stock backup. Restore that one if you need to ota update again
dotexe said:
i dont really know. Anyway , how about your free space. i dont know what happened because now i have less that 1 GB free space.
Click to expand...
Click to collapse
The best solution for me if I ever have this problem .. I will format data (not wipe data) in TWRP before I restore the backup (of course need to backup internal storage data somewhere else first)
Done . Now i have free space. many thanks !!
Hey everyone
The thing is that I was trying to return my phone to stock recovery to update my phone to Marshmallow and unroot it and I read this in another forum:"Boot your phone to TWRP recovery mode by turn off your phone then presses Vol up + Power to boot into bootloader then choose RECOVERY. There is a more simple way, by using “adb reboot recovery”.
Once came into TWRP main menu, now tap Mount -> Mount system then taps Home.
Tap Advanced -> File Manager, browse to “/system/xbin” folder. From there delete su, daemonsu or busybox if it exists. Also browse to “/system/app” the get rid of Superuser.apk."
So I followed these instructions and then when I rebooted the phone,it got stuck in bootloop. I can't turn it off now or get into the bootloader.
Android-HTC One M8
What can I do to have my phone again in stock recovery?
Thanks in advance
First of all if you rooted the rom this ain't going to work. You need a never rooted stock rom + recovery.
Hold power + volume up and switch to volume down when the screen turns black (do not let go of the power button) then you are in the BL. From there you go to the custom TWRP recovery.
Then you have to find a pure stock backup or a RUU that matches your OS/firmware number (if you haven't made one yourself), restore it and flash the stock recovery and you are done.
Mr Hofs said:
First of all if you rooted the rom this ain't going to work. You need a never rooted stock rom + recovery.
Hold power + volume up and switch to volume down when the screen turns black (do not let go of the power button) then you are in the BL. From there you go to the custom TWRP recovery.
Then you have to find a pure stock backup or a RUU that matches your OS/firmware number (if you haven't made one yourself), restore it and flash the stock recovery and you are done.
Click to expand...
Click to collapse
I flashed a stock recovery img,this is what I have now
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT51NWM00858
(bootloader) imei: 358716059354299
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d5206dbc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
From there I tried to flash the stock RUU 6.12.1540.4 and it always ends with error 155>UKNOWNERROR despite already relocked the device. Should I flash 4.24.709.3 RUU?
Also I try to get to the recovery menu but it only shows a phone with a red triangle,nothing else.
JPaul247 said:
I flashed a stock recovery img,this is what I have now
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.26.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.24.709.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT51NWM00858
(bootloader) imei: 358716059354299
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d5206dbc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
From there I tried to flash the stock RUU 6.12.1540.4 and it always ends with error 155>UKNOWNERROR despite already relocked the device. Should I flash 4.24.709.3 RUU?
Also I try to get to the recovery menu but it only shows a phone with a red triangle,nothing else.
Click to expand...
Click to collapse
You can't run the dev edition RUU at all as you are S-ON and have a different firmware. If you have the 709 RUU then try that indeed. But backup what you need because a RUU deletes EVERYTHING !
Mr Hofs said:
You can't run the dev edition RUU at all as you are S-ON and have a different firmware. If you have the 709 RUU then try that indeed. But backup what you need because a RUU deletes EVERYTHING !
Click to expand...
Click to collapse
So my steps would be S-OFF and from there download 4.24.709.3 RUU? with firmware you mean version-main, right?
Before all this mess I thankfully backed up everything I wanted
JPaul247 said:
So my steps would be S-OFF and from there download 4.24.709.3 RUU? with firmware you mean version-main, right?
Before all this mess I thankfully backed up everything I wanted
Click to expand...
Click to collapse
No S-OFF is NOT needed. just get the RUU with that version number indeed if it's even available. Then run it with a RELOCKED bootloader.
Mr Hofs said:
No S-OFF is NOT needed. just get the RUU with that version number indeed if it's even available. Then run it with a RELOCKED bootloader.
Click to expand...
Click to collapse
What if that version is not available?
JPaul247 said:
What if that version is not available?
Click to expand...
Click to collapse
Then you need a pure stock backup and restore it (usually done with the custom recovery TWRP)
Mr Hofs said:
Then you need a pure stock backup and restore it (usually done with the custom recovery TWRP)
Click to expand...
Click to collapse
I found a stock zip here in XDA,tried to flash it but it says this:
C:\Users\X\Desktop\HTC Fastboot\ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.011s]
finished. total time: 0.012s
C:\Users\X\Desktop\HTC Fastboot\ADB and Fastboot>fastboot flash zip firmware.zip
target reported max download size of 1826418688 bytes
load_file: could not allocate 1752557590 bytes
error: cannot load 'firmware.zip': Not enough space
Should I do a ramdump or something like that?
A stock back-up has to be unpacked and RESTORED with TWRP. No idea what you are doing now but i suggest to stop and read instructions first !
A stock zip can mean everything at this point.....where did you get it ?
Mr Hofs said:
A stock back-up has to be unpacked and RESTORED with TWRP. No idea what you are doing now but i suggest to stop and read instructions first !
A stock zip can mean everything at this point.....where did you get it ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I will then install twrp again and try the stock backup
Mr Hofs said:
A stock back-up has to be unpacked and RESTORED with TWRP. No idea what you are doing now but i suggest to stop and read instructions first !
A stock zip can mean everything at this point.....where did you get it ?
Click to expand...
Click to collapse
I can't push an adb sideload for the firmware.zip nor adb push it.
for the adb sideload says cannot read *sideload* . Any other way to push a .zip file into the phones sd card to mount it with twrp?
JPaul247 said:
I can't push an adb sideload for the firmware.zip nor adb push it.
for the adb sideload says cannot read *sideload* . Any other way to push a .zip file into the phones sd card to mount it with twrp?
Click to expand...
Click to collapse
I surrender with this .zip file.I will try to flash the custom rom Skydragon
JPaul247 said:
I surrender with this .zip file.I will try to flash the custom rom Skydragon
Click to expand...
Click to collapse
*While flashing got error MD5 file not found*
Did you even read the first posts on the backup thread.....how to do it all correctly ?
Mr Hofs said:
Did you even read the first posts on the backup thread.....how to do it all correctly ?
Click to expand...
Click to collapse
This is getting stressful,I want my phone back (thanks for replying everything,every step is one closer I hope) I think I read the correct post
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I am getting all recoveries and everything from there.I download them and try to apply them via push.I think didn't visit this backup thread you are talking of.
JPaul247 said:
This is getting stressful,I want my phone back (thanks for replying everything,every step is one closer I hope) I think I read the correct post
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I am getting all recoveries and everything from there.I download them and try to apply them via push.I think didn't visit this backup thread you are talking of.
Click to expand...
Click to collapse
There is no push, there is no ADB ... he said many times ... read post #1 to understand how-to ...
Basic
Install TWRP 2.8.7.0
Extract the downloaded 4.24.709.3_ckpv5.zip on your PC
Copy the 4.24.709.3 folder to TWRP backup directory
In TWRP select restore
Install 4.24.709.3 stock recovery
Reboot ... OTA... done.
Details - read throughly post #1 all the 14 steps.
Make note or maybe a flow chart that you can understand
Thanks for the reply.I will read everything again
JPaul247 said:
This is getting stressful,I want my phone back (thanks for replying everything,every step is one closer I hope) I think I read the correct post
http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
I am getting all recoveries and everything from there.I download them and try to apply them via push.I think didn't visit this backup thread you are talking of.
Click to expand...
Click to collapse
I did it thank you very much I truly don't know how to thank you more for replying and helping me
ckpv5 said:
There is no push, there is no ADB ... he said many times ... read post #1 to understand how-to ...
Basic
Install TWRP 2.8.7.0
Extract the downloaded 4.24.709.3_ckpv5.zip on your PC
Copy the 4.24.709.3 folder to TWRP backup directory
In TWRP select restore
Install 4.24.709.3 stock recovery
Reboot ... OTA... done.
Details - read throughly post #1 all the 14 steps.
Make note or maybe a flow chart that you can understand
Click to expand...
Click to collapse
Thank you so much for answering I did it
Hi there in need of some help. I have really ****ed up my install of twrp and supersu from my htc one m8.
I followed this person tutorial htconeroot com/htc-one-root I followed everything to the letter apart from enabling Dev enable usb debugging.
1st of all I downloaded this twrp file "openrecovery-twrp-2.7.0.2-m8" when I should have downloaded the latest version of twrp. Such a noob mistake I know now : (
2nd I also downloaded a older version of supersu SuperSU-v2.79-201612051815 which I loaded onto my phone and should have downlaoded the latest version.
I followed all the instruction on the video and when I rebooted after instaling supersu my device is now stuck on the HTC startup screen.
I tried to reboot again going into fastboot and recovery and nothing worked. I know I should have just updated supersu to the latest version but I followed some other peoples advice and now I have completelty screwd my phone I think.
I deleted supersu from twrp and wiped the files as well. My computer now does not recognise my phone folder to be able to install any updated version of supersu or install a ROM. My computer OS is windows 10 and it now sees my phone as a cd drive so cannot install anything on the drive at all.
I can get into twrp but nothing seems to work when I try to reset back to factory settings.
Is there a command line way in geting back into my phone and being able to sort this mess that I have made.
In need of some serious help from the experts here at xda developers.
All help is very much appreciated.
Thanks Steve
tartansteve said:
I followed this person tutorial htconeroot com/htc-one-root I followed everything to the letter apart from enabling Dev enable usb debugging.
Click to expand...
Click to collapse
These random "root" websites just copy content from XDA, and have little or no community to help you. All you need is on XDA, so I recommend stick to XDA.
Such "root" websites also don't give enough information, aren't well organized, and don't update it all. So they are very likely to get you into trouble, as you now know.
tartansteve said:
2nd I also downloaded a older version of supersu SuperSU-v2.79-201612051815 which I loaded onto my phone and should have downlaoded the latest version.
Click to expand...
Click to collapse
What version, if it wasn't SuperSU 2.79?
What version of Android was the phone on when you started? Was it Marshmallow?
tartansteve said:
I can get into twrp but nothing seems to work when I try to reset back to factory settings.
Click to expand...
Click to collapse
There is really no such thing as "reset back to factory settings" especially in TWRP. Just going in and wiping things, isn't going to fix the problem.
Try to fastboot flash an updated version of TWRP. If you were on Marshmallow, try current version 3.1.0-0 from there: https://dl.twrp.me/m8/
Once booted into TWRP, see if you can access the internal storage from your PC. If not, make sure internal storage is checked in "Mount".
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Sorry was this version SuperSU-v2.37.zip. I do appologise thats the latest version that I posted and was ment to be this version SuperSU-v2.37.zip this is the one that I installed.
Yes it was marshmallow.
I downloaded the latest version of twrp and can I ask how to re install twrp ??
I cannot access my phone internal storage for some reason my computer is not recognising my phone now. It was before as I installed supersu straight onto my phone internal storage and tried to boot the phone from that. It's now coming up as a cd drive and I cannot access to install anything on it.
In mount all I have
System >>> not checked
cache >>> not checked
Data >>> is checked
Micro SDcard >> is checked
USB-OTG >>> not checked
Thanks again for your help
Steve
tartansteve said:
I downloaded the latest version of twrp and can I ask how to re install twrp ??
Click to expand...
Click to collapse
Flash with fastboot. Which I would assume is the same way you did it before. Instructions on TWRP's website: https://twrp.me/devices/htconem8gsm.html
tartansteve said:
I cannot access my phone internal storage for some reason my computer is not recognising my phone now.
Click to expand...
Click to collapse
Let's get the right version of TWRP on the phone first, and see if that helps. If not, we'll go from there.
Updated twrp
Hi just to let you know that I have booted into the new twrp. I am using FWUL and using simple-ADB and it installed it no problem.
Just cannot seem to find how to install supersu onto my device as my phone is not showing up FWUL OS.
Sorry, what is FWUL?
Updatefor you
Hi just to say that I installed supersu as well the latest version SuperSU-v2.79-201612051815. After rebooting I am back to the htc page. I have no ROM installed at all on this and it's saying there no OS installed on my phone.
I want to install kali Linux Nethunter and I have downlaod the correct files to install.
WillI have to install another OS like Marshmallow or kitkat before installing Kali Nethunter.
Thanks again for yourhelp : ))
[LIVE-ISO][FWUL][STABLE] adb/fastboot without any installation and driver issues
[F]orget [W]indows se [L]inux
Did you not send me there to download it lol : ))
tartansteve said:
I have no ROM installed at all on this and it's saying there no OS installed on my phone.
Click to expand...
Click to collapse
You must have at some point in trying to "fix" the problem, wiped system in TWRP. System is same as ROM/OS. So if you wiped it, it's pretty obvious that no ROM is the result.
Flashing old SuperSU in itself doesn't result in no ROM/no OS. It just makes the phone stuck on boot screen, and flashing the proper SuperSU will fix it.
tartansteve said:
WillI have to install another OS like Marshmallow or kitkat before installing Kali Nethunter.
Click to expand...
Click to collapse
I've never used it. But reading the thread, it looks like you need a fully working OS. So pick a ROM, put it on the phone, and flash it. Then flash Kali Nethunter.
---------- Post added at 11:14 AM ---------- Previous post was at 11:13 AM ----------
tartansteve said:
[F]orget [W]indows se [L]inux
Did you not send me there to download it lol : ))
Click to expand...
Click to collapse
Ah, I see it's listed as one of the several options for adb/fastboot in the TWRP install instructions. I've never used that specific one, so the acronym confused me. Any fastboot/adb environment will work about the same. You didn't really need to install anything new on your computer. You already had fastboot on your computer to begin with (to unlock the bootloader), and that would have worked fine to install TWRP.
BackUp File
Hi there and thanks very much for your help very much appreciated. Before I did everything I made a back up and have the files on my desktop they are:
0C77AEECE8C258113148C6FB487946BF97B34672
01C669ECF50A775226B15B9F60EEB522AB34BE2F
I have ten of these files and a deafault file as well. Can I restore these to my hpne at all.
I am going to try and install marshmallow on my phone as that was the last OS that I had. Do I have to have the most current and updated version MM.
tartansteve said:
Before I did everything I made a back up and have the files on my desktop they are:
0C77AEECE8C258113148C6FB487946BF97B34672
01C669ECF50A775226B15B9F60EEB522AB34BE2F
Click to expand...
Click to collapse
What did you use to "backup" the phone? Those don't look like TWRP backup folder names. They look like MD5 verification codes?
Individual TWRP backup folders will usually have name format of the date/time the backup was made, such as: 2017-04-22-20-43-56....
tartansteve said:
I am going to try and install marshmallow on my phone as that was the last OS that I had. Do I have to have the most current and updated version MM.
Click to expand...
Click to collapse
There weren't many different official versions (maybe 1 or 2) of Marshmallow for each M8 carrier version. Any version MM should do.
"locked s-on" cant get to unlock and also stuck
ckpv5 said:
You may have outdated firmware and outdated TWRP version. Most of current ROM won't get installed on outdated TWRP.
Post fastboot getvar all result without serial & imei no. We'll see what you need.
Click to expand...
Click to collapse
===
I HAVE DONE THE WHOLE PROCESS OF HTC DEV UNLOCKING WITH CODE AND EVERYTHING BUT STILL IT IS LOCKED
PLZ REPLY ON E-MAIL IF U CAN OR WHATSAPPP +92 333 23 63 968
my phone HTC ONE M8_WHL is just stuck on either bootloader or htc logo and it doesnot allow to flash anything, what ever i do i get one error "error: not allowed" kind of, plz help me
==============================================================
C:\ADB_new>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.651.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA457SF00649
(bootloader) imei: 990004991183470
(bootloader) imei2: Not Support
(bootloader) meid: 99000499118347
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B70000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.238s
==============================================================