[Q] Flashing ICBINB help and advice needed - Samsung Galaxy S (4G Model)

Hello All,
I am a new SGS4g user and have had the phone for about a month now. I've been looking into flashing, and have looked over a large number of forum posts and such to help guide me through what seems to be a difficult process. the guide i've been most looking into was this one
http://forum.xda-developers.com/showthread.php?t=1122508
I'm trying to flash the ICBINB ROM onto my phone due to all the good things I've read about this particular rom.
I finally decided that I would do it today, but when I went to wipe the data in Clockwork orange, the process got stuck at a file named Android.Secure. The post above mentioned something about this, but I wasnt too sure how to avoid it. I ended up restarting the phone, finding that it had gone to stock, ran the clockwork restore and found that in the restoration it also got stuck on this same file. After several minutes of freaking out and panicking, I did another force restart and found that thankfully my phone is back to where it was.
So I was wondering if anyone could guide me to another post, or help me to find a solution to this problem. And, if you could also help me find a more detailed guide because now I'm scared to do anything to the phone at this point without further info.
Thanks for any and all help!

Did you try just following the instructions in the post for ICBINB?
http://forum.xda-developers.com/showthread.php?t=1157593
The link you posted is to the NOOB's guide, which is cool, but it specifically mentioned ROM Manager. Did you install that or anything?
It's hard to say without a bit more information as to what you were doing, what step you were on, what other changes you may have made to the phone first. Can you provide some details?

