Database Users

Can't Put Back Default Recovery?!

Hi Everyone!
I'm new here so I'm sorry if this has already been answered.
On my Nexus 7 which I rooted and unlocked, I still have the default/stock OS but put CWM recovery. Now I realise I want to put back the default one Google had on there but when I try to re-flash the recovery using fastboot flash recovery recovery.img , it seems to work
Code:
./fastboot flash recovery recovery.img
sending 'recovery' (5234 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.200s]
finished. total time: 1.904s
Except when re-booting into recovery, it shows this weird image that seems to be an error. See the attachment "screenshot" image.
So, is there any way to put back default recovery, while keeping root?
Thanks!
Michael

I'm pretty sure that image is the default recovery image on the Nexus, I think you need to reflash CWM, or try relocking then unlocking your BL and then flashing.

Use the nexus toolkit and choose the option to rename recovery restore files, and then choose the option to flash stock recovery

That is the stock recovery, once that picture comes up with the android hit power+vol up again and the options should come up
Sent from my SCH-I535 using XDA

Hi!
So by using the Nexus 7 Toolkit AND THEN the power/volume up. I got into the regular recovery again. Thanks! Michael
Sent from my Nexus 7 using XDA Premium HD app

problems with stock recovery
I'm in a similar position as the OP but cant get stock recovery to show options:
First, I unlocked and rooted, then flashed CWM 6 recovery via ROM manager with the idea of trying some different ROMs
Then, I realised that I'd prefer to stay Stock for now, with OTA updates etc, so I followed this guide to manually flash stock recovery.
When I tried to enter recovery (using Quick Boot or manually from the bootlocker screen) I got as far as the android with the red triangle, but could not get any options to show, no matter what combination of buttons I pressed.
Next, I installed the root toolkit (I'm on OSX so it's installed in my bootcamp windows XP partition - not sure if that is relevant) and flashed stock recovery that way. I got stuck at the same screen as point 2 above.
Finally, I have tried the rename files recommendation above, in toolkit, and re-flashed stock recovery in the toolkit, but I still cant get any option on the red triangle screen
Bearing the USB connection bug in mind, I've tried with USB connected, and disconnected, with USB debugging and without. Nothing makes a difference.
In desperation, I removed any CWM recovery files incase they might (!) be causing a problem, but I am unable to remove the file titled 'blobs'.
thanks in advance for any help.
I'm guessing this means my recovery is shot ... is there any way to save this, other than use a 3rd party recovery?

in addition, I've just flashed back to the factory image on the toolkit, but I'm still getting no stock recovery options.

greenglue said:
Hi Everyone!
I'm new here so I'm sorry if this has already been answered.
On my Nexus 7 which I rooted and unlocked, I still have the default/stock OS but put CWM recovery. Now I realise I want to put back the default one Google had on there but when I try to re-flash the recovery using fastboot flash recovery recovery.img , it seems to work
Code:
./fastboot flash recovery recovery.img
sending 'recovery' (5234 KB)...
OKAY [ 0.704s]
writing 'recovery'...
OKAY [ 1.200s]
finished. total time: 1.904s
Except when re-booting into recovery, it shows this weird image that seems to be an error. See the attachment "screenshot" image.
So, is there any way to put back default recovery, while keeping root?
Thanks!
Michael
Click to expand...
Click to collapse
It did work.
Plus re-read the first 23 words of Post# 2

gunner1937 said:
It did work.
Plus re-read the first 23 words of Post# 2
Click to expand...
Click to collapse
Is this in response to the OP or to my further query? The OP has solved his issue, but as mine was similar, I thought I'd add it on.
If your response was to me, I have tried locking and unlocking, and I'm not sure why re flashing Cwm would help either the OP or me (as per the first 23 words of post #2) as we both wanted to get away from CWM and back to full stock, and albeit rooted full stock.

eager27 said:
Is this in response to the OP or to my further query? The OP has solved his issue, but as mine was similar, I thought I'd add it on.
If your response was to me, I have tried locking and unlocking, and I'm not sure why re flashing Cwm would help either the OP or me (as per the first 23 words of post #2) as we both wanted to get away from CWM and back to full stock, and albeit rooted full stock.
Click to expand...
Click to collapse
My Post was a reply to the OP.
I tried to correct my Post regarding Post #2. I meant "read the first 13 words.
Sorry for the confusion.

