[Q] Baseband Issues - Verizon LG G2

First and foremost, let me say that I messed up.
Now that that's out of the way, let me begin;
I have a VS980 (obviously) with Cyanogenmod 11 running the latest nightly (6-26 I believe, running 4.4.4), and as many know the Verizon version has had issues with any rom with rotation issues. So I decided to search around and try and find a fix for this, and the most likely fix seemed to be flashing a KK baseband. I know before that my device was 12B or whatnot.
Well, now I'm in a bootloop, and have no clue what to do next.
Ive tried restoring from a nandroid backup and straight up reflashing the ROM.
I have TWRP 2.7.0.0 installed, but my United drivers wont recognize my G2 when in recovery (even though the computer sees it as "VS980" in devices), and I just downloaded and started up the SDK, but haven't downloaded anything other than that.
What I think might work is pushing the correct baseband to the phone, but I have no idea how to do so. I know basic ADB from a past experience, but very very basic.
I need some direction as what to do is what I'm saying. Any and all help is much appreciated, thank you so much!

Chirzu said:
First and foremost, let me say that I messed up.
Now that that's out of the way, let me begin;
I have a VS980 (obviously) with Cyanogenmod 11 running the latest nightly (6-26 I believe, running 4.4.4), and as many know the Verizon version has had issues with any rom with rotation issues. So I decided to search around and try and find a fix for this, and the most likely fix seemed to be flashing a KK baseband. I know before that my device was 12B or whatnot.
Well, now I'm in a bootloop, and have no clue what to do next.
Ive tried restoring from a nandroid backup and straight up reflashing the ROM.
I have TWRP 2.7.0.0 installed, but my United drivers wont recognize my G2 when in recovery (even though the computer sees it as "VS980" in devices), and I just downloaded and started up the SDK, but haven't downloaded anything other than that.
What I think might work is pushing the correct baseband to the phone, but I have no idea how to do so. I know basic ADB from a past experience, but very very basic.
I need some direction as what to do is what I'm saying. Any and all help is much appreciated, thank you so much!
Click to expand...
Click to collapse
If you can get it in download mode, restore it back to stock using the guide in the General section..

Doesnt download mode require it to actually boot? Im bootlooping.
Sent from my SCH-I510 using XDA Free mobile app

Chirzu said:
Doesnt download mode require it to actually boot? Im bootlooping.
Sent from my SCH-I510 using XDA Free mobile app
Click to expand...
Click to collapse
You should still be able to get into recovery, it's just getting the timing right. Recovery has it's own kernel.
Try holding down power for 15 or so seconds til it restarts, immediately hit the volume down and power, let go when the LG splash screen comes up and hit them both again.
You'll get the factory hard reset screen, keep hitting power til it gets you to Recovery.

CM11 nightlies are still based on JB kernel source, so you need the 12B radio for it to boot. That's why you're bootlooping. So if you have a 12B radio on your SD, you can flash that. Then clean flash your current build of CM11. Should boot up then. If I was you I'd think about updating to 24A, and use one of the ROMs that use KK kernel source. There's a CM11 for 24A build out. Not in nightlies but pretty frequent builds.

mjones73 said:
You should still be able to get into recovery, it's just getting the timing right. Recovery has it's own kernel.
Try holding down power for 15 or so seconds til it restarts, immediately hit the volume down and power, let go when the LG splash screen comes up and hit them both again.
You'll get the factory hard reset screen, keep hitting power til it gets you to Recovery.
Click to expand...
Click to collapse
Its not Recovery that I have an issue getting into, its download mode. I have no problem getting into there, however, I have no idea about anything regarding download mode.
JRJ442 said:
CM11 nightlies are still based on JB kernel source, so you need the 12B radio for it to boot. That's why you're bootlooping. So if you have a 12B radio on your SD, you can flash that. Then clean flash your current build of CM11. Should boot up then. If I was you I'd think about updating to 24A, and use one of the ROMs that use KK kernel source. There's a CM11 for 24A build out. Not in nightlies but pretty frequent builds.
Click to expand...
Click to collapse
I dont think I do, but do you know how I can get my drivers to work or where I can pull drivers from for my laptop to recognized my phone so I can push a radio to it?
Will definitely think about KK in the future, thank you.
Sent from my SCH-I510 using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?t=2448960 I got mine from this thread. I've had issues too some. Sometimes I've actually had to install them a couple times with the phone plugged into my laptop to get them to work

