[Q] Stuck in FIrefox OS. - Nexus 4 Q&A, Help & Troubleshooting

So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.

jaed.43725 said:
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
Click to expand...
Click to collapse
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified

luiseteyo said:
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
Click to expand...
Click to collapse
Ok. So what I did was kinda following your setup here. I had to get the Android SDK first. Then extract that into C:/. Then I got the 4.3 like you said and extracted that C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools. Then because of the new SDK I put the phone into the first 3-button mode. I then ran flash-all. And after a minute I had stock 4.3.

Related

Going back to Stock

Hi!
I'm trying to go back to stock+locked rom.
I have seen instructions with a lot of steps, but when I downloaded the rom from googe developers page, i noticed there is a flash-all.sh file that seems to do all the process...
Is this safe?
Code:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-occam-jdq39.zip
I don't want to brick the phone
Guide by efrant:
D. Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10l.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Optional (NOT optional for n00bs) -- Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the Dalvik cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked. See the notes section at the end of this post for information on re-locking the bootloader.
You have to unpack the system.image file as you can only flash .img files in fastboot. What`s with the sleep 5?
Good luck.
I've seen some youtube tutos that use that .sh file and it does flash the .zip with fastboot......
That's why I ask, I mean: The previous thread, which i already read before, is like a step-by-step process, when this .sh file would do it all for you!!
The sleep command gives 5 seconds of grace time for the device to reboot.....
GFXi0N said:
I've seen some youtube tutos that use that .sh file and it does flash the .zip with fastboot......
That's why I ask, I mean: The previous thread, which i already read before, is like a step-by-step process, when this .sh file would do it all for you!!
The sleep command gives 5 seconds of grace time for the device to reboot.....
Click to expand...
Click to collapse
Haven`t used that method myself, but if you think it will work go ahead
WOrst case scenario, the console woud throw me out to the command prompt and I would have to do it by hand......

Nexus 7 Bricked??/Broken

Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks
download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.
Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app
dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.
YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app
Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk

[Q] Stock flashable JWR66Y downlaod

Hello Community.
I have searched and searched and searched. Can some one link me to a full ODEX of JWR66Y ROM? I am trying to restore my N4 back to stock. Thanks will be given...
jgentry151 said:
Hello Community.
I have searched and searched and searched. Can some one link me to a full ODEX of JWR66Y ROM? I am trying to restore my N4 back to stock. Thanks will be given...
Click to expand...
Click to collapse
Here you are. Flash it using fastboot commands
DOWNLOAD
luiseteyo said:
Here you are. Flash it using fastboot commands
DOWNLOAD
Click to expand...
Click to collapse
Thanks!!! Do you happen to know the fastboot command? Or an instructional for this? Will I have to use stock boot loader and so on?
jgentry151 said:
Thanks!!! Do you happen to know the fastboot command? Or an instructional for this? Will I have to use stock boot loader and so on?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4 using xda app-developers app
jgentry151 said:
Thanks!!! Do you happen to know the fastboot command? Or an instructional for this? Will I have to use stock boot loader and so on?
Click to expand...
Click to collapse
this is my favourite guide.
Follow this steps:
1. Fastboot mode.
2. Type:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66y.zip
done!
Why download from random place when you get it officially from Google: https://developers.google.com/android/nexus/images#occam
And if you open the package it has the bat script file that will run all the commands to flash the phone automatically, you just have to put it in fastboot mode and unlock the bootloader first, or you can read the script file and manually type in the commands.
luiseteyo said:
this is my favourite guide.
Follow this steps:
1. Fastboot mode.
2. Type:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66y.zip
done!
Click to expand...
Click to collapse
Muchisimas Gracias!!!
eksasol said:
Why download from random place when you get it officially from Google: https://developers.google.com/android/nexus/images#occam
And if you open the package it has the bat script file that will run all the commands to flash the phone automatically, you just have to put it in fastboot mode and unlock the bootloader first, or you can read the script file and manually type in the commands.
Click to expand...
Click to collapse
Mine was the link from google. And I prefer to do it manually.
luiseteyo said:
Mine was the link from google. And I prefer to do it manually.
Click to expand...
Click to collapse
How do I flash stock Android without deleting any of my apps/data/settings?
Do I need to skip or remove any of those lines from the script??
The process will wipe your entire device. You have to back up your stuff and move it out of your phone. You can use the Helium app to back up apps data, if you don't have root you also need to install this http://www.clockworkmod.com/carbon for it to work.
You could leave your data alone and only flash certain partitions though. Don't run the scripts, do it all manually. Skip "fastboot erase userdata" which will wipe your apps data. Also skip "fastboot -w update image-nakasig-jwr66y.zip".
Extract the *.img files from "image-occam-jwr66y.zip" and flash them manually, skipping userdata.img of course, the other three files you want to flash would be:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
However, depending on the Android version and configuration, you might run into issues by doing this.