gunner1937 said:
My Post was a reply to the OP.
I tried to correct my Post regarding Post #2. I meant "read the first 13 words.
Sorry for the confusion.
Click to expand...
Click to collapse
No problem.

eager27 said:
Is this in response to the OP or to my further query? The OP has solved his issue, but as mine was similar, I thought I'd add it on.
If your response was to me, I have tried locking and unlocking, and I'm not sure why re flashing Cwm would help either the OP or me (as per the first 23 words of post #2) as we both wanted to get away from CWM and back to full stock, and albeit rooted full stock.
Click to expand...
Click to collapse
OMG Thanks man !! You don't even know how many hours I tried to fix my recovery... All I had to do to show up the menu was power + volume up *Angry*

[Q] Did I brick my Nexus 4?

Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil

I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?

ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.

Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.

aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).

aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.

You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app

try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688

Okay, thanks guys. I'm on it. Will let you know when I'm done.

That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd

I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?

aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.

chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images

aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.

chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:

Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!

[Q] Unable to Flash Nexus 7

hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks

Why were you trying to flash the bootloader? Were you trying to update to 4.18?

Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..

Anyway, is it normal for the bootloader flash attempt to fail?

hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.

korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...

This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.

hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked

hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help

hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first

ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?

hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.

ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild

tried to flash stock rom using wug's rootkit..
this is what happens...

hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?

Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis

I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.

hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.

