[SOLVED] Installed Android Revolutions HD Rom stuck in Bootloop!! - HTC One X

Hi guys, I'm stuck in a bootloop with Android Revolution HD Rom installed, I took the risk and flashed it now I'm in a bootloop.
I'm pretty sure I just need a firmware update...
Can someone tell me what to do please!!!

Care to walk me through what you've done step by step?

SUPERUSER said:
Care to walk me through what you've done step by step?
Click to expand...
Click to collapse
Hi, yep. I've unlocked the bootloader installed twrp and rooted.....but all the twrps I've tried won't allow me to stick in a usb with a rom on....
So I stuck Android revolution HD on internal storage and flashed it from there except I'm now stuck in the bootloop.
I can adb/fastboot but I can't adb sideload as the pc says no devices attached when I boot into recovery when plugged into pc....
It's was on Orange UK but they are no longer so I wanted to wipe....
It would be OK if I could s-off and superCID but I can't so I'm stuck!!!

SUPERUSER said:
Care to walk me through what you've done step by step?
Click to expand...
Click to collapse
version: 0.5a
version-bootloader: 1.36.0000
version-baseband: 5.1204.163R.30
version-cpld: None
version-microp: None
version-main: 3.16.61.8
serialno: ***********
imei: ************
product: endeavoru
platform: HBOOT-T30S
modelid: PJ4610000
cidnum: ORANG001
battery-status: good
battery-voltage: 4156mV
devpower: 100
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0

Just to confirm some details.
Is this the rom you flashed?
https://forum.xda-developers.com/showthread.php?t=1562603
And this file is the one you flashed?
https://androidfilehost.com/?fid=24415232478675057
The recoveries used for this device is divided into new and old layout.
Android Revolution HD uses the old layout.
To be sure you use the old layout just keep using an old version of.
https://eu.dl.twrp.me/endeavoru/
So you would use twrp twrp-2.6.3.0-endeavoru.img.
All the other links starts with 3.0 and that is the new layout.
If you have all this in order.
And you remembered to wipe everything before flashing this rom?
If so then your problem would be solved by easily flashing the boot.img in fastboot which is the kernel.
We cannot touch the kernel from the recovery because there is no official way to s-off the one x.
So when you flash a rom you are only half way there with this particular device because you need to boot to hboot and go into fastboot mode.
On a computer open the rom archive Android_Revolution_HD-One_X_33.1.zip and extract boot.img.
Open a cmd in the same folder ( hold shift and right click and select Open command window here)
In the cmd type "fastboot flash boot boot.img" without the quotes.
If you do not have adb/fastboot installed get it here https://forum.xda-developers.com/showthread.php?t=2588979
It will install all tools you need and even the driver but you will need to manually select this driver if your computer does not see your one x.
But we'll take it from there when and if that happens.

SUPERUSER said:
Just to confirm some details.
Is this the rom you flashed?
https://forum.xda-developers.com/showthread.php?t=1562603
And this file is the one you flashed?
https://androidfilehost.com/?fid=24415232478675057
The recoveries used for this device is divided into new and old layout.
Android Revolution HD uses the old layout.
To be sure you use the old layout just keep using an old version of.
https://eu.dl.twrp.me/endeavoru/
So you would use twrp twrp-2.6.3.0-endeavoru.img.
All the other links starts with 3.0 and that is the new layout.
If you have all this in order.
And you remembered to wipe everything before flashing this rom?
If so then your problem would be solved by easily flashing the boot.img in fastboot which is the kernel.
We cannot touch the kernel from the recovery because there is no official way to s-off the one x.
So when you flash a rom you are only half way there with this particular device because you need to boot to hboot and go into fastboot mode.
On a computer open the rom archive Android_Revolution_HD-One_X_33.1.zip and extract boot.img.
Open a cmd in the same folder ( hold shift and right click and select Open command window here)
In the cmd type "fastboot flash boot boot.img" without the quotes.
If you do not have adb/fastboot installed get it here https://forum.xda-developers.com/showthread.php?t=2588979
It will install all tools you need and even the driver but you will need to manually select this driver if your computer does not see your one x.
But we'll take it from there when and if that happens.
Click to expand...
Click to collapse
Fantastic, the Phoenix rose from the ashes!!!!
Thank you very much :laugh:
Everything you said above was correct, I just did what you said and voila, working perfectly.

Related

Can't access custom recovery

