Answer : bootloop problems after loading a new ROM

mjneid

Well-known member
Oct 26, 2010
98
11
0
I took this from MY post on XDA and thought it'd help here as well.

What you did .. .. ..

Okay so you've rooted your newly bought MyTouch4G, and you've made sure that s=off and you've flashed Clockwork ROM manager's recovery image that you got from the market. That is all the correct order. But when you flashed a ROM you got stuck in a bootloop.


Am i screwed???

Don't worry you are just in a "soft brick mode", or "limp mode" if you will.

What happened? Why is it doing this?
The Image that you downloaded and installed 3.0.0.5 is for 2.3 (Gingerbread) based ROMs only. [n3rd note] these are ext4 style ROMS. They act and store information differently than 2.2 which are Ext3 ROMs[/n3rd note].

This could also be caused by trying to flash a 2.3 using a older 2.x.x.x version of the Recovery Image. Those will only support the Ext3 style ROMs, which are FroYo (2.2) based ROM.

Okay what do i need to do to fix it


If you are using the 3.0.0.5 Recovery image
To fix your problem you need to flash any 2.3 based ROM, for time sake i will recommend Cyanogen(mod). Link to Cyanogen(mod)'s CM7RC2. While you are there you need to also store the G/Apps.



If you are using the 2.x.x.x Recovery Image
To fix your problem you need to flash any 2.2 based ROM, for time sake i will recommend RoyalGinger Thread can be found here


- Question: How do i find out what Recovery image i am using
- Answer: Boot the phone into the recovery mode. We'll touch on that in a little bit

Now when you download both of those files you also need to store them to SDCard.
NOTE: If you are using 2.x.x.x and going to flash RoyalGinger you will not need the g/apps. They have included this in their ROM, and MAKE sure to follow their specific directions for installing the ROM.



- Question: Now how in the world i am going to do that since my phone is in bootloop.

Answer:
Two ways one can do that
1) use a SDcard reader and just plug the card into a main USB port.
2) Mount the SDCard in the phone via the Recovery Image. *** i'd recommend this method since you are going to need to be in recovery anyway ***

Pull the battery from the phone an put it back in, then put the back on the phone. turn the phone on holding the power button along with the volume down rocker button. That will boot the phone into the HBoot (Engineering) Screen. From there you will see an option that says "recovery" [this is what i mentioned earlier, about the different versions] use the volume rocker to select it, then tap the power button to select it. The phone will reboot into what is called the recovery image. From there you will select "mount" then USB. That will mount the SDCard to the Computer.


If you are using the 3.0.0.5 Recovery image
Once you have move Cyanogen(mod) and the g/apps to the SD card unmount the SDCard.

Then navigate to "wipe data/factory reset" you will want to wipe the phone. That will format everything to a fashion that can be written over w/o problems.

Then navigate to "install .zip from sdcard" > " choose .zip " > then flash the main Cyanogen(mod) ROM. Then do the same but flash the g/apps that you downloaded.

Once those are done you can re-boot the phone. That will boot you into cyanogen.

If you are using the 2.x.x.x Recovery image
Please use the link i supplied above to get that ROM up and running once it is done, according to their instructions come back here.

Now i understand that may or may not want Cyanogen nor RoyalGinger on your phone. Well take care of that


What can i do to prevent this from Happening again?

Once you are up and running (make sure to log into your Google Account) go to the market and download Clockwork ROM manager again, and re-flash the recovery image.

Once you are done with that i HIGHLY suggest upgrading to the newest 3.0.0.6 Recovery image. You can do that one of two ways.


one way is to flash True_Blues method for installing 3.0.0.6 recovery image. Use this thread..

The second way is download the 3.0.0.6 recovery image, which i've attached and flash it via the ADB commands. If you need help with that, if you are using Windows or Mac, see my signature for True_Blue's method on EZ ADB. If you are using Unbutu 10.10 use this This Method to get ADB running. This is the method i used to ADB running on my Linux NetBook.
Download the file that i've attached and store just the recovery image from the .zip to the SDCard, from the ADB commands type

More information on this process can be found here


That will flash the newest recovery image to your phone

Once you have installed the 3.0.0.6 ROM Manager you can wipe and flash ANY MyTouch4G ROM that you want. It will handle both 2.2 (ext3) and 2.3 (ext4) ROM formats.

Please feel free to use this in your signature or link people back to. If you feel i made an error in this post please PM and i'll edit it accordingly.

If this thread has helped you solve your problem please hit the "thanks" button.

Here is the recovery 3.0.0.6
http://db.tt/f8FGA1e

Sent from my HTC Glacier using Tapatalk
 
Thank you for this!!!

I had done all the rooting-engineer boot loading etc... just installed rom manager, performed a backup, and then when i wanted to just restore my backup as a test, BAM stuck at the white tmobile mytouch 4g boot screen with no progress.

I just have to upgrade now to 3.0.0.6 ROM so I can restore my original backups. But if I like CyanogenMod V7.0.0-RC2 (and i think i will...), I may never need those backups.

Thank you! I knew I did everything right, but was worried a for a bit. :)

mjneid to my rescue for sure!
 
and what if you can't access recovery but can get into HBoot and download mode?

IF you can get into hBoot and have the engineering hBoot you could/can always flash the recovery via that image. or you can download and fastboot flash the PD15IMG and start over at ground zero.
 

Forum statistics

Threads
955,593
Messages
6,965,340
Members
3,163,338
Latest member
molitco2