yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] xenmonkey:
That happened to me too.

Redownloaded the boot.img and retried after a few failed attempts. (redownloading may have just been coincidence though)

---------- Post added at 02:58 PM ---------- Previous post was at 02:54 PM ----------

Does unticking debug mode and then reticking it solve anything?

I had to do that, but was using a PC not previously used for any android related stuff.
[Nexus 4 Android Development] USSENTERNCC1701E:
faceplam

Do folks still not know to check md5 :mad:
[Nexus 4 Android Development] xenmonkey:
I know very embarrassing.

But I deleted my original boot.img without checking the md5. Hence why I cannot rule out coincidence (rather than some other stupid thing I did) :)
[Nexus 4 Android Development] Stryder5:
Now that CWM has been released, HQRaja is going to update the OP with instructions on how to use CWM to root for those having trouble with the manual ADB steps.
[Nexus 4 Android Development] meln4ya:
Hey HQRaja, I know this must have come up once but have you tried using your Wallet app? R U getting a unsupported device error? When using my Nexus 7 it gives me the security warning and the unsupported device. If this has been answered then please forgive me. I know this is for the Nexus 4 NOT the 7 and - No I did not use this method on the 7 :~ )
[Nexus 4 Android Development] Stryder5:
I get the unsupported device warning, but can still use the app just fine. Haven't actually tried making a payment though.
[Nexus 4 Android Development] HQRaja:
Sorry no idea on anything related to Google Wallet. I'm from Pakistan and it's not available here.
[Nexus 4 Android Development] jimmyz:
This is normal for a rooted device. Wallet works fine despite the message
[Nexus 4 Android Development] sjgore:
The CWM method worked perfectly for me too, but my device didn't get wiped. Am I just lucky? :)
[Nexus 4 Android Development] Stryder5:
The command "fastboot oem unlock" is what will wipe your device. If you didn't run that command, your device will not be wiped.
[Nexus 4 Android Development] sjgore:
I did run "fastboot oem unlock" though. I then selected "Yes" and the status changed then to "Lock off" (or whatever the exact wording is).

***EDIT*** Just to double check, I went back into the bootloader and it definitely says "LOCK STATE - UNLOCKED".
[Nexus 4 Android Development] HQRaja:
That's weird since if you're coming from a locked bootloader, unlocking it ALWAYS wipes all your data, including that on the internal SD card. It has been this way since Nexus One all the way to Galaxy Nexus in my testing (I don't have a Nexus 4).
[Nexus 4 Android Development] sjgore:
I was fully expecting it to wipe, as mentioned in your excellent guide, but it didn't. Can't offer an explanation! :)
[Nexus 4 Android Development] Stryder5:
You somehow lucked out. It definitely wiped mine.
[Nexus 4 Android Development] sjgore:
I got an OTA update shortly before unlocking. Is it likely that could have anything to do with it?
[Nexus 4 Android Development] Stryder5:
Quite a few people udpated before unlocking/rooting.
[Nexus 4 Android Development] mgorman:
Just to clarify, you said that locking the boot loader works after you've unlocked it? I remember on my Nexus One that once you unlocked the boot loader you voided the warranty and you couldn't re-lock it. Can anyone verify this?
[Nexus 4 Android Development] Vandalet:
It's been a while since I've looked into this, does rooting still break Play Movies and Wallet like it did on my Galaxy Nexus?
[Nexus 4 Android Development] mgorman:
So I have the OTA update and installed and I followed all teh instructions and when i boot the insecure boot image my phone just sits at the nexus X loading screen and doesn't go past that
[Nexus 4 Android Development] kchino:
I used this method to root and everything is working fine. If you want to relock the bootloader then from the command line:

fastboot oem lock
[Nexus 4 Android Development] Stryder5:
Just reboot and try again.
[Nexus 4 Android Development] 0.0:
where do i place the recovery.img? if i want to fastboot it, do i place it in the platform-tools folder for example?
[Nexus 4 Android Development] kchino:
Yes, it should be in the same folder as your fastboot binary, usually platform-tools.
[Nexus 4 Android Development] jimmyz:
This non-wiping with unlocking the boot loader also happened with the google playstore galaxy nexi!
[Nexus 4 Android Development] evaradar:
There's still now official CWM Recovery for the Nexus 4 correct? Even though fkrone uploaded a working version? Meaning not from the CWM's website as there's still no Nexus 4 yet in that list.
[Nexus 4 Android Development] fkrone:
You can use my CWM. It is built with the official CWM sources with no modifications (except those which were needed to make CWM boot on Nexus 4).
[Nexus 4 Android Development] el3ctrik:
For the people who get this far looking for a fix to the infinite boot animation (particularly if you used the CWM method):

