Database Users

Hero Boot Loop 1st splash

Well i flashed my g1 to hero rom by JAC
and now its looping at the screen with the little android guy
what did i do wrong
Can someone help me out please
i made another thread but no ones being nice so no tough love please mods

Did you set your SD card up the way its suppose to be?

Repartition/format your SD card
Copy the update to it
Load Recovery
Wipe
Install
Boot

I had that problem the hero rom don't play well with the g1 I reformatted the card and started from scratch with a more stable rom

Figured i would update this with the knowledge i have gained. Erase the EXT2 / 3 partition then wipe. Load the ROM again and reboot. This should let it pass the boot loop. I had the problem this morning with Drizzy's Hero build and now with JAC's I am running tests with.

Krazyone said:
Figured i would update this with the knowledge i have gained. Erase the EXT2 / 3 partition then wipe. Load the ROM again and reboot. This should let it pass the boot loop. I had the problem this morning with Drizzy's Hero build and now with JAC's I am running tests with.
Click to expand...
Click to collapse
Thanks Krazyone, that's fixed my problem. Too bad there is no Thanks button, but here is the manual Thanks for you (+1).

Randomly losing file access

Crappy sd, or phone issue ?
Problem solved on reboot, but annoying all the same.
Currently on mt3g 32b, stock froyo.. but was also doing it on stock donut and biffmod..
8gig sd.. Think its a sandisk.
Sent from my MT3G 32b using XDA App

Chaosmstr said:
Crappy sd, or phone issue ?
Problem solved on reboot, but annoying all the same.
Currently on mt3g 32b, stock froyo.. but was also doing it on stock donut and biffmod..
8gig sd.. Think its a sandisk.
Sent from my MT3G 32b using XDA App
Click to expand...
Click to collapse
So you DEVELOPED something to make this happen?
Or perhaps you are DEVELOPING something to prevent this from happening?
Unless it's either of these your QUESTION would belong in the QUESTIONS and ANSWERS (otherwise known as GENERAL) thread.
Next time your new thead will be removed.

Chaosmstr said:
Crappy sd, or phone issue ?
Problem solved on reboot, but annoying all the same.
Currently on mt3g 32b, stock froyo.. but was also doing it on stock donut and biffmod..
8gig sd.. Think its a sandisk.
Sent from my MT3G 32b using XDA App
Click to expand...
Click to collapse
I was having this same issue on stock donut and donut roms. Also when i tried to use it to flash other roms, it couldnt be mounted. So I used my 4gb to flash CM6 and then formated the 8gb card in CM6 and never had a problem. CM6 ran really slow for me so i flashed Super D. It started to happen again in Super D, but I dealt with it. Stock Froyo came out, i switched to it, formated the 8gb card in Froyo and it hasnt done it since. So I would say its a donut problem. Try formatting it in Froyo or a Froyo based rom

wrong section.. sorry Moderator.
Yes, this is a Question.. and I will try that re-format procedure.
To clarify, I will randomly loose file access on the SD card, and regain it upon reboot.
I had formatted it previously using Amon-Ra's recovery to create the swap, ext and data partitions.

[q] omg need help. Mytouch 4g stuck on mytouch 4g screen.

Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.

thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
calm down take a breather us XDA users got your back, OK take out the battery and put it back in then go to the Hboot ( hold power and volume down) then once you get to the Hboot Settings use volume down to get to RECOVERY (i think its the third one) then once you get into Clockwork Recovery scroll down to (Backup and Restore) click then press (Restore) and then choose your Restore file it usually Year-month-day hope i helped you donate pls if i did
BE SURE TO KEEP THE CHARGER IN!!
p.s. if it turns off while its restoring even with the charger in let it boot into recovery mode and let it charge up a bit
incase you still need help gtalk me [email protected]
and p.s. CWM 3.0.0.5 is for gingerbread only

Certain roms require certain versions of clockworkmod. I don't know if this also applies to restoring from backups, though. Which type of rom did you flash?

If he flashed the add on 3.0.0.5 has ext3/ext4 support. Should be able to flash froyo and TB Rome.
Sent from my HTC Glacier using XDA App

3.0.0.6 supports ext3/ex4 3.0.0.5 only does Gingerbread
Edit: I'm being a dumbass yea what he said was right I'm overly tired and I have to explain to her why I was being a dumbass and trying to flash through fastboot but what I don't understand is why its still stuck at the boot screen

thisisjay said:
Hello,
I need some help. I decided to try out a mod while at work today. i tried it out and didnt like it too much and try to restore my last back up that i did before the change. the phone cut off then back on and was stuck on the mytouch 4g screen and has been this way for about 3 hours.i took the battery out and i went to the hboot screen and tried a factory reset and then the rom manager opened up (v3.0.0.5). from there i went to reboot now and it goes back to the my touch screen. idk what to do and i need help. im new to the droid and am unfamiliar with the terms. can anyone help PLEASE. if possible to gtalk me at j.d.louisy.
Click to expand...
Click to collapse
Three options
Option one: (easiest)
Since you flashed 3.0.0.5 you must flash a Gingerbread ROM, (Which you can download from here ). Make sure to flash the G/apps after you flash the ROM.
Option two:
you can flash a 2.x.x.x Recovery image, or flash 3.0.0.6 via script or manually do it via the HBoot.
Option three:
Flash the PD15IMG and start over from ground one.

thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.

thisisjay said:
thank you so much for the advice and help. i could bang my head on the wall for trying to load gorillasens. i shouldve left it alone. once i get home from work i will give it a try again.
Click to expand...
Click to collapse
Ah. i think i see what happened. You rooted your phone. downloaded Clockwork Rom Manager, then flashed a recovery image (which was version 3.x). then tried to flash a 2.2 ROM.
Okay. so what.....
a common mistake but one that can be avoided by doing a little research.
Clockwork's 3.0.0.5 recovery image is only compatible with Gingerbread (2.3) based ROMs.
Clockwork's 2.x recovery image are only compatible with FroYo (2.2) based ROMs.
gorilla is 2.2 So it's not cannot be flashed by the recovery image you are using.
if that is correct then the text in the recovery image should be orange in color. If that is correct.....If i were in your shoes i'd load CM7 w/ the GAPPS > download CWRM from the markert > scroll to the bottom (all clockwork recoveries) and flash the newest 2.x. then boot into recovery / make sure the text is GREEN, not ORANGE, wipe then flash your GorillaSense.

Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App

danger-rat said:
Can you cite a source, because I've also heard people claim that Clockwork 3 is backwards compatible, but there was no evidence either way...?
How would you go about switching from a 2.2 ROM to a 2.3 ROM? Do you have to backup with CWM 2, then install CWM 3 to install the new ROM? Doesn't make a lot of sense to me...?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
3.0.0.5 is not backwards compatible, which is the official 3.x that you download via the Application. 3.0.0.6 which is "beta" flashed via the HBoot is backwards compatible.
It's seriously jacked if you ask me.
to go from lets say CM6 > CM7 one would do a nandroid backup of CM6, then go to CWRM flash the 3.0.0.5 recovery image > boot into recovery and flash the CM7.
now to get back to a 2.2 ROM you have to scroll to the bottom of CWRM app's and flash a 2.x version of the recovery then do your nandroid restore, flash the 2.2 recovery image.
From what i've heard once 3.0.0.6 is finished you can use that for everything.

What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App

danger-rat said:
What a pain...
I'm real sketchy about the Clockwork 3 recoveries for the Nexus, because they've been screwing up partitions (mine included). Has there been any problems with Clockwork 3 on the Glacier?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I haven't had any problems with mine. The only problem that was noted was the 3.0.0.5 prior to the official release wouldn't do Nandroid Backups directly from the application. Some were reporting it work work from the recovery image, but mine never did.
and i have a feeling the reason it's screwing with Partitions is this (CM7/CW3.x) is a Ext4 set up. And CM6/CW2.x is a Ext3 set up.
but since it went official the only problem i've seen is people flashing the the wrong recovery for the wrong ROM. People are flashing 3.x because 3 is higher than 2 so they think it's an upgrade and have no clue on the who/what/when/wheres and whys of what its for.

The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App

danger-rat said:
The partition thing is different for the Nexus, because they are cross compatible to a certain degree. I rolled back to CWM 2, but I can still flash CM7 no probs...
It's interesting to note the differences between the two platforms though (Nexus vs Glacier).
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Yea between Google's way of doing thing and HTC, but i'm sure the chip-set has something to do with that. and with the sexy nexi only having 512Mb of memory the factor of tricking the phone to use the SD card has something to do with it i'm sure.

i have the 3.x recovery and i can flash iceglacier which is a 2.2 rom with out any issues. what i can't do is restore my backup from my other phone onto this replacement i just got. i made the backup with the 3.x recovery but i just keep getting stuck at the mytouch bootup screen... gonna try flashing the 2.x recovery and see if it lets me do the restore.

hey there everyone. just giving an update.......phone is still messed up. we tried putting gingerbread on and no go....tried flashing to PD15IMG and starting over. no go, it kept saying that "main version older <bad>" the phone wont go past the htc screen. im going on day 3 and no phone. *sigh* open for more advice. should i just buy another phone?

OMG OMG OMG i fixed it.......thank you for this post http://forum.xda-developers.com/showthread.php?t=957457 i re downloaded the PD(insert file name) and it worked. i broke down in tears. thank you guys sooooo much.

I used the .zip file to restore my mytouch, but now it wont go into Hboot.

I got the same problem and is fixed thanx to this link
http://forum.xda-developers.com/showthread.php?t=957457
now I have to root the phone again
Thank you

Thank goodness someone had this problem
I just ran into the same issue. whew good thing xda is here!!! Thanks fellas

[Q] HTC HD2 from android 2.3.6 to 2.3.7 upgrade

