Installed on my nexus LOLIPOP version through ADB / Fastboot.
How should I do now to upgrade to 5.0.1?
Do the same with the 5.0.1 image.
Thiagooo said:
Installed on my nexus LOLIPOP version through ADB / Fastboot.
How should I do now to upgrade to 5.0.1?
Click to expand...
Click to collapse
You can With adb sideload update ota manually without lose data
Here's how to upgrade to 5.0.1 on rooted Nexus 5
N/A
Err...
Why are you... Original question has been addressed already.
Yeah. I'm sure. Please stop suggesting toolkits to people.
Edward.Bernard said:
This is an easy way to upgrade to 5.0.1 without losing any data, though you will lose custom recovery and root. But those are easy to recover and are included here...
Setting up
You'll need a Windows PC, Nexus Root Toolkit software (WugFresh), and Flashify app (or similar)
Actually, the NRT software is not needed, but it makes the process stupidly easy. You can also do this by fastboot over ADB
Be sure to perform a full nandroid backup, just in case, though you shouldn't need it.
And absolutely backup your custom recovery using Flashify (or whatever you use)
Factory images
Forget about the OTA update and go to the Google Developers site for the factory images you want
Download the file to your PC, then unzip it and any zipped files contained within it (it's like one of those Russian dolls)
Now find the .img files for "boot," "bootloader." "radio," and "system." Move them into a new folder that you can easily find.
There are other image files, but you don't want those, because they'll over-write your data.
Flashing using Nexus Root Toolkit
Open NRT and be sure that you select your CURRENT model and build in the upper left-hand corner.
Under Advanced Utilities, click Launch
Under Fastboot Flash, click Boot [Kernel], then browse for you boot.img file and click Open.
Let NRT do the rest.
Repeat this Fastboot Flash process for Bootloader, Radio, and System in that order.
After you flash the system image, your Nexus will reboot and complete the update.
Re-root
In the process, you've lost root so reboot your phone back into bootloader
In the NRT main menu, change your model and build in the upper left-hand corner to reflect 5.0.1
The software will need to restart and update.
Now, under the Root heading, click Root
When your phone reboots, your superuser will request to be updated. Allow it, and reboot.
Now open Flashify, flash your custom recovery, and reboot.
You're done!
Click to expand...
Click to collapse
Boooooooooooooooooooooooooooooooooooooooh Learn how to use adb and fastboot yourself and teach this to inexperienced users.
Incredibly complex solutions.......!
Easier just return to stock flash via OTA and reroot... I think this is the easiest method (despite for me is still a little bit ****ty) to go with Android latest updates
Don't like the Google Dev imaging and flashing option
I dont know if this ota zip will work but you can try?, assuming you dont want to lose your data by going with googles images
phandroid.com/2014/12/15/nexus-5-6-android-501-factory-image-ota-update-zip/
MiSSigNNo said:
Incredibly complex solutions.......!
Easier just return to stock flash via OTA and reroot... I think this is the easiest method (despite for me is still a little bit ****ty) to go with Android latest updates
Don't like the Google Dev imaging and flashing option
Click to expand...
Click to collapse
How is that the easiest solution?
Flash stock, then ota? Why not just flash 5.0.1 stock and NOT ota?
rootSU said:
How is that the easiest solution?
Flash stock, then ota? Why not just flash 5.0.1 stock and NOT ota?
Click to expand...
Click to collapse
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
JayR_L said:
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
Click to expand...
Click to collapse
Its hard on a forum where punctuation isn't used often. I envisage that there should be a comma between "stock" and "flash". True, it could also be a full stop missing.
That said, I've seen many threads where people just say flash stock then ota so I've assumed this is the same..
JayR_L said:
I believe that is what he meant, just picked the wrong words. He meant 5.0.1 image when he used the term OTA.
Click to expand...
Click to collapse
With the NRT you just go back flashing to stock bootloader and then you can upgrade via OTA no-pain. After that you can reinstall back twrp (for example) and re-root device. No downloads required from external sources.
If you have to flash you have to go and pick the img and after that re-root. For me is a pain looking for the flash img every version! And worst part having to reboot for each image... boot, radio, system...
But I suppose it is a matter of preferences.
3 step method:
{
"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"
}
PD: BTW 5.0.1 only have boot and system for flashing?
Still though... Toolkits are bad. Use them at your peril and if you screw up, we're not wasting our time teaching the basics to fix it, that you would know if you did it properly the first time.
And reboot each time? What???
...and looking for image every time? Same place every time mate
You shan't need a toolkit. For one, Google themselves have put instructions on how to flash a factory image directly. And again, you shan't use toolkits.
And you DO NOT reboot for every image. You flash all of them at once, then you reboot.
Anyway this thread has degenerated to, plain and simply, diarrhea.
Related
and i went on this link below
[How To] Flash ICS ROMs with S-ON Unlocked
I'm assuming you have
•Fastboot set up as a PATH, or copied to the folder you are extracting boot.img to
•HTC Drivers installed
•Clockwork Recovery
i have the drivers installed but i dont know the path and its not giving me details and to make it easyier to me i put everything on my desktop so please help me out here cause im about to sell this device and buy myself a g2 or g2x or a samsung android phone i really like bulletproof rom installed bad all i need for help is get CWM on this phone then i can handle it from there thanks.
you can download rom manager from play and install cwm
{
"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"
}
You at least have to be unlocked and rooted. You're obviously not rooted, yet.
see
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Just being unlocked is not the same as being rooted. You need to be Unlocked AND rooted to install CWM through Root Manager. You're only half of that.
Coug76 said:
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
nope im having trouble doing that i need help on that part
With an unlocked bootloader I simply copy the fastboot and adb files, as well as whatever recovery image I want to flash and push the recovery via fastboot... however if you aren't confident in your skills with the command prompt or fastboot there is always the all-in-one toolkit for the MT4GS that can be downloaded from its own thread in the dev forums (I don't have the link handy but it seemed to work for me on my sister's mt4gs).
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted. I am also unable to install anything like Busybox or ROM Toolbox. It seems like the root just wasn't properly set up but none of the methods I've found actually work. I have tried to redo the rooting process, but to no avail.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
I'd say do a flash of CWM via adb. Then install Superuser through CWM using a zipped Superuser. Worked flawlessly for me.
yupThisIsMyName said:
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
Click to expand...
Click to collapse
Are you using the trackpad to select things in recovery? All of my other phones used power while in recovery to select things but the doubleshot uses trackpad to select
Sent from my myTouch_4G_Slide using Tapatalk 2
I'm of two different schools of thought here - my first thought is bad download of CWM... Honestly I'd just read up on fastboot flashing the recovery image and do that to ensure a good root. However as noted above the trackpad select did throw me off at first.
Sent from my myTouch_4G_Slide using XDA
OK, it looks like I don't actually have S-Off and I've got the newer Hboot which, from what I can tell, prevents me from using this method and the only two ways to do this seem to involve either doing some crazy stuff with wires or flashing stuff without taking a backup first. Both of these methods make me very nervous, especially since as far as I can tell there is no way to use anything like Odin or RSD Lite with this phone to restore it in case something gets messed up.
If anyone has a way I can take a backup before flashing a ROM or, better yet, has a way to restore the phone completely in case something goes awry that would be awesome.
Update: Yeah, looks like it was the trackpad thing preventing me from doing this properly. Totally bizarre considering the fact that I was able to select things just fine using the volume buttons but when I hit power (which selects on most devices), it didn't work right.
Thanks for helping me get past this hurdle everyone! Hopefully I can figure out how to get s-off.
Edit: Update - I flashed a ROM that already had root and now that works too. Good enough for now, I'll wait for a less scarey method to get S-off. I'm not about to start messing around with wires.
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
jaycuzhommie said:
Ive tried several rooting methods and ended up bricking my phone every time. I'm running 6.0.1, build number mmb29k.n920tuvu3dpg1. Recently heard of cf-auto-root but the package they have has a different build number(MMB29K.N920TUVU2DPD1) with the model number and android version being the same. Will the cf-auto-root method work? Or should I be using a different method? (I'm new to this whole rooting thing, came over from iPhone. Jailbreaking was far easier)
Click to expand...
Click to collapse
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image.
{
"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"
}
already the firmware the have for future if you wish render it to stock and clean
javierduran said:
to the be a novice as i, him agrees read well and and follow the instructions of post # 2 here
http://forum.xda-developers.com/tmo...rom-n920tuvu1boh4-5-1-1-deodexed-ciq-t3194270
as already have the last firmware not have that install still the instructions since the step # 7 as in the image. View attachment 3848895
already the firmware the have for future if you wish render it to stock and clean
Click to expand...
Click to collapse
This is a much better guide for his model
http://forum.xda-developers.com/showthread.php?t=3361990
Sent from my SM-N920T using Tapatalk
You only have to do is flash TWPR in odin (don't forget to uncheck F. Reset time and auto-reboot) before you flash the recovery, download the flashable Super SU and place it on SD , memory, otg or wathever. Just flash recovery, when odin ends, then boot directly into recovery and flash the super su and you are done. if you no want to install custom recovery, you must look for other options
clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Click to expand...
Click to collapse
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
The Apostle said:
I've read through a lot of the rooting threads here. From what I can see, the older stuff (2015) required flashing a new kernel as well. Is that just not the case anymore? Did I misread?
Click to expand...
Click to collapse
That's correct the new SuperSU modifies the kernel for you
Sent from my SM-N930F using Tapatalk
clsA said:
Don't make it harder than it is
Odin flash TWRP
Boot to recovery
Copy the newest version of SuperSU to the phone and flash it
Reboot ...your rooted
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
wrecless said:
I have attempted this twice and both times no luck. First attempt I flashed via odin the twrp .tar file and it was blocked by FRP. Had no clue what that was because there is no mention of it in the guide posted. Second attempt I turned on Oem unlocking in settings menu thinking that would work and flashed that successfully but the phone wouldnt boot or go into recovery. I ended up flashing the stock DPG1 firmware to fix the no boot issue and now im back at square one.
Am I missing something? Been rooting and Roming my phones forever but need a little help with this 1 thanks.
Click to expand...
Click to collapse
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
The Apostle said:
It works. I did it again last night after taking the PG1 update. All you need to do is... 1) boot into DL mode. 2) flash the TWRP tar file in the AP slot via Odin. 3) flash SU in recovery. That's it... you're done.
Click to expand...
Click to collapse
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
wrecless said:
Strange because thats exactly what I did. After flashing TWRP with oem unlock off in Odin all the phone would to is either show the T-mobile logo forever or boot to download mode. I saw something about removing google account. Did you also do that first?
Click to expand...
Click to collapse
I've did not remove my Google account. I've read that too but believe the circumstances were different.
You said you have OEM unlock ticked off? Should tick it on (so it shows blue)
You may want to dload the official PG1 FW from Sammobile.com and flash from scratch.
Hey Xda,
I have an S7 International G930f and the stock boot image wont flash in odin without bootloop, after frp unlock. So basically ive flashed the G930F(ENGroot) file, but the second part, flashing the boot img isnt flashing without bootloop.
So yeah- my phone is acting weird, im surprised it even works.
Running Stock Rooted 6.0.1 with TWRP
I've rooted/recoveried many a Samsung, but all this Dmverity, FRP unlock, these newer protocols have me confused.
I've got OEM unlock ON which is still a tad new to me-coming from S5. Unknown Sources Enabled. FRP Lock shows as OFF.
I've followed an FRP unlock guide-XDA here but the boot image wont take. Tried many times. Maybe its my July 1st Security patch?
Can someone tell me what i need to do to get this phone to where it is FRP unlocked, dmverity gone,keep root/recovery and update it?
p.s. I'm getting tons of bugs, random reboots, and WiFi passwords aren't saved on reboot. Plz help!
Thank you!
{
"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"
}
Read the main post in the TWRP thread in the development forums, all instructions in there
*Detection* said:
Read the main post in the TWRP thread in the development forums, all instructions in there
Click to expand...
Click to collapse
Thanks for the reply. If you are referring to this thread http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 thats what i followed.
But i did have some confusion about this section below from said thread. Im not sure what OP means by "if you only want a bootable system partition". Of course i would like this to be bootable, AND i would like to install SuperSU.
Its worded strange. Ok lets assume i did this incorrectly. Would you suggest i start over, factory wipe, then move forward with that threads directions?
If twrp and super su are already installed and working, but i dont have the right boot.img flashed, should i start all over or start somewhere in particular?
10. If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
You will need an external SDcard for this method, if you don't have one you will have to use adb sideload to install SuperSU.
If you only want a bootable system partition:
Download the latest dm-verity and force encryption disabler zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
Note: This does not disable the forced encryption on Bxxx firmware, only Axxx firmware due to a change in vold by Samsung.
Click to expand...
Click to collapse
dovedescent7 said:
Thanks for the reply. If you are referring to this thread http://forum.xda-developers.com/galaxy-s7/development/recovery-official-twrp-herolte-t3333770 thats what i followed.
But i did have some confusion about this section below from said thread. Im not sure what OP means by "if you only want a bootable system partition". Of course i would like this to be bootable, AND i would like to install SuperSU.
Its worded strange. Ok lets assume i did this incorrectly. Would you suggest i start over, factory wipe, then move forward with that threads directions?
If twrp and super su are already installed and working, but i dont have the right boot.img flashed, should i start all over or start somewhere in particular?
Click to expand...
Click to collapse
"if you only want a bootable system partition" means if you don't want to flash SuperSU, but want your phone to boot correctly with TWRP installed, if you don't follow that step, regardless of SuperSU, your phone is a soft brick
Flash TWRP
Wipe Data (Yep, to disable encryption, so backup first)
Flash DM-Verity~zip
Flash Super-SU.zip
Reboot
More in depth here
http://www.droidorigin.com/root-samsung-galaxy-s7/
*Detection* said:
"if you only want a bootable system partition" means if you don't want to flash SuperSU, but want your phone to boot correctly with TWRP installed, if you don't follow that step, regardless of SuperSU, your phone is a soft brick
Flash TWRP
Wipe Data (Yep, to disable encryption, so backup first)
Flash DM-Verity~zip
Flash Super-SU.zip
Reboot
More in depth here
http://www.droidorigin.com/root-samsung-galaxy-s7/
Click to expand...
Click to collapse
hey man i do appreciate it. Thank you for confiriming,the above link worked! thank you!!!!!!!!
dovedescent7 said:
hey man i do appreciate it. Thank you for confiriming,the above link worked! thank you!!!!!!!!
Click to expand...
Click to collapse
:good:
Hey guys! I haven't been in the rooting community for a while and when I was my phone was end of life. How can I accept an OTA while being rooted?
I assume I will have to unroot through SuperSU, update like normal, then re-root with the latest SuperSU. Is that correct? I saw some using FlashFire, but I am kind of uneasy about an automated app rooting my device.
Some additional info:
Phone on Feb security update
Phone rooted with latest SuperSU
I did not install custom recovery, only booted it to flash SuperSU
I don't want to lose any data on my phone
Thanks in advance guys! Hopefully with your help I can get this bad boy updated!
Bump?
No one can help me?
Google android factory OTA. That will get you to Google's full ota which you will need to sideload with adb. Full instructions are on the page with the download. And probably a dozen how to's posted here in the last couple of days.
What I did i downloaded from herehttps://developers.google.com/android/images#sailfish unzipped the file edited the batch took the -w out saved the file and ran the Bach file re installed twrp and root should not loose anything but its a possibility this link will you better directions its what I used https://forum.xda-developers.com/showpost.php?p=71321307&postcount=31
It's a bit more involved, but I always download the latest factory image, edit the batch file to remove the "-w" which doesn't wipe it. Then I boot back into TWRP and install the TWRP zip (not necessary if you don't want to keep it), then install SuperSU zip.
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
{
"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"
}
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
What's the reasoning behind having to do each OTA in order?
joshw0000 said:
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
dejanspa said:
What's the reasoning behind having to do each OTA in order?
Click to expand...
Click to collapse
You're welcome to try going straight to the latest OTA but it's my understanding that each one only contains the updates from that specific release. If it fails you could always modify the flashall.bat file of a full restore image and flash it with your computer. Then boot TWRP with fastboot, flash TWRP from the booted TWRP, and install SuperSu.
Sent from my Pixel using Tapatalk
Okay. Also in this method you don't have to modify any file to get rid of the "-w" so it won't wipe data? If I do what you did all my files and apps should still be there when I reach the last OTA.
Sorry iphone convert so i'm new to this.
joshw0000 said:
You're welcome to try going straight to the latest OTA but it's my understanding that each one only contains the updates from that specific release. If it fails you could always modify the flashall.bat file of a full restore image and flash it with your computer. Then boot TWRP with fastboot, flash TWRP from the booted TWRP, and install SuperSu.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
dejanspa said:
Okay. Also in this method you don't have to modify any file to get rid of the "-w" so it won't wipe data? If I do what you did all my files and apps should still be there when I reach the last OTA.
Sorry iphone convert so i'm new to this.
Click to expand...
Click to collapse
Nope. Nothing to modify as long as you download the OTA files from the link I posted and not the full image files from a different section. The image files are the ones that have the flashall.bat file that have to be modified before flashing. There's nothing to modify in the OTA's. That's another reason I like my method as I have 78GB or pics/videos/music that I'd hate to lose.
Sent from my Pixel using Tapatalk
joshw0000 said:
Here's the easiest method in my opinion (No PC required). This method requires TWRP recovery.
With TWRP already installed, download the next "Sailfish" OTA from here - https://developers.google.com/android/ota. Notice I said "next", not latest. If you're several OTA's behind you'll want to download all of the updates to bring you current. For example, I started yesterday on NMF26V and these are all of the files I downloaded.
You'll also need the latest TWRP, SuperSu, and any mods you plan to install. Now we're ready to start.
Boot to TWRP and install the "Next" OTA file. No need to do any wipes, just simply flash it. When it completes, immediately flash TWRP installer, then reboot.
Now reboot back to TWRP, flash the next OTA, immediately flash TWRP again, and reboot. Continue this until you're on the latest update.
Now simply boot back to TWRP and flash SuperSu. I also installed Elemental (after an additional reboot for good measure) as I like the swipe to sleep function.
Sent from my Pixel using Tapatalk
Click to expand...
Click to collapse
Thanks, this was new for me :highfive: I always used to flash the system, boot etc, but this was a lot easier :good::victory:
Juhler said:
Thanks, this was new for me :highfive: I always used to flash the system, boot etc, but this was a lot easier :good::victory:
Click to expand...
Click to collapse
Glad I could help.
Sent from my Pixel using Tapatalk
For the April OTA update I was able to install the file that came to the phone using FlashFire. Trying to uninstall SuperSU and then take the OTA on the phone hadn't worked the previous two times I had tried it. When I tried the March OTA update on the phone with FlashFire it also didn't work, so I'm not clear if the latest FlashFire update was why the April OTA on the phone worked without issue. I thought maybe I needed to use the restore option in FlashFire to get it to work, but on the April OTA it turned out that I didn't need to use any of FlashFire's restore options like I had been planning on trying. For the April OTA to the phone, using FlashFire ended up being quicker and simpler than the previous manual process I had been doing to install the files Google posts online and then root the phone again. Since I'm using SuperSU to root the phone, I'll keep using FlashFire to update if it keeps working like it did this month.
Yeah OTA updates are patches not full OS files so must be done in order.
Using flashall with -w removed is the cleanest method as it rewrites all system files.
Personally I'm not a fan of patching the OS.
This is the Xiaomi Mi A2 Lite's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Automatic ROOT
Install APKs
Uninstall APKs
Take a Screenshot
Take a Screen Reocrd
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
Yay ^_^ Thanks for the efforts Respected devs. Hope it makes life way easier for people here at the community ^_^
unlock bootloader and root still delete all of my files right?
machine1104 said:
unlock bootloader and root still delete all of my files right?
Click to expand...
Click to collapse
Yes
Xiaomi Mi A2 Lite got messed up
Hi there!
I have just received my new Xiaomi Mi A2 Lite phone and wanted to pass all of my data from my old phone to it in a way that it was required to be rooted.
KingRoot didn't work on this new phone, so I unlocked bootloader and tried to install TWRP recovery on my phone.
Installing to the recovery partition did not work. I searched the error it gave me and found a thread saying that flashing it to the boot partition worked for them. So I did. Next thing that happened is that my phone did not boot into the OS (operating system) ever again. It only booted TWRP.
I have since been able to remove TWRP (though I made a back up of it) but the phone still stays on just the loading part before going to the OS.
I have since been able to get back the fastboot and stock recovery, but the phone will not start into the OS anymore.
How can I fix this?
I have been searching for ways to restore my android to the 8.1 Oreo version that it was.
Can I do it with this Tool All In One? Please help! Thank you in advance!! Much appreciated!!
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
chillout23 said:
hello
i have unlocked bootloader and wait for TWRP and want to root my phone.
Can I flash TWRP and root with this tool easy? And will I lost all data if do that?
Click to expand...
Click to collapse
If you need to flash twrp and root.no, you will not lose data
Ok. Thank you very much for answer
Then will try
chillout23 said:
Ok. Thank you very much for answer
Then will try
Click to expand...
Click to collapse
I would suggest using the root method mentioned here
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
Twrp does not have good results for most people.
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
chillout23 said:
With this method I will lost all data on my phone and I do not want to setup phone 1 more time. Twice was just enough
I know that already but thank you anyway
Click to expand...
Click to collapse
If your bootloader is unlocked, you should not lose any data just installing magisk
Yes...my fault. My BL is unlocked already.
But I posted in that thread...because of some reason does not work. But this is not thread about it
Thanks for help
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
chillout23 said:
So...Installed TWRP but does not recognize anything in internal storage. Not recognize SD card.
When boot again to TWRP goes to "something"...some kind of empty stock recovery with android logo and nothing more.
Oh man...that will be interesting ride...to put TWRP or root device
Click to expand...
Click to collapse
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
uptowner said:
Because your not supposed to install the twrp image just boot from it and if you do install it then you have to flash the original boot image for which ever 8.1 update your on to get rid of it.
This is explained on the team win page for daisy wish i had read that first after re flashing my os twice and boot image once trying to install this am just using the phone as is for now until i get the urge to try again
Click to expand...
Click to collapse
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
uptowner said:
Because your not supposed to install the twrp image just boot from it
Click to expand...
Click to collapse
Installed TWRP image. I know what is .img
mauronofrio said:
This tool can only boot the recovery or can boot the recovery and automatic flash the installer, i'm not udnerstanding which is the problem
Click to expand...
Click to collapse
oops sorry i should check what thread this is before trying to answer a question i blame alcohol .
Thing is there are posts out on the net that advices people with the a2 lite to install the twrp image to their inactive slot and not to just boot it and that's where things seem to start going wrong.
This has absolutely nothing to do with this tool and sorry i just dived in here and confused people.
maybe some kind passing mod will get rid of the post apologies again
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
mesuahas said:
Hi, I bought this device one weeks ago. I wanna flash new android pie OTA update. I dont know how to use this program exactly and I dont wanna lose my data and deal with brick risk.
I understood only one thing from other websites:I must use sideload method .Can someone guide me?Actually I have experience from my old devices(Note 4, Lg optimus, Xperia P) but this is new. I dont wanna broke it immediately .XD.
Click to expand...
Click to collapse
Read the op follow it exactly how it says if u don't know something research it.i have root with no problems if u do as the op says u shouldn't have no problems
Will this work on pie at all?