hold power + down vol twice until you get back to the fastboot screen

fastboot boot cwm-recovery-mako.img

clear cache + dalvik cache

unplug from pc

reboot from within CWM

That's how I got out of the loop :) hope it helps
[Nexus 4 Android Development] evaradar:
Gotcha. Will do so when I get my Nexus 4. So this won't be any different than when the devs at CWM make it official for the Nexus 4 on their website correct? Does this CWM also stay permanent? Or does it go away? Since we are booting and not flashing it?
[Nexus 4 Android Development] Unconn:
Link. (espically if you actually start a thread for this over there)

Also, what is going to happen here if the questions ar over there?
[Nexus 4 Android Development] fkrone:
At the moment it is not permanent but I am working on this. But it seems like you need at least do one update to make it permanent. But let me work on this and then we will see.
[Nexus 4 Android Development] sjgore:
I made a backup using CWM, as recommended in the steps in the 1st post, but I can't find where on earth it put the backup folder/files? Anybody know?

There's nothing in /sdcard/clockworkmod/.
[Nexus 4 Android Development] evaradar:
Sure thing.
[Nexus 4 Android Development] Stryder5:
Post this in the CWM thread, not here.
[Nexus 4 Android Development] hello00:
so im trying to use these codes and it says device not found? i was able to unlock the bootloader and flash boot tho

adb shell mount -o remount,rw /system
adb push su /system/bin/
adb push Superuser.apk /system/app/
adb push busybox /system/xbin/
adb shell
chmod 06755 /system/bin/su
chmod 0644 /system/app/Superuser.apk
chmod 04755 /system/xbin/busybox
cd /system/xbin
busybox --install /system/xbin/
exit
exit
[Nexus 4 Android Development] jimmyz:
Look in data/media for the cwm folder
[Nexus 4 Android Development] kchino:
Make sure adb is in your path or folder that you're running the commands from. Try running "adb devices" no quotes first, you should see it reply with your nexus 4 and the serial. If not "cd" (change directory) to the folder that has the adb binary and run the commands from there.
[Nexus 4 Android Development] guifort:
Thanks You,

It's OK !

It have installed OpenVPN Perfect !

Good job ;)
[Nexus 4 Android Development] flipper203:
nexus rooted, everything works....
[Nexus 4 Android Development] Stadsport:
Done and working great, thanks!
[Nexus 4 Android Development] rptw:
why does this not replace the existing boot image

but this does?
[Nexus 4 Android Development] hello00:
i used the cwm method thanks anyways
[Nexus 4 Android Development] Traxex_:
My phone stucks at the Google logo after tring to boot into the insecure kernel :/

Already did the OTA update.
[Nexus 4 Android Development] HQRaja:
Neither of those commands replace the existing boot or recovery image. Here is the syntax of simply booting with an image without flashing it:

fastboot boot imagename.img

The imagename.img could be a boot image or a recovery image, and this will simply make the device boot using that image one time, upon using the command. A reboot will revert back to the original boot or recovery image.

To flash an image, you use this syntax:

fastboot flash <partition> imagename.img

For example

fastboot flash boot boot.img

will flash boot.img as the boot image

Similarly,

fastboot flash recovery recovery.img

will flash recovery.img as the recovery image. These changes will be permanent and will persist till another boot or recovery image is flashed.
[Nexus 4 Android Development] HQRaja:
I can verify that the bootloader of all Nexus devices including and after Nexus S can be relocked after unlocking. It wasn't relockable only in case of the Nexus One.
[Nexus 4 Android Development] HQRaja:
That was in reference to off-topic questions i.e. those that aren't directly related to this guide. This thread is the right place for any questions/issues related to this guide. =)

And you can find the Nexus 4 Q&A section by clicking the 'Google Nexus 4' link above and then clicking 'Nexus 4 Q&A'. It's the standard convention on XDA for all devices BTW.
[Nexus 4 Android Development] HQRaja:
There is a problem with custom recoveries on Jelly Bean (should be fixed by now as Koush just posted the latest official CWM recoveries for Jelly bean devices, though not sure if one for Nexus 4 is out there yet). It basically creates a folder named 0 in /sdcard/ each time the phone is factory reset (or each time a recovery operation is performed...not sure but it does happen) and all your stuff then goes into that /sdcard/0/ folder as it is then treated as the /sdcard/ folder.

