Develop Bugs

Stuck on HTC Boot image please help

Two weeks ago:
I rooted my phone using HTC's method since I had already ran the update to 1.5 shooter. I flashed CWM to the recovery of the phone and took a backup. Loaded ViperROM and all was good.
Last night:
I wanted to load a new kernel since the one I put on there was not working well with WiFi. At the time I did not know i could just boot to HBOOT then go to recovery I thought I had to use Fastboot. Using Fastboot and doing the commands from memory I think I flashed it to the boot instead of recovery... Not exactly sure what I did but whatever it was i'm stuck in a continual reboot that gets no further then HTC.
What I've tried so far to resolve issue:
1. Boot into recovery and restore from backup. - Did not work
2. Boot to recovery and load a new ROM (Myns zip). - Did not work
3. Boot to recovery and load a stock ROM (4.53.651.1_Rooted_deodexed_signed.zip) - Did not work
4. Rename the stock ROM(from above) as PG86IMG.zip and put on SD. - Didnt work
Any ideas cause i'm out and I dont want to go back to my previous Evo 4g.

cgprelude said:
Two weeks ago:
I rooted my phone using HTC's method since I had already ran the update to 1.5 shooter. I flashed CWM to the recovery of the phone and took a backup. Loaded ViperROM and all was good.
Last night:
I wanted to load a new kernel since the one I put on there was not working well with WiFi. At the time I did not know i could just boot to HBOOT then go to recovery I thought I had to use Fastboot. Using Fastboot and doing the commands from memory I think I flashed it to the boot instead of recovery... Not exactly sure what I did but whatever it was i'm stuck in a continual reboot that gets no further then HTC.
What I've tried so far to resolve issue:
1. Boot into recovery and restore from backup. - Did not work
2. Boot to recovery and load a new ROM (Myns zip). - Did not work
3. Boot to recovery and load a stock ROM (4.53.651.1_Rooted_deodexed_signed.zip) - Did not work
4. Rename the stock ROM(from above) as PG86IMG.zip and put on SD. - Didnt work
Any ideas cause i'm out and I dont want to go back to my previous Evo 4g.
Click to expand...
Click to collapse
From what I've read regarding the HTC unlock method, when you boot the custom recovery, the HTC unlock method does not grant the custom recovery write access to the boot partition.
There are only three ways I'm familar with having write access to the boot partition when having used the HTC unlock method:
1) From normal android mode, the boot partition is unlocked and you can flash a kernel/write to it. My application, Flash Image GUI, works great for this purpose.
2) Using fastboot to temporarily load the custom recovery. When using fastboot to temporarily load the custom recovery, the HTC unlock method grants the temporarily loaded custom recovery write access to the boot partition.
3) Having the bootloader directly flash the boot partition via a PG86IMG.zip file.
Hope that helps! Good luck!

#2. That reminds me. I did try to use fastboot to flash the boot partition. I was doing: fastboot boot (kernel i found online as .zip) (stock rom i found online.zip)
This did not work then i tried:
fastboot flash:raw boot (kernel) (rom.zip)
this did not work either. Am i doing this wrong?
Your #3 option. Where can I download the PG86IMG.zip file so that the bootloader will flash my boot partition?

cgprelude said:
#2. That reminds me. I did try to use fastboot to flash the boot partition. I was doing: fastboot boot (kernel i found online as .zip) (stock rom i found online.zip)
This did not work then i tried:
fastboot flash:raw boot (kernel) (rom.zip)
this did not work either. Am i doing this wrong?
Your #3 option. Where can I download the PG86IMG.zip file so that the bootloader will flash my boot partition?
Click to expand...
Click to collapse
2) fastboot boot c:\downloads\custom-recovery.img or temporarily boot the custom recovery with write access to the boot partition to flash the .zip file
also, you can directly flash the kernel, but the modules will not work until you manually push those: fastboot flash boot c:\downloads\boot.img
3) http://goo-inside.me/shooter/ruu - the latest version is 2.08 which must be what you're using to have used the HTC unlock method.

It seems that u have an evo 3d but u are trying to use evo 4g rom. Or maybe I'm not understanding this
Sent From My Pocket

Semi-bricked One X

Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me

did you erroneously flash the boot.img to the recovery partition? that would be the only thing that would cause that i'd think..
i would retry the following.
fastboot flash recovery clockworkmod-5.8.4.0.img
fastboot flash boot boot.img
fastboot erase cache
with boot.img being the kernel provided with your cm10 rom and clockworkmod-5.8.4.0.img being the name of your CWM recovery image.
as for fastboot working intermittently I would check to make sure the cable is snugly plugged into the computer and try another cable if possible.