My goal: Get CM 11 on my One X
What I've done so far: (using simplified filenames)
Unlocked bootloader via HTCdev
adb push cm11.zip /sdcard/
adb push gapp.zip /sdcard/
adb reboot bootloader
fastboot flash recovery clockwork.img
disconnect USB
selected "Recovery" from HBOOT menu.
Result: Stuck on white screen with HTC logo when accessing recovery.
(I can boot into stock ROM and use the phone, but not access custom recovery)
Might or might not be relevant:
I flashed boot.img from CDM11.zip first, that caused the device to hang at normal boot as well.
After quite a lot of googling, I found what I believe is the correct boot.img for my device, as it boots normally now (as long as I don't try to boot recovery)
If I flash (what I believe to be) stock recovery, I get the black screen with a red triangle on it.
Results from fastboot getvar all:
Code:
version: 0.5a
version-bootloader: 1.72.0000
version-baseband: 3.1204.171.33
version-cpld: None
version-microp: None
version-main: 2.18.401.2
serialno: FA2Cxxxxxxxx
imei: 3535670xxxxxx
product: enrc2b_u
platform: HBOOT-T30S
modelid: PM3511000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4101mV
devpower: 82
partition-layout: None
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: None
hbootpreupdate: 2
gencheckpt: 0
So, I think I've done enough searching to say that not many people have this exact problem.
Care to help me out by nudging me in the right direction?
Flash this recovery
https://www.dropbox.com/s/7zxfzbwewzq6hmq/twrp-recovery2.img
And also do the command after flashing :
Fastboot erase cache
Then try to enter it again.
Mr Hofs said:
Flash this recovery
https://www.dropbox.com/s/7zxfzbwewzq6hmq/twrp-recovery2.img
And also do the command after flashing :
Fastboot erase cache
Then try to enter it again.
Click to expand...
Click to collapse
Same result...
And I'm sorry that I didn't mention it earlier; I have tried a few different versions of CWM and TWRP all without success.
And now that I see the command, I also remember trying that one as well.
But for the record;
Code:
adb reboot bootloader
fastboot flash recovery OneX\twrp-recovery2.img
fastboot erase cache
disconnected USB
selected HBOOT
selected Recovery
Stuck on white screen with green HTC logo.
Rename the recovery name to just recovery.img and try
Fastboot flash recovery recovery.img
Fastboot erase cache
And make sure to use the original HTC usb cable and a 2.0 usb port (directly ....not via any hub or extension chord)
Mr Hofs said:
Rename the recovery name to just recovery.img and try
Fastboot flash recovery recovery.img
Fastboot erase cache
And make sure to use the original HTC usb cable and a 2.0 usb port (directly ....not via any hub or extension chord)
Click to expand...
Click to collapse
Still stuck on white screen with HTC logo when trying to access Recovery.
Ah CRAP !!!!!!! you have the HOX +......STOP flashing stuff from here immediately !!!!
Get the recoveries and roms from the hox+ section asap. That will help you
Mr Hofs said:
Ah CRAP !!!!!!! you have the HOX +......STOP flashing stuff from here immediately !!!!
Get the recoveries and roms from the hox+ section asap. That will help you
Click to expand...
Click to collapse
Holy crap! You're right!
When I look at the "About" section; it's a One X+ !
Good thing I didn't get the recovery in then, because then I'd be flashing ROMS in a minute!
THANKS for noticing!
Yeah just rechecked the posts, i firstly stopped reading at the hboot of 1.72 sorry ....should have seen it faster than this !

Can't Flash TWRP Recovery

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)

M8 won't boot