Thanks man, Ill definitely try that out when I get to my computer.
Sent from my SCH-I510 using XDA Free mobile app

JRJ442 said:
http://forum.xda-developers.com/showthread.php?t=2448960 I got mine from this thread. I've had issues too some. Sometimes I've actually had to install them a couple times with the phone plugged into my laptop to get them to work
Click to expand...
Click to collapse
Update: The drivers honestly didn't matter in the end I think, as I tried it with 3/4 of them successfully installing (The CDC one never installed correctly) and everything went perfectly!
Thank you so much for pointing me in the right direction.
Sent from my kickass VS980

Related

[Q] Actually can't flash back to stock using Odin or otherwise

I've tried using both Odin methods, even using sdk tools, through command prompt with adb. Nothing is working. My Captivate gets to the download screen, and that's as far as it gets. I've watched numerous videos about this, and haven't come across this problem before.
I'm not an idiot, i've flashed a few roms before, but i'm using phoenix 6.0 with a basic speedmod kernel, no under/over clocking.
Can someone please help me with this, it's extremely frustrating. Thank you
wow
wow, ok, now I still can't get back to stock with odin, nor can I get back the first boot screen past the AT&T World Phone screen
Are you either able to do download with the Vol Up & Down and insert USB and have ODIN recognize?
More details, how did you get here, what have you tried?
Sent from my Captivate using XDA Premium App
mcord11758 said:
More details, how did you get here, what have you tried?
Sent from my Captivate using XDA Premium App
Click to expand...
Click to collapse
I dont mind helping... easier way is IM tho.... google talk.... i'll IM my gmail....
lovethegame0204 said:
I've tried using both Odin methods, even using sdk tools, through command prompt with adb. Nothing is working. My Captivate gets to the download screen, and that's as far as it gets. I've watched numerous videos about this, and haven't come across this problem before.
I'm not an idiot, i've flashed a few roms before, but i'm using phoenix 6.0 with a basic speedmod kernel, no under/over clocking.
Can someone please help me with this, it's extremely frustrating. Thank you
Click to expand...
Click to collapse
When I first decided to flash to stock using Odin I had all kinds of issues. Everything from nothing happening to it only flashing halfway through. My problem turned out to be the cable. I was using a cheap microUSB cable at work. When I got home, I used the original cable that came with the device and had no issues.
Things you can try;
- Using a different microUSB cable
- Making sure you have the samsung drivers installed. If they are, uninstall and reinstall
- Try different USB ports with the microUSB cable. Some people say they had problems using the front ports while others the back ports. Worth a shot
- Try using a different version of Odin either newer or older
- If you have access to another PC, try flashing from there as well
Hope this helps
i've tried using both odins, the 3 click, and the one click. I've gone in with "AIO Captivate Toolbox" and also through the command prompt with adb.exe. It starts flashing and puts my phone into download mode, where Odin has it recognized, then it gets removed, but it never comes back like its supposed to.
for b naughty my google name is [email protected]
B-Naughty said:
Are you either able to do download with the Vol Up & Down and insert USB and have ODIN recognize?
Click to expand...
Click to collapse
I can get into download mode, but after that, odin stops recognizing my phone, and it never comes back to odin. I just have to unplug and reboot it.
ok guys, a couple people said re install the drivers, and that worked. Thank you very much, you saved me from owning a brick. Apparently it didn't install them properly the first time. Thank you to those that helped, I really appreciate it, truly. This is a great site, and the devs, and other members are awesome
lovethegame0204 said:
ok guys, a couple people said re install the drivers, and that worked. Thank you very much, you saved me from owning a brick. Apparently it didn't install them properly the first time. Thank you to those that helped, I really appreciate it, truly. This is a great site, and the devs, and other members are awesome
Click to expand...
Click to collapse
I too am having huge driver issues... I uninstalled the ones that work perfectly, and installed the ones in the aio tool... now huge driver issues... took me an hour to go to stock and load another rom... fixin to load cyanogen so gotta use the nexus s drivers... hopefully those will work better...
lovethegame0204 said:
I can get into download mode, but after that, odin stops recognizing my phone, and it never comes back to odin. I just have to unplug and reboot it.
Click to expand...
Click to collapse
Make sure Odin is up and running prior to going into download mode.
Will not fully reboot after flash back to stock ROM
Just flashed back to stock Rogers with Odin. Everything went OK untill reboot. It gets stuck at the ROGERS screen, then just shuts off!! and ideas?

