Hello boys.. I've a big problem: I'm stuck on first boot!!
I got the cyano 10.1.3 stable, flashed the boot.img by command line, in the TWRP recovery (the only one for my HTC One X+) full wipe and install the zip of the rom.. reboot... but the phone is stucked on boot.
I've tried a lot of times, then I've decided to use another cooked rom, MagioROM.. same problem:
ie extract the boot.img, flashed by command line window, in the recovery full wipe, and install of the rom. the installation goes on, show me the % of progress, at the end he seems all ok, then ask me "Reboot Now?" or not, then I reboot ma the phone is still blocked with the boot image. I've tried a lot of times, making wipe after the rom installation, same thing.. installing gapps before the reboot, no way.. installing gapps and making full wipe..
HEEEEEELP!!
By you got CM10.1.3 you mean that you are running it or can't past the Boot animation?
I have had this problem the first time I flashed CM. I fixed it this way :
-Full wipe (data, dalvik, cache, system) just be sure not to wipe the internal sd....
-Flashed the ROM.
-Fastboot flash boot boot.img
-cleared cache through recovery or fastboot
-Restarted and there I was running CM. Followed the same steps to return to stock.
Hope I mentioned something that u missed or a step that u weren't aware of .
Good luck
Sent from my HTC One X+ using xda app-developers app
Ghand0ur said:
By you got CM10.1.3 you mean that you are running it or can't past the Boot animation?
I have had this problem the first time I flashed CM. I fixed it this way :
-Full wipe (data, dalvik, cache, system) just be sure not to wipe the internal sd....
-Flashed the ROM.
-Fastboot flash boot boot.img
-cleared cache through recovery or fastboot
-Restarted and there I was running CM. Followed the same steps to return to stock.
Hope I mentioned something that u missed or a step that u weren't aware of .
Good luck
Click to expand...
Click to collapse
sorry for my english I mean I've downloaded it (while my phone running the original sense 5.0 with android 4.2.2).. mmh by your explanation, my error is flashing the boot.img before flashing of the rom..
I'll try as you told me.. thanks!!
No way.. same thing, the cell is stucked on first boot. Any solution ??
I honestly don't know the problem but here are some guesses:
-You installed a Rom belonging to one x not x+, or At&t and you are INT. Or something.
- Try to reboot the phone again. Some people reported that the first boot is bugged and it might boot the second time.
- Try another ROM like pure AOSP or some other kind of ROM
Just a top of my head guesses which you should do.
I am trying to clear ideas for the more professional devs. Hope I help in someway :S sorry mate , I am sure everything will be fine.
Sent from my HTC One X+ using xda app-developers app
Ghand0ur said:
I honestly don't know the problem but here are some guesses:
-You installed a Rom belonging to one x not x+, or At&t and you are INT. Or something.
- Try to reboot the phone again. Some people reported that the first boot is bugged and it might boot the second time.
- Try another ROM like pure AOSP or some other kind of ROM
Just a top of my head guesses which you should do.
I am trying to clear ideas for the more professional devs. Hope I help in someway :S sorry mate , I am sure everything will be fine.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
No, I chosen the right roms.. the device is an hox+ ita (int, I suppose)
I've tried something like 40 reboots in the past 4 days..
The rom's I've tried: cyano 10.1.3 rc2 and MagioROM 4.0
Can be a problem of recovery? Maybe this is the error.. sincely I don't remember wich version I used..
tsuby2002 said:
No, I chosen the right roms.. the device is an hox+ ita (int, I suppose)
I've tried something like 40 reboots in the past 4 days..
The rom's I've tried: cyano 10.1.3 rc2 and MagioROM 4.0
Can be a problem of recovery? Maybe this is the error.. sincely I don't remember wich version I used..
Click to expand...
Click to collapse
I changed the bootloader, installing the latest twrp 2.6.3, erase cache, reboot, full wipe, flashed the rom, reboot..
and now the phone is freeze on boot:
I CANNOT EVEN SHUTDOWN IT!!! It's a brick?
HEEELPPP!!
Freezes on the ROM's boot? That means you did not "fastboot flash boot boot.img"
Open the ROM that you downloaded on your PC (.zip) and drag out the boot.img
Copy it to your fastboot folder.
Now to restart your phone, hold down the power buttons for 10 seconds. Release it, then hold it down for another 10 seconds. The screen still didn't go dark? Hold down the power button till the screen goes dark, keep holding the volume down button till the phone boots up, it should get you to the bootloader. Enter the fastboot mode.
Connect your phone to the computer.
Flash the boot.img
Restart and then the ROM should work fine.
If you do not know how to flash boot the boot.img , you can youtube it. It's pretty close no matter which phone it is.
Good luck.
Edit: I just noticed that I already said that , sorry I am kinda fuzzy , just woke up. But the issue with you is the BOOT.img , I am 90% sure of it. Just keep trying to flash the BOOT.img and restart, should work with you.
Sent from my HTC ONE X+ using XDA Developers app with a random Kame-Hami flying up yo' face.
Ghand0ur said:
Freezes on the ROM's boot? That means you did not "fastboot flash boot boot.img"
Open the ROM that you downloaded on your PC (.zip) and drag out the boot.img
Copy it to your fastboot folder.
Now to restart your phone, hold down the power buttons for 10 seconds. Release it, then hold it down for another 10 seconds. The screen still didn't go dark? Hold down the power button till the screen goes dark, keep holding the volume down button till the phone boots up, it should get you to the bootloader. Enter the fastboot mode.
Connect your phone to the computer.
Flash the boot.img
Restart and then the ROM should work fine.
If you do not know how to flash boot the boot.img , you can youtube it. It's pretty close no matter which phone it is.
Good luck.
Edit: I just noticed that I already said that , sorry I am kinda fuzzy , just woke up. But the issue with you is the BOOT.img , I am 90% sure of it. Just keep trying to flash the BOOT.img and restart, should work with you.
Sent from my HTC ONE X+ using XDA Developers app with a random Kame-Hami flying up yo' face.
Click to expand...
Click to collapse
boot.img issues ? Thanks.. So, i recharged the phone (yesterday he didn't shutdown in any way) ,
running the phone in bootloader, "fastboot usb" was highlighted,
cheched that boot.img was in the right folder, fastboot the boot.img by the prompt of pc, ok, erase cache too,
reboot. 4 minutes ago..
Hoping well !!!
tsuby2002 said:
boot.img issues ? Thanks.. So, i recharged the phone (yesterday he didn't shutdown in any way) ,
running the phone in bootloader, "fastboot usb" was highlighted,
cheched that boot.img was in the right folder, fastboot the boot.img by the prompt of pc, ok, erase cache too,
reboot. 4 minutes ago..
Hoping well !!!
Click to expand...
Click to collapse
Nothing to do.. the phone didn't boot correclty, after 14 min i had to turn it off!
Another flash of the boot.img, then (by recovery) I locate the rom (where, on pc, i found the boot.img), I installed it, now he's trying to boot..
I'm not lucky with this hox+
Just a question.. the boot.img I only copied on pc.. but a copy is still in the zip of the rom on smartphone.. he can stay there, or I have to delete it ?
Keep it there. I hope one of the devs can reply to your thread :S sorry mate, I'm out of ideas.
Sent from my HTC ONE X+ using XDA Developers app with a random Kame-Hami flying up yo' face.
Maybe a problem of bootloader? How I can see if it's unlocked or not? I'm pretty sure to complete the unlocking step by step.. but..
with the bootloader locked, it's possible, like I do, have another recovery BUT he didn't complete the rom installation ?
tsuby2002 said:
Maybe a problem of bootloader? How I can see if it's unlocked or not? I'm pretty sure to complete the unlocking step by step.. but..
with the bootloader locked, it's possible, like I do, have another recovery BUT he didn't complete the rom installation ?
Click to expand...
Click to collapse
Come non detto: bootloader is unlocked (is highlighted in pink),
it show me:
enrc2b_U PVT SHIP S-ON RL
HBOOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-3.1204.171.33
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH: OFF
Hardware secure boot ?
Try to sideload another rom with à different boot.img check the link on The four threat how to sideload it
http://forum.xda-developers.com/showthread.php?t=2066390
Hope you get lucky with it.
hellboysz said:
Try to sideload another rom with à different boot.img check the link on The four threat how to sideload it
http://forum.xda-developers.com/showthread.php?t=2066390
Hope you get lucky with it.
Click to expand...
Click to collapse
Thanks for the attempt, I tried as hasoon2000 wrote..
Boot into recovery manually, turned off hox+ and restart in in same way until the BOOTLOADER pops up,
go on recovery, connected the phone to pc,
in TWRP, under "Advanced" and selected ADB Sideload,
runned AIO on pc then press ADB Sideload a ROM, hit with violence "YES" (it's the 5° evening I spend to solve this problem)
Then selected the ROM cm10.1.3, It had to be sideloaded into the phone,
BUT, HOLY CRAP, the result of "All-in-one" is..
"adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
what's wrong ?
tsuby2002 said:
Thanks for the attempt, I tried as hasoon2000 wrote..
Boot into recovery manually, turned off hox+ and restart in in same way until the BOOTLOADER pops up,
go on recovery, connected the phone to pc,
in TWRP, under "Advanced" and selected ADB Sideload,
runned AIO on pc then press ADB Sideload a ROM, hit with violence "YES" (it's the 5° evening I spend to solve this problem)
Then selected the ROM cm10.1.3, It had to be sideloaded into the phone,
BUT, HOLY CRAP, the result of "All-in-one" is..
"adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
what's wrong ?
Click to expand...
Click to collapse
Try to rename the zip into cm10 or something. That will help..
Related
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Bairdog35 said:
Hello! Sorry for posting this here, Idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, I have searched the forums before to see If someone had found a solution while I was having the error!
Sorry for this, but I posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 So moderators will you please delete the above post! Thanks so much!
This has happened to me so many times, I got frustrated, then I tried this out of the blue and it seemed to work..
Some examples of ROMS that froze on boot on my HTC EVO 3D HBOOT 1.5
All Infected ROMS
MIUI
Synergy
Senseless ROM
CleanRom
and some others..
These are the steps I took to fix the issue!
1. Flash ROM and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (Power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into PC or MAC
4. Make sure you have the latest android SDK, im pretty sure you do if you have been flashing roms!
5. EXTRACT the .zip file of the ROM that you are using that freezes.
6. Open the folder and copy the boot.img from that ROM
7. Paste that .img into the folder that has your adb and fastboot files for the Android SDK!
8. in terminal navigate to that folder, and do the following commands
PC:
Code:
fastboot flash boot boot.img
Ive done it on the PC and most of the time I have issues.. like failing of transferring over of the boot.img.. So far I don't know a way around this besides to keep trying!!
MAC:
Code:
./fastboot flash boot boot.img
Ive done it on my mac as well, and so far I have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~Bairdog35
Click to expand...
Click to collapse
Your problem lies in your HBOOT 1.5.... you need to flash the kernel separately, either the way you described it, or I think theres an app called FlashGUI
or just access recovery from fastboot & flash like normal.
This should be moved
Lulz. 10 char.
Sent from my PG86100 using xda premium
SketchyStunts said:
or just access recovery from fastboot & flash like normal.
This should be moved
Click to expand...
Click to collapse
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
arozer said:
This.
Maybe OP doesn't know about it so I'll guide him.
OP, we appreciate you trying to help but if you follow the steps below you should have no problem.
1. Download the Rom you want and place it on your sd card.
2. Plug your phone in to your computer and open a cmd file where 'adb' is located and type "adb reboot bootloader".
3. Your phone will now restart and boot into bootloader. Now type in "fastboot boot recovery.img". Your phone will now boot into your recovery.
(At this point, you can unplug your phone.)
4. Use the recovery as how you normally would and wipe/flash, etc.
Enjoy.
Click to expand...
Click to collapse
Yes I do this, and I still have to do what I provided up above. Idk what is wrong with my phone.
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
shadowmike said:
Your recovery can't flash kernels. Hence the boot loop.
There is a program in the evo3d theme and apps forum for us 1.5 boot loader users to flash the kernel using an app in android then you reboot to recovery and flash rom.
The app is called flash image GUI
http://forum.xda-developers.com/showthread.php?t=1192527
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode!
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
If you use that app and flash the boot.img from the rom and then go into recovery and flash the rom it should work
Sent from my HTC Evo 3D using XDA App
bairdog35 said:
hello! Sorry for posting this here, idk if this is the right area for this kind of thing but anyways lets get started!!
Im sorry if this had already been posted, i have searched the forums before to see if someone had found a solution while i was having the error!
Sorry for this, but i posted this already here: http://forum.xda-developers.com/showthread.php?t=1370478 so moderators will you please delete the above post! Thanks so much!
this has happened to me so many times, i got frustrated, then i tried this out of the blue and it seemed to work..
Some examples of roms that froze on boot on my htc evo 3d hboot 1.5
all infected roms
miui
synergy
senseless rom
cleanrom
and some others..
these are the steps i took to fix the issue!
1. Flash rom and see if it freezes on boot, if it does start below
2. After flashing rom and confirming that it does freeze.. Boot into bootloader (power+volume down key) and press the power button while highlighted over fastboot.
3. Plug in your device into pc or mac
4. Make sure you have the latest android sdk, im pretty sure you do if you have been flashing roms!
5. Extract the .zip file of the rom that you are using that freezes.
6. Open the folder and copy the boot.img from that rom
7. Paste that .img into the folder that has your adb and fastboot files for the android sdk!
8. In terminal navigate to that folder, and do the following commands
pc:
Code:
fastboot flash boot boot.img
ive done it on the pc and most of the time i have issues.. Like failing of transferring over of the boot.img.. So far i don't know a way around this besides to keep trying!!
mac:
Code:
./fastboot flash boot boot.img
ive done it on my mac as well, and so far i have had no errors! It works everytime.
9. After that reboot your phone..
10. Watch in awe as your phone should reboot and not freeze!
Thank you for reading this!!
~bairdog35
Click to expand...
Click to collapse
this worked for me it was hanging at the htc white logo screen did this steps and the phone passed the first boot logo and it turned on fine!!!
That's due to not flashin a kernel right or you skipped a part of the wipe.
Virus has this guide for flashing the kernel on his page
The problem with using this "Flash Image GUI" is the FACT that if an individual can't boot a ROM, they obviously can't run the apk.
Individuals with HBOOT 1.5 have two choices in this situation (bootloop)...
Either
1. "adb reboot bootloader" after which you run "fastboot boot recovery.img" (recovery.img must be placed in fastboot directory), then you flash the ROM/kernel in question...
Or
2. Flash boot.img through fastboot (which is what the above "should" do in the fist place).
BTW: If you always have a problem with bootloops, you aren't loading recovery the way you should...
You can either run the commands mentioned earlier in this post, or go to
forum.xda-developers.com/showthread.pho?t=1403148
and download the batch in the second post "jthein1989_batch.zip" (you will still need to download and copy the recovery.img to the folder).
Just download twrp or clockwork and copy it as "recovery.img" to the directory that you unzipped the batch to... Then, just follow the OP of my thread...
Sent from my PG86100 using XDA App
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Or you could try...
Fastboot boot my kernel or ill kill you.img
Sent from my HTC EVO 3D using xda premium
jcfunk said:
Maybe I'm a noob,
But you mean you can't select Recorery from Hboot menu? Even if you installed twrp? I don't know much of what I'm doing only had 3d for week. but its locks up at white HTC screen all the time.
Click to expand...
Click to collapse
With HBOOT 1.5 you "can" start recovery without ABD, but "S-ON" will not allow you to properly flash to the BOOT partition (limitation of the HTC unlock method). Therefore, users with HBOOT 1.5 need to go to extra lengths to flash the BOOT partition.
Sent from my PG86100 using XDA App
Having HBOOT 1.5, I've ran into this very problem. I'm not sure if it's hardware or what, but my phone will not run any Sense 3.5 ROM's I've tried. The phone just won't boot! I gave up trying 3.5 ROM's. I used ABD to put a 3.0 kernel back on and restore the recovery and everything is fine again. This will probably be my last HTC phone. Hoping something better besides the S2 is coming soon.
When i open bootloader (Holding Power + Volume-down), it keeps pushing a 'update' whether i click yes or no, it still forces me to reboot which in the end leaves me stuck on the HTC white screen.
Any help would be welcomed
diddykonga said:
When i open bootloader (Holding Power + Volume-down), it keeps pushing a 'update' whether i click yes or no, it still forces me to reboot which in the end leaves me stuck on the HTC white screen.
Any help would be welcomed
Click to expand...
Click to collapse
1. Easiest is to plug your phone into a computer while its off and adb works when it's off. Deleted the update.zip or ph98img.zip on your sdcard.
option 2.
take out sdcard. boot into hboot. plug phone into a charger usb or wall. pull battery out and put in sdcard, put battery back in and enter recovery.
Thanks for that, ended up doing the second option
Now, was wandering if i could get some assistance with flashing to EclipticRez.
First, while in TWRP 2.3.3 i got to wipe, run Factory reset, then cache, then dalvik cache.
After having done that, i go to install and find a folder i created called Roms which holds the EclipticRez.zip, and choose it. I proceed through the options, choosing Lunar for the kernal, and choosing S-On for the safety mode. Let it run through a rather super quick installation then it asks me if i want to reboot i click yes, and am still presented with an every lasting HTC White Screen.
Would you happen to know what im doing wrong? Thanks
diddykonga said:
Thanks for that, ended up doing the second option
Now, was wandering if i could get some assistance with flashing to EclipticRez.
First, while in TWRP 2.3.3 i got to wipe, run Factory reset, then cache, then dalvik cache.
After having done that, i go to install and find a folder i created called Roms which holds the EclipticRez.zip, and choose it. I proceed through the options, choosing Lunar for the kernal, and choosing S-On for the safety mode. Let it run through a rather super quick installation then it asks me if i want to reboot i click yes, and am still presented with an every lasting HTC White Screen.
Would you happen to know what im doing wrong? Thanks
Click to expand...
Click to collapse
You need to flash the boot IMG if you are s on.
Sent from my ADR6425LVW using Tapatalk 2
Do i do that after i have installed/flashed the ROM?
and where do i need to be to do it? (Recovery, HBoot, etc..)
Thank you for your help
diddykonga said:
Do i do that after i have installed/flashed the ROM?
and where do i need to be to do it? (Recovery, HBoot, etc..)
Thank you for your help
Click to expand...
Click to collapse
Flashed in fastboot. "fastboot flash boot boot.img" You can flash the boot.img after or before you install the rom.
Well i tried using the hansoon tool, and just using the command prompt, but im still getting stuck on the white HTC screen
Any help?
Tried relocking my hboot, but now for some reason my adb wont ever detect my phone.
Can anyone help? like a link to the drivers or something?
I'm s-on and just flashed Ecliptic myself.
I selected Lunar kernel and my phone didn't do the kernel install itself but it put the PH98IMG file on my sd card. I can't remember if after the ROM flashing it left me at the bootloader or not, but you should be able to get to it.
Perhaps you thought that was the OTA and wanted to not take it? If it appeared immediately after flashing the ROM it's the kernel and you need to let it flash in order to be able to completely boot up the phone.
At this point you need to unlock the bootloader again. Then disconnect the phone from pc, power down, pull battery and boot into bootloader by holding vol down + power until the bootloader screen shows up. It should find the PH98IMG file and ask you if you want to update, say yes.
If you pulled the "stockboot.img" file from the ROM it may not be working since you selected the Lunar kernel during the ROM flash setup.
If you've already deleted the PH98IMG file then just pull the lunarboot.img and flash that in fastboot, it should work. You can just do it right after unlocking the phone while it's still connected to your pc.
fastboot flash boot lunarboot.img
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
JM1084 said:
I am running santod's rooted Stock ICS rom, which has been running excellent, love it very much. Today I went to do a backup in recovery and noticedit will not boot into recovery. I am running the 4EXT recovery as suggested in the rom forum post. Nothing I do seems to be able to boot the recovery. I can't reboot into recovery from the 4EXT app. I boot the phone with the volume down key, and try to enter recovery from there. Still nothing. I get my initial boot logo, then screen goes black, then boot logo again and it proceeds to boot up normally. I have tried re-flashing the recovery from the 4EXT app, I even tried rom manages and using the latest clockwork mod recovery. Nothing gets me into recovery. Also have noticed my phone will not stay powered off when on the charger. If I power off, plug the charger in, after a few seconds phone powers itself on. Could it be related?
I followed the rom installation instructions to the letter.
Installed the 4EXT recovery.
Flashed the ICS radios.
Wiped all my partitions except my SD card.
Flashed rom and have enjoyed for weeks now.
Only other info I know to provide is I installed the debloated/deodexed rom
Did not flash the kernel as I didn't experience boot loops.
Thanks in advance for any assistance folks!
Click to expand...
Click to collapse
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
santod040 said:
Did you rename or remove the Radio file from the sd card as suggested in the OP of the rom thread?
It will not let you get into Recovery if there is a PG05IMG.zip present on the root of the sd card.
If that's not the case, reflash 4ext from within the Recovery control app.
Just installing the app doesn't install the Recovery.
You must also install the actual Recovery from within the app if you haven't.
Click to expand...
Click to collapse
Yeah, there is no PG05IMG.zip in the sd card root. Also I have tried reinstalling the recovery from the 4EXT recovery control app.
Current verson of recovery installed is 4EXT Recovery Touch v1.0.0.5 RC8.
Tried reflashing that, and also the RC9 test build that is out right now.
Still no go on getting into the recovery.
Thanks.
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
santod040 said:
When you do the volume down and power option with the device off, you need to first press the volume down and then while holding that, then press and also hold the power button, you should feel it vibrate, keeeeeep holding them down, do not let go.
Wait until you see what should be a white hboot screen with menu options, then you may let go.
If you hold power first or don't hold them both down long enough, it will just try to boot normally.
Not that that would explain why you can't get there from within Recovery Control app.
What is your hboot version and how did you root your device?
Click to expand...
Click to collapse
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
santod040 said:
Yes, you can flash Recovery images from hboot, just like you flash a radio.
With it named PG05IMG.zip and placed on the root of the sd card.
HERE is one you can try.
If that doesn't work, I may have something you can try from fastboot to clear the Recovery cache, and maybe that will resolve the issue.
I have only seen one other user have this occur and his device simply ended up getting replaced because he wasn't able to mount to usb for doing fastboot commands either.
Click to expand...
Click to collapse
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Edit: I confirmed his hboot is 6.04.1002. same as mine
JM1084 said:
Still no go flashing that recovery in hboot. What is the process of clearing recovery cache?
On a side note, in talking to my father, his bolt seems to have the same issue. We both were rooted with the same method, and I believe we have the same hboot version. Only difference is he flashed the rom using clockwork recovery.
Click to expand...
Click to collapse
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
Alrighty, I will give that a shot. I am at work right now and am about to head out of town so I will be unable to try it until sunday. I'll post the results here asap. Thanks again!
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
zomgalama said:
Same ROM, same problem,I even tried flashing a different recovery. Rooted using really old one click method a month after thunderbolt release.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
What is your h boot version?
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Well, I've got several Bolts here, and a couple of them have that same hboot and were used to test the stock roms with.
So I do not think it's a root or hboot issue, but I do not know what the issue would be other then corrupt Recovery cache.
To try and fix it by clearing the cache, do the following:
Download the erasecache.zip file from www.4ext.net/erasecache.zip
First boot your device into bootloader while connected via usb.
If it reads "fastboot usb" you are already in fastboot mode.
If it reads "hboot usb" then select "fastboot" in the bootloader menu.
Extract the file anywhere on your computer, and then start the file erase_cache.cmd with
elevated rights (right click erase_cache.cmd and select to run as administrator)
Watch for any error messages and tell me the results please.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If the above method fails, try this way:
This requires a little adb or command line knowledge(not much) and the appropriate files on your system.
Please boot into bootloader -> fastboot mode
and then issue the following fastboot command:
fastboot erase cache
afterwards boot recovery from the bootloader menu and enter the
wipe menu and format cache
Click to expand...
Click to collapse
No Go, my tbolt will not mount in Win7, it just says the device has malfunctioned. Rebooting into the bootloader with USB in will not show anything in Windows, even in fastboot. It makes the device connection sound but no devices show up. Running the CMD file in the zip you linked does nothing, I'm at 10 minutes now where it just says "Waiting for device". Is my device just done for?
JM1084 said:
It was rooted using the Revolutionary method, did it a year or more ago.
Hboot version is 6.04.1002
When I try to go to recovery from the hboot screen it does the same, vibrate, white HTC screen, black screen, vibrate, white HTC screen, normal boot. No recovery.
Is there any other method of getting into recovery or re-flashing the recovery?
Click to expand...
Click to collapse
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
coltspackers said:
I think I had a similar problem once. Boot back into your hboot screen. Then select "factory reset". If you have a 3rd party recovery installed, like it sound like you have (4ext, right?), it will boot you to recovery so you can administer the reset yourself (it doesn't actually wipe anything, just brings you to your recovery's home screen).
Let me know how it goes.
Click to expand...
Click to collapse
Thanks for the info, but this didn't work either. I'm also on 6.04.1002 and rooted mine a week after the T-Bolt shipped manually via adb.
This happened about a month ago also, and I thought it was ext4 but managed to get an older TWRP recovery to work after working on it for about a day and a half without a working phone. At least I have a working phone at this point.
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
allo_87 said:
Same ROM, same recovery (4ext), same problem. Rooted by adb a month after launch, hboot 6.04.1002
Click to expand...
Click to collapse
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
Excellent advice, thanks man.
Sent from my ADR6400L using Tapatalk 2
My thunderbolt's recovery spin mysteriously started working again yesterday, not sure why.
Doesn't matter though since I switched carriers now:/
Sent from my Sprint LG Optimus G
Still nothing for me. Worse yet is the fact that I can't adb because my usb has not worked properly since "the soup incident"
Sent from my ADR6400L using Tapatalk 2
santod040 said:
Might be wise to bring it to Max's attention.
He makes the Recovery that is disappearing and may have suggestions or ideas on how to prevent this in the future.
I have flashed every rom I have ever posted at least once.
Most of them, may times and have yet to run into this issue.
I have had Recovery become corrupted once or twice quite some time back and not be able to get into it.
But it was easily fixed by reinstalling/reflashing a recovery.
I guess what I'm saying, is if there is a common issue occuring on our device with some ICS users and his Recovery, he should know about it.
Here's how to contact him: LINK
Hopefully he can help or look into the root of the issue, since I know he has had a few users with this same issue in the past.
Click to expand...
Click to collapse
After going over the issue with Max and trying several fixes he suggested (he even made me an app that would format my cache), it seems I either need to obtain an RUU and flash the stock software/recovery back on and re-root or try flashing an updated hboot that already has s-off. The thinking is that it is my hboot that is causing the issue. Does anyone know what files I need? I have a couple of things to try at home to see if I can get my usb working again, if not, anything I do will have to be a flashable zip from the bootloader. Thanks!
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Seleren said:
Hello there,
I've had my OneX+ for a few months already and I've been using TWRP for quite a while. A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery. The recovery worked for a while but then the phone decided to simply not boot into recovery at all and instead rebooting into the ROM again. I tried reflashing the recovery and using CWM instead of TWRP. CWM seems to work but when I try to do a backup it just reboots back into ROM after it seems like it almost finished the backup, if I try to Factory reset/wipe anything the phone again simply just reboots to ROM ...
I really have no idea what to do now, plzhalp.
Click to expand...
Click to collapse
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Lucky Thirteen said:
Hi Seleren...
Can you specify which phone version you have? AT&T/TELUS or International?
That would really help us to guide you to the good solution. Don't worry you can not brick your device with patience you'll be back on track.
Click to expand...
Click to collapse
I have the International model.
jbharbin said:
i had an issue like this a while back. open up an abd and run fastboot erase cache, fastboot flash recovery (yourrecoveryname).img, then fastboot erase cache again. mine wouldnt boot into twrp after flashing a rom, it would show the teamwin screen then boot into the rom and these steps fixed it.
Click to expand...
Click to collapse
Tried that already, nothing changed at all, TWRP logo shows up and then the phone reboots to ROM. CWM works partially as I said, it reboots when I tell it do do anything (backup/wipe/flash) and the phone is unaffected.
Bump. Help please, I tried flashing another kernel but that didn't help. I can't even wipe or flash another ROM in CWM.
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Try redownloading the recovery and rewriting it. It may be a bad download.
Sent from my One X+ using xda premium
Re: [Q] Recovery problems - unable to boot into TWRP, CWM fails
Flash the kernel and then the recovery with fastboot and see what happens.
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
@Seleren I would be interested to know if the above worked for you? Also useful if anyone else gets this problem
Lucky Thirteen said:
Download a fresh recovery for your International (ENRC2B) model here.
Put this file in the platform-tools of your SDK folder.
Plug the USB cable coming from your computer to your phone.
Then open a command prompt window and type : adb devices (you should see your serial at the screen)
Again type : adb reboot-bootloader (Enter)
Type again this command : fastboot devices (you should see your serial at the screen)
Type this command (if serial is successful) : fastboot flash recovery your_recovery_name.img (Enter)
Clear cache with : fastboot erase cache (Enter)
Once done unplug your USB cable, click one time on Power button.
One Volume rocker down to select Recovery.
Confirm by clicking on Power button to reboot in Recovery.
Try to flash an International ROM only.
What result you obtain by doing this?
Click to expand...
Click to collapse
I've already tried that numerous times, I can get to erasing cache etc but once I try to boot into the recovery ... I'm done. TWRP won't boot even after erasing cache. CWM fails at wiping/backuping/flashing and just reboots without any notice at all. I'm really out of ideas now.
Sorry for a bit late answer.
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
Seleren said:
Hello there,
... A few weeks ago, though, I flashed ViperX ROM and their TWRP-mod recovery....
Click to expand...
Click to collapse
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Lucky Thirteen said:
This is really strange. Are you sure you are correctly rooted? Which method have you followed to root your phone? The above method I gave you, I have done this numerous times, switching from CWM recovery to TWRP recovery to access different backup on my phone, and it never fails on me.
Are you sure that your SDK folder is well installed and fully functional? Are HTC's drivers correctly configured? What is your phone responding to you when you type : adb devices?
---------- Post added 20th March 2013 at 12:14 AM ---------- Previous post was 19th March 2013 at 11:25 PM ----------
I know you are not allowed to post yet in their thread but I suspect your issue could be related to their ROM, I will try to point this thread to someone from Venom ROM.
Click to expand...
Click to collapse
Yes, I am correctly rooted, I've rooted numerous phones, I unlocked using the official HTC method. I could say I'm not a complete noob to Android. I wouldn't even post here if I didn't try all the standard procedures.
I flashed the Non-touch CWM yesterday and nothing changed (not that I expected it to). I decided I'll try flashing the bootloader in the end but I have to back up my whole SDCard before that ...
Bump.
SALVATION
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
hukel56 said:
Here something strange I've been encountering... Every time I flash a boot.img over TWRP it won't boot to TWRP. I have to flash the recovery over the boot.img.
Click to expand...
Click to collapse
wut?! TWRP = Recovery
boot.img = KERNEL
Seleren said:
Well, since I don't want to be like others who just say "Solved", here's the solution I came up with.
1. Get your new ROM's zip to your SDCard
2. Flash CWM since TWRP won't boot
3. Flash ROM from CWM, it will be flashed even though the phone will unexpectedly reboot.
4. Flash the bootImage from fastboot (Thank god at least that works)
5. Go back to recovery, go to Mounts menu and wipe every options you can (cache, data, system)
6. You will most probably lose your SDCard data too.
7. Reflash the ROM you wanted.
8. Voila.
PS: Disclaimer: I am not responsible for any damage to your device that may occur while using this procedure.
Click to expand...
Click to collapse
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Lloir said:
wut?! TWRP = Recovery
boot.img = KERNEL
Click to expand...
Click to collapse
Yea idk. But this happens
Lloir said:
either you used the wrong TWRP recovery image or it wasn't flashed correctly
Click to expand...
Click to collapse
I wish that was the problem, I tried quite a few versions, including the one from ALL IN ONE toolkit, an older version that previously worked, the latest version and the ViperX version. Trust me, that was not the problem.
hukel56 said:
Yea idk. But this happens
Click to expand...
Click to collapse
What Lloir meant to say was that the boot.img has nothing to do with the recovery, so flashing a boot.img will NOT change your recovery to so-said TWRP.
TWRP is being flashed by a different command namely 'flash recovery' instead of 'flash boot' like previously mentioned boot.img
Alright, so i have an EVO 4g lte and i attempted to root it today. It didnt turn out very well to say the least... I unlocked bootloader and flashed TWRP recovery.I then flashed superSU, and at the same time i flashed a custom rom and gapps zip. Then hit reboot. It has not booted up since.. It will just sit at the white HTC screen. i tried clearing cache and Dalvik cache, also did a factory reset. tried flashing cm10 rom onto the device as well as a rooted stock rom. nothing works! the farthest i have gotten was with the cm10 rom and it went to the cyanogenmod boot logo but was in bootloop still. I downloaded the ADT tool bundle but the phone wont show up on the device list. Can anyone help? im completely stumped.. Im fairly new to rooting and custom roms, but i have rooted multiple tablets and samsung galaxy phones and havent had any issues. this is my only phone also, i just gave my backup to my mother because her phone broke... please if anyone knows how to fix this let me know. when i boot into recovery mode it says Tampered and Unlocked at the top as well as S-On. I can also go into TWRP recovery with no problems. just cant use fastboot with my computer (windows 7 PC).
I am pretty sure i know what i did wrong, I flashed SuperSU to gain root at the same time i flashed the custom rom and gapps.. on all the other devices i would reboot after root and then flash the custom rom seperately.. but is there a way to correct my mistake?
Since you are s-on you have to fastboot flash the boot.img/kernel first and then flash CM and gapps
Any questions PM me
OK sorry to be a noob but how do I do that? I used cmd.exe while rooting but now it won't recognize my device. Much thanks for any help!!
Sent from my GT-P5110 using xda app
If in bootloader type fastboot devices
In recovery type adb devices
See if you get a reply
In fast boot USB menu on the phone, I typed fastboot devices on cmd and it came up blank.
Sent from my GT-P5110 using xda app
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
bigdaddy619 said:
Sounds like a driver issue
1.Uninstall everything HTC from your PC
2.Reboot your PC
3.Plug your phone in and it will load a bunch of drivers
4.Try the command again
If that does not work get the latest drivers from HERE use the ones dated 6/6/13
and don't forget the BMP drivers towards the bottom of post 1
Click to expand...
Click to collapse
ok ill uninstall all that and give it a try. is pm a better contact method for you?
AUSRA15 said:
ok ill uninstall all that and give it a try. is pm a better contact method for you?
Click to expand...
Click to collapse
Here is fine
bigdaddy619 said:
Here is fine
Click to expand...
Click to collapse
OK rebooting now I'll see if it uninstalled everything.
:fingerscrossed:
OK were connected now, now what? :good:
PC and phone are talking ?
fastboot devices
yes they are talking now. fastboot devices and my phone shows up.
i tried fastboot flash boot.img but it wont recognize the command, i placed the boot.img file into the platform-tools folder inside my C drive. what am i doing wrong? its late at night and im frustrated so i know im screwing something up...
ok good BTW which version of twrp are you using? Let me know before you continue.
pull the boot.img from the rom zip and copy it to the folder you opened your cmd window from
then type fastboot boot boot.img
once it says successful press the power button to return to HBOOT and use the vol keys to navigate to recovery
Once there choose wipe and wipe cache/dalvik cahce/system/data or factory reset depending which version of twrp you are using
then flash CM and gapps
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
AUSRA15 said:
C:\Users\Corey>fastboot boot boot.img
cannot load 'boot.img': No error
thats what i typed in and thats what it said back to me. not quite sure what the problem is.
the boot.img is placed in the same folder as the fastboot application
Click to expand...
Click to collapse
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
bigdaddy619 said:
try fastboot flash boot boot.img
My bad I was looking at a buddies thread for the commands
Click to expand...
Click to collapse
same thing, cannot load unknown error. also i am using twrp 2.6.0.0
Ok lets try something different at least it will get you up and running
Get twrp v2.4.1.0 from http://techerrata.com/browse/twrp2/jewel
put it in the same folder you are using and we will downgrade your twrp for now
copy and paste this in the cmd window
fastboot flash recovery openrecovery-twrp-2.4.1.0-jewel.img
then fastboot erase cache
ok got the twrp done succesfully as well as the wipe cache. whats next? i think i figured out what i was doing wrong, i hadnt opened the file directory. cd downloads, cd android files, etc.
should i try going into recovery now on the phone and flash a rom, or should we stay on fastboot and push the boot.img?
Easiest way to open a cmd window is to press shift and right click inside the folder and choose open cdm window here
That way you know you are in the correct folder.
Yeah go ahead and try to flash the boot.img again