Hi there,
I have the NexusHD2-Gingerbread_V3.1a_NAND_(Android-2.3.6) on my HTC HD2 and I downloaded the TyphooN_CM7_v3.6.8-MAGLDR ROM but there was a slight problem, everything went well up until the moment when the phone boot up which it stayed on the android figure for ever, i have waited maybe 20+ minutes for it to load/boot but there was nothing. I re-flash twice but still nothing was happening, also rebooted the phone couple of times but it kept locking at the boot up android figure screen. Do you have any ideas why or any other suggestions? Please if you could help that would be most appreciated.
MAGLDR Ver. 1.13
ClockMod 3.2
Thanks
Chris
email: [email protected]

crosis001 said:
Hi there,
I have the NexusHD2-Gingerbread_V3.1a_NAND_(Android-2.3.6) on my HTC HD2 and I downloaded the TyphooN_CM7_v3.6.8-MAGLDR ROM but there was a slight problem, everything went well up until the moment when the phone boot up which it stayed on the android figure for ever, i have waited maybe 20+ minutes for it to load/boot but there was nothing. I re-flash twice but still nothing was happening, also rebooted the phone couple of times but it kept locking at the boot up android figure screen. Do you have any ideas why or any other suggestions? Please if you could help that would be most appreciated.
MAGLDR Ver. 1.13
ClockMod 3.2
Thanks
Chris
email: [email protected]
Click to expand...
Click to collapse
Which cwm partition size did you use ? system/cahce.
If you used the right knows, that means that you have bad blocks. That can affect a lot of thing. Increasing Misc partition helps.

It is not an upgrade it is a clean installation of the nw rkm. I formatted the old system 2.3.6 and I installed the 2.3.7 ftom scratch on the internal memory of the phone. I haven't touched the sd whatsoever. The proccess was exactly the same as I did with the 2.3.6 version of android. Hmm don't know why is acting like this, please help, thanks
Sent from my Nexus One using XDA App

crosis001 said:
It is not an upgrade it is a clean installation of the nw rkm. I formatted the old system 2.3.6 and I installed the 2.3.7 ftom scratch on the internal memory of the phone. I haven't touched the sd whatsoever. The proccess was exactly the same as I did with the 2.3.6 version of android. Hmm don't know why is acting like this, please help, thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Pm me your teamviewer Id. I will help you.

Right now on the phone i have the 2.3.6, am not going to do the attempt for the phone tongiht, is getting late for this now , as for teamviewer how would you help me? everything takes place on the phone. If you want we can do this on the weeknd at some point. do you have msn or skype so we can arrange the meeting? lol
Thanks for your effort bud

Try redoing the partition as the other poster said. Tytung's NexusHD2 uses a 135MB partition with 2MB of cache. Typhoon's uses a 150MB partition with 5MB of cache. If you didn't change the partition size and are still using the one for Tytung's when going to Typhoon, this is probably the cause of the boot up issue you are seeing.

Ok, you mean to make the partitions on the sd card right? And the rom will install on the sd and not on the phone then? So I have to format the sd?
Sent from my Nexus One using XDA App

evo is messing up

ok my evo has been messing up alot lately. it all started with the front camera like 2 weeks ago the front camera does not work at all and certain roms will not boot. i flashed roms almost every week and always superwiped and everything. i am using Amon RA 3.11 right now i am running MetrogenMod (CM7). Yesterday my phone was in a bootloop that would only boot at the splash screen and reboot over and over again. It became a "usb brick" and it wouldnt detect the sd in recovery but i was able to fix it using adb in fastboot with this guide. flashed the rom all over and now its working except for the ffc. i think some of the files in the internal memory are corrupted but i have not been able to find anything to fix it. i have flashed many roms, RUU, updated radios. i am running out of ideas. Can anyone help me?
my phone:
s-off
revolutionary
Hboot 6.16.1002
radio: 2.15.00.0808
HW: 004
by the way the roms i can run are: Radiance(sense 3.5), Energy (sense3.5) MIUI ICS, CM7.1, CM7.2 rc1, Metrogenmod, stock, 4korners,
this roms only boot up for 3 minutes and then reboot over and over every 3 minutes (yes they boot correctly but as i am trying to set it up it reboots): MIUI GB, rainy day, TN shooter rom for evo 4g

Try doing a fresh install with re formatting your sd card as well. Use Amon Ra to format sd and upgrade to ext 3.
Of course back up what you want on sd, but remember, not all data transfers from one version of android to another well. i.e. app data from gb won't function well on ICS and the opposite too.
Though ultimately, it could be a hardware failure. In which case take out to Sprint and get it replaced... That is about all you can do at that point.
Sent from my PC36100 using xda premium

imheroldman said:
Try doing a fresh install with re formatting your sd card as well. Use Amon Ra to format sd and upgrade to ext 3.
Of course back up what you want on sd, but remember, not all data transfers from one version of android to another well. i.e. app data from gb won't function well on ICS and the opposite too.
Though ultimately, it could be a hardware failure. In which case take out to Sprint and get it replaced... That is about all you can do at that point.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
well i already did that many times, i wipe everything 3 times manually, format the sd card, partitioned it, and all that but it still has that problem. since i dont have sprint (im flashed to metropcs) i will just look for another evo