During my testing on Galaxy Nexus with 4.2, I ended up with many folders like that and my stuff (backups and zip files I transferred to phone for flashing etc) scattered across /sdcard/, /sdcard/0/, /sdcard/0/0, /sdcard/0/0/0 and so on. Was a mess, but getting everything from there back to the appropriate folder on /sdcard/ (like getting the backup I found in /sdcard/0/0/clockworkmod to /sdcard/clockworkmod) manually while connected to PC fixed it and I could restore it from CWM.

Hope it helps. =)
[Nexus 4 Android Development] HQRaja:
Happened with several others too. Retrying booting with the same boot.img again worked for pretty much all. I have also added this info to the OP now.
[Nexus 4 Android Development] HQRaja:
Seems your device is being detected in fastboot mode but not in adb mode. Try disabling USB debugging on your phone and re-enabling it? If that doesn't work, try reinstalling the drivers manually from device manager.
[Nexus 4 Android Development] yungfresh:
I booted the recovery and flashed super user. And now when I reboot I'm just stuck at the nexus sign. Please help!
[Nexus 4 Android Development] Stryder5:
Did you boot the recovery? Or did you flash it?
[Nexus 4 Android Development] yungfresh:
I did this command

Code:

fastboot boot recovery-clockwork-touch-6.0.1.6-mako.img

Now my phone won't start past the nexus logo
[Nexus 4 Android Development] :
Try flashing the stock boot.img found here: https://developers.google.com/android/nexus/images#occamjop40c

fastboot flash boot boot.img
[Nexus 4 Android Development] tweaked:
Thanks for the files. Was odd tho, The instructions weren't correct for me.

I powered off held down volume for fastboot. Then at a prompt I did fastboot boot cw.img

It auto restarted into recovery. I then made a back up and then flashed the SuperSU and busy box. Then rebooted.

Root available.

/Shrug :D Still awesome tho:laugh::cool:
[Nexus 4 Android Development] evaradar:
Not sure if you guys know, but thanks to Koushik official CWM has been released for the Nexus 4 and Nexus 10:

http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.6-mako.img

http://download2.clockworkmod.com/recoveries/recovery-clockwork-6.0.1.6-manta.img
[Nexus 4 Android Development] HQRaja:
Thanks for the info. I will update the OP with a link to official CWM. =)
[Nexus 4 Android Development] evaradar:
You're most welcome. Now we wait for an official SuperSU I take it? Unless this one is official: http://www.mediafire.com/?es35lyioe8hxbxh
[Nexus 4 Android Development] GSMachinst:
The official CWM will just boot but not flash?? Any ideas why?
[Nexus 4 Android Development] evaradar:
With the Official CWM based on the links I posted, you flash it. No need to boot it I think. Just like how we used to do it before vs booting. Since this is permanent and updated by the CWM team and Koushik its good to go. The CWM method in the first page was boot because it was a temporary fix.

Should not cause any boot loops too. Could be wrong. Again I can't tell since I don't have the actual device yet.

Anyone can please correct me on this and I would appreciate it.
[Nexus 4 Android Development] DarkRyoushii:
I got it to flash but it's coming up with android and a red ! sign.. no go with the flashing I suppose.
[Nexus 4 Android Development] aimetti:
yep i got hung on nexus logo too

boot to recovery wipe cache and dalvik , boots fine now.

however even with the CWM image from their site it wont hold onto the flash. I can boot to it but not flash and go back in.

Also, unlocked phone and it didnt wipe
[Nexus 4 Android Development] satbir7:
Thank you for the TIP!!!

You got me out of the infinite BOOT Loop.........
[Nexus 4 Android Development] HQRaja:
The one I provided is official SuperSU. The zip file provided in the official one doesn't include busybox and only has SuperSU APK file and the su binary. I simply added busybox and modified the updater-script to remove some unnecessary commands for these devices and add busybox installation commands. The SuperSU APK itself and the su binary are both the same as those in the latest official SuperSU 0.98 =)
[Nexus 4 Android Development] satbir7:
Thanks for this thread!!!

Just rooted my Nexus!!!!

On a side note, can someone please make an IRC channel, where we can chat about all this stuff.....?
[Nexus 4 Android Development] aimetti:
So im rooted w/ the adb option , however now I cannot get recovery to start.

Anyone else?

Tried stock recovery , also fails to flash it seems. Boot to recovery just boots as normal
[Nexus 4 Android Development] satbir7:
I have the same issue, the recovery does not seem to stick, it is only okay when we boot it from fastboot......
[Nexus 4 Android Development] aimetti:
ya whats worse is I cant even flash stock recovery.

