Standard disclaimer applies: if anything breaks down, it wasn't me.
Use this only on LG Thrive P506, not P505 or others.
Here's a flashable zip with the latest AT&T FOTA rom (thunderg-user 2.2.2 FRG83G LG-P506-V11h.19BA7112F9). Old, non-working mirror is here.
Changes from stock rom?
- rooted, deodexed, added a2sd support.
- updated Google apps (market, gmail, maps, voice search).
- added FM radio app (from P500) and AppWidgetPicker.
- RTL fix applied.
- AT&T apps moved from /system to /data, so they can be uninstalled.
- build.prop modified: debug.sf.hw=1 and wifi.supplicant_scan_interval=120.
How to flash?
- if you don't have a custom recovery, you first have to root, install Rom Manager and install CWM (use Optimus One (Old BB) version for now, it's imperfect but usable).
- use Rom Manager to boot to recovery (do nothing else from Rom Manager!), make a backup, and install the zip. The rom does not wipe your data, but do a factory reset before complaining about FCs.
Advanced topics
- a patched CWM recovery can be found here. It only solves the color issue, not others. A real solution may be pending.
- I usually delete DunServer.apk and IQAgent.apk from /system/app, as they seem to run automatically and do nothing. Perhaps WapService.apk is expendable too. YMMV.
- AT&T preset bookmarks/contacts can be removed by using SQL tools on the appropriate databases. I didn't bother with wifi/apn presets.
Saving a post for a rainy day.
Thank you so much for working on this, as soon as I get home from my trip I'll be trying this out, I can't wait.
Maybe you can share some screenshots?
It's a stock, non-themed firmware.
See the official page or any review of the Thrive for screenshots.
This Stock P506 Thrive ROM didn't Recovery my P506 Thrive - Why?
Had all the prerequisites setup to apply this Stock P506 Thrive ROM.
In a pinch I needed a ROM and I tried this ROM for my P506 Thrive.
Has anyone also had problems recovering to this ROM? And if so, how did you work around and make a good recovery using this ROM?
Would this work on a Phoenix (P505)?
I tried it and it has the color issue where everything is blue/green and poor resolution. Has anyone found a fix for this yet?
electech said:
Would this work on a Phoenix (P505)?
I tried it and it has the color issue where everything is blue/green and poor resolution. Has anyone found a fix for this yet?
Click to expand...
Click to collapse
One possible fix is not to install a P506 rom on a P505.
It is also written in boldface in the 2nd line of the original post.
Another fix is to restore the backup you did in CWM recovery.
brightstar2 said:
Had all the prerequisites setup to apply this Stock P506 Thrive ROM.
In a pinch I needed a ROM and I tried this ROM for my P506 Thrive.
Has anyone also had problems recovering to this ROM? And if so, how did you work around and make a good recovery using this ROM?
Click to expand...
Click to collapse
What kind of problems? bootloop or FC? did you try to wipe?
LG Thrive P506 2.2.2 ROM Recovery hasn't recovered
Hi,
The P506 phone boots into CMW recovery over and over. Or with key-press sequence phone will boot into fastboot.
Problem isn't limited to this tweaked 2.2.2 ROM, the backup when restored is equally stuck in the boot to CMW.
Wiped many times in my opinion, but what does "wiped" mean to you? Maybe I didn't do it precisely as you want/require before attempting 2.2.2 recovery.
I think you should reflash recovery from fastboot.
Wipe is relevant if you get FCs or standard boot bootloops, not so much for recovery bootloops.
LG P506 Thrive Failure to Recover in to 2.2.2 ROM Newbie
Will try ...
Would you consider sending me a PM, URL or post with tad bit more precision (on reflash recovery from fastboot). Only a few months with this. Still a Newbie
I wrote you a link in the thread you opened.
(As a last resort, I'd try to flash the P506 original stock recovery and see what happens, perhaps it'd do a factory reset.)
Fastboot cries on Update of LG P506 Thrive ROM
If you mean that I should give these fastboot commands...
>fastboot -w
>fastboot update /sdcard/p506_AT_T_v11h_deodexed_rooted.zip
... THEN my LG/Fastboot cries with the following errors/messages:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
errror: update package has not android-info.txt or android-product.txt
So close, so many URLs to consider for remedy and if someone would take a moment and type out the right fastboot command or share the pin-point URL how-to. THEN Thanks in ADVANCE!!
I haven't seen any tutorial around here that recommends the use of fastboot update.
- fastboot flash recovery cwm-recovery.img,
- fastboot boot cwm-recovery.img (keys not working now)
- adb shell
- reboot recovery (keys are working now)
- flash the rom itself from within CWM.
Thanks, Will try (2nd, 3rd) time to flash & recovery LG P506 Thrive
Thanks that is precise and super clear! I needed that. More than worth the few extra bytes of redundant data. Appreciate your time. Will try this again over the week.
And was there a significant typo (prior posting)
Thanks again ... not up to 100% speed with expert android lingo and acronyms, so spelling it out helps.
brightstar2 said:
And was there a significant typo (prior posting)
Click to expand...
Click to collapse
Nope, just missed a letter while typing (key->keys)
Must something obivious I'm doing wrong to Recovery LG P506 Thrive with 2.2.2
Tried, still boots into recovery (orange). Do you see something obvious?
fastboot flash recovery CWM3100-p506-recovery.img
-- OK
fastboot boot CWM3100-p506-recovery.img
-- OK
Then Original Blue-style CWM Recovery on phone
adb shell
-- OK
reboot recovery
-- OK
Now Orange-style CWM Recovery on phone
Apply update from .zip
Choose zip from sdcard
/sdcard/p506_AT-T_v11h_deodexed_rooted.zip --- selected and installed
-- OK
Power Down
Power Up
--> Back into Orange-style CWM Recovery
and here the LG P506 stays following recovery with 2.2.2 ROM
SOLVED - LG P506 Thrive Now 2.2.2 after unroot & AT&T OTA upgrade try to 2.2.2
Thanks to the XDA Forum and users. With it I stitched together a solution and have returned my LG P506 (AT&T Thrive) to good working order with 2.2.2
This was my first Android learner phone, since I would soon need to know Android +/- for work.
Started with a backed up (and backed up) Rooted LG Thrive running 2.2.1 with CWM Recovery. Tried to unroot and return to stock (unfreeze AT&T bloatware, unroot, etc). The AT&T 2.2.2 over-the-air (OTA) was successful, but after reboot the P506 was stuck in a CWM boot-to-recovery mode.
All the fastboot commands, all the CWM recovery commands worked fine. New Custom Stock ROM 2.2.2 re-flashed fine, but the phone would still either boot to CWM Recovery to Fastboot-mode depending on Keys/buttons pressed at boot.
So phone wasn't bricked, but was stuck.
From this XDA forum (this and other XDA forum posting here and there). The Solution was found.
From another LG P506 thread here I got 2 files boot.img and system.img for LG P506 (I did use these files, but perhaps a full custom CWM ROM recovery would be good to -- These are the facts, you can refine)
From the LG Fastboot command I
>fastboot flash boot boot.img
>fastboot flash system system.img
Tried to boot but still stuck at CWM Recovery
POST AFTER POST here says wipe phone more or less. I did wipes with CWM Recovery. I was never really sure how to do enough but NOT TOO MUCH of a WIPE. Too timid as a noob, never tried to fastboot to erase.
LEARNED POINT: fastboot erase is/must-be different than CWM Recovery wipes/formats etc.
The LG P506 was a starter Android phone to learn on, build skill and make mistakes without wrecking an $800 phone.
I had seen another XDA Forum posting about the structure of the phone's file system ... it showed 'system' 'cache' 'userdata' 'misc' 'FOTABIN' 'FOTA' ... plus a few more.
HINDSIGHT: I looked for but could not find a good here is how ANDROID boots for this phone. (1) this .. (2) that ... (3) etc .. kernel, GUI, etc. I suspect I would have learned that something I erased below like FOTA or FOTABIN was running and dying throwing me into CWM Recovery.
I felt I had nothing to loose at this point and no matter what I tried I was (up to that point) still always able to get into CWM Recovery. CWM Recovery ROCKS!
The BREAK THROUGH....
In fastboot mode again.
>flastboot erase FOTA
>flastboot erase FOTABIN
>fastboot erase misc
>fastboot erase cache
>fastboot erase userdata
>fastboot reboot
... there was the LG P506 running 2.2.2 sans the AT&T bloatware. Battery needed recharged, so I took my son to House of Air in the Presidio in San Francisco for trampoline dodgeball.
Nearly 24 hours later the LG P506 Thrive is still working fine.
I suspect that (1) either the boot & system img were needed and something needed erased/wiped.
-- OR --
(2) something like FOTA and/or FOTABIN need erased first and foremost.
As newbie, I was not sure quite what to do at each turn. Using google, I struggled to find insightful android documentation for my problem that was current and not about older versions of ANDROID. The Forum experts use acronyms and speak at an expert-level at times, but the gist of what they shared feels/felt sound. But kind of hard to hear Babe-Ruth explain how to hit a HOME RUN and all together different thing to step into the batter's box and hit a HOME RUN.
Anyhow, the XDA FORUM ROCKS. The experts are EXPERT, I'm unworthy. THANK YOU FOR THE HELP.
If anyone is having problems with this rom you're not doing something right. I wiped dalvik cache, cache, system, and battery stats. Then flashed the rom. Then reboot. It took a few minutes to start up. But its working great. Now im doing some experimenting. I have done several things to my phone as well. Internet speed tweak (which made my dl speeds increase dramatically) and other things. If anyone has things they want tested on a thrive, im willing to do it.
Sent from my LG-P506 using XDA App
Related
Please read this post in its entirety before downloading and flashing.
THIS IS FOR I9020T ONLY! IF YOU DECIDE TO GET BRAVE AND TRY THIS ON AN I9020A, I9023 OR D720, MAY THE FORCE BE WITH YOU. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO ANY PHONE BY USING THIS ROM.
YOU MUST FLASH THIS ROM USING CLOCKWORKMOD RECOVERY. THIS WILL NOT FLASH USING THE STOCK ANDROID 3E RECOVERY AS THE ZIP FILE IS NOT SIGNED. I HAVE NOT TESTED IT ON OTHER RECOVERIES.
This is probably more for posterity now than anything else, however I have created a CWM-flashable full on ROM for the Nexus S Gingerbread firmware, version 2.3.1, build GRH78. This is built exactly the same way that the full OTA ROM packages for 2.3.3 and 2.3.4 were built.
Some notes:
1. Flashing this ZIP will remove ClockworkMod Recovery on first boot. Android 2.3.1 introduced a script that automatically overwrites alternate recoveries with the stock Android 3e recovery each time you reboot your phone. The script is located in /system/etc/install-recovery.sh. If you root the ROM, you can rename this file to avoid flashing the stock recovery on each reboot.
2. Flashing this ZIP will overwrite your bootloader and radio, restoring them to I9020XXJK1 and I9020XXJK8 respectively. These are the versions that came stock with GRH78.
3. GRH78 is receiving OTA updates. As of this writing, the latest version of Android is 2.3.4, and Google is pushing an OTA update for 2.3.1 to 2.3.4.
4. This ZIP will NOT clear your user data or cache. For users running a stock ROM, I would highly suggest clearing your data and cache manually as sometimes downgrading without clearing data and cache can cause problems. If you are coming from a non-stock ROM, you are required to clear your data and cache or the ROM will not boot.
5. Since writing NFC tags wasn't introduced until GRI40/2.3.3, the Tags app is read-only.
6. There is no video chatting through Google Talk. This feature was not introduced until GRJ22/2.3.4.
Instructions:
1. Download the Stock GRH78 ROM package here.
2. Copy it to the root of your USB storage.
3. Reboot into ClockworkMod Recovery (or flash it).
4. Select "Install ZIP From SD Card"
5. Select "Choose ZIP"
6. Find the ZIP file and select it.
7. Wait for it to finish.
8. Wipe data and cache (optional but HIGHLY recommended for stock ROM users and REQUIRED for non-stock ROM users)
9. Reboot and have fun.
Reserved...just in case.
Hello,
I tried your ROM with my Nexus S (I didn't know the version exactly) and I have now a black screen and the phone won't boot or show me anything =(
OyoKooN said:
Hello,
I tried your ROM with my Nexus S (I didn't know the version exactly) and I have now a black screen and the phone won't boot or show me anything =(
Click to expand...
Click to collapse
Aw come on man.......you gotta read! Can you get into recovery?
Sent from my Nexus S using XDA Premium App
Yes I know, I'm a dumb ass.
I have only access to fastboot (via Terminal only).
Try flashing Clockwork Mod Recovery with fastboot.
fastboot flash recovery.img
I did but I even don't know if I can boot into the recovery because the screen stay off.
Can you get to the bootloader? If you don't even see the bootloader screen, you may have bricked it.
I managed to fix it using ODIN.
Thanks.
Congrats Glad you got it working.
plz plz help begging u !
OyoKooN said:
I managed to fix it using ODIN.
Thanks.
Click to expand...
Click to collapse
i made the same mistake plz plz help me ....
i m stuckkkkk !
Lol I can't help but say what a bunch of retards haha. Make sure you gave the correct version before flashing. Might give it a try one of following days
Sent from my Nexus S
Please read this post in its entirety before downloading and flashing.
THIS IS FOR I9020T ONLY! IF YOU DECIDE TO GET BRAVE AND TRY THIS ON AN I9020A, I9023 OR D720, MAY THE FORCE BE WITH YOU. I AM NOT RESPONSIBLE FOR ANY DAMAGE CAUSED TO ANY PHONE BY USING THIS ROM.
YOU MUST FLASH THIS ROM USING CLOCKWORKMOD RECOVERY. THIS WILL NOT FLASH USING THE STOCK ANDROID 3E RECOVERY AS THE ZIP FILE IS NOT SIGNED. I HAVE NOT TESTED IT ON OTHER RECOVERIES.
This is probably more for posterity now than anything else, however I have created a CWM-flashable full on ROM for the Nexus S Gingerbread firmware, version 2.3.2, build GRH78C. This is built exactly the same way that the full OTA ROM packages for 2.3.3 and 2.3.4 were built.
Some notes:
1. Flashing this ZIP will remove ClockworkMod Recovery on first boot. Android 2.3.2 contains a script that automatically overwrites alternate recoveries with the stock Android 3e recovery each time you reboot your phone. The script is located in /system/etc/install-recovery.sh. If you root the ROM, you can rename this file to avoid flashing the stock recovery on each reboot.
2. Flashing this ZIP will overwrite your bootloader and radio, restoring them to I9020XXJK1 and I9020XXJK8 respectively. These are the versions that came stock with GRH78C.
3. GRH78C is receiving OTA updates. As of this writing, the latest version of Android is 2.3.4, and Google is pushing an OTA update for 2.3.2 to 2.3.4.
4. This ZIP will NOT clear your user data or cache. For users running a stock ROM, I would highly suggest clearing your data and cache manually as sometimes downgrading without clearing data and cache can cause problems. If you are coming from a non-stock ROM, you are required to clear your data and cache or the ROM will not boot.
5. Since writing NFC tags wasn't introduced until GRI40/2.3.3, the Tags app is read-only.
6. There is no video chatting through Google Talk. This feature was not introduced until GRJ22/2.3.4.
Instructions:
1. Download the Stock GRH78C ROM package here.
2. Copy it to the root of your USB storage.
3. Reboot into ClockworkMod Recovery (or flash it).
4. Select "Install ZIP From SD Card"
5. Select "Choose ZIP"
6. Find the ZIP file and select it.
7. Wait for it to finish.
8. Wipe data and cache (optional but HIGHLY recommended for stock ROM users and REQUIRED for non-stock ROM users)
9. Reboot and have fun.
Reserved...just in case.
Thank You will post results if needed,i doubt it,again thank you very much,ping33tx
I can access the bootloader, I can access the clockwordrecovery, odin recognizes the device, but I can not access the intern sd.
I can only try to restore by odin
I'm looking rom to use the odin.
My nexus s is bricked, anyone help-me
I'm Brazilian and I used google translate, sorry.
i was googling for stock roms and found this
i had no idea if i have the i9020t or not
now my phone wont even turn on, no life
any ideas?
*EDITED: not sure which version i do have actually
SS2006 said:
this rom was bad...i was googling for stock roms and found this
i have the i9020t
now my phone wont even turn on, no life
any ideas?
Click to expand...
Click to collapse
Wanted to flash this ROM, just wanted you to confirm that yours is an i9020A, not i9020T, therefore that's the reason why it won't turn on now.
Sorry for your phone by the way.
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Can you boot it to bootloader?
From off position, try Vol UP + Power.
If you can see the Android logo and 4 menu options, you got yourself a great deal.
SS2006 said:
that could be the reason, i got this phone for very cheap and it was soft bricked so i had no idea if it was 9020a or 9020t (no box with it)
if this is the case, what can i do, USB jig or jtag?
Click to expand...
Click to collapse
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
al_madd said:
See at the back of your battery....
reboot to boatloader..
hopefully you can still get to recovery...
Click to expand...
Click to collapse
He doesn't need to. If he can get to the bootloader, he can flash and boot a recovery via fastboot.
No guys, seems i got myself in a mess. It is indeed a i9020a (the info under battery was erased so i didnt know0 and i flashed the i9020t rom in this thread (different radios)
so this thing is HARD bricked, screen won't turn on, no bootloader, nothing, tried to get it into download mode (even without screen turning on) assuming it was working, but odin doesn't realize its there
so i think my only solution is jtag. I can buy a usb jig but I think that usb jigs dont do anything for hard bricked phones, am i right
Much thanks for your help.
Hello experts,
After CAREFULLY reading the instructions to root and install Cyanogen on my X2, I have run into a problem. After downloading Rom Manager from the market, I installed CWM, which worked fine.
Going by the instructions, I wanted to ensure I performed a NANDroid backup of the stock ROM, 'just in case'. So i did.
After confirming, and granting 'su' privileges, the phone restarted, only to be stuck on the LG logo.
Holding down VOL DNW + POWER is no help, as the phone was still stuck on the logo.
I don't understand what I have possibly done wrong, but none of this was stated in the wiki so I am assuming i'm in a unique situation?
After some googling:
> I have read that it may be from CMW converting to EXT4.. whereas the stock rom can only run in EXT3? .. android.modaco.com/topic/336318-4-apr-r1-backtoext3-for-converting-your-device-er-back-to-ext3/ ..
> All hope is not lost as apparently, I can flash to stock rom using NVFlash: .. android.modaco.com/topic/335474-25-mar-nvflash-stock-rom-release-v10b-dated-1300166062-15032011/ ..
Ok, so I understand I have a possible solution to my problem (NVFlash), however I would like to know why this happened & how I can avoid it from happening in the future.
Thanks for your help in advance.
sumsoomi.
Incase anyone else has the same problem,
SOLUTION:
For P990 - NVFlash instructions: http://forum.xda-developers.com/showthread.php?t=1229407&highlight=recovery
Recovery images: http://forum.xda-developers.com/showthread.php?t=1098745&highlight=recovery
Does this mean two versions of CWM are installed?
One with Rom Manager & one with NVFlash?
If so, how to get rid of one?
sumsoomi said:
Incase anyone else has the same problem,
SOLUTION:
For P990 - NVFlash instructions: http://forum.xda-developers.com/showthread.php?t=1229407&highlight=recovery
Recovery images: http://forum.xda-developers.com/showthread.php?t=1098745&highlight=recovery
Does this mean two versions of CWM are installed?
One with Rom Manager & one with NVFlash?
If so, how to get rid of one?
Click to expand...
Click to collapse
NVflash is a built in safety system by nVidia, it has nothing to do with the recovery image. You should be very careful with NVflash, because it's very low level and even the slightest mistake could brick your phone.
sumsoomi, S0ci0 ............................ thnx
boot problem
you can try this http://forum.xda-developers.com/showthread.php?t=1617458,fl**** with cwm if you can boot in cwm recovery
hi last night (very late) i was trying out a miui rom i am trying to port, i used the wrong update-script and i seems as though its overwritten my unsafe partition even though i was in safe. i couldnt see the safeboot splash but could still get to it form tools in the bootloader menu, i now have the safeboot menu back but no touch buttons. i have done a restore but i only have 2 backups and this is making me think i haven't backed up when i got on the leak.
so dose any one have a backup they would let me try to see if this is the case, can i fastboot out of this (i dont really understand how fastboot works with this phone as its locked down), or is there anything else i can do to get it back working i would like to keep root if possible.
Are you still able to boot your phone when you try to boot your phone of you can then the best thing for you is that try to install fresh stock room of your phone repeat the whole process again that would be better.
If I or anyone else have helped you in any kind of way please press THANK YOU button.
what type of phone do you have.if you Samsung thing will go fast and smooth to go back to stock Rom
If I or anyone else have helped you in any kind of way please press THANK YOU button.
i have droid 4 this is the droid 4 sub forum, i can boot the safe rom, i used to be able to boot non-safe (had miui on it) but after trying a restore form backup its not booting. i am still new to safe boot i dont fully know how it works.
I think you should be able to use the process for going from one leak to another to to get back to a stock ICS leak system. Follow the instructions in the Droid 4 Utility Updated thread.
Sent from my Droid 4
been thinking that and hoping it to as i think there is root for ICS now, but you are ment to unfreeze apps and uninstall safeboot before you upgrade both of witch i cant do, there is no apps to unfreeze to as the partitions gone.
and safeboot is the only thing that is making this phone not bricked.
Unfreezing and uninstalling recovery shouldn't matter the way I understand it. Fastbooting .219 should wipe that stuff out allowing you to freshly install the ICS leak.
Sent from my Droid 4
Yea, I'd fastboot "back" to 219, which of course WILL brick you, but also allow you to flash the ICS leak, which should get you back to a working phone.
Luckily there are root methods for ICS now, so you don't need to have root on 219 to enjoy root on (ICS) 213 :laugh:
Don't worry man, I've done it a dozen times already.
Just flash the system.img and the preinstall.img .219 fastboot files and erase your data and cache partitions with moto-fastboot:
Code:
moto-fastboot erase userdata
moto-fastboot erase cache
moto-fastboot flash system system.img
moto-fastboot flash preinstall preinstall.img
moto-fastboot flash boot [boot.img for .208/.213 kernel]
(You can skip erasing your /data partition if you want but unless you really need something on there, it's usually best to just start fresh.)
You can find the moto-fastboot executables on xda here with a quick search.
Otherwise you can just do a normal fastboot flash through RSD Lite but the method above is a bit quicker since you only really need to re-flash your /system and /preinstall partitions. If you choose to use RSD Lite, then you have to delete the boot.img file in the .219 package and replace it with the .208/.213 boot.img that you can find here on xda.
Pop the corresponding leaked .208/.213 update .zip file onto your external sdcard and reboot your phone into recovery mode by pressing Vol-Up+Vol-Down+Power and choosing Recovery Menu from the screen with white text on a black background and follow the prompts to install the update from your external card and you're good to go.
thanks i will try this soon.
i have updated to 213 now and it boots in to the animated droid eye but dose nothing not even getting a logcat.
got it working just updated again then wiped catch and data then it booted thanks a lot.
Sweet, glad to hear it. Happy hacking!
YABLP (Yet Another Boot Loop Problem)
Hi,
I'm having a devil of a time installing CM7 on my GalaxyS I9000. Description of my procedure and problem below.
I've been beating my head against a wall for a week so any help GREATLY appreciated.
-John
Phone: Galaxy S "I9000"
Trying to Flash: CM7.2.0 using CWM Recovery
What I did:
Flash stock ROM w/ODIN v1.85 - OK
Wipe Data/Wipe Cache
Flash ChainFire (CF-Root-XX_OVA_JVU_2.3.6-v4.3-XWM3RFS.tar) w/ODIN v1.85
Wipe Data/Wipe Cache
Phone now rooted OK
Boot to CWM Recovery
Install zip from sdcard
Select update on SDCard (cm-7.2.0-galaxysmtd.zip from CM site)
Flash completes in just a few seconds - much too quick!
Phone reboots automatically
Now stuck in boot loop
Screens in boot loop:
1. GalaxyS/GTI9000/Samsung
2. GalaxyS/Cyanogen(mod)
3. CWM menu scrolls by too quickly to read
Back to 1.
Tried Heimdall but complained about missing XML file
Tried installing "Datafix". Would not install (says not compatible with device)
Tried STFW: many reports of same problem but no solutions seemed relevant & appropriate
Clues:
After CF flash, disk use as follows
/system: used 27.3M, free 9.4M (97%) (seems pretty full)
/data: used 47M, free 1916M (2%) (seems pretty empty)
Me thinks maybe /system is too small/full to accept update?
This is the 3rd I9000 I've flashed. First 2 went Ok but this time it failed although identical files/procedures used (I think).
HELP!
I've seen a similar problem on my I9000 - I think the CWM scroll complains about "can't mount /data".
I'm in a similar position, I can't get anything to flash and boot though : http://forum.xda-developers.com/showthread.php?t=1967982
This happens pretty much every time you flash any kind of CM rom from stock. All you need to do is flash CM7, it will go in to bootloop with various text scrolling through thats too fast to read. You just pull battery while in the bootloop. Then replace battery, three button combo to recovery and flash the same CM7 zip again. This time the install will take a while longer. Afterwards flash gapps and reboot and you should be good to go.
I tried this - but same result, just spins round on the CM boot screen
Where do the wipe data and wipe cache commands fit in to this? Before/after both installs?
I don't normally bother with gapps - just trying to get it loaded. Does that make a difference?
Also, no SIM card in at all during all this...
IT WORKED!
Bless you BandiBp!
I'll be sending my first-born by return mail (please don't tell my wife
Yeah that happens because its flashes a kernel with a new partition system. Dunno why only a few roms warn people about this.
Sent from my GT-I9000 using xda premium
You're welcome mate, yeah the reasons are the new partition changes on different roms. I agree that rom flashers should be warned in advance about this. Would reduce problems A LOT. My general rule is if a Rom installs in under 5 secs, then you should always flash again.
Anyways have fun.