Hello guys, this is my situation.
I had a G1 whit android 1.1, these are the steps I did:
1) I install the new radio (latest version) (before, assured me that the phone in the booted mode say PVT)
2) I install the SPL haykuro's 1.33.2005
3) The phone is stuck on the T-Mobile G1 Screen, I remove the batery, put on again and update the CyanogenMod 3.6 rom.
4) The phone is stuck on the tmobile g1 screen again! ... I removed the battery, turn on the phone and stay stuck again.
5) I can enter in the booted mode and recovery mode but I do not know what to do.
which is what I do now?
Thanks for responding
pd:Sorry for the spelling, I do not speak English.
did u wipe before installing the rom?
pkrattu said:
did u wipe before installing the rom?
Click to expand...
Click to collapse
you are talking about a Hard Reset (alt+w) ? yes, I do it before and after, but the situation remains the same.
use power + camera and reflash dreaimg. your phone is only soft bricked so you can fix this. then after you reflash dreaimg regain root access and follow the flash procedures to image your phone to a non standard build.
Flash to JF ADP1.5 first, See if that works. Is your card partitioned?
why make him flash to a jf build first it's an unneeded step the reason i tell him to reflash rc29 or rc7 is cause it's easier to follow him right from the beginning to make sure he helped to the fullest extent once he regains root access as long as he flashes the 1st radio 2nd spl 3rd non standard build of his choice he's fine flashing a jf build does nothing except add a step that is not needed and makes it more confusing
I reflash to rc7 and can enter in the SO.
Well, I try again to update a rom, but first I make a backup.
Thanks guys !
well, the same problem again.
I install this time:
1) Rc29
2) recovery image + spl
3) JF 1.5 ADP
and the phone stuck in the G1 screen again.
I do not know what I'm doing wrong.
Just a wild stab, did you confirm that the SPL flashed correctly? You would know by booting into it (CAMERA+POWER).
If not, I would flash the radio again (just as a precaution plus its fast), flash the SPL then confirm it has been flashed successfully.
Then grab the JF 1.51 ROM, wipe then flash that.
Is it even possible to jump from RC29 right to 1.5? I would try to go JF 43 than to 1.5
I don't see why not as long as he has updated his radio before flashing JF 1.51. Far as I'm aware JF 1.51 doesn't require additional internal space (that Haykuro's SPL provides). The key is in the Radio before the big jump up in revision number.
If I'm wrong though, feel free to correct me, Its been a very long time since I started out rooting my G1
For history's sake I went from Stock RC8 > Modified RC7 (to root) > Modified RC8 > JF 1.3 > JF 1.51 > Dude 0.8 - 1.3RC2 > Cyanogen 3.5 - 3.5.4.1
ok try this reflash rc7 get root access install the recovery.img flash hard spl
let us know when you get to that point then we'll run some tests
Well, I could solve the problem. Thanks guys !!
I repeat the installation (downgrade, recovery, hardSPL, radio) but this time I install the Dude cupcake 1.2b full, and this time everything went well !
I guess that would make a mistake at any step of the installations. Surely.
But, I have a new problem. When I download any app from de Android Market, an error arises ... "insufficient storage available". (yes, I have space in the phone memory).
which is what I do?
Related
k i had to unroot my fone cuz my apns was acting up. so my question is.
right after i update the spl, while in still in recovery
flash the rom that i have on my g1.
then reboot right.
it should have the arrow pointing down right. then followed by the g1 then loading screen.
Whenever updating to the latest SPL do these things first...
- Upgrade your radio to the latest version and confirm that it has been flashed
- Flash the SPL and give it time. Do not pull the battery if there are icons still on the screen. If you do you run the risk of bricking your G1
- Once flashed, check to see if the SPL has been flashed (reboot, CAMERA+POWER)
- If all clear then flash your desired ROM
hiroots said:
k i had to unroot my fone cuz my apns was acting up. so my question is.
right after i update the spl, while in still in recovery
flash the rom that i have on my g1.
then reboot right.
it should have the arrow pointing down right. then followed by the g1 then loading screen.
Click to expand...
Click to collapse
I think the SPL restarts your phone during the installation. I don't think you get the choice of whether you want to install the ROM at the same time *I think* (I haven't installed the SPL in a while). I don't think its required at any rate. Just reboot the phone into recovery once you're certain that the SPL flashed correctly.
Just make sure you get the radio first, haha. You shouldn't need to unroot because your APN's aren't working, just wipe and reflash...that normally fixes a lot of problems.
NeoBlade said:
Whenever updating to the latest SPL do these things first...
- Upgrade your radio to the latest version and confirm that it has been flashed
- Flash the SPL and give it time. Do not pull the battery if there are icons still on the screen. If you do you run the risk of bricking your G1
- Once flashed, check to see if the SPL has been flashed (reboot, CAMERA+POWER)
- If all clear then flash your desired ROM
Click to expand...
Click to collapse
both of the times ive rooted and installed that spl i would flash it and it would go to g1 screen twice, after a couple of minutes the second time i just pull battery, put in card reader (or have an extra card handy with a build) and copy a build onto it, then boot into recovery and flash it. its worked twice this way for me...
i have recovery 1.3.1 and if you flash the spl it wont reboot. so should i push the old recovery, then install the spl. then let it reboot, then flash my rom.
hiroots said:
i have recovery 1.3.1 and if you flash the spl it wont reboot. so should i push the old recovery, then install the spl. then let it reboot, then flash my rom.
Click to expand...
Click to collapse
well when you install the spl, it will hang on the g1 screen, it needs a build. so oyu have to pull the battery and put a build/rom on the card, then boot into recovery and wipe and flash. At least these are the instructions i followed and it worked both times i did it...dont know if that answers your question. When i did it i think i flashed 1.3.1 after the spl but i dont think it should make a difference...have you read any of the various tutorials? some of them are not good so be careful
hiroots said:
i have recovery 1.3.1 and if you flash the spl it wont reboot. so should i push the old recovery, then install the spl. then let it reboot, then flash my rom.
Click to expand...
Click to collapse
Once the SPL is flashed on, you have to physically hit home+back or whatever it is to reset the phone, DON'T SELECT WITH TRACKBALL, or else it won't write anything. Once you do that, it should say writing hbootimg or something then restart. It will appear with an icon on the screen for a few, and I can't stress this part enough, DO NOT PULL THE BATTERY, or you have a paperweight. Once its done doing its thing, it will reboot into recovery on its own.
xsnipuhx said:
Once the SPL is flashed on, you have to physically hit home+back or whatever it is to reset the phone, DON'T SELECT WITH TRACKBALL, or else it won't write anything. Once you do that, it should say writing hbootimg or something then restart. It will appear with an icon on the screen for a few, and I can't stress this part enough, DO NOT PULL THE BATTERY, or you have a paperweight. Once its done doing its thing, it will reboot into recovery on its own.
Click to expand...
Click to collapse
fyi...
this is the thread ive followed twice and have successfully flashed the so called 'dangerous' spl twice. Unless I read it wrong it says 'pull the battery' after flashing the spl. Either way it worked
http://forum.xda-developers.com/showthread.php?t=534461
My post above was for anyone who has Cyanogen recovery. That was the problem I had when I was updating to Danger SPL
xsnipuhx said:
My post above was for anyone who has Cyanogen recovery. That was the problem I had when I was updating to Danger SPL
Click to expand...
Click to collapse
i see. i mustve flashed 1.3.1 after the spl then...
DMaverick50 said:
i see. i mustve flashed 1.3.1 after the spl then...
Click to expand...
Click to collapse
Danger SPL has been out longer then 1.0 if I remember correctly.
Hiya ppl,
I recentlly rooted my phone and wanted to use teh JACxHERO ROM om my phone so I download the radio 2.22...... and the SPL.
According to the guides you need to do Radio first (update.zip) then SPL (spl_signed.zip). Then do a wipe and load your ROM.
The radio updated fine but when I do the SPL upgrade it is stuck at the G1 T-Mobile screen, or return to the recovery screen.
No matter I tried wiping and updating ROM again with JACxHERO again. Still same issue.
Put back my nandroid backup and other ROM is back. I also noticed that after the wipe all my data is still there nothing changed.
My question:
The radio is up to date. Should I:
wipe
SPL
wipe
ROM
wipe
????????
Thanks in advance
What recovery image are you using, Cyanogens? Is the SPL actually the new one? Hold camera and power when the phone is off and you should come to a white screen with skateboarding androids (if nyou come to a rainbow coloured screen, it didn't work)
YuYe said:
Hiya ppl,
I recentlly rooted my phone and wanted to use teh JACxHERO ROM om my phone so I download the radio 2.22...... and the SPL.
According to the guides you need to do Radio first (update.zip) then SPL (spl_signed.zip). Then do a wipe and load your ROM.
The radio updated fine but when I do the SPL upgrade it is stuck at the G1 T-Mobile screen, or return to the recovery screen.
No matter I tried wiping and updating ROM again with JACxHERO again. Still same issue.
Put back my nandroid backup and other ROM is back. I also noticed that after the wipe all my data is still there nothing changed.
My question:
The radio is up to date. Should I:
wipe
SPL
wipe
ROM
wipe
????????
Thanks in advance
Click to expand...
Click to collapse
Boot into the SPL and make sure it updated (Power + Camera button)
The SPL should be 1.33.2005
If not the SPL did not update correctly (If your using Cyan's recovery, do the SPL upgrade, but reboot pressing Home + Power instead of using the trackball)
If it is 1.33.2005, then try flashing another Hero ROM and seeing if it works
Also, make sure your SD card is clean (wipe your ext partition, you do have one right? )
one of the guides on here says that after you've flashed the new spl, you will get stuck on the g1 loading screen and you need to reflash with the rom you were originally running, let it reboot back into that rom, then try and flash jachero
eg
if you were originally running a cyanogen rom
flash radio
flash spl (then reboot and you will be stuck at the g1 screen)
reflash cyanogen (let it reboot completely)
then flash the jachero rom
that's what i did and it worked for me
I have the Cyanogen recovery 1.4 i Believe (latest and greatest)
OK really wierd indeed i see the android staking funny
This is what is says:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA11000)
RADIO-2.22.19.261
APR 20 2009, 15:30:43
HBOOT
<BACK> Fastboot Mode
I enabled fastboot now as well.
Jet when I flas the JACxHERO ROM it is loopt at G1 screen or turn back to recovery.
**Just download all zip's will do it now.
Make sure you have the correct partitions.
So no ROMs will flash?!
I know I have the correct partitions:
ext3 500MB
FAT32 1400 MB
linux-swap 32MB
I can flash others but I want HERO
Its Flashing right now brb with answer
LOL it hangs at the HERO logo
YuYe said:
I know I have the correct partitions:
ext3 500MB
FAT32 1400 MB
linux-swap 32MB
I can flash others but I want HERO
Its Flashing right now brb with answer
Click to expand...
Click to collapse
fat32>ext3>swap
you got the orders wrong.....
yeah I truned it around
Ok nice it worked thanks for clarying for me.
Only one thing, it is running slow. is it because of build ? or because my mem setting are incorrect ?
YuYe said:
Ok nice it worked thanks for clarying for me.
Only one thing, it is running slow. is it because of build ? or because my mem setting are incorrect ?
Click to expand...
Click to collapse
Welcome to Hero builds... they're all going to be slow compared to the Cupcake-based builds, though a lot of tweaking can help somewhat.
Also you have a class 4, a class 6 will help some more.
ok thnQ for the tip
And also my bat was running empty, charged my bat and worked a lot faster.
Not trying to be dumb but i been using JF 1.5 for like 6 month (completely forgot about xda and android stuff for about 4 month since i busy with school).
So now i got JF 1.5 and i want the new Cyanogen V 4.2.3.1 since i did read alot and seem like the best one for now.
And so i did try to install......for about 4 HOURS.
I tried :
- JF 1.5 -> Cyanogen V 4.2.3.1 = Stuck at the boot screen
- JF 1.5 -> cm-recovery-1.4.img -> signed-dream_devphone_userdebug-ota-14721.zip -> Cyanogen V 4.2.3.1 = After boot screen (when it suppose to come on the welcome screen) it just turn blank...the screen is one but completely blank.....
- I WIPE again -> HTC ADP 1.6 DRC83 -> Cyanogen V 4.2.3.1 = Samething, blank page.
So what did i do wrong? I did do the install of the recovery Img 1.4 and the ota-radio-2_22_19_26I.zip.
I did wipe everytime i install something.
Sorry for the bothering and noob asking for help but i do need help....i tried my best and sitted here for 4 hours already
And talking about those Guide on WIKI, i tried to follow all of them and still.......only thing i didnt try is reflash, unroot, root again and do the install of new ROM
Is your SD card partitioned correctly?
You need:
FAT32
EXT 2/3/4
Linux-swap
Do you have those three partitions?
If so, did you wipe your EXT partition?
rp1783 said:
Is your SD card partitioned correctly?
You need:
FAT32
EXT 2/3/4
Linux-swap
Do you have those three partitions?
If so, did you wipe your EXT partition?
Click to expand...
Click to collapse
Omg, i only have 1 partition
It Fat32 i believe and i dont know how to make the other
i have the Class 6 8GB though, what shud i do?
Quick update.
I just follow the Stock to Cyanogen Post to upgrade.
I reflash the whole phone, root then Cyanogen again with format 3 Partition of Fat32 (7000MB), ext2 (700MB) and Linux-swap (150MB) and it still doesnt work, stuck at boot screen this time.....i really really dont know what to do now, i tried everything
alright buddy, you don't need to have any ext or linux swap partitions to run cyanogenmod
just make sure you have his recovery image, 1.4, or amon ra's recovery flashed on your phone
now you might as well just flash the haykuro "death/danger" spl to repartition your phone's internal memory. flash the radio before the spl
now go into recovery and wipe data/cache,
follow cyanogen's directions on how to upgrade
flash the adp 1.6 htc recovery image file from the htc site, DO NOT REBOOT
immediately flash the latest cyanogenmod update on top of that, reboot,
it'll give you some stuff about writing the radio, just let it do it's thing
now you're done, boot up
and give it some time.
first boot takes a little bit more
enter your credentials into your phone, let it sync
then reboot again, it lets everything soup together
phamous said:
alright buddy, you don't need to have any ext or linux swap partitions to run cyanogenmod
just make sure you have his recovery image, 1.4, or amon ra's recovery flashed on your phone
now you might as well just flash the haykuro "death/danger" spl to repartition your phone's internal memory. flash the radio before the spl
now go into recovery and wipe data/cache,
follow cyanogen's directions on how to upgrade
flash the adp 1.6 htc recovery image file from the htc site, DO NOT REBOOT
immediately flash the latest cyanogenmod update on top of that, reboot,
it'll give you some stuff about writing the radio, just let it do it's thing
now you're done, boot up
and give it some time.
first boot takes a little bit more
enter your credentials into your phone, let it sync
then reboot again, it lets everything soup together
Click to expand...
Click to collapse
I just did the exactly same thing u said and it get past the Boot G1 Screen, then pas the Cyanogen Screen then it get stuck at a blank screen again, what wrong with that?
Since you're able to get to the "Cyanogen" screen -- do you have adb installed on your computer? A logcat of what's going on would be useful.
Alternatively; try flashing the "illegal" version of the newest Cyanogen ROM -- the "single flash" update. However, do it a little differently than you'd otherwise expect.
With the old JF 1.5, install Cyanogen Updater from the Market. Download any update -- doesn't matter what; you won't be flashing it.
Download the single-flash version of Cyanogen's actual ROM from the developer forum; and then dump it into the same folder that the CM Updater app dumped to. From within the contextual menu of the CM Updater app, choose "existing update" -- and then flash the single-update version.
//SOMETIMES//, flashing a ROM via the CM Updater will produce different results than flashing it "manually". I have no explanation for why this is, but I /have/ seen it happen.
Hi there,
I too am running JFV1.51 and wish to change to Cyanogen 4.2.15.1.
I have the iamage from HTC but nothing changes when I flash it and attempt to immediately flash Cyanogen over it?
Did you have any luck in resolving this issue/
Many thanks!
You guys that are having issues need to use ddms or adb shell logcat to see whats going on.
Going from Cupcake to Donut is going to change a lot in your phone and will take several minutes to complete. Most of which is in Framework. That Android boot animation that pops up is in there so thus it may seem like it's stuck at the G1 logo. Also you should consider flashing your phone to the newest radio (2.22.19.26I or 2.22.23.02).
ok this is what you really do lol no if ands or butts to this method.
goto www*androidhustler*blogspot*com and scroll down and search for ( 2010 how to get latest cyanogen mod ) download all apropiate files and begin steps.
let me know how easy these steps are and email me with any questions at: b6gsix#gmail*com
the ( # ) needs to be the ( @)
the ( * ) needs to be a period ( . )
enjoy the latest my friend and u know cm 507 is out. if u want to install cm507 on your g1 goto to youtube and in the search bar type in "androidappman" and i have 2 vids posted both part 1 and part 2 enjoy
Sent from my HTC Dream using the XDA mobile application powered by Tapatalk
E:Can't open /sdcard/update.zip
Hi,
Firstly, many thanks!
However, after following this comprehensive and generally straight forward guide I still can't flash the new CM!
I followed all the steps exactly, downgrading to RC7 (I'm in the UK) & re-rooting the phone.
When I reach the stage of flashing Android 1.6 Base Image, the CM ROM & the radio it states:
E:Can't open /sdcard/update.zip
and aborts!!!
I also do not have the option of alt+a only alt+s which is apply sdcard:update.zip
Where am I going wrong? And what should I do?
Thanks,
Joe
joeleenus said:
Hi,
Firstly, many thanks!
However, after following this comprehensive and generally straight forward guide I still can't flash the new CM!
I followed all the steps exactly, downgrading to RC7 (I'm in the UK) & re-rooting the phone.
When I reach the stage of flashing Android 1.6 Base Image, the CM ROM & the radio it states:
E:Can't open /sdcard/update.zip
and aborts!!!
I also do not have the option of alt+a only alt+s which is apply sdcard:update.zip
Where am I going wrong? And what should I do?
Thanks,
Joe
Click to expand...
Click to collapse
If you don't have ALT+A available, you have a recovery loaded other than what the guide says/thinks you should have. Are you using the recovery it suggests? Be it Amon Ra, Clockwork, etc.
Hi,
I was initially running Jesus Freak cupcake 1.5. Now the phone is currently at RC7 and rooted using telnet after starting the whole process again.
I am currently following the guide on the cyanogenmod wiki. I am using the recovery image suggested: CM recovery 1.4 img.
However, when I get to the stage for Flash Android1.6 & CyanogenMod latest I get stuck and states E:Can't open /sdcard/update.zip.
All other guides seem to be specific to the US, for example androidhustler. I don't where to go next!
Please help!
Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks
Do you have Amon Ra recovery?
No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)
When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.
I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating
1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.
why is it that that 99% of newbs are on cyanogen
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu
what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.
airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok
thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!
very quick question..
did you wipe dalvik-cache?
Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik
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.