hey guys
i upgdated my google maps app today and during the process my phone froze up and when u used adb logcat it had shown that my phone was in a loop with something like "system/lib/libdvm.so" and stays in that loop forever. ive tried restoring it using nandriod and it doesnt do anything, the last restore i had was before i flashed which was pre cyanogen 4.1.99 and it doesnt do anything when i restore it now that i was on cyanogen 4.2.12.2.
i can still get into recovery and ive tried reflashing cyanogen 4.2.12.2 via this method:
http://wiki.cyanogenmod.com/index.php/Upgrading_From_Older_CyanogenMod_or_other_rooted_ROMs
and it still just hangs at the libdbm.so loop anything i can do to unbrick the phone?
ive tried to restore it, nothing happens and it just hangs at the rogers logo adb logcat just "waiting for device".
thanks ahead of time!
nvm figured it out...was one scary experience haha..
Related
I have a black rooted g1. Ive flashed it a couple of times everyrthin was good untill i flashed the 1.6 donut. When i did that i got a black/blank screen . So i did the recovery and then all i got was the start up ( u know were it shows how to use ur g1) so i try logging into my account and then i just got fore close after fore close and my phone wont respond to anything . All i can do is go to the boot loader. Ive tried flashin cm rom and samething goes. what did i do wrong what can i do to fix this? Helpppp! Inees my g1 and i dont have insurance. Im just happy that it is not bricked!
you might have lost root happened to a few people when they flashed the htc recovery. just boot into recovery wipe and reflash the rom is all else fails wipe ur partition
hi,
I have a G1 that I got with unrooted 1.6
I followed instructions at http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod to get CM 4.2 on the phone, that worked without any problems
I then installed DangerSPL and followed instructions at http://forum.xda-developers.com/showthread.php?t=672992 to get CM 5.0.7 installed, and that also worked.
When I installed ROM Manager to partition SD card for apps2sd, the phone would not boot any more, it kept getting stuck at the G1 / T-mobile screen
I then entered fastboot and reinstalled RC7 (DREAIMG.nbh)... that booted without a problem... I then re-flashed cm-recovery-1.4, went into recovery and installed cm 5.0.7 and gapps... I'm not sure but I may have skipped radio and danger this time around
since then the phone won't boot or enter recovery or enter fastboot... any attempts to boot into any of those results in the phone getting permanently stuck on the G1 / T-mobile screen
I'm out of ideas here, so any help would be greately appreciated.
thanks,
allixsenos
allixsenos said:
hi,
I have a G1 that I got with unrooted 1.6
I followed instructions at http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod to get CM 4.2 on the phone, that worked without any problems
I then installed DangerSPL and followed instructions at http://forum.xda-developers.com/showthread.php?t=672992 to get CM 5.0.7 installed, and that also worked.
When I installed ROM Manager to partition SD card for apps2sd, the phone would not boot any more, it kept getting stuck at the G1 / T-mobile screen
I then entered fastboot and reinstalled RC7 (DREAIMG.nbh)... that booted without a problem... I then re-flashed cm-recovery-1.4, went into recovery and installed cm 5.0.7 and gapps... I'm not sure but I may have skipped radio and danger this time around
since then the phone won't boot or enter recovery or enter fastboot... any attempts to boot into any of those results in the phone getting permanently stuck on the G1 / T-mobile screen
I'm out of ideas here, so any help would be greately appreciated.
thanks,
allixsenos
Click to expand...
Click to collapse
Why would you unroot just because a ROM wouldn't get past the G1 screen. Too bad you didn't post about that instead of completely unrooting and trying again.
Oh, you probably didn't miss danger spl the second time around and forgot to flash radio and now you're soft bricked. Sorry, there's nothing we can do.
Hey Guys,
I have a G1 running the Cyanogen 6.0. It was working fine last nigh before i went to bed. Got up this morning and went to make a call and i got this error message:
the process com.android.phone has stopped unexpectedly. please try again
So i rebooted figuring i hadn't done it in a while and that would do the trick. Phone reboots and still had the error and it wouldnt go away. So i decided id just reflash, went to reboot into recovery and now its just stuck on the Tmobile G1 screen. Cant get into recovery no matter what i try, and now i cant even get back in period.
Any thoughts here? Is it finally bricked?
Specifics please.
RC1 or RC2? What recovery, etc.? Can you fastboot? Can you boot into safe mode? etc...
RC2, Amon Ra. I can fastboot but its not loading the Dream.img.
and no i cannot reboot into safe mode.
Think i got it figured out.
If your file is named "Dream.img" then that is a HUGE problem... Should be "Dreaimg.nbh"
I have attempted to flash two different themes now to my wilfire but everytime I reboot after flashing it gets stuck on the boot animation until I get bored, remove the battery and restore my nandroid backup. I'm running Cyanogenmod 6.1 stable on my wildfire and both themes have been confirmed as compatible. Any thoghts on why this is happening?
after getting stuck on boot animation and pulling the battery, dont nandroid backup....try simply rebooting the phone again and see if it gets past it......same kinda thing happened to me recently and that worked
Thanks for the reply but still gets stuck on boot anim.
All,
I had rooted a Captivate recently for a friend and installed CM7. After about a week, my friend decided to go back to stock. Prior to rooting, I made a backup of his stock rom just in case. I then showed him how to restore via Clockwork if need be. Tonight he came in to work and wanted to restore to stock, now he is stuck with a boot-looping Captivate. Now the phone sits at the AT&T World Phone splash screen. I've tried and tried all night to get the phone in DL mode so that I can use the One-Click ODIN restore but to no avail. I can't seem to get the phone in DL mode no matter what I try. Whenever I attempt, the phone simply reboots to the AT&T splash. Please assist if available.
P.S. When I plug the phone into any USB I get a circle (reminiscent of the Android loading spinner) in the center of the screen.
Assistance is greatly appreciated.
Thanks.
- E.
thats not how clockwork backups work...those are to restore your set up to the way you had it once you flash the rom it was backed up from thats why hes looping. you would odin back to stock THEN restore and it would be like he never flashed anything at all.
build/buy a jig that'll for sure get you int download mode.
Loop
I'm getting that same loop screen. What I did was use odin to restore my captivate back to factory because the 2.2 update wouldn't allow me superuser permission. After it was back to factory I rooted with super one click. It was successful but when i went to reboot the att world screen looped.
Help please
superoneclick works fine on 2.2.........you had no reason to go back to 2.1