[Q] Seriously? Why does my new captivate constantly brick?

Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device

Every ROM I flash gets stuck on the flash screen. Thoughts?

I just bought a used Hero as a temporary phone and I'm trying to get off the stock rom. I rooted the phone and flashed a MIUI rom. It got stuck on the splash screen during boot. Not feeling like dealing with it, I just ended up RUUing it. Then I rerooted it and tried another rom...same deal. Now I back to stock again. Any thoughts on how to fix this?
Thanks
You didn't firate anything, did you?
Try manualy flashing the boot.img in the rom from fastboot. Sometimes thats the problem.
Regards
Sent from my Galaxy Nexus using XDA
oohaylima said:
You didn't firate anything, did you?
Click to expand...
Click to collapse
Urban dictionary tells me that means fake pirating...? If that's the case, no. I haven't even installed anything let alone log into my google account.
EDIT: I'm guessing you meant firerat. Nope, I haven't messed with anything.
flakesdk said:
Try manualy flashing the boot.img in the rom from fastboot. Sometimes thats the problem.
Regards
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Good idea. I'd need abd for that though to run the commands right? I'm really trying hard to avoid installing it on my computer.
Why ?? If your going to be modding your phone s-off,eng-bootloader & adb are all tools you will definitely need. If not then you may have a few headaches down the line if something goes wrong.
#Root-Hack_Mod*Always\
laie1472 said:
Why ?? If your going to be modding your phone s-off,eng-bootloader & adb are all tools you will definitely need. If not then you may have a few headaches down the line if something goes wrong.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
I won't be doing anything beyond flashing a custom rom.
I just dug up my Hero. It had CM6 previously. I tried flashing an updated ROM and it does not get past the HTC logo. I tried 4 different ROMs. Using CMW recovery. Wipe/Format all...and nothing.
Yeah I'm completely out of ideas. I may just have to suck it up and install adb.
Which version of CWM are you running? I've used 2.5.0.1 for all of my ROMs and never had a problem. I should have the zip to flash through recovery and the HERCIMG flashable through HBOOT if you wanna try.
Sent from my PC36100 using xda premium
Adb is a breeze to install. Takes less than 20 min. Pm me if and when you wanna set it up, and believe me when I say you will not regret it. Adb makes modding your phone a little easier.
#Root-Hack_Mod*Always\
scl23enn4m3 said:
Yeah I'm completely out of ideas. I may just have to suck it up and install adb.
Click to expand...
Click to collapse
What radio do you have? I remember people having issues when using the older radio (.27) instead of the newer (.29). Then again, it might not make a difference at all either. Just a thought.
i second drunkpilots radio idea, thats what gave me a headache for an hour the other night wondering why my cm7 wouldnt boot, updated to newest sprint radio and bam booted right up
Alright I just upgraded my radio. What's the best/easiest way to root it from here since I'm back to stock now?

Unable to get into Recovery after 4.1.2 upgrade...