By chance did your device wipe after doing the oem unlock?
[Nexus 4 Android Development] satbir7:
No it did not wipe for me...
[Nexus 4 Android Development] jimmyz:
could it be similar to the galaxy nexus where there was a script (recovery-from-boot.p) that reflashed the stock recovery upon reboot?
[Nexus 4 Android Development] satbir7:
I would not know, because this is my first ever NEXUS device!!!!
[Nexus 4 Android Development] jimmyz:
Maybe look in /system for recovery-from-boot.p and try renaming it
[Nexus 4 Android Development] aimetti:
ya tried that , no luck
[Nexus 4 Android Development] yungfresh:
I went and downloaded image. and still no dice. it keeps saying it cant load recovery...
[Nexus 4 Android Development] jok4h:
Tried the official recovery also.

Fastboot said it installed it successfully but it doesnt boot into Recovery.

It will attempt to boot into recovery. Fail than boot into phone.
[Nexus 4 Android Development] yungfresh:
What was the tip? I can't seem to get out of the boot up screen. Nothing I do works. Please share.
[Nexus 4 Android Development] YoungAceAtlanta:
Not working for me.. i just get a android guy with a sign coming out of his stomach -_-
[Nexus 4 Android Development] sjgore:
So that's at least 3 of us then who didn't get our devices wiped when we unlocked. Interesting.
[Nexus 4 Android Development] YoungAceAtlanta:
Now I flashed the recovery but it doesn't boot into recovery.. it just reboots twice and that's it

Root apps work. Just recovery don't
[Nexus 4 Android Development] yungfresh:
my device is unlocked and all data is still there. can anyone confirm the updated CWM touch sticks and you boot up correctly after flashing?
[Nexus 4 Android Development] P0MM3S:
those who get stuck in bootloop after flashing - did you also try "fastboot erase cache" before flashing?
[Nexus 4 Android Development] Shaky156:
Haha was just about to put that here aswell
[Nexus 4 Android Development] P0MM3S:
sorry shaky, i "forked" you :D i'm @ work right now, so i could not test it myself
[Nexus 4 Android Development] darkamikaze:
I cant' for the life of me get this working. doing

fastboot flash recovery recovery.img

causes me to bootloop and not be able to get into recovery X_x.

doing

fastboot boot recovery.img

Lets me boot into CWM but the power button doesn't seem to select anything.

The Touch version made my screen slowly glow white and it was starting to freak me out so I rebooted :| any ideas?

--Edit--

Went balls deep and tried the touch again. worked this time around. Although, add me as one of those who didn't get wiped.
[Nexus 4 Android Development] xelin0:
Same problem for me, it

went through the process, it said it sending and writing recovery ok.

Now when I try to boot into recovery it just goes to an android guy, stomach open with a red triangle with exclamation mark outside.
[Nexus 4 Android Development] P0MM3S:
damn....erase cache didn't do the job...same as b4...

EDIT:

Nice, now its bootlooping,,,,,
[Nexus 4 Android Development] Shaky156:
Did you erase the cache after installing recovery? If not try that

Once I get my PC n phone setup I'll see if I can boot into it
[Nexus 4 Android Development] P0MM3S:
Tried this...aaaand, again, bootlop...flashed now a factory image...

Gesendet von meinem Nexus 4 mit Tapatalk 2
[Nexus 4 Android Development] JPOKeefe:
Is this not supposed to delete cwm every time you boot up?

because it does for me
[Nexus 4 Android Development] cithrix:
Where can I get the original recovery image to flash it back?

I also get in a bootloop.

Erase cache doesn't help.

//edit: Well, I found the original recovery image.
[Nexus 4 Android Development] steslatt:
Well this has been a balls up for me. First time around followed instructions to flash recovery and ended up with bootloop, could not boot the device at all only into bootloader. I had to flash the original factory image to get the phone to boot again, but now I have no stock recovery, it just shows the android robot with red exclamation.

I can boot into cwm if i use the fastboot boot recovery command but I cannot get a recovery to write. My bootloader successfully unlocked so what is going on? I have managed to root buy booting into cwm using the above method but I am stuck with no recovery.

How can I get a recovery back?
[Nexus 4 Android Development] jimmyz:
Are you sure that is not the stock recovery (robot with red!). When u see that screen have u tried pressing volume up and pwr at same time to see if the options pop up?
[Nexus 4 Android Development] steslatt:
Where did you get the original recovery from? did you manage to get stock recovery back on your phone?
[Nexus 4 Android Development] Benxter:
tried to flash CWM touch and non-touch, same result as everyone else -> didn't work. But I was still able to boot properly. So I took the advice and did a "fastboot erase cache" and flashed again. Now I get into bootloop. So thanks for that :>

