Database Info

[SOLVED] Rooting a Factory-S-OFF'ed Desire S (need assistance)

Hi all,
so I've been reading around here for a few weeks now. Found a few guides on rooting the Desire S and tried to get basic orientation.
Now I'd like to discuss my particular situation for a bit with you guys, before I attempt to actually do the job on my phone.
There is a slight difference between where I'm finding myself and where all the rooting guides seem to aim:
I bought my Desire S already S-OFF'ed.
You can see my exact specs at the lower end of this post.
As it appears, AlphaRev and Revolutionary are supposed to be used with S-ON devices. I'm not sure what would happen if I run these tools with my S-OFF device.
GingerBreak doesn't work with HBOOT-0.98.0002. So that won't help me either.
The most promising method i found so far is the Temproot + Revolutionary method by Silver Bullet, which has been tested on a device with the exact same Hboot and ROM build as mine, with the only exception, that I am on S-OFF.
Today I've been successful in achieving temporary root access, using the commands from Silvers thread. (I got the # prompt.)
Sof far, so good. Now I've got and S-OFF'ed device with temporary root access possibility.
Silver proposed this in a personal message (hope it's ok I'm posting it here):
You could try to get temporary root access using the commands I have posted in my guide. If you get the "#" prompt then you have root access, so you could use dd from the command prompt to a) backup your current HBOOT, just in case, and b) flash the recovery manager of your choice.
With the recovery manager in place, you'd be able to flash whatever rom you like.
Please note that I have no means to test this procedure on my own!
You should take your risks if you dare!
Now I don't understand how I "use dd from the command prompt to a) backup your current HBOOT, just in case, and b) flash the recovery manager of your choice."
So what do all of you think about this approach? Do you see it as safe? If not, what could possibly be a safer method? Any other suggestions/comments?
Also, could anyone kindly direct me to some info about how exactly do I flash a recovery in this setup?
Thanxalot!

since you are already s-off i think you should be able to install a custom recovery on your device(im not sure about this you may want to wait for someone else to confirm this just to be safe)
once you have a custom recovery you can install a custom ROM or a prerooted stock ROM to gain ROOT access
try this recovery
this is the link to the DS index thread for easy access to more useful threads

If you are s-off, you have fastboot so you can flash a recovery with adb. And flash a new rom
Sent from my HTC Desire S using XDA Premium App

kartkk said:
since you are already s-off i think you should be able to install a custom recovery on your device(im not sure about this you may want to wait for someone else to confirm this just to be safe)
once you have a custom recovery you can install a custom ROM or a prerooted stock ROM to gain ROOT access
try this recovery
this is the link to the DS index thread for easy access to more useful threads
Click to expand...
Click to collapse
Yea, I've been thinking in the same direction.
So there are two possibilities I can think of right now, as to how to install 4EXT recovery.
1) Download "4EXT Recovery UPDATER" to my phone -> then -> Enter temporary root state using adb -> then -> download & flash 4EXT recovery automatically using "4EXT updater"
or
2) Download "4EXTRecovery_v2.1.0_saga.zip" to computer -> then -> enter temporary root state using adb -> then -> flash "4EXTRecovery_v2.1.0_saga.zip" from computer using fastboot.
Agreed? Which one seems more reasonable to you guys?

Could someone experienced please confirm that I'm getting this right?
Flashing 4EXT recovery via fastboot:
1) download <4EXTRecovery_v2.1.0_saga.zip>
2) extract the <recovery.img> file from that zip archive
3) run these commands: fastboot flash recovery recovery.img
Correct? Do I need to wipe something first or can I just flash right away?
Secondly, Silver was talking about first backing up my current Hboot using adb, before I attempt to flash the 4EXT recovery. Does anyone please know how to do this? Can't find it anywhere explained.
Thanks

You'll first need to download and extract the adb & fastboot links from my signature and esnure that you have the HTC Drivers installed on your PC (also in my links in my signature).
Then follow the instructions within the Flash CWM & su via fastboot link that's in my signature.
That will put CWM (clock work mod a custom recovery and make you root by installing the su (super user) )
I'd say follow this and then once you've CWM and are root simply install the 4EXT from the market and update recovery to 4EXT (again link in my sig).
Any question then fire away?

ben_pyett said:
You'll first need to download and extract the adb & fastboot links from my signature and esnure that you have the HTC Drivers installed on your PC (also in my links in my signature).
Then follow the instructions within the Flash CWM & su via fastboot link that's in my signature.
That will put CWM (clock work mod a custom recovery and make you root by installing the su (super user) )
I'd say follow this and then once you've CWM and are root simply install the 4EXT from the market and update recovery to 4EXT (again link in my sig).
Any question then fire away?
Click to expand...
Click to collapse
Ok, got you ben_pyett. Thanks for clear instructions.
So no way (or need) to backup hboot prior to flashing recovery?
And no need to enter temporary root state before flashing WCM?
Gonna give it a try.