[Q] [Softbricked[ Help! Accidentally flashed recovery image to boot partition...

Ok, so I unlocked my Nexus 7 (2013). Then I was trying to root it and after booting it into the bootloader, I typed:
"fastboot flash boot twrp.img" I was supposed to type "fastboot flash recovery twrp.img"
PLEASE HELP! My device boots into TWRP EXCLUSIVELY!
How do I get my os back? Is it gone? Can this be easily fixed?
I will be eternally in your debt if you can help me out, I feel so stupid, this is the first time I've bricked something and I've been unlocking, rooting, flashing android devices since my G1, then my Nexus One, which I even repartitioned the system partition so it could fit 4.2.2 Cm 10. I also unlocked, my touch pad and flashed cm dual booting with web os. Unlocking/rooting/flashingcustomrecovery on my Nexus 4 was a one click though so I guess I was rusty.
Edit: messed up a bracket in the title... Great...

I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app

Coronado is dead said:
I am not an expert, but I think you'll be fine flashing a ROM image as that will install the boot files. I'd get confirmation though.
But no crying!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I don't have a rom image on my device though? How can I get one on there when I can only get into the bootloader or recovery...
Thanks for responding! I hope I can get this fixed...

In TWRP I think there is a way to mount USB and transfer it over. Maybe under advanced?
Sent from my Nexus 7 using xda app-developers app

Hmm maybe someone could make a .zip file to flash the boot loader in twrp

And there is always the option of getting the factory image from Google and using it over USB with fastboot on. Clean slate.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:54 AM ---------- Previous post was at 12:53 AM ----------
How to factory image restore:
http://www.androidpolice.com/2013/0...stock-using-a-full-factory-image-and-root-it/
Sent from my Nexus 7 using xda app-developers app

Flash any custom kernel, as it stands as "boot" partition.
Or just flash the boot image manually from the factory image:
Code:
fastboot flash boot boot.img
Then flash TWRP like normally you did before:
Code:
fastboot flash recovery recovery.img
Sent from my Galaxy S3 i9300

If you can go to bootloader or TWP, then you have many choices to fix your Nexus.
1. Download a factory image from Google, boot to bootloader and flash the whole thing. And remember to download the right factory image for Nexus 7(2013) (flo or razor). Check MD5 after downloading to make sure everything is OK. If you dont know how to flash a factory image, there is a couple topics in General and Q&A to assist you.
2. Or you can download a custom kernel in the Original Development area. THen boot to TWRP, use ADB to push the custom kernel file to your device, then install it by TWRP.
3. You can use a toolkit which I dont recommend.

Ok, so in my frantic attempts to fix this, I was trying to get adb sideload to work and was told to try and do a factory reset and wipe system and internal storage. I did this and still can't figure out how to get sideloading to work, I'm trying adb sideload rom.zip, and adb push rom.zip /sdcard which is what I read from another thread, but have not been able to get the factory image over.
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>

OH GOD!
Download the Factory Image of Android 4.3 for ‘razor’ Nexus 7 tablet from here.
> this download contains the full system, bootloader, recovery and kernel boot img files.
Extract the ‘tgz’ factory image archive and place all contents into a single folder.
Next, you will need to edit a file so that your data will not be wiped. If you want to wipe data then you should skip this step.
> so, edit the ‘flash-all.bat’ for Windows or ‘flash-all.sh’ for Mac / Linux using a text editing tool:
- you will need to edit the ‘fastboot update’ command so that it will transform from ‘fastboot -w update image-razor-jss15j.zip’ into ‘fastboot update image-razor-jss15j.zip’. You will basically need to delete the ‘-w’ text, which is the command that tells fastboot to wipe data from your device.
- continue to the next step when you’re sure that the ‘-w’ text has been removed.
Now, power off your Nexus 7 2013 tablet.
Boot it into Bootloader Mode.
Connect it with your computer via USB cable.
Run the ‘flash-all’ script and wait for the factory image to be successfully installed.
Ok, so I did this, I downloaded the factory image, and ran the flash all command and that failed and now it's hard bricked! here is a screenshot of what the flash-all command output...
I will seriously pay someone to help me fix this at this point! I'm freaking out!
http://imgur.com/XsAJ4FV

mattj7 said:
Also, when I go to flash the .img that came with the factory image, fasboot says:
<code>sending 'boot' <2100 KB>....
OKAY [ 0.080s]
writing 'boot'...
FAILED <remote: image is not a boot image>
finished total time: 0.090s
</code>
Click to expand...
Click to collapse
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.

Never mind, the problem had been solved.

sfhub said:
You must have done something wrong. The boot.img that came with the factory restore is 6880KB not 2100KB.
Take things slow. You are still in a place where you can recover. If you make too many mistakes, you can make it even harder to recover.
Click to expand...
Click to collapse
Yes, it was the factory image for the first nexus 7, I just ran the flash all on the right one and now I can boot just fine
WHEW
Ok guys, great job everyone!
Now I'm going to figure out if the custom recovery is still there, it probably isn't, and I can just flash it with fastboot now.

slamdunksaliby said:
Hmm maybe someone could make a .zip file to flash the boot loader in twrp
Click to expand...
Click to collapse
The only way is by the fastboot way, because it's an .img file
And don't forget that you can find all files that you need to this thread => [Index] REPO for all you need for your nexus 7 FLO (2013)

philos64 said:
The only way is by the fastboot way, because it's an .img file
]
Click to expand...
Click to collapse
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:

Nburnes said:
Well, that is untrue. The bootloader .img is just a collection of other .img that get flashed to their respective partitions, such as aboot, sbl1, sbl2, sbl2b, sbl3, sbl3b, and rpm. :good:
Click to expand...
Click to collapse
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means

philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.

philos64 said:
Please I don't agree when you say it's untrue.
For most users, this is the easiest solution for this.
If you do a survey, I would like to see how many people know that you can flash by other means
Click to expand...
Click to collapse
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).

sfhub said:
Well, I know you can flash by other means.
I don't think he said it was the easiest to flash from twrp. He just said it could be done, which it can.
I think far more people have done it through recovery than have known they have done it.
Everyone who flashes the JSS15J OTA will get the bootloader flashed in the way he described. If twrp is using the same kernel as stock recovery, then it can be done in twrp also.
Click to expand...
Click to collapse
Nburnes said:
I'm not personally attacking you or anything and I am sorry if you took it that way.
I'm just stating that saying fastboot is the only way is not true. The partitions can easily be flashed through CWM/TWRP as they have been with, from my experience, Galaxy Nexus, Nexus 4, and Nexus 7 (2012).
Click to expand...
Click to collapse
No problem
But as I said, almost users don't flashed by the way of the partitions.
It would be better to say the easiest way
Sent from my HTC One using Tapatalk 4 between sky and earth

[Q] JWR66V Nexus 4 4.3 Stock Kernel?