Sorry about any terminology...
Recently my htc one m8 stopped booting. I had rooted it a long time ago and had a ROM that was working fine for a long time. No recent changes.
On normal boot it sits on the white and green text 'htc' forever.
If I boot with power+down buttons I get to a hboot screen, but choosing 'recovery' takes me to a white screen small pink 'Entering Recovery' text. Nothing happens. To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
I can see the sdcard through a pc card reader and manipulate files. Is there any way to copy files manually so it will boot?
This is on Win 10, UK unlocked version of phone.
bt999 said:
To even get power+down screen to be available I had to move two zip files from root of sdcard which I guess were related to the custom rom, being 0P6BIMG.zip and M8-GPE-03-16-2015.zip
Click to expand...
Click to collapse
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
bt999 said:
I tried reinstalling twrp after downloading the latest .img file
fastboot command
c:\twrp>fastboot flash recovery twrp-3.0.2-0-m8.img
just says <waiting for device> whether on pink text screen or white 'htc'
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Fastboot clarification
redpoint73 said:
When you have a file named 0P6BIMG.zip, it will automatically try to install it every time you enter bootloader. Its an update or RUU of some sort, placed there by you, but exactly what is impossible to tell.
The other file is a ROM zip for a GPE ROM, which I would guess is the custom ROM you installed. It doesn't make a difference for this file not be on the SD card or not (bootloader will not try to install it automatically, and bootloader will function normally).
Are you in bootloader-fastboot mode when you run the command (which is required)? Meaning, FASTBOOT should be highlighted in red just under the green text on the bootloader screen. If not, just select using the vol buttons, and confirm using power button.
Click to expand...
Click to collapse
Thanks for your reply.
I guess the 0P6BIMG.zip file would explain why it was always slow to boot when things were working ok, if it was being reinstalled each time. I don't recall its purpose.
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Is there a log file that would show how far through the normal boot things get? I guess it is inaccessible until things work better.
bt999 said:
I wasn't in bootloader-fastboot mode when trying the fastboot command, but have tried it again.
When connected to an Ubuntu 16.04 machine the white on red text says 'fastboot usb', but ubuntu commandline fastboot flash ... gives same 'waiting for device'. When connected to Win 10 white/red text just says 'fastboot', if that is relevant. When I installed fastboot on Win 10 from instructions at http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 there is a note to remove Google drivers before installing new ones - I did not do this, not sure if relevant, but new driver install gave no errors.
Click to expand...
Click to collapse
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
bt999 said:
Is there a way to copy a new ROM image to the sdcard so that on 'normal' booting it gets detected and applied? Or to copy twrp somewhere manually?
Click to expand...
Click to collapse
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Old twrp
redpoint73 said:
Try going into Windows Device Manager, finding the device, and picking the option to manually select drivers, and select the generic Android MTP drivers. See if that helps fastboot connect.
Make sure you have HTC drivers (HTC Sync) installed as well. Try to re-install HTC Sync.
You can't flash a ROM, if TWRP isn't working properly. And there isn't a way to make one automatically flash upon normal boot, that I am aware.
I've seen some folks make 0P6BIMG.zip files for TWRP, which will install automatically when you boot to bootloader. But honestly, USB fastboot connectivity is a pretty vital thing to have working, and usually just a matter of right drivers and a good cable (and being in fastboot mode is a must), so shouldn't be that hard to troubleshoot.
Click to expand...
Click to collapse
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
bt999 said:
I have got a twrp running, unfortunately it says it is only compatible with bootloader 3.19 and above when I try to install the rom. I have 3.16.
Do you know where I can get an old twrp?
Thanks.
Click to expand...
Click to collapse
https://dl.twrp.me/m8/
twrp versions
xunholyx said:
https://dl.twrp.me/m8/
Click to expand...
Click to collapse
Thanks. I have now tried
twrp-2.7.0.1-m8.img twrp-2.7.1.0-m8.img twrp-2.8.7.0-m8.img
twrp-2.7.0.2-m8.img twrp-2.8.0.0-m8.img twrp-3.0.2-0-m8.img
The oldest ones don't run the newer ones work but I still get an error on attempting to install the custom ROM. I think I may be misinterpreting the error message. I now think it is telling me the custom ROM needs bootloader 3.19, rather than twrp not being able to run, i.e. twrp knows not to install the rom.
Message 'This package supports bootloader(s): 3.19.0.0000; this device has bootloader 3.16.0.0000'
Do you know how I can update my bootloader?
bt999 said:
Do you know how I can update my bootloader?
Click to expand...
Click to collapse
Post fastboot getvar all result without serial & imei no.
Without proper info, everyone is guessing what you actually need.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I found this thread http://forum.xda-developers.com/showthread.php?t=2696282 and went through the process with a zip linked from there , but I guess it was old and turned out to still be 3.16
Shouldn't HTC be distributing these files? Or my carrier?
You need to relock bootloader if not yet done.
Command :
fasboot oem lock
fastboot reboot-bootloader
Then follow this : http://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Put both files in your adb/fastboot folder.
(The guide was written for system-wide adb/fastboot)
Once completed, you can re unlock boorloader and install latest TWRP and install any ROM that you like, if you want to.
I have a working phone now, htc setup screens ended up with no google account prompts or apps, so I installed cwm nightlies and open-gapps hoping I would have full functionality, however gapps was rejected for not having enough internal storage.
I don't care whether htc or cwm but need gapps/play store. Is there anything you can suggest?
/Last reply lost..]I now have a working phone with cwm nightlies. Unfortunately open-gapps wont install saying not enough space on internal drive.
Any suggestions on how to clear space or to make HTC install Google accounts/store (it did not ask)?
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
bt999 said:
I have a working phone now.
RUU didn't install google app store, so I installed cwm nightlies. I got an error that there was not enough space on internal for open-gappps.
Is there a way to free up space?
Click to expand...
Click to collapse
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Solved
ckpv5 said:
I have no idea what cwm nightlies is ... but if you have this kind of error not enough internal space ... you need to format data (not wipe) in TWRP.
Install latest TWRP, select wipe - format data - yes ... reboot to recovery again, now you can install ROM.
Click to expand...
Click to collapse
I installed a mini gapps that had just Play Store then installed other apps manually through that.
Thank you all for your help, this is a well-informed forum.
For anyone reading one thing I learned was to run fastboot from Ubuntu/Linux with 'sudo' or else it will not connect, just says 'waiting for device'
ckpv5 said:
I have no idea what cwm nightlies is
Click to expand...
Click to collapse
He means CM, not CWM. Easy mistake to make (adding one letter) but the two are completely different things (Cyanogen Mod custom ROM versus Clockwork Mod custom recovery).

