Related
Hello everyone,
Need some help here, i don't want to factoy flash again, i have a nexus 7 2013 wifi on Lollipop (5.0) rooted with a custom kernel and TWRP.
How to update with the new OTA to 5.0.1, without loosing data and without having FC after the flash ?
Is there a way to flash it with TWRP or with Nexus Root Toolkit ?
I read that i can download the 5.01 system image from Google, extract the system.img from it and flash it in fasboot and i will conserve my data and be updated to 5.0.1.
Is that correct and without issues?
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
Is running fastboot format cache necessary?
^I'm no expert but I can't see why not to run it, not going to hurt anything and could possibly save you some problems later.
anhhuy1605 I'd just go to the factory images page download it and do a full clean install. I would not recommend trying to upgrade from KK and keeping data. Though I'm sure it's worked fine for lots of people.
yosmokinman said:
^Yes.
Fastboots the best way to go. No toolkits needed. Takes a couple minutes.
The normal commands to update would be:
fastboot flash bootloader bootloadername.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot reboot
Since the bootloader didn't change you can skip that part. The kernel (boot) didn't change either this time I don't think but I'd flash it always when flashing system.
Just drag system.img and boot.img to your fastboot folder (platform tools if you downloaded the sdk), hold shift and right click> open command window here then run the above commands.
Let it boot then reflash su from twrp.
Pretty sure you can also drag the image-razor.zip to your fastboot folder and run fastboot update imagename.zip. You will have to reflash twrp though.
Click to expand...
Click to collapse
It's all done, i flashed only the system.img then TWRP and elementalx, i can't live without the DT2W.
Thank You for your very detailed post.
anhhuy1605 said:
Hi, this is a little off topic.
I have a 4.4.4 rooted one and it failed to update to 5.0.1. Now it says system is update even though it still 4.4.4. Is there anyway for me to fix it and get update?
Click to expand...
Click to collapse
First thing first:
1. Uninstall any mod and busybox and xposed (Make sur that your system is clean) thant Unroot with supersu
2. Flash the stock boot (kernel) and stock recovery
3. Sideload the ota for 5.0 and flash it
Hopefully it will be allright but don't forget to backup your data with titanium backup to your computer.
Hello eddy0147,
from where did you get the system.img for 5.0.1?
eddy0147 said:
It's all done, i flashed only the system.img then ...
Click to expand...
Click to collapse
Thanks!
tungdil
tungdil said:
Hello eddy0147,
from where did you get the system.img for 5.0.1?
Thanks!
tungdil
Click to expand...
Click to collapse
If you decompress the new Factory Image from here : https://developers.google.com/android/nexus/images
You're welcome
Thank you very much! :good:
Actually I expected that this factory image would also only contain a system.new.dat just like the LRX21P did before. That's why I din't even have a look at it. I just downloaded and extracted it, and could convert it to a mountable image (using simg2img)
Cheers,
tungdil
P.S.: Just finished flashing Stock 5.0.1 as secondary ROM with MultiROM after building a flashable zip using this system.img. Thanks again eddy0147 for the hint :good:
hey
when my phone boots shows that my device is not verified by google , what to do?
Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.
Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?
sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551
Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM
Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully
Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again
sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro
I have an 8T, it's the same of 8 only with the Nfc, can i use the ginkgo rom?
If you are referring to the MIUI EU ROM you could try, but it will probably fail and nobody has tried it yet.
The issue is we have no way (yet) to recover the device if will bootloop. We have the full ROM file, but it's a recovery zip: inside the zip I can't find a recovery we could flash in fastboot.
EDIT:
Download this recovery for RN8 https://www.androidfilehost.com/?fid=4349826312261617206
Extract the file and rename it to recovery.img
Reboot the device in fastboot and run
"fastboot boot [recovery.img]"
This will NOT flash the recovery but only boot it. If it loops, just reboot the device and will be back to normal.
olivercervera said:
If you are referring to the MIUI EU ROM you could try, but it will probably fail and nobody has tried it yet.
The issue is we have no way (yet) to recover the device if will bootloop. We have the full ROM file, but it's a recovery zip: inside the zip I can't find a recovery we could flash in fastboot.
EDIT:
Download this recovery for RN8 https://www.androidfilehost.com/?fid=4349826312261617206
Extract the file and rename it to recovery.img
Reboot the device in fastboot and run
"fastboot boot [recovery.img]"
This will NOT flash the recovery but only boot it. If it loops, just reboot the device and will be back to normal.
Click to expand...
Click to collapse
Ok thx, what about the custom aosp roms?
zikam12 said:
Ok thx, what about the custom aosp roms?
Click to expand...
Click to collapse
Well, try this step first. Without TWRP, you can't flash anything.
zikam12 said:
I have an 8T, it's the same of 8 only with the Nfc, can i use the ginkgo rom?
Click to expand...
Click to collapse
Yes it loading (but without Nfc and maybe wifi won't work)
soket1 said:
Yes it loading (but without Nfc and maybe wifi won't work)
Click to expand...
Click to collapse
you've tried?
zikam12 said:
you've tried?
Click to expand...
Click to collapse
Instructions
soket1 said:
Instructions
Click to expand...
Click to collapse
Can u translate it? Pls?
zikam12 said:
Can u translate it? Pls?
Click to expand...
Click to collapse
Instructions from Pilprod
Conditions: unlocked bootloader, access to Fastboot, computer with ADB and all drivers.
TWRP
Ginkgo v10.3.5.0.PCOMIXM firmwares for fastboot
1. Load the phone in Fastboot and connect to the PC.
2. Download the firmware and recovery from adb on the links above.
3. Unpack the recovery with adb in the folder (for sample: C:\\adb)
4. Unpack the firmware .
From the image folder, copy system.img, recovery.img and the boot.img, to folder with TWRP and adb.
5. Open the command line and write .
cd C:\adb
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Click to expand...
Click to collapse
If everything is done correctly, the phone should start booting from the bootleg Redmi Note 8
6. After booting into the system, you can try and experiment with the firmware from RN8.
If you want to return to Redmi note 8T firmware and / or put TWRP and ROOT, then again load the phone in fastbut and continue.
fastboot flash recovery twrp.img
Click to expand...
Click to collapse
Loading into recovery.
After downloading TWRP, if you want to firmware Redmi note 8T, then do Wipe Data, System and all caches, without closing TWRP, copy to the phone this firmware, flash and boot into the system.
Hi all !!!
so did anyone manage to flash a ROM from the redmi note 8 on the 8T ?
hello,
My phone is deblocked, i'm an Mioi 12.5 and android 11, then.
I want to install twrp 3.629 or twrp-unified with adb and fastboot on my RN 8 pro :
adb reboot fastboot => ok
fastboot flash recovery twrp.img =>ok
fastboot reboot recovery => unknow reboot target recovery !!!
with xiaomiadbfastboottools.jar, it's the same, i can install my twrp.img, but can't restart in recovery mode (it's grey), and the phone restart in system !
Where i'm wrong ? and what may i do ? may i do install magisk ?
Thank you for your help !
avecousans said:
.....
adb reboot fastboot => ok
fastboot flash recovery twrp.img =>ok......
Click to expand...
Click to collapse
I used the command: fastboot flash recovory recovery.img after renaming twrp.img.
Perhaps that helps.
Thank's ! But it dont work
I see somewhere that this twrp don't work with the RN8P based on MTK
So, i extract vbmeta.img and patch with :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img =>ok
and flash the twrp => ok .... but always the same, i can't reboot in recovery mode, with fastboot or with button power + up
I can't install twrp, still.
avecousans said:
Thank's ! But it dont work
I see somewhere that this twrp don't work with the RN8P based on MTK
So, i extract vbmeta.img and patch with :
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img =>ok
and flash the twrp => ok .... but always the same, i can't reboot in recovery mode, with fastboot or with button power + up
I can't install twrp, still.
Click to expand...
Click to collapse
Did you try older TWRPs?
bmwdroid said:
Did you try older TWRPs?
Click to expand...
Click to collapse
No, it seems to be the last on, the 3.6.2.9 for bégonia, find on the official Twrp site
avecousans said:
No, it seems to be the last on, the 3.6.2.9 for bégonia, find on the official Twrp site
Click to expand...
Click to collapse
I know but not all official TWRPs are tested working as I had to learn myself.
avecousans said:
No, it seems to be the last on, the 3.6.2.9 for bégonia, find on the official Twrp site
Click to expand...
Click to collapse
3.6.2_9...
And "_9" mean for Android 9 version of Miui and custom rom based on that.
If you want to use TWRP in Miui 12.5.x, find TWRP for Begonia that name "3.x.x_11". And sure it's unofficial.
Oh good !
I try it soon as possible
thank you for your help, i can install twrp 3.6.0.11 and it's allright !
I'm new to Xiaomi devices , I Have Xiaomi 11 lite 5g ne ( lisa ) global version ( Snapdragon 778G 5g ) and I wanted to install the cherish os 4.2 on it but I don't know how to flash the custom recovery for it, can someone please tell how to flash it step by step? I'll be so grateful.
Did u unlock bootloader ??
If not u must do it first
After register for unlock u must wait 7days to unlock...
boneszbo said:
Did u unlock bootloader ??
If not u must do it first
After register for unlock u must wait 7days to unlock...
Click to expand...
Click to collapse
Yes, I only want to know how to flash the custom recovery for the cherish os step by step
Muneebos77 said:
Yes, I only want to know how to flash the custom recovery for the cherish os step by step
Click to expand...
Click to collapse
Reboot to bootloader (fastboot)
Connect the phone to PC
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
If already on custom ROM skip the previous steps and flash with your recovery
fastboot reboot recovery
Select Wipe data/factory reset & confirm
Go back and select Apply update from ADB
ADB sideload Cherish-OS*.zip
After installation is complete, Reboot the system.
Thanks but I don't know how to this :
" • fastboot flash boot boot.img
• fastboot flash vendor_boot vendor_boot.img "
If you can tell how exactly I can do it ( detailed step by step) I'll be so thankful.
you have to enter fastboot mode of your phone. hold volume down and power button on booting. You will see in orange letters "FASTBOOT" on your display. Then connect your device to PC
the boot.img and vendor.img are files which you will find here also the newest cherish os rom version is there.
"fastboot ..." are the commands you need when your phone is in fastboot mode connected to your PC (type in Commandline)
you need Minimal adb and fastboot tools on your PC
don't forget to format Data before flashing zip file in recovery.
so , I should download the both files , boot image and the vendor image , and after that in the cmd , I just type the commands without dragging the files ?
Muneebos77 said:
so , I should download the both files , boot image and the vendor image , and after that in the cmd , I just type the commands without dragging the files ?
Click to expand...
Click to collapse
yes
This YouTube video helped me to install custom recovery and custom ROM on my 11 lite 5G NE Global
I watched it , but I don't know if the same method will work with the cherish recovery or not because it has 2 image files
Muneebos77 said:
I watched it , but I don't know if the same method will work with the cherish recovery or not because it has 2 image files
Click to expand...
Click to collapse
Which 2 image files do you mean? Here are all files you need. (boot.img vendor_boot.img; just rename them) and cherishOS in Version 4.1 and 4.2
I installed it yesterday from this source:
CherishOS - Browse /device/lisa at SourceForge.net
sourceforge.net
sensimilia1982 said:
Which 2 image files do you mean? Here are all files you need. (boot.img vendor_boot.img; just rename them) and cherishOS in Version 4.1 and 4.2
I installed it yesterday from this source:
CherishOS - Browse /device/lisa at SourceForge.net
sourceforge.net
Click to expand...
Click to collapse
Oh , so I just have to download the qsvendor_boot.img ( the recovery ) ?
Muneebos77 said:
Oh , so I just have to download the qsvendor_boot.img ( the recovery ) ?
Click to expand...
Click to collapse
You need qsvendor_boot.img, qsboot.img and Cherish-OS*.zip
Oh ok
My BL is already unlocked and has the latest Miui 13 and A12 global official firmware. it will be first time custom recovery to be flashed.
I wonder if my all data to be erased during Orange fox recovery?
sas_sas said:
My BT is already unlocked and has the latest Miui 13 and A12 global official firmware. it will be first time custom recovery to be flashed.
I wonder if my all data to be erased during Orange fox recovery?
Click to expand...
Click to collapse
Installing OF to Ramdisk in Boot partition has nothing to do with wiping Data partition