Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Issue fixed, see below!
************************************************************************************************
Ok guys, the problem was solved in an odd way!
I got annoyed with the flashing errors, and flashed the old kernel and radio I was using with my Illusion rom which thankfully got me back to that even though I had lost all of my data (backed up though).
For anyone having this problem and wants to unroot to go back to 4.3 or is trying to flash the legit 4.3 rom from Google and then maybe unroot or just use the 4.3 rom direct from Google...
DOWNLOAD THE LEAKED 4.3 ROM AND FLASH USING STANDARD CWM METHOD.
DOWNLOAD THE .84/.83 KERNEL AND FLASH THIS AS WELL.
After this I got the legitimate OTA update which was only 3.4mb and it even fixed root so I am now back to complete stock, locked bootloader and no root!
Hope this helps
Click to expand...
Click to collapse
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode. Personally, I do the following:
1. Extract the entire TGZ (including the update.zip)
2. Move all the IMG files into one folder
3. Rename them to easy names, e.g. bootloader, radio, system, userdata, boot, recovery, etc.
4. Flash them all in turn, rebooting the bootloader each time
5. Once all done, erase/format the cache (fastboot erase cache and fastboot format cache)
6. Boot into recovery and clear cache again and then do a factory reset (this makes sure the unit see all the internal memory)
7. Reboot the phone
Should all work now
siravarice said:
Hey guys, I'm currently trying to flash back to the new 4.3 factory image that I downloaded from Google, however, it all goes fine, I flashed the bootloader, flashed the radio and it all says it has been updated properly, then when I try and flash the system.img files and boot.img files they just say no such file or directory exists and stops, meaning the phone is unusable at the moment until I flash something.
Anyone know why this is happening?
BTW I'm using a mac.
Click to expand...
Click to collapse
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
4.3 (JWR66V)
https://dl.google.com/dl/android/aosp/occam-jwr66v-factory-08d2b697.tgz
7zip
http://www.7-zip.de/
[HOW-TO] How to flash a factory image / return to stock / unlock / root #
http://forum.xda-developers.com/showthread.php?t=2010312
EddyOS said:
Easiest way of flashing the system image is to just use the flash-all script included in the TGZ - just extract it out and run it when the phone is connected in fastboot mode
Click to expand...
Click to collapse
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
info.brandenburg said:
Maybe you have corrupted files? Retry the download from google and unpack all with 7zip.
I did that yesterday and all works fine.
Click to expand...
Click to collapse
Did that, same thing happened. I tried flashing the entire .zip and then I tried separately and it still didn't work.
Ok so I know it is just the system.img file that doesn't work, as all the other files have just flashed fine! Going to re-download and see if that helps.
siravarice said:
How would I do that on a mac? I tried typing:
./fastboot flash flash-all.bat
but do I need to use the .sh version?
Click to expand...
Click to collapse
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
EddyOS said:
You just run the script, you don't flash it. It's a batch file which then does all the fastboot commands. You also use flash-all.sh as you don't have Windows
Click to expand...
Click to collapse
Still doesn't work.
I used: bash flash-al.sh
And it just said fastboot not found in certain lines for the command and did nothing. I thought it fixed itself when I swapped USB ports but when it got to the system.img it just gave me the same error again. It flashes everything else ok but not this file, it's the third time I have downloaded it and now I have no way to get it back to being useable as when I press start it just gives me a black screen
HELP PLEASE!
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
EddyOS said:
I would but I use Windows and it's all fine. Might be worth downloading the factory image again, checking the md5 and trying to flash the system image again
Click to expand...
Click to collapse
Im trying to install some Samsung Android Drivers on my old laptop but the thing is so slow it's basically impossible to work from now
I've redownloaded the files, I don't know how to check the MD5Sum though. Still nothing doing. I get this error:
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6166 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6664 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (531281 KB)... ERROR: usb_write failed with status e00002be
FAILED (data transfer failure (No such file or directory))
edue3e4:4.2unrootnexus4 Simon$
It really doesn't want to write the system.img file, or maybe it doesn't want to write to system?
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
efrant said:
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-makoz10o.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.48.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) 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) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== the second option seems to work better for most people. Thanks joostburg.
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.
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
If you have a 16GB device, and it now shows up as 8GB, reboot into recovery (hold power and press volume up when you are at the screen with the android and the red exclamation mark), and wipe cache. If that still doesn't work, boot back into recovery and do a factory reset. Or do this
Click to expand...
Click to collapse
EddyOS said:
What happens if you extract the system.img file and flash it via fastboot manually?
fastboot flash system system.img
I always use this guide if I forget:
Click to expand...
Click to collapse
That's exactly what I have been doing, I prefer doing it manually as I don't like using Toolkits and finding a good one for mac is hard enough.
It just says that it cannot send it because the file or directory does not exist, yet if I unplug the phone it does go back into my old rom I was using before that, even though I flashed a new radio and recovery.img, boot.img, user data.img, everything except system.img as it doesn't work
Something clearly wrong with the partition but no idea what...
I know right, I've gone back to the ROM I had previously and downloaded the leaked 4.3 rom and flashed it through flashify. If it works I will simply lock the bootloader again and it should be good to go!
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Hmmy 4444 said:
i did the same way through nexus tool kit 2.0 n p.s i guess the file was corrupted that y it failed in the mid. ill try it again
Click to expand...
Click to collapse
Let me know if you get anywhere with it!
it worked.. jst copy the image n dont rename it n go to google nexus 4 toolkit folder n there u would see a folder named *put googlr factory image here* paste it there n before starting ur bootloader must be unlocked.. so thats that.. after that that open the nexus 4 toolkit n then click on number 9 whch says download extract + flash google factore stock rom n then after that type 2 whch says flash google factory image... n thats it. it will automatically flash it.... gv me thanks too
Sent from my Nexus 4 using xda app-developers app
Hi there, same issue with me on a mac
Plus can you tell me how you went back to the previous rom, my phone is unusable right now and i do have a nandroid backup so.
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
EddyOS said:
Have either of your tried to flash the 4.2.2 factory image? Would be interested to see if it works
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I dont mind, can you direct me towards a post where they show how to, i m not sure of all this and dont want to mess around with wrong files.
UPDATE: I tried and that works just fine. Rebooted to 4.2.1
Related
So I downloaded the newest stock image and I've done all I need to do in terms of drivers and such. But the file is a .tgz and when I try to push it it says "adb cannot read sideload." My device is being detected by adb in cmd. I also notice if you unpack the file there IS a zip, but there's also a new bootloader and such.
Do I have to have an unlocked bootloader for this to work? Or will flashing the .zip be okay?
I did this same thing today but I had to unlock my bootloader. ( which wipes all your data). I also had to extract a few levels deep in that file. You should research doing a factory image install because there are a few steps to do with fast boot besides pushing the 1 file over.
Sent from my Nexus 10 using Tapatalk 4 Beta
Recon0212 said:
So I downloaded the newest stock image and I've done all I need to do in terms of drivers and such. But the file is a .tgz and when I try to push it it says "adb cannot read sideload." My device is being detected by adb in cmd. I also notice if you unpack the file there IS a zip, but there's also a new bootloader and such.
Do I have to have an unlocked bootloader for this to work? Or will flashing the .zip be okay?
Click to expand...
Click to collapse
Hi! I also got the same sideload error when I tried to update my nexus 4 to 4.3. Turns out the drivers were faulty. I recommend that you uninstall and delete your current drivers from device manager and install the Universal Naked Driver from here and then sideload the file.
It worked for me.. Lets see if it works for you too.
About the .tgz part, extract the file, move all IMG files into one place and flash them one by one (reboot bootloader each time). Now erase the cache (fastboot erase cache and fastboot format cache), clear the cache again from recovery mode then to a factory reset.
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Cantacid said:
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Click to expand...
Click to collapse
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
kzoodroid said:
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
Click to expand...
Click to collapse
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Cantacid said:
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Click to expand...
Click to collapse
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
kzoodroid said:
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
Click to expand...
Click to collapse
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
sn0warmy said:
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
Click to expand...
Click to collapse
In the other walk through flash system image and boot image is replaced by "./fastboot update image-occam-jwr66v.zip". This could help those who are having problems flashing the system image file. I've also seen this method used for windows in that all you flash is the bootloader image then the update image and your done.
-w is to clear the userdata, but the problem is its not pushing the system.img on the phone! Tried without -w and yet the same issue! I have restored my previous rom and madea nandroid for 4.2.2 stock! Might go back to that and try updating ota! Can somebody confirm if i have to lock bootloader and lose root to get an update!
I have no clue why the same steps work for 4.2.2 but not 4.3 image files!
Sent from my Nexus 4 using Tapatalk 4 Beta
One thing I don't think anyone has mentioned (which may actually be the core solution to this problem for everyone) is that you need to update your SDK Platform from 17 to 18 and you need to install "Android Support Repository" in order for 4.3 to properly flash. To do this open terminal and paste the path to the "android" executable file found under sdk/tools. My path was:
/Users/kevin/Desktop/Android/sdk/tools/android
After pasting the appropriate path into terminal hit enter. This will open the SDK Manager. Once SDK Manager is open it will ask to update outdated drivers. One of the drivers being updated is SDK Platform. Before hitting the update button scroll down to the 'Extras' folder and check the box next to "Android Support Repository". Now hit the update button.
After doing this, reboot the computer (may or may not be necessary) and try flashing again by following the steps I provided in post #5. Let me know if that solved it.
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Cantacid said:
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sdk/tools is located wherever you extracted the .zip file to. In my case I just put it all in a parent folder on the desktop called "Android".
I know there is many topic like this, but I need urgent help. We go to holiday on saturday and I have to decide what to do.
Today got I back my N7 from Brno/Czech from warranty repair. Than the device shut down and I couldn't power on, they replaced my charger and sent back the device. I sent on 26th in July with an RMA number.
When I got back the device I started by the courier and it booted into Android. About 10 minutes later it showed me an update to 4.3 and I allowed it. It restarted and when it was ready the device didn't powered on again. It remained on the Google logo. Now - when I tried to wipe/Hard reset - it only shows the Google logo in the middle and a Start sing on the upper right corner.
I can do:
- recovery
- ADB sees the device
- Nexus 7 toolkit sees too
- Nexus Root Tools sees too
- I can install recovery (TWRP-CWM-stock) it works
- bootloader lock/unlock
but
I cant install
- system/image
- boot
- bootloader
- radio
- etc...
It looks like the flash storage is injured. 20 minutes before I sent a command: flash radio now the device in fastboot and on the upper left corner there is a white text: "Booting downloaded image" It doesn't respond...
I need an advice how to forward, send it back or is there any sollution'
bigsee said:
I know there is many topic like this, but I need urgent help. We go to holiday on saturday and I have to decide what to do.
Today got I back my N7 from Brno/Czech from warranty repair. Than the device shut down and I couldn't power on, they replaced my charger and sent back the device. I sent on 26th in July with an RMA number.
When I got back the device I started by the courier and it booted into Android. About 10 minutes later it showed me an update to 4.3 and I allowed it. It restarted and when it was ready the device didn't powered on again. It remained on the Google logo. Now - when I tried to wipe/Hard reset - it only shows the Google logo in the middle and a Start sing on the upper right corner.
I can do:
- recovery
- ADB sees the device
- Nexus 7 toolkit sees too
- Nexus Root Tools sees too
- I can install recovery (TWRP-CWM-stock) it works
- bootloader lock/unlock
but
I cant install
- system/image
- boot
- bootloader
- radio
- etc...
It looks like the flash storage is injured. 20 minutes before I sent a command: flash radio now the device in fastboot and on the upper left corner there is a white text: "Booting downloaded image" It doesn't respond...
I need an advice how to forward, send it back or is there any sollution'
Click to expand...
Click to collapse
need not to worry man...its a common problem...i have xperienced more than 50 times than while doing fastboot it doesnot respond after a certain period of time and when u power off and start the defice it goes into fastboot mode
solution:
for device: enter in fastboot mode
chose power off then leave it for five minutes till then do the instructions for laptop or computer as mentioned below
for computer/laptop:
shutdown (do not restart, it should be shutdown)
then power on ur computer wait for it to finish booting
plug the usb cable in other port (other than the previous port u were trying)
then power on ur device let it go to fastboot
then plug the usb cable to it
wait for 2-3 minutes
then flash the stock factory image by clicking on flashall.bat
hopefully it will take 5-10 minutes to do the work
and if it exists more than 20 minutes...disconnect ur device and repeat the procedure...till u suceed...
sorry mate but this is the only solution to it...
i have tried it many times...
if u succeed...do reply and hit thx...or if u face another problem...just post the reply:good:
dr.sushant said:
need not to worry man...its a common problem...i have xperienced more than 50 times than while doing fastboot it doesnot respond after a certain period of time and when u power off and start the defice it goes into fastboot mode
solution:
for device: enter in fastboot mode
chose power off then leave it for five minutes till then do the instructions for laptop or computer as mentioned below
for computer/laptop:
shutdown (do not restart, it should be shutdown)
then power on ur computer wait for it to finish booting
plug the usb cable in other port (other than the previous port u were trying)
then power on ur device let it go to fastboot
then plug the usb cable to it
wait for 2-3 minutes
then flash the stock factory image by clicking on flashall.bat
hopefully it will take 5-10 minutes to do the work
and if it exists more than 20 minutes...disconnect ur device and repeat the procedure...till u suceed...
sorry mate but this is the only solution to it...
i have tried it many times...
if u succeed...do reply and hit thx...or if u face another problem...just post the reply:good:
Click to expand...
Click to collapse
Thank you for the answer! I'm trying-I'm trying and trying, but none...
I got two error messages, the first is when it sends the radio to the device:
sending 'radio' <16384KB>...
OKAY [2.078s]
writing 'radio'...
FAILED <remote: <BadParameter>>
finished. total time: 2.094s
the second at the end:
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
When I hit The Anykey (I didnt find it at first ) nothing happens... so I'm sad again...
What can I do yet?
bigsee said:
Thank you for the answer! I'm trying-I'm trying and trying, but none...
I got two error messages, the first is when it sends the radio to the device:
sending 'radio' <16384KB>...
OKAY [2.078s]
writing 'radio'...
FAILED <remote: <BadParameter>>
finished. total time: 2.094s
the second at the end:
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
When I hit The Anykey (I didnt find it at first ) nothing happens... so I'm sad again...
What can I do yet?
Click to expand...
Click to collapse
What factory image have you tried?
Update requires '1231_0.17.0_1205'
Click to expand...
Click to collapse
I think this one can be dodged by installing the 4.2.2 factory image (I remember that 4.2.2 had 1205 BB so this should install it) from here. Also have a look here for how to return to stock. It also worked for me upgrading to 4.3.
I hope it helps
al3x1393 said:
What factory image have you tried?
I think this one can be dodged by installing the 4.2.2 factory image (I remember that 4.2.2 had 1205 BB so this should install it) from here. Also have a look here for how to return to stock. It also worked for me upgrading to 4.3.
I hope it helps
Click to expand...
Click to collapse
Hy!
This image: nakasig-jdq39-factory-0798439d.img unzipped to the directory of fastboot in c:\
I tried this:
Code:
- unpacking the .zip file
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot format userdata
(optionally: fastboot flash userdata userdata.img)
from here:
http://forum.xda-developers.com/showthread.php?p=44317341#post44317341
And it was succes! The tablet booted in, I could set it up, but there is a minor (major?) problem: it has lost 75% os the storage capacity, the storage is 6.02 GB.. it is a 32 GB 3G version...
I dont dare to upgrade now
edit: oopppsss I forgot: I made the above commands in a machine: winXP32 - 768 MB RAM - and a Blackberry USB cable!!!
bigsee said:
Hy!
This image: nakasig-jdq39-factory-0798439d.img unzipped to the directory of fastboot in c:\
I tried this:
Code:
- unpacking the .zip file
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot format userdata
(optionally: fastboot flash userdata userdata.img)
Click to expand...
Click to collapse
It sounds like one or more partitions are not mounted by android (either they are not formatted properly or i don't know, but android can't see it/them).
I think you can try erasing them at all...however when I upgraded it to 4.3 I used that flashall.bat (or something like that) you can find inside the archive downloaded from Google website. You can try that too, it's basically the same thing as typing them by yourself, but you know...just to be sure everything it's ok.
Also from what i see in your code, you don't flash the radio (baseband) image at all and because of that your baseband/radio problem will persist at a further update. You formatted user data so you don't care about your files, so you can perform a full wipe and erase everything just to get things done well.
However, if you want to do it by yourself try theese full wipe instructions (OF COURSE YOU HAVE TO CHANGE bootloader-tilapia-4.23.img AND radio-tilapia-1231_0.18.0_0409.img AND image-nakasig-jwr66v.zip WITH YOUR 4.2.2 ONES (THEESE ARE FOR 4.3)):
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-jwr66v.zip
al3x1393 said:
It sounds like one or more partitions are not mounted by android (either they are not formatted properly or i don't know, but android can't see it/them).
I think you can try erasing them at all...however when I upgraded it to 4.3 I used that flashall.bat (or something like that) you can find inside the archive downloaded from Google website. You can try that too, it's basically the same thing as typing them by yourself, but you know...just to be sure everything it's ok.
Also from what i see in your code, you don't flash the radio (baseband) image at all and because of that your baseband/radio problem will persist at a further update. You formatted user data so you don't care about your files, so you can perform a full wipe and erase everything just to get things done well.
Full wipe instructions (OF COURSE YOU HAVE TO CHANGE bootloader-tilapia-4.23.img AND radio-tilapia-1231_0.18.0_0409.img AND image-nakasig-jwr66v.zip WITH YOUR 4.2 ONES (THEESE ARE FOR 4.3)):
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-jwr66v.zip
Click to expand...
Click to collapse
Thanks! I store this method but I wait a little bit more because I started a new RMA by Asus. Now I'm waiting for their answer.
bigsee said:
Thanks! I store this method but I wait a little bit more because I started a new RMA by Asus. Now I'm waiting for their answer.
Click to expand...
Click to collapse
As you wish
At least it came back from repair - from Brno - with a JOP40D FW and a working 4.2.1.
After update - to 4.2.2. - it showed an error but it could boot into the former system ... 4.2.1...
I had to reflash to the JWR66Y FW without the correct recovery...
Currently my Nexus 7 is living with a working 4.3 but without a recovery
I played with N7 a little bit. I discovered that I can only be succes if I erase boot/recovery/system/userdata and than flash these img's individually anyway I get a "booting failed" message w/o working recovery and/or android. Nor the flash-all.bat nor the bootloader/radio/update doesn't work.
Q: Philos64 wrote a super howto (here: http://forum.xda-developers.com/showthread.php?t=2175086) to flash the stock and he says: "Reboot to your recovery for confirm the install - You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode[, if your Nexus doesn't reboot itself, reboot yourself!" I never do it because of the missing recovery... Should I/can I write only the BL or radio end at the end and step into recovery to finish or levye it on the present state?
Did you tried boot into stock recovery then via fastboot?
No I didnt. I enjoyed the working system...
Tapatalk 2-vel küldve az én Nexus 7-ről
The aim of this thread is to make an easy guide to flashing stock firmware. Owners of previous nexus devices already know all this stuff, this thread is aimed at making the process as simple as possible for new users. This will work regardless of what modifications you've done to your device. Remember to backup all your important data and do this with the knowledge that all flashing activity carries some risk.
Download
Factory image here
(for windows users) Minimal adb & fastboot
(for mac users) adb & fastboot for mac
Follow the instructions to install adb on your computer.
Prepare your tablet
Enable developer options in settings > about tablet and tapping build number 7 times
Open developer options and enable usb debugging. (If you haven't unlocked your bootloader yet, tick enable oem unlock)
Extract images
Place the downloaded factory image inside your adb folder and extract with 7zip.
A new folder will be there called something like volantis-lrx21. Open and extract "image-xxxxx-zip" to your adb folder. We are interested in these files:
bootloader-flounder-xxxxxx.img
boot.img
recovery.img
cache.img
system.img
vendor.img
Place these files directly into your adb folder.
# I recommend renaming the 'bootloader-flounder-xxxxxx.img' to just 'bootloader.img' to make it easier to type.
Now that everythings set up, we can start flashing
Plug in your device. Open the adb folder, hold shift and right click and select open command window here
(if your having driver issues try using Pdanet)
Run these commands one at a time
Code:
adb devices
adb reboot bootloader
if you haven't unlocked the bootloader yet run
Code:
fastboot oem unlock
and follow the instructions using the volume keys to scroll through the menu. This procedure will wipe all data.
Run the following commands one at a time
Code:
fastboot flash bootloader bootloader-flounder-xxxxxxx.img
[B] [I](replace 'bootloader-flounder-xxxxx.img' with full name of bootloader image[/I])[/B]
fastboot reboot-bootloader
fastboot -w
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash system system.img
fastboot flash vendor vendor.img
(OPTIONAL) At this stage you can relock the bootloader if you want by running the command
Code:
fastboot oem lock
finally reboot the device by running
Code:
fastboot reboot
Thats it. Enjoy your tablet in factory condition
Great. Is it possible to make a batch file to run all the commands at once?
albsat said:
Great. Is it possible to make a batch file to run all the commands at once?
Click to expand...
Click to collapse
There is already a flash all batch script that comes with the firmware files but I've noticed that some people have problems with it so I decided not to include it. It should work fine most of the time.
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Cool, thanks for the information.
Thanks for creating this! Will come in handy. Saving this for later
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
scotty1223 said:
i am long-time familiar with htc,but new to nexus. i was looking thru a couple downloaded factory image files and having noticed that "rebootRUU" is an oem command,and that "image-xxxxx-zip" contains an android info document,i am curious if anyone has tried flashing image-xxxxx-zip as a zip file,in ruu mode?
Click to expand...
Click to collapse
I indeed tried this as a last chance hoping it would bypass bootloader lock protection. It didn't work since I think the factory image is not signed by HTC as RUU are . It also lead to a fastboot crash. Now sending my nexus 9 for RMA
Sent from my HTC One using XDA Free mobile app
remedya said:
This has been useful as the update from 5.0.1 to 5.0.2 kept failing on my rooted device. It was successful and educational.
Click to expand...
Click to collapse
Same here. The manual flash method worked very well. Here's hoping that Google doesn't muck 5.1
cant flash stock rom
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
nyasha1935 said:
I'm trying to downgrade my nexus 9 from DU rom 5.1.1 to stock for everything. I'm running the flash-all.sh on linux while my tablet is in bootloader mode. Tab makes and few checks and reboots automatically in bootloader mode. I reboot tablet and still has the DU rom. Any tips
Click to expand...
Click to collapse
Art Vanderlay said:
The flash all script doesn't seem to work on linux. You shouldn't have a problem if you write the commands out manually.
Click to expand...
Click to collapse
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
cam30era said:
As indicated, the flash all script doesn't work very well on any system. Flash each .img separately via fastboot.
Click to expand...
Click to collapse
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
doitright said:
Problem is that the tgz is too big for the device's buffer, so it craps out before it actually writes the images. Its been this way for a while over several different nexus devices. Kind of like nobody at google ever even bothered to test the process.
Click to expand...
Click to collapse
I agree.
I also used Linux but I executed the commands individually rather than using the script. It worked.
remedya said:
I also used Linux but I executed the commands individually rather than using the script. It worked.
Click to expand...
Click to collapse
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
nyasha1935 said:
I cant flash system.img I get error
sending 'system' (1108544 KB)...
FAILED (remote: data length is too large)
finished. total time: 0.105s
Click to expand...
Click to collapse
Update your Android SDK.
These instructions also worked with 5.1.1
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
maxtcee said:
im trying to install back to facctory i erased my system and recovery and data and now when i try to flash bootloader i get error cannot open bootloader someone please im stuck in bootloader mode
Click to expand...
Click to collapse
Are you writing the full name and file path for the bootloader img?
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
NOTE: You must have your bootloader unlocked. If you've never unlocked your bootloader, I don't think there's any way to do this without wiping your data.
STEP 1: Install fastboot
Fastboot is Google's utility for flashing factory images. You can also use it to flash custom recoveries like TWRP and CWM. The standard way to get is is through Google's Android SDK, but that's a bit heavy-duty, so you can also download just the most important tools (fastboot and adb) separately, packaged by users. Here are some links:
Official Google Android SDK (cross-platform): http://developer.android.com/sdk/index.html#Other[1]
Unofficial for Windows: http://developer.android.com/sdk/index.html#Other[2]
Unofficial Mac/Linux: http://code.google.com/p/adb-fastboot-install/[3]
Windows users might also need to install drivers: http://developer.android.com/sdk/win-usb.html[4] (can any Windows users confirm whether it's necessary?)
STEP 2: Prepare factory image
Download the latest Nexus 6 factory image at https://developers.google.com/android/nexus/images#shamu[5]
Unzip it and open the resulting folder
Unzip the "image-shamu-*.zip" file in there
You should now be looking at something like this: http://i.imgur.com/mzrfwrP.png [6]
STEP 3: Flash! (Ah-ahhhhh! [7] )
Connect your phone to your computer via USB, and enter the bootloader. You can enter the bootloader by holding down the power and volume-down buttons to boot. Once you see the bootloader, you can release the buttons.
Open a terminal/command prompt. The syntax might be slightly different on Windows than on Mac or Linux, but basically the same. Anything you see in <> you need to replace, e.g. with the actual path to your factory image folder. The rest you should be able to copy and paste. (Tip: you can easily enter a folder path into your terminal/command prompt by simply dragging the folder onto your terminal window. This works on Mac, Windows, and the vast majority of Linux GUIs.) Enter these commands:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Reboot the bootloader.
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
cd <image-shamu-lmy47d>
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
If you DO NOT use a custom recovery (like TWRP or CWM), then also: fastboot flash recovery recovery.img
Don't worry if you see messages like "target reported max download size of 1073741824 bytes". Just wait and let it finish.
Reboot your phone and enjoy. It's normal for the first boot to take a while. Going from Kitkat to Lollipop took about 20 minutes. Going from 5.0 to 5.0.1 took 5-10, I think. YMMV.
A WORD OF WARNING: If you're moving between ROMs, you generally should do a complete reset, including wiping data. Many users have reported problems going from KitKat to Lollipop without wiping data and recommend a factory reset anyway. If you're okay with wiping everything, you can simply use Google's included flash-all scripts, or flash the userdata.img file yourself. Personally, I'm not going to bother wiping adta for an incremental update like 5.0.1->5.1. As always, be sure to back up your data!
Shamelessly stolen from: http://www.reddit.com/r/Nexus5/comments/2phqy7/howto_upgrade_android_using_nexus_factory_images/
Shouldn't you also fastboot reboot bootloader after radio flash?
This is the scenic route.
I tried to update using wugz, without unlocking the bootloader. failed. Oh well, I'll wait to receive ota
Unless this method doesnt require unlocking?
If you have an OTA zip file, this is different than using a System Img?
I do not think you need to lose data or unlock your bootloader?
Found a link for the OTA zip file.
If I remember right you can copy the zip to you phone with a USB cable.
Go into the bootloader, Volume Down and Power.
Select the zip.
I did not think you needed a terminal and all the commands if you had the OTA zip on your phones SD card.
Am I wrong does something like this not work?
or
I can just wait.....
This worked great.
I was unbranded with VZ sim, unlocked, rooted with TWRP recovery. Didn't want to lose all that nor my apps or data. This method upgrades to 5.1 without any loss.
When I was done with the flashing, I rebooted to TWRP recovery (not system) in order to wipe dalvik and cache (just to be certain). I wiped and then rebooted to system. TWRP noticed I didn't have SuperSU installed so it installed it for me. Meaning, once I got my system rebooted, I still had root too.
All in all, this process worked great for me. Thanks.
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
---------- Post added 14th March 2015 at 12:17 AM ---------- Previous post was 13th March 2015 at 11:53 PM ----------
Nikos2k said:
I run the first two commands
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
fastboot reboot-bootloader
they worked, then i moved to the radio
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
but it failed.
Any idea?
Click to expand...
Click to collapse
This is the message after the radio flash command:
fastboot flash radio radio-shamu-d4.0-9625-02.95.img
target reported max download size of 536870912 bytes
sending 'radio' (85422 KB)...
OKAY [ 2.697s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing modem ...**☺
FAILED (unknown status code)
finished. total time: 3.721s
Why the failed message?
I'm decrypted. Will this re encrypt my Nexus or do I have to flash a non enforce img?
Thank you, this really helped.
Since my bootloader was locked i had to unlock it as well.
Had a bit of a scare with the whole erasing screen staying on for too long.
Went back and redid the process, and went downstairs for 5 minutes, came back and phone was booted.
Anyway, thank you again
Will this work on an encrypted phone?
mikeadamz said:
Tired of waiting for the OTA? Can't use it because you're rooted? Don't want to wipe your entire phone? No problem! Here's how you can upgrade with Google's Nexus factory images without wiping your apps or sdcard.
<<snip>>
Click to expand...
Click to collapse
I don't suggest that anyone read and follow someone else's instructions when doing something like this. Not because the instructions are wrong or anything, but because blindly following instructions doesn't involve *understanding* anything.
So rather than reading and following instructions, read and UNDERSTAND the process of installing factory images as delivered with the factory images (flash-all.sh). If you UNDERSTAND the process and what everything does, then (a) you *already know* what needs to be adjusted to do what you want, and (b) if something starts going wrong in the middle of it, you will understand why, and what to do to correct it.
mikeadamz said:
cd </path/to/shamu-lmy47d>
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.08.img
Click to expand...
Click to collapse
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Nick D said:
First, thanks for the write up, I do greatly appreciate it. Second, thanks for the tip on dragging file locations into the command prompt. Very helpful.
Now my question. When I did this I tried using exactly the steps above and had no luck whatsoever. I'd cd to the location of the img files as noted and it would say fastboot is unrecognized as an internal or external command. I moved the file into the fastboot location and got the same issue. I finally ran the fastboot from the adb folder location and just referenced the full file path for each img file (using the drag and drop method) and everything went swimmingly. My question is just about using fastboot. Should it have worked when I used cd to go to the img file location? Is there something I need to do to make it work as you described?
Thanks!
Nick
Click to expand...
Click to collapse
Install this:
http://forum.xda-developers.com/showthread.php?t=2588979
Now ADB and fastboot are installed system wide. Put your files anywhere, I use the desktop. Hold shift and right click on wherever your files are and select "open command prompt here" and flash away. Simplified, no more dragging and dropping.
Will try with the new update (5.1.1 (LMY48M)) to ensure it works. Thanks!
[/COLOR]
handyarrow said:
Will this work on an encrypted phone?
Click to expand...
Click to collapse
Have been flashing this zip in twrp after the fastboot stage without an issue for the last few updates - http://forum.xda-developers.com/nexus-6/development/mod-disable-force-encryption-rom-kernel-t3000788
Flashed LMY48M with fastboot method and it works great.
My phone is encrypted.