HTC with locked internal memory

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

How to get CID when computer can't detect phone?

So, after unsuccessfully flashing Lollipop to my HTC One X, I'm stuck. When I turn on the phone, I'm met with a looping "Resurrection Remix" logo that won't go away. I can boot into the CWM recovery menu, but any and all methods of restoring the phone via this menu have failed so far.
The main problem here is that my phone will only show up on my computer when I 'mount usb storage' through the recovery menu. When I try and run the 'fastboot getvar cid' command, though, it hangs on 'waiting for device' and nothing happens thereafter. I've seen that I need the correct CID so that I can get the right RUU for my phone....and even then, getting the right RUU seems to be difficult as well, with all the dead links I've seen scattered around.
I'm done with trying to get this new ROM to work, and I just want to go back to what I had on my phone. How the heck can I fix this one? I'll give you any information you need about the phone, but I just don't know how/what. Very new to all of this, and so very over my head!
Kind regards,
Jim.
I maybe wrong here as I'm not familiar with that ROM.
But your problem is wrong recovery. To install a lollipop ROM you need to use TWRP with New Layout.
CWM won't work.
You need to boot to bootloader to run fastboot command. While in recovery only adb command works.
There were multiple videos/tutorials that used this ROM with CWM, so that was why I used those 2 together. Anyways, I was indeed in fastboot when I was trying to get my CID.
In Resurrection Remix thread I read you need TWRP with new layout.
You should read the thread not some online videos/tutorials.
Try command fastboot getvar all
Also check your PC device driver show MyHtc not some warning
Simple steps to go :
1] Download Resurrection Remix 5.8.8 or any else of your choice
2] Download Twrp 3.0.2-0
-----Make sure you backup----
3]Open Twrp
4]Select Wipe
5] Advanced Wipe
6] Select everything
7] Wipe
8] Goto home of recovery
9] reboot to recovery again
10] Send the rom from pc to the phone
11] Flash!
12] Wait it to boot (first boot takes up to more than 15-45 mins)
:good:
Thank you ckpv5, I shall read threads in the future for sure. My device does show up as My HTC in Devince Manager, so it's seeing it there, just not in the cmd line.
Thanks DevUt. I had a look around for version 5.8.8 of Resurrection, but the only one I found was for a Lenovo device? Suffice it to say, I didn't want to use that one. I looked on the Resurrection site, and my device isn't actually listed at all....I then checked out CyanogenMod, and there IS a version available for the HTC One X. I think i'll go with this one. There is a very detailed wiki page on how to install it.
If (more like when) I run into any problems, i'll come back here!
Peaceful Jim said:
Thank you ckpv5, I shall read threads in the future for sure. My device does show up as My HTC in Devince Manager, so it's seeing it there, just not in the cmd line.
Thanks DevUt. I had a look around for version 5.8.8 of Resurrection, but the only one I found was for a Lenovo device? Suffice it to say, I didn't want to use that one. I looked on the Resurrection site, and my device isn't actually listed at all....I then checked out CyanogenMod, and there IS a version available for the HTC One X. I think i'll go with this one. There is a very detailed wiki page on how to install it.
If (more like when) I run into any problems, i'll come back here!
Click to expand...
Click to collapse
you can try mone CM12.1 it's pretty good!
I myself use Resurrection remix 5.5.9 (sorry it was 5.5.8)
And please use the thanks button
Hmm, well if you're using RR 5.5.9, maybe I'll go with that, since I can at least get your support with it!
I have some questions about your instructions. (My questions are in brackets)
1] Download Resurrection Remix 5.8.8 or any else of your choice (do i simply transfer the zip file to the phone?)
2] Download Twrp 3.0.2-0 (same as above)
-----Make sure you backup---- (Do i need to do this, since I have nothing on my phone?)
3]Open Twrp
4]Select Wipe
5] Advanced Wipe
6] Select everything
7] Wipe
8] Goto home of recovery
9] reboot to recovery again
10] Send the rom from pc to the phone
11] Flash! (How do I do this?)
12] Wait it to boot (first boot takes up to more than 15-45 mins)
Also, i'm trying to find RR 5.5.9 and TWRP 3.0.2-0 but all the ones i find are *example* download RR 5.5.9 for (insert phone model here)
Are they actually different? Or are RR 5.5.9 and TWRP 3.0.2-0 the same, no matter which phone?
Again, thank you for your assistance and patience!
Bump.
Bump. Could really use some help with this.
Peaceful Jim said:
Bump. Could really use some help with this.
Click to expand...
Click to collapse
Which help that you need ? If it's about the Resurrection Remix, unable to help.
First thing that we need to know whether your fastboot is working or not.
As I mentioned earlier, what happens when you type command fastboot getvar all after you connect your phone while in bootloader mode
(not hboot mode) ...
Here is mine as example ... can you get the same as these ?
(Of course with your device CID)
If possible then we can talk about installing TWRP with New Layout and ROM.
If not possible, you may need different set of HTC USB drivers.
Code:
E:\Desktop>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.5
(bootloader) serialno: [COLOR="Red"]removed[/COLOR]
(bootloader) imei: [COLOR="Red"]removed[/COLOR]
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) [B][COLOR="Red"]cidnum: HTC__044[/COLOR][/B]
(bootloader) battery-status: good
(bootloader) battery-voltage: 3744mV
(bootloader) devpower: 26
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.816s
Peaceful Jim said:
Hmm, well if you're using RR 5.5.9, maybe I'll go with that, since I can at least get your support with it!
I have some questions about your instructions. (My questions are in brackets)
1] Download Resurrection Remix 5.8.8 or any else of your choice (do i simply transfer the zip file to the phone?)
2] Download Twrp 3.0.2-0 (same as above)
-----Make sure you backup---- (Do i need to do this, since I have nothing on my phone?)
3]Open Twrp
4]Select Wipe
5] Advanced Wipe
6] Select everything
7] Wipe
8] Goto home of recovery
9] reboot to recovery again
10] Send the rom from pc to the phone
11] Flash! (How do I do this?)
12] Wait it to boot (first boot takes up to more than 15-45 mins)
Also, i'm trying to find RR 5.5.9 and TWRP 3.0.2-0 but all the ones i find are *example* download RR 5.5.9 for (insert phone model here)
Are they actually different? Or are RR 5.5.9 and TWRP 3.0.2-0 the same, no matter which phone?
Again, thank you for your assistance and patience!
Click to expand...
Click to collapse
BEFORE DOING THIS CHECK YOUR DRIVERS ,ADB CONNECTION AND FASTBOOT
Every rom and recovery are different for every Devices
You can search our forums and find out out huge collection
Backup is optional
Twrp 3 :: http://forum.xda-developers.com/htc-one-x/orig-development/twrp-htc-one-x-t3429300
You can chose any ROM that says NEW LAYOUT
P.S first convert to new layout
Flashing = Clicking on the install button ,selecting the zip , and sliding the bar to install it
Check the the thread I gave to see how to install recovery
And last when you install the in the 10] step you need to transfer the rom
And don't worry this is one time investment as you go new layout ,you don't need to do all this steps
ckpv5 said:
Which help that you need ? If it's about the Resurrection Remix, unable to help.
First thing that we need to know whether your fastboot is working or not.
As I mentioned earlier, what happens when you type command fastboot getvar all after you connect your phone while in bootloader mode
(not hboot mode) ...
Here is mine as example ... can you get the same as these ?
Click to expand...
Click to collapse
C:\Users\Jimmy\Desktop\fastboot>fastboot getvar all
(bootloader) version: 0.5a
(bootloader) version-bootloader: 1.73.0000
(bootloader) version-baseband: 5.1204.167.31
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.707.5
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: endeavoru
(bootloader) platform: HBOOT-T30S
(bootloader) modelid: PJ4610000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: low
(bootloader) battery-voltage: 3503mV
(bootloader) devpower: 2
(bootloader) partition-layout: None
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: None
(bootloader) hbootpreupdate: 2
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.876s
Peaceful Jim said:
(bootloader) cidnum: HTC__044
Click to expand...
Click to collapse
So you solved your first problem "How to get CID when computer can't detect phone?"
So what do you want to do next ? Back to stock as you mentioned on your first post ?
Peaceful Jim said:
I'm done with trying to get this new ROM to work, and I just want to go back to what I had on my phone. How the heck can I fix this one?
Click to expand...
Click to collapse
Or you want to install other ROM ?
Most lollipop ROMs require TWRP with New Layout. They won't work on CWM recovery.
Read this : http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
ckpv5 said:
So you solved your first problem "How to get CID when computer can't detect phone?"
So what do you want to do next ? Back to stock as you mentioned on your first post ?
Click to expand...
Click to collapse
Yes please! I just want my phone back to stock so I can use it again!
Peaceful Jim said:
Yes please! I just want my phone back to stock so I can use it again!
Click to expand...
Click to collapse
First - charge your device as your current battery-status is low.
Do you still have CWM recovery installed ? If yes .. just use it, transfer the stock ROM zip to your device after you mount usb storage while in recovery.
Download : https://www.androidfilehost.com/?w=files&flid=20860
You can use either one ... odexed is pure stock, deodexed is modified stock and both are non-rooted
After downloaded the stock ROM zip, extract out the boot.img
If you don't have CWM recovery installed, I suggest TWRP - use this one : https://www.androidfilehost.com/?fid=24438995911971082
fastboot flash recovery twrp2810-endeavoru-OldLayout.img
transfer the download stock ROM zip after you enable MTP (do it twice)
After you installed the ROM zip, boot to bootloader and install the extracted boot.img
fastboot flash boot boot.img
Reboot - done.
If you prefer the nandroid backup method, let me know then I'll upload my stock non-rooted nandroid backup (but this will take time)
ckpv5 said:
First - charge your device as your current battery-status is low.
If you don't have CWM recovery installed, I suggest TWRP - use this one : https://www.androidfilehost.com/?fid=24438995911971082
fastboot flash recovery twrp2810-endeavoru-OldLayout.img
transfer the download stock ROM zip after you enable MTP (do it twice)
After you installed the ROM zip, boot to bootloader and install the extracted boot.img
fastboot flash boot boot.img
Reboot - done.
Click to expand...
Click to collapse
I couldn't charge my phone simply by plugging it into the computer. It would always boot to the bootloader and never charge. However, I found a script that loads the bootloader, then turns the phone off and repeats this process. Somehow it charges the phone, just very, very slowly. Once it has 3.68v of battery, apparently that will be enough to flash a recovery onto it. So I will wait until it has charged before I try your instructions.
ckpv5 said:
fastboot flash recovery twrp2810-endeavoru-OldLayout.img
Click to expand...
Click to collapse
I get the following message:
C:\Users\Jimmy\Desktop\fastboot>fastboot flash recovery twrp2810-endeavoru-OldLayout.img
sending 'recovery' (7720 KB)...
OKAY [ 0.941s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.145s
Is your bootloader relocked ? You need unlocked bootloader to fastboot flash recovery.
You not yet answer my previous question.. do you still have CWM currently installed ? If yes, just use CWM to install the ROM zip.
ckpv5 said:
Is your bootloader relocked ? You need unlocked bootloader to fastboot flash recovery.
You not yet answer my previous question.. do you still have CWM currently installed ? If yes, just use CWM to install the ROM zip.
Click to expand...
Click to collapse
It must be relocked. I will unlock it now. And sorry, I don't still have CWM installed. That's why i'm trying to put TWRP on there now

Categories

Resources