Hi all.
I have a US T-Mobile G1 and I've jacked it up.
Yesterday I had Froyo for Trout 1.82 working and I tried updating the hboot and radio to 1.33.0013d and 2.22.28.25, respectively. Everything seemed to be working fine until I made an error... I flashed the kernel ezBiffTestKernel20110222-2708_S.zip. Don't ask me why I did this, I couldn't tell you. Since then the phone has boot looped from the G1 splash screen to a black screen, back to the splash screen.
The phone has AmonRA 1.70 and I can still get into it.
At this point I have tried wiping data and both caches from within recovery, using fastboot and the flashable superwipe. After trying each of these methods, I have reflashed F4T, which is always successful but doesn't fix the boot loop. I've also tried flashing on the Cyanogen 6.1.0.DS, which is what the phone was running before F4T.
All the boot loop threads I have found here and elsewhere say that such problems are due to not wiping before a ROM flash and that wiping and reflashing will fix it... I don't know what to do.
Go into HBOOT-mode and have a look at the values presented here.
If you are really on SPL 1.33.0013d and RADIO 2.22.28.25, then you will need a 2708-kernel, otherwise you will have a boot-loop.
If you are not on 2.22.28.25 or 2.22.27.08, then you must not install a 2708-kernel, otherwise you will have a boot-loop ...
HBOOT says that hboot is 1.33.0013d and radio is 2.22.28.25.
So you are saying that I need to flash a 2708 kernel? I guess it can't hurt to try it again since I'm stuck where I am.
I flashed that kernel on again and now it is booting... So why did it give me issues last night?
mr_fosi said:
I flashed that kernel on again and now it is booting... So why did it give me issues last night?
Click to expand...
Click to collapse
Probably you flashed the kernel before flashing the ROM?
Kernels have to be flashed always on top of the ROM, otherwise the kernel contained within the ROM will overwrite the kernel flashed before.
No, I had the ROM on there first. I'm going to chalk it up to one of the "electronics do strange things sometimes" category. Thanks for your help.
Related
So I was running OpenEclair v1.1.1, and since putting eclair on it, I've been unable to flash to any other rom. It goes through the wipe/install process, but when the device reboots I just get the rogers screen forever. I can then go back into recovery and re-flash OpenEclair to get it working again. I just got through all that hassle with rogers and made it out with my data and my root, so I was now attempting to fix this issue, and figured it couldn't hurt to upgrade my radio and try out amon ra's 1.5.2R image.
Unfortunately, I downgraded the SPL to 1.33.0009 right after trying to flash another ROM which didn't work, and performed the downgrade before I put a working ROM back on it (to use flashrec to get to amenra's), so at present I can only get into the SPL. My cyanogen1.4 recovery seems to be gone as I just get the original triangle ! logo (no menu or anything) when trying to start up in recovery mode.
Now what did I do, and how far back do I need to dig through tutorials to get back to a working rooted ROM? I'm not really sure what point I'm actually at, whether I still have root or not, or where to start.
Ninzoku said:
So I was running OpenEclair v1.1.1, and since putting eclair on it, I've been unable to flash to any other rom. It goes through the wipe/install process, but when the device reboots I just get the rogers screen forever. I can then go back into recovery and re-flash OpenEclair to get it working again. I just got through all that hassle with rogers and made it out with my data and my root, so I was now attempting to fix this issue, and figured it couldn't hurt to upgrade my radio and try out amon ra's 1.5.2R image.
Unfortunately, I downgraded the SPL to 1.33.0009 right after trying to flash another ROM which didn't work, and performed the downgrade before I put a working ROM back on it (to use flashrec to get to amenra's), so at present I can only get into the SPL. My cyanogen1.4 recovery seems to be gone as I just get the original triangle ! logo (no menu or anything) when trying to start up in recovery mode.
Now what did I do, and how far back do I need to dig through tutorials to get back to a working rooted ROM? I'm not really sure what point I'm actually at, whether I still have root or not, or where to start.
Click to expand...
Click to collapse
Have you got a fastboot mode you can boot into? At least then you could fastboot boot a (non-peristent) recovery image to let you then restore from a nandroid backup...assuming you have some good backups either on the phone or on a PC that can be copied to the phone.
I should note you haven't said what kind of phone you have (G1 or Magic) or really provided anything resembling a complete set of relevant information about your phone and its current state. So it's hard to help.....even if this was the right forum...and it isn't.
Try formatting or using a new memory card.
I'm using a rogers Dream, I have a 2gb SD card with 32MB linux swap and 500MB ext3
HAD 1.33.2005 SPL, 1.4 cyanogen recovery image.
Now I have 1.33.0090, can't get into recovery.
Trying to boot normally brings me to a rogers screen.
I CAN get into fastboot, can I put cyanogen's recovery back on?
Sorry if this is the wrong forum, where should I have posted?
Also, I don't know what information IS relevant to this, so please bear with my noobness.
Is there a recovery that will let me flash a ROM without changing the SPL back to 2005? Apparently if I can get the phone to boot up I should be able to use flashrec to upgrade the radio and SPL from the point I'm currently at.
Moved as not Android Development.
So I'm not sure what I did but the phone boots now...
Holy sh** it wasn't just me. I have this SAME problem. After flashing eclair and wiping and flashing another ROM it just stays at my splashscreen FOREVER. Even broke my nandroid, so I can't restore. How I fix mine everytime: Flash a rom OVER open eclair boot up... you'll probably get a sht load of force closes and all that but once you ge tto login screen just reboot into recovery and wipe and flash or nandroid restore then it should work.
If you guys are rogers, then you will most likely be ebi1, in which case, dont forget that you must also flash an ebi1 kernal to get past the boot screen.
So the phone booted into the original 1.5, I didnt realize the downgrade of my SPL flashed the ROM too. I put flashrec on and flashed Amen Ra's new recovery image and the rogers radio update, this is what I'm at now.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
Radio-3.22.26.17
Trying to flash to a custom rom again still fails. I've tried cyanogenmod, super D, and openEclair, it doesn't seem to matter. Where can I get an ebi1 kernel to flash?
E: looking at your signature, it seems I've got the right radio, I'll try using that port tool.
That did the trick! I followed the steps in your signature, flashed a rom, then flashed the ebi1 kernel and my phone booted like a dream. Pun intended.
Edit: So I'm back to only being able to run openeclair. Flashing cyanogen and then briancrook's ebi1 kernel still only gives me the rogers screen. I am however able to flash back to openEclair to get access to a working device again.
Edit: openEclair is running like garbage, it keeps completely locking up the device, I haven't even been able to log into my gmail account to get my contacts back.
Okay, I've managed to get the rom running smoothly by wiping everything, flashing the non-ramhack version of openEclair 1.2.2, then flashing the 1.2.2 ebi1 kernel. Unfortunately for some reason when I do get into eclair, I have no phone app, no settings, and no contacts app, even tho the contacts still work if i try to message someone. This is infuriating.
Hi,
I tried flashing the brand new CyanogenMod 5 with Eclair for G1, and I seem to be in "serious" trouble now.
Before flashing:
I had already installed DangerSPL for a few months with no issue
Had the latest radio
Was happily running SuperD1.9.3 with WG Kernel and JIT enabled
Made a Nandroid backup just in case I wished to go back
Wiped Dalvik-cache and Data/Cache to avoid boot loops
All of this with Cyan's Recovery 1.4.
After flashing the ROM and the Gapps, my phone restarted and got stuck on the G1 screen (no boot screen) for, maybe 15 to 30 minutes, which seemed a bit long for me... I finally decided to remove the battery, went back to recovery and made a Nand restore.
But after the restore, rebooting had the same effect : stuck on G1 screen.
I tried flashing several custom roms with no luck (all stuck on G1 screen).
I finally decided to flash the official ADP1.6 ROM from HTC (signed-dream_devphone_userdebug-ota-14721.zip) which installed fine (and updated the radio by the way), and it finally booted on stock Donut.
I tried then to reinstall custom roms but get stuck on G1 screen everytime I try... and flashing Amon_RA's recovery won't work (i keep booting on the stock recovery). But as a workaround, I can use fastboot to boot into Amon_Ra's recovery.
The questions now are :
did I lose root access, thus preventing from installing custom ROMs ?
if so, is it possible to downgrade while being under DangerSPL ? Won't it brick the phone ?
Is there anybody else who had the same problem with upgrading to Cyan's 5 ?
I really need to get custom roms back, stock sucks on G1... but there is no way i can afford bricking my phone.
Thanks for help guys!!
As long you can get to your custom recovery menu, you still have root access.
Keep the Danger SPL, not worth changing it and the Danger SPL has fastboot also.
It takes a while to boot into a newly flashed ROM so just wait 5-15 min.
Do these steps:
1)Do a FULL WIPE of the phone (data, dalvik-cache, ext, battery stats, and rotation ****You won't have some of these options with Cyanogen's recovery. Just wipe what you can****)
2)Repair the ext partition
3)Flash CyanogenMod 5.0.7-DS-Test 1 (this is the g1/mt3g version)
4)Without wiping or rebooting, flash the gapps .zip file
5)Reboot and set up the ROM
6)Flash the latest Amon_RA recovery for your device. Cyanogen uses Amon-RA's recovery now.
1. Upgrade your recovery....cyanogen stopped working on his a while ago, upgrade to Amon_RA's recovery.
2. You only have to wipe data/dalvik, and maybe sd-ext. you do NOT have to wipe battery stats or rotation EVER.
3. Flash CM Rom
4. Flash gapps
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
alou2 said:
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
Click to expand...
Click to collapse
Give us your spl (hboot) and radio. Go into fastboot and type exactly what you see.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
Try upgrading your radio? You shouldn't HAVE to, but it might work.
Are you on Amon_RA's recovery now?
I'll try upgrading radio, but it's weird I can't switch back to other custom donut builds...
I've used Amon-RA's recovery to wipe and install the ROM this time.
For some odd reason though, it seems i can't "install" Amon_RA recovery (it seems to switch back to stock recovery), but just boot it through fastboot...
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
make sure you're flashing the right recovery. dream still has two options. just like mytouch has H or G.
the one with "R" on the end of it is for rogers, one without it is for USA ones.
What files are you flashing? It sounds like you're flashing an old 1.6 base that has a recovery image included. Are you flashing the DRC83 Defanged as a base?
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
Click to expand...
Click to collapse
I run into the same issue, I was upgrading from the latest cm 1.6 and after trying a few different things, after wiping with alt+w, I reinstalled danger-spl then installed the cm update, then the google apps; after doing this, it worked fine. BTW, it took about 15 mins to boot up though.
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
Click to expand...
Click to collapse
There is your problem. DO NOT FLASH THE DRC83 BASE!!!
Just repartition your sdcard (if you want to), upgrade to ext3 or ext4, then follow the last 2 steps.
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
alou2 said:
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
Click to expand...
Click to collapse
I'm not sure if this will make a difference, but flash Gapps first then flash CM5 then reboot and everything should work...
or
You might want to check and make sure your MD5 is correct too..
why would you flash gapps first? you have to flash it on top of cm5.
Yeah... quite sure this won't help.
What could prevent the phone from booting custom firmwares but still allowing to install them ? (and finally I can still run the su command through adb, and get root access, but apps can't get root...)
tehseano said:
why would you flash gapps first? you have to flash it on top of cm5.
Click to expand...
Click to collapse
I rooted my G1 for the first time. I flashed CM 5.0.7 then GApps (no reboot in between). When the phone booted, none of the Google Apps were on the phone. Went back to recovery and did a wipe and flashed GApps then CM (no reboot) and everything installed correctly. Someone said to flash CM first then GApps, but that didn't work for me. Weird.
Hi there. I just got my G1 as a backup phone, and I am having issues with flashing CWM. When I flash it, I choose "HTC Dream", and it flashes successfully. However, when I try to boot into CWM, it will just hang at the G1 splashscreen. I have noticed Amon_RA recovery works fine, but the ROM I want to use (COS-DS) is recommended to be flashed with CWM. I have tried formatting the SD card and reflashing already (many times). I also tried the experimental versions of CWM but they will not flash at all. If it helps, my buddy installed SuperD (a donut ROM) on this G1 before he gave it to me.
My G1 is a 32B PVT device, with the Engineering S-OFF, HBOOT 1.33.2005 (DREA10000), Radio 2.22.23.02, and CPLD-4.
NikolaiT said:
Hi there. I just got my G1 as a backup phone, and I am having issues with flashing CWM. When I flash it, I choose "HTC Dream", and it flashes successfully. However, when I try to boot into CWM, it will just hang at the G1 splashscreen. I have noticed Amon_RA recovery works fine, but the ROM I want to use (COS-DS) is recommended to be flashed with CWM. I have tried formatting the SD card and reflashing already (many times). I also tried the experimental versions of CWM but they will not flash at all. If it helps, my buddy installed SuperD (a donut ROM) on this G1 before he gave it to me.
My G1 is a 32B PVT device, with the Engineering S-OFF, HBOOT 1.33.2005 (DREA10000), Radio 2.22.23.02, and CPLD-4.
Click to expand...
Click to collapse
From my experience with ROM Manager/ClockworkMod. The recovery do not work well. I recommended that you stay away from it.
Amon RA works fine without CWM.
I had the same problem when I first started flashing ROM. My big mistake was to start using it. Took me about a few months to realize that it does not work well and it will hang at the G1 screen.
Now I see that they still have not fix this problem. LOL!
BeenAndroidized said:
From my experience with ROM Manager/ClockworkMod. The recovery do not work well. I recommended that you stay away from it.
Amon RA works fine without CWM.
I had the same problem when I first started flashing ROM. My big mistake was to start using it. Took me about a few months to realize that it does not work well and it will hang at the G1 screen.
Now I see that they still have not fix this problem. LOL!
Click to expand...
Click to collapse
I agree!! 100% CWM doesnt work as well as RA and personally that COS-DS rom isn't that great... froyobylazslo is way better!!! but if you really want cwm that just downlaod "rom manager" from the market and apply/flash cwm through there... very simple
ldrifta said:
I agree!! 100% CWM doesnt work as well as RA and personally that COS-DS rom isn't that great... froyobylazslo is way better!!! but if you really want cwm that just downlaod "rom manager" from the market and apply/flash cwm through there... very simple
Click to expand...
Click to collapse
That is how I flashed CWM...
NikolaiT said:
That is how I flashed CWM...
Click to expand...
Click to collapse
If you already installed Amon RA, then I would recommend uninstalling CWM. Then you should be able to get into the Recovery Mode.
If you have not, I suggested that you do. Then uninstall the CWM.
It is not that hard to boot into Amon RA recovery and do what you need to do. I found out that it is easier than trying to use ROM Manager/CWM.
Also, you might want to try different ROM (IE: froyobylazslo, gengerbread yoshi, or even SuperAosp) if you are so incline to use CWM.
Following this thread: http://forum.xda-developers.com/showthread.php?t=1098899
I was able to do everything except install the hboot0013d.zip; it kept on comping up saying to many firmware found & wasn't able to store hboot.
if I go to fast boot right now my phone says
dream pvt 32b eng s-off
hboot- 1.33.2005
radio 2.22.27.08
I tried installing cyanogenmagpie but that wont work; the phone is stuck in a loop where the t-mobile g1 logo comes up for about 2 minutes then it resets; Idk what to do
any help will be greatly appreciated...
did you wipe the device? try flashing ohsaka superwipe than flash the hboot file..
following ldrifta's advice, I was able flash the hboot file and flash the cm7 magpie rom. It took for a while but it booted. Now the problem is that the rom wont let the phone part of the phone work. I keep on getting a force close about the phone & messaging once i boot it. I'm sorry for all the problems guys, any help would be appreciated again
that sounds like its the rom... try another rom lol if you still have the same issue than your sim card may be messed up, happened to me before. just out of nowhere it stopped working..
ps. make sure you wipe system, data, cache and sd-ext each time before flashing roms...
lol what rom would you suggest?
uhhhmmmm depends what you like... froyo, sense, gingerbread.. lol list goes on and on... but uhh
1. froyo by lazslo
2. EzGingerbread
3. SenseLX
4. FroSense
5. Magic sense
6. COS GB
7. AOSP 2.2
i think froyobylazslo is the only rom you need to flash a 2708 kernel with... but it worth it
Hello again. Like in subject.
Issue happened when i tried to flash Liberty 5.1 ROM. Well i did not read all requirements ;/ - but i do have a nandroid backup that works like a charm (and i don't know why?)
specially about Radio: 2708+ and SPL: 1.33.0013d.
So i flashed it on Radio 26.91i and Hayakuro's SPL.
Than i read other requirements
3) Flash recovery-patch.zip.
So Dream was stuck in G1 logo. After super wipe i deciced to make 3) Flash recovery-patch.zip.. So i did. Still stuck on G1 logo. So i used this CMTD removing zip and i deciced to flash Radio: 2708+ and SPL: 1.33.0013d.. SO i did. Still nothing. i cannot flash any rom. Even DRC83_base_defanged gives a G1 stuck. Even logcat is't ready at the moment, and i cannot reboot it via SEND+Menu+END... battery removing, restoring nandroid, and on the road again.
Well i am stuck right now in 1.6 SuperD with RamHack, Radio: 2708+ and SPL: 1.33.0013d., 128 SWAP, 512 EXT which is superior fast, but i'd like to test other roms from time to time, and i am wondering why the device is being blocked on other roms. MTD should be restored, and even if i flash other rom on my nandroid backup (i remamber it should normally give bootloop) i am stuck with G1 logo.
If anyone could help me with this issue it would be super. I flashed many things to my G1 over the years (and this is third G1 ) but i have never been is situation when logcat shows -waiting for device-...
PS: i never got LIBERTY rom working :/
I have installed BananaBread 4.0 by Banana4444 and i think it's working. Logcat talks to me like crazy, Bootanimation breaks the glass. I wonder why...
Well i can see desktop
After a while playing with dekstop i will try to install something else and check if it will work.
Sometimes the remove.zip doesn't seem to work, I noticed that sometimes it needs to be flashed twice to get it to stick. You can always flash amonra again just to make sure.
Does adb work when you are using super d right now? If not then you probably have a driver issue. If it does then make a nandroid (sounds like you did) wipe all, supperwipe, fastboot -w, grab a known stable Rom (maybe ezgingerbread or froyobylaszlo) and flash that in recovery along with any gapps/kernel/etc. (Froyobylaszlo has gapps and kernel packaged with the Rom so try this one as nothing else needs to be flashed)
Sent from my Desire Z using xda premium
Sometimes the remove.zip doesn't seem to work, I noticed that sometimes it needs to be flashed twice to get it to stick. You can always flash amonra again just to make sure.
-Well i tried to flash it once, and after i sent AmonRA via fastboot. just to be sure its clean. It gave me no effect.
Does adb work when you are using super d right now? If not then you probably have a driver issue. If it does then make a nandroid (sounds like you did) wipe all, supperwipe, fastboot -w, grab a known stable Rom (maybe ezgingerbread or froyobylaszlo) and flash that in recovery along with any gapps/kernel/etc. (Froyobylaszlo has gapps and kernel packaged with the Rom so try this one as nothing else needs to be flashed)
- i tried to flash Defanged, superD, super E, superF, CM5,6,7,9,10, FroyoByLaszlo, Liberty, CronMod, Superfast and chromatic - every gave same effect. I have nandroid via recobery, and logcat works every time. just new flashed roms are stuck before logcat can be run from /system.
In the evening i will try Laszlos rom and i will post results here.
Dude. Are we the last G1 forum readers?
_________________________________
EDIT:
Now everything works... so just need to be on newest updates.