Error on Android 5.0.2 OTA Update

Well i'm trying to update my Nexus 7 2012 to Android 5.0.2, after receiving the OTA update but keep getting an error.
I rooted my Nexus 7, and been thinking that's the problem, since it restarts to install the OTA update but goes to Recovery mode, and when i try to manually install the file get the following error :
https://www.dropbox.com/s/dqjc2ztzfbkvnuy/IMAG0897.jpg?dl=0
Any tips or solution for the problem?
Thanks in advance
Go here and flash the full image: https://developers.google.com/android/nexus/images
Skeetch79 said:
Go here and flash the full image: https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Didn't want to do that, because means i'm going to loose everything
lmcmil said:
Didn't want to do that, because means i'm going to loose everything
Click to expand...
Click to collapse
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Thanks for the tip and explanation Skeetch79, will try to do like you wrote.
lmcmil said:
Thanks for the tip and explanation Skeetch79, will try to do like you wrote.
Click to expand...
Click to collapse
Np. Keep me posted
Sent from my XT1096 using Tapatalk
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
This method works great! I was in the same boat. I analyzed the updater script and then analyzed the ro.build.fingerprint from my system, and it doesn't contain the weird one that it errors out on. I debated just removing the build prop check and repackaging it as an update, but decided against it.
@lmcmil - per chance, did you flash a different kernel and/or switch to F2FS before this happened? If so, that might correlate to mine, since I did do that....
Either way, I'm gonna run stock again for a while and see how it feels.
EDIT:
I think these lines:
Code:
mount("ext4", "EMMC", "/dev/block/platform/sdhci-tegra.3/by-name/APP", "/system", "max_batch_time=0,commit=1,data=ordered,barrier=1,errors=panic,nodelalloc");
getprop("ro.build.fingerprint") == "google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys" ||
getprop("ro.build.fingerprint") == "google/nakasi/grouper:5.0.2/LRX22G/1649326:user/release-keys" ||
abort("Package expects build fingerprint of google/nakasi/grouper:5.0/LRX21P/1570855:user/release-keys or google/nakasi/grouper:5.0.2/LRX22G/1649326:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
are what causes it to explode. First, it tries to mount ext4 instead of F2FS, which makes sense, but would cause the system partition to be unreadable if you converted it to F2FS. That COULD explain the odd "deestroy" build prop it thinks it got when it pulled ro.build.fingerprint, since when my system was fully booted mine matched the stock LRX21P using getprop from adb.
toastido i tryied to load the OTA using the Nexus Root Toolkit and the error i got was regarding missing calculator, wich i removed after installing "Calculator ++" app
Still haven't had time to try this method, i'm working this weekend so only next week i can give it a try and post the result.
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Good Man !!!
Thanks Very Much for that one,
I got stuck on the boot after performing the advised but a quick Cache Wipe sorted that out.
Once again Much Obliged !!!
Yeah forgot to mention the above. if you are stuck in a boot loop: shut down. reboot to recovery. wipe cache and dalvic. Reboot. Profit.
Sent from my XT1096 using Tapatalk
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Does this also work if I want to go back to Kitkat? I am asking, because I've tried the following:
Code:
@echo off
echo. listing devices:
fastboot devices
echo. To continue press Enter
pause
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
REM adopt the following line according to the bootloader image filename
fastboot flash bootloader bootloader-flo-flo-04.02.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And no matter, if I do a wipe cache afterwards or not, I end up in a boot-loop.
Do you know a way to keep apps and settings while going back to Kitkat?
nieroster
lmcmil said:
toastido i tryied to load the OTA using the Nexus Root Toolkit and the error i got was regarding missing calculator, wich i removed after installing "Calculator ++" app
Still haven't had time to try this method, i'm working this weekend so only next week i can give it a try and post the result.
Click to expand...
Click to collapse
lmcmil said:
Well i'm trying to update my Nexus 7 2012 to Android 5.0.2, after receiving the OTA update but keep getting an error.
I rooted my Nexus 7, and been thinking that's the problem, since it restarts to install the OTA update but goes to Recovery mode, and when i try to manually install the file get the following error :
https://www.dropbox.com/s/dqjc2ztzfbkvnuy/IMAG0897.jpg?dl=0
Any tips or solution for the problem?
Thanks in advance
Click to expand...
Click to collapse
TWRP is incompatible with 5.x OTA: it uses its own moronic default.prop instead of importing the device build.prop (or something like that) . It needs to be fixed.
You have to bother flashing the full image (minus the wiping eventually) and reinstall root & TWRP with every update, just like the rest of us
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
lmcmil said:
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
Click to expand...
Click to collapse
Well decided to use the Nexus Root Kit and flash the full image LRX22G, doing it now.
Will post how it went.
lmcmil said:
Got an Failed error at fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>.
So now i don't have a valid bootloader and also can't enter recovery because it was erased at fastboot erase recovery <hit enter> step
And also typing fastboot devices my Nexus 7 isn't detected, what can i do now?
Click to expand...
Click to collapse
I had the 2012 Nexus 7 WiFi before I picked up the 2013 model. I had the same issue with that bootloader. Seems to be a common issue. Here are articles discussing the issue and fixes.
http://android.stackexchange.com/qu...t-flash-bootloader-failed-remote-invalidstate
https://code.google.com/p/android/issues/detail?id=62198&
http://forum.xda-developers.com/showthread.php?t=2573015
I remember flashing a modified bootloader to resolve the issue, since as you can see the bootloader packaged with the images is borked.
EDIT: try flashing the appropriate bootloader from this thread: http://forum.xda-developers.com/showthread.php?t=2417097
lmcmil said:
Well decided to use the Nexus Root Kit and flash the full image LRX22G, doing it now.
Will post how it went.
Click to expand...
Click to collapse
So my Nexus 7 is now running with 5.0.2, and did not loose any apps since i chose the "No wipe mode"
Going to root it again, and install latest TWRP Recovery
lmcmil said:
So my Nexus 7 is now running with 5.0.2, and did not loose any apps since i chose the "No wipe mode"
Going to root it again, and install latest TWRP Recovery
Click to expand...
Click to collapse
So i have now a Nexus 7 running 5.0.2, already rooted again and with TWRP 2.8.4.1.
Thanks a lot!
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- ...
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
Thanks for the great tutorial! Used it yesterday on my rooted Nexus 7 to upgrade to 5.0.2, worked like a breeze! :good:
Afterwards I used WugFresh's Nexus Root Toolkit to regain root.
Skeetch79 said:
Thought you would say that! .
You can always:
- download the image for your device from the google nexus website I gave you
- unzip the tgz file
- Find the resulting tar file and unzip it
- you will now have a folder
- inside the folder will be a bootloader-grouper-4.23.img file, image-nakasi-lrx22g.zip file, flash-all.bat file and two .sh files
- unzip the zip file to the same directory as the bootloader-grouper-4.23.img file
- reboot your nexus into bootloader mode
- plug the nexus into your PC
- open a command prompt in the same directory as the image, sh and bat files (on windows 7 hold the shift key and right click on an empty space within the folder and choose open command window here)
- in the command window type fastboot devices, make sure device is recognized
- if not, set up your pc for adb and fastboot, if so, continue
- type in the command prompt:
fastboot erase boot <hit enter>
fastboot erase cache <hit enter>
fastboot erase recovery <hit enter>
fastboot erase system <hit enter>
fastboot flash bootloader bootloader-grouper-4.23.img <hit enter>
fastboot reboot-bootloader <hit enter>
fastboot flash boot boot.img <hit enter>
fastboot flash recovery recovery.img <hit enter>
fastboot flash system system.img <hit enter>
fastboot reboot <hit enter>
This will preserve your app and data settings.
If you had custom recovery installed just reboot into fastboot and flash the recovery of your choice. example: fastboot flash recovery ,recovery image name>
If you want to reroot, download a superuser zip file to your device, reboot back into your custom recovery and then install the SuperUser zip of your choice (i.e. chainfire's SuperSu)
Hopefully this is straightforward and self explanatory
Click to expand...
Click to collapse
I followed this tutorial yesterday and everything went great I now have 5.0.2 working on my Nexus 7 2013, with no problems I can detect at the moment. Thank you, because I was just frustrated I saw the OTA notification without being able to do anything.
Cheers.
I try it too 5.0.2 ota update and nothing still on 4.4.4 I guess on Lollypops for me

How to install and use ADB and fastboot

1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
sellfy said:
Thanks for the great step by step tutorial.
I've tried to instal the Fastboot Image via the above guidem
1. Connect your Android device to computer via USB.
2. Ensure USB Debugging mode is ENABLED on Android device.
3. download adb driver
4. unzip adb driver and instal it
5. Extract the Minimal ADB and Fastboot Tool file to your PC
6. Download your RecoveryFile.img file or full fastboot Rom file and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ” so all files will be in single folder. (Which I've done with TOS319I Fastboot Image file)
7. open folder Minimal ADB and Fastboot, click on " open command window here "
8. Now type following command
adb fastboot
Unlocking the bootloader
adb reboot bootloader
fastboot reboot
Then, adb reboot bootloader
fastboot devices
*** But when I use the fastboot flash recovery TOS319I.img and to use the downloaded and renamed recover image, it says unable to load file TOS319I.img
Can you please let me know what should I do?
Thanks in advance
Click to expand...
Click to collapse
i know that you should use cyanogen os version rom of wileyfox storm (FIRST)
then you can flash custom rom or upgrade to official android 7 rom
that means , first you should downgrade to cyanogen 13
Again bootloop
ghertas said:
1.
Connect your Android device to computer via USB.
2.
Ensure USB Debugging mode is ENABLED on Android device.
Settings > About Phone > Build number > Tap it 7 times to become developer;
Settings > Developer Options > USB Debugging.
3.
download adb driver
http://adbdriver.com/downloads/
download Minimal ADB and Fastboot
https://forum.xda-developers.com/showthread.php?t=2317790
4.
unzip adb driver and instal it
http://adbdriver.com/documentation/...river-installer-for-windows-xp-vista-7-8.html
http://adbdriver.com/documentation/how-to-install-adb-driver-on-windows-8-10-x64.html
5.
Extract the Minimal ADB and Fastboot Tool file to your PC
6.
Download your RecoveryFile.img file or full fastboot Rom file
and put under the extracted folder “ Fastboot or Minimal ADB and Fastboot ”
so all files will be in single folder
7.
open folder Minimal ADB and Fastboot
in the folder , On your keyboard press SHIFT and right click with your mouse " Shift + right click "
click on " open command window here "
8.
Now type following command
adb fastboot
Unlocking the bootloader
Note: Using the fastboot command
When the fastboot command is used on the Storm, the vendor id command option must be added.
The vendor id for the Storm is 0x2970. For example, fastboot devices, would be fastboot -i 0x2970 devices.
Enable OEM unlock in the Developer options settings on the device.
(Note: Not all devices have this setting, so continue with next step if yours does not.)
Connect the device to the computer through USB.
From a terminal on a computer, type the following to boot the device into fastboot mode:
adb reboot bootloader
Once the device is in fastboot mode, verify your PC sees the device by typing fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine. See fastboot documentation for more info.
If you see "no permissions fastboot", try running fastboot as root.
From the same terminal, type the following command to unlock the bootloader:
fastboot -i 0x2970 oem unlock-go
If the device doesn't automatically reboot, reboot it from the menu. It should now be unlocked.
Since the device resets completely, you will need to re-enable USB debugging on the device to continue.
fastboot reboot
Installing a custom recovery using fastboot
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination for your device while it is powered off.
Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
fastboot reboot
full rom fastboot
adb reboot bootloader
fastboot devices
fastboot flash aboot emmc_appsboot.mbn
fastboot flash abootbak emmc_appsboot.mbn
fastboot erase DDR
fastboot flash sbl1 sbl1.mbn
fastboot flash sbl1bak sbl1.mbn
fastboot flash tz tz.mbn
fastboot flash tzbak tz.mbn
fastboot flash hyp hyp.mbn
fastboot flash hypbak hyp.mbn
fastboot flash rpm rpm.mbn
fastboot flash rpmbak rpm.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash cache cache.img
fastboot erase splash
fastboot flash splash splash.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I've exactly followed your instructions for *"full rom fastboot"*, and all was done 'OK'. But Still the device is in bootloop and not going into recovery OR andriod system
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
idforpc said:
ghertas said:
"full rom" was a zip file of cyanogen version
cyanogen realised two files of each rom
recovery version and fastboot version
if you want to install a custom rom on your device
Yes, I've download cyanogen Fastboot version, The only problem i've got is that my phone doesn't go into recovery mode although I've flashed TWRP also cn 13, but still the device only boots in fastboot only
When I select Recovery mode in Fastboot menu the device goes into bootloop.
Click to expand...
Click to collapse
"fastboot reboot"
after boot the device , "Power off" the device and press volume down and power at the same time until you see the recovery on screen
"TWRP" is a custome recovery for install custom rom s
did you do all of those on " lineage wiki " ?
https://wiki.lineageos.org/devices/kipper/install
download the last version of twrp recovery
https://androidfilehost.com/?fid=1395089523397922500
Click to expand...
Click to collapse

Categories

Resources