• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Boot loop/soft brick help

two questions: I put the 4ext pg86img.zip in my root sd card and doesn't show up when tried to flash from twrp 1.1.

#2: I have folders taking up some space on my sd card, like goo-manager and program isn't on the phone. Can't I delete them without issues, since not on cyan 10.1 os. Far an app goes.
 
You can't flash a PG86IMG zip through recovery. You boot into the bootloader and say yes when it asks you to update. As far as deleting the folders you will be fine.
 
I want to clarify this: Safely remove your SD Card, then disconnect it in TWRP

I choose usb storage toggle in twrp 1.1, put the cyan 10.1 in the root of sd card. and it power button to toggle it back. Is that what you mean by "disconnect"??
Yes. What I mean by safely remove is to eject or safely remove it from your PC first. The terminology may be different depending on your computer, but the meaning will be the same. After that, disconnecting the USB by whatever means TWRP tells you is the second step. I've never used TWRP, so I'm not familiar with how it works.
 
two questions: I put the 4ext pg86img.zip in my root sd card and doesn't show up when tried to flash from twrp 1.1.
Anything named PG86IMG.zip can ONLY be flashed through the bootloader. You cannot & should not flash these with the recovery. These are firmware files, which recovery is not equipped to handle.
 
Anything named PG86IMG.zip can ONLY be flashed through the bootloader. You cannot & should not flash these with the recovery. These are firmware files, which recovery is not equipped to handle.
You can also flash them with the "fastboot flash zip PG86IMG.zip" command but you need to be in the "fastboot usb" mode in the bootloader to do that. As you said, recovery is not an option for flashing firmware files.

ramjet73
 
You can also flash them with the "fastboot flash zip PG86IMG.zip" command but you need to be in the "fastboot usb" mode in the bootloader to do that. As you said, recovery is not an option for flashing firmware files.

ramjet73
Indeed... the problem encountered in this thread a couple of times with these PG86IMG.zip files is precisely why I personally prefer using fastboot to flash firmware. It's cleaner & easier in my opinion.
 
I wish Android OS had the option like Cyan 10.1. To boot in recovery or bootloader from your phone. Boy, that makes it easy vs. my pc finding it. I get more bars on my signal and Wi-Fi. Curious to see my battery life, going to bed with 100% and charging every other day is annoying.
 
So watching a youtube video from PocketNow, he talks about cyanogen 10.1 mod. Calling versions of nightly, stable versions..etc. So if I get updates from my phone, will they be "stable" or take your chances.
 
So watching a youtube video from PocketNow, he talks about cyanogen 10.1 mod. Calling versions of nightly, stable versions..etc. So if I get updates from my phone, will they be "stable" or take your chances.
This question is best suited to the developers of that ROM, or in one of their threads, but I believe updates delivered through their manager will be stable unless you specify otherwise in the settings.
 
I've got the following file that was linked for me 4ext_1_0_0_5_rc9 pg86img_zip in the root of my sd card. When I reboot evo v into bootloader it doesn't prompt me to update like told it should. Am I not doing this correctly??
 
I've got the following file that was linked for me 4ext_1_0_0_5_rc9 pg86img_zip in the root of my sd card. When I reboot evo v into bootloader it doesn't prompt me to update like told it should. Am I not doing this correctly??
It has to be renamed to PG86IMG.zip (caps matter).

ramjet73
 
Success...I booted into recovery (4ext) and it says am in "safe mode" and to wipe my cache. This sound about right. Should I wipe all of them. wipe dalvik cache also.
 
Now my recovery boots into 4ext, do I need to flash the 4ext updater or no need to run that. Now that am running cyan 10.1, any programs/software would be good to flash for my phone to run the best.
 
To clarify, the 4ext updater program is a pay program that is not flashed (just installed). Any programs that live inside of the ROM are not flashed, just installed. The difference is that things that are flashed modify low-level things on your phone, whereas software lives on top of that foundation.

Ad-away is a good program to get, and anything else you want... feel free to experiment!
 
To clarify, the 4ext updater program is a pay program that is not flashed (just installed). Any programs that live inside of the ROM are not flashed, just installed. The difference is that things that are flashed modify low-level things on your phone, whereas software lives on top of that foundation.
Actually the 4EXT Recovery Updater is a free app that can be downloaded from 4EXT Development and has to be installed from the apk (sideloaded). It's 4EXT Recovery Control that is the paid app in the Play Store.

If you've never download the updater app before you will also get a 3 day trial on the the advanced features, after which it will revert to just installing and updating 4EXT to the current version.

ramjet73
 
4ext recovery control is worth the cost, and it supports the great work the developer has done. Think of it like a donation for someone's hard work & dedication. If your phone is ever "broken" you have a safe place to fix it from.
 
when I was reading the "Wild for the night" post for cyanogen 10.1, it mentions a "Wimax log cleaner zip". Is this something should have done when installing cyan 10.1??
 
Just wanted to make sure had all the files to flash. Joe-Blow stating cyan 10.1 came with stock kernel, and linked a Team Dirt ASOP Kernel. But paragraph down had some hanging up issues.

Reason for asking, was when I was rebooting phone it showed the little white circle turning and then just got stuck there. I wanted to make sure wasn't missing programs to flash or install. I'll check with developer like you suggested....Thank You.
 
Hello everyone.

I own an HTC EVO V 4G, which I have come to understand is practically identical to the 3D.
I went ahead and did the simple(ish) bootloader unlock process through HTC Dev, and had my phone rooted for at least a year now, tried a few S-ON capable roms, the usual mild rooting stuff, etc etc....

Much more recently, I decided that some of these S-OFF roms make my Unsensible rom look pretty old, and tried out the whole Wire Trick method through unlimited IO.