For everyone else who tries this: DO NOT USE "fastboot erase cache"!!!!

I already tried to flash the original recovery.img but still bootloop.

Any ideas how to get rid of bootloop and NOT having to restore to stock image?
[Nexus 4 Android Development] steslatt:
Just tried that now, nothing happens.

EDIT - After trying a few times it worked :) thanks. I still can't get a custom recovery to write though :/
[Nexus 4 Android Development] jimmyz:
Something is rewriting the recovery after a reboot. This would explain why you can load a custom recovery into ram w fast boot but can't get it to stick. Can u post some screenshots of your /system?
[Nexus 4 Android Development] Benxter:
Ok for everyone who got into bootloop here is how to fix it without flashing stock image again and loosing all data:

boot into bootloader by holding volume down and power button.

type in command prompt: fastboot boot recovery.img (make sure recovery.img is the CWM image)

now within CWM use wipe cache

reboot

et voila ;)
[Nexus 4 Android Development] llblwskydrgn:
I'm a total newb at this and I finally got it to work after an hour of fiddling. Also, I was pleasantly surprised to see that my device wasn't wiped. I went the CWM route btw.
[Nexus 4 Android Development] jdk2:
I did this yesterday evening and used the CWM method. I was also surprised that the data wipe never happened.
[Nexus 4 Android Development] steslatt:
I don't think its getting re written. When I flash cwm and try and boot into recovery it just reboots normally (no recovery at all). Then when I flash stock recovery it works fine.
[Nexus 4 Android Development] mcnob:
OK, well I got it out of bootloop but still can't boot into recovery to get root. Anyone who got the bootloop issue and managed to get into CWM care to share what you did?

Thanks.

Edit: Can someone post a stock recovery download link please until this is sorted?
[Nexus 4 Android Development] steslatt:
I just used the method:

Fastboot boot recovery.IMG then when in cwm recovery flash the su and busy box zip
[Samsung Galaxy S Blaze 4G] chjema:
Ok I have looked everywhere for a fix.

On Stock and stock based ROMS my gps works great, no problems, however in any CM/Aokp/Slimbean/etc. My gps is wayyyyyy off. Its not using the gps satellites but the cell towers, it marks me as 1500+ feet away from where I really am. Re-flashed tweaked and it worked perfectly,

I have downloaded every GPS app to calibrate, fix, re lock, you name I have done it but it still will not use the GPS satellites, just the cell towers, This is in Google Maps mind you. 4 different versions of Google maps did nothing.

With WI-Fi on it works perfectly, but I drive for a living and cant be on WiFi all the time. Sucks. Any ideas?
[Samsung Galaxy S Blaze 4G] dr4stic:
Did your phone ever go to full stock ICS before you went on to the AOSP based roms? I'm asking because I wonder if maybe there's something with the ICS versions of the firmwares, or maybe the lack thereof.

EDIT: Btw, if you install the full stock rom (including all the firmware partitions) and then try the AOSP roms, and it works, please let me know via PM... I've been thinking about specifying that people have come from the stock ICS rom just to make sure they have the latest firmwares on the phone.
[Samsung Galaxy S Blaze 4G] dwitherell:
Have you tried messing around w/ the gps.conf file in /system/etc/ ?

This thread

has got some stuff that (at least by the reports of others) has achieved some amazing improvements across a number of different phones/roms/carriers/etc. Not sure it'll help, but worth a shot :)
[Samsung Galaxy S Blaze 4G] chjema:
No...I have not been on full stock in a long time.

Right now on CM10 GPS not working right. Will do a full wipe and install Tweaked 2.0 and it works on that perfectly.

I will check out that thread and see what I can do.
[Samsung Galaxy S Blaze 4G] dispozable:
I just started using Mytracks a few days ago for my bike rides/dog walks and mine is pretty accurate on CM10. The only thing I notice goofy with my Google Maps is sometimes when I take a break and look at my phone, the compass doesnt always show the correct direction I am facing til I start moving again. This may be cause I have the phone in my pocket or on the dog but fixes as soon as I move. Lock on is under 20 secs as well. Did you change the min/max values in the settings?
[Samsung Galaxy S Blaze 4G] chjema:
FFS man. You alone have pimped my phone out more than I can say. Thanks man. This worked. It is now accurate to within 2 meters. Hell it shows what room I am in. lol

Thanks again!!!

To all flashing a non-stock ROM I highly recommend the ADB Push Installer seen here

You have to use the ADB Push file...it took me 20 secs.