Related
So I flashed CM9 alpha 13(after wiping) but can't get service to activate on my phone. Same problem I'm having with alpha 9. I use the activate button when it starts and it tells me it failed. Under "About Phone" and "Status" I can see that the My Phone Number setting is wrong so is the MIN.
When I call my carrier to manually activate, the short codes they give me to manually input this info do not work.
Anybody else had this problem?
Go into Sprint Zone, and try to manually activate.
Sent from my MB855 using xda premium
Nevermind. That won't work. Sorry
Sent from my MB855 using xda premium
Flash cm9 and reboot dont install gapps till after it activates
Sent from my MB855 using XDA App
I will try this. Thank you sir!!
Ok, so I wiped... Flashed CM9. Rebooted. The activation call failed, so I called sprint to manually activate again. They asked me to punch in ##971912# which is supposed to pop up a dialog screen where I can manually input MIN etc but did not. Not sure what to do.
Flash back to a blur rom activate then reflash
tcf84 said:
Ok, so I wiped... Flashed CM9. Rebooted. The activation call failed, so I called sprint to manually activate again. They asked me to punch in ##971912# which is supposed to pop up a dialog screen where I can manually input MIN etc but did not. Not sure what to do.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Ok, I've got my phone up and running on Rocko's ROM. I'm doing a nand backup now. So, to be clear... I need go to my recovery. Data Reset and wipe dalvik cache. Then I need to flash CM9. I then need to activate(or make sure I'm still activated), and once that is confirmed I need to flash Gapps?
Sorry. I'm just trying to figure out where I went wrong the first time...
Try that, you're the first person to have issues so its a new issues
tcf84 said:
Ok, I've got my phone up and running on Rocko's ROM. I'm doing a nand backup now. So, to be clear... I need go to my recovery. Data Reset and wipe dalvik cache. Then I need to flash CM9. I then need to activate(or make sure I'm still activated), and once that is confirmed I need to flash Gapps?
Sorry. I'm just trying to figure out where I went wrong the first time...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
tcf84 said:
So I flashed CM9 alpha 13(after wiping) but can't get service to activate on my phone. Same problem I'm having with alpha 9. I use the activate button when it starts and it tells me it failed. Under "About Phone" and "Status" I can see that the My Phone Number setting is wrong so is the MIN.
When I call my carrier to manually activate, the short codes they give me to manually input this info do not work.
Anybody else had this problem?
Click to expand...
Click to collapse
I had this problem as well. I've also bricked my phone flashing an electrify pudding by mistake on my photon. My fix after fixing my boot loader issues was: I reverted to completely stock. Then I called sprint and had to reactivate my phone. After getting everything working and having a secure connection for over a day I then flashed cm7 to make sure that would work. After it did I did a says wipe and wiped everything else. And flashed cm9 then went into recovery wiped and flashed again. Then I flashed gapps and boot up. After booting up I went back and wiped again. And then used the phone for about twenty minutes and wiped and flashed "all" again. It was a long drawn out process. But I have had none of the issues that people are having on the forum. Battery life is great after calibrating. 3G is almost as fast as the 4G I had. Never have a single reboot or battery pull. Wifi and Bluetooth bead on perfect. I'm new to xda but not development. I'd post my success in the forum, but I'm not yet at ten post.
Sent from my MB855 using XDA App
FanBoy_Hunter said:
I had this problem as well. I've also bricked my phone flashing an electrify pudding by mistake on my photon. My fix after fixing my boot loader issues was: I reverted to completely stock. Then I called sprint and had to reactivate my phone. After getting everything working and having a secure connection for over a day I then flashed cm7 to make sure that would work. After it did I did a says wipe and wiped everything else. And flashed cm9 then went into recovery wiped and flashed again. Then I flashed gapps and boot up. After booting up I went back and wiped again. And then used the phone for about twenty minutes and wiped and flashed "all" again. It was a long drawn out process. But I have had none of the issues that people are having on the forum. Battery life is great after calibrating. 3G is almost as fast as the 4G I had. Never have a single reboot or battery pull. Wifi and Bluetooth bead on perfect. I'm new to xda but not development. I'd post my success in the forum, but I'm not yet at ten post.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
I tried reverting to stock as outlined by qbking77 but every time I sbf'ed the file as instructed I lost my recovery. The 'Unlocked' notice disappeared as it was supposed to but once I did that I couldn't get any recoveries to stick, stock or CWM, until I "re-unlocked" the phone with that sbf. Even then I couldn't get the stock recovery to write properly.
I'm pretty new to all of this. I unlocked my Optimus S and tried a few ROMs on it before I settled on Reborn Rom, but that's about my only experience with these things. I'm not incompetent(I hope) when it comes to this stuff, but it's definitely a learning curve. I'd like to master the whole process though so I can delve into the dev side of things a bit.
Joker - Thanks for the help. I'm up and running with no problems.
What did you do?
tcf84 said:
Joker - Thanks for the help. I'm up and running with no problems.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
A combination of what you and FanBoy suggested. First I wiped and flashed Rocko ROM. Got the phone to activate. Then I wiped. Flashed CM9. Wiped again. Booted up and verified service was active. Wiped again, Flashed CM9 again, wiped again, and flashed gapps v3.
I really don't know what the problem was to start. I originally tried to flash CM7 and couldn't get signal at all. So I flashed MIUI with the same issue. Finally I flashed CM9 and had signal but couldn't activate. So the problem wasn't tied to CM9, but I honestly have no idea what I did to lose signal/activation or to gain either of those back, but my phone does work now and I've successfully flashed both CM9 and Rocko without the loss of signal or service and have nand backups of both since my biggest problem originally stemmed from not having a nand backup of my latest working set up.
I think I hear the ice cream man!
tcf84 said:
A combination of what you and FanBoy suggested. First I wiped and flashed Rocko ROM. Got the phone to activate. Then I wiped. Flashed CM9. Wiped again. Booted up and verified service was active. Wiped again, Flashed CM9 again, wiped again, and flashed gapps v3.
I really don't know what the problem was to start. I originally tried to flash CM7 and couldn't get signal at all. So I flashed MIUI with the same issue. Finally I flashed CM9 and had signal but couldn't activate. So the problem wasn't tied to CM9, but I honestly have no idea what I did to lose signal/activation or to gain either of those back, but my phone does work now and I've successfully flashed both CM9 and Rocko without the loss of signal or service and have nand backups of both since my biggest problem originally stemmed from not having a nand backup of my latest working set up.
Click to expand...
Click to collapse
Most custom roms disallow communication from what ever it is that allows you to activate with sprint. I noticed that porting in sprintzone.apk often doesn't work and you can't activate with the dialer because it requires communication with sprintzone. So you need to flash to a rom that allows activation and then work your way back up. Glad to hear you got it working.
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
avus_m3 said:
Well, my phone is non responsive to anything I do and I am unable to get into download mode. I rooted the phone using this guide from creepyncrawley (http://forum.xda-developers.com/showthread.php?t=1311081).
For a complete device history:
I later installed a nightly of CM9. Everything worked great for the most part with the various nightly builds. I changed to the UCLD3 leak for awhile without hitch.
I needed something off of my stock rooted rom from the thread above so I did a restore...again no problems with the switch. I did have to fix permissions to open some apps.
I switched back to the UCLD3 leak to test data speeds with plans on switch to the new CM 9 nighlty. I booted into recovery and wiped data, cache, and dalvik. I went to install the CM 9 4/17 rom and it checked the rom and started the install. The progress bar never moved at all and after awhile the screen/phone turned off. Since then, the phone is completely unresponsive. I am unable to get into download mode, the cap lights do not turn on...nothing.
What happened...I have no clue. Is there any way I can fix this with the tools here?
Click to expand...
Click to collapse
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
dandrumheller said:
This might be a stupid question, but... Dead battery?
Sent from my SGH-I777 using Tapatalk 2 Beta-6
Click to expand...
Click to collapse
Phone has been plugged in the charger for awhile now...nothing.
AJ Newkirk said:
You may want to try a jig, if you haven't updated the bootloaders.
Were you switching between these using nandroid backups?
Click to expand...
Click to collapse
I only used a nandroid backup for restoring back to the stock rom. For everything else, I used CWM and a zip install.
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
AJ Newkirk said:
I'd try pulling the battery and leaving it out for 10-15 mins.
I find it hard to believe that you would brick your phone using a known good .zip file in CWM.
The bootloaders should be intact - so it should be recoverable.
Something else is at play here. Either it is hard locked-up or you have a hardware issue.
Click to expand...
Click to collapse
That's what I thought. Like I said, it started the flash but then look like it hung. The progress bar did not move at all. After a bit the phone turned off. What is hard locked-up? I do remember when I first plugged the charger in after the phone died/suspended it did vibrate.
creepyncrawly said:
I'd also suspect battery or hardware.
Try to get into download mode with the battery out. Use the same sequence, vol+ and vol- then plug in the usb cable. The usb will supply the power. If it won't go into download mode that way then I would suspect hardware rather than battery.
Click to expand...
Click to collapse
Phone is basically new. I tried leaving the battery out and holding down the vol keys and plugging into USB. Screen does nothing.
c0ldburn3r said:
Did you flash ld3 using the one click odin or thru a cwm file?
If a jig doesn't work than the bootloader is most likely corrupted.
10 char this
Click to expand...
Click to collapse
As I posted above I only used Odin from the original rooting. Everything else was CWM.
I guess I need to find out how to make a jig and try that as my only remaining option??
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
w1209 said:
Same thing happened to me earlier today when flashing the latest MIUI V4 from UCLD3 in CWM. It flashed without any errors, but upon hitting reboot the device shut off and would not respond to anything. Tried leaving battery out for an hour, tried USB jig, and several other tricks to try to boot into download. Sent the phone off to Mobile Tech Videos for repair
avus_m3 I think your bootloader is corrupt just like mine.... but how?!?
Click to expand...
Click to collapse
That's not what I want to hear
I just don't understand how this can happen. Even if lets say worse case scenario the rom is screwed, my battery dies during the update or whatever...I should still be able to get into CWM or at least download mode right?
It's very odd indeed considering MIUI doesn't have a bootloader included either, and according to CWM it flashed without any problems. The only other possibility I could think of is that the ROM got corrupted while copying onto the phone. I checked MD5 checksum after downloading onto my computer but not on my phone before flashing. Still, could a corrupt ROM without bootloader hardbrick the phone? I thought the SGS2 was supposed to be very hard to brick when not flashing something like a bootloader
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
If a USB jig doesn't work, I guess call up Samsung and play dumb? Worst thing that will happen is they'll send your phone back to you. Sorry to hear about your bad luck :/
Here's an odd idea... you didn't happen to get water in it, did you?
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
dayv said:
If the boot loaders and param.lfs are intact you should be able to get download mode (as long as there are no hardware problems).
Recovery on the other hand is in the kernel on our phones so if the kernel did not flash properly it could cause recovery not to work.
I have read somewhere a while back where someone had their battery die during a flash and they had to get different battery altogether to get the phones to power back on - don't know if that is the case here. It was as though their battery would not charge in their phone after it died during the flash. But if you guys know someone close to you that have the same phone I would try their battery just to see. There could be some other hardware malfunction also.
I don't know if cwm recovery touches any of the boot loaders or the param.lfs in the nandroid backup/restore process. As far as flashing a cwm zip one needs to check the zip to make sure the zip dies not contain boot loaders or param.lfs - as long as the zip being flashed does not contain those then it should be pretty safe to flash.
Sent from my SGH-I777 using XDA Premium HD app
Click to expand...
Click to collapse
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
nakedninja42 said:
I hard brick too! I can't get jig to work at all and can't connect to download mode. I was at ~40% battery and flashed AOKP coming from ld3. I hit reboot in recovery and the screen went black.
If I can't get it working tonight I going to AT&T in the morning
---------- Post added at 11:19 PM ---------- Previous post was at 11:16 PM ----------
Using the odin one-click I tried to flash using Mobile ODIN, it only flashed the param.lfs (this was before the helpful instructions from entropy on how to extract properly). Don't know if that has any effect on my problem.
Click to expand...
Click to collapse
Not sure, but if your param.lfs got corrupted that could be your problem.
Sent from my SGH-I777 using XDA Premium HD app
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Yes....coincidence. I have flashed form UCLD3 to AOKP (and CM9) & back more than a few times without issue.
@avus_m3, w1209, and nakedninja42:
With three similar hard bricks, there is a patern. We should gather as much information as possible. What package did you use to put UCLD3 on the phone immediately before the bad flash? Also, exactly what parts did the AOKP or MIUI package that resulted in the bad flash contain?
I used the latest version posted in the thread (I think there is only one LD3 package?): hxxp://goo.im/devs/task650/SGH-I777/Task650_I777_UCLD3_signed.zip
(not allowed to post links yet)
Same for MIUI: hxxp://goo.im/devs/ktoonsez/downloads/miuiandroid_I777-2.4.13b.zip
(not allowed to post links yet)
I know for sure that the MIUI MD5 checksum matched after downloading to my computer. Will see what the MD5 checksum is of the file on my phone after I get it back from MTV. If it is the same there is a definite pattern. If not it was just bad luck and my fault for not verifying it on phone before flashing
w1209 said:
Same exact thing happened to me as dayv, except I was flashing to MIUI. Coincidence between the three of us that we were flashing FROM LD3 or not? Sorry to hear about your phone as well. Lesson learned is to wait for other to flash before you?
Click to expand...
Click to collapse
Just to be clear this did not happen to me directly - just responded as I remember reading somewhere about a battery dying during a flash and that person needing to get another battery to get their phone back to life - again the battery may not have anything to do with what happened hear.
But it does look like this happened to two people after flashing away from ld3 leak - though it just may be coincidental hardware issues. we will see if there are more people who have trouble after flashing the leak.
Sent from my SGH-I777 using XDA Premium HD app
So i purchased an atrix 4g off of eBay, and it has a few Root applications on it, but isn't actually rooted.
The android recovery mode is also broken, i get an android robot with the Attention symbol. Would post a link to one i found on the internet but i cannot since i am under 8 posts.
The phone was on 2.3.6 build # 4.5.141 when i received it. and i have done nothing to it so far.
So maybe someone applied OTA updates and killed the root or something, idk.
in the end the end i would like to root it with some ISC.
So is there anyway i can Reset everything to stock out of the box. Or to fix the problems with recovery?
Also for now it wont really be used as a phone, as i don't have a sim yet.
To cover the basics here let's make sure the phone isn't bootloader unlocked or rooted. To check bootloader, when you boot the phone, does the moto screen say "Unlocked" in top left hand corner of the screen? If not, it isn't. Then for root, check it with the app root checker basic or pro from market. Get back to the thread once you can answer those questions and then I will post something to help you with the getting ics.
Sent from my Atrix with XDA Premium
Both of those come up as a no So no unlocked boot loader and no root
Try this but you know the risks of messing with the phone right??? Read EVERYTHING before you do. Your phone says a different version of firmware than the thread but if you look back in the posts of the thread in the end, it will work. You can also read the Atrix thread stickies.
Edit.... having trouble posting link ... give me sec.
Edit 2....can't post from phone. Let me post it from my computer when I get to the computer in the morning.
Sent from my Atrix with XDA Premium
Is this the link you wanted to post?
http://forum.xda-developers.com/showthread.php?t=1182871
If so i cant go through with it because my "Android Recovery" menu is broken.
Ahh now i see, i was selecting the wrong option stupid me
Ok now i have my bootloader unlocked CMW installed, wouldn't boot into android just sat there on M dual core screen for a long time. Ok tries to install another rom
MIUI but that has the same problem gets stuck at That Screen, i can still get into recovery, and everything.
Now what?
dfanz0r said:
Ok now i have my bootloader unlocked CMW installed, wouldn't boot into android just sat there on M dual core screen for a long time. Ok tries to install another rom
MIUI but that has the same problem gets stuck at That Screen, i can still get into recovery, and everything.
Now what?
Click to expand...
Click to collapse
Did you wipe before installing?
Sent from my MB860 running Jokersax's CM9
Yes i wiped
dfanz0r said:
Yes i wiped
Click to expand...
Click to collapse
Try cm9. Here's the order you should do it in:
1. Full wipe
2. Flash 0.6
3. Flash 0.6 again
4. Flash gapps
Sent from my MB860 running Jokersax's CM9
dfanz0r said:
Is this the link you wanted to post?
http://forum.xda-developers.com/showthread.php?t=1182871
If so i cant go through with it because my "Android Recovery" menu is broken.
Ahh now i see, i was selecting the wrong option stupid me
Click to expand...
Click to collapse
Yup that was it.
Glad you found it.
Sent from my Atrix with XDA Premium
giqbal said:
Try cm9. Here's the order you should do it in:
1. Full wipe
2. Flash 0.6
3. Flash 0.6 again
4. Flash gapps
Sent from my MB860 running Jokersax's CM9
Click to expand...
Click to collapse
This doesn't work either same result
Does anyone else have any ideas?
dfanz0r said:
Does anyone else have any ideas?
Click to expand...
Click to collapse
Have you flashed a different ROM for the time being to at least have a working phone? Like a blur or cm7 ROM?
Sent from my Atrix with XDA Premium
Thats is what i was going to try next, i havent got to it today.
Are you flashing plugged in? Try flashing the rom without having your phone plugged in.
Also, if you're at the M logo screen, I suggest waiting it out for quite a while. Be patient. I used to think when I flashed roms that I was stuck at M logo, but I just wasn't waiting long enough, especially coming from a full wipe.
Otherwise, try doing a battery pull and then putting it back in and booting it up.
You can also try using Nottachtrix with the installer? I've heard that fixes a lot of people's problems that are getting stuck at logo screen.
well right now it seems that the battery is dead and wont charge....
So im not sure what im gonna do about that
Ok so im installing NottachTrix now will report how it went when done.
Also about leaving it on to boot, i did that for 24 hours, nothing happened
Edit:
It seems to be working so far. The phone is stuck at a charging screen with a battery icon, much more than it was before.
dfanz0r said:
Ok so im installing NottachTrix now will report how it went when done.
Also about leaving it on to boot, i did that for 24 hours, nothing happened
Edit:
It seems to be working so far. The phone is stuck at a charging screen with a battery icon, much more than it was before.
Click to expand...
Click to collapse
Wipe cache partition, wipe data, wipe delvik. Install Rom (cm7). Reboot recovery. Install gapps. Reboot now. If it's not working perhaps you cwm is outdated?
Sent from my MB860 using xda premium
NottachTrix works fine so far, my battery just needed to charge some.
After flashing nocturnal Rom and installing apps i experienced a slight overheating and i turned off my phone. I turned it back on and I was unable to access the Rom, recovery, or boot loader. I flashed stock with LGPNST and i re-rooted and unlocked the bootloader. I had the same problem upon rebooting. SO...I can flash through LGPNST stock and root but every time i try the boot loader unlock and reboot my phone has the original problems . I've tried the process a few times with the same results.please help.
Dr0!dFreek said:
After flashing nocturnal Rom and installing apps i experienced a slight overheating and i turned off my phone. I turned it back on and I was unable to access the Rom, recovery, or boot loader. I flashed stock with LGPNST and i re-rooted and unlocked the bootloader. I had the same problem upon rebooting. SO...I can flash through LGPNST stock and root but every time i try the boot loader unlock and reboot my phone has the original problems . I've tried the process a few times with the same results.please help.
Click to expand...
Click to collapse
Nevermind that i got it working
Dr0!dFreek said:
Nevermind that i got it working
Click to expand...
Click to collapse
It may be helpful to someone else, if you were to explain how you fixed it.
Yes, it would indeed be quite helpful if you could elaborate... because this just happened to me and I'm stumped...
I followed the same exact procedure I've used other times without error...
Except that now, after LGNPST, then root, then freegee... go to restart the phone and it hangs... won't boot up. What gives?
I repeated the process and did a factory reset after LGNPST back to stock, since I noticed (oddly enough) that all my apps were still there after LGNPST (full, to 100%)...
Still no luck...
EDIT-- Can't for the life of me figure this effing thing out. LGNPSTed I don't know how many times... with factory reset, without... I've tried fully relocking and unrooting the device... both through the FreeGee app *and* manually through adb... no error mssgs, double-checked... everything followed to the letter. There's only one constant each time: Once I've re-unlocked the bootloader (either with the app or through adb)... the phone is basically softbricked... once I turn the power off, it is A) not possible to boot into the stock rom, B) not possible to access fastboot menu, and C) not possible to boot into recovery. The only thing it *is* possible to do is get into download mode... and from there I'd just have to LGNPST again, but what's the point, because once I've done that and tried to unlock again, I already know what's coming. Never been this frustrated with a phone before, any help would be greatly appreciated.
EDIT 2-- No luck. LGNPSTed to stock once more, and factory reset, because yet again, all my apps were still intact... idk. Anyways, decided to do some hunting around with adb, and "adb reboot recovery" produced an error screen... the android lying on his back with case open... am I to assume this means there is a problem with my recovery partition that could be causing my difficulties... or would one expect to see this screen when trying to access recovery on the stock phone?
adfurgerson said:
It may be helpful to someone else, if you were to explain how you fixed it.
Click to expand...
Click to collapse
Honestly I don't know how it was resolved. I lgpnsted and rooted and unlocked the bootloader like 5 times.I got into recovery a few times but then got the same problem two more times. The last time I got into recovery I managed to flash a custom kernel and everything was fine from then on. I just don't understand how this problem is caused or even how it is truly fixed.
Sent from my LG-E970 using xda premium
dht2005 said:
Yes, it would indeed be quite helpful if you could elaborate... because this just happened to me and I'm stumped...
I followed the same exact procedure I've used other times without error...
Except that now, after LGNPST, then root, then freegee... go to restart the phone and it hangs... won't boot up. What gives?
I repeated the process and did a factory reset after LGNPST back to stock, since I noticed (oddly enough) that all my apps were still there after LGNPST (full, to 100%)...
Still no luck...
EDIT-- Can't for the life of me figure this effing thing out. LGNPSTed I don't know how many times... with factory reset, without... I've tried fully relocking and unrooting the device... both through the FreeGee app *and* manually through adb... no error mssgs, double-checked... everything followed to the letter. There's only one constant each time: Once I've re-unlocked the bootloader (either with the app or through adb)... the phone is basically softbricked... once I turn the power off, it is A) not possible to boot into the stock rom, B) not possible to access fastboot menu, and C) not possible to boot into recovery. The only thing it *is* possible to do is get into download mode... and from there I'd just have to LGNPST again, but what's the point, because once I've done that and tried to unlock again, I already know what's coming. Never been this frustrated with a phone before, any help would be greatly appreciated.
EDIT 2-- No luck. LGNPSTed to stock once more, and factory reset, because yet again, all my apps were still intact... idk. Anyways, decided to do some hunting around with adb, and "adb reboot recovery" produced an error screen... the android lying on his back with case open... am I to assume this means there is a problem with my recovery partition that could be causing my difficulties... or would one expect to see this screen when trying to access recovery on the stock phone?
Click to expand...
Click to collapse
I had access to stock and I could root it. One thing that bothers me is that when I flash with lgpnst my data isn't erased and I feel like there may be a problem there of whether lgpnst is even taking our phones back to stock completely
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
I had access to stock and I could root it. One thing that bothers me is that when I flash with lgpnst my data isn't erased and I feel like there may be a problem there of whether lgpnst is even taking our phones back to stock completely
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
dht2005 said:
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
Click to expand...
Click to collapse
Sorry I wish I could help but I don't know that much.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
Sorry I wish I could help but I don't know that much.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
It's okay, I posted in XsMagical's thread, I'm hoping he can shed some light.
But actually, I'm just glad that I'm not the only one this has happened to...because if this error is reproducible, it can probably be fixed... so that's good. Thanks for your replies!
dht2005 said:
Yes, I know, I've had that same thought. I think I've done what you did... LGNPSTing and unlocking etc... but even as I try like hell, I haven't been able to get back into recovery even once.
Click to expand...
Click to collapse
There have been a small number of phones that will not unlock with standard freegee. They can be unlocked but it is riskier, you would need to talk to Shelnutt in irc.
http://webchat.freenode.net/?channels=lg-optimus-g
adfurgerson said:
There have been a small number of phones that will not unlock with standard freegee. They can be unlocked but it is riskier, you would need to talk to Shelnutt in irc.
http://webchat.freenode.net/?channels=lg-optimus-g
Click to expand...
Click to collapse
Our phones successfully unlocked with freegee originally but some error caused us to lose access to the bootloader and corrupt whatever ROM we were on and then cause errors where we could use free gee but run into problems. In my situation the problem was resolved somehow and free gee worked fine afterwards
Sent from my LG-E970 using xda premium
I'll try and post how I fixed it, but it is recovery related. I'm also working on another way to reset our phones without using LGNPST, but I've been really busy. I'm close though and I believe it will be easier and faster.
Sent from my LG-E970 using Tapatalk 2
I'm still at work but I read most of the post and will try to see if there is a work around
Stroked from my Dirty Nocturnal'd Optimus G
droidiac13 said:
I'll try and post how I fixed it, but it is recovery related. I'm also working on another way to reset our phones without using LGNPST, but I've been really busy. I'm close though and I believe it will be easier and faster.
Sent from my LG-E970 using Tapatalk 2
Click to expand...
Click to collapse
XsMagical said:
I'm still at work but I read most of the post and will try to see if there is a work around
Stroked from my Dirty Nocturnal'd Optimus G
Click to expand...
Click to collapse
Thank you guys! I'm willing to try anything at this point. I appreciate it. And droidiac... this phone could really use a quick, easy, and reliable way to completely reset back to 100% stock, so that sounds exciting!
dht2005 said:
Thank you guys! I'm willing to try anything at this point. I appreciate it. And droidiac... this phone could really use a quick, easy, and reliable way to completely reset back to 100% stock, so that sounds exciting!
Click to expand...
Click to collapse
I just picked up a new laptop today so it's going to be a while unless it goes well.
Sent from my LG-E970 using Tapatalk 2
Just for the sake of documentation, I made a little log of my most recent attempt at getting back into the fastboot menu... obviously it's convoluted, but hey... sometimes experimentation gets results. This time, however, it did not... still no luck.
LGNPST back to stock
factory reset from settings->backups
run root exploit
restore original backups from first time freegeeing via adb using carrett's method
reboot
full unroot from SU app
factory reset
LGNPST to stock
re-run root exploit
reboot
re-unlock with freegee script (adb)
disconnect cable
reboot
(right here is the failure. after running "power off and reboot" from the power button menu, phone shuts off. it tries to start up, then i get a quick flash of the LG logo, straight to a backlit black screen that hangs indefinitely. only thing possible from here is to enter download mode.)
Back to the drawing board...
Same here
dht2005 said:
Just for the sake of documentation, I made a little log of my most recent attempt at getting back into the fastboot menu... obviously it's convoluted, but hey... sometimes experimentation gets results. This time, however, it did not... still no luck.
LGNPST back to stock
factory reset from settings->backups
run root exploit
restore original backups from first time freegeeing via adb using carrett's method
reboot
full unroot from SU app
factory reset
LGNPST to stock
re-run root exploit
reboot
re-unlock with freegee script (adb)
disconnect cable
reboot
(right here is the failure. after running "power off and reboot" from the power button menu, phone shuts off. it tries to start up, then i get a quick flash of the LG logo, straight to a backlit black screen that hangs indefinitely. only thing possible from here is to enter download mode.)
Back to the drawing board...
Click to expand...
Click to collapse
Just for documentation and in case I can help solving this, I am having the same problem, I explain my case with more detail on the FreeGree Thread, but pretty much I am on the same ship as you, I have tried after LGNPST, with and without factory reset, with the Google Play application and with the desktop application, but same result, black screen after restart.
I have a brand new phone, picked it less than a week ago, could LG have changed something? bootloader/recovery partition sizes? something?
I am still within the 14 days period and as much as I like the phone, if I can't bootloader unlock, means I will be stuck on stock ROM, and that is something I don't want... might as well go and change it for a different phone, or sell it and get a nexus 4...
I get same.thing. black screen after freegee. Its two days old. So now what!?
Sent from my LG-E970 using xda premium
Its a known issue. IRC guys can help. Something about the misc.IMG file getting corrupted
Sent from my Nexus 7 using xda app-developers app
nygfan760 said:
Its a known issue. IRC guys can help. Something about the misc.IMG file getting corrupted
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
How does this happen from a random stock ROM. I think I was using nocturnals ROM and how was the problem resolved through multiple flashes?
Sent from my LG-E970 using xda premium
Hello everyone, Forgive me if I seem a bit flustered, but I am. I was adding a few fonts with an app from the play store. It would restart after each fine, and there was no issue. On the final one, it restarted, but then got hung up for 10 minutes on the ATT logo. I have restarted it with the power button numerous times now, and it has done nothing different. I have only rooted the phone, I have no custom recovery or anything. I booted into the LG stock recovery, canceled the reset, and it still hung up at the ATT logo.
What might have happened, and how can I fix this? I would rather not hard reset, but if I have to, I have to. Please respond with anything at all that might help me. I'm using my old GSII right now, and the newer sim doesn't fit quite right in it. I can make calls and stuff, but i want to get back on the OG as fast as possible. PLEASE respond with anything helpful. Thanks.
I am running stock Jellybean (The initial jellybean we got, I think it was 4.1.1), rooted. No custom roms, no custom recovery.
UPDATE: I did a factory reset (by holding power and volume down). It is still doing the same thing. It gets to the ATT logo and plays the music "Dee dee dee dee 'click'", then stops. Nothing more happens. At all. I've let it sit for a while and nothing is happening. So now the question is, how can I save it with that in mind?
chrisphoenix7 said:
UPDATE: I did a factory reset (by holding power and volume down). It is still doing the same thing. It gets to the ATT logo and plays the music "Dee dee dee dee 'click'", then stops. Nothing more happens. At all. I've let it sit for a while and nothing is happening. So now the question is, how can I save it with that in mind?
Click to expand...
Click to collapse
Sound like you need to use LGNPST or use a teenybin then flash a custom ROM. Factory reseting ( I think) only clears out the /data partition which is where all user and app data is saved. If something in the /system partition is not allowing it to boot, that is why the factory reset didn't work. To fix you have to restore the /system partition back to stock.
To do so, flash a full bin. Which will reset the phone to complete stock (no root, no unlocked bootloader).
Or you can flash a teenybin. Which is smaller and safer. Flashing a teenybin unlocks the bootloader and puts a custom recovery. From there you can just flash a new ROM.
Joecascio2000 said:
Sound like you need to use LGNPST or use a teenybin then flash a custom ROM. Factory reseting ( I think) only clears out the /data partition which is where all user and app data is saved. If something in the /system partition is not allowing it to boot, that is why the factory reset didn't work. To fix you have to restore the /system partition back to stock.
To do so, flash a full bin. Which will reset the phone to complete stock (no root, no unlocked bootloader).
Or you can flash a teenybin. Which is smaller and safer. Flashing a teenybin unlocks the bootloader and puts a custom recovery. From there you can just flash a new ROM.
Click to expand...
Click to collapse
Thanks. Do you know if there's an accurate guide on how to do the teenybin? It's been ages since I've done anything more than root, and I'm not sure what to search for.
chrisphoenix7 said:
Thanks. Do you know if there's an accurate guide on how to do the teenybin? It's been ages since I've done anything more than root, and I'm not sure what to search for.
Click to expand...
Click to collapse
The directions to use the Teenybin are in the OP found here: http://forum.xda-developers.com/showthread.php?t=2230994
The hardest part is getting LGNPST working properly. But that's easy now thanks to the auto install.
Did u fix your phone?
Going to assume teeney bin worked for op. It did for me when I had issues
Sent from my LG-E970
Apologies all, yes I got it working... Mostly. WiFi quit working completely (refused to connect), phone calls took forever to go through, and other odd issues. I'm running it off an old backup of ICS on my external SD. The issues were too much for me to handle, and I was scared to do anything more, so I've got a Moto x. I'm going to try to correctly fix the OG now, so hopefully by documenting the process I can help someone else.
Sent from my XT1058 using xda app-developers app
chrisphoenix7 said:
Apologies all, yes I got it working... Mostly. WiFi quit working completely (refused to connect), phone calls took forever to go through, and other odd issues. I'm running it off an old backup of ICS on my external SD. The issues were too much for me to handle, and I was scared to do anything more, so I've got a Moto x. I'm going to try to correctly fix the OG now, so hopefully by documenting the process I can help someone else.
Sent from my XT1058 using xda app-developers app
Click to expand...
Click to collapse
i was scared to use teenybin like you but 4.4 lured me into trying. Give teenybin a try its not that bad. you just need to install it, download the teenybin, launch the program, boot your phone into download mode and run the program with the dll and bin files selected.
optimusv45 said:
i was scared to use teenybin like you but 4.4 lured me into trying. Give teenybin a try its not that bad. you just need to install it, download the teenybin, launch the program, boot your phone into download mode and run the program with the dll and bin files selected.
Click to expand...
Click to collapse
I used the Teenybin. It worked enough so I could install my backup. The OS got wiped completely, so I think the kernel just couldn't handle all the stuff it had to anymore.
Sent from my XT1058 using xda app-developers app
I used LGNPST to make full recovery and i dont have any problems with this software.. if want help just ask me.. i will guide you..