I just installed the latest Das Bamf 2.0 Beta 5 and my Thunderbolt is stuck on the dots screen (background only with notification bar on top, 0 signal bar, battery and wrong time). I cleared everything before I flashed to the rom but I am stuck. What did I do wrong? What can I do to fix this?
Boot into recovery and wipe then reflash the rom or a backup. Don't fret.
Sent from The Republic of Texas
ddgarcia05 said:
Boot into recovery and wipe then reflash the rom or a backup. Don't fret.
Sent from The Republic of Texas
Click to expand...
Click to collapse
I guess that I have overlooked it, probably because I am worried as hell about screwing my phone.
Probably be a dumb question because I should have seen it but, How do I boot into recovery?
Edit: Found it. When I was looking for it earlier I didn't go far enough, needed to go one more page.
Well she lives again. I also tried to flash to 2.0 beta 5 and it did the same thing again. I am not sure what the problem is, but I guess I will just enjoy a rooted TB for a little while and then flash to a ginger rom of some sort.
Did you flash the radio for bamf that is posted in the first thread of bamf?
There is a special radio you need to flash to get gingerbread working.
Sent from my GingerBamf'd Thunderbolt
capflya said:
Did you flash the radio for bamf that is posted in the first thread of bamf?
There is a special radio you need to flash to get gingerbread working.
Sent from my GingerBamf'd Thunderbolt
Click to expand...
Click to collapse
Will this keep it from even loading the lockscreen?
If so do I flash it before or after the rom?
Edit: I just went to the 2.0 Beta 5 thread and looked, I do believe I flashed the correct radio. I will give it a try again in the morning, it is almost 1 here so I really need to get into the bed, gotta be up at 6 in the morning for work.
Happened to me too. I just reloaded the new GB radio and the flashed the 2.0 rom. All good after that.
Haha... Yeah lack of sleep doesn't help... Give it another shot after you've had a chance to get some rest.
Some people have had issues like yours. You could try re-flashing just the ROM. If all else fails just re-flash everything like eatrice313 did. You'll get it eventually.
If you flashed the radio in the bamf 2 thread then you did the right radio. You flashed it in hboot right? Should have been named P05IMG.zip If you did that then you did it right. Flash rom, then radio.
I used the non-adb method - flash rom, batt pull, then hold power and vol down to boot into hboot then flash the P05IMG file.
Sent from my GingerBamf'd Thunderbolt
capflya said:
Haha... Yeah lack of sleep doesn't help... Give it another shot after you've had a chance to get some rest.
Some people have had issues like yours. You could try re-flashing just the ROM. If all else fails just re-flash everything like eatrice313 did. You'll get it eventually.
If you flashed the radio in the bamf 2 thread then you did the right radio. You flashed it in hboot right? Should have been named P05IMG.zip If you did that then you did it right. Flash rom, then radio.
I used the non-adb method - flash rom, batt pull, then hold power and vol down to boot into hboot then flash the P05IMG file.
Sent from my GingerBamf'd Thunderbolt
Click to expand...
Click to collapse
After some sleep I carefully downloaded the Alpha Gingerbread radio set and flashed it through hboot and then reflashed the Bamf 2 ROM and got the same result, broken on reboot.
Sorry man... not sure whats going on. Did you try rebooting to recovery and reflashing just the ROM after it boots up and is "broken"?
Somebody with more knowledge might be able to help out, I'm still fairly new to the android scene.
capflya said:
Sorry man... not sure whats going on. Did you try rebooting to recovery and reflashing just the ROM after it boots up and is "broken"?
Somebody with more knowledge might be able to help out, I'm still fairly new to the android scene.
Click to expand...
Click to collapse
I did attempt that but it didn't work out for me.
The odd thing is that I tried to flash to Gingeritus and I kept getting force until the phone would just shut down. Could these two problems be be related?
cmcconkey said:
I did attempt that but it didn't work out for me.
The odd thing is that I tried to flash to Gingeritus and I kept getting force until the phone would just shut down. Could these two problems be be related?
Click to expand...
Click to collapse
I would try REdownloading the latest Bamf Beta 5 and putting it on your sd card...then factory reset everything and wipe cache and dalvik cache, and reflash Bamf. You may have gotten a bad download file.
Taykiin said:
I would try REdownloading the latest Bamf Beta 5 and putting it on your sd card...then factory reset everything and wipe cache and dalvik cache, and reflash Bamf. You may have gotten a bad download file.
Click to expand...
Click to collapse
I will give that a try this evening, for some reason I left my data cable at home (all 5 of them).
cmcconkey said:
I will give that a try this evening, for some reason I left my data cable at home (all 5 of them).
Click to expand...
Click to collapse
lolzzz...yeah it happens, let us know and if anything I'll help you troubleshoot your problem.
I'm having the exact problem. Flashed the GB radio, had no service with the froyo rom, flashed BAMF GB Beta 5, boot animation plays and then phone freezes.
I just reflashed the radio and still nothing I'm about to reflash the ROM and see what happens
Did you wipe Data?
I wiped data and cahe and dalvik cache
How long did you let it sit before turning off/pulling battery/throwing at the wall? First boot can take upwards of 5 minutes.
Are you talking about the animation screen or the home screen after that? I let it set a few min at the home screen and nothing happened
Just my .02.... When I and most others made the switch from froyo to gingerbread, it wasn't an exaggeration when we say "wipe, wipe, and wipe again". I wiped everything 3 times... By that I mean factory reset 3 times, wipe dalvik 3, batt stats and all 3 times. Flashed Rom in recovery, batt pull before reboot, volume down + power to get to hboot, flash radio and reboot. I had zero reboots upon startup and haven't had a problem since. Well at least no problems that weren't directly caused by experimenting with some stuff. When the phone does boot the first time, just walk away from it and let it do its thing. The kernel needs to settle. Don't jump in and start trying to set it up too fast. Patience helps a lot in the beginning.
edit: Solved, just flash one .zip at a time. So flash AOSP lockscreen.zip then reboot, go back into CWM and flash the next one. Thanks anoninja118!
Hoping someone can help, I flashed the Sens3 theme on Eclipse(I know it's for GC, I didn't care lol) and it was pretty buggy so I immediately rebooted into CWM and flashed eclipse131/aosp/screencapture/Vrecorderfix and rebooted. When it finally booted up I noticed the lockscreen was still the puzzle, I thought that was weird so I tried taking a screenshot(back+home) and it wouldn't work. I rebooted and reflashed the .zips(excluding eclipse131 this time) then rebooted and again, none of them were active. So I went back into recovery and reflashed Eclipse131 then let it fully reboot so it could convert and ****, then I went back into recovery again and tried flashing the .zips, still nothing. Last thing I tried was clearing cache/dalvik and reflashing but alas, to no prevail.
Any help would be appreciated, I have everything backed up in Titanium so it's no big deal to lose my apps but I don't want to redo my 7 home screens lol.
blarrick said:
Hoping someone can help, I flashed the Sens3 theme on Eclipse(I know it's for GC, I didn't care lol) and it was pretty buggy so I immediately rebooted into CWM and flashed eclipse131/aosp/screencapture/Vrecorderfix and rebooted. When it finally booted up I noticed the lockscreen was still the puzzle, I thought that was weird so I tried taking a screenshot(back+home) and it wouldn't work. I rebooted and reflashed the .zips(excluding eclipse131 this time) then rebooted and again, none of them were active. So I went back into recovery and reflashed Eclipse131 then let it fully reboot so it could convert and ****, then I went back into recovery again and tried flashing the .zips, still nothing. Last thing I tried was clearing cache/dalvik and reflashing but alas, to no prevail.
Any help would be appreciated, I have everything backed up in Titanium so it's no big deal to lose my apps but I don't want to redo my 7 home screens lol.
Click to expand...
Click to collapse
when I ran eclipse for a while I had kinda the same problem... I found out to get them to work each zip needs its own flash session in CWM i.e. flash AOSP lockscreen or whatever then boot up phone, boot into CWM and flash next .zip and repeat
blazing through on my VZ Droid Charge 4G
anoninja118 said:
when I ran eclipse for a while I had kinda the same problem... I found out to get them to work each zip needs its own flash session in CWM i.e. flash AOSP lockscreen or whatever then boot up phone, boot into CWM and flash next .zip and repeat
blazing through on my VZ Droid Charge 4G
Click to expand...
Click to collapse
Appreciate the fast response, testing it out right now. Doubt it will work since the first time I flashed Eclipse I did all the flashes in one go but let's see :]
edit:...it worked... fine, you win. I'll hand out thanks where they're necessary... thanks! really appreciate it lol.
blarrick said:
Appreciate the fast response, testing it out right now. Doubt it will work since the first time I flashed Eclipse I did all the flashes in one go but let's see :]
edit:...it worked... fine, you win. I'll hand out thanks where they're necessary... thanks! really appreciate it lol.
Click to expand...
Click to collapse
np lol I've tried out all the roms at least once so I've had most of the problems people post and I try to solve it and pass on the info
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.
Hi,
I have flashed new ROM ( [ROM]SKY-ICS 4.2F6-2.6.1 (8/4)(UCLF6 Base) AT&T-OFFICIAL ICS.PROJ MARGARINE, W/ G-NOW).
Phone works fine, exept that I can't shut down or restart the phone - it just freeze.
thanks
I had same problem before... was from backup cwm when I do restaro backup... I just flashed same rom again never I get this problem
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
i had similar problem on previous version of sky ics. i went through the normal process of format system, clear cache, wipe davilic, but regardless of the version of sky ics, it would never shutdown/reboot. (got tired of holding down volume up/down and power to hard boot).
I ended doing ODIN back to att stock and verifying it shutdown/reboots fine.
Then i went through and installed skyics again. BAMMM it works fine afterwards...
Sounds like you had a bad install. Do a factory wipe and clean reinstall of SkyICS. If that doesn't fix it, take yourself back to stock, re-download (and check MD5s on) all files you need to install Sky, then reinstall it.
A good rule of thumb I use if a clean wipe fails, or something just doesn't feel right afterwards, is, "When in doubt, return to stock."
Thanks! problem was solved, I reflashed the stock rom then the custom one
Thanks! problem was solved, I reflashed the stock rom then the custom one
It happens usually due to an old CWM, so if it happens again update it.