I have a Nexus 4, 4.3 JWR66V , Stock ROM and on Franco's Kernel currently and am looking to OTA update to later builds and eventually KitKat.
I've got the OTA requests on my phone and am trying to return to STOCK (following Efrant's guide and other threads) so I can apply them. But I can't find a stock Kernel for JWR66V? There is one for JWR66Y which I understand should work, however when I load it to Boot (using WugFresh Nexus Toolkit) my phone does not switch on fully (blank screen).
Can you please point me in the direction of a JWR66V stock kernel that will work or help me figure out what I'm doing wrong?
Thanks!:good:

devesh254 said:
I have a Nexus 4, 4.3 JWR66V , Stock ROM and on Franco's Kernel currently and am looking to OTA update to later builds and eventually KitKat.
I've got the OTA requests on my phone and am trying to return to STOCK (following Efrant's guide and other threads) so I can apply them. But I can't find a stock Kernel for JWR66V? There is one for JWR66Y which I understand should work, however when I load it to Boot (using WugFresh Nexus Toolkit) my phone does not switch on fully (blank screen).
Can you please point me in the direction of a JWR66V stock kernel that will work or help me figure out what I'm doing wrong?
Thanks!:good:
Click to expand...
Click to collapse
Download Nexus Factory Images and flash it.

mohitgalaxy3 said:
Download Nexus Factory Images and flash it.
Click to expand...
Click to collapse
Thanks mate - again I'm struggling to find the Nexus factory images for JWR66V - I can only seem them for JWR66Y and this boot.img didn't work for me.

Flash the JWR66Y images... system, boot, recovery, radio, and bootloader. As long as you don't flash the userdata.img, your data won't get wiped.

chrisbo4 said:
Flash the JWR66Y images... system, boot, recovery, radio, and bootloader. As long as you don't flash the userdata.img, your data won't get wiped.
Click to expand...
Click to collapse
Ok thanks mate...going to try that right now and report back.
Are you (or anyone else) familiar with the Wug Fresh Nexus Root Toolkit? Is the Boot/Flash image utility in this a good way to flash images? The Boot image option lets you preview the .img and then reverts back to the old one upon reboot - sounds good to me but anything I should check/be wary of when using this?

devesh254 said:
Ok thanks mate...going to try that right now and report back.
Are you (or anyone else) familiar with the Wug Fresh Nexus Root Toolkit? Is the Boot/Flash image utility in this a good way to flash images? The Boot image option lets you preview the .img and then reverts back to the old one upon reboot - sounds good to me but anything I should check/be wary of when using this?
Click to expand...
Click to collapse
I have used Wug's toolkit in the past, however it bootlooped my device. I'm sure it was user error, but anyway decided to learn adb and fastboot. Long story short... no I'm not familiar with the toolkit, even though I used it once before. Any luck with flashing the images?

chrisbo4 said:
I have used Wug's toolkit in the past, however it bootlooped my device. I'm sure it was user error, but anyway decided to learn adb and fastboot. Long story short... no I'm not familiar with the toolkit, even though I used it once before. Any luck with flashing the images?
Click to expand...
Click to collapse
Ok thanks - have just refamiliarised with adb and fastboot now, and am mid way through flashing those img files! Shall update shortly

devesh254 said:
Ok thanks - have just refamiliarised with adb and fastboot now, and am mid way through flashing those img files! Shall update shortly
Click to expand...
Click to collapse
have flashed all of those files using adb fastboot - still says my kernel is the franco one though?!
i noticed after i flashed all of those files (the boot one being the last) that it rebooted with a blank screen. i then have to switch off, switch on, it turns on as normal but shows the kernel is still the same in settings.
just to check i am doing this right - i put the phone in fastboot mode and through a cmd prompt, flash each img one at a time. is there a way to flash them all at once? i suspect not all of them are flashing...

You can flash the "flashall.bat", that will flash all of the images in one command. That's strange that flashing the boot.img doesn't overwrite the franco kernel. Perhaps try to "fastboot reboot-bootloader" between each .img.

Hmm
Ok I managed to flash all the files now...bootloader radio boot recovery and system - but my phone is not switching on. It get's stuck at the Nexus X logo and doesn't go beyond that!
Any ideas please?
Update - just went in to the stock recovery and wiped cache too....seem to be stuck on the X but it says "Android is Upgrading too"....hopefully this will work now!

Good news - it all worked! Clearing the cache did the trick and I have now OTA'd all the way to 4.4.2!
Thanks for your help mate and everyone else :good::laugh: