Related
Hi, I'm kinda hoping someone can help me here... (apology's early on for the rambling)
My HOX is running the factory ROM of ICS, but the bootloader was unlocked. Yesterday, I was going to flash the JB RUU on to it. So, following the steps found on XDA (somewhere, cannot remember where) I tried flashing the new firmware.zip on to it first. The first steps being to relock the bootloader using 'fastboot oem lock' (or something like that)... The bootloader relocked and I 'believe' the firmware.zip flash was succesful.
I then tried running the JB RUU, but it failed, leaving me on ICS.
So I decided to stick a custom ROM back on to it, which mean me reflashing the Unlock_code.bin... Once flashed, my phone went through the usual official htc 'are you sure you want to unlock bootloader, etc...' jargon... However, my Fastboot said it had failed.
I then tried to go back in to Fastboot / recovery (volume down + power) but the phone just boots up. I have also tried 'adb reboot recovery' but my phone shuts down and then I get a black screen, with a phone and red triangle / warning sign...
My phone will boot up (and appears) to work normally, but I am now unable to enter recovery to flash anything new on to it.
Please can someone help me here....
Go to settings, power and turn the fastboot option off.
Then you should be able to go to bootloader using the power+vol thing
Also, you could go to developer, in settings, and enable the usb debug stuff
then try adb reboot bootloader
Should work as well
Did u also flashed a stock recovery ?
When you can enter the bootloader check if it's unlocked now and reflash the cwm 5.8.4.0 recovery and also do
Fastboot erase cache
The red triangle is the stock recovery which will have been flashed in the firmware.zip you previously installed.
Instead of adb reboot recovery
Do
adb reboot bootloader
It should take you straight to hboot
Sent from my EndeavorU using xda app-developers app
bagofcrap24 said:
The red triangle is the stock recovery which will have been flashed in the firmware.zip you previously installed.
Click to expand...
Click to collapse
No, firmware is hboot and recovery is recovery.
---------- Post added at 01:05 AM ---------- Previous post was at 01:04 AM ----------
Squid2883 said:
The bootloader relocked and I 'believe' the firmware.zip flash was succesful.
Click to expand...
Click to collapse
So what's your hboot version?
D/l Android Revolution HD 22.0 and boot.img 0.1 for Android Revolution HD 22. ,
I installed HTC drivers on PC, followed instructions below
1. Turn OFF the device
2. Turn ON the device in bootloader mode (hold power + vol down)
3. Enter fastboot mode using navigation keys
4. Connect the device to PC via USB cable
5. Double click on 'install-boot-windows.bat'.
6. Enter recovery and flashed Android Revolution HD ROM
When finished it said Rom was flashed successfully I rebooted, it went to splash screen and went no further.
I tried re installing the Rom again same result I left it over nite still on splash screen in the morning.
I completely wiped phone clean, restored to factory default re installed Rom, put phone in fast boot and tried to flash extracted boot img with no success.
USB storage wont mount in recovery, it comes up with E: Unable to open ums lunfile (no such file or directory)
sd card wont mount so due to not having removable sd card on this device I cant put any other roms or backup files on phone
Any help would be appreciated
Phone info is
Recovery Clockwork mod v5.8.2.7
Unlocked
Endeavoru PVT ship s-on RL
HBOOT-0.43.0000
:crying:
Your hboot needs to be upgraded.. Were on ics when u rooted and flashed ARHD 22.0 directly? Jb roms dont work on Hboot 0.43
http://forum.xda-developers.com/showthread.php?t=2049864
---------- Post added at 09:02 AM ---------- Previous post was at 09:01 AM ----------
hawkinau said:
D/l Android Revolution HD 22.0 and boot.img 0.1 for Android Revolution HD 22. ,
I installed HTC drivers on PC, followed instructions below
1. Turn OFF the device
2. Turn ON the device in bootloader mode (hold power + vol down)
3. Enter fastboot mode using navigation keys
4. Connect the device to PC via USB cable
5. Double click on 'install-boot-windows.bat'.
6. Enter recovery and flashed Android Revolution HD ROM
When finished it said Rom was flashed successfully I rebooted, it went to splash screen and went no further.
I tried re installing the Rom again same result I left it over nite still on splash screen in the morning.
I completely wiped phone clean, restored to factory default re installed Rom, put phone in fast boot and tried to flash extracted boot img with no success.
USB storage wont mount in recovery, it comes up with E: Unable to open ums lunfile (no such file or directory)
sd card wont mount so due to not having removable sd card on this device I cant put any other roms or backup files on phone
Any help would be appreciated
Phone info is
Recovery Clockwork mod v5.8.2.7
Unlocked
Endeavoru PVT ship s-on RL
HBOOT-0.43.0000
:crying:
Click to expand...
Click to collapse
Your hboot needs to be upgraded.. Were u on ics when u rooted and flashed ARHD 22.0 directly? Jb roms dont work on Hboot 0.43
http://forum.xda-developers.com/showthread.php?t=2049864
daninantro said:
Your hboot needs to be upgraded.. Were on ics when u rooted and flashed ARHD 22.0 directly? Jb roms dont work on Hboot 0.43
http://forum.xda-developers.com/showthread.php?t=2049864
---------- Post added at 09:02 AM ---------- Previous post was at 09:01 AM ----------
Your hboot needs to be upgraded.. Were u on ics when u rooted and flashed ARHD 22.0 directly? Jb roms dont work on Hboot 0.43
http://forum.xda-developers.com/showthread.php?t=2049864
Click to expand...
Click to collapse
LOL, u know that did cross my mind but was told it should be ok, obviously it isn't ok so now I'm of to upgrade my Hboot. and yes I was on ICS
However do u know which version of HBOOT I can upgrade to with out having to make sure the CID# is right etc
Thanks a million will let u know the outcome. :laugh:
daninantro said:
Your hboot needs to be upgraded.. Were on ics when u rooted and flashed ARHD 22.0 directly? Jb roms dont work on Hboot 0.43
http://forum.xda-developers.com/showthread.php?t=2049864
---------- Post added at 09:02 AM ---------- Previous post was at 09:01 AM ----------
Your hboot needs to be upgraded.. Were u on ics when u rooted and flashed ARHD 22.0 directly? Jb roms dont work on Hboot 0.43
http://forum.xda-developers.com/showthread.php?t=2049864
Click to expand...
Click to collapse
hawkinau said:
LOL, u know that did cross my mind but was told it should be ok, obviously it isn't ok so now I'm of to upgrade my Hboot. and yes I was on ICS
However do u know which version of HBOOT I can upgrade to with out having to make sure the CID# is right etc
Thanks a million will let u know the outcome. :laugh:
Click to expand...
Click to collapse
After a little more research I see that u can find the CID# with the phone booted, so if I have to know my CID# in order to upgrade HBOOT how do I find it when I cant boot the phone and can only get into Fastboot
I am stuck on the CyanogenMod splash screen and can't do anything to exit it either because I can't activate Developer Mode to run fastboot. What should I do?
Stein Ichimaru said:
I am stuck on the CyanogenMod splash screen and can't do anything to exit it either because I can't activate Developer Mode to run fastboot. What should I do?
Click to expand...
Click to collapse
Have u tried power off and power on while holding Vol down button that will get u into fast boot mode
Yes, when I do that I keep getting an error saying device not found and I'm at the last straw with the stupid thing.
hawkinau said:
Have u tried power off and power on while holding Vol down button that will get u into fast boot mode
Click to expand...
Click to collapse
Did you solve your issue ?
Ow and btw upgrade your recovery yours is old and does not support ums and charging the battery in recovery
Flash this one
http://db.tt/SPXdFfPw
Stein Ichimaru said:
Yes, when I do that I keep getting an error saying device not found and I'm at the last straw with the stupid thing.
Click to expand...
Click to collapse
yep feel your pain, I dont get an error, the device just dont show up, pc doesn't recognize it, thought it might have been Win 8 and drivers not working so went on a WinXP PC installed drivers and JBFWTool which supposedly does everything but make coffee and my f*&$% phone went flat,
so far I have spent 10 solid hrs on it trying a thousand things to fix it and I'm no further advanced than I was 10 hrs ago, I'm just about over it as well
Mr Hofs said:
Did you solve your issue ?
Ow and btw upgrade your recovery yours is old and does not support ums and charging the battery in recovery
Flash this one
http://db.tt/SPXdFfPw
Click to expand...
Click to collapse
No I didn't Mr Hofs opps u must have added the last bit while I was replying to your first bit lol ok I will try it
hawkinau said:
No I didn't Mr Hofs opps u must have added the last bit while I was replying to your first bit lol ok I will try it
Click to expand...
Click to collapse
but once again I am having probs with the PC seeing the phone when I flash an img file it says it flashed successfully but I dont know if it has or not,
do u upgrade the the recovery by flashing it frm the PC?
Yes put the file in the fastboot folder on the pc and rename it to recovery.img
Then open the command window in that folder, hold shift + right click and open command window here
Then flash it
Fastboot flash recovery recovery.img
Fastboot erase cache
And while you are at it.
Fastboot getvar version-main
That will tell me the firmware you need to flash to upgrade the hboot if you didn't do that yet. Can't say if you need the same firmware as the thread where you got redirected to !
hawkinau said:
but once again I am having probs with the PC seeing the phone when I flash an img file it says it flashed successfully but I dont know if it has or not,
do u upgrade the the recovery by flashing it frm the PC?
Click to expand...
Click to collapse
Just check by going into recovery if recovery is upgraded and yes u flash it on your phone from pc..
---------- Post added at 12:50 PM ---------- Previous post was at 12:45 PM ----------
Stein Ichimaru said:
I am stuck on the CyanogenMod splash screen and can't do anything to exit it either because I can't activate Developer Mode to run fastboot. What should I do?
Click to expand...
Click to collapse
Restore your backup and then before flashing cyanogenmod rom flash the boot.img from the zip of cyanogenmod rom
Mr Hofs said:
Yes put the file in the fastboot folder on the pc and rename it to recovery.img
Then open the command window in that folder, hold shift + right click and open command window here
Then flash it
Fastboot flash recovery recovery.img
Fastboot erase cache
And while you are at it.
Fastboot getvar version-main
That will tell me the firmware you need to flash to upgrade the hboot if you didn't do that yet. Can't say if you need the same firmware as the thread where you got redirected to !
Click to expand...
Click to collapse
WHOWHOOO I feel like I'm getting somewhere now just flashed the recovery and now can mount USB in recovery and ran Fastboot getvar version-main and the # 1.26.980.3
daninantro said:
Just check by going into recovery if recovery is upgraded and yes u flash it on your phone from pc..
---------- Post added at 12:50 PM ---------- Previous post was at 12:45 PM ----------
Restore your backup and then before flashing cyanogenmod rom flash the boot.img from the zip of cyanogenmod rom
Click to expand...
Click to collapse
Thanks mate can now see the light at the end of a very long tunnel lol used a different PC and got the recovery updated just waiting for the correct HBOOT version to flash then install the rom and back in business and I have a phone again after 12 hrs with out one. how did we ever survive before mobile phones lol
Aha Optus Australia ! I want you to run a ruu and update via official ota, because the stock backups for Optus are rare. And if you want to be able to update to sense 5 then you 100& need a stock backup !!!
Here is the ruu
http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260560-signedexe/
Relock the bootloader :
Fastboot oem lock
Then keep the phone in the bootloader and execute the ruu.exe from the pc with administrator rights ! Right click it and select run as administrator
It will flash the phone back to full stock, stock rom, recovery and kernel.
Note : it will wipe EVERYTHING.
Mr Hofs said:
Aha Optus Australia ! I want you to run a ruu and update via official ota, because the stock backups for Optus are rare. And if you want to be able to update to sense 5 then you 100& need a stock backup !!!
Here is the ruu
http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260560-signedexe/
Relock the bootloader :
Fastboot oem lock
Then keep the phone in the bootloader and execute the ruu.exe from the pc with administrator rights ! Right click it and select run as administrator
It will flash the phone back to full stock, stock rom, recovery and kernel.
Note : it will wipe EVERYTHING.
Click to expand...
Click to collapse
Gr8 thanks for that, looks like a lot more messing around but should be worth it in the long run I hope, u relock and unlock the bootloader in recovery don't u? I think I saw those options in there earlier, doesnt mater if it wipes everything I have a back up of my storage and I have factory reset it 2-3 times in the last 12 hrs I will have to charge it a bit now as it went flat about half an hr ago I will let u know how it goes :victory:
No you lock it via fastboot commands, all commands starting with fastboot are done with the phone in the bootloader !
So the steps are :
1: run the ruu like described
2: after all updates via phone menu you should get to jellybean android 4.1.....check your bootloader and make sure the hboot number is above 1.31 !
3: unlock the bootloader again with the unlock code
Fastboot flash unlocktoken unlock_code.bin
4: flash the custom recovery
Fastboot flash recovery recovery.img
Fastboot erase cache
and make a NANDROID BACKUP RIGHT AWAY ! Very important !!!
5: flash the boot.img from the new desired rom
Fastboot flash boot boot.img
Fastboot erase cache
6: make a full wipe in the recovery (wipe all except the sdcard !)
7: install the new rom.zip in the recovery
8: reboot and enjoy JB !
Mr Hofs said:
No you lock it via fastboot commands, all commands starting with fastboot are done with the phone in the bootloader !
Click to expand...
Click to collapse
OK and to unlock it again once all this is done would it be fastboot oem unlock ?
Sorry here's me rabbiting on down here and didn't see your edited post above cheers will follow instruction thanks
Updated my post
I had started a previous thread, and in attempting to fix my phone, it seems I may have bricked it.
I somehow flashed a gsm rom for my CDMA verizon HTC one m7. In attempting to revert to a stock rom I am now stuck.
I attempted to flash http://forum.xda-developers.com/showthread.php?t=2224752 as a stock dump, it would fail at the end of the installation.
I tried flashing a stock recovery found on that link and it failed to boot, one time it had a picture of a phone with green arrows going in a circle and loading bar under it, then it went to the regular boot, when I had 4.3 PAC Rom still installed. I was using TWRP as my recovery. I then for reasons unknown to me, flashed clockworkmod recovery 6.0.4.7, which is when I must have wiped all data and tried installing the stock rom from the link above. When flashing it using clockwork it goes through till the end it says:
>>> Setting permissions
set_metadata_recursive: some changes failed
E: Error in /data/media/0/one.zip
(Status 7)
Installation aborted.
I go to reboot and then clockwork mod says I'm not rooted...
It reboots and just keeps rebooting the flash screen.
I power and down volume to go into bootloader and select recovery again.
It goes into clockworkmod and immediately at the bottom it says:
CLockworkMod Recovery v6.0.4.7
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
I was trying the adb sideload to add another rom but it said device not found.
Any help would be appreciated.
also Tried reflashing TWRP a few versions older than the newest, and it shows the TWRP splash screen but then reboots and goes to the HTC screen.
In the bootloader menu this is the top
*** UNLOCKED ***
M7_WLV PVT SHIP S-OFF RH
CID-VZW__001
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OpenDSP-v32.120.274.0909
OS-3.11.605.1
eMMC-boot 2048MB
Jan 20 2014, 23:10:47
I tried looking up ways to flashboot and img to get it up and running but can't figure it out.
How did u manage to flash a gsm ROM
Sent from my HTC One VZW using Tapatalk 4
I'm not sure, it stemmed from my last post, one guy said that is why I had no service and no baseband when flashing from PAC Rom (JB) to the new PAC Rom or Paranoid ANdroid (KK) versions. Basically when flashing the new PAC I would use the PAC for VZW and it would fail, but the PAC with no provider would work but I would have no service. I'm not sure that is totally why though. But through that, someone suggested I update the firmware, I followed the link in the last post, updated the firmware, re flashed the KK roms with no difference. Then they suggested to just reflash a stock rom and stock recovery, the stock recovery they linked wouldn't boot, so I tried reflashing to clockworkmod recovery and tried installing the stock rom they suggested again, and it would fail during flashing it. I wiped my backups in that process and now I'm stuck with clockworkmod recovery and fastboot. Tried reflashing TWRP 2.6.3.1 which is the latest that would work on my phone, now it shows just the TWRP flash screen and doesnt go into the recovery, so I am now again with clockworkmod.
Have you tried flashing a ruu? Your s-off
sk842018 said:
Have you tried flashing a ruu? Your s-off
Click to expand...
Click to collapse
Ya all you need to do is flash an ruu dude
http://www.htc1guru.com/downloads/ruu-file-downloads/
I can't find a VZW one in that list..and I dont want to mess anything further at this point.
Your good, just do a RUU, u will go back to 4.3, then update the firmware, takes about 15 minutes
---------- Post added at 06:45 PM ---------- Previous post was at 06:39 PM ----------
Goto the Verizon HTC one development section, look for Santod040's thread about 4.4.2 Rom radio kernel, the links to the decrypted (this is what you want) 2.10.605.1 RUU are in the second post, and all instructions are there
Sent from my HTC6500LVW using XDA Premium 4 mobile app
---------- Post added at 06:47 PM ---------- Previous post was at 06:45 PM ----------
You can't get worse at this point, I promise ?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
from that post I did the firmware update, I tested flashing the newest TWRP and it finally now works. So I flashed the only rom on the SD Card, from that same post by Santod040, the odexed version, which I had previously put on the sd card after wiping everything.. and it didn't fail to instal on the new TWRP like it did on clockworkmod, it said successful, then it asked to install SuperSU because it said I wasn't rooted, I said yes and now I am stuck in a bootloop again.
Tried to reflash again, except say no to installing SuperSU, and same result, a bootloop...
May I will try using the adb sideload tomorrow and add another ROM. last time the sideload wouldn't run, but maybe it will work now with the new TWRP.
Thanks for you help guys.
inthrewtheoutdor said:
from that post I did the firmware update, I tested flashing the newest TWRP and it finally now works. So I flashed the only rom on the SD Card, from that same post by Santod040, the odexed version, which I had previously put on the sd card after wiping everything.. and it didn't fail to instal on the new TWRP like it did on clockworkmod, it said successful, then it asked to install SuperSU because it said I wasn't rooted, I said yes and now I am stuck in a bootloop again.
Tried to reflash again, except say no to installing SuperSU, and same result, a bootloop...
May I will try using the adb sideload tomorrow and add another ROM. last time the sideload wouldn't run, but maybe it will work now with the new TWRP.
Thanks for you help guys.
Click to expand...
Click to collapse
Flash the RUU, not the firmware update. Then turn it on and test. After that, then update your firmware / radio. Test again. THEN flash your recovery, both CWM and TWRP work. Test, make a backup. Then try flashing a ROM.
Here is the RUU link - http://goo.gl/JEkyCk
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip rom.zip (rename file to rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip rom.zip
After that, update firmware, flash recovery, backup, profit.
hey guys... I flashed this rom: http://forum.xda-developers.com/show....php?t=2694193
then my device kept rebooting only on htc screen and that's it. tried different roms but didn't work. maybe Ihaven't tried the correct ones. right now I'm stuck in to bootloader only and the device is:
*** TAMPERED ***
*** RELOCKED ***
M7_WLV PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-1.13.41.01.09_2
OS-3.11.605.1
recovery doesn't work. so far I'm trying to get something to work with fastboot, in other words, searching for RUU which will flash and make it work. if you have something in mind and can help me, please do so. THANKS!!!
inthrewtheoutdor said:
from that post I did the firmware update, I tested flashing the newest TWRP and it finally now works. So I flashed the only rom on the SD Card, from that same post by Santod040, the odexed version, which I had previously put on the sd card after wiping everything.. and it didn't fail to instal on the new TWRP like it did on clockworkmod, it said successful, then it asked to install SuperSU because it said I wasn't rooted, I said yes and now I am stuck in a bootloop again.
Tried to reflash again, except say no to installing SuperSU, and same result, a bootloop...
May I will try using the adb sideload tomorrow and add another ROM. last time the sideload wouldn't run, but maybe it will work now with the new TWRP.
Thanks for you help guys.
Click to expand...
Click to collapse
You can also just download a Rom with root baked in. Bonestock is great, Santod040 or hawknests sense 6 roms are great. Lots of options there
Sent from my HTC6500LVW using XDA Premium 4 mobile app
ccarr313 said:
Flash the RUU, not the firmware update. Then turn it on and test. After that, then update your firmware / radio. Test again. THEN flash your recovery, both CWM and TWRP work. Test, make a backup. Then try flashing a ROM.
Here is the RUU link - http://goo.gl/JEkyCk
Place the zip in your fastboot/adb directory on your computer.
Put the device in fastboot mode
(Volume down and power until menu appears, select fastboot using power button)
Connect the device to the computer
Enter the following commands from terminal/command prompt in the fastboot directory, one at a time:
fastboot oem rebootRUU (this puts the device in RUU mode)
fastboot flash zip rom.zip (rename file to rom.zip)
It will say that the update did not finish, to flush again, so repeat the above step:
fastboot flash zip rom.zip
After that, update firmware, flash recovery, backup, profit.
Click to expand...
Click to collapse
That did the trick, in that exact order. I really appreciate the help guys!
inthrewtheoutdor said:
That did the trick, in that exact order. I really appreciate the help guys!
Click to expand...
Click to collapse
Glad to help!
Hey there guys, I've just unlocked Bootloader as described on the htcdev./ site,
Unfortunately, now when I enter HBOOT, no only do I recieve a "failed to open usb master mode" and "pj46img.zip" fail message, but when I click "Recovery", my phone switches back to fastboot. I need to backup my system to downgrade and root afterwards.. anyways
Anyone experienced this before or has any idea what to do?
The Model is: HTC Endeavor , Android ver. 4.2.2, Sense 5...
and...
What the status bar tells me :
*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode : disabled
HW secure boot: enabled
MODEM PATH : OFF
Jun 21 2013,18:24:41
Error message is normal because you have the usb connected. Without cable you won't get the message.
Second when you are in the bootloader do the command :
Fastboot erase cache
And you need to flash or boot a custom recovery !
Fastboot boot recovery.img
Or
Fastboot flash recovery recovery.img
The custom recovery has to be named "recovery.img" and be placed in the fastboot folder on the pc !
And what do you want to downgrade ?
Cache erased
Mr Hofs said:
Error message is normal because you have the usb connected. Without cable you won't get the message.
Second when you are in the bootloader do the command :
Fastboot erase cache
And you need to flash or boot a custom recovery !
Fastboot boot recovery.img
Or
Fastboot flash recovery recovery.img
The custom recovery has to be named "recovery.img" and be placed in the fastboot folder on the pc !
And what do you want to downgrade ?
Click to expand...
Click to collapse
Wow, thanks for such a quick answer.. sorry for not coming and thanking sooner...
Anyways.. I erased the Cache as recommended.
The reason why downgrade was because somewhere I read there are problems with rooting my phone on 4.2.2 so I thought downgrading to 4.1.1 would be adequate... Anyways recent research pushed me into believing it is not necessary...
Yeah, so anyway I've been looking for a custom recovery to use as you said...
version-main: 4.18.401.2
cidnum: HTC__032
Do I need to find a recovery for exactly my CIDnumber?
Custom recovery to enable flashing of all roms (sense 5 and kit Kat)
https://www.dropbox.com/s/14c1ikgsp38axwv/twrp-recovery2.img
Thanks again!
Mr Hofs said:
Custom recovery to enable flashing of all roms (sense 5 and kit Kat)
Click to expand...
Click to collapse
Thank you many times! :good:
Stuck... damn it!
Yeah, umm hello there again.
So I used the Cyanogenmod recovery in the end...
Anyways I let myself led by the guide posted by Thömy (http://forum.xda-developers.com/showthread.php?t=2583037)...
Everything went fine, I got the bootloader unlocked (before already), the recovery provided by ClockWorkMod, did a Data wipe, downloaded everything necessary, booted into Recovery... but when I got to flash the CM 11.0.zip (installing from the zip file in recovery) It failed..
So for no reason i decided to simply restart the phone and try whatever will I find then.. I haven't got past the white/green HTC screen though and I'm stuck at it... I can get back to recovery or the Bootloader, but nothing more, nothing less...
Any Idea?.. I'm struggling with it for a few hour now and feel lost
MartyPavelka said:
Yeah, umm hello there again.
So I used the Cyanogenmod recovery in the end...
Anyways I let myself led by the guide posted by Thömy (http://forum.xda-developers.com/showthread.php?t=2583037)...
Everything went fine, I got the bootloader unlocked (before already), the recovery provided by ClockWorkMod, did a Data wipe, downloaded everything necessary, booted into Recovery... but when I got to flash the CM 11.0.zip (installing from the zip file in recovery) It failed..
So for no reason i decided to simply restart the phone and try whatever will I find then.. I haven't got past the white/green HTC screen though and I'm stuck at it... I can get back to recovery or the Bootloader, but nothing more, nothing less...
Any Idea?.. I'm struggling with it for a few hour now and feel lost
Click to expand...
Click to collapse
Use the Recovery that Mr Hofs gave you and flash the CM 11 package. Should work. CWM recovery sometimes gives you errors while flashing since you may have to modify the updater-script with-in the package to flash successful.
Nice, felt some progression
aromerblz said:
Use the Recovery that Mr Hofs gave you and flash the CM 11 package. Should work. CWM recovery sometimes gives you errors while flashing since you may have to modify the updater-script with-in the package to flash successful.
Click to expand...
Click to collapse
Cool :good:
So I used the Recovery from el Maestro and flashed the CM 11 package.
I got to a "Cyanogenmod" booting screen at which I'm stuck...
It updated some files but, that's all and the arrow wheel keeps spinning? any Idea?
btw: I'm really sorry if someone already had this problem,
I swear I spent hours looking for one, but when I found a similar one,
it wasn't really what I was looking for in the end
[EDIT] Also when I try to boot the system with the boot.img file included in cm-11 package, I'm not stuck on the Cyanogenmod screen but all the way back on the HTC logo screen again
Flashed the boot.img from the cm11 zip ?
Flash instead of Boot
Mr Hofs said:
Flashed the boot.img from the cm11 zip ?
Click to expand...
Click to collapse
Yes, I until now was directly booting "fastboot boot boot.img" with cmd on computer.
Now when I flashed it into the device, I cannot even get to the Cyanogenmod screen, hehe
MartyPavelka said:
Yes, I until now was directly booting "fastboot boot boot.img" with cmd on computer.
Now when I flashed it into the device, I cannot even get to the Cyanogenmod screen, hehe
Click to expand...
Click to collapse
The flash command should be "fastboot flash boot boot.img" are you sure you are doing it right?
aromerblz said:
The flash command should be "fastboot flash boot boot.img" are you sure you are doing it right?
Click to expand...
Click to collapse
yep Did it exactly this way ... It now behaves the same as when only booted with the boot.img :/
Did you perform a full wipe within the custom recovery before installing the cm zip ? Seems to me you forgot to wipe something !
MartyPavelka said:
yep Did it exactly this way ... It now behaves the same as when only booted with the boot.img :/
Click to expand...
Click to collapse
Ok try this..
Assuming you already did a full nandroid backup, do the following:
1. Do a FULL wipe on your device.
2. Flash the ROM again
3. Reboot to bootloader
4. Flash the boot.img again
5. Reboot
6.Thank me if it works.
Should work, that's normally the steps I take when flashing ROM's and have never failed me.
If he flashes the boot.img alresdy its a wipe issue. Doesnt matter when you flash it because it's not going to be changed installing a rom or wiping partitions from within the recovery (definitely not on a s-on device)
6: kinda corny to mention that isn't it ! Bit of a desperate call for appreciation......not confident enough you need confirmation
Got past it!
aromerblz said:
Ok try this..
Assuming you already did a full nandroid backup, do the following:
1. Do a FULL wipe on your device.
2. Flash the ROM again
3. Reboot to bootloader
4. Flash the boot.img again
5. Reboot
6.Thank me if it works.
Should work, that's normally the steps I take when flashing ROM's and have never failed me.
Click to expand...
Click to collapse
Well, wow... ok... I got past the logo screen and I now get keyboard failure messages... but wow... thanks... A huge rock fell of my chest... Thanks to both of you... I did a full wipe again.. I guess it was a wipe issue afterall -_- what a noobfailure..
I don't think it "kills to try" like I mentioned at the bottom that's how I usually do mines when am blocked by issues. and NO not desperate for appreciation either.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
MartyPavelka said:
Well, wow... ok... I got past the logo screen and I now get keyboard failure messages... but wow... thanks... A huge rock fell of my chest... Thanks to both of you... I did a full wipe again.. I guess it was a wipe issue afterall -_- what a noobfailure..
Click to expand...
Click to collapse
Have you flashed the GAPPS?
aromerblz said:
I don't think it "kills to try" like I mentioned at the bottom that's how I usually do mines when am blocked by issues. and NO not desperate for appreciation either.
---------- Post added at 01:33 PM ---------- Previous post was at 01:31 PM ----------
Have you flashed the GAPPS?
Click to expand...
Click to collapse
Yeah... Wrong version
aromerblz said:
and NO not desperate for appreciation either
Click to expand...
Click to collapse
LOL !
MartyPavelka said:
Yeah... Wrong version
Click to expand...
Click to collapse
Just flash the correct one and you should be good to go.. :victory:
I've got the Sprint HTC One M8. Bootloader unlocked, rooted, S-off, CWM recovery.
I'm trying to flash ViperOne M8 and done just about everything I can think of but without any luck. It completes install, but upon reboot, it boots back to the bootloader. At that point, I'm able to get into recovery but can't boot into ROM.
I've been trying ViperOne 1.6.0, and currently downloading an older version to see if that'll work.
I tried Android Revolution HD and InsertCoin. Both worked fine, so I know I'm able to flash custom ROMs just fine, but not ViperOne. Any ideas?
jlaprevote said:
I've got the Sprint HTC One M8. Bootloader unlocked, rooted, S-off, CWM recovery.
I'm trying to flash ViperOne M8 and done just about everything I can think of but without any luck. It completes install, but upon reboot, it boots back to the bootloader. At that point, I'm able to get into recovery but can't boot into ROM.
I've been trying ViperOne 1.6.0, and currently downloading an older version to see if that'll work.
I tried Android Revolution HD and InsertCoin. Both worked fine, so I know I'm able to flash custom ROMs just fine, but not ViperOne. Any ideas?
Click to expand...
Click to collapse
I was having problems with some ROMs as well and I was able to fix it by doing an "advanced wipe" in TWRP and wiping the cache, dalvik, data and system. The default wipe in TWRP does not wipe system.
Not sure if CWM does this or if you have similar options, but you might want to make sure you wipe system.
chobungus said:
I was having problems with some ROMs as well and I was able to fix it by doing an "advanced wipe" in TWRP and wiping the cache, dalvik, data and system. The default wipe in TWRP does not wipe system.
Not sure if CWM does this or if you have similar options, but you might want to make sure you wipe system.
Click to expand...
Click to collapse
Yeah, I've tried wiping everything multiple ways. I actually tried to switch recovery from CWM to TWRP so I could do their advanced wipe, but it wouldn't work.
I attempted to change to TWRP using fastboot (adding TWRP to fastboot folder, and using the "fastboot flash recovery" command), but when I did that, nothing happened. Command prompt went to the next line without any confirmation or error.
jlaprevote said:
Yeah, I've tried wiping everything multiple ways. I actually tried to switch recovery from CWM to TWRP so I could do their advanced wipe, but it wouldn't work.
I attempted to change to TWRP using fastboot (adding TWRP to fastboot folder, and using the "fastboot flash recovery" command), but when I did that, nothing happened. Command prompt went to the next line without any confirmation or error.
Click to expand...
Click to collapse
Hmm that's odd. Did you try using adb sideload? If that doesn't work I guess I would redownload the ROM (or maybe an older version), make sure to verify the md5, and try installing again.
Sorry I can't be of much help! Good luck!
Update: Resolved!
Tried previous versions of ViperOne with no luck.
Tried to flash TWRP again and I was able to do so just fine. Flashing with TWRP successfully installed ViperOne! Very happy with it.
Hmm... I have the Sprint M8 H/K edition and having the same problem ??
Using TWRP and did advanced wipe (cache, dalvik, data and system)
Also tried flashing both "stock" version and "viper" version in the aroma options and still same thing... goes through the flash process and then just boots into HBOOT???
I downloaded twice and also checked the md5 so that's not the issue
jlaprevote said:
Update: Resolved!
Tried previous versions of ViperOne with no luck.
Tried to flash TWRP again and I was able to do so just fine. Flashing with TWRP successfully installed ViperOne! Very happy with it.
Click to expand...
Click to collapse
Which version of TWRP did you use to resolve your issue?
Thanks!
Please help!
jlaprevote said:
Update: Resolved!
Tried previous versions of ViperOne with no luck.
Tried to flash TWRP again and I was able to do so just fine. Flashing with TWRP successfully installed ViperOne! Very happy with it.
Click to expand...
Click to collapse
Can you explain again what you did?
I'm trying to restore a TWRP backup that included ViperOne M8, but it just gets stuck in boot (never see desktop). It doesn't reset to HBOOT, but again, just stays on boot screen forever. Both ViperOne M8 TWRP backups I have don't work, but when I flash a pre-ViperOne M8 backup, it works. But now I'm back to like a month ago. I don't understand why my ViperOne M8 backups don't work, but the pre-VM8 one does.
Please help, if you can!
Thank You,
RockStar2005
does your current firmware match the firmware on the nandroid backup you are trying to restore?
remember, If you upgraded your firmware to 4.4.3, and you are restoring a nand that was made with 4.4.2 firmware, you could have issues
wase4711 said:
does your current firmware match the firmware on the nandroid backup you are trying to restore?
remember, If you upgraded your firmware to 4.4.3, and you are restoring a nand that was made with 4.4.2 firmware, you could have issues
Click to expand...
Click to collapse
It turns out the version I had of TWRP was corrupted. I'm going to delete it. So I guess I'm good now.
Thank You,
RockStar2005
I have the same problem! I just rooted my m8, flashed TWRP 2.8.1.0on my phone.
Flashed viper 3.2.1 (flashed successful) . but it boots into hboot mode everytime.
trekdrop said:
I have the same problem! I just rooted my m8, flashed TWRP 2.8.1.0on my phone.
Flashed viper 3.2.1 (flashed successful) . but it boots into hboot mode everytime.
Click to expand...
Click to collapse
did you erase the cache after flashing TWRP ?
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
clsA said:
did you erase the cache after flashing TWRP ?
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Yes.
Treid diffrent trwp... still no luck
Luckily i can restore everything with my nandroid back up.
trekdrop said:
Yes.
Treid diffrent trwp... still no luck
Luckily i can restore everything with my nandroid back up.
Click to expand...
Click to collapse
are your versions of adb and fastboot up to date ?
https://www.dropbox.com/s/0wzwt8843zx27nh/Fastboot.zip?dl=0
clsA said:
did you erase the cache after flashing TWRP ?
fastboot flash recovery openrecovery-twrp-2.8.1.0-m8.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
Which version trwp do i need?
trekdrop said:
Which version trwp do i need?
Click to expand...
Click to collapse
your TWRP is fine, that's what I'm using
clsA said:
your TWRP is fine, that's what I'm using
Click to expand...
Click to collapse
i used this one: openrecovery-twrp-2.8.1.0-m8_whl.img because i have a sprint (HBOOT 3.19.0.0000)
I now used yourspenrecovery-twrp-2.8.1.0-m8
and now it boots ok... but after i enter my pin number it goes to htc screen (the white one whit green htc letters)
trekdrop said:
i used this one: openrecovery-twrp-2.8.1.0-m8_whl.img because i have a sprint (HBOOT 3.19.0.0000)
I now used yourspenrecovery-twrp-2.8.1.0-m8
and now it boots ok... but after i enter my pin number it goes to htc screen (the white one whit green htc letters)
Click to expand...
Click to collapse
don't flash a recovery not made for your phone ! ... If you have Sprint use the Sprint recovery
the question was what version of fastboot do you have and use, and did you erase cache after flashing the recovery
clsA said:
don't flash a recovery not made for your phone ! ... If you have Sprint use the Sprint recovery
the question was what version of fastboot do you have and use, and did you erase cache after flashing the recovery[/QUOT
s-on
Hboot 3.19
And yes i did erase cache.
---------- Post added at 10:32 AM ---------- Previous post was at 10:00 AM ----------
This is a screenshot from my bootloaderscreen.
http://i57.tinypic.com/1zdpz7a.jpg
Click to expand...
Click to collapse
trekdrop said:
clsA said:
don't flash a recovery not made for your phone ! ... If you have Sprint use the Sprint recovery
the question was what version of fastboot do you have and use, and did you erase cache after flashing the recovery[/QUOT
s-on
Hboot 3.19
And yes i did erase cache.
---------- Post added at 10:32 AM ---------- Previous post was at 10:00 AM ----------
This is a screenshot from my bootloaderscreen.
http://i57.tinypic.com/1zdpz7a.jpg
Click to expand...
Click to collapse
that's not the bootloader of a Sprint phone ... M8_UL is a GSM Phone, I hope the Sprint recovery you flashed didn't screw up your partitions
Click to expand...
Click to collapse