The phone itself boots up fine, however whenever I try to load up recovery (I have flashed TWRP) some red text flashes, then it loads into fastboot.
I heard it might be a cache or bad TWRP file, however I have no idea how to fix either of them.
Any advice would be greatly appreciated.
IVIemories said:
The phone itself boots up fine, however whenever I try to load up recovery (I have flashed TWRP) some red text flashes, then it loads into fastboot.
I heard it might be a cache or bad TWRP file, however I have no idea how to fix either of them.
Any advice would be greatly appreciated.
Click to expand...
Click to collapse
Which ROM u running KK or LOLLI ?
TWRP for kk & Lo are in this ZIP
Download : https://mega.nz/#!yQ1RRZxK!fzcw9gdxgYd4Qd-8FTPoYuJroZ6RGHHkeb6381NncEo
how to flash here: https://www.youtube.com/watch?v=xsn6co4Ve6M
I tried flashing the stock recoveries, but it gave the same result. Whenever I select recovery, the 'entering recovery' text flashes for a second, then the phone goes into the fastboot menu.
I'm running KK by the way.
Whats you complete model number like 820U | 820n | 820Q | 820S
Here is Twrp recovery for kk https://mega.nz/#!zM8G2AwJ!6QH8eZYZ8aoe_ap_UGu1iLf_NnqsnD4bhHp2u42MH8k
Here is stock recovery for kk https://drive.google.com/file/d/0B2DumUOvI46KM2toeGR3QXpLYW8/view?pref=2&pli=1 [ for 820U ]
Code:
how to flash here [video guide: https://www.youtube.com/watch?v=xsn6co4Ve6M
More info :http://forum.xda-developers.com/desire-820/development/play-recovery-htc-desire-820-dual-sim-t3225782
Keep in mind to flash any custom recovery (twrp,cmw,philz touch) you need to have you bootlodder unlocked
If stock is not working can you may flash TWRP
The phone model in both settings and hardware info only displays as HTC_0PFJ50. Again, both flashes work fine, it's just that whenever I enter recovery, it goes into the fastboot menu instead of the recovery menu (bootloader has been unlocked).
IVIemories said:
The phone model in both settings and hardware info only displays as HTC_0PFJ50. Again, both flashes work fine, it's just that whenever I enter recovery, it goes into the fastboot menu instead of the recovery menu (bootloader has been unlocked).
Click to expand...
Click to collapse
Can you do "fastboot getvar all" and post the result here
Whenever I try that, it only comes up with the 'adb help' list, in fact all the adb commands ends up with the help menu apart from 'adb devices' which results in
(List of devices attached
HT57NYC00235 offline)
Fastboot getvar all ends with a endless <waiting for device>. USB debugging has been turned on.
IVIemories said:
Whenever I try that, it only comes up with the 'adb help' list, in fact all the adb commands ends up with the help menu apart from 'adb devices' which results in
(List of devices attached
HT57NYC00235 offline)
Fastboot getvar all ends with a endless <waiting for device>. USB debugging has been turned on.
Click to expand...
Click to collapse
which fastboot & adb drivers you have , you need HTC this
https://mega.nz/#!6BcyEYZT!fMpb8fsPwgQ8Hryci1z3YmMcN43tM0gZqydV3I8dz30
It was still giving the same thing, until I realized the device wasn't being recognized.
I installed the ADB driver in device manager and 'fastboot getvar all' got me this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.05.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT57NYC00235
(bootloader) imei: 355719062070426
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: HTC__039
(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: 735c2625
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
IVIemories said:
It was still giving the same thing, until I realized the device wasn't being recognized.
I installed the ADB driver in device manager and 'fastboot getvar all' got me this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.05.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT57NYC00235
(bootloader) imei: 355719062070426
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: HTC__039
(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: 735c2625
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
Click to expand...
Click to collapse
Code:
./
-Read me well before you flash this recovery
/.
THIS twrp recovery is for your model A51_TUHL, but for lollipop
hence, it won't run on your kitkat which you have rite now . Can you make OTA update from your phone & get lollipop but for that too you need to flash your working stock recovery & re-lock boot lodder.
After this is done Go for lollipop OTA update & when your phone will Run lollipop
After that again Unlock bootlodder,
Code:
fastboot flash unlocktoken unlock_code.bin
- Unlocking bootlodder will wipe your device so make all types of backup
After bootlodder is unlocked stay at bootlodder and flash this twrp recovery 2.8.7
To conclude i think there is no twrp for kitkat your model .
LINKS:
Download Link: https://drive.google.com/open?id=0B1rsNvL8ZF-RMHNab3VJNFVaNEE
TWRP discussion : http://forum.xda-developers.com/des...p-2-8-7-0-64bit-a51ul-a51tuhl-europe-t3287214
:good:
Flashing the stock recovery rom still doesn't allow me to enter recovery. Relocking the ROM and checking for software update tells me that my phone is up to date. (not sure if this has anything to do with having no recovery). Now the bootloader is stuck in 'relocked' mode, and trying to unlock it again fails because I cannot enter recovery.
I'm probably taking up too much of your time anyway, and since I can use my phone without any problems (just no root) I think I might as well give up at this point. Maybe i'll figure it out eventually after a lot of trial and error.
Regardless, thank you very much for the continued support!
Its your wish
h1dd3n_sn1p3r said:
Which ROM u running KK or LOLLI ?
TWRP for kk & Lo are in this ZIP
Download : https://mega.nz/#!yQ1RRZxK!fzcw9gdxgYd4Qd-8FTPoYuJroZ6RGHHkeb6381NncEo
how to flash here: https://www.youtube.com/watch?v=xsn6co4Ve6M
Click to expand...
Click to collapse
820n running LOLLlPOP rom . are these recoveries are compatible to flash on my device?
android201 said:
820n running LOLLlPOP rom . are these recoveries are compatible to flash on my device?
Click to expand...
Click to collapse
yes go ahead
BTW which you are going to flash ?
h1dd3n_sn1p3r said:
yes go ahead
BTW which you are going to flash ?
Click to expand...
Click to collapse
i need to flash again my device official rom or custom rom 820n a51_ul because it has a extraordinary screen saver. i need to remove it. i did factory reset but its still there.
android201 said:
i need to flash again my device official rom or custom rom 820n a51_ul because it has a extraordinary screen saver. i need to remove it. i did factory reset but its still there.
Click to expand...
Click to collapse
hmm ok
h1dd3n_sn1p3r said:
hmm ok
Click to expand...
Click to collapse
are these recovery compatible with the d820u ? i have a d820u running on lollipop with bootloader unlocked
edit :nvm i got twrp 2.8.7 working
Hi.
I seem to be having the same issue as the original poster - on the same model hardware, whenever I attempt to load into recovery, it appears the system starts loading it then immediately bails back to Fastboot mode. This occurs using the recovery image linked from this thread, as well as with various other recovery images that I've tried. Each recovery image loads into the phone without error, but every time the result is the same.
Otherwise the phone boots without issue and appears to operate normally. Note that I have successfully unlocked the boot partition.
I've included the output of "getvar all" below, however one thing that may be relevant that I have noticed is that when I load into HBoot there is a brief moment where it appears the phone is verifying *.zip images. It's too quick for me to get file names, but the only thing I can think of is that it looks like it's overwriting existing partitions with stock images every time HBoot loads. Is this a thing?
Any assistance would be appreciated.
Code:
# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.980.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT54DYC00362
(bootloader) imei: 355719061276677
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: OPTUS001
(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: a82a385a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
all: Done!
finished. total time: 0.007s
Hi This seems to be the same issue that I'm having. Getting bootloop on everything, when i select recovery it bootloops. I relocked the bootloader now i get errors trying to unlock. I've tried to fastboot new recovery but get Signature verify fail. I'm not sure what happened to it as a friend brought it like this. they said they did the official update then it went in to bootloop. The bootloader said "RELOCKED" So i presume they've already rooted this and put a custom recovery on but then its been deleted when they've done the official update to lollipop.
On bootloader it says Software status: Official
This is the dual sim 820n version. I've asked for help in a few threads but with no replys but came across this thread which more or less fits what my issue.
Please this is driving me mad now. Thanks
h1dd3n_sn1p3r said:
Whats you complete model number like 820U | 820n | 820Q | 820S
Here is Twrp recovery for kk https://mega.nz/#!zM8G2AwJ!6QH8eZYZ8aoe_ap_UGu1iLf_NnqsnD4bhHp2u42MH8k
Here is stock recovery for kk https://drive.google.com/file/d/0B2DumUOvI46KM2toeGR3QXpLYW8/view?pref=2&pli=1 [ for 820U ]
Code:
how to flash here [video guide: https://www.youtube.com/watch?v=xsn6co4Ve6M
More info :http://forum.xda-developers.com/desire-820/development/play-recovery-htc-desire-820-dual-sim-t3225782
Keep in mind to flash any custom recovery (twrp,cmw,philz touch) you need to have you bootlodder unlocked
If stock is not working can you may flash TWRP
Click to expand...
Click to collapse
Mine is 820q on kk can you send me the correct link as the given link did not work
Related
I Was following the guide > http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792 to update my firmware and CID which i successfully did. As per the tutorial, it mentioned that i should copy a ROM on sdcard before procedding. Which i did but amazingly the ARWWizard also flashed my SDCARD (? Not sure but my card was empty).
Anyways, I was able to boot into the OS (old) and i realized i need to install recovery. I issued
Code:
adb reboot bootloader
fastboot flash recovery <recovery_image>
I tried installing TWRP 2.8 but it remains stuck at "Entering Recovery", so i isntalled 2.7 and I was successfully in the recovery. There I wanted to cleaned everything, internal storage, cache, delvik cache etc (not microsd). And went on to menu to install OS from sdcard but it was empty.
I thought lets do the sideload with
Code:
adb sideload rom.zip
and got error Can not read rom.zip.
I changed the location of rom.zip to other location and did adb from that location but still no luck. I was under the impression that since i have installed recovery ... I can reboot ... I tried and now i am stuck at Android Boot loading screen ...
While on that screen, my computer shows that it is trying to install MTP drivers but it fails and hence now i can't use ADB to reboot or do anything.
Any help would be appreciated.
I answered you here!
Forsaked said:
I answered you here!
Click to expand...
Click to collapse
alright .. after struggling so much i am finally able to have my phone running. But i guess the ARUWizard didn't upgraded the firmware. The reason i am saying this is that I installed Viper4.1 ROM and it clearly stats in their FAQ that my WiFi wouldn't work if i don't have proper firmware.
Looking at this guide I am confused which firmware to install.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(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: 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: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
EddyOS said:
If you're using Viper, it's based on 4.16.401.10 so you need this FW package:
4.16.401.10_firmware.zip (rename it firmware.zip - not firmware.zip.zip!)
Flash it in RUU mode using fastboot flash zip firmware.zip. Once you've flashed the package it'll replace TWRP with the stock recovery so download TWRP again and flash when connected in the bootloader with fastboot flash recovery recovery.img and you're good to go
Click to expand...
Click to collapse
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
..alee said:
Thanks. One question
What do you mean by RUU Mode ? do you mean flashing the firmware like this
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
fastboot reboot bootloader
fastboot flash recovery twrp.img
I really appreciate the help you guys are providing
Click to expand...
Click to collapse
Very nearly right...
Code:
fastboot oem rebootRUU
fastboot flash zip fimrware.zip
[B]fastboot reboot-bootloader[/B]
fastboot flash recovery twrp.img
You missed the dash
The firmware flash might need to be done twice. If it says it's failed and reboots the unit, do the same command again to flash it but if it says complete then reboot the bootloader to flash TWRP
Thanks ...
I got it working but now there are two weird issues.
1. My camera doesn't work. Whenever i click on HTC Camera, it shows a black screen (as if camera view is blocked, I can see on screen buttons and options but black background).
2. My phone doesn't recognize the SD Card which i was using before.
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
EddyOS said:
Can you post your output from fastboot getvar all (removing your IMEI and serial number) again?
Click to expand...
Click to collapse
Just want to let you know that the camera issue is before installing this ROM. It was because of the camera that i decided to upgrade from 4.3 to 5.0 Android. The SD card issue has been resolved. Here is my fastboot command details
Code:
(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-OFF
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.044s
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
EddyOS said:
I'm guessing you flashed TWRP again? That explains why the main-version is blank. The rest seems to be in order so not sure what the issue is now
Click to expand...
Click to collapse
my main version is blank ever since I started upgrading my phone. Even if you look at the posts which posted 3 days before (before upgrading) they all had blank main-version.
True. If you are willing to try putting your phone back to 100% you could use the guide in my signature and then at least you'll be back to a point where it should all work
okay ... from your post it seems like only devices with HTC_* CID's can be restored to stock. Given that I am supercid, I can write whatever CID I Can but my original cid was VODP001. Do i have to worry about that ? Would your method work on my device as well ?
Super CID means you can flash anything so just try it. OK, it'll go back to the unbranded build as opposed to the Vodafone build but that's not a bad thing
Hello , After i update my phone to 5.0.1 wifi working but not for all websites ( i cant sign in to Apps Or Open Some websites that i can open in 3g ) ,i dont know why , sometimes it's not working ever , when i try to install venom rom i have a same problem , but when i revret back to 4.4.4 wifi back to work (SORRY FOR MY ENGLISH)
My Phone Info :
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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!
finished. total time: 0.019s
Thanks
ahmad_saadedein said:
Hello , After i update my phone to 5.0.1 wifi working but not for all websites ( i cant sign in to Apps Or Open Some websites that i can open in 3g ) ,i dont know why , sometimes it's not working ever , when i try to install venom rom i have a same problem , but when i revret back to 4.4.4 wifi back to work (SORRY FOR MY ENGLISH)
My Phone Info :
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.708.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B63000
(bootloader) cidnum: HTC__622
(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!
finished. total time: 0.019s
Thanks
Click to expand...
Click to collapse
Your firmware appears to be up to date. Are you using an older version recovery? Update to TWRP 2.8.4.0 or 2.8.5.0, then try flashing a Lollipop ROM again.
i have TWRP 2.8.5.0 ! , Thanks For your concern
When I said Factory Reset/Wipe data in stock recovery in other thread, I meant stock recovery not TWRP. Did you really do that ?
The next thing you can try is to flash the signed firmware again .. it may fix your problem too.
If you can't find one, I have that firmware.
ckpv5 said:
When I said Factory Reset/Wipe data in stock recovery in other thread, I meant stock recovery not TWRP. Did you really do that ?
The next thing you can try is to flash the signed firmware again .. it may fix your problem too.
If you can't find one, I have that firmware.
Click to expand...
Click to collapse
yes , i do it using a stock recovery but nothing happens , as i read i cant flash firmware because im still s-on
Thank you
ahmad_saadedein said:
.... i read i cant flash firmware because im still s-on
Thank you
Click to expand...
Click to collapse
You read wrongly. For S-On device, can flash only a signed firmware. For your device version you can flash an untouched firmware that I have here : http://forum.xda-developers.com/showpost.php?p=58769132&postcount=4591
1. Make a nandroid backup for the ROM that you have now (you need that later)
2. put your device in bootloader/fastboot mode
3. relock bootloader - fastboot oem lock
4. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.18.708.12_firmware.zip
fastboot flash zip 4.18.708.12_firmware.zip .....( again for the 2nd time)
fastboot reboot
5. check your wifi
6. If it's good then boot to bootloader, unlock bootloader with the unlock_code.bin
7. flash latest TWRP 2.8.5.0
8. restore your backup
If the wifi still no good ... try my backup that I linked above. If still no good ... I'm out of idea to help you.
ckpv5 said:
You read wrongly. For S-On device, can flash only a signed firmware. For your device version you can flash an untouched firmware that I have here : http://forum.xda-developers.com/showpost.php?p=58769132&postcount=4591
1. Make a nandroid backup for the ROM that you have now (you need that later)
2. put your device in bootloader/fastboot mode
3. relock bootloader - fastboot oem lock
4. run these commands
fastboot oem rebootRUU
fastboot flash zip 4.18.708.12_firmware.zip
fastboot flash zip 4.18.708.12_firmware.zip .....( again for the 2nd time)
fastboot reboot
5. check your wifi
6. If it's good then boot to bootloader, unlock bootloader with the unlock_code.bin
7. flash latest TWRP 2.8.5.0
8. restore your backup
If the wifi still no good ... try my backup that I linked above. If still no good ... I'm out of idea to help you.
Click to expand...
Click to collapse
I try This , im already using your nandroid backup , the problem still here , maybe it's about something related with wifi setting i get tired from this , anyway thank you very much for your help you are a great devloper
Hi,
Apologies in advance because I'm sure this is a very noob problem, but I was trying to update my M8 to lollipop and ended up messing it up somewhere. It was rooted before, S-Off, unlocked, using Android HD 4.4.4.
When I try to flash the Android HD Lollipop rom in TWRP from internal or external sdcard, or from USB OTG, the installer starts and looks successful until it gets to "Creating toolbox symlinks". After that it says "symlink: some symlinks failed"
When it finishes, it goes back into recovery and TWRP says "Successful"
When I go to reboot TWRP says it isn't rooted and asks if I'd like to root. Whether I say "yes" or "no" it reboots to a white HTC screen with a little lock at the bottom. The lock wasn't there when I started. After a few seconds the screen turns off then back on, then it goes into recovery.
If I try to install the update-supersu from internal or external card, or from USB OTG, in TWRP it says "success" and no errors, but then when I go to reboot it, it says "does not appear to be rooted" and asks if I'd like to root it. Whether I say yes or no it reboots, freezes, then boots into recovery and I start over.
In boot where it used to say "tampered" it now says "modified", and under that "unlocked", "s-off", a bunch of numbers that look important, but nothing in "OS-".
I can get into recovery and fastboot or hboot just fine. I have ADB, fastboot, and I think all the drivers I need on my laptop, and both recognize my phone when it's plugged in and I type "adb devices". I've tried like 10 different guides to push and flash and honestly too many commands to remember, but nothing that can get it to boot into a working rom.
To be honest, every single time I've tried to root something, I've broken something, but usually if I keep looking I can find the same problem and someone who's fixed it and figure it out, but I've been at it nearly 20 hours straight now and I just can't see what I'm missing (besides OS Dx)
If anyone knows what I've done and how to undo it, I'd be grateful for any advice.
Thanks,
Josh
*** I think I got the wrong firmware, but not sure how to find the right one without downloading them reandomly and checking the android-info***
Boot to bootloader/fastboot then run command fastboot getvar all
Post here the result (delete serial no. & imei no.)
Will see what we can do later
Your problem most probably is the old version of TWRP (2.7.0.2) that you use.
You should try 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware.
Sure
(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:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader)
(bootloader)
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(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.016s
Blue67982 said:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.213311491.A04G
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
So you have a AT&T device.
What actually you want to do because there is no lollipop update for AT&T yet.
Since your device is S-Off, you can change
CID : CWS__001 to 11111111
MID : 0P6B12000 to 0P6B10000
then flash a EU firmware.
Or you take any unsigned EU firmware.zip, open it with 7-zip and extract out the android-info.txt and edit this android-info.txt to include your CID and MID (use notepad++ for this), drag the modded android-info.txt into the unsigned firmware.zip
Flash this modded firmware, should work too.
And important thing about TWRP : 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware
Then you can install any of the lollipop Sense base custom ROM.
Thanks. I'll chug some coffee and give it a try.
Ok, I changed my CID and MID without too much trouble, but about "TWRP : 2.8.3.0 if you have a KitKat firmware and 2.8.5.0 if it is a Lollipop firmware", how can I tell which I have?
Oh, I used the ADB method if that matters.
After change of CID/MID, you need to flash firmware.zip in RUU mode not ADB.
Your current firmware is KitKat .. if you stick to it, you need 2.8.3.0
After you flash a 4.xx.xxx.x firmware - you need 2.8.5.0
Check this : http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Thanks for putting up with all the questions.
I just want to make sure I'm doing this correctly. I need to update the firmware to a 4x one, then twrp 2.8.5.0, then root and rom? I'm reading the guide you linked, but I'm not sure which firmware to use, for example it lists 5xxBase, then underneath it lists firmwares starting with 4xx.
Or does it not matter?
1. Update firmware, flash the widely use - 4.16.401.10
2. Flash TWRP 2.8.5.0
3. Install ROM
No need manual root because custom ROM is prerooted.
I got to go now .. be back in next 4 hrs
ckpv5 said:
flash the widely use - 4.16.401.10
Click to expand...
Click to collapse
TYSM!! That's what I was looking for
Ok, I updated the firmware and TWRP (I think), but when I try to do anything like flash a rom all the partitions come up as unmountable before the installer starts. I know I read something similar before so I'll try to find that.
\fastboot>fastboot getvar all
(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-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(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: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You don't seems be using the updated TWRP 2.8.5.0
Your fastboot shows that you may use the old 2.7.0.2
Download and install TWRP 2.8.5.0 - http://techerrata.com/browse/twrp2/m8
command fastboot flash recovery openrecovery-twrp-2.8.5.0-m8.img
Then boot to recovery - select wipe - advance - format data - yes
Go to reboot menu - select recovery (to reboot back to recovery
Select "Mount" menu - enable MTP
Transfer the ROM zip to either Internal Storage or MicroSD (if you have one)
Then try to install the ROM.zip
that's so weird...from within twrp the little info bar thing at the top says v2.8.5.0
Ill install again
Yeah .. unless you remove the (bootloader) version-main: info, TWRP 2.8.5.0 should not remove that after you flash the firmware.
Anyway ... try the other steps that I mentioned.
You did it man, you fixed the phone I thought I would have to throw away.
Thanks for answering so many noob quuestiuns
I owe you one
Blue67982 said:
You did it man, you fixed the phone I thought I would have to throw away.
Thanks for answering so many noob quuestiuns
I owe you one
Click to expand...
Click to collapse
Great :good::good:
You don't owe me anything ... just love to help
Since he had a at&t phone, why did you not tell him the change the cid to dev edition and run the ruu in fastboot mode, that wont have been easier?
toysoldierq said:
Since he had a at&t phone, why did you not tell him the change the cid to dev edition and run the ruu in fastboot mode, that wont have been easier?
Click to expand...
Click to collapse
Different ways to skin the same cat. There is nothing "wrong" with the solution that was used.
It worked, and now I know to make 100% sure I have the right versions of everything BEFORE I start, so I'm happy.
hye all
i have tried all the files available for desire 816 but dont access to custom recovery mode , phone unlocked and rooted.
phone infos :
version: 4.4.2
soft number 1.0.0.D816
SDK: 6.21
kernel 3.4.0
thanks in advance for any help
do you know what custom recovery is? Have you installed TWRP or CWM? if so, one sure way to enter recovery would be to connect your phone to pc and type this command in a command prompt console (CMD)
Adb reboot recovery
Click to expand...
Click to collapse
if you don't have proper ADB/Fastboot, you can get it form here
you also need to have proper htc drivers on your pc which can be installed by installing HTC sync manager.
but if you have unlocked and rooted your phone, you probably have all of these already.
thanks for reply, so twrp is installed properly, phone unlocked and rooted, when i install any of the custom recovery availables in TWRP or here, the phone dont enter on recovery mode, it shows a red message then return back to fastboot mode,
Or something is missing, or the recovery file is not good for this phone.
greetings
0rOShiMaRu said:
thanks for reply, so twrp is installed properly, phone unlocked and rooted, when i install any of the custom recovery availables in TWRP or here, the phone dont enter on recovery mode, it shows a red message then return back to fastboot mode,
Or something is missing, or the recovery file is not good for this phone.
greetings
Click to expand...
Click to collapse
TWRP IS a custom recovery. I don't know what you're trying to do.
are you trying to install a stock recovery(original hTC recovery without any modifications) in order to get lolipop OTA update? then maybe you have this red triangle error. if the stock recovery in that thread doesn'r help you, maybe you have a different device. you can type these codes in command prompt to see your phone info and then copy them here for us to see:
Code:
Adb reboot bootloader
then after restart
Code:
Fastboot getvar all
thx for reply
yes im trying to update the phone, i have tried to add a recovery to launch the OTA update but noway. So i wanted to install a full recovery for the 5.0 android system.
if you have a way to launch the ota update directly it will be very fine for me
informations
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.20.5352.19.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.55.1402.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HC48CWW03860
(bootloader) imei: 354011060222253
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a5_dugl
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9C90000
(bootloader) cidnum: HTCCN703
(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: 703d7086
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.133s
waiting for replies, thx
(bootloader) product: a5_dugl
(bootloader) modelid: 0P9C90000
(bootloader) cidnum: HTCCN703
your phone seems to be of a different variant than most of the stock recovery files found on XDA, so naturally they won't work on your device. you'll have to find the specific stock recovery for your variant with above IDs.
i really dont know from which country this phone is coming !! i am really lost !!
i downloaded the official update from htc usa support, and that recognize that phone have a different ID
pffffff
HTC One M8
Unlocked and S-off
From UK so with international network
Cyanogenmod 11 i think
Clockwork recovery
Soooo i bought the M8 secondhand with Cyanogenmod installed, however, i couldnt do any updates due to error status 7. i tried the normal fix (delete code which checked authorisation of phone) but to no avail. since then the error came back and i managed to get a different error on reboot: "root access possibly lost. fix?". I've cleared cache(s) and done a factory reset. No matter what i pressed it would be in a boot loop. I can still get to bootloader and recovery. then i tried to change the recovery to TWRP however when i try and fastboot, my device is not recognised by my laptop so i cannot add the ADB driver to the device.
sorry for sounding very vague / idiotic, i have no idea what i have done and no idea what i am doing to try and fix it. that means sadly i will need to be spoonfed the fix. if you need any more details or pictures of the problem let me know
thanks in advance
josborn42 said:
i couldnt do any updates due to error status 7. i tried the normal fix (delete code which checked authorisation of phone) but to no avail.
Click to expand...
Click to collapse
Are you trying to update to CM12.1? If so, the error is for a reason, and not to be bypassed in the way you describe.
If you are on an hboot older than 3.19, I don't think it will work with CM12 and 12.1. You'll need to update hboot (and rest of firmware, preferably) to proceed.
Also, CWM may be too old for CM12 as well.
josborn42 said:
then i tried to change the recovery to TWRP however when i try and fastboot, my device is not recognised by my laptop so i cannot add the ADB driver to the device.
Click to expand...
Click to collapse
Not sure what you mean here. Are you trying to install HTC Sync (and corresponding driver) by connecting the phone?
You can just do an XDA search for "simple adb" and you will find a couple really easy adb/fastboot installers.
how do i see what hboot i am on? and how would i update it?
i've installed HTC Sync but it doesn't recognise my phone being connected (so i cant view any files on the phone) and i've installed a simple ADB/fastboot but i can't see the driver option when trying to add it to my phone on Device manager. i have got to the stage whereby i have the ADB/fastboot folder and have the TWRP file in the same folder, just i cant get any further.
where would i begin getting to cyanogenmod 12.1, or would it be easier to revert back to a basic android os?
i know this is probably incredibly frustrating for you as i am a complete novice, but i greatly appreciate your help
i would post pictures to help but i cant as im a new member, i will when i can
josborn42 said:
i've installed HTC Sync but it doesn't recognise my phone being connected (so i cant view any files on the phone)
Click to expand...
Click to collapse
This in itself does not mean the phone is not connecting by fastboot. And fastboot is the important thing here, so we can update TWRP, etc.
Try rebooting into fastboot mode, and try the command and see if your phone's ID is returned: fastboot devices
If you don't get the phone's ID and just "waiting for device" you do indeed have some type of USB connectivity problem.
josborn42 said:
how do i see what hboot i am on? and how would i update it?
Click to expand...
Click to collapse
Boot into bootloader, andyour hboot number is listed near the top of the screen.
Since you are s-off, its fairly easy to update the firmware (and I would suggest to update all the firmware, not just hboot) by flashing the proper firmware.zip. But let's determine whether that is even the problem, before we worry about flashing firmwares.
hboot is: 3.16.0
also my phone is detected by my laptop so all is well there
i have installed a simple 15 second ADB file but am unsure how to proceed from here
josborn42 said:
hboot is: 3.16.0
Click to expand...
Click to collapse
Your firmware is very old, so will need to be updated to run CM12.1. Also, newer versions of TWRP will not run with your old hboot.
Do a fastboot getvar all, and post the output, but delete your IMEI and serial numbers (as these are private info). Need more details on the phone (particularly CID) in order to know how to proceed.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(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.107s
josborn42 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___001
(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.107s
Click to expand...
Click to collapse
I'm going to suggest WWE/International firmware. The updates are available way before O2 updates.
Download this firmware (it also includes TWRP2.8.4.0). Rename it to firmware.zip and place it into your fastboot folder.
Next, boot into fastboot and change your CID to superCID (it won't flash with the O2 CID)
fastboot devices to make sure you are connected (a bunch of letters and numbers/your serial# means you are)
fastboot oem rebootRUU (a black screen with the HTC logo means you are in RUU mode)
fastboot oem writecid 11111111 (eight ones) You are now superCID!
Now flash the firmware
fastboot flash zip firmware.zip
If you get "error 90 hboot pre-update" (and you probably will with how old your current firmware is) run the same command again and the firmware will flash properly. The first run only updated your hboot.
The process will stop at 75% to 90%. That's normal and gives you a chance to check your console output. The last few percentage is the reboot.
The bar will fill to 100% after you enter fastboot reboot-bootloader
That's it. Good luck!
thank you both so much! so now do i just download the appropriate cyanogenmod version and flash it over?
josborn42 said:
thank you both so much! so now do i just download the appropriate cyanogenmod version and flash it over?
Click to expand...
Click to collapse
Yes. But there are more ROMs out there as well. Try them out and find the one that suits your needs best.
hi there i have htc one m8 rooted s-on & software status is modified
i got a new update so i flashed the stock recovery then downloaded the update and pressed install
it was loading the update and suddenly the screen frozen on the htc ONE screen without responding
i tried the volume down + power button nothing happened then i tried volume up + power button
it reboots and freezes on the same screen - tried to remove the sim & sd card but nothing happened
what should i do plz ???
cid : htc_j15
build number : 4.16.401.10