Database Users

help! about factory image ota

fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:

sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?

xIC-MACIx said:
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
Click to expand...
Click to collapse
the development section. only dev question ? ok

sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
If you have the factory image, from Google (and nowhere else), just run the flash-all.bat file. You "may" have to unlock your bootloader prior to running it if you haven't already, and you'll need to have the device in fastboot mode prior to running the batch file too, but once those 2 simple tasks are done, the batch file takes care of the rest.
If your using a toolkit or some other method for flashing a factory image, I suggest stopping, and just doing the above.

This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...

craigacgomez said:
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
Click to expand...
Click to collapse
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english

lKBZl said:
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
Click to expand...
Click to collapse
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium

dboftlp said:
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
There is... i've seen a post in google + from a guy that links you to a google page with n10 4.2.1 img.

sikagoon7 said:
Nexus 10 hasn't gotten the (JOP40D) images yet which means the only way to get the 4.2.1 update is to get an OTA. I think the OTA link is floating around AndroidPolice and AndroidCentral somewhere but you'll have to look. Whatever images for 4.2.1 on the Nexus 10 are fake because Google hasn't even released them yet.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium

dboftlp said:
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..

lKBZl said:
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
Click to expand...
Click to collapse
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...

Watcher64 said:
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Click to expand...
Click to collapse
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?

lKBZl said:
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
Click to expand...
Click to collapse
I don't see how that would matter, I used the aosp browser as well, and all I did was put stock recovery back on ..
hmmmm
Maybe you should just flash one of the updated stock/rooted roms in the dev section.

Please help with updating...I feel like such a noob, and I feel shame...

Hey all...I'm sorry for sounding like such a noob (trust me i'm not as big as one as you may think) I'm just having a hard time grasping the idea of updating my Nexus. Let me explain:
I'm currently running stock rom but have Matr1x kernel on my phone. The only thing I've changed so far are a few icons (by pulling files from the nexus toolkit, replacing the icons and pushing them back to my phone).
I would prefer not to have to go through and redo all my icons, and would just like to get 4.2 onto my phone.
I looked over the directions on how to do this, but for the life of me (and IDK why) i can't seem to get my head around it...and it's making me feel real real stupid...
can someone please explain to me like i'm 5 how to do this? Or maybe just point me in the direction of a youtube video that will walk me through it...?
Thanks in advance and sorry for being such a noob...

Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.

estallings15 said:
Why not just backup the apk's+data you edited, save them to your computer, flash the stock images, root and restore the apps+data?
Edit: And flash a 4.2.2 kernel.
Click to expand...
Click to collapse
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...

zbt1985 said:
Do I backup via toolkit or with titanium backup?
Also, i tried getting back to stock but for some reason couldn't get it to flash the img file...idk what i was doing wrong...maybe u can give me some pointers on it.
Idk y i'm having such trouble with this, i've been on android since the very begining (had a g1 2 months after it came out)...I guess I was just spoiled with my vibrant being so easy...
Click to expand...
Click to collapse
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot

estallings15 said:
First of all, ditch the toolkit. You don't learn anything when you use toolkits. Probably why you're in the situation you're in.
Backup with titanium, or just make a nandroid and use titanium to extract the apps later.
To flash stock images:
Reboot into bootloader.
Open command prompt and "cd" to the directory where fastboot lies.
Type these commands -
fastboot flash system system.img
fastboot flash boot boot.img
Optional -
fastboot flash bootloader bootloader.img
fastboot flash radio radio.img
Then reboot
Click to expand...
Click to collapse
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...

zbt1985 said:
Here's where the confusion lies...what do u mean cd where fastboot lies...I know how to cd, but not sure what you mean by where the fastboot would be...
Click to expand...
Click to collapse
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.

estallings15 said:
I extract the adb folder from the android SDK and drop it in C:\.
So for me, it's "cd C:\adb"
I believe in the SDK it's in platform-tools or some such jazz. You can always do a search on your computer...
You have installed the android SDK, right? If not, your toolkit might have the adb and fastboot files in it. Grab them from there. Make it work. You can do it.
Click to expand...
Click to collapse
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!

zbt1985 said:
Yes I have the SDK as I use eclipse to complie the apps i make (i cheat)...
I see adb.exe, but not the folder for adbe...
Thanks for all the help man, I hit the thanks button for u!
Click to expand...
Click to collapse
There should be a fastboot.exe and a few .dll files, as I recall.
Could someone upload all the latest files needed for adb and fastboot in a zip for him? Won't take you 5 minutes. I'm not by my computer.

Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]

dEris said:
Why not flash CM10.1 or latest Xylon.
Back up apps with titanium, flash ROM, flash gapps, restore via titanium.
Or do you want stock?
[Nexus⁴]
Click to expand...
Click to collapse
I wanted stock...i only want this for 1) getting updates faster than cm 2) being able to update the hard way and not be a kiddy about it...
Better for me to learn...

http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium

just follow efran's guide, he got the step by step: http://forum.xda-developers.com/showthread.php?t=2010312

gravitysandwich said:
http://forum.xda-developers.com/showthread.php?t=2145848
Scenario #3
Continue to section C.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That's what is confusing me...
Sent from my Nexus 4 using xda app-developers app

Download this http://d-h.st/iy0. Unzip it. Plug your phone I'm the computer, go to the directory where you installed the toolkit. (Right click on the shortcut/properties it should say it there) go in the directory, FLASH ITEMS HERE folder. Put the boot.img and system.img in there. (Radio.img is optional). Open the toolkit and go to flash images. Flash boot.img first. The directions should be on the toolkit. Then system and etc... Make sure you put it in fast boot or type no when the toolkit asks if your in fastboot mode. This will NOT delete your data. When you flashed everything, go to settings on your phone. (If there is a bug with updating it through settings, clear cache and data for Google services framework and force stop it. Then go to cache on root explorer (/cache) and delete the corrupt/partial update and try Again). Once you reboot, cwm will ask if you want to install update. Hit yes and install untrusted package. Then it will try to replace cwm with stock recovery so hit no. If you lost your root then get supersu from the play store and install the binaries via cwm.
Hope this helps.
Sent from my Nexus 4 using xda premium
---------- Post added at 12:11 AM ---------- Previous post was at 12:02 AM ----------
Btw I chose to flash it through toolkit because I was afraid you would've got the commands mixed up and you would never get it. One day you probably will
Sent from my Nexus 4 using xda premium

Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app

zbt1985 said:
Muchos gracias.
Would thank but on my phone
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can thank you your phone.

So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium

gravitysandwich said:
So it worked? Your welcome. I'm guessing you lost root. Here is the zip if you need it
http://download.chainfire.eu/314/SuperSU/UPDATE-SuperSU-v1.20.zip
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Haven't had a chance to try it, doing it now...thanks!

[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] [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

Get softbrick with bootloop

Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.

In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app

nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.

nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.

MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...

nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.

v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.

nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:

@nhatminhng How did you get your phone fixed? is your phone unlocked?

tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.

nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.

tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.

tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.

v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app

CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.

v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.