Folks
I need help to solve a problem.
I bought a HTC One M8x and decided to set up a rom custon. I study the subject before. I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error. I was exploring the tool I ended up pressing and making procedures that were not listed, but apparently did not issue before starting the installation made the backup and then wipe. I started the procedure to install, entered the install section and located the ROM and sent install. After a while appeared an error saying that the installation was not possible, I managed to recover the backup, but the phone was not the same. I realized that my internal memory is no longer visible, I can not download pictures or audios in whatsapp, another thing I noticed is that the file manager also does not provide the internal memory (directories, programs, and others). When I try to synchronize your phone with your computer to the same thing, I can see the micro SD, but can not see the internal memory. I possibly when I was digging the Recovery program just blocking the internal memory and wanted to know how do to reverse. Does anyone have any ideas.
Do you have access to bootloader? if yes. You can try to restore your phone with HTC RUU
ddfilho said:
I took the program kit available for the M8 and follow all the steps to unlock. All this function normally, however when installing the ROM custon the device just gave error.
Click to expand...
Click to collapse
Using the (now outdated) toolkit was a mistake. Whenever modding these devices, you need to research the current methods applicable to the current state of the phone, not methods from 2 years ago (and all the toolkits have not been updated in that long or more).
The toolkit installs an obsolete version of TWRP, and that is probably why the ROM is failing to flash. It probably also wiped out your OS version on bootloader screen and getvar (not a major issue, but an inconvenience if you want to determine the firmware number).
You should update to more current version of TWRP. But you'll probably need to solve the issue of your internal storage first, which is apparently been corrupted. Go into TWRP, and try the option in Wipe to "Format Data" (button next to "Advanced"). This usually fixes the corrupt internal storage issue.
Also do fastboot getvar all, and post the results, so we can see more info about the phone, and more properly provide guidance. Delete IMEI and serial number before posting.
I have access to the bootloader but do not know run this action. Could you tell me where I can walkthrougt to do so.
Thank you for your help
Pardon
Now that saw the second message. I will perform this procedure now
Friend
Your solution worked perfectly.
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Thanks again
ddfilho said:
I wanted your help to make the second action, I entered the bootloader and accessed the fastboot but did not find the getvar option. Could you tell me how to do it.
Click to expand...
Click to collapse
This isn't an option on the phone, if that is what you mean. Its a fastboot command issued from your PC, and you'd know how to issue a fastboot command if you unlocked the bootloader via HTCDev.com, instead of letting the toolkit do it for you. Which is another reason I don't like the toolkits: they shortcut the learning process, and leave you without the skills to solve basic problems, which almost inevitably happen.
You're going to need to figure out where fastboot.exe was installed during the bootloader unlock process. Once you've found that, you can then:
1) Connect phone to PC, booted into bootloader-fastboot mode
2) On PC, open a window for the folder that contains fastboot.exe
3) Hover mouse cursor over the window, and Shift+Right Mouse button, then select "Open command window here" and this will open up Command Prompt to the fastboot directory
4) In Command Prompt window, type: fastboot getvar all
5) You will see output with details about the phone, to copy the desired text, right click on the command window, select Edit>Mark, then highlight the desired text (getvar output) and press Enter. Then paste the text.
6) Be sure to delete IMEI and serial number from getvar output before posting it here
ddfilho said:
I found the TWRP 3.0.2, I believe it is the last version but need help because I believe that the update version is not simple, I installed the 2.7.0.2 version.
Click to expand...
Click to collapse
Exact TWRP version depends on your current firmware, which we can determine from the getvar output above.
Once we've determined the proper TWRP version, its easily installed by putting the file in your fastboot folder, and flashing with fastboot command. Again, we see how valuable it is to know how to use fastboot. But don't try that, until we've determined the proper version from getvar output.
I managed to perform the procedure now. See the information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(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: 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: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
ddfilho said:
I managed to perform the procedure now. See the information:
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-main:
Click to expand...
Click to collapse
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
redpoint73 said:
As I suspected, your firmware number (version-main) info was wiped out by using an obsolete version of TWRP (known bug). But luckily I know the radio number corresponds to Marshmallow firmware.
Flash TWRP 3.0.2 using the fastboot install method here. No need to install Android SDK, or drivers noted in the instructions, since you already have fastboot setup (and you're a fastboot expert now ); and not need to reboot using adb, if you do it using the button combo other otherwise.
After getting the updated TWRP version installed, you should be able to put the desired custom ROM on the phone, and flash it. If not, take note of any error messages or other behaviors, and post them here.
Click to expand...
Click to collapse
Folks
Thank you for your help
I managed to update TWRP following the instructions, but when I tried to install the ROM did not succeed.
It gave an error as if he could not open the file or install, see the message:
Error opening: `/and-sec/uuuuuuuu.uuu'(I/O error) ===> Several lines with mensagem.
You know how I can be able to install any rom?
In TWRP go to WIPE then select Format data, type yes
Then go to REBOOT select recovery ... now try again to install ROM
Related
Hello,
I am trying to fix my issue and have done a ton of reading but can't figure out where to go from here. I've had my phone rooted for months and tried to flash a newer custom ROM today and it ended up locking my phone into a boot loop. I was able to get out of it and had to re install a recovery tool (have installed both CWM and TWRP and they work fine). But I can't actually get a ROM back onto my phone because I don't have one on the SD card and I can't get one to it. I just want to put a stock ROM back onto it at this point.
I can't boot into windows to access the SD card because whenever I boot the phone normally it just goes back to boot looping. I have tried ADB push when in recovery to put a ROM on the SD card and I continually get permission denied when I try to do that. I have tried ADB sideloader and I can't get that to work either. How can I go about getting a ROM to my phone so I can flash it via CWM/TWRP?
Fastboot works fine and I can flash recoveries no problem. ADB appear to work but I can't understand why I can't just get push to work. Any help would be greatly appreciated.
HTC One M7 on Verizon.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 1.12.42.0731
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.10.605.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-97af273845
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
NotATreoFan said:
If you type "adb devices" from a Command Prompt, do you see your phone listed?
Try powering off your phone, then holding Power+VolDown until you get to HBOOT. From there, enter recovery (TWRP is my preferred). ADB push does not require anything to be done prior to using it, so assuming you can see your phone with "adb devices", proceed like this:
Rename the ROM you want to flash to ROM.zip
Type "adb push ROM.zip /sdcard/" No quotes
If the ROM is around 1GB, this will take 5-10 minutes.
Once done, use TWRP file manager (under Advanced) to verify the file is there.
Reboot back into recovery and verify it's still there. If it is, install it. If it's not, you will have to RUU back to stock and go through the unlock process again.
Click to expand...
Click to collapse
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
factor00 said:
No it isn't showing up when I do that while in recovery.
C:\Users\Mat\Desktop\adb>adb devices
List of devices attached
Click to expand...
Click to collapse
What about fastboot?
NotATreoFan said:
What about fastboot?
Click to expand...
Click to collapse
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
factor00 said:
Yes fastboot is working. I can see the phone info still. You said I can just RUU. I didn't realize I could do that. That's fine with me I have no issue with that.
I just re-lock the boot loader and then run the RUU from windows? Would this be the appropriate file? RUU Zip M7 WL JB 50 VZW 1.10.605.10 Decrypted from HTC1 Guru.com (I can't post the actual link do to the forum rules.) The CID and model id match what my phone says.
Thanks for all your help!
Click to expand...
Click to collapse
I haven't done anything RUU in a while, so I don't want to steer you wrong. But I believe you can use decrypted to get everything up and running. Check the general forum for a guide on returning to stock.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Just remember to keep s-off while running the ruu
Self-admitted newb here. Been reading up on FAQs and instructions on how to Root my new device and am eager to learn more to eventually fully optimize. I was able to unlock, but when attempting to flash TWRP recovery, it'll just hang forever with this message:
"sending 'recovery' (11976 KB)...".
I confirmed checksums of files downloaded, USB Debugging is flagged, Fastboot is deselected, updated the HTC drivers on my PC, and my S/N is acknowledged with the 'fastboot devices' command. I even did a Factory Reset from bootload screen, as this is a new device with no data on it yet.
Any helpful suggestions on determining next steps would be greatly appreciated!
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(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
You need 2.7 series..
flyera343 said:
You need 2.7 series..
Click to expand...
Click to collapse
Agreed, and I was mistakenly attempting to flash twrp-2.8.6.1-m8.img initially . I'm sorry I failed to mention that in the original post and yes, I also did erase cache several times. Re-attempting to flash twrp-2.7.0.1-m8.img is when the 'sending recovery' hang issue comes up.
bump
pill_popper said:
(bootloader) version-main: 1.54.401.109
(bootloader) modelid: 0P6B12000
(bootloader) security: off
Click to expand...
Click to collapse
You have a very old software version. Since your device is S-Off, I suggest :
1. change the MID 0P6B12000 to 0P6B10000
Follow this thread : http://forum.xda-developers.com/showthread.php?t=2708581
2. run 4.16.401.10 RUU.exe - https://docs.google.com/file/d/0B17smFr95pleeTQ5U1NzNkZzM0U/edit?pli=1
RUU will flash your entire phone back to stock including recovery
(as your device is S-Off, no need to lock/relock bootloader)
3. Now you can install the latest TWRP recovery and do whatever you want to do
Thank you for your kind words. I appreciate it. Will follow up on the points covered in your post and report back.
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery. This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
ckpv5 said:
Ahh.. you need a rooted ROM to do that change of MID.
Without a custom recovery installed, you may not have a rooted ROM.
Reading back your problem ... the error is stuck at sending recovery, not enter recovery.
Click to expand...
Click to collapse
Correct, sorry if I wasn't being clear about that. I've Unlocked, but not yet rooted hence, the attempt to send TWRP. I haven't yet taken next steps though.
ckpv5 said:
This is possible if you don't have a proper fastboot/adb files.
Try this : http://forum.xda-developers.com/showthread.php?t=2317790
then try to install TWRP recovery again
Click to expand...
Click to collapse
More reading! :cyclops:
**Updated**
So I've tried using Minimal ADB tool as well. Now instead of hanging, I'm eliciting errors.
target reported max download size of 1830711296 bytes
sending 'recovery' (11976 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 5.023s
I'm running as Administrator in Windows 7, I can hear the PC recognize the phone when I plug it in the USB and I've also confirmed multiple times the 'fastboot devices' command recognizes my phone.
If this might be a USB related issue, how would I go about investigating in that direction? Not sure what is preventing me from simply flashing a TWRP recovery. Any thoughts on this are welcome, thank you.
*bumpity bump*
So I can see 'FASTBOOT USB' in bootloader mode, and the fastboot devices command returns my S/N, but still the adb devices command just returns the message 'list of devices' and nothing else. Attempting to flash TWRP recovery still fails. I've uninstalled all HTC stuff and manually updated the driver to 'MTP USB Device' via Device Manager per redpoint73's advice. Before I give up on this PC, are there any additional steps I can take? Any guidance from you guys would be appreciated, thanks!
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
ckpv5 said:
First, you don't run adb command when on fastboot mode, only fastboot command will work.
Is the USB 3.0 on PC ? You need USB 2.0
Is your device properly working ?
I like to suggest to flash Dev Edition firmware to your device or simply run the Dev Edition RUU to bring the hboot/software version to the latest version before you try TWRP again.
You have MID/CID that match/fit a Dev Edition device except the software version no.
Click to expand...
Click to collapse
I guess what most on here would consider to be trivial are to me revelations. Thank you for your response and now I see my device S/N is recognized after running the adb devices command when the phone is running in 'normal' mode! Yes, it is properly working but sadly, all four USB ports on the PC are USB 3.0 I'll read up on your suggestions and reply with questions at that point before taking action. Again with the reading! :cyclops: My concerns here are if stock recovery would continue to work if I go down either of those paths and how the phone is supposed to respond if it's not responding when attempting to flash TWRP. Thanks again for your inputs, I appreciate it!
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
ckpv5 said:
First .. you need to know your reason to install a TWRP. If you plan to install a custom ROM, it won't properly work because you have a very low version hboot as most custom ROMs require a hboot 3.19.0000
then .. there are other ways to achieve this (all because you have a S-Off device)
1. You can install TWRP using the external_sd (microSD) method but you can only use a lower version TWRP 2.7.x.x or better 2.8.1.0 (because you failed in fastboot method)
2. As I said earlier - install the latest firmware.zip but using the external_sd method too ... but your device may get stuck because your ROM is too low
3. The safest/fastest is install RUU but again you need a USB 2.0 (I'm not sure whether you can install RUU zip using the external_sd method).
4. Back to no. 2 - you can install the firmware.zip using the external_sd method (need to do it twice) then install TWRP again the external_sd method then you need to install a ROM or restore a backup meant for the newer hboot 3.19
Click to expand...
Click to collapse
If I wanted to attempt #3, please point me to the correct version as it wasn't clear to me what file to choose here:
http://forum.xda-developers.com/showthread.php?t=2701376
Thanks!
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
ckpv5 said:
http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
1. put device on fastboot/bootloader mode
2. run the exe (select run as administrator in windows context menu
3. follow instruction - accept, next, next, blablabla until finish
Click to expand...
Click to collapse
The whole point of this exercise is to gain root so that yes, I can have the option of flashing a custom ROM. I noticed in the executable's file name you referenced model M8_UL_L50, but mine is M8_UL_CA. I also noticed its radio version differs from the one listed in my getvar all file. *edit* I've now realized this file is straight from HTC.
Since my current version is so old, is it still OK to run this to update to the latest version rather than updating to an intermediate version before updating to the latest version? Just wanted to confirm before taking any unnecessary action. Thank you again for your patience and the helpful information!
M8_UL - M8 with LTE
L50 - Android L 5.0
CA - US region
Radio version different because yours is old/lower version and this is newer/latest version and you're going to update hboot, radio and many more with this RUU. You need the update in order to install custom ROM as I mentioned before most custom ROMs work only on hboot 3.19.0000
You have S-Off device, you don't need intermediate version ... and most important RUU doesn't need intermediate version because RUU will wipe clean your device and replace all images with those come with it. (So make a backup of your important files to PC)
I bought a second hand HTC ONE M8 recently. It was previously locked to a Swedish Carrier (called "3").
When I insert a SIM card from another carrier, a window pops up right after I enter the PIN code, asking me to type in a code to unlock the network.
The code I have, but whenever I type it in and hit "unlock", the phone gets stuck at "requesting network code. Very much like in this post:
http://forum.xda-developers.com/showthread.php?t=2791553
The phone has a Play Edition ROM, which is not the original. Some say that a solution is to revert back to stock ROM, but I'm not sure how.
Anyone has any other ideas? Google searches yield surprisingly few good results.
Yeah .. usually you need to revert back to non-rooted stock then only you can use the unlock code.
Post fastboot getvar all result (without serial & imei no.) then we'll see the next step to take.
Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
ckpv5 said:
Yeah .. usually you need to revert back to non-rooted stock then only you can use the unlock code.
Post fastboot getvar all result (without serial & imei no.) then we'll see the next step to take.
Read this : http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
Click to expand...
Click to collapse
Thank you for answering.
I tried the link but I never managed to get HTC Sync Manager to recognize the phone.
fastboot getvar all only yields "waiting for device". What could be wrong? I've tried multiple ways of installing drivers manually, but to no avail.
You need to put the device on bootloader/fastboot mode to run fastboot command.
Read again the link given, you're supposed to uninstall htc sync manager and also you need to install adb/fastboot
ckpv5 said:
You need to put the device on bootloader/fastboot mode to run fastboot command.
Read again the link given, you're supposed to uninstall htc sync manager and also you need to install adb/fastboot
Click to expand...
Click to collapse
Alright, here we go! Thank you so much!
C:\Users\Johan>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.23.213311491.A13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.07.1700.14
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(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: 11459804
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.110s
This will involve many steps as I don't see any RUU for this carrier ...
1. You need to install 6.13.771.4 firmware.zip
Download the fw_6.13.771.4.zip from post #5 in my backup thread and read how to install the firmware. You can skip the relock bootloader part as you have a S-Off device.
Leave it unlocked .. can you confirm current status .. the booloader is unlocked or locked or relocked ?
2. Install TWRP the latest version 3.0.2-0 ... link to download on post #1 in same thread
3. Restore 6.13.771.4 backup that you can download on post #3 - read how-to on post #1
4. run the unlock code
ckpv5 said:
This will involve many steps as I don't see any RUU for this carrier ...
1. You need to install 6.13.771.4 firmware.zip
Download the fw_6.13.771.4.zip from post #5 in my backup thread and read how to install the firmware. You can skip the relock bootloader part as you have a S-Off device.
Leave it unlocked .. can you confirm current status .. the booloader is unlocked or locked or relocked ?
2. Install TWRP the latest version 3.0.2-0 ... link to download on post #1 in same thread
3. Restore 6.13.771.4 backup that you can download on post #3 - read how-to on post #1
4. run the unlock code
Click to expand...
Click to collapse
I can confirm it is unlocked. I started following the steps in post #1, but can't seem to complete step 5. I try to make a backup of the boot, but when I do, several red errors in the log appears. All of them starts with
Failed to/Unable to mount '/cache, /data, /carrier (invalid argument).
What might cause these errors?
Forgot to write more on item 2.
Install TWRP the latest version 3.0.2-0 ... link to download on post #1 in same thread
Because you're converting back to Sense from GPE ... you need to do these before you can proceed to item 3.
In TWRP - select wipe - Format data - type yes
Once it is done doing its stuff, use back button select reboot - recovery
Now you can proceed item 3.
ckpv5 said:
Forgot to write more on item 2.
Install TWRP the latest version 3.0.2-0 ... link to download on post #1 in same thread
Because you're converting back to Sense from GPE ... you need to do these before you can proceed to item 3.
In TWRP - select wipe - Format data - type yes
Once it is done doing its stuff, use back button select reboot - recovery
Now you can proceed item 3.
Click to expand...
Click to collapse
That worked fine.
Now I'm stuck at number 9 instead. When I press "Restore" in the TWRP menu, I don't have anything to select.
Also, what looks more right?
Computer\HTC One_M8\Internal Storage\0\TWRP\BACKUPS\SH45FWM04430\2016-08-18--10-23-37_MRA58K.H14_release-keys\6.13.771.4
or
Computer\HTC One_M8\Internal Storage\0\TWRP\BACKUPS\SH45FWM04430\6.13.771.4
Doesn't seem to make a difference anyway though.
The second one but without \0\
Should read Computer\HTC One_M8\Internal Storage\TWRP\BACKUPS\SH45FWM04430\6.13.771.4
Try redo the backup of boot ... then it will write correct location Computer\HTC One_M8\Internal Storage\TWRP\BACKUPS\SH45FWM04430\xxxxxxxxx
After redo the backup ... select Restore and check whether TWRP can see the folder that you backup. If yes, now you have correct location
Instead of transferring the 6.13.771.4 folder, you also can copy the contents of the 6.13.771.4 folder (there should be 8 items) to Internal Storage\TWRP\BACKUPS\SH45FWM04430\xxxxxxxxx and replace the contents when asked by windows
ckpv5 said:
The second one but without \0\
Should read Computer\HTC One_M8\Internal Storage\TWRP\BACKUPS\SH45FWM04430\6.13.771.4
Try redo the backup of boot ... then it will write correct location Computer\HTC One_M8\Internal Storage\TWRP\BACKUPS\SH45FWM04430\xxxxxxxxx
After redo the backup ... select Restore and check whether TWRP can see the folder that you backup. If yes, now you have correct location
Instead of transferring the 6.13.771.4 folder, you also can copy the contents of the 6.13.771.4 folder (there should be 8 items) to Internal Storage\TWRP\BACKUPS\SH45FWM04430\xxxxxxxxx and replace the contents when asked by windows
Click to expand...
Click to collapse
It worked! Thank you so much, you're a HTC wizard.
Mumfi said:
It worked!
Click to expand...
Click to collapse
Great :good:
I take it the network unlocked problem is now solved.
Thanks for the donation, highly appreciated
i have a htc one m8 gsm LTE version. and whenever i try to clean update from twrp it shows the screen for a couple seconds and then reboot and it does it again. sometimes it says setup wizard has stopped working. plz help
Need more info, in order to help.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
cm 14.1
redpoint73 said:
Need more info, in order to help.
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
Click to expand...
Click to collapse
im new to android and rooting and i dont know what fastboot getvar is and the twrp version is 2.7.0.2
Abhay Purba said:
im new to android and rooting and i dont know what fastboot getvar is and the twrp version is 2.7.0.2
Click to expand...
Click to collapse
Did you unlock the phone and root it yourself?
If so, the process to do fastboot getvar, is the same as the fastboot command you used to unlock the bootloader. Connect the phone to PC, boot into bootloader-fastboot mode, open command prompt on PC (probably need to change directory to whatever folder contains fastboot.exe), then type fastboot getvar all
Then post the output, but delete IMEI and serial number before posting (these are personal data what should never be posted online).
Alternately, in bootloader, tell us what it says for hboot number, radio baseband number, and OS number. This doesn't tell as all the getvar data, but at least it gives us a few critical pieces of info.
Your TWRP version is very old. Its not compatible with CM14 (or 13, for that matter). Probably also not appropriate for your phone's firmware (but need more info to determine that).
Did you use a toolkit to unlock the bootloader (that particular TWRP version is a telltale sign)? If so, the toolkit is obsolete (hasn't been updated in almost 2 years) and many of its components therefore cause more problem than they solve. More importantly, the toolkit is a crutch, which shortcuts the learning process, and it gets you stuck without the proper knowledge to get yourself unstuck (as you now see). For instance, if you used the toolkit, than you have no idea how to do basic stuff needed to mod these phones, like fastboot commands.
Getvar
redpoint73 said:
Did you unlock the phone and root it yourself?
If so, the process to do fastboot getvar, is the same as the fastboot command you used to unlock the bootloader. Connect the phone to PC, boot into bootloader-fastboot mode, open command prompt on PC (probably need to change directory to whatever folder contains fastboot.exe), then type fastboot getvar all
Then post the output, but delete IMEI and serial number before posting (these are personal data what should never be posted online).
Alternately, in bootloader, tell us what it says for hboot number, radio baseband number, and OS number. This doesn't tell as all the getvar data, but at least it gives us a few critical pieces of info.
Your TWRP version is very old. Its not compatible with CM14 (or 13, for that matter). Probably also not appropriate for your phone's firmware (but need more info to determine that).
Did you use a toolkit to unlock the bootloader (that particular TWRP version is a telltale sign)? If so, the toolkit is obsolete (hasn't been updated in almost 2 years) and many of its components therefore cause more problem than they solve. More importantly, the toolkit is a crutch, which shortcuts the learning process, and it gets you stuck without the proper knowledge to get yourself unstuck (as you now see). For instance, if you used the toolkit, than you have no idea how to do basic stuff needed to mod these phones, like fastboot commands.
Click to expand...
Click to collapse
So i updated the custom recovery and tried to install cm14.1 and that didnt work smae problem. but i did get the information you wanted. so here you go. thanks for all this .
C:\Users\notor>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(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_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
all: Done!
finished. total time: 0.034s
Im assuming you may have a canadian provider?
I believe there are issues with that if it is the case. If it is flashing correctly and allowing you to boot into the rom and then rebooting, i doubt it would be twrp.
You may need to wait a couple of days as TeamM8 are building a rom specifically for Canadian carriers which disables the AGPS which is causing your issues. (If that is what the issues are)
Alternative is to flash CM13 for the time and update when they release a working build.
miffymiffy said:
Im assuming you may have a canadian provider?
I believe there are issues with that if it is the case. If it is flashing correctly and allowing you to boot into the rom and then rebooting, i doubt it would be twrp.
You may need to wait a couple of days as TeamM8 are building a rom specifically for Canadian carriers which disables the AGPS which is causing your issues. (If that is what the issues are)
Alternative is to flash CM13 for the time and update when they release a working build.
Click to expand...
Click to collapse
awesome where can i find this rom when it comes out
Abhay Purba said:
awesome where can i find this rom when it comes out
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-m8/development/unofficial-cyanogenmod-14-t3490208
he mentioned it this morning
miffymiffy said:
Im assuming you may have a canadian provider?
I believe there are issues with that if it is the case. If it is flashing correctly and allowing you to boot into the rom and then rebooting, i doubt it would be twrp.
Click to expand...
Click to collapse
Good catch, and interesting issue, which I was not aware of.
Although it would be helpful if the OP confirmed he actually uses a Canadian provider.
OP should be as specific as possible, and answer all questions posed to them, if they want proper help.
yes im a canadian user. and i have fixed the problem by disabling gps. Thanks
Hi guys I have an HTC ONE M8 running 4.4.4 with TWRP and Root installed and a few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual. When I did that and rebooted the phone, the phone is stuck on the HTC logo and I can only boot into bootloader mode and also into TWRP. Also TWRP is also saying I have lost root access.
What can I do to fix this problem can I restore back to 4.4.4 as a new device and re-root it and install TWRP? How do I get out of this mess? It is S-ON and Software Status is MODIFIED.
No matter how long I leave the phone it will stay on the logo until it dies or until I boot into bootloader.
Thank You Guys I Have Lost Hope Honestly.
IF ANYONE CAN HELP ME PLEASE PROVIDE THOROUGH INSTRUCTIONS! THANK YOU!
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
TechMan123456 said:
few weeks ago I tried to go into TWRP and clear cache and dalvik-cache and such, as usual.
Click to expand...
Click to collapse
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
redpoint73 said:
First of all, the fact the screen comes on at all, means it almost certainly not bricked, and recoverable. You just can't boot into OS, and with TWRP installed, that is not too serious a problem.
On the other hand, once you have TWRP installed, the first thing you should always do before rooting or other mods, is to use TWRP make a backup of system and boot.img. And even after successful root, it's good to make a backup of the rooted ROM. If you had a TWRP backup o the phone, in an event like this (no boot into OS) you can simply boot into TWRP, and restore the backup.
If you have no backups, you can download the proper one from the collection: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
You can then restore using the instructions from that same thread. You only need to do steps 4-9 to get the phone running again, then reboot. Steps 1-3 relate to installing TWRP (which you already have). Steps 10 and on, are optional as they will install stock recovery to the phone, which will allow you to update to more current Android version (which will eventually get you up to Marshmallow).
If you need help determining what version number TWRP backup to restore from the above linked collection, then do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Another option is to RUU back to stock (if your version M8 has an RUU) if you are okay with the phone being wiped. If you are s-on, you will need to relock the bootloader in order to RUU. Then after RUU, unlock the bootloader again, install TWRP and root the phone.
What does "and such" mean? Did you wipe anything besides cache and Dalvik?
Click to expand...
Click to collapse
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
xunholyx said:
MTP device driver?
What does it say next to "OS" in your bootloader?
Also, if you can boot to recovery you should be able to restore a backup
Click to expand...
Click to collapse
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
you can use a card reader to put the rom or the backup on external sd card
or use an OTG USB flash memory
also connect the device to pc while you are in recovery this should work by it self no need to install MTP driver
which OS you have on your pc ??
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
No OS is usually an easy fix. Download a ROM on your PC, put it onto your extSD, and flash the ROM in recovery. The reason you have no OS is because you wiped system in TWRP. If you do that, you need to flash a ROM after or you'll have no OS on a reboot.
It's best to never wipe system in TWRP as this is done by default in recovery when you flash a ROM. There will be the odd instance that it is suggested to wipe it ( I've never seen that with HTC based ROMs), but if it isn't then don't.
---------- Post added at 08:52 PM ---------- Previous post was at 08:47 PM ----------
TechMan123456 said:
There is no OS installed at all for some reason! When I try to download a backup I need to flash it and the only way to do so is by having the MTP Driver installed in order to drag it into TWRP and flash the backup. I can't do so because it fails to install my MTP Driver.
Click to expand...
Click to collapse
Ahhh, reding it a second time I realize you mean OS is blank in your bootloader. You should also update your TWRP version
TechMan123456 said:
The MTP Device Driver is not installing on my PC for some reason. It is saying installation failed on the MTP Device window on my computer.
Click to expand...
Click to collapse
Not clear which drivers you are trying to install, the HTC drivers from their website, the ones which load from the phone, built-in Windows drivers, etc.?
Try going to HTC's website, and download HTC Sync, which will also install the drivers. If you already have this installed, try uninstalling, and re-install.
Alternately, the Android MTP device drivers built-in to Windows is a generic version of drivers which can often get at least adb/fastboot working, and probably also allow you to drag/drop to internal storage in TWRP. If these drivers are the ones failing to install, it would imply there is something wrong with your Windows installation (which there isn't a lot we can help you with) rather than anything with the phone.
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Arslan8997 said:
hey
i also have the same problem in boot-loader OS is blank
i have downloaded the nandriod backup and restored it using TWRP but after successful restore i didn't get the os back and again it goes to boot-loader and show OS blank
Click to expand...
Click to collapse
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Also, what version TWRP?
Click to expand...
Click to collapse
I also try RUU sprint version ROM but it didn't work
TWRP v2.7.0.2
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXX
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Arslan8997 said:
I also try RUU sprint version ROM but it didn't work
Click to expand...
Click to collapse
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
redpoint73 said:
How did you pick a nanddroid backup to download, if you don't know the OS number?
Click to expand...
Click to collapse
redpoint73 said:
You need to be more specific:
What version number of file name of the RUU you tried? Zip format or exe format? If zip format, did you flash by fastboot, or SD card method?
Did you get an error message, if so, what did it say exactly? If no error message, what was the mode of failure (what happened exactly - be detailed - at what exact point did the RUU fail, status of the phone, etc.)? Saying "It didn't work" doesn't give us any info to troubleshoot why it failed, or how to get it to work.
Also, you did not provide all the info requested (questions I asked you in my last response):
Click to expand...
Click to collapse
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Status of phone is
bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.09.20.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: XXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: XXXXXXXXXXXXX
(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: 8a0f02ff
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Arslan8997 said:
RUU_M8_WHL_M60_SENSE70_SPCS_MR_Sprint_WWE_6.20.651.3.exe
this i have try to install but faild to install it give error of to pick the correct rom
when i check the ruu log there was an error of (status read failed (Too many links))
Click to expand...
Click to collapse
You need to flash the firmware 6.20.651.3 in order for the RUU to install (firmware and RUU are different things - so don't confuse the two). The firmware and how to flash are described here (as well as all the Sprint RUUs): https://forum.xda-developers.com/showthread.php?t=2729173
Just a heads up, if you don't know already: No need to relock the bootloader to do this (flash either firmware or RUU) since you are s-off, and no benefit in doing so. Plus, relocked bootloader gives you less options to recovery, so it is not recommended to relock it in your case.
Also, in regards to your original question (no boot after restoring TWRP backup): you never answered my question of how you picked a TWRP backup to download and restore (which I asked twice before). Now that I see you have the Sprint version M8, I will guess that you tried to restore the incorrect version backup. Sprint version uses different kernel from most other M8 versions. So if you don't restore the proper one, no boot is the expected outcome. Also, even if Sprint, it would have to be the same version you were on before (Kitkat) which is another reason it would not boot.