mimirom said:
Ok, got you ben_pyett. Thanks for clear instructions.
So no way (or need) to backup hboot prior to flashing recovery?
And no need to enter temporary root state before flashing WCM?
.
Click to expand...
Click to collapse
You can always get the original HBOOT (recovery) back from a stock ROM RUU if and when you need, see link to STOCK ROMS in the thread DEV INDEX
you may be able to do it via temp root fr3vo and adb but I'm not 100% . Temp root - If you're S-OFF I don't think you need to, but be sure to flash correct verison of CWM (saga) or else there is trouble.

I downloaded the newest CWM (recovery-clockwork-5.0.2.0-saga.img) for saga from the Clockworkmod website.
Attempted to flesh it simply using fastboot. This is what I got.
{
"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"
}
So perhaps the next step could be 1) get into temporary root state 2) flash
Comments?
edit: Ok, I see now the difference - to do it via temproot + adb I need to work with android up and running.

mimirom said:
I downloaded the newest CWM (recovery-clockwork-5.0.2.0-saga.img) for saga from the Clockworkmod website.
Attempted to flesh it simply using fastboot. This is what I got.
So perhaps the next step could be 1) get into temporary root state 2) flash
Comments?
edit: Ok, I see now the difference - to do it via temproot + adb I need to work with android up and running.
Click to expand...
Click to collapse
was your device in HBOOT, FASTBOOT USB ?
How to start Fastboot USB mode:
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Wait for sdcard scan to complete.
Plug in USB cord connected to the computer
Press power ONCE and Fastboot USB mode starts

ben_pyett said:
was your device in HBOOT, FASTBOOT USB
Click to expand...
Click to collapse
Yes, it was. That's why I get the device listed when I do the <fastboot devices> command
I tried the same procedure also in hboot mode, but there I get a <waiting for device>
When the phone is in fastboot I get <FAILED (remote: not allowed)> now.
Thanks for your assistance ben_pyett. Appreciate it.
edit: So something changed, since I'm not getting the <FAILED (command write failed (Unknown error))> anymore, but now it's <FAILED (remote: not allowed)>

Ensure that you device has device has "Debug USB" enabled
Boot and then Settings->Applications->Development->USB Debugging = YES (tick)
and then try again

Unfortunately that's not the problem. The phone has been in debugging mode from the beginning. It also shows the <usb debugging connected> in status bar when I connect it.
I found an older thread where people seem to have been successful rooting s-off devices with superoneclick. Will read through it.

Thinking back to what I did after I'd Made my s devices s-off although I used xtc
Although first question, have you tried running ginger break? You'll find a link to it from within the root section of the http://forum.xda-developers.com/showthread.php?t=1146601DEV INDEX a sticky in that forum on the root sub section
Anyway what I did myself I've I was s-off was to Install a boot image that then enabled me to simply run one click, which gave me root.
http://forum.xda-developers.com/showthread.php?t=1105763 Link to boot image post
You find link the link to ginger break and super one click used with in the Dev INDEX within the root sub section
So try ginger break first and if that doesn't work, then boot image and super one click which is literally that easy
Once you're root simply download ROM manager from Android market and use that to install Cwm as it's only one click
Good luck
Swyped from my Desire S using XDA Premium

Great help, thanks!
I tried Gingerbrake a few weeks ago without success. A far as I know it doesn't work with HBOOT-0.98.0002. Some folks propose downgrading the hboot but I noticed that it's supposed to be dangerous. However I'll give it another try.
The one click method you propose looks good, thanks. I remember though that I tried to flash something using a "PG88IMG.zip" during my few initial attempts to get root, and my phone refused to read it from the sd card.
Would love to try it right away, have to leave though...
Cheers.

