Database Users

Rooting nexus 7 is impossible

Well unlocking the boot loader is possible but when rooting the nexus 7 gets stuck in fastboot when its suppose to be rebooting its self oh well I been at it all night so now I realized its impossible
Sent from my Nexus 7 using xda app-developers app

Use the toolkit, worked great for me. I couldnt get the adb right so I tried that. My nexus 4 was easy without the toolkit though..
Sent from my Nexus 4

I get a error saying failed <remote: <>
Sent from my Nexus 7 using xda app-developers app

If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.

How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app

I'll just go to yahoo answers I'll have more help there
Sent from my Nexus 7 using xda app-developers app

Class_of_punk26 said:
How come y'all help everyone else but I can't even get a hint on what I'm suppose to do I'll just return my tablet and get a new one Cruz obviously its gotta be my tablet
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
If you unlocked the bootloader and you're having trouble rooting your device then I don't see you being able to relock the device either, which is critical to do before returning it as technically an unlocked device is out of warranty.
And you say no one is helping you, but you haven't provided any information at all. We have no idea what you did to even cause that error, and you were recommended just to use a toolkit if you want, as that is an easy approach, and you haven't responded on whether you have done that either.

Exactly, how is anyone supposed to help if you don't tell us what you did.
How did you unlock fast boot? What did you try to get rooted?........etc

User is informed of multiple posts. So hopefully, with your help, the root issue can get resolved.
User MUST tell people exactly the steps taken to replicate the error. Including PC type and Operating System.
I hope we do not see duplicated posts anymore.
So if some of you more experienced users, can do some "hand holding" and walk him through the steps, then it will be appreciated. As clearly, he has issues on his own.
Do it for XDA...
MD

bftb0 said:
If you can unlock the boot loader, you can do *anything* to your tablet starting with fastboot.
Learning to install drivers is a Windows issue - the skills needed to analyze & resolve driver problems have almost nothing to do with what device is attached to the other end of the USB cable.
Toolkits are a crutch for avoiding learning a very small number of skills; if you don't want to learn those skills, probably you shouldn't be rooting.
Throw away your toolkit and read the fastboot thread. The whole process is far easier than you think.
Click to expand...
Click to collapse
I agree 100% on Toolkits

That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)

arclight25 said:
That sounds like a windows driver issue. I had a similar issue when rooting my N7.
Open device manager
Look for Nexus 7
Does it have the yellow triangle on it? If yes, then your ADB driver is not installed, or not installed correctly
In ADB mode it should show up in the device manager as Android ADB Device (or something similar)
Click to expand...
Click to collapse
Yeah, this was my problem.. That's the only reason I used the toolkit. It wouldnt install right after downloading USB driver through SDK . got me pissed off and uninstalled every driver, and installed my nexus 4 all over also. Some how that one went easy..
Sent from my Nexus 4

LOL op went to yahoo answer, hilarious!
If he is still reading this, USE THE GOD DAMN TOOLKIT FFS, its pretty much idiot proof.

Yea, toolkit is the only way to go.

I think he is stuck in the same place I am stuck in. Whenever I get to the "Reboot Bootloader" in the Toolkit, it fails to go any further. I've made a thread about it here: http://forum.xda-developers.com/showthread.php?p=37524971
The toolkit isn't for everyone, unless of course I'm doing something wrong.

as long as toolkit detects your device, you can simply flash the google image and have everything reset, i dont see how that isnt for everyone honestly......

I used Wugfresh's toolkit and everything worked easily. I dont know any other way to do it, and the toolkit makes it easy for Gnex or Nexus 7.

[Q] Device Offline: Brand New Nexus 4, 4.2.2

So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
EDIT: Consider this solved... it seems I had a bit much to drink... little did I know I don't need ADB... just fastboot.
Oh well All is well.