Vorphs said:
Hy guys,
I have a international rooted One X. I decided to switch to a non sense ROM so I flashed Cyanogen 10 on it and now I'm having major problems...after I flashed it, I was stuck in a boot loop - the phone was constantly restarting at the Cyanogen logo. I went to Hboot, and tried to go into recovery to flash something else, but when I clicked recovery, the phone restarted and Cyanogen was working This is the only way to enter Cyanogen now, as a normal reboot or shut down will just get me into the boot loop and I cannot enter recovery at all...also, the phone is not charging when its turned on/cyanogen running...only charges when its shut down...I have no ideea what the hell happened...fastboot is not really woking either, most of the time its just stuck at "waiting for phone" part.
Please help me
Click to expand...
Click to collapse
I have just overcome a similar problem myself.
Start over, and do factory reset (after nandroid). Then flash the latest clockwork recovery to your phone (CWR 5.8.4.0) using
"fastboot flash recovery <filename.zip>" in the command line
then, boot into recovery, insert usb cable and choose mount usb. simply drop CM rom zip file onto your phone form the PC.
then unmount, go back to recovery menu and select install zip from sd card, then choose your zip file. after this, select reboot system from recovery. it should work fine.
I think you may have acidentally installed the CM10 rom as recovery using the wrong syntax in fastboot.
Hope that helps

Thx for the reply's, unfortunately whenever i try to flash something using fastboot, i get "error: cannot load imagename.img". Only the erase cache command works...

Fixed it using fastbootflasher!

[Q] Boot Loop and not entering recovery!

I wasn't able to adb sideload from recovery though I could when the phone was on. so i tried clearing cache from stock recovery and it got interrupted. Now when i start the phone, boot loops and i can't even enter recovery. Any help please!

Update
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?

AnudeepS said:
Now I can enter recovery after long charging and I could wipe cache. I can boot normally.
Problem now is that adb devices command can actually detect the phone when it's booted and functioning; but the adb devices command can't detect the device when in fastboot or after entering recovery! Can anyone provide solution to this?
Click to expand...
Click to collapse
Where are you getting your adb/fastboot toolkit? If using the ones your Linux distro (Debian, Ubuntu, etc) provided, then consider them out of date. I had the same problem with fastboot recognizing my phone...once I downloaded fresh ones from Google's SDK, I was back in business!

Am on windows and i had fastboot_adb(1.0.32) already installed.

Update
I could update by flashing through Kernel Adiutor app (needs root permission & Busybox). Root lost when flashed complete firmware and root remained when flashed just the update file.zip.
what i did was-
I put zip file (completely downloaded firmware from ASUS website-also tried OTA downloaded and updated the phone) on MicroSD card, renamed the file MOFD_SDUPDATE.zip. This flashed through Kernel Adiutor app- recovery- cwm-flash.
Re-reooted the phone with 1 click method (method #3) when flashed the complete rom. If you just flash the update zip root remained.
All working fine for now.
PS: I use Z008 2gb model.

I can flash a rom and gapps, but it still boots to TWRP 3.0.1 recovery. Any ideas?

I was given a bad kindle fire hd 8.9 that failed a factory update and was stuck in a factory boot loop with restore options that didn't work. I have done a lot of work on it and have gotten it to the point where I have TWRP 3.0.1 on it and I think I have the drivers working correctly. It shows up in device manager, fastboot works, and I can transfer files via windows explorer over to it. I can flash a rom via twrp after dragging files to it in windows explorer, but after flashing ResurrectionRemix-M-v5.6.9-20160528-jem.zip and open_gapps-arm-6.0-nano-20160605.zip it just reboots back into TWRP. I have tried to use the 2nd bootloader thread and did the following:
fastboot -i 0x1949 flash bootloader kfhd8-u-boot-prod-8.1.4.bin
fastboot -i 0x1949 flash boot kfhd8-freedom-boot-8.4.6.img
and I already have TWRP 3.0.1, so I didn't re-flash that. After that, within TWRP, I flash the resurrection remix rom and gapps, but it boots back to TWRP when I reboot it after a successfull rom install. Any ideas? Thanks!

Never mind. It booted successfully after several reboots with it going to recovery. Not sure why it took that many reboots or power cycles to boot.

My OP3 won´t boot into recovery even after flashing stock image via fastboot

Hello everyone,
i think my OP3 is bricked, cuz after i wanted to install new custom ROM with TWRP it went south. When I swiped to install the ROM it showed, it´s corrupt so i wanted so i wanted to push some other .zip to the phone through adb, but no device showed after adb devices or fastboot devices in fastboot. So I tried restore phone from backup i had via TWRP and the phone just wouldnt boot. Oneplus logo showed for a few seconds then it disappears and phone goes dark. Have to hold start button for 10 sec for hard restart phone and then i can go only to fastboot (now it will show fastboot devices in command line). Recovery won´t boot. Tried flashing stock recovery, some versions of TWRP and still just OP logo and dark.
Thanks for every help.

I think for:
fastboot -w
fastboot flash recovery recovery_of_ur_choice.img
on flashboot mode obviously ^^
With that, u must have access to twrp