Hi ben_pyett,
it clicked! (pun fully intended)
I first flashed the boot image and then ran SuperOneClick.
I have SuperUser installed. RootChecker confirmed full root access. Right now Im doing a Nandroid backup from CWM recovery.
Loved to see that recovery screen again (I'm coming from Wildfire)
So thank you ben_pyett for your patience and willingness to offer not-just-sporadic support.
_______________________________________​
There were slight complications occurring during the root process. Superoneclick hanged at step 6. After disabling USB debugging it showed a few more lines in the right window section and after enabling USB debugging again it finished the root procedure without further problems.
It seems to me that the phone now takes longer to shut down plus, more importantly, Wifi stopped working. It gives an error message on the Wifi tab in settings.
Actually the phone appears generally unstable now. It just gave me a <Tell HTC> notification with something like "the phone just recovered from an abnormal reboot."
Hope I can sort this out by flashing a new rom...
So far, so good. Go to bed now.

mimirom said:
Hi ben_pyett,
it clicked! (pun fully intended)
I first flashed the boot image and then run SuperOneClick.
I have SuperUser installed. RootChecker confirmed full root access. Right now Im doing a Nandroid backup from CWM recovery.
Loved to see that recovery screen again (I'm coming from Wildfire)
So thank you ben_pyett for your patience and willingness to offer not-just-sporadic support.
_______________________________________​
There were slight complications occurring during the root process. Superoneclick hanged at step 6. After disabling USB debugging it showed a few more lines in the right window section and after enabling USB debugging again it finished the root procedure without further problems.
It seems to me that the phone now takes longer to shut down plus, more importantly, Wifi stopped working. It gives an error message on the Wifi tab in settings.
Actually the phone appears generally unstable now. It just gave me a notification with something like "the phone just recovered from an abnormal reboot."
Hope I can sort this out by flashing a new rom...
So far, so good. Go to bed now.
Click to expand...
Click to collapse
Now you have root you can get custom recovery and from there you can Custom ROMS, there are loads to choose from.
All the problems you report are fixable.....wifi fails as boot image is missing Wifi do modules, but a custom well resolve that, glad you got there in the end.
Ensure that you have Settings->Power->Fastboot set to OFF (un-ticked)
night

Can't root your desire s ? Me too...

smartceleron said:
Can't root your desire s ? Me too...
Click to expand...
Click to collapse
Well, no, I actually rooted it the way described in this thread... The thread is also labeled as "solved" now.
Did u try to follow the steps described? What are your specs?
Sent from my HTC Desire S using XDA App

[Guide / Tool][10/15/12] - Update to Official Jellybean Then Root or Custom ROM!

I wrote this guide do to the general lack of information for users about the Jellybean update. This guide is basic in nature and will provide you with all the tools and links you need to update from an ICS based ROM to the official JB ROM then re-root or prepare for custom ROM.
If you already have the Official JB Update simply unlock it and proceed to Section #2. This guide was intially intended for those who cannot update because of Asus stupid lock out program once you unlock.
Warning
I have tested this guide on my device multiple times and never have one single issue. I cannot say it will work perfect for you! I am not responsible for anything that goes wrong including but not limited to; A $500 brick! The economy imploding worse, Nuclear war, End of the world on 12/12/12!
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
Windows 7 or Windows 8 PC
General Overview
Flash Asus JB update
Flash TWRP 2.2.3
Flash SuperSU or Custom ROM
Profit!
Please do not be afraid to ask for help!
This guide was written for people who need help. I didint write it for myself because I already know how to do it, lol
Donations gratefully accepted but never expected!
Please hit Thanks and Rate the thread 5 Stars
Click to expand...
Click to collapse
-Scott

Section 1 - Flash Asus JB update
Obtain the appropriate Jellybean update from the Asus Support Site HERE
Go to Downloads and pick the local / region specific update file for your device. For the intent of this guide I will focus on the US Based variant but all other devices will follow the exact same steps.
{
"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"
}
After you download the Jellybean update you must extract the zip file in the zip (I dont know why they did this!). The name of the first zip file will be "US_epad_user_10_4_4_16_UpdateLauncher.zip"
The zip file inside of that will be "US_epad-user-10.4.4.16.zip" This is the file we will flash to update to JB!
To do this open the first zip file with your zip [rogram of choice, (as you can see I use 7zip) and pull out the only other zip file in there (US_epad-user-10.4.4.16.zip).
Once you have that file copy it to you internal SD card. Although, untested, external SD should work too.
Now.... Reboot to recovery. To do this power down the device, and then Hold Volume Down and then press power untill you get a menu that says press XX key to boot to recvoery.
Once in recovery you MUST wipe data before you continue!
Now flash the ROM file you just copied like it was a plain old fashioned custom ROM or Root.zip. Just select it and flash!
Once the flash is done reboot. Dont be scared... This will take a LONG time... Maybe in upwards of 3 to 5 minutes. This is normal. Its completely rebuilding the device!
Once the device is all booted up and you are at your desktop we can proceed to Section 2.

Section 2 - Flash TWRP 2.2.2.3
First we need to obtain TWRPREcovery. You are free to use any version you want, including ClockworkMod (although I highly discourage CWM and recomend TWRP).
You can find TWRP HERE. Remember I recommend the 2.2.2.3 version. 2.3.0.0 gave me some issues.
Now that you have the file download you need to rename it to "recovery.blob" for use with my tool!
Now download the attached tool and unzip it. It contains the fastboot and ADB files you will need to flash the recovery.
Next place the recovery.blob in the folder
Turn on USB Degging in the developer menu of the device. This is very important otherwise you will be just sitting there forever, lol
Now initiate the "Recovery Install Tool.bat" file. This will reboot you to bootloader and flash the recovery for you ;c)
Done!

Section 3 - Flash SuperSU or Custom ROM
Needless to say I am partial to custom ROMS ;c) But I know some may be content with just flashing root so I will show you how to obtain the correct root file and or ROM and give a brief over view on how to flash them. This section will be pretty routine and will not contain a lot of new info for most of you!
Obtain my favorite root app, SuperSU, from HERE
Copy to storage
Reboot to recovery
Flash and Be rooted!
Same steps for a custom ROM. The best Custom ROM can be found HERE! ;c)

Section 4 - Thanks!
Thanks to Dess_troy for making TWRP for our devices!
Thanks to Chainfire for the root app!
Thanks to all the Developers on XDA that have taught me (in one way or another) everything I know!
Special Thanks to all the CleanROM users who have inspired me to push CleanROM to be the premier custom ROM for your Android Device!

Please feel free to rebuild this for the Linux or Mac platform and re-distrubute!

So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app