Ok, so I ran into a VERY weird issue and was wondering if anyone else has experienced this or has a better solution then what I found.
My Nexus7 was running stock JRO03D. I had it rooted, using the Motley kernel with CWM Recovery - but outside of that, everything else was pretty stock. Anyway, I decided to upgrade to the 4.1.2 image. I pulled the one it downloaded automatically out of /cache and looked at the updater-script to see what it did. I noticed it replaced a lot, including the boot image, so I figured it would be better just to let it do everything and revert my custom stuff later. So I replaced the kernel with the stock JRO03D kernel and, using CWM, flashed the upgrade. Everything seemed to go perfect and it completed the upgrade. Prior to rebooting it, I also flashed the "unofficial" motley 4.1.2 kernel posted on XDA. I rebooted the device, and CWM warned me that 'su' needed to be fixed (how nice!) and made it suid again. It rebooted and after android "updated", everything was up and running. I confirmed in settings that it was on 4.1.2 with the custom kernel. SU was suid root as well. Perfect!
Not quite.
I decided to try rebooting into recovery to make sure CWM was still there, or flash it back if it wasn't. I opened up a terminal emulator, removed the new recovery-recovery image in /system, and did "reboot recovery". The Nexus7 rebooted, but rebooted right back into normal operation. Very weird. So I hooked it up to my computer, figuring CWM was gone, and tried to fastboot flash it back. Fastboot said it did, but I still wasn't able to reboot into recovery. I tried three different versions of CWM and even TWRP, but no dice. Every time I tried rebooting into recovery (using terminal emulator, adb shell or bootloader method) it just went right back into the normal boot process.
I spoke to some people on IRC who recommended reflashing the stock image from Google (without wiping user data). I reflashed the bootloader and then did a fastboot update <stock image>, and it said it replaced boot, recovery, system, etc. It rebooted automatically, and I tried going into stock recovery. That still did NOT work. Instead, I got a very sick looking android guy who was lying down with a red triangle with an exclamation point over him. I was a bit worried and upset at this point. I tried reflashing CWM/TWRP again, but nothing. When I did this, I no longer got the unhappy android image, but it just booted up normally.
I decided to try and doing a more thorough wipe, using fastboot to wipe cache/boot/recovery/system manually. Then I reflashed the bootloader and stock image. Still no recovery (stock or custom).
As you can imagine, I was getting even more concerned now. Especially since I was no without root and no way to get it back (since I couldn't get into recovery to flash the zip for it).
I tried every other thing I could think of to flash recovery back, but nothing worked. It wouldn't load at all.
Finally, I was about to do a complete factory reset and wipe/reflash of everything, but one last thought crossed my mind. I found the older (JRO03D) bootloader and flashed that. Reloaded bootloader and selected "Recovery". Voila, I was in TWRP Recovery Mode! (which was the last one I tried installing). I was able to reinstall my SU.zip and get everything back up and running.
SO, long story short, I'm now on 4.1.2, running the newer unofficial motley kernel and have su back. But I'm also stuck on the older 3.34 bootloader. If I try upgrading it back to 3.41, I won't be able to get into recovery.
Has this happened to anyone else? It doesn't seem like it. Is there a HW issue with my device causing this problem? I can't believe it's software related since I tried two different copies of the 3.41 image. Does anyone have any other suggestions on how I can upgrade the bootloader while keeping the ability to get into recovery mode?
Also, while everything *seems* to be working OK using 3.34, do you think it will cause other problems since I'm using 4.1.2?
Thanks.
*MOD EDIT* please don't quote the entire OP
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
MetalWych said:
Thanks for the bootloader info. I was in the same boat, and once I found your post, I went back to JRO03D and my recovery has returned.
Again, thanks, you F'n rule!!!
Click to expand...
Click to collapse
No problem. I'm glad to hear that my solution above helped someone else, and also that I'm not the only one experiencing the problem. I assume you mean you only went back to the JRO03D bootloader and not the whole image, right?
What I'm most concerned about is that it seems like my N7 (and possibly yours as well) is defective. I'm not an uber-expert on Android, but I'm fairly knowledgeable. With a stock system, outside of userdata, that I reflashed multiple times from multiple sources, to have any type of recovery (stock or custom) not work is a bit upsetting. Since it works fine on the older bootloader, it definitely seems to be an issue with that. But since most people do not have the same issue, the only variable I can see being the difference is hardware.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
It looked more like a warning symbol that something went very wrong then a stock recovery screen.
I've gone into stock recovery on other Android devices before, and it looked similar to CWM. There was a menu that allowed you to install "authorized" update.zip files, factory reset the device, etc. There was no menu here, just a very pissed off and sick looking android guy .
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
There's a big thread around here somewhere with people having the same problem as the op. Unfortunately, staying with the 3.34 bootloader is the only 'fix' I've read about. I still can't figure out why some people run into this problem and some don't. I used twrp to flash the update when it became available, and twrp continued to work afterwards.
spongers said:
I believe I am having the same issue. Would you mind linking me to the bootloader which worked for you? Tried searching but couldn't find it. Thanks, and great post!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
It took me a long time to find the old full JRO03D update, since Google only has the latest one on their page. I uploaded the bootloader out of it and you can download it here:
http://core.routed.com/bootloader-grouper-3.34.img
Reboot the Nexus7 into bootloader mode and run:
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
and then you should be able to flash recovery and get into it.
Metallice said:
That android with the red triangle sounds like the stock recovery... so I think you actually got it to work, but you just didn't have a custom recovery...
Then again I don't think I've ever seen the stock recovery. Haha
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
The android with the red triangle does not sound like the stock recovery, it is THE stock recovery.
Under JB 4.1.2 you do not need anymore to connect the N7 to a computer - like it had to be under JB 4.1.1 - to access the bootloader and then the recovery.
Now, pressing volume + power brings the bootloader , the up volume, one press, and then power press put the N7 to recovery. The recovery is the android with the red triangle. To enter in the recovery menu pressing power + volume up brings the menu with the following options:
i) reboot system now,
ii) apply update from ADB,
iii) wipe data/factory reset,
iiii)wipe cache partition.
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
smirkis said:
the fact that you were able to do volume down + power button into bootloader, then select recovery, makes me know its working. and the android guy on his back is the stock recovery... so everything is working fine. you said you flashed motley kernel, it may have something to do with that, and a few other things. you really need to understand how the N7 works, and what it will do if you do not do certain things.
what u should try is, fastboot flash recovery, then fastboot boot recovery
flash a different rom, i prefer Paul's Jr8 as its close to stock with nice little tweaks and see if your issue continues.
at the end of everything, i honestly find this more user error then device related. not everyone understands what the N7 is doing, and why.
Click to expand...
Click to collapse
Smirkis, my initial thought was that something went wrong in the upgrade process, possibly with the kernel like you suggested, so, as I mentioned in the OP, I flashed everything back to stock 4.1.2. I used flashboot to manually erase boot, cache, recovery and system. I then reinstalled the bootloader from Google's update tarball. I then used fastboot to update to image-nakasi-jzo54k.zip. At this point, outside of wiping sdcard, everything was stock 4.1.2.
While I will admit that I didn't realize that the dead-looking android meant stock recovery (and that's good to hear), subsequently flashing a custom recovery (CWM or TWRP) would continually fail to load it. In fact, I couldn't even boot into the recovery manually without flashing it. While using 100% stock, I attempted to flash three different versions of CWM and one version of TWRP. It claimed it updated, but I was not able to get back into recovery - either through bootloader, adb or "reboot recovery".
I know it's easy for people to always jump to the "user error" answer, but I fail to see how that is the case here. Based on your response, I don't think you actually read what I did and just jumped to the wrong conclusion, especially since I already tried your recommendation and much more. I am not running any custom ROM - everything was always stock outside of recovery, root and kernel. If you can explain your reasoning for thinking I did something wrong in all of my numerous attempts to get it working, I would appreciate it since maybe that would provide a solution. While I did attempt to use a custom kernel originally, that obviously isn't the issue if going back to stock didn't fix it.
Additionally, reverting back to the older bootloader magically fixed everything, while all other attempts failed. Subsequently reinstalling the custom kernel didn't break anything either. So if it wasn't the bootloader and something else was broken, I would assume it would be broken in both versions of the bootloader. The fact that this problem is affecting others, granted a small number, and the same solution works for them, leads me to believe that there is either a bug in the bootloader affecting some N7s or some rare HW defect causing a few of us problems.
There is a conversation about the new android update the boot-loader update and A Power management chip on the nexus 7.. It seems this chip is being changed out. The new chip functions the same as they have been using but Its not compatible with the old boot-loader . The above is the reason for the boot-loader change.. Google is aware of the troubles everyone in this thread is having . I would be looking for a new very tiny update in the near days. Just a guess im wondering if the truth is they are gearing up for the 3g version of nexus .maybe the pm chip being changed has a issue with the added radios. They did say ITS NOT A Chip upgrade but will not say why they are making the switch .
sorry i do not have a link . but everyone knows how to get to google groups ..
Happy Reading..
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
smirkis said:
I just got another N7 in the mail today, gonna unlock n root it when i get off work. hopefully i end up in your situation so i can attempt to assist in resolving this. why the old bootloader works for you, and never worked for the rest of the world is beyond me. they updated it for a reason lol, i even called google the first week i got mine in july to tell them about the bootloader and they "said" they would forward that info to the development team. it took almost 3 months for them to fix it.
if the old one works for you, then use the old one. the only difference really is the fact that reboot to recovery thru bootloader actually works. if it works for you, don't upgrade.
mine on the other hand, couldn't get into recovery via bootloader. i was dieing for that upgrade, and when it came i was beyond relieved. i did a RMA this week because my first one had screen lift since the 2nd day i owned it lol, so i'll report back when i get home in an hour or so on my results.
Click to expand...
Click to collapse
Just to clarify, going from bootloader->recovery never worked for me either. Whenever I needed to get into recovery mode, I just opened up a terminal, su'd to root and then ran "reboot recovery", or occasionally doing it via adb. However, those methods always worked for me until I upgraded to the latest bootloader. Then, no custom recoveries would load via any method.
My Nexus7 was first generation. I actually picked it up in Sams Club the day before they were officially released. So if Google made any HW changes in the different revisions, that might explain the difference in results on 4.1.2. Though I imagine most people on XDA also picked theirs up out of the first batch, so I don't think that could be the case. What seems more likely is that there are minor hardware differences that are causing some people's to fail with the 3.41 bootloader, while most don't have that issue. It will be interesting to see if you experience the same issue on your new one though.
gunner1937 said:
Concerning specifically the OTA update for an unlock and root N7 there should be no problem during the process using stock recovery or CWM 6.0.1.0 as long as OTA Rootkeeper is set, before the installation, in order to keep root.
Click to expand...
Click to collapse
It didn't worked for me. I've tried Rootkeeper apk, but it was useless.
This was driving me crazy until I've found this topic! I've tried resetting it to original settings, using rootkeeper and traditional methods, nothing, zero!
At last, phonic saved my life, and finally I a could root my Nexus 7!
I never responded but my RMA worked as it should. but the issue has been resolved with recovery updates from the developers. the rest of the world who had issues should be good to go. I ended up selling my 16gb unit and got a 32 and it works as it should as well. are we all happy campers now?
Sent from my Nexus 7 using xda premium
I've had similar experiences where the way certain kernels install zips are packaged, the wipe custom recoveries at install. In that situation, I've never wiped anything from system, but rebooted into bootloader and fastboot boot recovery "recovery.img". Then from there install the recovery.zip. The worst is when this happens when you get flash happy away from home and the kernel doesn't work. No way to fix without a comp w/SDK. Glad you're back up and running.
(I cannot be held responsible if the aforementioned damages your device; do the research and own the process.)
I am so glad to have found this thread. This problem was beginning to drive me nuts.

