[Q] Need to flash 4.3 stock recovery - Nexus 4 Q&A, Help & Troubleshooting

Hello,
I installed Open Recovery with TWRP and I want to return to the stock recovery.
Where and how can I find the 4.3 stock recovery in order to install it and how ?
Many thanks :good:

this what you're looking for?
http://forum.xda-developers.com/showthread.php?t=2010312

No, I need only the 4.3 Stock Recovery and without any wipe.

isotoper said:
No, I need only the 4.3 Stock Recovery and without any wipe.
Click to expand...
Click to collapse
You can try Wugfresh's Nexus Toolkit, it has many tools such has a stock recovery flasher.
Since I am on holiday I have no idea if Android 4.3 is supported on the Toolkit yet.
Sent from my Nexus 4 using Tapatalk 4 Beta

andyabc said:
You can try Wugfresh's Nexus Toolkit, it has many tools such has a stock recovery flasher.
Since I am on holiday I have no idea if Android 4.3 is supported on the Toolkit yet.
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Toolkit doesn't support 4.3 yet.

isotoper said:
Toolkit doesn't support 4.3 yet.
Click to expand...
Click to collapse
Android 4.3 does have a new recovery which does look better so I have no idea how to rip it out.
Sent from my Nexus 4 using Tapatalk 4 Beta
---------- Post added at 02:55 PM ---------- Previous post was at 02:30 PM ----------
Maybe you can get the recovery from the Nexus Stock Image site:
https://developers.google.com/android/nexus/images#occamjwr66v
Extract it and try to get the image.
Once you get the image go to Fastboot mode and enter the command: fastboot recovery [image name].img
Sent from my Nexus 4 using Tapatalk 4 Beta

Thanks, but I'm not so familiar with that fastboot script.

Easiest way is to download the 4.3 stock image and just flash the recovery image.

Any instructions?

isotoper said:
Any instructions?
Click to expand...
Click to collapse
my friend the task you are trying to accomplish will have instructions where ever you find the images. Have you search for the image you need? I think you are just looking for a zip file with stock recovery in it. This is not the norm but if you want stock that badly you may have to learn how to use fastboot and flash all stock that way. I know you dont want to lose your data but you may have to make the choice of data vs custom recovery. Go into the CWM or TWRP thread and kindly ask if someone can package the stock recovery in a zip file for you