scrosler said:
Pre-requisites
Unlocked bootloader
Custom Recovery
Any version of TF700T
-Scott
Click to expand...
Click to collapse
A number of people have asked and I have usually replied that it is possible to use the Asus provided UnLock tool - the one on the website that says is only compatible with ICS - with a tablet that has been updated to JB.
In short the Unlock tool works in Jellybean!
You might want to add this as an addendum to your original post.
Cheers,
Eric

i apologize for my beligerant question but if i want to try the new cwm touch recovery, do i just rename it to recovery.blob? when i downloaded it it was the usual iso. when renamed it didnt change anything so i dont wanna brick my tab. figured id ask first. thanks for the awesome walk through tho man. i really apreciate it. loving your roms. have 2.0 downloaded already. also can you pm the link to your tf300 kernel you used? i need to show off some high quadrant numbers lol

Confused...
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?

BlastTyrantKM said:
So, the very first step is unlocking the bootloader, correct?
Sent from my S2 Skyrocket using XDA app
Click to expand...
Click to collapse
BlastTyrantKM said:
How do I get a custom recovery on my tablet before this whole process? I've read thru some threads, do I need to be rooted first on ICS before starting this process of updating to JB? I'm not getting the official ASUS JB OTA...I've checked for the update about 500 times, I'm just not getting it.
At this point, I have an unlocked but unrooted, and wiped stock TF700T on ICS. Whats my next step?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
This guide is for people who have already unlocked there device any may have had a custom ROM installed pre-JB.
You fall into a unique and rather off situation. I have never heard of some one not getting the OTA.
You could follow these steps but as a pre-step...
Download and unlock with the Asus unlock tool. Its on the same download page.
Download an ICS based recovery and use that in in place of the one noted for now. And then just start at Section 2. Then start back over at Section 1.
Basically we will put a recovery on your device in Section 2. Then start over at step 1 by applying the JB build then put a recovery back on, as it gets wiped off by Asus builds and your all set.

So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
The stock recovery will only flash firmware zips with a certain name. Rename the zip to EP201_768_SDUPDATE.ZIP and try again.

I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.

yes you lose root. this will make your tf700 like the factory jellybean firmware which is not rooted. go back to op and keep reading. each section builds on the previous. first get the jellybean firmware. im still playing with mine stock its so damn smooth. then you flash a custom recovery using his tool. then you flash the zip which gives you root. then i would make a back up so you can always get back to that point. then you can look into custom roms like scotts sweet clean rom for tf700 series
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse

beowolfschaefer said:
So I got the OTA JB update from Asus. I unlocked the boot loader using the Asus app. I downloaded and extracted US_epad-user-10.4.4.16.zip then threw it on the insternal SD card ( /storage/sdcard0 ). I rebooted with the volume key press and selected recovery. It gave me a message saying "booting recovery kernel". The next thing I see is an android on his back with a red exclamation sign.
What am I doing wrong?
Click to expand...
Click to collapse
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
joseph473 said:
I upgraded to jb firmware and lost root. My 700T is unlocked. I thought I followed the procedure correctly but I did not get the message correct message when I ran the program. My device is not rooted. Can you tell me what I might be doing wrong.
Click to expand...
Click to collapse
To me it looks like you are trying to run the batch file without extracting the contents.

Thank you for this guide! Although it took me some time to understand it as I was on non-rooted/locked JB stock rom.
---------- Post added at 01:34 PM ---------- Previous post was at 01:29 PM ----------
scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually had similar problem as this guy. I was already on JB and the guide is made for people that are on ICS.

scrosler said:
To me it looks like you are trying to run the batch file without extracting the contents.
Click to expand...
Click to collapse
I am using a borrowed PC. I am a Mac user so forgive my ignorance. But when I look at the folder with Scott's Tool in it it looks like everything is extracted.

scrosler said:
If you have the JB Update why ware you trying to install it again? Proceed to section #2. You just need the Recovery and the Root portion. Skip step 1.
Click to expand...
Click to collapse
I actually tried this last night with no luck. I guess it was something funny with my desktop in that it couldn't connect using fast boot. Anyway I brought it in to work and ran it here and everything is fine. I am going to throw your stock/root rom on it now. Thanks for your help!

CWM-SuperSU-v0.96.zip
Hello,
thanks a lot for the guide, it is really clear and detailed.
My question is something I did not find on the previous question and it is more a double check to be sure I am not doing something I should not.
You say to install SU with the package copied on the internal SD, and you added a link to the SU thread. in this thread, the only SU as a package you can find is CWM-SuperSU-v0.96.zip, as it is CWM, will it work if I install it with TWRP? or there is special settings in this package that will not be recognised by TWRP?
Thanks in advance for your help
Regards

S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.

S4 T-Mobile + 4.3 = "there is no su binary installed and supersu can not install it.
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?

no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta

Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
beaver2233 said:
no, there's no working root at this time.
Sent from my GT-I9505 using Tapatalk 4 Beta
Click to expand...
Click to collapse

dotpage said:
Thank you for the info.
I have to say this, the speed improvement on 4.3 is very noticeable. I am back to CM10.1 and it feels slow in comparison...
Click to expand...
Click to collapse
How did you get back to CM10.1?