Thanks for the response stephen,
Well what I had done up to that point was just create a recovery on ROM manager. Then I booted into clockwork and began the wipe of data, as the steps in the ICBINB steps said. It was here that it got stuck.
I have an update though. I tried again flashing this time through Rom Manager. When I did it, the Rom manager did its stuff and then began a reboot, where the phone got stuck on the opening screen (where it says galaxy s 4g and has the S logo). I shut it down, and tried to restart it and when I did, a voice started says `convert system partition, system not available`` and would get stuck. I pluged into odin and selected-repartition. Now, if I reboot I go into a red Voodoo lagfix recovery v. 3.0.2. Now as far as I know, I never put in a lagfix, so I have never seen this screen before. When I select the reboot option, it just gets stuck again and the voice says the previous statment once more. So what do I do from here?

From what I've read on this forum ROM Manager doesn't seem to work well with our phone. I can't speak from any experience with it, though.
The voice you heard is Linda. That's the voice you hear when voodoo lagfix is converting your partitions from the rfs filesystem to the ext4 filesystem. It sounds like something got hosed in the process of what you were doing.
Boot into voodoo recovery, disable voodoo across the board to be safe, and see if the phone boots. If not, try following my directions above to get on a stable GB ROM.
If you're able to ODIN the ROM & boot, then you can use the phone & flash other ROMs and whatnot.
If you're able to ODIN the ROM but it gets stuck in a loop or has an error, more than likely the voodoo is still enabled and this ROM can't use ext4. You would then need to ODIN one of drhonk's kernels (http://forum.xda-developers.com/showthread.php?t=1194032). Use the KG4 one. It comes with CWM Red, voodoo, and root.
Once you flash it you should be able to utilize the voodoo menu in CWM to enable or disable voodoo.

OKAY now I think I effed up royally.
I followed the steps, but then I tried to upgrade to ICBINB GB and now clockwork wont start. The samsung galaxy s4g logo will pop up, then it will go away. Occasionally I will get a full pixelated screen. Is there any recovery from this?!!!??
and it keeps cycling through this over and over again

If u can get to download mode ur fine...get one of the Odin leaks fo gb...put file in pda..flash...then get kj1 Drhonk kernel with voodoo...follow directions to do that...flash...should hear Linda...then, any ROM u choose to flash I'd put it directly on to ur sd...do NOT get ROM manager for anything instead goto market and get qick boot..once u do that...may the phone be with u. I'm nowhere near an expert but this saved my phones more than once.
Sent from my SGH-T959V using xda premium

Ps..if an leak gives u booy loop..three button recovery, factory reset SHOULD set u right on leak ROM
Sent from my SGH-T959V using xda premium

UPDATE
I have done something (not too sure what) and have been able to get into the main phone, however I am unable to get into Clockwork because whenever I do it is just Pixelatios. I keep seeing pixelations randomly at startup. It looks like I have the ICBINB theme and stuff, but I kinda want to go back and undo this and go to my saved backup. Any advice?

Related

No service?

I have searched a bit and can't find what I am looking for. I have a rooted tbolt and not new to rooting but not familiar with the d2global(my son's phone). So I rooted via the 4z method and everything went smooth. Downloaded cw bootstrap and loaded liquid gingerbread 2.5. I am very upset as I forgot to make a backup prior. Anyway I did a factory reset, cache wipe, etc.. and loaded the rom. Now there is no service and I am stuck in aiplane mode. I am hoping there is a simple fix. Any help is appreciated.
Thanks!
Nevermind, figured it out Loaded CM7, must have been something within the liquid rom.
there is no liquid rom for the d2g, if you try installing a rom for the d2 (which i assume liquid is for) your radio wont work, which is why its always in airplane mode.
cm7, on the other hand, is made for the d2g.
onedrops said:
I have searched a bit and can't find what I am looking for. I have a rooted tbolt and not new to rooting but not familiar with the d2global(my son's phone). So I rooted via the 4z method and everything went smooth. Downloaded cw bootstrap and loaded liquid gingerbread 2.5. I am very upset as I forgot to make a backup prior. Anyway I did a factory reset, cache wipe, etc.. and loaded the rom. Now there is no service and I am stuck in aiplane mode. I am hoping there is a simple fix. Any help is appreciated.
Thanks!
Click to expand...
Click to collapse
i did the same thing, and now i'm stuck, i tried to do a recovery and somehow it won't let me i tried holding the power and volume down to try to do a manual recovery, cause i did a backup so i can restore, unfortunately i can't get to that recovery...if i knew liquid 2.5 was bad i shouldn't have installed that POS...any help will be good, thanks
Your baseband is FUBAR, so you need to reflash an SBF.
Instructions here.
Finding the images and RSDLite with Google should be easy enough; if not (and only in that case), PM me.
JFYI: there is no way to get to CWM if you cannot boot the OS to at least a bootloop after the point where adb shell becomes available.
Thank you
Thanks, i will def give it a try...i can get to bootloader by holding power button and both volume button...i just didn't know what to do from there...
The problem i'm having is :
phone does boot up running liquid 2.5, problem no service stuck in airplane mode
all function of the phone works just can't make calls etc without service
i do see the backup files when i open file manager, just can't get it to open up, hopefully that bootloader thing works,
if rom manager was working that would help solv e everything cause i would be able to restore, but the app is not there when loaded liquid, usually when you ask to rebbot it would give you an option to reboot or recover...oh well
thanks so much hopefully i can try to resolve it later tonight...
by the way what is CWM, what does that mean
CWM is ClockworkMod Recovery, the “custom” recovery that lets you perform backup and restore of your phone's flash memory and install various custom ROMs and modifications. See http://droid.koumakan.jp/wiki/ClockworkMod_Recovery for a bit more information on it.
Question where would i find the images and what rev RSDLite do i use 4.9 or 5.0, sorry, just asking...
Google the file names, should net you some results.
4.9 or 5.0, doesn't really matter. 5.0 is reported to work better than 4.9 on Windows 7 systems.
thanks, i got it to work....thanks so much...

Any way to root w/o ODIN + wipe?

Before you flame, I did read this and was still a bit confused.
Basically, I've been using my Verizon-ROM'd Charge (with the latest updates) for about a month now. I'm ready to ODIN over to a new ROM (probably the 8/3/11 HumbleComb ROM), but without a one-click root, I'm not sure how I can install/run/backup all my data with TB if I don't have root access.
So right now, I'm looking for any way to root my Charge, backup all the apps/data before I flash a ROM that seems (from my reading) to do a full wipe.
The other problem I'm having is in regards to my wife's Charge. We both came from Vibrants and she had quite a few important apps (with critical data) she'd like to bring over. However, she could care less about going to a rooted/aftermarket ROM. She just wants her old apps to work.
I've searched fellas... I'd really like some help on this. Please throw me a line... even if it's a link to a thread I missed.
Thanks in advance.
Wrong section but just odin this kernel, it doesnt wipe any of your data. Then you can use Titanium Backup or whatever you use to backup your apps. Dont restore system apps unless you want force closes.
http://forum.xda-developers.com/showthread.php?t=1092114
Nevermind...
mbh87 said:
Wrong section but just odin this kernel, it doesnt wipe any of your data. Then you can use Titanium Backup or whatever you use to backup your apps. Dont restore system apps unless you want force closes.
http://forum.xda-developers.com/showthread.php?t=1092114
Click to expand...
Click to collapse
Awesome! I'll give it a try and see how it goes. I appreciate the helps.
**EDIT**
That worked perfectly. Thanks! Backing up everything with TB now in preparation for flash a real ROM.
Mods, please move as necessary.
most roms nowadays will root you when flashed/odined so yeah just back everything up and load up the rom of your choice
blazing through on my VZ Droid Charge 4G
Things were going so well, I decided to flash HumbleComb 1.5 using Odin. Now I'm stuck at the Samsung logo. I'm guessing it was because the tool originally recommended here enabled the lagfix. Funny thing is, if I reflash HC 1.5 from Odin, the first thing I get is the recovery screen. Inside the voodoo settings there, it says Voodoo is disabled and not scheduled to be enabled on the next boot (this was after the 2nd flash, though). Voodoo had to be enabled. I got a 1400+ quadrant score...
Gotta read the "fix your phone" thread now. Was too tired to fart around with it last night. At least I got everything backed up.
Flapjack said:
Things were going so well, I decided to flash HumbleComb 1.5 using Odin. Now I'm stuck at the Samsung logo. I'm guessing it was because the tool originally recommended here enabled the lagfix. Funny thing is, if I reflash HC 1.5 from Odin, the first thing I get is the recovery screen. Inside the voodoo settings there, it says Voodoo is disabled and not scheduled to be enabled on the next boot (this was after the 2nd flash, though). Voodoo had to be enabled. I got a 1400+ quadrant score...
Gotta read the "fix your phone" thread now. Was too tired to fart around with it last night. At least I got everything backed up.
Click to expand...
Click to collapse
Wipe everything in recovery (data/cache/dalvik) and then plug into Odin and flash. That works every time for me when it sticks on the Samsung logo...

Lost all my apps after reboot... (Infuse 4G)

I am posting this as somewhat of a noob...
I went from ROM after ROM after ROM with no problem. Then I installed Dlev GB (WICKED SWEET!!!!) and reinstalled my all my apps with TiBu; but upon getting every thing I wanted set up, restarting, I lost ALL of my apps over and over. I then started to Data wipe and Dalvik wipe and install repetedly trying to get it working. NO SUCCESS... Then went back to stock using gtg's "Returne to Stock" (Always a HUGE THANK YOU!!!!) and started from scratch as it were. Installed Modded CWM again gtg, and then installed Dlev one more time... Come to find out that i REALLY screwed things over before doing the return to stock. What also was happening was that each time that I would use TiBu, it would throw EVERYTHING into my System Partition instead of just installing it in the USB/Internal SD.
So if you are running across this also... Here is the way I worked it out. It doesnt take all that long, just get all your tools infront of you before going forward.
Tools list:
[ODIN][UCKD5] GTG's Ultimate Unbrick - Return to stock - Working PIT included (gtg465x)
[RECOVERY] 100% working ClockworkMod Recovery for Infuse 4G (gtg465x)
USB Cable
What ever ROM you would like to install
And that is it!! Just start going step by step and you will be on your way to a clean slate. Enjoy! But don't come back to me if you do something wrong and Brick the Junk out of your Infuse! I'm just stating what helped me and hopefully it will for you if your in the same boat.

I give up! Ready to Root!!

On my 4th G2x. Same problems as the others. Reboots on its on, sleep of death. In fact this morning I was talking on phone and it shut down. I had to remove battery and reboot.
I called Customer Service that has always been super nice. This time they said, oh, since this is your 4th and this one just in 6 days I can't help you I have to send you to Tech. The Tech guy basically said "known software problem, sending replacement won't do any good. Can't give you different phone. Maybe it is your SD card and apps you have loaded. He actually told me Facebook app could cause it to shut down. Said to reset to factory, remove SD card and use it for 3 days with no apps. After 3 days if all is well then start adding apps. I asked what if it has problems during the 3 days? He said, 'there is nothing we can do. I will report this to LG and they will send out an update. I don't know when but they will update the software".
WTH?! So I am done. I will do the root. Now i just need to read all these great threads to figure out how and which version! Wish i could just pay one of you to do it for me!
Thanks for letting me rant.
I've been running stock since August with no issues but I really wanted the LG Camera app so I installed CWR and flashed the WeaponX rom with no issues. Everything works and it's even smoother then stock Gingerbread. Just follow the directions to the T and the process should take less than fifteen minutes if you have all your files ready to go.
Enjoy!
seangprice said:
I've been running stock since August with no issues but I really wanted the LG Camera app so I installed CWR and flashed the WeaponX rom with no issues. Everything works and it's even smoother then stock Gingerbread. Just follow the directions to the T and the process should take less than fifteen minutes if you have all your files ready to go.
Enjoy!
Click to expand...
Click to collapse
Thanks! Which directions did you follow? There are a number of threads here.
The directions are a bit confusing as they reference other threads and then have comments stating this step is now obsolete. etc. Seems like I first need to get the ROM Manger?
https://market.android.com/details?id=com.koushikdutta.rommanager.license&feature=search_result
Correct?
i followed this http://forum.xda-developers.com/showthread.php?t=1060715 and was fine. this was my first root as well.
http://forum.xda-developers.com/showthread.php?t=1056847
I used this method to NvFlash and install Clockwork recovery which is the basic software you need in order to flash ROMs. You do not need ROM Manager. Once you've done the NvFlash and installed CWR you can copy your ROMs to the SD card or phone storage and flash through Clockwork Recovery. Make sure you backup your stock install through CWR prior to flashing anything new so you can return the phone to a usable state.
As always follow the directions verbatim, some steps take time as well. Also make sure your battery is 100% charged... If it dies during any portion of the process bad things can happen.
I had all of those issues until I flashed cm7... then the issues became very minimal... I once had 8 reboots in a day on stock rom, during phone calls and everything... You are definitely taking a step in the right direction
P.S. my wife has completely stock phone on stock rom and has Facebook app with no issues, she just got lucky I guess
To OP: do you have 2.2 or 2.3 installed as your stock rom... read carefully there are different instructions for both
Never use ROM Manager. Even if it worked perfectly on our phone I still would never recommend it. I've seen it cause more harm than good.
Anyways, you don't even technically need root to flash a ROM.
Just NVFlash CWM. After that you can upgrade to the latest CWM via ADB. Then flash your desired ROM. I suggest CM7.
yeah, you know ROM manager... now forget it. Use NVflash and clockwork
I got myself in trouble!
I followed instructions and all went well. I installed the GB, no problems. No I was brave so I thought I would try the Cyanogen mod. It too installed fine. I don't like it. Now i can't get rid of it! I tried reinstalling the GB and the cyanogen won't go away! i tried restore to factory, but it won't go away!!
Please lend me your advice on how to remove Cyanogen mod!
donbeth said:
I got myself in trouble!
I followed instructions and all went well. I installed the GB, no problems. No I was brave so I thought I would try the Cyanogen mod. It too installed fine. I don't like it. Now i can't get rid of it! I tried reinstalling the GB and the cyanogen won't go away! i tried restore to factory, but it won't go away!!
Please lend me your advice on how to remove Cyanogen mod!
Click to expand...
Click to collapse
Then just wipe and flash a new ROM.
Make sure you wipe data, cache, dalvik then format system before flashing new ROM.
Clearly I am a dunce.
I uninstalled the driver on pc. Did a reinstall. Flashed ROM again. Installed GB zip. rebooted and the dang Cyanogen MOD is still there!
I even went over all steps again, this time flashing back to stock. Still Cyanogen MOD is boots up
donbeth said:
Clearly I am a dunce.
I uninstalled the driver on pc. Did a reinstall. Flashed ROM again. Installed GB zip. rebooted and the dang Cyanogen MOD is still there!
I even went over all steps again, this time flashing back to stock. Still Cyanogen MOD is boots up
Click to expand...
Click to collapse
Yes yes you are when you flash a new rom wipe data wipe cache wipe dalvik and wipe system
Sent from my LG-P999 using XDA App
i remember, I followed this video.
http://theunlockr.com/2011/05/03/how-to-load-a-custom-rom-on-the-t-mobile-g2x/
to install a new rom
remember: (once you've copied the zip on sd card, power the phone to enter into clockwork and steps)
1. back up and restore
2. wipe data/ factory reset
3. install zip from sd card
so far, it hasn't failed me
you can skip the first one, but shouldn't
Just download Weapon if you want to go back to stock. Its Stock with a few needed tweaks and fixes. Very stable and no issues.
G2x - 2.3.7 CM7
Transformer - 3.2 Revolver OC/UV
The reboot issue were in all my G2X(3). Only rom that fixed that was Weapon G2X. Running a custom rom is the way to go with this phone, otherwise you'll go through 100 replacements with same issues.
Today I did an exchange for my brother's line which he has the G2X and the rep told me I could get a brown color G2X because they no longer carry original color or a Sensation. (Not sure what he was talking about brown color because I thought all G2X were the same color other than the white floating around)
So I decided to just get the Sensation, I know it's got issues of it's own, but will give it a shot because I want the G2X to just be a memory of the past.
This phone could have been a beast, but will never live to it's full potential.
Good luck and if you need to exchange again and you don't mind getting a Sensation I would suggest bringing that up to the rep.
Hercules Hercules!!
I'm a little confused...I've been using ROM Manager just fine...?
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
If you screw up and can't boot up, ROM manager cannot get you into recovery. Only an NV flashed clockworkmod recovery will boot up in the event of a boot loop.
Sent from my LG-P999 using xda premium
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
You don't have recovery with Rom Manager, yeah it flashes all the roms but if you get into a bootloop or worse then you are SOL.
Hercules Hercules!!
Neejay said:
I'm a little confused...I've been using ROM Manager just fine...?
Click to expand...
Click to collapse
Rom manager works just fine. However, like previously said, you just need to NVFlash first for safety reasons.
From a complete stock G2x, NVFlash, Nandroid Backup, and flash a previously downloaded rom (Weapon or CM7 or MIUI or Eaglesblood or any of the other wonderful roms). Custom roms have root so THEN you can go to town with Rom Manager.
I use Rom Manager as my primary flashing service because it not only downloads them, but will automatically reboot into recovery, perform your desired wipe options, and flash. With CM7 it will automatically check for the latest GAPPS and flash it too in one fowl swoop.
Just have to NVFlash first.
I NVFlashed my neighbors G2x the day he got it and, while he didn't want to try custom roms just yet, we did a Nandroid Backup just for laughs. Now he's running MIUI.

I think I broke it.

I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
At this point, i would suggest to do a full wipe (clear data/factory reset, caches and also format system under storage and mounts). Then flash your flavor of CM7 and while still in CWM, flash the kernel of your choice, DON'T REBOOT, but clear cache/dalvik. Reboot, let it sit for a while and you should be good.
Sent from my LG-P999 using xda premium
Luriden said:
I just got this phone yesterday and immediately installed CM7. Thinks were going well, except for the random restarts at the lock screen and some apps not working. I read that Faux's CM stock kernel improves stability, and I hoped it would fix the restarts.
I read the directions thoroughly, wiped out the cache, wiped out the Dalvik cache, installed the kernel, and rebooted. It got stuck at a black screen, but I read that it does take a while, so I left it for about 10-15 minutes before removing the battery.
I wiped all caches, including user data, and reinstalled CM7 hoping it would fix whatever kernel problem just happened. Now it freezes at the blue LG screen.
I've tried several different caches that are all supposed to be comparable with my phone, and after installing them (after wiping all caches and /system each time) I'm stuck at the blue LG screen. I also tried flashing the entire phone to stuck, but to no avail. Installing the GB Kernel stock got me back to the black screen, this time flashing a brighter shade of black periodically, but still after 20 minutes, nothing happened.
I'm going insane after spending all day searching these forums and Google. If there's anything I can try besides installing kernels and reinstalling CM7, please let me know. I'm an idiot and didn't backup before I installed CM7 the first time, and every backup I've downloaded gives me an MD5 checksum error. At least I still have access to recovery. Most results I pulled up with searches brought me to people who lost their recovery menu as well, I'm not sure why I can't fix this even with the recovery menu still intact.
Click to expand...
Click to collapse
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after that you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Instaling custom kernel instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
ratza66 said:
This is what you need to recover your phone
http://forum.xda-developers.com/showthread.php?t=1248644 , after you need to root again and reinstall NVflash. Check youtube for instractions to flash CM7 on your phone. Good luck
Click to expand...
Click to collapse
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Make sure you downloaded his CM7 version and not Stock kernel.
Luriden said:
That worked! I came across that earlier, but I downloaded a similar package with a flash.bat that didn't fix it. Sure enough, I'm back. Thanks!
Click to expand...
Click to collapse
You welcome, I've added info on how to install custom kernel too
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Luriden said:
What are the usual behaviors while waiting for the phone to boot up for the first time with the new custom kernel? I downloaded the latest March nightly of CM7 (the latest April build gave me a bad file error while trying to install for whatever reason) and Faux's LGE Pre-OC/UV Kernel Version 013, did the proper order of installation, and it's been sitting for about 15 minutes now at a black screen that keeps flashing on and off. With USB plugged into my PC, I'm hearing a rapid "plugged/unplugged" sound loop with each flashing screen. Will I have to do the whole ROM Recovery tool process to try again?
Click to expand...
Click to collapse
You can't install custom kernel on nightly release. Use RC 7.2 and yes do the rom recovery and back it up so the next time you can just restore to any rom that works on your phone.
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Luriden said:
This may sound crazy, but I feel like I CM7-proofed my phone. Ever since I messed up that first time with the kernel and used the recovery tool, I can't get CM7 loaded anymore. I got 7.2 RC and installed it with the kernel the proper way, and got stuck at the LG screen.
So I used the recovery tool again, then NVFlash, wiped data/cache, installed the root file, then tried installing just 7.2 RC by itself. No luck.
I used recovery tool again, then NVFlash, then wiped data/cache, then used restore to bring it back to the stock + root that I made this morning before trying 7.2 RC and I'm back... so I went to CWM again and did wipe data/cache, and installed the SAME CM7 file I installed with yesterday morning which worked fine at the time, the latest stable release (7.1), and I'm still stuck at the LG screen.
This makes absolutely no sense. EaglesBlood installs fine, so it's not a problem with custom roms, I just don't like EaglesBlood (and EaglesBlood also froze when installing a custom rom the correct way as well). I'm tempted to just stick with the stock GB 2.3.3 + root since it works, I'm just missing the features I had yesterday of CM7 before I installed that god forsaken kernel.
Click to expand...
Click to collapse
I Think you are missing a one step, Wipe Dalvik. Ok let start from the begining,
First restore your phone to stock, let it boot. Root your phone and install CWM. Install CM7.2 RC rom and let it boot. Go back to the CWM and follow this instructions:
Wipe Cache
Wipe Dalvik
Wipe Batt Stats
Install Kernel
Fix Permissions
Reboot
all these steps are important. I was using CM 7.2 RC with Faux's kernel without any problem and it worked flawlessly
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Luriden said:
I just tried again with those instructions, and I still can't even get CM7 to boot up for the first time.
- Recovered my phone to stock using rom recovery tool
- Let boot, got to android's home screen, shut down
- Used One-Click-Recovery's "Flash CWM 5.0.2.0 Internal and External SD ROM" feature to install CWM (I'm assuming this is the proper way. I learned this from a YouTube video and it helped me to root my phone and get CM7 working the first time)
- Booted into CWM, wiped user data and cache, installed root-g2x-su-2.3.6.3.zip
- Restarted just to be sure (though I have tried just flashing CM7 after the root without restarting) and got into the android home screen just fine after I had to go through initial setup again. Though oddly enough my Google Apps were still present. They weren't present the very first time I rooted my phone, I had to install gapps.
- Shut down phone, went into CWM again
- Wiped user data, wiped cache, installed CM7 7.2 RC1
- Rebooted
- Stuck at blue LG screen for eternity.
I'm using the same root file as I did when I rooted my phone for the first time, and I've tried using this same method with the very first CM7 file I successfully installed and ran, and I'm still stuck at the blue LG logo unless I stock recover again and stick with stock. Rooting works fine, I've been able to run rooted apps on the stock rom, I just can't install any version of CM7 again for the life of me.
Click to expand...
Click to collapse
Follow this guy on YT, you will find everything there
http://www.youtube.com/watch?v=fxMnnarHaOU
Installing CM7 tutorial
http://www.youtube.com/watch?src_vi...id=annotation_334516&feature=iv&v=Cy9on64jAZs
This one is even better
http://www.youtube.com/watch?v=vUaWXM8GwUI
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Luriden said:
I've done what all three of those videos have shown. These methods work for other custom roms just fine, just not CM7 which is what I want, regardless of what build I use. Which rom is the closest to CM7? I tried EaglesBlood and I noticed a lot of changes I didn't agree with, I didn't toy around with it long enough to see if I could get it working like CM7.
EDIT: Even tried Nullifier Dual Wipe, still stuck. Just... wow.
EDIT #2: Now EaglesBlood doesn't even want to run, also getting stuck at the LG logo after recovering, wiping data/cache, and flashing the rom. It worked fine last night, I just erased it so I could give CM7 another shot and didn't have enough space on my SD to have a backup of that AND my rooted stock.
EDIT #3: Did the recovery/root/flash method again, going from fresh stock to flashed CM7, and this time it sits at the blue LG logo for a few seconds, before restarting and going back to the white LG logo. I wiped the cache though to prevent a bootloop, and I think most bootloops occur with the CM7 logo anyway.
There's no chance of any files being on the micro sd that could be causing the problems, could there? And is there anything else I should be wiping/formatting these tries? Like maybe rom recovery doesn't wipe EVERYTHING out, and I still have remnants of other attempts still?
Click to expand...
Click to collapse
No chance. Nothing will be left over when you wipe your phone. Your SD card is only accessed when you tell CWM to do so. Take your phone back to stock. Do it again this time try either a froyo rom or ICS rom. Then go back wipe everything and install CM7. Sometimes you have to take the long way. after flashing my phone a bazzilion time I learned this the hard way when I couldnt load EB ICS anymore. Had to run GB to get to ICS. Try it in reverse or from a step below and it should go through fine. IF it doesn't, you might have to use ICS instead, which may be stuttery, but works damn well.
DupleX01 said:
Keep in mind that you have to clear cache/dalvik right AFTER you have flashed the kernel, before reboot.
Click to expand...
Click to collapse
I'm wondering why he still has the issue. YOU CLEAN CACHE BEFORE FLASHING KERNEL/ROM UPDATES!!!
Sent from my LG-P999 using xda premium
For God sake, just flash a random ROM to get access to inside your phone.
1. DIAG your phone OFFLINE with v21e baseband (phone will automatically restart)
2. Let it stay for 5mins after that
3. Use your phone for 15mins
4. Root using 1Click
5. Install CWM
6. Install your ideal ROM + GAPPS (if needed) via CWM
7. Reboot
8. Go outside your living room and watch TV for at least 15mins
9. Reboot your phone into CWM and flash your ideal kernel
10. Enjoy!!!
You better know which ROM/kernel to choose from. Period.
How to upgrade/downgrade your baseband? Do some search, please!
Sent from my LG-P999 using xda premium
I'll do a flash of Froyo or ICS and possibly some baseband research tomorrow. Considering my luck getting a simple rom flash to work, I don't feel too comfortable dealing with the baseband.
A friend was brave enough (somehow) to let me root and install CM7 on his phone, he has the same phone as mine. I got CM7 7.2 RC and Faux's DM UV working like a dream on my first try. Tried it on my phone after recovering it, same problem. So it's a problem that exists deeper on my phone, not with my methods.
The NAND restores for GB and Froyo give me MD5 checksum errors, and the stock zipped rom of GB gives me an installation failed error, so I'm thinking a zipped Froyo rom won't work either, but it might be worth a shot.
Tried Weapon and MIUI too. No go. If I don't get stuck at the blue LG logo, then I'm stuck in a loop between the two LG logos or stuck at a flashing black screen. 8/10 times though it's the blue LG, I think the other errors may have actually been me forgetting to wipe my cache when I was flustered.
I'll try ICS, and hopefully won't get to a point where I have problems installing things I used to be able to, since that seems to be the pattern. After that I finally give up.
I FIGURED IT OUT! Well, sort of. For the hell of it, I downloaded CM7 7.1.0.1 through Rom Manager and it installed fine. It downloaded it to my internal SD, so I hooked it up to my PC to copy the 7.2.0 RC1 to my internal SD and tried installing. No go.
So I went on my phone's web browser and redownloaded 7.2.0 RC1 that way directly to the phone. It works. So somehow, roms I copy from my PC to the phone appear to not work, yet apps and kernels still do. I'm running CM7 7.2.0 RC1, downloaded through my phone's web browser, with Faux's DS UV kernel, copied from my computer. After four days, I finally found a workaround, so I'll stick to it. Whatever works, I guess. I can try reinstalling my USB drivers, but I can probably get by with a combination of the phone's web browser and ES File Manager w/ LAN if need be.

Categories

Resources