x3phyr said:
So, got a replacement Nexus 4 today, and it's been updated to 4.2.2 and for some reason, it comes up as offline on ADB no matter what I do.
However, the funny thing is, my other Nexus 4, the one I was getting the replacement for, connects to ADB wonderfully. Shows up as a device, no problem. It's on 4.2.1.
Question 1: How can I manage to get the gosh darn thing to be recognized as online. I've tried two different cables, both of which connect with the 4.2.1 nexus but not the 4.2.2.
Question 2: Can I install a custom recovery without ADB?
Click to expand...
Click to collapse
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?

Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.

Unlock and Root 4.2.2
h.nocturna said:
Is the device recognized by Windows? Checking under Computer>Properties>Device Manager does the phone show up correctly?
Click to expand...
Click to collapse
If you're trying to unlock and root your nexus, you can follow the steps on this forum http://forum.xda-developers.com/show....php?t=2147413 There's another way to unlock and root your device (via adb) since Wugfresh's NRT doesn't support 4.2.2. Just make sure you use the correct .img file for your specific device.
You can also update any old SDK files by opening the SDK Manager on your pc.

USSENTERNCC1701E said:
Use the search in the future please. Just update ADB. With 4.2.2 the phone will pop up to ask you if you want to authorize your computer to access the phone, this "feature" requires the updated ADB, no change to fastboot, so you'll be fine getting the recovery on there, but ffr with ADB.
Click to expand...
Click to collapse
I did use the search feature and I will have you know that the FIRST THING I DID was download and update the absolute most recent ADB so thank you, but the degrading "learn to search" comment was not applicable.
Anyhow, this whole conversation is fairly irrelevant since I got what I needed to do, done.
Thanks for the help everyone.

Mind telling me what you did, im stuck in the same situation

gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
same situation. whatd you end up doing?

gsusx said:
Mind telling me what you did, im stuck in the same situation
Click to expand...
Click to collapse
whocanhebe said:
same situation. whatd you end up doing?
Click to expand...
Click to collapse
Download this and replace your old adb & fastboot
http://forum.xda-developers.com/showpost.php?p=37935821&postcount=26

Have you tried entering:
adb kill server
adb start-server
Read this:
http://stackoverflow.com/questions/8162581/why-does-adb-return-offline-after-the-device-string
It worked for me. I did it last night when I had the same issue.

hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong

gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
if you have updated adb try killing the server with adb kill-server

EZ
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.

gsusx said:
hiya
might be havving a blonde day but even using this my device still shows in cmd as offline when i type "adb devices"
what am i doing so horribly wrong
Click to expand...
Click to collapse
Have you downloaded the updated version of adb from post #8? And make sure you use that rather than whichever you were using? That was all I needed to do to get my offline Nexus 4 online again...

It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2

VoiD_Dweller said:
It have something to do with usb debugging not being enabled on the new phone?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
In that case, I don't think you get the "offline" status from adb - I think it wouldn't appear at all?

It appears that the Linux SDK isn't fully updated (as of today, newest build is 0219). My adb version is 1.0.29, and from a bit of research it seems that that version cannot ask your device for the OK it needs in 4.2.2. I hope I'm wrong though...
EDIT: When I had basically given up, I re-checked one last time, and there it was on my screen; the OK. Unfortunately, I have no idea what permitted this. Let the building start. Good luck to all of you!

jotss said:
Hey
Guys had the same problem and it was really simple to solve.
When you start adb and type adb devices and your device comes offline.
Go to settings>developer options - unchecked USB debugging and check it again, right after your computer will recognize your phone and in the phone will appear a box with your computer's Mac address asking you to allow connection.
Click to expand...
Click to collapse
^ This worked for me. Thanks a lot! :good:

[Q] adb offline nexus 7 4.2.2

Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:

Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?

how to do that?
compty said:
Hello there, have you unlocked your bootloader?
Also have you installed the correct drivers?
And is USB debugging mode enabled on your nexus?
Click to expand...
Click to collapse
how to unlock bootloader 4.2.2?
yes usb debugging is enabled

I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.

google toolkit error trying to unlock
compty said:
I assume you are using Google Nexus 7 Toolkit?
If so there should be an option which says unlock bootloader.
Click to expand...
Click to collapse
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally

Same problem
leo9252 said:
Oh yeah sorry about that however when I try to unlock the error adb devices offline comes also it can't find adb anywhere even when my nexus is on normally
Click to expand...
Click to collapse
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.

Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981

further problems
sicameron32 said:
I feel your pain as I too am having the same problem. I am posting on here so I can easily follow your post. I will tell you also that I think it has something to do with 4.2.2 but not positive at this point. I have rooted a Nexus One, HTC Dream, SGH679, so I do have some experience with this. I have changed ports, cables, started and stopped the service, rebooted the tablet, toggled the debugging just keep getting the offline. When I plug my phone in and use it, it sees it and it works fine, then when I plug the tablet back in it go back to offline. I even removed all the drivers on the computer just so it would get confused with the phone driver and still no luck. I think the driver is fine tho because it says it is in device manager, and I can transfer files back and forth from my tablet to my computer. Don't loose heart tho I think the answer is out there and I will keep working on it, and checking back to see if anyone else has had success.
Click to expand...
Click to collapse
So I was going to do it the old fasion way by following this guide
http://forum.xda-developers.com/showthread.php?t=2150661
I didn't quite get step four because the nexus 7 doesn't have an SDcard, but I copied the zip to the root of the device.
When I did step 7 the device did not go to Fastboot, it didn't go anywhere other than a black screen. I think I have a faulty unit, or the holding of the volume buttons with the power is really not the way to get to fastboot, either way I am looking at a brick right now. Any thoughts will be welcome. I messed around with it for 10 min now and got the device to re-boot. Not sure if I should try the fast boot option again.

Are you on Windows 8 by any chance?
Because I couldn't get it to work on Windows 8 and had to use Windows 7.

You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.

everyone i got it working! adb offline fixed
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.

leo9252 said:
It took me a while but I finally fixed it! Here's what I did I went crazy and searched all over the web with the keywords adb offline nexus 7 4.2.2 I then found a website that related to my issue it said to update SDK manager so I downloaded the manager then found android 4.2 next downloaded all that was under the 4.2 package and next downloaded the extra packages next thing I knew I plugged in my nexus and on it on the screen it told to choose yes or no on USB debugging and that's all you have to do to fix the problem of the adb offline bullstuff. I hope you guys will be able to understand what I'm writing to you. I also use windows 7 for this.
Click to expand...
Click to collapse
It won't let me download and install anything from the 4.2 list...did you do anything else?