AlAmeri said:
How did you get back to CM10.1?
Click to expand...
Click to collapse
Flash it using a custom recovery
Me Gusta!

Me Gusta said:
Flash it using a custom recovery
Me Gusta!
Click to expand...
Click to collapse
So flashing ROM without root is possible?

AlAmeri said:
So flashing ROM without root is possible?
Click to expand...
Click to collapse
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.

fcknghst said:
Directly from Android, no. You'll need root to do that. Just power off your device, when its turned off press and hold volume up, home and power at the same time. Flash from recovery.
Click to expand...
Click to collapse
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.

AlAmeri said:
So Android 4.3 without root. I have a costume recovery, CWM, I could simply just flash a new ROM and it wouldn't brick my S4?
Sorry for the newbie questions but I'm coming from zero experience.
Click to expand...
Click to collapse
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )

fcknghst said:
Yup. Just do a wipe and flash whatever you like. As long as you have access to bootloader, and keep a backup it is very hard to brick your phone - Im new to samsung, but as i understand with Odin it is even harder to brick it.
On a side note, i had some issues getting it to mount /system - Turns out that it cant if the phone is plugged into the computer (i did a facepalm after trying ~3hours getting it to flash CM )
Click to expand...
Click to collapse
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.

AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse
So you cant restore your backup, from before 4.3?

fcknghst said:
So you cant restore your backup, from before 4.3?
Click to expand...
Click to collapse
Exactly. I tried searching for stock firmware, couldn't find one. So I thought either I find a way to restore. Or flash an already rooted ROM. You see my dilemma.

{
"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"
}
dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse

Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
AlAmeri said:
The thing is I backed up my old system before I flashed Android 4.3. Now CWM cant access the directory. I'm afraid if it can't access the directory then it wont be able to flash properly and I will for ever be stuck on bootloop.
Click to expand...
Click to collapse

dotpage said:
Use Odin to reload TWRP, it happened to me too... Put phone in Download mode, use PDA option pointing to TWRP's file...
Click to expand...
Click to collapse
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?

AlAmeri said:
But I don't have TWRP. I use a CWM based recovery.
How does it work?
So I flash TWRP using odin, and then what?
Click to expand...
Click to collapse
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.

fcknghst said:
In any case - Back up your current (working) installation - There will be a way to get root in the future. Now you dont have to worry about not being able to use the phone (since you have a working backup), and you can goahead and flash something else.
Dont bother installing different recoveries, they all work just fine - And TWRP wont be able to restore from a CWM backup anyways..
But I dont understand why CWM cannot access your former backup.
Click to expand...
Click to collapse
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.

If you find 4.2.2 vanilla(T-Mobile) let us know, I am looking for that ROM....
AlAmeri said:
That's actually genius. Don't know why I haven't thought of it earlier. Backup and experiment.
Thanks.
Chainfire is taking longer than usual. Its got me worried. I'm loving Stock Android, going to try flashing 4.2.2. Hopefully won't run into trouble.
Click to expand...
Click to collapse

dotpage said:
Did ODIN, then CFRoot (CF-Auto-Root-jfltetmo-jfltetmo-sghm919), SuperSu fails with "There is no SU binary installed and SuperSU cannot install it"...
Anyone had luck getting SuperSU wrking on 4.3?
Click to expand...
Click to collapse
dont know if this will work for you but here goes. i have a T999L (T-Mobile LTE S3) i have twrp installed on it and i have slimbean 4.3 official build installed on it, i had the same issue with getting 4.3 rooted but i got it figured out first make sure in the developer options you have superuser allowed by adb and apps.
( if you don't see developer options in your settings menu
go to :Settings>About Phone> click on your build number several times until you get a toast that says your almost a developer keep clicking until it says it has been enabled)
then you will use motoChopper to push the exploit to get the superuser.apk added to the system/apps folder once you do this it won't work as they have somehow allowed access for the expoit to push the .apk but not push the binary to the system/xbin folder.
now pull the SU binary out of the motoChopper folder on your computer and place in on your sdcard
boot into TWRP, mount the file system and copy it from your sdcard to the system/xbin folder and voila you are done, when you go to reboot your device from TWRP it will ask you if you want to fix the Superuser permissions just skip and reboot
( all rights thanks and so on go to the original developer djrbliss and i do not take any credit for his work, nor did i get permission to modify his work, i tried but got no response so i modded it for myself to use and i am now sharing, all i did was swap the Superuser.apk and SU binaries he used in his exploit.) @djrbliss if you would like this post removed just let me know and i will pull it!
not sure why the list showed up as 1 1 1 2 but i think you get the point

[OutDated!] Working Root Method For 5.0 Lollipop Roms [OE1] [OG5] [OK3] [PB1]