Stuck on Android is Upgrading: Starting Applications

I can't seem to find any solution to this. I have flashed 6.16.217 via RSD and ICS Tools. The same thing happens no matter what I do. It hangs on this screen. I'm officially feeling helpless.
strakajagr said:
I can't seem to find any solution to this. I have flashed 6.16.217 via RSD and ICS Tools. The same thing happens no matter what I do. It hangs on this screen. I'm officially feeling helpless.
Click to expand...
Click to collapse
Seriously does anyone know of anything I can possibly do to make this boot again after I flash it? It just hangs on the black screen after the dual core logo, every time. I can't imagine my phone can be bricked when it can still be communicated with, but I simply cannot load android. UGH!!!!!!
Have you tried going in to stock recovery and wiping data and cache?
kwyrt said:
Have you tried going in to stock recovery and wiping data and cache?
Click to expand...
Click to collapse
I have data wiped/factory reset in stock recovery at least 30x. I do it every time before I flash. I had flashed using RSD and using ICS Tools. Both APPEAR to work as they get through, error free. It's only after I boot the phone up for the first time that I either a) get stuck on the black screen after the moto logo, or b) get to the point where is says android is upgrading, and then starting applications, where it then hangs indefinitely.
It's basically driving me nuts. I can't think of another way to skin this cat.
strakajagr said:
I have data wiped/factory reset in stock recovery at least 30x. I do it every time before I flash. I had flashed using RSD and using ICS Tools. Both APPEAR to work as they get through, error free. It's only after I boot the phone up for the first time that I either a) get stuck on the black screen after the moto logo, or b) get to the point where is says android is upgrading, and then starting applications, where it then hangs indefinitely.
It's basically driving me nuts. I can't think of another way to skin this cat.
Click to expand...
Click to collapse
Have you tried wiping AFTER fastbooting? Not sure it would make a difference but might be worth a shot. I just recently fastbooted my Xoom and it wouldn't boot until after I factory reset in stock recovery. One other thought, are you sure your were on .217? Maybe you could try using the method used when moving to new ICS leaks from an older leak. (Man that seems like forever ago. LOL).
Droid 4 - AOKP JB
kwyrt said:
Have you tried wiping AFTER fastbooting? Not sure it would make a difference but might be worth a shot. I just recently fastbooted my Xoom and it wouldn't boot until after I factory reset in stock recovery. One other thought, are you sure your were on .217? Maybe you could try using the method used when moving to new ICS leaks from an older leak. (Man that seems like forever ago. LOL).
Droid 4 - AOKP JB
Click to expand...
Click to collapse
Yeah I tried wiping after my flash to no avail. I was running 217, but I'm still about to try installing an older version (213) from my SD card. It's not like things can get any worse.
ICS tools? I thought there was a ICS SBF file now. Doesn't that make the whole "ICS tools" thing unnecessary now?
strakajagr said:
Yeah I tried wiping after my flash to no avail. I was running 217, but I'm still about to try installing an older version (213) from my SD card. It's not like things can get any worse.
Click to expand...
Click to collapse
I really wish there was a way I could install ANYTHING over the flash via my SD card, but stock recovery only allows official builds.
strakajagr said:
I really wish there was a way I could install ANYTHING over the flash via my SD card, but stock recovery only allows official builds.
Click to expand...
Click to collapse
There's no way... but I just fixed it. I used a different USB cable (because the other one was intermittently losing connection) and it works. Unreal.
strakajagr said:
There's no way... but I just fixed it. I used a different USB cable (because the other one was intermittently losing connection) and it works. Unreal.
Click to expand...
Click to collapse
On another note, I used ICS Tool to root it (Using option 9) and it did the same thing all over again, to my phone. Unreal. I had to RSD it to get it back. WTF?!?! I think this is a sign that I ought not hack the phone, but I will seemingly never learn.

Categories

Resources