guys im stuck in boot loop :( tried everything - G1 Q&A, Help & Troubleshooting

guys im stuck in a loop in a hero loop but i tried installing the tmobile rom too and its looping too... it goes to teh g1 screen adn then the next screen where it says android or hero and it continues to loop... ive tried repairing my ext2 ive tried everything and its pissing me off cuz nothing is working ive tried searching and ive done what the searches or what the hero loops have told me to do but nothing is working

clear your davlik-cache, format your ext partition(s) and reflash.

alleyezondisromo said:
guys im stuck in a loop in a hero loop but i tried installing the tmobile rom too and its looping too... it goes to teh g1 screen adn then the next screen where it says android or hero and it continues to loop... ive tried repairing my ext2 ive tried everything and its pissing me off cuz nothing is working ive tried searching and ive done what the searches or what the hero loops have told me to do but nothing is working
Click to expand...
Click to collapse
try wiping ext partition, if it still loops, format sdcard and recreate partitions and try to flash again, make sure you wipe before you reflash!

Try this....in recovery menu...wipe,wipe ext,wipe again,repair ext,wipe again flash,repair ext....reboot!!....make sure that you have the hero.zip on the root of your card if not just use a card reader and put the zip file and do what i just told you....good luck

Related

HERO PROBLEM please HELP!!!

I just finished installing hero
but its looping at the hero Logo with the little android guy
Did i do something wrong or is it just booting up
for the first time???
Its been about 5 minutes now please help me out
ps i didnt repair eternal system files before wipeing/flashing
you think this is why???
If it takes more than 10 you should try rebooting. If it does it again then try wiping and reflashing it
Builds normally take anywhere from 5-10 minutes to boot up the first time. This is due to them setting up some framework before they begin to work.
Now, if you see it flicker and re-animate, that's a boot loop. Watch the animation closer, and if it disappears and then appears again (within a split second), then it's a boot loop. In this case, make sure you have the correct SPL and Radio installed.
well heres what it does
its at the screen after the TMO G1 screen
Now it animates HERO
then the little android guy waves Etc..
then it goes black then rpeats this
Boot Loop
or Wrong SPL/Radio(i dont think so i had 2.22.1.216, and the spl was 1.33.2005
Yup, that's a boot loop. Try wiping/reflashing, and see what you get. Which build of Hero are you using?
iM using JAChero 2.6.3
but ididnt repair the ext sys files b4 wipeing/flashing
as instructed
you think this is why its looping
considering i have right spl/radio
should i
repair
wipe
then flash
watchyaself said:
iM using JAChero 2.6.3
but ididnt repair the ext sys files b4 wipeing/flashing
as instructed
you think this is why its looping
considering i have right spl/radio
should i
repair
wipe
then flash
Click to expand...
Click to collapse
In your other thread you said you were setting up your partitions with Paragon.. Are you sure you got them correct?
FAT32 - Ext2 or 3 - Linux swap ?
If a wipe / flash doesn't fix it, try redoing the partitions.
If you have Cyanogen's recovery, click the "Partition from the phone" link in my sig, it'll show you how to do it all.
Oh yeah.. When you have a new question on this issue (partitioning your card and flashing Hero) just post it as a reply in here, instead of starting new threads and editing your old ones. Makes it hard to follow what you've tried already if you keep changing it up.

g1 turned into black screen after android skatin

ive failed to partition my phones in console, so I reformated sd card and puttin back the cyanogen rom into and wipin and then reflashin the cyanogen, but now it turn into a blackscreen right after android flashin logo screen...is it bricked?
im totaly out of myself right now as I just dont know what to do to get it back to work again...plus just to had to my pain ive accidentaly made a backup. veyr unlucky...I need help cause I dont think ill sleep well tonite.
forken said:
ive failed to partition my phones in console, so I reformated sd card and puttin back the cyanogen rom into and wipin and then reflashin the cyanogen, but now it turn into a blackscreen right after android flashin logo screen...is it bricked?
im totaly out of myself right now as I just dont know what to do to get it back to work again...plus just to had to my pain ive accidentaly made a backup. veyr unlucky...I need help cause I dont think ill sleep well tonite.
Click to expand...
Click to collapse
if you can get into the recovery screen or bootloader it is not bricked and since you said all you got to the android screen you are just bootlooping. try to wipe, run fix file extensions, reflash rom, hopefully that will fix the bootloop. if not try to flash jf1.51 since it does not do an auto apps2sd. at least from there you can sleep knowing your phone is usable then when you have time you can re-partition your sdcard and go back to cyanogen's rom
ive run file extensions and it saids... error checkin filesystems! run e2fsck manualy in console? is that what I should do?
ive run the file extension run the e2fsk in console, wipin, reflashin and it still turned into a black screen when I get to the blue android flashin logo...
now ive remove the sd card from the phone and tried turned it on and when i got to the android screen it , the phone turned off and i think IAM now bricked since I cant turn it back on... wow
if the redlight still appear does that means theres still hope???
okay tried camera and red button and it worked but said battery charge to low so I guess it was just runnin out of battery..ill get back to it once it charged enough.
please someone take time to help me thank you...
anyone have any idea on how to solve this problem???
forken said:
anyone have any idea on how to solve this problem???
Click to expand...
Click to collapse
try to either repartition your sdcard. or flash JF 1.51 because it doesn't require any partitions then you will have a phone while you can partition your card for cyanogen's rom
so if I change teh Sd card you think it will work?
cause Im having an HARD time partitining my sd card it seem like its my stickin point in allthose processing...
you could try

[Solved] SPL issue stuck.....

First off...
G1 PVT 32B
recover img1.4
new radio 2.22.19.26I
intalled hard spl, in recovery img after installing hard spl phone rebooted to recovery then at the bottem said formatting cache:.... stuck there for 15 mins so I tried Alt S to reboot, After that it gets stuck on G1 screen. I can still get back to recovery. should I try to redown load spl, is it possible I got a bad download or did I do some else wrong
maybeoneday said:
First off...
G1 PVT 32B
recover img1.4
new radio 2.22.19.26I
intalled hard spl, in recovery img after installing hard spl phone rebooted to recovery then at the bottem said formatting cache:.... stuck there for 15 mins so I tried Alt S to reboot, After that it gets stuck on G1 screen. I can still get back to recovery. should I try to redown load spl, is it possible I got a bad download or did I do some else wrong
Click to expand...
Click to collapse
first boot into bootloader(camera and home) and see if you have a white screen with 3 skating androids.
if you do then you have the hard spl.
sometimes when you flash a spl it will wipe your phone.
if you do have the hard spl just go ahead and flash whatever rom you want to use.
if you don't have a card reader go into the recovery console and type ums_enable to mount your sdcard and put the rom on your sdcard then type ums_disable to unmount the sdcard, then finally type reboot recovery and when it boots up flash your rom.
That did it David just uploaded CM 4.0.4 and its up and running. You have been alot of help tonight, kick you a little something for your help...
wait , you push alt-s, are you still using the orignal recovery, do yourself a favor and flash cm recovery 1.4, nandroid backup and restore, flash any zip.
maybeoneday said:
That did it David just uploaded CM 4.0.4 and its up and running. You have been alot of help tonight, kick you a little something for your help...
Click to expand...
Click to collapse
thank you very much
Thanks!!
I was having the same issue... ( I have the pimped recovery as well)
The first couple times I tried, I was getting no changes to the spl...
I tried one more time, wiped to be sure, proceeded to install spl
I then made it to same point, "formatting cache..."
I decided to start the reboot process and quickly pressed
"cam + power" when the screen went black and BAM,
got the 3 skateboarding androids
and it says "HSPL 10.95.3000"
I then reinstalled latest Cyan, and partitioned the sdcard with sdparted.txt
8gig Class 6 (100MB Swap, 1024MB ext4, 6893 Fat32)
Rebooted and
Thx!!
I am trying to unroot my friend's G1... I found a tutorial on XDA (link) and it worked fine without any problems on my phone, however when I go into recovery mode (CyanogenMod v1.4+JF) and I hit Alt+S, it starts to install the update.zip and it reboots and starts up in recovery and gets stuck on Formatting CACHE:... I've let it sit for quite a while and still nothing. I can reboot the phone, but it just starts back up in the rooted mod. When I start into the bootloader (camera+power), it's not the three android's on skateboard, it's the colored screen, and it doesn't give me the option to install DREAIMG.nbh file. I'm not quite sure what to do, especially since I had absolutely no problem testing this tutorial on my own phone.
EDIT: I figured out that the bootloader is downgraded and working. Now when I load the bootloader, it goes to the grey screen and says Loading... No image found! I have searched the forums and google for a solution to this program and so far nothing I've found is working. I've reformatted my SD card many times to FAT32, as well as redownloaded the DREAIMG.nbh file... Any help would be great!
EDIT 2: I'm not sure what the problem was or what I did to get it to work, but after formatting over and over and downloading and redownloading, and trying different SD cards, it finally started to work.
Ok. I have done everything that was suggested up above. I also get the 3 android skateboarders and I have tried to install the new
[ROM] CyanogenMod - Keeping You Legal For Less (STABLE) [UPDATED 10/31 - v4.2.3.1]
Which installs just fine. But then I reboot the device and it continues to be stuck on the G1 Splash Screen.
I can verify that I updated the Radio first and confrimed it was updated then updated the SPL and got formatting cache and waited like 15 mins and then now I am stuck.
So I what david1171 suggested and still nothing.
Any suggestions would be nice.
Thanks

problems flashing, stuck in boot loop

Hey peeps, hope somebody out there can help. I have quite a strange problem and have tried everything I know to sort it with no luck.
Ok before I start I just want to say I'm not playing the blame game, it was probably an unhappy coincidence it happened at the time it did.
I was on kingk's 2.0 hero rom, but decided i'd try maxisma's, so I wiped, formatted ext, flashed maxisma 2.0, then 2.0.1 which had just been released as a fix. Rebooted the phone. Everything was going smooth, I got a little flash of the notification bar same as what happens with every hero rom I've tried, then I got FC on messaging, then the phone froze. Thinking nothing of it, reboot, reflash after a wipe, but I repaired ext after wiping it. Flashed 2 and 2.0.1, then rebooted. Phone got to htc logo, then froze for a few seconds before going back to the animated android. Ok, this rom needs more time in the oven I thought.
I then wiped, formatted and repaired and flashed kingk's rom back to my phone, boot loop
I tried mlign, boot loop
I tried xrom, boot loop
I flashed htc image and then cyanogen's rom, finally got booted.
I've spoken with MikeTaylor (he has the patience of a saint, buy him a beer, I did) and he suggested clearing the dev folder, I tried and was prompted with "device or service in use" so that didn't work. I even thought going back to stock would help, but it didn't. I then thought it had something to do with the SPL, cyanogen's being the only rom not needing haykuros, so I flashed "the official donut" which also gave me a boot loop.
So here I am, asking for any suggestions, and I'm willing to try anything.
Many thanks in advance for any help, and I hope when I get fixed, this thread isn't used anymore, we don't want more people with my problem
The only suggestion I can make is recreating the partitions on your card using parted or something like that. I had the same problem as you going from Cyan to xROM, recreated the partitions and it was fine
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
senaia said:
well, not near computer to back things up, but i'l give it a go, it's either that or fastboot erase me thinks
if it works, thanks in advance, if it doesn't then thanks for trying
Click to expand...
Click to collapse
Oh, I assumed that card wouldn't mount so it wouldn't matter if you couldn't back up
So what does fastboot erase do? Wipe out /system?
i was hoping somebody here could tell me that, i've never used fastboot other than changing the splash screen and that was done using a tool, so i didn't actualy use it lol. card mounts, the flash goes through ok, but it just never boots, unless it's cyanogen mod, which i've not used for about 2 months, xrom awesomeness got to me, but i decided to try out a few hero / sense roms while JAC was out of the office, and now i can't go back to it lol
Sorted, being lazy doesn't work. I used amonra recovery to make the partitions initially which worked, then had this problem. Tried using it again and it said it worked but I still couldn't flash. When I checked manually using parted, it showed 3 partitions. Fat32, blank, and swap. Recreated the partitions and I'm now back to full flashing fun. Unfortunate coincidence it happened right after flashing maxisma's 2.0.1

Help lol im in a big mess I cant fix it! D:

Alright so I got a G1 firmware 1.6 also i have no data plan im running everything straight off wifi anyways, i was running KingxKxRom V2.3 (the Hero Sense theme) and I decided to try this new one I found called MLIGN-Hero V3.3 anyways i tried running the theme it loaded succesfully but with ALOT of force closes then i went into recovery and recovered my old theme again (kingxkx) then i went back into recovery and tried running signed-dream-ots 14721 and i accidently didnt run one of the new cm updates since 4.2.14.1 came out and i forgot to select it and rebooted my phone left it loading for 30 mins it was stuck on the loading android screen then i took out my battery and went into recovery but then i noticed it wasnt the normal recovery it showed up blue with a phone and a exclamation point saying E: cant open /cashe/recovery/command... ive tried rerooting my phone wiping/factory reset and clearing my sd cache and nothing i did the DEAMING fastboot and then tried rerooting and installing the cm recovery but my telnet doesnt work every time i hit su its invalid or trying to run it through adb shell too......im in a big mess right now is my phone bricked?....as of now i wiped everything cleared my sd (saved everything to my flash just incase before clearing my sd) and i just fastbooted RC29 through fastboot and now my recovery screen is yellow but still showing the same as the blue recovery......someone save me from pulling my hair out!! thanks!
Krovee67 said:
Alright so I got a G1 firmware 1.6 also i have no data plan im running everything straight off wifi anyways, i was running KingxKxRom V2.3 (the Hero Sense theme) and I decided to try this new one I found called MLIGN-Hero V3.3 anyways i tried running the theme it loaded succesfully but with ALOT of force closes then i went into recovery and recovered my old theme again (kingxkx) then i went back into recovery and tried running signed-dream-ots 14721 and i accidently didnt run one of the new cm updates since 4.2.14.1 came out and i forgot to select it and rebooted my phone left it loading for 30 mins it was stuck on the loading android screen then i took out my battery and went into recovery but then i noticed it wasnt the normal recovery it showed up blue with a phone and a exclamation point saying E: cant open /cashe/recovery/command... ive tried rerooting my phone wiping/factory reset and clearing my sd cache and nothing i did the DEAMING fastboot and then tried rerooting and installing the cm recovery but my telnet doesnt work every time i hit su its invalid or trying to run it through adb shell too......im in a big mess right now is my phone bricked?....as of now i wiped everything cleared my sd (saved everything to my flash just incase before clearing my sd) and i just fastbooted RC29 through fastboot and now my recovery screen is yellow but still showing the same as the blue recovery......someone save me from pulling my hair out!! thanks!
Click to expand...
Click to collapse
those aren't themes, they're roms
Hmmm. Without a data plan, you haven't gotten past the initial setup wizard since the downgrade, have you?
You'll need to bypass that first.
Try the instructions in this post:
http://forum.xda-developers.com/showthread.php?t=452316
You have to get past that setup wizard to be able to unroot using the telnetd hack, IIRC.

Categories

Resources