THIS IS AN OUT DATED METHOD. A MUCH EASIER METHOD CAN BE FOUND
EMMC 15
EMMC 11
Scroll Down To This Post#3 For Instructions​
This is the main thread for rooting (and installing safestrap) on VERIZON Galaxy S5's running
OE1
OK3
OG5
PB1
If your firmware is NOT listed above, you MUST FIRST Follow the section that says "Flashing PB1", This will upgrade/downgrade depending on if you are on any other versions of Android. Yes it will downgrade from marshmallow, so don't ask.
Important Information​
One of the apps in this thread "Supersu-me" Is required to complete this process, otherwise you will be stuck with the Kingroot Superuser Manager(which blocks alot of actions we need). You can buy the App here. Supersu-me Pro The new version MAY NOT WORK ANYMORE!!! If you have issues, please message the developer of the app @gatesjunior, we cannot help.
If anyone wants to make a donation make a donation to @GeTex
[email protected]
A Special Thanks To @GeTex For Mods to the root.bat and updating the old instructions
A Special Thanks Also To @be free for the new simple method
WARNINGS​This Is Very Important!!! Once Your Rooted Do Not Flash Any Firmware Zips Found In My Other Threads Unless They Specify NO_BOOTLOADERS In The File Name!
Reactivation lock MUST BE TURNED OFF!!!
Before Doing Anything Please Install The Latest Samsung Drivers SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe
YOU MUST DO THIS
General Information​This is confirmed working on BOK3 Rom with BOK3 Bootloaders, BOG5 with BOG5 Bootloaders, BPB1 with BPB1 Bootloaders and BOE1 with BOE1 Bootloaders!, that were previously unrootable! Just make sure in bottom directions you flash the kernel that matches your firmware!
These files were provided to me by @voices! the files are by CDMA YEMEN TEAM.
I provided the method and editing of files and last but not least @alnazef34 he was the first to tell me about this.
Also would like to thank @gatesjunior for making the Supersu Me app. Please goto his thread and thank him donate to him and go buy his Super-Sume Pro at the playstore and keep a copy for future.
A Special Thanks To @GeTex For Mods to the root.bat and updating the old instructions
A Special Thanks Also To @be free for the new simple method
Understanding the process​
So alot of confusion has surfaced from this thread and how it works and I'd like to explain most of whats going on hopefully without error. When verizon updated the bootloader they made it impossible to downgrade the system back to Kitkat so we could abuse towelroot. Later it was found that while we cannot flash our Systems back we could flash the kernel, allowing us to run the same basic exploit via an ADB terminal remotely and install a root exploit. The end result is that we can then flash our kernel back to Lollipop and then use the exploit to allow kingroot to install it's root method, and then shortly after, we are able to use supersu me to remove kingroot and install SuperSu. Your original kernel is important but for the most part you should all do this on PB1 anyways. NI2 or NK2 are both kitkat kernels and can be used(one is included in the zip)to accomplish this process. because you clearly are not on a Kitkat system it will FREEZE while booting because it's not supposed to boot a lollipop system. So In order for root.bat to work(or root2.bat) you MUST flash a kitkat kernel(NI2 or NK2) and once it succeeds you must flash your original kernel(probably PB1)
Installing PB1​
(You will lose all of your app data and apps installed, your internal storage will be fine, backup is recommended anyways
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
2. Reboot to recovery (Power+Volume Up+Home Button) and wipe data from recovery, reboot to bootloader
3. Plug In your phone and open Odin located in the OK3_ROOT folder
3a. Make sure your phone is recognized (In the Odin Screen Under ID:COM the box under will be blue with your com port id #)
4. Click the AP button in the Odin Screen and locate and click on the G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 this is the file that was unziped from the G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip(Everything you do will be flashed via AP!!!!)
4a. This will take a few minutes for odin to load and verify MD5. When done in the odin message box it will say
Code:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS.
5. Under options DO NOT CHANGE ANYTHING (Previously I had you check NandErase but this was part of the problem with root not finishing)
6. Now click on Start
7. When finished you will get a green box that says PASS!
8. Phone will reboot automatically to recovery and finish updating then it will restart
9. When Phone has finished loading and has booted up go through setup and do not add any google accounts or samsung accounts or anything
Rooting Instructions​Please read EVERYTHING ABOVE BEFORE CONTINUING
This is the BlackCat Update, Hopefully it's better
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
2. Unzip folder.(You need a unzip application like 7z or Winrar)
3. Open The Folder and click Bat file #1, Install APKs, plug in your phone and follow directions
All the Steps for the main rooting process are done ON THE BAT FILES, READ THEM!!!!
If the root process hangs Close the bat, unplug phone pull battery and reboot phone to recovery (VolUp+Pwr+Home). In recovery wipe cache only and reboot. If phone reboots back to recovery instead, pull battery and manually reboot. Now plug phone back in and Launch Bat #3.
IF you get into android and cannot get root, Open bat file #2 and start from there again
If your phone wont reboot, use Bat #4 and try and enter download mode manually(VolDown+Pwr+Home)
4. Open KingRoot.apk Click The Up Arrows a couple of time until you get to Try It and click Try It and that's it don click nothing else just close Kingroot. You should now have root. If It says Root not available and the bat said your were rooted Reboot Phone and open KingRoot You should now be rooted(otherwise reboot phone and check again)
5. Optional: If you Dont want to use SuperSu Me Skip To 6 and try but if it doesnt work then you will have to use SuperSume . Now open SuperSU-Me app (This app is now a paid app so setup Google Play and buy and it will remove kinguser and replace it with SuperSu. If you can't get the Paid version to work. The SuperSu Me 6.7 version worked. So you may have to hunt that one down by asking the Dev of the app) After this process SuperSu will ask to update binary click update normal
6. Copy this G900V_Fix Safestrap.zip (It may come in handy later on) to your SD Card and Internal Storage Copy Safestrap_Flashable_Kernels and Safestrap_Flashable_Firmware and anything else you want to install like the below rom
7. Now open Busybox Installer Allow KingRoot permission click on install
8. Click on Safstrap Allow KingRoot permission then click Install Safestrap after it installs reopen Safestrap and click on install again
9. Reboot phone open Safestrap app and Click Reboot To Recovery. If during this process you every get stuck on samsung screen.
Pull battery reboot phone to bootloader (VolDwn+Pwr+Home) Plug phone into computer open Odin In the AP Slot Flash VZW_BPB1_KERNEL_ONLY.tar.md5 Located in the LOLLIROOT Folder
10. Install This zip Knox_Removal_SU_BB_INIT.D.zip If you dont want a custom rom your done!
11. If you want to flash a custom rom make a backup In safestrap. Then in safestrap Click Wipe then Click Advanced Wipe Then Wipe System,Wipe Data,Wipe Cache Then Install any rom of your choosing as long as it is a Verizon S5 TocuchWiz Based Rom CM builds will not work! If you want you can try this it is stable. If for some reason you get an error flashing zips install this zip G900V_Fix Safestrap.zip in safestrap then you will be able to install roms. That zip wipes system and formats it so you will need to install a rom or backup before leaving safestrap
VZW_BPB1_ODEX_DEODEX_V8.zip This is a fully stock rom just like you had except it is Pre Rooted Knox free Deodexed with Tethering Fix, SDWrite Fix. Other than that all the bloat is still there but now your rooted you can remove it or flash different rom whatever
12. After flashing any rom I would head over to my Safestrap Thread and flash the latest version of Safestrap
Extra Information​Extra Information
If you soft brick your device and you made a backup in safe strap, flashing the NK2 kernel will get you back into safestrap, allowing you to restore your backup
THIS DOES NOT UNLOCK YOUR BOOT LOADER!!! To Unlock the bootloader look at the Sticky in the Development Forum. You cannot flash anything through the stock recovery. Do not try to, you will softbrick!
If you try and flash a rom or anything else, make a backup first, it saves many headaches.
If you cannot flash roms with the error "set_metadata_recursive failed" or something, you likely need to start from scratch BUT with the S5 PIT file(matching your size, there's a 16GB pitfile floating somewhere)
Realize your phone warranty is likely gone after doing this, should anything arise, you can try and get to download mode and flash the stock image again and it may go back to normal status but we cannot encourage fraudulent warranties, no matter how pathetic Samsung's policies are.

If something goes wrong! Here is the Factory Tar BPB1 Full Restore Image.
G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip
Here are the new safestrap flashable firmware zips with no bootloaders these are safe to flash on all versions of bootloaders
BOC4_Firmware_No_Bootloaders.zip
BOD5_Firmware_No_Bootloaders.zip
BOE1_Firmware_No_Bootloaders.zip
BOG5_Firmware_No_Bootloaders.zip
BOK3_Firmware_No_Bootloaders.zip
BPB1_Firmware_No_Bootloaders.zip
Here are the new safestrap flashable kernel zips these are safe to flash on all versions of bootloaders
G900V_OC4_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OD5_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OE1_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OG5_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_OK3_Stock_KERNEL_SafeStrap-Flashable.zip
G900V_PB1_Stock_KERNEL_SafeStrap-Flashable.zip

Wow ...

Chopstix9 said:
Wow ...
Click to expand...
Click to collapse
Edit: Its confirmed Working!!
Need some testers to confirm!

jrkruse said:
Need some testers to confirm!
Click to expand...
Click to collapse
No disrespect intended but I am not going to flash up to stock locked from where I am to test it !! Come on people !!! If you have a locked phone and want root, here's your chance to contribute to a potential major break through on our phones ...

Chopstix9 said:
No disrespect intended but I am not going to flash up to stock locked from where I am to test it !! Come on people !!! If you have a locked phone and want root, here's your chance to contribute to a potential major break through on our phones ...
Click to expand...
Click to collapse
Edit: Confirmed Working!!
Notice I didn't either, but it should work since all you have to do is flash the NI2 kernel which you can still do on the oe1.og5 and ok3 firmwares. They just wouldn't let you flash the ncg system.img

Edit: Confirmed Working!!

Yes it works. However my unknown mistake after achieving root with my bok phone was that I immediately installed titanium backup and a message came up saying something about an unauthorized action. My phone rebooted and now says start up failed . Use the verizon softwair repair assistant on a computer to repair your device. Of course this is impossible. I suppose if I had installed busybox and safestap first and placed a rom on the phone I would have been ok. Fortunately the phone was a spare but I'm still not happy.

rnh said:
Yes it works. However my unknown mistake after achieving root with bok was that I immediately installed titanium backup and a message came up saying something about an unauthorized action. My phone rebooted and now says start up failed . Use the verizon softwair repair assistant on a computer to repair your device. Of course this is impossible. I suppose if I had installed busybox and safestap first and placed a rom on the phone I would have been ok. Fortunately the phone was a spare but I'm still not happy.
Click to expand...
Click to collapse
Flash the BOK3 kernel it should boot
If it doesnt, Here is the Odin Factory tar image just flash in odin G900VVRU2BOK3_G900VVZW2BOK3_VZW.zip. This does not have the BOD5 bootloaders so it will flash fine for you

Thank you JK. How you stay up with all of these threads impresses me. Flashing the bok3 kernel worked. Now to continue I should install the bb and ss because apparently using the phone just rooted with rooted apps won't work?
Also, in the process of rooting as advice to anyone who wants to do it; when using the bat program, I found if it doesn't work right away close it then reopen it and it starts right away.
With titanium backup still installed the unauthorized app messge remained so I uninstalled tb and rebooted the phone with no problem

rnh said:
Thank you JK. How you stay up with all of these threads impresses me. Flashing the bok3 kernel worked. Now to continue I should install the bb and ss because apparently using the phone just rooted with rooted apps won't work?
Also, in the process of rooting as advice to anyone who wants to do it; when using the bat program, I found if it doesn't work right away close it then reopen it and it starts right away.
With titanium backup still installed the unauthorized app messge remained so I uninstalled tb and rebooted the phone with no problem
Click to expand...
Click to collapse
I added the apk above that will work with lollipop

So it seems this works!. The only thing you will want to do is make sure the kernel you flash after you root matches your firmware so you dont get the unauthorized actions message!. And I would get a custom rom flash asap because the stock verizon rom still has knox. I posted in the OP the files you should need to get busybox and lollipop safestrap installed
Edit Root_OG5_V2.zip contained a folder called SafeStrap Flashable Firmwares please dont use these as they contain older bootloaders and may brick your phone. So if you downloaded Root_OG5_V2.zip before i pulled it please dont use those zips
Edit Root_OG5_V3.zip Contains all the files you will need

Tried it, and got stuck after the NI2 kernel update. The batch file would never recognize the device again... ended up having to wipe and recover... more than happy to try again though
***my bad, tried the old method... didn't realize it was updated.
---------- Post added at 07:20 AM ---------- Previous post was at 06:29 AM ----------
confirmed working! You guys rock!

We have a winner! I followed the steps exactly and poof ROOT!
{
"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"
}
Thanks millions

Mine does not reboot after the .bat file fails the first time. I continue on, and when I get to the samsung screen, and I run the .bat once more it gets stuck at 'installing root now' and does not proceed. Help would be appreciated!

Awesome job @jrkruse.
I don't personally need this because I never updated my bootloader but for all of the people out there who updated via OTA or bought a phone that was already updated, you are a life saver.
As always, great work.
---------- Post added at 07:43 AM ---------- Previous post was at 07:27 AM ----------
Actually, I'm quite curious if I may just want to do a full stock Odin flash of OK3 (bootloader and all) since I never plan on going back to kitkat and I can just gain root and deodex the ROM myself for Xposed afterwards.
I've noticed that using the old bootloader with new updates causes my phone's screen to do weird things when I try to charge it while it's off. Using the correct bootloader may fix that.

so once more, I have installed every package for the SDK. Modded my paths correctly so that adb is usable.
flashed phone back to the OK3 .tar provided.
I run the .bat, it sees the phone and attempts to install root.
I now get 1 of two results.
first, it will hang at 'installing root now' and never proceed, or it will error out "error; device not found" and fail. Neither of these options promp a reboot.
as I mentioned earlier, if I proceed to install the kernal provided, the screen gets stuck at samsung, and the .bat once again hangs at 'installing root now'

Aireos said:
so once more, I have installed every package for the SDK. Modded my paths correctly so that adb is usable.
flashed phone back to the OK3 .tar provided.
I run the .bat, it sees the phone and attempts to install root.
I now get 1 of two results.
first, it will hang at 'installing root now' and never proceed, or it will error out "error; device not found" and fail. Neither of these options promp a reboot.
as I mentioned earlier, if I proceed to install the kernal provided, the screen gets stuck at samsung, and the .bat once again hangs at 'installing root now'
Click to expand...
Click to collapse
Maybe try using a different port on your computer. Did you goto developer options and enable usb debugging? After that did you accept the Allow USB debugging dialog
View attachment 3606452

jrkruse said:
Maybe try using a different port on your computer. Did you goto developer options and enable usb debugging? After that did you accept the Allow USB debugging dialog
View attachment 3606452
Click to expand...
Click to collapse
I have enabled debugging, and have tried different ports. Must've gone over every detail about 6 times total. For now, I just flashed back to factory. Will try again in a few hours if I get some decent replies..

Juust brought my spare to work. Seeems I was on boe1. Is there a kernel for that? I don't think it will do a software update to bok while rooted.

[TOOL][DAISY] TOOL ALL IN ONE (Drivers|Unlock|TWRP|Factory Image|Stock Recovery)

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?