isotoper said:
Any instructions?
Click to expand...
Click to collapse
Download the Android ADT Bundle from http://dl.google.com/android/adt/adt-bundle-windows-x86-20130717.zip
Extract the file and copy the "platform-tools" folder to C:\Android (create this folder if it doesn't exist). The final path should be C:\Android\platform-tools
Download the factory images from https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz . Extract them and find a file called "recovery.img". Copy this file to your platform-tools folder in C:\Android
Open a command Window in your platform-tools folder by holding SHIFT and right-clicking on it
Type:
Adb devices
And make sure it says "device" after some numbers.
Now type:
Adb reboot-bootloader
Wait for the device to reboot to bootloader.
Now type:
Fastboot flash recovery recovery.img
That's it.

Wow, thanks. I will try that and update.
It's not suppose to wipe any data, right?

Ok, done that and this is the cmd output :
sending 'recovery' (6738 KB)...
OKAY [ 0.220s]
writing 'recovery'...
OKAY [ 0.411s]
finished. total time: 0.634s
I think it worked just fine !
But how should I verify that I do have the stock 4.3 recovery and process succeed ?
Thanks !!

isotoper said:
Ok, done that and this is the cmd output :
sending 'recovery' (6738 KB)...
OKAY [ 0.220s]
writing 'recovery'...
OKAY [ 0.411s]
finished. total time: 0.634s
I think it worked just fine !
But how should I verify that I do have the stock 4.3 recovery and process succeed ?
Thanks !!
Click to expand...
Click to collapse
Yes, that's OK.
You see the stock recovery for yourself by turning off your device (unplug from charger if that's the case), and then press and hold its power and volume down buttons at the same time for a few seconds until you boot into bootloader. From there you can access the recovery using the volume buttons.
You can also type:
adb reboot-bootloader
In a command Window and then go to recovery using the volume buttons.
The stock recovery has an android laying on its back (or face down, can't remember right now).
By the way, a little tip: you won't see any options in the stock recovery unless you press and hold the power button and press the volume up once. I mention it because you may need it someday
Cheers

Mercado_Negro said:
Yes, that's OK.
You see the stock recovery for yourself by turning off your device (unplug from charger if that's the case), and then press and hold its power and volume down buttons at the same time for a few seconds until you boot into bootloader. From there you can access the recovery using the volume buttons.
You can also type:
adb reboot-bootloader
In a command Window and then go to recovery using the volume buttons.
The stock recovery has an android laying on its back (or face down, can't remember right now).
By the way, a little tip: you won't see any options in the stock recovery unless you press and hold the power button and press the volume up once. I mention it because you may need it someday
Cheers
Click to expand...
Click to collapse
I like seeing the kindness you shared here. For the sake of many I thank you. Though I've been helping for several years its more often I find [email protected]@holes responding as though they were born with the device and Google code 101 in their hands. I do not tolerate smartarses or lazy but I do find it nice to see people helping. Thanks again..
Sent from my Nexus 4 using xda premium

Droid2drummer said:
I like seeing the kindness you shared here. For the sake of many I thank you. Though I've been helping for several years its more often I find [email protected]@holes responding as though they were born with the device and Google code 101 in their hands. I do not tolerate smartarses or lazy but I do find it nice to see people helping. Thanks again..
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Those words mean a lot to me, thanks. It makes it worth the effort
Have a beautiful day/night, kind sir!
Cheers

Mercado_Negro, I don't have words to thank you ! This is what the forum exits for, I myself helping as much as I can to others with things that I know, instead of telling them to go and search for syntax or other solutions . You helped me so much !!
I wish that most of the forum members will be kindly like you .
Regarding to the recovery, also my previous custom recovery ("Open Recovery") looked like the stock one with an Android lying on his back and some rows of data under him so I cannot see the difference visually.
Maybe there is an app for knowing what is your system data which can verify I have the stock recovery now.
Thanks!

isotoper said:
Mercado_Negro, I don't have words to thank you ! This is what the forum exits for, I myself helping as much as I can to others with things that I know, instead of telling them to go and search for syntax or other solutions . You helped me so much !!
I wish that most of the forum members will be kindly like you .
Regarding to the recovery, also my previous custom recovery ("Open Recovery") looked like the stock one with an Android lying on his back and some rows of data under him so I cannot see the difference visually.
Maybe there is an app for knowing what is your system data which can verify I have the stock recovery now.
Thanks!
Click to expand...
Click to collapse
You're welcome!
No, that's not the recovery, that's the bootloader. Once you're there, push your volume buttons until you see an option called "Recovery Mode". one you see it, push your power button and it will take you to recovery. There you'll see another Android laying on its back but no letters below. That's the stock recovery.
The openrecovery a.k.a. TWRP is very different and you'll notice the difference right away

Yes it is, great.
Thank you very much sir.

Related

Semi-Bricked myTouch 4G

Alright I have a semi-bricked mytouch 4G. (a friend's phone) I followed the gfree guide and did the hboot flash and now I'm in a boot loop. I have the original boot screen loaded and I can get to the recovery menu. S is off so the phone is rooted. How do I get CWM on the phone so I can install a new ROM and kernel so I can unbrick this thing. With my verizon fascinate I have options to go from where I am stuck (Odin and .md5 files). Where do I go from here? Can somone give me a step by step without pointing me to a different forum? I have searched for more than a couple of hours and this is where I have found myself.
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
darinmc said:
Did you go into a bootloop because of the rooting process? What did you do once you rooted the phone? Did you download ROM Manager? Need a lot more info about what was done in order to help you. You can flash cwr through adb, but before we get there I think you should break down exactly what happened post-root.
Click to expand...
Click to collapse
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
fsuagentsmith said:
I beleive it was after rooting. I followed the directions for gfree rooting exactly (of at least so I think, however, we can see that is apparently wrong). Rebooted the phone to check that S-off and then was stuck at a boot loop with the my touch 4g boot screen.
Click to expand...
Click to collapse
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
I get sending recovery failed... any help from there?
fsuagentsmith said:
I get sending recovery failed... any help from there?
Click to expand...
Click to collapse
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
neidlinger said:
on your phone do you where it says "fastboot usb" on the HBoot screen? does that show up?
Click to expand...
Click to collapse
yes, I see that
fsuagentsmith said:
yes, I see that
Click to expand...
Click to collapse
ok I changed it to that screen on the phone while trying to push the recovery image. It worked!!!
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
neidlinger said:
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Where is the reboot recovery option? As I said in original post I'm familiar with Samsung Galaxy and CWM not so much this phone.
fsuagentsmith said:
Where is the reboot recovery option?
Click to expand...
Click to collapse
are you in Recovery or in Hboot? what color is the screen? black or white?
neidlinger said:
Awesome from here just go to the development section and pick out which ROM you like and use their directions for installing it.
as of currently i am using CM7.0.0 and my wife is using RoyalLiquid. Both are really nice ROMs.
Click to expand...
Click to collapse
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
neidlinger said:
are you in Recovery or in Hboot? what color is the screen? black or white?
Click to expand...
Click to collapse
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
fsuagentsmith said:
This is HBoot, Screen is white. My selections are Fastboot, Recovery, Factory Reset, etc. Do I select recovery?
Click to expand...
Click to collapse
Awesome!!! I see what you told me to do! When I select recovery this is CWM 3! Awesome. I will see where I can go from here. I still may have questions.
fsuagentsmith said:
I'm planning on using CM7. what do I select after? just recovery on the HBoot menu?
Click to expand...
Click to collapse
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
neidlinger said:
Select recovery from the HBoot menu. That should reboot the phone into recovery. Once you are their select mount, then USB and store the ROM and the Gapps on the SDcard
Wipe the phone
select flash .zip from SDcard
Select the option for you to pick the .zip
flash the ROM
Flash the Gapps
Fix permission via the advanced menu
reboot the phone.
Click to expand...
Click to collapse
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
fsuagentsmith said:
Many thanks. I am up and running now on CM7. Looking at kernels to add to the tweak. Thanks again.
Click to expand...
Click to collapse
glad to see you got it going.
just make sure to do nandroid backups prior to flashing any new Kernels and make sure they are compatible with AOSP 2.3 ROMs.
neidlinger said:
Since you have the engineering Hboot. this isn't that big of a problem, but you do need the ADB drivers at the bare minimum... use the blue link in my signature to get those up and running if you don't already.
first things first you need a recovery image.
Download this recovery image Download from here
Once you download it store the image only in the tools folder of your SDK or your c:\adb folder if you used True_blues method
now boot into your Hboot screen and plug the phone into the computer
go to your CMD prompt and type
Code:
fastboot devices
it should show you the serial number of the phone
if it does
then change your drive to the tools folder... basically where ever you store that image....
then type
Code:
fastboot flash recovery recovery.img
it should show you something like
Code:
sending 'recovery' (3426 KB)... OKAY [ 1.172s]
writing 'recovery'... OKAY [ 0.797s]
finished. total time: 1.969s
if it does unplug the phone and use the volume keys to navigate to the reboot recovery option
once you are their you can flash any ROM you want.
Make sure to update the recovery image to 3.0.2.x once you are up and running.
Click to expand...
Click to collapse
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
steb0ne said:
Heeeeelp??? I'm having the same issue with the boot loop. My phone locked up when tried flashing CM7 and failed to restore my nanbackup. I can't boot to CM recovery anymore and when I tried to run that command, I'm getting "writing recovery.... FAILED <remote: image update error>"
*Note, that link u posted to download the recovery img is down
Click to expand...
Click to collapse
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Nicgraner said:
Can I get some background info?
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Well, I was rooted and had been running the leaked 2.3 stock rom. Decided I wanted to try CM7...and flashed it and it appeared to flash okay b/c I was able to boot up, but I couldn't get gapps to install, so I ended up trying to restore from my backup, and that failed, and I couldn't get back to CM recovery. So, I'm stuck in a constant boot loop.

CWM vs TWRP recovery

What is the Difference between CWM vs TWRP recovery and which one is best for the my nexus 7
Any idea?:highfive:
OLYMPIAKOI said:
What is the Difference between CWM vs TWRP recovery and which one is best for the my nexus 7
Any idea?:highfive:
Click to expand...
Click to collapse
Both are relatively similar. I would have to take the side of TWRP at least on the N7. Last time i tried to flash something with CWM it didnt wipe correctly or flashed incorrectly and ended up with a courrpt ROM. Had to redownload and reflash with TWRP and it was fine. Dont know what it is with CWM on this device but on my Gnex it was just fine. As of right now i would stick to TWRP. It also doesnt do the whole blob deal for nandroids which IMO isnt quite ready and causes issues. At least in my experience.
Installation
ÜBER™ said:
Both are relatively similar. I would have to take the side of TWRP at least on the N7. Last time i tried to flash something with CWM it didnt wipe correctly or flashed incorrectly and ended up with a courrpt ROM. Had to redownload and reflash with TWRP and it was fine. Dont know what it is with CWM on this device but on my Gnex it was just fine. As of right now i would stick to TWRP. It also doesnt do the whole blob deal for nandroids which IMO isnt quite ready and causes issues. At least in my experience.
Click to expand...
Click to collapse
And where should I Flash TWRP?
1. Boot
2. Bootloader
3. Recovery
4. System
5. Userdata
Which Option shouldI choose?
D/L Goo.im from the PlayStore and install TWRP from there.
Sent from my Nexus 7 using xda app-developers app
OLYMPIAKOI said:
And where should I Flash TWRP?
1. Boot
2. Bootloader
3. Recovery
4. System
5. Userdata
Which Option shouldI choose?
Click to expand...
Click to collapse
Reboot to bootloader
open command prompt or terminal
type:
Code:
fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
(or whatever its called)
hit enter
You should see something like this:
Code:
[email protected]:~/Downloads$ fastboot flash recovery openrecovery-twrp-2.3.1.1-grouper.img
sending 'recovery' (7064 KB)...
OKAY [ 0.931s]
writing 'recovery'...
OKAY [ 0.489s]
finished. total time: 1.420s
[email protected]:~/Downloads$
then use the volume keys to ether select reboot or reboot to recovery
dparrothead1 said:
D/L Goo.im from the PlayStore and install TWRP from there.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yep!
I just did it as I had a problem with CWM, in goomanager you just go settings and choose "install open recovery" when it has downloaded you then select "reboot recovery" and that's it.
I think I like it better than CWM already, I like being able to name my backups as I do them, very handy.
ROOT
OK I have istalled TWRP ,
Now, HOW DO I ROOT IT?
OLYMPIAKOI said:
OK I have istalled TWRP ,
Now, HOW DO I ROOT IT?
Click to expand...
Click to collapse
Easily with either one of these.
http://forum.xda-developers.com/showthread.php?t=1766475
http://forum.xda-developers.com/showthread.php?t=1809195
I've used the latter.
OLYMPIAKOI said:
OK I have istalled TWRP ,
Now, HOW DO I ROOT IT?
Click to expand...
Click to collapse
Flash a superuser package or flash a custom ROM.
Sent from my Nexus 7
I have always used CWM on my phone for no reason other than that was what came w/ the kernal or rom pick of the day. Using the Nexus 7 Toolkit http://forum.xda-developers.com/showthread.php?t=1809195 I installed CWM, or tried to, ended up going to the play store for touch.
I have tried holding the power key, powerkey + vol, power++ or - vol and can not get into CWM to no avail. Yes it was connected to USB. I have to use Rom Manager to get to it. Just thinking if something/everything locks up there should another way to get to recovery.
Can I have both Twerp and CWM at the same time?
No. One recovery at a time.
But if you have root access all you need to do is get the terminal emulator from the market type :
Su(enter, grant root)
Reboot recovery
Or if you have adb on your computer (which you really should of you're going to be flashing anything) Just make sure you have. Usb debugging on and type: adb reboot recovery.
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
studacris said:
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
Click to expand...
Click to collapse
Thanks.....That's what I thought....didn't happen.
studacris said:
No. One recovery at a time.
But if you have root access all you need to do is get the terminal emulator from the market type :
Su(enter, grant root)
Reboot recovery
Or if you have adb on your computer (which you really should of you're going to be flashing anything) Just make sure you have. Usb debugging on and type: adb reboot recovery.
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
Click to expand...
Click to collapse
There are also apps like Quick Boot if you don't want to have to type in the terminal window each time you want to go to recovery
studacris said:
Btw the button combo is all three buttons(both volumes and the power button to boot into the bootloader the use the volume keys to toggle the option to recovery mode and hit the power button to confirm.
Click to expand...
Click to collapse
Vol Down and power is all it takes for me from a powered down state. The All-Three button is for hot-reboots.
a5ehren said:
There are also apps like Quick Boot if you don't want to have to type in the terminal window each time you want to go to recovery
Click to expand...
Click to collapse
+1 for Quick Boot
With the N7 running, I have found that if I hold the power button down with or without combos for 15-20 sec. it'll reboot, not just shut down. And yes, when starting with the power & -vol it starts in fastboot. I guess I assumed that it would behave just like my sg4g....live and learn .
I'm using ROM Manager to get to TWRP. Haven't decided which I like best twrp or cwm.
My thanks for putting up w/my noobie questions!
Sent from my Nexus 7 using xda premium
TheAtheistReverend said:
Vol Down and power is all it takes for me from a powered down state. The All-Three button is for hot-reboots.
+1 for Quick Boot
Click to expand...
Click to collapse
Firstly, love your username.
And You're right about the button combo.. I thought I was in the section for my phone lol.
Apps such as that are useful enough I spose.
Power tool is what I used back when my phone first came out and there was no rom with an extended power menu.
Was written by an xda recognized developer and good friend of mine, flappjaxxx
link to power tool if you wanna check it out

Nexus 4 stuck in bootloader no recovery

hello i tried to download and flash paranoid ROM on my nexus 4 after some time i dnt like it so try to revert back to nexus 4 stock rom but something went very wrong and now my phone stock in boot loader
wen i try to switch on my phone it directly goes to boot loader i cnt do anything if scroll down and go to recovery my phone went black and its also not starting that.
wen try to connect my phone to computer to recover it ...most of the tool kits showing msg that u dnt have usb debugging on
Please help how to recover my phone
I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 08:06 AM ---------- Previous post was at 08:04 AM ----------
This is the took kit that I used and I had no debug on
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
Zehlek said:
I had that issue once with when flash back from PA. I have to flash IMG files using a toolkit
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx
You'll have to do it the old fashioned way, i.e. use fastboot. If you're not familiar, don't rush it, research each step and ensure you have the drivers set up, adb and fastboot installed, etc...
Did you flash the stock recovery back on? IIRC once selecting Recovery from the bootloader you're presented with a black screen, and then must hold the power button for a second or two and then the stock recovery will show up. Limited options available however, wipe data, cache, etc...
http://forum.xda-developers.com/showthread.php?t=2010312
core81 said:
Can u please tell me whice toolkit i should use and what is the procedure to do that many thanx
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
First select 1 to install drivers. Then download Google factory image and put Boot, System, Recovery in folder(to flash IMG files) in your toolkit folder. Then use option 11 to flash each one. Make sure you are in bootloader mode
axtzenswas
Zehlek said:
http://forum.xda-developers.com/showthread.php?t=1995688
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time
core81 said:
okay i ll try and get back to you..but should my computer can identify the device in boot loader mood?
any way i ll try the stock recovery method also and get back to you guys
many thanx for your time
Click to expand...
Click to collapse
fastboot commands work from BL, adb doesn't. So long as the drivers are installed you will be able to see your phone.
https://developers.google.com/android/nexus/images#occam
That is the link to the factory images for the nexus 4.
http://forum.xda-developers.com/showthread.php?p=42407269
That is the fastboot you will need. (FOR WINDOWS)
turn off the phone and plug it in to fully charge it.
install fastboot
extract the files from the factory image into the fastboot folder.
turn on the device and leave it in the bootloader. (if need be turn off the device and hold vol up and down plus the power until you see bootloader)
run "fastboot devices", this will list any devices that fastboot sees. if your device is not in the list something more is wrong.
This images shows "adb devices" but it is the same output for "fastboot devices" https://sites.google.com/site/rodsmods13/_/rsrc/1370839220039/home/example screenshot.png
now run the "flash-all.bat"
dl200010 said:
...now run the "flash-all.bat"
Click to expand...
Click to collapse
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.
dl200010 said:
Yeah I completely forgot that! I don't have the image downloaded to look at to list the commands to install without using the bat file.
Click to expand...
Click to collapse
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff
CMNein said:
bat file is definitely the way to go however*, I've grown to hate typing terminal commands :laugh:
*Except for that one time I forgot to edit stuff
Click to expand...
Click to collapse
I admin three Linux headless servers, so it is like second nature to me. Maybe best route for him is for one of us to modify the bat and post it.
Sent from my Nexus 4 using XDA Premium 4 mobile app
CMNein said:
Although a reminder that running the bat file without removing the userdata.img file from the zip, and editing the -w out of the bat file will wipe the sdcard in case the OP's is still intact.
Click to expand...
Click to collapse
my frnd can u please explain little bit more about the process
THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot
core81 said:
my frnd can u please explain little bit more about the process
Click to expand...
Click to collapse
One you have the factory image in hand and have the following files extracted to your platform-tools folder, you'll want to keep on opening the archives until you're left with the following, but don't extract anything from the zip file:
-bootloader-mako-makoz20i.img
-radio-mako-m9615a-cefwmazm-2.0.1700.84.img
-image-occam-jwr66y.zip
-flash-all.bat
You'll want to open the image .ZIP and delete userdata.img.
Then open the flash-all.bat and delete the -w as seen on line 23 in the screen capture.
core81 said:
THANKS TO CMNein dl200010
MY PHONE IS BACK TO NORMAL
thanks alot
Click to expand...
Click to collapse
Awesome, I see you got yourself sorted out while I was replying :highfive:

Help - I'm stuck in a bootloop 4 circles !

Hi I just tried to flash Android 4.4.4 without wiping & losing root using Nexus Root Toolkit
as per this link trendblog.net/flash-android-4-4-4-without-wiping-and-loosing-root/
I had slimkat 4.4.4 and tried to put stock 4.4.4 on this
After success messages the toolkit told me to wait for it to boot up but I am stuck on the four circles.
I have no recovery !!!
What can i do ?
Stop using took kits. They're nothing but trouble. Flash the factory image in fastboot and start over
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
First Google 15 second adb install xda. That'll set up fastboot on your PC. Then download the factory image. Google nexus 4 factory image. Extract that using 7-zip or winrar. In there is a flash-all.bat. just double click it. It will wipe your device so backup off the device first
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
k500zm said:
Yes I know I've been foolish to use a kit
Please can you tell me what I need and the steps to do this ?
Click to expand...
Click to collapse
Here is an excellent guide how to use fastboot:
http://forum.xda-developers.com/showthread.php?t=1907796
It is guide for Nexus 7, but the proceeding is just identic like with all other Nexus devices.
tetakpatalked from Nexus 7 flo
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Also is it possible to get my files from the device before I wipe ?
I never used fastboot before - but I'm gonna learn fast now !
Click to expand...
Click to collapse
You say you can't boot into recovery? That's going to be a problem retrieving data
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Is there no way to get cwm back on there ?
k500zm said:
Is there no way to get cwm back on there ?
Click to expand...
Click to collapse
Maybe, you'll need fastboot for that too. Download the latest image file from here. Rename it recovery
http://techerrata.com/browse/twrp2/mako
We'll go from there. You're going to learn a lot more than you bargained for
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
k500zm said:
Thanks guys. I am in a bit of a panic here.
couple of questions
Click to expand...
Click to collapse
If my usb is connected will the nexus 4 take power from it so my battery will not drain completely ?
Click to expand...
Click to collapse
Correct, but I'm not sure for the bootloader mode. I don't own a N4. Rather charge your battery first, it should work.
Also is it possible to get my files from the device before I wipe ?
Click to expand...
Click to collapse
If you're lucky, ADB might work even in bootloop if USB debugging was enabled in the developer options. As you didn't wipe, there is a small chance ADB pull might work.
IMHO the best you can do is to flash any custom recovery like TWRP or PhilZ with fastboot. The recovery.img file must be saved in the same folder where fastboot.exe is.
I assume Google USB driver is properly installed?
Fastboot must work, check in the guide I posted link for in my first post here how to check that fastboot commands are working. If "fastboot devices" returns "(your N4 serial No) fastboot" and your custom recovery is saved in proper folder, enter in CMD:
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
After that, enter recovery mode, there is another chance your ADB pull function might work. The phone should charge in recovery mode.
To install SlimKat again, format: system, data, cache, dalvik cache (TWRP) or choose factory reset and "clean to install new ROM" in PhilZ. Then flash ROM and Gapps, best with ADB sideload.
tetakpatalked from Nexus 7 flo
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
k500zm said:
Ok I'm all ears and eager to learn
Ok downloaded - renamed to 'recovery.img'
Click to expand...
Click to collapse
Did you install fastboot with the 15 second adb install?
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
I have installed Android SDK manager and the 15 sec drivers
I have android bootloader interface in my xp device manager
k500zm said:
I have installed Android SDK manager and the 15 sec drivers
Click to expand...
Click to collapse
OK, we'll try with that. Put your recovery image in the same folder as fastboot.exe. Open a command window in that folder, shift right mouse click in a open area in that folder
Plug your device into the USB port. Type
fastboot devices (return) in the cmd window
Is your device recognized? If it is then in the cmd window type
fastboot flash recovery recovery.img
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
ok - this is what I got...
C:\adb>fastboot devices
fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
k500zm said:
ok - this is what I got...
C:\adb>fastboot devices
01...... fastboot
C:\adb>fastboot flash recovery recovery.img
sending 'recovery' (7928 KB)...
OKAY [ 0.250s]
writing 'recovery'...
OKAY [ 0.453s]
finished. total time: 0.703s
C:\adb>
Click to expand...
Click to collapse
That sounds excellent, mate! Now try to reboot into the recovery mode
BTW: it isn't recommended to write down your device's serial No in worldwide public forum, it is your privacy in fact. Best edit your post now and remove big part of it (I also did it im my quote of your post)
tetakpatalked from Nexus 7 flo
k500zm said:
Ok I have TWRP started on my device [ i use cwm though will my nandroid backup be compatible with twrp ?]
Click to expand...
Click to collapse
Good job. The nandroid won't be compatible. Let me see if I can find a cwm image. Now that you know how to use fastboot
Sent from my Nexus 5 using XDA Free mobile app
I have a nandroid backup from cwm just before i fcud up - is there any way to restore this ?
Thanks for your help so far geezers

[GUIDE] How to Unlock the Bootloader, Flash a Factory Image, and Return to Stock

This guide will help you unlock your bootloader, flash a factory image, and return you to a stock device. It is wriiten assuming you have a windows PC (MAC users, see post 2). This can be helpful if you need to RMA your device or if you are getting erratic behavior or messed something up.
Tools and Files You’ll Need
If you don’t have adb and fastboot installed on your PC go here for a quick install of the necessary files, thanks to @Snoop05, http://forum.xda-developers.com/showthread.php?t=2588979
For MAC users go here. http://forum.xda-developers.com/showthread.php?p=32305619
For Linux users, http://forum.xda-developers.com/showthread.php?p=10746225
For the factory image go here, https://developers.google.com/android/nexus/images You’ll download a .tgz file. Use winrar or 7-zip to extract the file to its own directory and remember where that directory is. Inside is another zip file, extract that too. You’ll need those image files if you use the long method to install the factory image. It’s also good to know where they are as they come in handy as you get more familiar with fastboot and what you can do with it.
How To Unlock the Bootloader
If you don’t have developer options enabled on your device go to settings, about device and tap on the build number 7 times.
In settings, developer options enable oem unlock
Now you get to use fastboot! Boot you device into the bootloader, vol up + power with your device shut off. Once booted into the bootloader connect it to your PC with the usb cable and open a command window on your PC. Once connected type the following command in the cmd window:
fastboot devices (Your device serial number should show up and this will ensure fastboot is working properly)
​Then type:
​fastboot oem unlock (This will unlock the bootloader and you’re now good to go)​
NOTE, UNLOCKING THE BOOTLOADER DOES WIPE YOUR DEVICE SO BACKUP OFF YOUR DEVICE FIRST
How To Flash the Factory Image, SHORT METHOD
Open a command window on your PC in the same directory as you extracted the factory image. In that directory shift, right click in an open area and use “Open a command window here”
Boot your device into the bootloader and connect it to your PC. Then simply double click on the flash-all batch file. Note that there are batch files in there that will work for Windows as well as Linux machines
Let the batch file run and when it’s done you’ll be back to stock.
NOTE THAT FLASHING BY THIS METHOD DOES WIPE YOUR DEVICE SO MAKE SURE YOU BACKUP OFF YOUR DEVICE FIRST.
How To Flash the Factory Image, LONG METHOD
In this method each factory image is flashed separately. This should be used if you have problems with the short method and as you get more familiar with fastboot you’ll be able to flash only the images that you need for your specific requirement. For instance, you might want to only flash the stock recovery if you’re trying to take an ota and you’ve installed a custom recovery. The order that you flash the images is not important.
In the folder you extracted the factory image it’s easiest if you re-name the bootloader image file to simply bootloader and radio. Then open a Windows command window in that folder and use the fastboot commands:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader
fastboot –w (NOTE, this command does wipe your device. It’s possible to flash the factory image without this command but if you’re going from different revision numbers of android it’s highly recommend to wipe the device)
Now open a Windows command window in the same folder that you extracted the zip file in, the one where you find recovery, system, etc. Then run the fastboot commands:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img [Note, flashing system takes a long time, so let it do it's thing]
fastboot flash vendor vendor.img
Congratulations, you’ve now flashed a factory image and learned how to use fastboot!
For MAC users, proceed each fastboot command with a ./ e.g. ./fastboot flash boot boot.img
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
GedBlake said:
This should be made a 'sticky'...
An excellent well written tutorial... succinct, clear and to the point.
Far better to use fastboot instead of a toolkit... Everything is more transparent, and you actually gain a better understanding of your device as a result.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks @GedBlake. I would have responded sooner but I had to get home and check my tablet. Actually both work, vol up + power and vol down + power.
Sent from my Nexus 9 using XDA Free mobile app
But.... Toolkit so easy?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639!
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought.
Edit : That ^^^^ was a hint to other members to get your guides, tutorials, info threads, FAQ... Etc... Going..... This is a Nexus section after all. :silly:
Darth said:
But.... Toolkit so easy? ?
(agreed... Toolkits not the best choice)
Thread stuck. Great guide @jd1639! ?
If we get enough guides, tutorials, how to's and other great info threads.... I would suggest a "sticky roll up" thread, so too many stickies aren't created.
Food for thought. ?
Click to expand...
Click to collapse
I'll keep an eye it and do a roll up when the need arises
Sent from my Nexus 9 using XDA Free mobile app
cant flash system.img
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
nyasha1935 said:
I Xubuntu 14.04 I can't seem to flash the system.img I get the following error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.032s
Click to expand...
Click to collapse
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
cam30era said:
It's possible that you need to update your Android SDK to the latest. There was a recent change (within last 6 months) to fastboot to allow flashing these large .img files.
Click to expand...
Click to collapse
Ok thanks gonna try on windows, im a noob on linux
nyasha1935 said:
Ok thanks gonna try on windows, im a noob on linux
Click to expand...
Click to collapse
You'll be sorry.....
cam30era said:
You'll be sorry.....
Click to expand...
Click to collapse
Ok back to linux, how do I update android SDK
nyasha1935 said:
Ok back to linux, how do I update android SDK
Click to expand...
Click to collapse
http://rootzwiki.com/topic/20770-gu...-adb-and-fastboot-in-linux-ubuntu-and-mint12/
Is it possible to flash a factory image using a custom recovery like TWRP?
Sent from my Nexus 9 using Tapatalk
iamroddo said:
Is it possible to flash a factory image using a custom recovery like TWRP?
Click to expand...
Click to collapse
Is it possible to extract the .img from the volantis-lmy47x-factory-3efdc8d4.tgz from https://developers.google.com/android/nexus/images and flash them individually with TWRP (with the exception of recovery.img, which I guess would over-write TWRP)? Can it this be done directly from 5.0.1 or would I need to first upgrade to 5.02?
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Leoncino said:
Hi, I'm Italian so i'm sorry if my english is bad xD what happens if i flash a different kernel? Will i lose my warranty?
If yes, if i flash the factory image, will i have my warranty again?
And, again, sorry for my bad english
Click to expand...
Click to collapse
No need top apologize. You're English if fine.
There's a lot of discussion and lack of agreement about what affects the warranty on the Nexus 9. HTC says that even unlocking the bootloader "may void the warranty".
My advice would be to do what you want to it, but make sure you understand what you are doing. Ask a lot of questions before you do something you're unsure of.
Unlock your bootloader (if you haven't already). Do not relock bootloader if something goes wrong (this does not solve anything). With an unlocked bootloader, you can recover from almost any problem.
And you can flash the Google factory images anytime you want to return to stock.
I'm sorry there's not a clear answer to your question.
cam30era said:
No need top apologize. You're English if fine.
Click to expand...
Click to collapse
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Leoncino said:
Thanks
So it's like Samsung knox, we don't know what happens to our device.
An other little question? Is the same if i root my device? Need to unlock bootloader?
Click to expand...
Click to collapse
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
cam30era said:
Bootloader has to be unlocked to root, install custom recovery (TWRP). And note that when you unlock bootloader, it will wipe the contents of your SDcard. If you have anything important there, back it up on your PC.
Click to expand...
Click to collapse
And what happens if i lock again my bootloader, will i restore the warranty?
Leoncino said:
And what happens if i lock again my bootloader, will i restore the warranty?
Click to expand...
Click to collapse
That's a good question, without a clear answer (unfortunately).

Categories

Resources