• 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

I think you should do a few things before running ruu

First
Make sure there are no pg86img on the root of your SD.

Next flash the jbear 1.50 hboot

Then remove that pg86img

Wipe everything except SD in recovery

Reboot recovery

Wipe everything except SD again

Now flash pacman

Flash gapps

Reboot
 
I went ahead and tried what you had suggested adamhos, step for step...
But it looks like it didn't work, I couldn't get out of the bootloader.

I've run the RUU Brian, returned to stock... And my phone boots up! xD
I was beginning to think I would never hear the annoying virgin mobile boot logo again. xD

Now... Am I safe to re-root, and re-unlock bootloader, and... reflash recovery, and try again?
 
Yep, you're safe to try again. You don't really need to do the bootloader unlock because you're S-off.

Here is a bootloader flashable version of 4ext recovery: https://db.tt/9VEkAHRe

Just needs to be renamed to PG86IMG.zip

Then go back to my bootloader thread and download the jb_1.50.5050 hboot.

Follow these instructions (read through them first to understand how to change hboot without getting caught in a bootloop so you can flash PAC rom):
How to use a PG86IMG.zip file!
First let me start by stressing something important! Verify the integrity of the download by checking the file against its md5 checksum that I provided for each file. You can use a free software such as MD5 Checker to do the job. Or if you'd like to check on your phone without a pc, download MD5 Checker for android from the play store. If for whatever reason your download gets corrupted, using a corrupted file can brick your phone! So use an md5 checker to verify the integrity of the file, it's quick and easy and can keep your phone safe!

1. Download File. Check md5 for a match ;)

2. Place the file on the root of your sd card (not in any folders).

3. Rename the file to PG86IMG.zip

4. Reboot into bootloader.

5. When asked to update, say yes by hitting volume up.

6. When it's all finished, hit power button to reboot.

7. *Important! After booting up, immediately rename or delete the file.

*The presence of the file on your sd card will prevent you from entering recovery in an emergency situation. It's nothing to panic about, but if you get caught in a bootloop, you will have to manually remove the file using a pc and card reader or another phone. That said, to avoid bootloops and being stuck with no way to boot up and no way to enter recovery, plan ahead. If you are on a rom that requires hboot 1.58 and you flash hboot 1.5, you will hit a bootloop and not be able to access recovery. You would then need to remove the file or flash a compatible rom through fastboot connected to a pc.

Okay. Now with instructions and warnings out of the way, I will give you my personal preference on how to flash a different hboot that will be incompatible with your current rom without getting a bootloop and having to use a pc to fix the situation.

Follow steps 1-3 above. Stop! Now, instead of rebooting into the bootloader, we are going to bypass the bootloader by rebooting directly into recovery. Some roms have this feature built in. I recommend downloading something like ROM TOOLBOX from the play store. It's a great app to have if you are rooted. Rom Toolbox has a built in rebooter menu (with widgets) that allows this function. Alternatively go get QUICK BOOT from the play store. So once in recovery, wipe and flash the rom normally. Once finished, continue to steps 4-7.

This will allow you to do everything completely from your phone and avoid getting stuck. Remember, this is just for when you are changing hboots that will be incompatible with the rom you are already using (ie: ICS to GB). Just following steps 1-7 normally is fine for just flashing radios or switching between different GB hboots etc.

Let me know if you have any questions about it before starting. Changing hboots is serious and should be done as little as possible and with care taken. Don't skip on the md5 check. A bad download could cause possible permanent brick.

And make sure to delete PG86IMG.zip files from the SD card when done using them.
 
Thank you. Very much xD

It might be hard to believe after all of this, but I usually am very careful about what I do to my device, since I use it for everything and don't have a quick backup plan in case it breaks...
So I tend to freak out a bit when it does xD

I really do appreciate the help. By far the biggest reason why I feel okay flashing my bootloader, or getting custom ROM's or even rooting at all is because of the support you all offer here.

I'll be sure to post any questions if (and when) I have them.

MANY thanks! xD
-----------------------------------------edit

As a side note (or two)...
I figured out the reasons for RUU not working the first time, and also for the file changes not "sticking".
I had had the wrong RUU before, (So I guess it's a very good thing it didn't work anyway xD)
And as for the files; Ubuntu wasn't done writing to the drive before I disconnected the drive.
I just wish it would have told me that was why...

Oh well xD

Thank you!
 
Back
Top Bottom