After a solid 3 hours of staring at my laptop screen....
I rebooted into the bootloader with that glorious S-OFF overtop.

As you might understand... I was very eager to install one of those amazing roms, and downloaded and tried installing the PACman rom for the EVO 3D, admittedly (and regrettably!!) rushing a bit :/

So, after flashing and rebooting, I was stuck in a bootloop with PACman's boot screen. I tried rebooting back into recovery through bootloader (pull out battery, volume down + power, reboot into 4ext recovery) and wiping everything except SD-card, re-installing the ROM, with no success.
At that point I was frustrated enough, to the point where I ended up trying anything I thought might have the slightest chance of giving me my long-awaited rom.

I don't remember what I did exactly, but I flashed a few more files, actually modified the updater-script in the ROM zip.... :/
And now I'm stuck at that White n' Green HTC boot logo, it does not reboot, just stays on constantly, laughing at my hours of fruitless labor.

I can boot into the bootloader whenever with a battery pull, go into 4ext with no troubles.
I have a backup of stock rom, but after whatever I did... Everything I have tried gives me the same results.
I've spent literally the past 9 hours trying to fix this thing, stayed up all night because I need it for the day, and the next day, and the next day...

I tried using the RUU, but I have taken both OTA updates, and even when I finally did get it to start up and run, it denies me almost instantly...

Some device specifics:
I am using linux (Ubuntu).
I own an HTC EVO V 4G (shooter)
I used to run 4.0.4 stock ROM.
Switched to Unsensible (with no issues before S-OFF)
Using 4ext recovery.
Currently on JuopunutBear HBOOT-1.57.5757.
Radio is 1.09.00.0108.
Last ROM I tried flashing before giving up in fear of throwing my phone was PACman.

A few weird things... That scare me a bit...
I can put anything on my SD-card from Ubuntu fine through 4ext's USB function, but everything I do doesn't "stick"...
As in... I put a PG861IMG on the root, see it stay on the root in Ubuntu's file manager, but then boot into bootloader and it doesn't register that there is one.
This is just one example, any other files I transfer over don't take either.

I've been using another phone (I think it's an ancient EVO 4G (Not an EVO V 4G))
I us that one to hold the SD card, and things transfer fine on that one, so I don't think it's the SD card.

If anyone can give me a miracle reply that will save my whole life, you have no idea how appreciative I would be.

Thank you in advance to any replies and/or advice and/or suggestions, etc...
 
I'm mobile so I might be a little short but I'll try to hit all the important stuff. :)

After a solid 3 hours of staring at my laptop screen....
I rebooted into the bootloader with that glorious S-OFF overtop.

congrats!

As you might understand... I was very eager to install one of those amazing roms, and downloaded and tried installing the PACman rom for the EVO 3D, admittedly (and regrettably!!) rushing a bit :/

lesson learned, ask questions before stepping into the unknown. ;)
The reason PAC rom wouldn't boot is because it requires a downgraded hboot version.

I have a thread here: http://androidforums.com/cdma-evo-...8902-radios-hboot-firmware-all-downloads.html that has all the hboot versions for evo v and evo 3d. In the first (radio) post, there are instructions for using a PG86IMG.zip and special instructions for switching hboots specifically for this scenario (ICS to jb).


At that point I was frustrated enough, to the point where I ended up trying anything I thought might have the slightest chance of giving me my long-awaited rom.

I don't remember what I did exactly, but I flashed a few more files, actually modified the updater-script in the ROM zip.... :/
And now I'm stuck at that White n' Green HTC boot logo, it does not reboot, just stays on constantly, laughing at my hours of fruitless labor.


Before we worry about having severely messed anything up, let's come back to this part later if needed.

I can boot into the bootloader whenever with a battery pull, go into 4ext with no troubles.

Good! If you can access bootloader and recovery, you're probably going to be able to recover.

I tried using the RUU, but I have taken both OTA updates, and even when I finally did get it to start up and run, it denies me almost instantly...

what specific error is the RUU returning? Because you are S-off, you can run the RUU. Does not matter that you have taken the latest OTA or that the bootloader is locked/unlocked, etc.

What state is your phone in when you attempt to run the RUU? My advice is to put the phone into fastboot USB mode and attempt the RUU again. If that gives you an error, let me know what it is.



A few weird things... That scare me a bit...
I can put anything on my SD-card from Ubuntu fine through 4ext's USB function, but everything I do doesn't "stick"...
As in... I put a PG861IMG on the root, see it stay on the root in Ubuntu's file manager, but then boot into bootloader and it doesn't register that there is one.
This is just one example, any other files I transfer over don't take either.

Not sure if it was a typo, but it should be PG86IMG.zip

Does Ubuntu show file extensions by default? If not, make sure the file isn't actually being called PG86IMG.zip.zip


If anyone can give me a miracle reply that will save my whole life, you have no idea how appreciative I would be.

Thank you in advance to any replies and/or advice and/or suggestions, etc...

Unless something you did caused hardware damage like corrupting a partition so that the RUU can't install, the RUU should recover everything just fine.
 
I've applied the HBOOT 1.50 from the post you linked me to.
I just did the one for Spring users rather than the Juopunut Bear one, as the Sprint one was exactly 1.50 and the other wasn't.
But, instead of returning to HTC logo and staying there, now it just restarts into bootloader again. Even when selecting just a regular reboot, or just pulling the battery and turning it on normally.
 
Because we don't know exactly what you did to the phone you should start with the RUU.

Put the phone into fastboot USB mode and run the RUU.

Then we'll move forward with PAC rom after the phone is in a working state.
 
Back
Top Bottom