myleb said:
You must update adb command from here:
http://forum.xda-developers.com/showthread.php?t=1766475&page=251
JB 4.2.2 is asking for debugging PC white list, please enable and allow it when prompt. Check here.
http://www.androidpolice.com/tags/android-4-2-2-adb-device-offline/
I got exactly the same problem and now it works for me.
Click to expand...
Click to collapse
FWIW, here is my experience:
PC: Win7 Pro x64 SP1 - SDK platform-tools 16.0.1 - SDK Tools 21.1 - ADB v 1.0.31
N7: JDQ39 Stock *
( *OK, i diddled default.prop in my boot image to set "ro.secure =0". I don't know if that could make a difference or not )
The Nexus 7 asks for confirmation of inbound adb sessions for every new adb server invocation on the client PC.
When it does ask for credentials, you have to get to the on-screen display pretty quickly - a couple of seconds at most. If you don't the device will be reported as "offline" by the first invocation of
adb devices
If you accept the connection, the next time you run "adb devices", the status is back to normal (reports "device" instead of "offline").
You can test this out yourself - just iterate in a loop these three commands:
adb devices
adb devices
adb kill-server
Nothing that can't be understood by someone who knows what is going on; but I suppose that all the toolkits are running adb underneath the hood, so it is certainly possible to get tripped up when using a toolkit if you aren't Jhonny-on-the-Spot when that dialog pops up on the tablet.
Also, for the adventuresome:
I note that the new stock JDQ39 (4.2.2) ramdisk has a new line in the default.prop that was not in JOP40D (4.2.1) :
Code:
ro.adb.secure=1
I suppose that could be toggled off if you have a favorite kernel/ramdisk setup and you don't want to be bothered by this stuff. But it does mean unpacking/repacking your boot images.
cheers

I'm having the same problem. Never recognizes an ADB device. When it does it shows my serial number followed by "offline."
Any ideas? I'm ready to return this thing.
---------- Post added at 08:28 PM ---------- Previous post was at 08:16 PM ----------
Out of curiousity what driver are you using and how are you installing it?
Also where is your device coming up in the device manager?
I've tried so many things that I think I'm getting off track. Sadly my motorola phones were much easier to root.

how come you cant?
LucentBirch said:
It won't let me download and install anything from the 4.2 list...did you do anything else?
Click to expand...
Click to collapse
How come you can't download and install from the SDK manager?
That's how my problem got fixed.

Worked
jibdev said:
Have you tried updating the data files in NexusRootToolkit?
http://forum.xda-developers.com/showthread.php?p=37955981#post37955981
Click to expand...
Click to collapse
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.

you're welcome
sicameron32 said:
Thank you.... this worked first time go! So happy!
Thanks to all involved.... This is by far the most useful forum for phones.
Click to expand...
Click to collapse
I knew someone would find this useful.
:laugh::good:

leo9252 said:
I knew someone would find this useful.
:laugh::good:
Click to expand...
Click to collapse
The sad thing is I have no idea what finally got it to work. Maybe just an extra reboot I had forgotten at some point. I do know however that I had to add a few extra lines (hardware ID) to the .inf file in the usb driver. Not sure which did the trick. I also used a combo of the toolkit to unlock and the manual method to root. Also I am unable to boot my device into the bootloader/fastboot via windows and rather have to manually (physically) shut down the device and enter the bootloader via the physical buttons. Probably an issue with the windows drivers again, but at least I have full functionality once in fastboot.
Only thing is now I can't get access to the storage via windows. And there's no way in hell I want to change the ADB drivers without knowing which finally worked for me. I'm thinking though that this is an entirely different device in device manager (I'm obviously not that knowledgeable).
Also I'm kinda annoyed by the unlocked padlock symbol on startup. I suppose that should be a welcome sign of achievement after spending all day trying to unlock/root, especially for such an unlearned person as myself.

did you clear this issue?
leo9252 said:
Im trying to root my nexus 7 what exactly am i supposed to do to achieve that?
i got this error adb offline and it's screwing with the rooting process
i upgraded to 4.2.2 yesterday help me achieve rootness
also am i suppose to unlock my nexus before rooting it.:victory:
Click to expand...
Click to collapse
if not, pls gimme a mesg.
cause I'm a noob, I cannot use link here. :crying:
This issue is included in 4.2.2, and ADB is disabled by default for security.
I tested on my Nexus 4, 4.2.2 running. :fingers-crossed:

Okey. So to summarise: there is this new security feature in android 4.2. that makes the device show a popup if you want to allow the connected computer to use the adb = debugging bridge. But for this to work, you need to have the newest adb binary, which needs to print 1.0.31 when you run "adb version"
(found that info here --> http://www.androidpolice.com/2013/0...s-from-stealing-your-data-in-some-situations/ )
Under linux when you try to do it the old-school google-recommended way and download the huge "adt-bundle-linux-x86_64-20130219" and use the "android" tool to find new updates to the platform tools, it will tell you you already got the latest version which is rev 16.0.2 which contains an adb binary which will print version 1.0.26 which will not work with this new android 4.2.2 security feature.
So after searching for a linux adb 1.0.31 binary, I found it here:
https://github.com/mozilla/r2d2b2g/commit/2eefcc05366173ca51635da8f542fd8473ba0fea -->
https://ftp.mozilla.org/pub/mozilla.org/labs/r2d2b2g/adb-1.0.31-linux.zip
with that binary I finally can use adb on my nexus 7 again.

Lost root and recovery PC can't see nexus4

My PC couldn't see my nexus and I noticed this problem before I knew of an update and yet the update was that same day....
Anyhow the PC wouldn't see the nexus but every other device it does see. We're talking mint 13 mint 11 win7 and Xp... All saw the device prior. So I couldn't get the 4.3 update because fastboot didn't work either. I brick proofed my options prime if anybody knows what that is like you know that I know drivers and fastboot lol. So anyway I need drivers I think so I delete them and reinstall ..we forgot what the first attempt looked like but after trying many times and using the nexus tool kit to delete all the old drivers or installed drivers I then reinstall with error. It reads windows could install driver properly or close to that and the device was labeled as nexus 4 adb but it had a exclamation mark in yellow below it and it didn't work. Hard to believe that it can't be seen on Linux at all of course I don't know the tricky tricks I usually plug it in and boom it ask me what I want to do with it and no now nothing.. Also notable is the fact that I was on stick type Roms and then went to cm10 with LTE enabled and of course older radios since then it seems no connection. Maybe it's my cord but I tried two... I hope it a cord issue. . I
Sent from my Nexus 4 4.3 ota with no root now and no recovery at all using xda premium
Edit. After shining my led light into the end of the cord I only can see 4 of the 5 prongs inside the device end of the USB cord. So I guess that's my problem which sucks cause I deleted the drivers I installed before. Oh well... Have 4.3?

[Q] IMEI unknown Baseband unknown (yes another one) Problem

Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached

Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.

thorindwarf said:
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
Click to expand...
Click to collapse
I have tried with a couple of SIM cards, and also without it. No luck, the SIM Cards were pretty old tho, I will try with a new one and see what happens.
Other thing, Shouldn't I see the IMEI and baseband without a SIMCARD in anyways??
Thanks

I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app

I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.

raptir said:
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
Click to expand...
Click to collapse
Hi, I already tried that, the 4.2.2 that i flashed was from there :/ (with fastboot)
Also I completely took apart the phone today, and the motherboard seems fine (for what the naked eye can see)
The battery seems to drain really fast tho.

pocketrussian said:
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Thank you, I will do that as soon as I figure out how to do it.
With diagnostic mode you mean that download mode or there is another one?
Also I noticed that every time i use LGNPST a window saying that my device is being installed pops up, could it be a driver issue?

I don't think that this would work in download mode. I just tried with LGNPST in download mode and it's asking for an spc code. I tried 000000 but I didn't work. I tried qpst and it says it can't read phone settings in download mode. Again, I don't know much about this but there must be another mode (diagnostic) for which this might work. I googled but wasn't able to find any # codes that work on the n4. Perhaps from the terminal emulator if your phone is rooted. I wish I could help more but I just got this n4 recently and I am not an expert in any of this stuff.
Sent from my cm_tenderloin using xda app-developers app

Same problem here...
venec said:
Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Click to expand...
Click to collapse
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???

stenosis said:
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
Click to expand...
Click to collapse
Nope, no solution for me, tried everything that is here in xda, and nothing works :/

venec said:
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
Click to expand...
Click to collapse
I'm with the same issue. Any good news?

elbosio said:
I'm with the same issue. Any good news?
Click to expand...
Click to collapse
Nope, tried everything nothing works so far
I'm thinking about sending it to this guys or wait for kitkat and hope for the best:
http://mobiletechvideos.mybigcommerce.com/lg-phones/

OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app

I'm having the same issue so the phone is going back to Google for replacement. It has been acting wonky for a few days anyways.
I tried the Google factory flash script, flashed a few different radios, and followed this thread:
No luck.
I was running AOKP 2013-10-15 Nightly. And the problem started with the phone doing a constant boot loop for a few hours without me noticing. It was some kind of issue with the power button getting stuck that appears to have resolved itself but it took the radio with it.

Droid2drummer said:
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes it was 4.2, so you mean do the LGNPST thing and after flash 4.2 image?
I already did that with the 4.2.2 (JDQ39) image and still no luck

I had the same issue, and I solved it by flashing the factory images... Twice.