Related
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
Has anyone successfully installed TWRP 2.6.3.3 (http://techerrata.com/browse/twrp2/m7) on your HTC One? I have tried all three methods on installing it and I can't seem to get it to stick on my phone.
Method one: Goo.im app
From the menu, selecting Install OpenRecoveryScript and selecting Yes results in No recoveries were found for your device.
Method two: ADB / Terminal
Opened up an ADB shell and used dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 which successfully installed it. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Method three: Fastboot
Booting into the bootloader and selecting the fastboot option in order to run fastboot flash recovery recoveryfilename.img successfully installed. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Holding volume down + power and selecting Recovery from the bootloader also reboots to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
No idea how to get this installation to stick. Can anyone help out?
the twrp for m7 doesn't work.
the twrp for m7vzw is the one you need.
raphytaffy said:
Has anyone successfully installed TWRP 2.6.3.3 (http://techerrata.com/browse/twrp2/m7) on your HTC One? I have tried all three methods on installing it and I can't seem to get it to stick on my phone.
Method one: Goo.im app
From the menu, selecting Install OpenRecoveryScript and selecting Yes results in No recoveries were found for your device.
Method two: ADB / Terminal
Opened up an ADB shell and used dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p34 which successfully installed it. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Method three: Fastboot
Booting into the bootloader and selecting the fastboot option in order to run fastboot flash recovery recoveryfilename.img successfully installed. Rebooting to recovery goes to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
Holding volume down + power and selecting Recovery from the bootloader also reboots to the HTC screen that says Entering recovery and then reboots the device for a normal startup.
No idea how to get this installation to stick. Can anyone help out?
Click to expand...
Click to collapse
I used Flashify from the Play Store and it worked perfectly. The recovery held and was able to flash CM11. My fastboot has been screwed ever since I upgraded to Win8.1 so Ive been using that app as an alternative.
EDIT- Using the correct one as the previous post alluded to would also be a great idea. I didn't even catch that.
wiredout46 said:
the twrp for m7 doesn't work.
the twrp for m7vzw is the one you need.
Click to expand...
Click to collapse
Ah thanks, didn't even notice that. Working great now. If anyone comes to this thread looking for the m7vzw image, it can be found here: http://goo.im/devs/Flyhalf205/M7VZW
raphytaffy said:
Ah thanks, didn't even notice that. Working great now. If anyone comes to this thread looking for the m7vzw image, it can be found here: http://goo.im/devs/Flyhalf205/M7VZW
Click to expand...
Click to collapse
2.6.3.3 is in the verizon htc one original development subforum. just flashed it and it works fine.
Guys help! Installed TWRP 2.6.3.3. specifically for installation Maximus HD after installation did WIPE and accidentally formatted storage on which lay installer Maximus 30 HD, how do I copy installer again on storage, because mode Bootloader - Fastboot USB can not get access to it?
How come I can't find VZW TWRP 2.6.3.3?
and only can find 2.6.3.4?
sorry, just curious
andybones said:
How come I can't find VZW TWRP 2.6.3.3?
and only can find 2.6.3.4?
sorry, just curious
Click to expand...
Click to collapse
2.6.3.3 had the charging bug no?
if you need it, i have a copy of it.
Problem
Hey
I was flashing my htc to CM11 and it says that flash was successful, but now my htc one stuck when you try to power on it says only HTC quietly brilliant and wouldnt go on. What should I do ?
peca_slo said:
Hey
I was flashing my htc to CM11 and it says that flash was successful, but now my htc one stuck when you try to power on it says only HTC quietly brilliant and wouldnt go on. What should I do ?
Click to expand...
Click to collapse
Did you wipe data before or after flashing?
Flyhalf205 said:
Did you wipe data before or after flashing?
Click to expand...
Click to collapse
yes i did i have rot the cm10.2 but it stuck on logo screen of cm
peca_slo said:
yes i did i have rot the cm10.2 but it stuck on logo screen of cm
Click to expand...
Click to collapse
You did flash the Verizon recovery and Verizon rom?
Flyhalf205 said:
You did flash the Verizon recovery and Verizon rom?
Click to expand...
Click to collapse
Yes I did but I think this is not a good verzion for me cuz i have m7-ul model, but now I can do nothing with the phone. It would be good if i could get it back to stock
peca_slo said:
Yes I did but I think this is not a good verzion for me cuz i have m7-ul model, but now I can do nothing with the phone. It would be good if i could get it back to stock
Click to expand...
Click to collapse
Might be better to go to the ul variant thread at http://forum.xda-developers.com/htc-one
Can't Flash TWRP after installing MaximusHD
So I am a noob at this stuff and successfully flashed TWRP 2.6.3.3. I installed the MaxHD ROM shortly after following all instructions that I could find. I ran into bootloop and had to revert to an old firmware then flashed the current firmware and viola MaxHD booted right up. However, now I can not flash TWRP back as my recovery. Everytime I flash it and go into recovery it goes into MaxHD ROM. If anyone has any ideas they are much appreciated.
Also, I have read for over three weeks on these boards before posting even my first post so I have tried to research the problem if anyone was wondering that.
Jaayyrod said:
So I am a noob at this stuff and successfully flashed TWRP 2.6.3.3. I installed the MaxHD ROM shortly after following all instructions that I could find. I ran into bootloop and had to revert to an old firmware then flashed the current firmware and viola MaxHD booted right up. However, now I can not flash TWRP back as my recovery. Everytime I flash it and go into recovery it goes into MaxHD ROM. If anyone has any ideas they are much appreciated.
Also, I have read for over three weeks on these boards before posting even my first post so I have tried to research the problem if anyone was wondering that.
Click to expand...
Click to collapse
Is MaxHD a Verizon rom? That could be an issue if it's not. Also, the latest TWRP is 2.7.0.8. Haven't had any issues with it. Are you flashing it with fastboot commands? You might try the app Flashify.
Sent from my HTC6500LVW using Tapatalk
brholt6 said:
Is MaxHD a Verizon rom? That could be an issue if it's not. Also, the latest TWRP is 2.7.0.8. Haven't had any issues with it. Are you flashing it with fastboot commands? You might try the app Flashify.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
Good call...it is not for the Verizon HTC One. Thanks much.
It doesn't say it's not in the write up about the ROM...I had to dig into the replies to see if anyone else asked.
Hey there. So I'm new to XDA but not so much to flashing and what not. I often, however, do dumb tests that fail and brick my phone, but I always get it back. This one is a little tougher. Here are the details:
-HTC One (M8) T-Mobile
-Phone was unlocked and rooted (still unlocked, not sure about rooted), but S-On.
-Tried flashing a kernel with S-On. Turned out to be packaged in a recovery. Didn't go so well. Turning the device on always went straight to Fastboot mode.
-Eventually got Philz recovery installed. Tried sideloading a nandroid backup. No avail. Still booting straight to fastboot.
Any ideas? Not a genius, but I know my way around. Is there any 100% complete refresh coming straight from Fastboot?
What exactly did you try to flash?
Sent from my HTC One_M8 using Tapatalk
djmatt604 said:
What exactly did you try to flash?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
The new OTA update first. When that didn't work, I tried flashing the stock kernel back.
Go here, read, try it.
Look at last few posts as well concerning tmo
http://forum.xda-developers.com/showthread.php?p=52242287
umjammerlammy said:
Go here, read, try it.
Look at last few posts as well concerning tmo
http://forum.xda-developers.com/showthread.php?p=52242287
Click to expand...
Click to collapse
I haven't read the thread in that link, but in my experience when it boots straight to recovery it means the boot image is corrupt or missing. Not sure if you can do this with s-on, but to get back to normal I flashed twrp then downloaded and flashed a stock nandroid backup, then flashed an OTA via TWRP. After that everything was back to normal.
ashyx said:
I haven't read the thread in that link, but in my experience when it boots straight to recovery it means the boot image is corrupt or missing. Not sure if you can do this with s-on, but to get back to normal I flashed twrp then downloaded and flashed a stock nandroid backup, then flashed an OTA via TWRP. After that everything was back to normal.
Click to expand...
Click to collapse
Ah, yes.
This also would work.
Most likely he's got OS-
I was trying to convert my 5.0.1 GPE (already converted a couple months ago) back to Sense using the MaximusHD ROM and following the Youtube guide below.
All went well until I flashed firmware 1.54.401.5, found in this thread (http://forum.xda-developers.com/showthread.php?t=2733523). Now, the phone only reboots to the red exclamation mark every few minutes and the only thing I can do is Volume up + Power into the stock Android recovery. I'm not sure if it's possible to even power off since it only reboots to the red exclamation. ADB also does not detect the device in stock recovery, although the "device connected" tone plays through my PC speakers
Is there any solution to this? Any help would be appreciated.
Rango85 said:
I was trying to convert my 5.0.1 GPE (already converted a couple months ago) back to Sense using the MaximusHD ROM and following the Youtube guide below.
All went well until I flashed firmware 1.54.401.5, found in this thread (http://forum.xda-developers.com/showthread.php?t=2733523). Now, the phone only reboots to the red exclamation mark every few minutes and the only thing I can do is Volume up + Power into the stock Android recovery. I'm not sure if it's possible to even power off since it only reboots to the red exclamation. ADB also does not detect the device in stock recovery, although the "device connected" tone plays through my PC speakers
Is there any solution to this? Any help would be appreciated.
Click to expand...
Click to collapse
Red eclamation mark is stock recovery, volume up and power to access the menu, so its normal, complete the rest of returning to stock, just follow that guide, not the youtube video.
After firmware flash
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP recovery - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
Seanie280672 said:
Red eclamation mark is stock recovery, so its normal, complete the rest of returning to stock, just follow that guide, not the youtube video.
After firmware flash
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
Click to expand...
Click to collapse
How do I get into bootloader if the phone is constantly boot looping to a red exclamation?
Rango85 said:
How do I get into bootloader if the phone is constantly boot looping?
Click to expand...
Click to collapse
just hold volume down + volume up + power until the phone goes off, takes about 15 to 20 seconds to go off, then quickly release all 3 buttons and hold volume down only until in the phone boots to the bootloader.
Seanie280672 said:
just hold volume down + volume up + power until the phone goes off, takes about 15 to 20 seconds to go off, then quickly release all 3 buttons and hold volume down only until in the phone boots to the bootloader.
Click to expand...
Click to collapse
It worked! Now in bootloader, gonna flash recovery now and post an update.
Seanie280672 said:
just hold volume down + volume up + power until the phone goes off, takes about 15 to 20 seconds to go off, then quickly release all 3 buttons and hold volume down only until in the phone boots to the bootloader.
Click to expand...
Click to collapse
Ok, I flashed the latest TWRP file (twrp-2.8.6.0-m8.img) in Fastboot but when I try to boot into TWRP, it stalls on the "Entering Recovery" screen. Any ideas as to what is causing this?
Rango85 said:
Ok, I flashed the latest TWRP file (twrp-2.8.6.0-m8.img) in Fastboot but when I try to boot into TWRP, it stalls on the "Entering Recovery" screen. Any ideas as to what is causing this?
Click to expand...
Click to collapse
fastboot flash recovery recovery name.img
fastboot erase cache
fastboot reboot-bootloader
Now try enter recovery again.
Seanie280672 said:
fastboot flash recovery recovery name.img
fastboot erase cache
fastboot reboot-bootloader
Now try enter recovery again.
Click to expand...
Click to collapse
Same problem . I can, however, browse my internal storage and micro sd card on my PC in the stalled "Entering Recovery" screen. I can try to flash a stock recovery and then re-try flashing TWRP?
Or are there any alternative methods I can use to get a working OS installed?
Rango85 said:
Same problem . I can, however, browse my internal storage and micro sd card on my PC in the stalled "Entering Recovery" screen. Should I flash a stock recovery and re-try flashing TWRP?
Or are there any alternative methods I can use to get a working OS installed?
Click to expand...
Click to collapse
Did you factory reset in stock recovery ?
Seanie280672 said:
Did you factory reset in stock recovery ?
Click to expand...
Click to collapse
Yes, I'm afraid.
Rango85 said:
Yes, I'm afraid.
Click to expand...
Click to collapse
Strange, try another version of twrp, like the one recommended 2.7.?.?
Thanks man, v2.7.0.2 worked Doing a full factory reset now and will keep you updated.
Ok, update: After a lengthy 1st reboot after the install, I'm finally running the ROM . However, the WiFi doesn't seem to work as well as the camera.
Any solutions to this?
Rango85 said:
Thanks man, v2.7.0.2 worked Doing a full factory reset now and will keep you updated.
Ok, update: After a lengthy 1st reboot after the install, I'm finally running the ROM . However, the WiFi doesn't seem to work as well as the camera.
Any solutions to this?
Click to expand...
Click to collapse
First of all, looks like the newer twrp didn't work due to the old first edition firmware and I would say if you have flashed a lollipop rom, it's the same problem, the old 1xxxxx firmware, as your s-off, just update your firmware, I'd recommend flashing a 2xxxx package first, then a 3xxxxx then 4xxxxxx you will then have to flash the latest version of twrp as you'll have stock recovery back on your phone.
Firmware is here -
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
Seanie280672 said:
First of all, looks like the newer twrp didn't work due to the old first edition firmware and I would say if you have flashed a lollipop rom, it's the same problem, the old 1xxxxx firmware, as your s-off, just update your firmware, I'd recommend flashing a 2xxxx package first, then a 3xxxxx then 4xxxxxx you will then have to flash the latest version of twrp as you'll have stock recovery back on your phone.
Firmware is here -
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One_M8/401/
Click to expand...
Click to collapse
I ended up installing a stock rooted Lollipop 5.1 ROM (http://forum.xda-developers.com/showthread.php?t=2706441) instead of MaximusHD. Camera is now functional and everything appears to run fine EXCEPT for the WiFi which simply won't turn on to scan available networks. Might update the firmware to 4xxxxxxx a bit later, but wouldn't that wipe the OS again?
Rango85 said:
I ended up installing a stock Lollipop 5.1 ROM (http://forum.xda-developers.com/showthread.php?t=2706441) instead of MaximusHD. Camera is now functional and everything appears to run fine EXCEPT for the WiFi which simply won't turn on to scan available networks. Might update the firmware to 4xxxxxxx a bit later, but wouldn't that wipe the OS again?
Click to expand...
Click to collapse
If you ran a stock ruu then your firmware should of gone to the latest, just noticed you ran a gpe ruu, I thought you were trying to get back to sense ?
Seanie280672 said:
If you ran a stock ruu then your firmware should of gone to the latest, just noticed you ran a gpe ruu, I thought you were trying to get back to sense ?
Click to expand...
Click to collapse
I converted to GPE RUU w/ OTA updates from stock Sense back in January of this year. Only yesterday I've decided to convert back to Sense using a ROM based on it (MaximusHD in this case) and ran into these problems. I then installed a 5.1 ROM instead (not 5.1 RUU) from graffix's thread last night when I installed the TWRP 2.7.
So correct me if I'm wrong, the method is (in bootloader):
fastboot oem rebootRUU
Click to expand...
Click to collapse
then
fastboot flash zip 4.16.401.10.zip
Click to expand...
Click to collapse
Correct?
Rango85 said:
I converted to GPE RUU w/ OTA updates from stock Sense back in January of this year. Only yesterday I've decided to convert back to Sense using a ROM based on it (MaximusHD in this case) and ran into these problems. I then installed a 5.1 ROM instead (not 5.1 RUU) from graffix's thread last night when I installed the TWRP 2.7.
So correct me if I'm wrong, the method is (in bootloader):
then
Correct?
Click to expand...
Click to collapse
Yes that's correct, but don't forget to run the flash command twice as the first time will fail, however, that is a sense firmware not a gpe firmware.
You were doing alright with your convert back to sense and just needed to flash the latest firmware to bring your phone up to speed.
Seanie280672 said:
Yes that's correct, but don't forget to run the flash command twice as the first time will fail, however, that is a sense firmware not a gpe firmware.
You were doing alright with your convert back to sense and just needed to flash the latest firmware to bring your phone up to speed.
Click to expand...
Click to collapse
I understand, but if I want to use a 5.1 GPE ROM (like http://forum.xda-developers.com/showthread.php?t=2706441); is it ok to use the 4.16.401.10 firmware or would I need another GPE specific firmware?
Rango85 said:
I understand, but if I want to use a 5.1 GPE ROM (like http://forum.xda-developers.com/showthread.php?t=2706441); is it ok to use the 4.16.401.10 firmware or would I need another GPE specific firmware?
Click to expand...
Click to collapse
I'd recommend the gpe firmware.
Seanie280672 said:
I'd recommend the gpe firmware.
Click to expand...
Click to collapse
Is there any link to the GPE firmware? There's so many files when I do a search that I don't know which specific one is needed.
EDIT 1: 4.16.401.10 seemed to work fine and I also managed to update to the latest TWRP recovery.
EDIT 2: The OS took quite some time to reboot after the first install but I'm inside 5.1 now and WiFi seems to work
So I was flashing a new rom (ICE Rom) for my htc m9. I flashed it without wiping the data and the process was successful without any errors. When i tried to reboot the phone it took me to the bootloader. All i could do was switch between recovery, bootloader and download mode. I tried to reflash the rom but the recovery kept restarting as soon as i press the button to flash, as if it was crashing. I thought, maybe if i update the recovery i could flash the zip. I tried to update recovery from bootloader but i couldn't since my device is S-ON. So being me, a gigantic wannabe android dev, went to the RUU and flashed the recovery img. And now when I try to access the recovery it gives me an error, "Failed to boot to recovery mode". I also believe that i might have accidentally deleted the OS, but I am not sure about that. Really need HELP. PLEASE.
Summary:
HTC M9
Unlocked
S-ON
Cant access recovery
Can access RUU, Bootloader, Download mode.
-------------------------------------------------------
Edit: I flashed the oldest possible twrp recovery image and was able to access the recovery after that. Only need to find a way to fix the other problem.
What is your firmware version? If you tried to install a Marshmallow based ROM without upgrading the firmware, that might explain your symptoms.
computerslayer said:
What is your firmware version? If you tried to install a Marshmallow based ROM without upgrading the firmware, that might explain your symptoms.
Click to expand...
Click to collapse
I am not sure about the firmware version but I flashed a updated version of my previous rom, and now i can boot normally. Not sure what the issue was. Both the roms are marshmallow. Any ideas what the problem could have been?
Yea. Messed up boot and recovery cache versions, as well as maybe a broken recovery partition.
You messaged me in private saying you had the same issue as the other dude. If that was the case, he has a bad NAND chip pretty sure.
For now, I doubt that is the case on your phone. However, should you end up with a broken recovery that wasn't flashed fully or was and then went to sh!t later, that could be an indicator for a bad NAND too. Could. It can also be a number of other things like just bad flashing practice, bad flashing hardware (cable, ports, drivers, incompatible controller chips...) etc.
If I were you, I would see that I get my hands on a good, current RUU and run that.
Either as zip, which I would flash by using an SDCard, or by exe, which I would run on my PC with the phone connected and working drivers. The drivers are most safely obtained by installing HTC Sync Manager from here: http://www.htc.com/us/software/htc-sync-manager/.
US RUU's you will find here: http://www.htc.com/us/support/rom-downloads.html
For any other RUU, non-US, you will need to dig through XDA, Google Search, known sites such as AFH, Androidruu.com, ir-files....
The RUU would even out all partitions and get them into a reliable stock state. Then you could reflash TWRP afterwards and then a ROM. Viper preferably. Because that is my Team and I helped you
nukerdude50 said:
I am not sure about the firmware version but I flashed a updated version of my previous rom, and now i can boot normally. Not sure what the issue was. Both the roms are marshmallow. Any ideas what the problem could have been?
Click to expand...
Click to collapse
Bad flash, double check md5 and filesizes.
Beamed in by telepathy.