I really need help! Ok so here's the deal: I flashed the new RA-dream v1.3.2 recovery this morning and coming from MLIGN 3.0 Hero I wiped EVERYTHING the recovery allowed me to: data + cache, Dalvik-cache, battery stats? and rotate settings along with repartitioning my sd card. After that I wanted to go back to Cyanogen's 4.2.3.1 so I wiped but it now won't go past the Tmobile G1 Screen! I've tried everything, including flashing other Rom's wiping partitioning again, letting it stay at the screen for and hour! all in all I can't get past it, but I can get to recovery.. did I do something wrong? any help would be great cause till then, I'm phoneless
when you do an adb logcat, are you seeing a restart loop?
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.
Okay so im sure the answers for this are here in this forum, but this forum is huge and Ive been working on this for 2 days now. Just got a G1. Want to put ANY rom on it at this point. Ive tried following the "[GUIDE] STOCK-2-CYANOGEN" sticky in the development forum several times, to a T, and cant seem to even get past the 3rd step.
Ive started this over and over again - here's my process. Put DREAMIMG.nbh on my newly formatted FAT32 2GB SDcard. Reboot, get into bootloader, flash the phone with the update. Phone restarts, I enter my google info in, Im on the phone. I place cm-recovery-1.4.img on the sdcard root (ive tried two others and they have the same outcome) Now I root, which took awhile to work in the first place.. enter enter, telnetd, enter, go to market and download telnet. connect localhost. I type this:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery cm-recovery-1.4.img
cat cm-recovery-1.4.img > /system/recovery.img
....everythings gravy, no errors thrown, etc. I put the Hard SPL update.zip on the root of the sdcard, i shut phone off. Attempt to go to bootloader, it stalls on the G1 splash screen, and Ive waited up to 30 mins, before i ultimately have to remove the battery. I cannot load into, or add a new recovery console so I can even continue attempting to flash ANY rom. SO, I start from scratch...over, and over again. Unroot the phone, reload original bootloader, and they work. 2 days in circles!
Now I normally can figure these types of things out, especially with research that this forum has plenty of, but im at my wits end. WTH am i doing wrong I cant follow these guides any better than word for word! Man Ill PAY someone to just get a rom loaded for me at this point heh
wow that guide is old use this one
http://wiki.cyanogenmod.com/index.php/Main_Page#Upgrading_from_Vanilla:_Installing_your_first_mod
okay this is where Im getting hung up on. I did all of that, and once I turn off my phone to install the actual OS, this part "Flash Android1.6 & CyanogenMod latest", i hold home and press power, then the Tmobile G1 splash appears and just hangs... Never proceeds to the recovery option or anything for that matter, without taking out the battery. It doesnt do this when I have it stock, just after i flash cm-recovery-1.4.img
I've no idea if you'll get different results, but you could try flashing Amon_RA's recovery instead of cyanogen's. Just change cm-recovery-1.4.img to recovery-RA-dream-v1.6.2.img (or whichever version you choose).
http://forum.xda-developers.com/showthread.php?t=566669
Okay so I just used Amon_Ra's, followed the instructions and flashed it via terminal, with no errors, just the same as cm_recovery reacts. Shut off fone, and tried home+power. Its frozen on the G1 splash............... How is it if I actually just revert it back to unrooted stock, the recovery console works fine..but any of the updated ones I need to use to get a ROM just will NOT work..?? Please help, im seriously going on like 17 hours with this thing...I genuinly will pay someone if we get this figured out! So very desperate!
hmm strange.
in terminal type
su <enter>
reboot recovery <enter>
Or from command prompt if you have adb setup
adb reboot recovery <enter>
see if that gets you into recovery correctly.
I apologize, I forgot to mention I had done that also, shortly after my last post.. Its not like im not doin the research here hehe. I did the $su, then reboot recovery. it rebooted, and froze at the same splash. I dont have adb, nor know what it is. This shouldnt be this complicated i wouldnt think. Do u think its something wrong with my phone that I cant simply load an alterate recovery image? I mean, it DID work before I had to continually set this thing back to stock..
just fyi, bc ive seen other ppl have this problem..i resolved the issue by reloading dmd64 firmware, then starting over again. I also used recovery-RA-dream-v1.5.2 instead of recovery-RA-dream-v1.6.2 or cm_recovery. Not sure if this made a difference in addition to updating to dmd64, but i was finally able to boot in to recovery and flash the images
I've got the exact same problem !!!
I've installed and used custom ROMs for over a year now, and last week I tried to upgrade to CM5 and since then, I haven't been able to use any other custom ROM, only the official HTC ADP1.6 stock ROM (which sucks...).
Each time I install one, it freezes on the G1 screen and nothing happens (even restoring my pre-CM5 nand backup does the same, it freezes on G1 screen )
Haven't had time to try yet (and honestly, I'm a bit tired of reflashing my phone, I need it sometimes and those things take a lot of time...), but I'm going to try switching back from Amon Ra's latest to Cyan's 1.4 recovery, reflash adp1.6 and a superD right after it, without rebooting to see if it works.
I'll let you know if it works (and then wait for official Froyo, if it ever comes out for the G1, with its official Apps2SD...)
Just rooted my droid with this:
forum.xda-developers.com/showthread.php?t=764470
All of that went fine and I went to install my first ROM. The phone went to restart as I assumed it should and it has been on the red eye/droid screen for the past half hour+ now. Assume I know nothing, how can I fix this?
Assuming you have a custom recovery flashed (I hope you do) reboot into it and wipe data and cache. It should then reboot just fine into your new ROM. Worked twice before for me.
SandmanGTP said:
Just rooted my droid with this:
forum.xda-developers.com/showthread.php?t=764470
All of that went fine and I went to install my first ROM. The phone went to restart as I assumed it should and it has been on the red eye/droid screen for the past half hour+ now. Assume I know nothing, how can I fix this?
Click to expand...
Click to collapse
I'll be adding "whipe data/clear cache" to the instruction set of that post.
Trying to give the mother in law my old N6. It was rooted / bootloader unlocked. First attempt was to factory reset from within the OS. That worked fine, until I rebooted... it wouldn't boot.
I then downloaded the Shamu factory images from Google's website (shamu-n6f27m-factory-bf5cce08) and ran the flash-all.bat script. Multiple errors showed up during the script... but I chalked it up to ADB looking for boot slots etc, whereas this one has none.
Phone booted fine. Installed apps, set up the phone, power cycled it and promptly entered a bootloop.
Ran flash.all again, phone booted fine. Flashed TWRP, booted into recovery, checked things out in there (didn't do anything but flash the TWRP) tried to reboot, phone bootloops.
Flashed TWRP, booted into Recovery, tried to erase system, etc.... multiple errors again. Booted into bootloader, ran Flash-all... phone boots. Installed some apps, rebooted phone and bootloop again.
Then I did something REALLY stupid, I locked the bootloader from ADB. Now I'm on the bootloader, but can't OEM unlock because it's asking me to boot into the OS and enable the ability from Developer options.
I've no idea why this phone is doing this - booting fine into the OS once and then getting into a bootloop every time thereafter.
If anyone can shed some light on this, I'd appreciate it. Also, how in the hell do I unlock the bootloader now that I've locked it and I can't boot into the OS or run the Flash-all.bat anymore since it's locked?
Is your recovery stock? If it is, sideload the last OTA from Google and that should get you back into Android so you can toggle the OEM Unlock button.
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
usafle said:
Thanks. I was getting the "no command" on Stock recovery. Finally fixed this freaking issue after multiple flashes and wipes and everything else I could think of. Finally got it sorted.
Click to expand...
Click to collapse
So did you finally figure out what it could have been that you were doing wrong?
Strephon Alkhalikoi said:
So did you finally figure out what it could have been that you were doing wrong?
Click to expand...
Click to collapse
No. I could only assume I had messed something up when I was using it back in the day and really hosed something up. System wouldn't wipe, cache wouldn't wipe, userdata wouldn't wipe in "fasboot" just kept getting "unable to find XXXX".
So multiple flashes into TWRP and bootloops trying to really REALLY wipe the device finally fixed it. I just kept erasing / wiping every partition I could find in Stock Recovery, TWRP, and with fastboot commands. Finally I got them all wiped/cleared and was able to flash the stock OS back on and have it 'stick'.