I have a stock, rooted nexus 7 Flo on 5.0. I would like to move to 5.0.1 but I cannot because the update cannot install through Android because of CWM and there doesn't appear to be a flashable zip to use!
Download the system image then:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Then flash the root zip through twrp. Done.
Or you could flash the stock recovery, flash the OTA, then reflash CWM.
yosmokinman said:
Download the system image then:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
Then flash the root zip through twrp. Done.
Click to expand...
Click to collapse
nhizzat said:
Or you could flash the stock recovery, flash the OTA, then reflash CWM.
Click to expand...
Click to collapse
Won't this wipe all my data? I don't want to redo my device.
No it won't wipe data. Data will only be wiped if you use the flash-all file without removing the -w or fastboot flash userdata.
That was useful!
Related
What are the commands for flashing a rom in fastboot?
Ive tried
Code:
fastboot flash ----.zip
?
Am doing this cause JOKERDROID4.2BUZZ.zip wont flash in clockwork mod 3.2.0.0 or 4.0.0.2. It flashes in 2.5.1.7 but boot loops. I am coming from cm7 what do you think?
You can only flash a particular partition with Fastboot, like /system /data, Recovery, boot etc. AFAIK, You cant flash a Zip ROM as is the case with CWM.
You can check the list of Fastboot Commands here:
http://android-dls.com/wiki/index.php?title=Fastboot
Also, you got 2.5.1.7? Where? AFAIK Wildfire only has 2.5.0.7. Anyway, you can use Fastboot to replace your CWM 3.x or 4.x with 2.5.0.7, then try flashing Jokerdroid. Also, make sure you are performing a wipe (Factory Reset / Wipe data in Clockworkmod)
Where can i get 2.5.0.7?
Cant remember where i got 2.5.1.7 the file name was 2.5.0.7 but cwm said 2.5.1.7?
It's there under Custom Recoveries:
http://forum.xda-developers.com/showthread.php?t=1029318
jokerdroid just bootloops!?
i have wiped and wiped cache and delvik!
Try Redownloading the ROM. Or, if you search the thread, there is one version which is clocked at 648MHz. Try that. Probably the high CPU clocks are not suiting your device.
EDIT: Scratch that. Its clocked at 710, so shouldn't cause an issue.
Well after boot looping 5 or so times it rebooted cwm then rebooted system and bootlooped once but the powered up? Wierd!
if you want to flash a .zip package:
fastboot update filename.zip
if you want to flash an img. file:
depending whether you want to flash a new recovery:
fastboot flash recovery filename.img
or a new ROM:
fastboot flash system filename.img
I do however strongly recommend erasing you current recovery before flashing a new one:
fastboot erase recovery
and do a full wipe (this will erase your data, recovery and system partitions)
fastboot erase system -w
Hi, I recently installed official android 5.1 from factory source but now I have issues "missing" storage.
32GB Nexus 7 2013 (Wifi)
TOTAL: 26,9 GB
Used: 17,3GB
Free: 9,6GB
Theese numbers are not supposed to be what they are right out of the box with barely no apps installed and nothing else stored. I am supposed to have much more free space.
I followed this guide to install every .img file manually that was included in the official factory images.
Install instructions followed:
Flash bootloader and radio (radio does not appear on all devices, if it's not in your tgz, you don't need it)
fastboot flash bootloader <bootloader file name here>.img
fastboot flash radio <radio file name here>.img
After flashing the bootloader/radio, you need to reboot the bootloader as shown below, don't skip this step!
fastboot reboot-bootloader
Now you can move on to the rest of the files
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
NEXUS 9 ONLY - flash this as well
fastboot flash vendor vendor.img
If you want to wipe cache and user data (full wipe), flash these
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Finally, just reboot your device, and Android should start up.
fastboot reboot
The reason that I "manually" flashed every .img file is because I got errors when using the flash-all.bat file
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 842365088 bytes
error: update package missing system.img
Thanks in advance for help!
EDIT:
Confirmed: factory reset/data wipe in stock recovery solved the storage problem
Try formatting data with twrp. That fixed the no storage problem I had a while ago.
yosmokinman said:
Try formatting data with twrp. That fixed the no storage problem I had a while ago.
Click to expand...
Click to collapse
I haven't installed TWRP yet, do you know if it supports 5.1? Any chance that the stock recovery can do the same?
You could try a factory reset/data wipe in stock recovery. Latest twrp works fine.
yosmokinman said:
You could try a factory reset/data wipe in stock recovery. Latest twrp works fine.
Click to expand...
Click to collapse
Confirmed: factory reset/data wipe in stock recovery solved the storage problem
Thank you very much
my nexus 32gb is showing like 26.5gb after the update for 5.1 this is normal value? 6gb is consumed by the OS or something?
my device is fullwiped
So I flashed Euphoria OS in my Zenfone 2 ZE551ML 16GB variant but now I wanna go back to stock rom. So I downloaded a full stock rom version WW-2.19.40.22. I booted into TWRP recovery, wiped data and all and then flashed the stock rom and then this assert failed get prop error appears. I can't flash the stock rom and I'm stuck with Euphoria. Any info on how I can get back to stock rom?
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
knoneNull said:
hello i think your devices is unlock you can use a system.img to revert back to stock if you came from custom rom
fastboot erase data
fastboot erase cache
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
then reboot if you stuck on asus logo re flash again the system.img and your done..
---
second option is flash stock recovery and boot.img and use adb sideload for flashing stock rom good luck
Click to expand...
Click to collapse
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
caveat13 said:
I'm unable to use the adb sideload method. My device disconnects when I activate sideload on it but it reconnects when I cancel it.
Click to expand...
Click to collapse
try to charge it first , then try again, if not work i think the best is send to service center or try to message shakalaca may be he can help you
SO, i'm trying to ADB sideload the latest firmware (MRA58V), but when I go to the google developers website, it downloads in a .TGZ file.
https://developers.google.com/android/nexus/images
I've tried changing it to .ZIP, then flashing, but it fails invalid signature.
What am I doing wrong?
Thanks,
Thread moved to proper forum
Simply flash the .img files inside the zip with fastboot. Takes 2-3 minutes.
Since only boot and system changed that's all you need to flash.
The commands I used today for 6.0.1:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot reboot
That's it, doesn't wipe anything.
yosmokinman said:
Simply flash the .img files inside the zip with fastboot. Takes 2-3 minutes.
Since only boot and system changed that's all you need to flash.
The commands I used today for 6.0.1:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot format cache
fastboot reboot
That's it, doesn't wipe anything.
Click to expand...
Click to collapse
Thanks worked perfect.
Sent from my SM-G920T using XDA Free mobile app
All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance
Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.