Related
Alright, so I finally found a Razr M that has the bootloader unlocked and went to root it and it wouldn't root. I booted into recovery and it has TWRP installed on it so I tried to install CleanRom and it failed and said something about it tried to patch something but I can get a picture if need be.
I'm kind of at a loss on what I need to do, bootloader is definitely unlocked since it has the splash screen and it says unlocked on the black screen (sorry don't know what it's called). It's on baseband .81P so if there is anything anyone could tell me I would greatly appreciate it.
collins521 said:
Alright, so I finally found a Razr M that has the bootloader unlocked and went to root it and it wouldn't root. I booted into recovery and it has TWRP installed on it so I tried to install CleanRom and it failed and said something about it tried to patch something but I can get a picture if need be.
I'm kind of at a loss on what I need to do, bootloader is definitely unlocked since it has the splash screen and it says unlocked on the black screen (sorry don't know what it's called). It's on baseband .81P so if there is anything anyone could tell me I would greatly appreciate it.
Click to expand...
Click to collapse
Which tool did you use to root? The first time I tried to root right after getting the phone, I had to wipe cache/dalvik and FDR. Also, since your BL is unlocked, you should just be able to flash a SU binary in TWRP and get root. I know there's one running around here somewhere.
RikRong said:
Which tool did you use to root? The first time I tried to root right after getting the phone, I had to wipe cache/dalvik and FDR. Also, since your BL is unlocked, you should just be able to flash a SU binary in TWRP and get root. I know there's one running around here somewhere.
Click to expand...
Click to collapse
I tried the Batman utility and also motofail2go
collins521 said:
I tried the Batman utility and also motofail2go
Click to expand...
Click to collapse
Motofail was for 4.1.1 and Motochopper was for 4.1.2 (this was included in the utility 1.20). Sometimes these things have to be run multiple times, at least that's what I've seen.
Here's Chopper by itself: http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/ . However, you might have to wipe to get this to work, I did anyway. Before it comes to that, I would try to flash SU in recovery.
Thanks, flashed the SU Binary's and I'm up and running..now I have root and all is well in the world haha
Awesome! Been trying to solve that world peace issue like forever, man! Good deal!
Sent from my XT907 using Tapatalk 4 Beta
Lol now to get a 4.2.2 rom (Well maybe it isn't .2 I can't remember) to actually boot on here...can't seem to get it past the boot animation and I've flashed SlimBean, Chameleon, and another
I recently updated to the developers preview of Fire OS 5.0 and I had TWRP installed and I was not able to downgrade using the ADB sideload method. So for people that have the same issue here is what you need to do to resolve this and get back to Fire OS 4.0
Summary:
Rolling back to Fire OS 4 is easy! Simply visit the page below and follow the instructions provided to complete the rollback form.
http://www.amazon.com/gp/html-forms-controller/wdp_gen_rb
Note: The rollback process requires you to provide both your email used to participate in the Developer Preview, as well as your device's DSN. Instructions on obtaining your DSN are included in the link provided.
What version of OS 4 does this roll you back to?
junglistknot said:
I recently updated to the developers preview of Fire OS 5.0 and I had TWRP installed and I was not able to downgrade using the ADB sideload method. So for people that have the same issue here is what you need to do to resolve this and get back to Fire OS 4.0
Summary:
Rolling back to Fire OS 4 is easy! Simply visit the page below and follow the instructions provided to complete the rollback form.
http://www.amazon.com/gp/html-forms-controller/wdp_gen_rb
Note: The rollback process requires you to provide both your email used to participate in the Developer Preview, as well as your device's DSN. Instructions on obtaining your DSN are included in the link provided.
Click to expand...
Click to collapse
You had TWRP with OS 5.0. So you had root and OS 5.0? how?
siegesoldier said:
You had TWRP with OS 5.0. So you had root and OS 5.0? how?
Click to expand...
Click to collapse
No I had root on 4.5.4 with twrp and I did not have my nav bar so I decided to try to upgrade to 5.2.0 thinking I would be able to downgrade. I was stuck at this OS because I can't get into the stock recovery or twrp. So basically I need to go back to 4.5.3 to gain root and upgrade back to 4.5.4.
DoLooper said:
What version of OS 4 does this roll you back to?
Click to expand...
Click to collapse
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
Lol, so just to be clear, this isn't something you've even actually done yet. Nice. So what, you're just working on theory and leading people to do it with you blindly? Awesome. Post back when you have something with substance for us.
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
I'm guessing it will be 4.5.4, but if it's lower that would make getting 4.5.3 (and root!) much easier. Hope you can keep an eye on it and block OTA as soon as it comes through. thx.
This is directly from Amazon and the zip is signed. There is no reason it shouldn't work. I am just trying to let anyone in the same boat as me this may help them. No need to be rude.
I apologize if that sounded rude. Wasn't my intent at all. I assumed downgrade would be OTA, and it would help everyone if we can get the developer preview and then downgrade in the way you suggest to 4.5.3 or less.
No not you I was referring to the post above yours
junglistknot said:
Not sure yet because it takes like 48 hours to get the update sent to the device. As soon as I know I will let you know.
Click to expand...
Click to collapse
Have you gotten the rollback yet? If so has it fixed your ability to get to the recovery?
I finally received the update but I can install it because it still needs to boot to the recovery. Sorry for the misleading post. Just so everyone knows it also was 4.5.4 OTA. So I still need to flash the recovery.img through fastboot so if anyone has this img please share.
junglistknot said:
I finally received the update but I can install it because it still needs to boot to the recovery. Sorry for the misleading post. Just so everyone knows it also was 4.5.4 OTA. So I still need to flash the recovery.img through fastboot so if anyone has this img please share.
Click to expand...
Click to collapse
I have 4.5.3 recovery img somewhere, but I am not sure it'd help you since I doubt you could flash anything through the fastboot. I'll dig it up, and upload.
bibikalka said:
I have 4.5.3 recovery img somewhere, but I am not sure it'd help you since I doubt you could flash anything through the fastboot. I'll dig it up, and upload.
Click to expand...
Click to collapse
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
junglistknot said:
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
Click to expand...
Click to collapse
In the same boat anxiously awaiting for someone to find a stock recovery.img
junglistknot said:
Yes I can flash in fastboot but it needs to be an img file. I have done it before. If you could please upload it I will give it a shot. Thanks
Click to expand...
Click to collapse
wyldeice said:
In the same boat anxiously awaiting for someone to find a stock recovery.img
Click to expand...
Click to collapse
Well, this is 4.5.3. I dd'ed from my recovery when doing backups. See if it works!
so after messing with this so much bootloader is locked again and I am not able to flash recovery via fastboot. Looks like I will need to wait until someone can root 5.2.0 OS. Unless anyone else has any ideas because I feel like I have tried everything.
junglistknot said:
so after messing with this so much bootloader is locked again and I am not able to flash recovery via fastboot. Looks like I will need to wait until someone can root 5.2.0 OS. Unless anyone else has any ideas because I feel like I have tried everything.
Click to expand...
Click to collapse
5.2.0 can be rooted, but you'll have to start with a working TWRP, which means you already must have root. For independent 5.2.0 root, you may wait for a long time.
With fried recovery and no root, I don't think you are going anywhere, other than to Amazon customer service
bibikalka said:
5.2.0 can be rooted, but you'll have to start with a working TWRP, which means you already must have root. For independent 5.2.0 root, you may wait for a long time.
With fried recovery and no root, I don't think you are going anywhere, other than to Amazon customer service
Click to expand...
Click to collapse
Well I had TWRP and root beforehand. In fact SuperSU is still in the app drawer but it says the binary isn't installed. I can wait though I know I can bring this thing back to life at some point. I have a galaxy s5 rooted with CM12 on it so that will keep me busy while I wait.
Edit: Amazon is sending me a new Fire HD 7. Be here on Friday
junglistknot said:
Well I had TWRP and root beforehand. In fact SuperSU is still in the app drawer but it says the binary isn't installed. I can wait though I know I can bring this thing back to life at some point. I have a galaxy s5 rooted with CM12 on it so that will keep me busy while I wait.
Edit: Amazon is sending me a new Fire HD 7. Be here on Friday
Click to expand...
Click to collapse
Just curious what you told them? I am in the exact same place as you, but it was with my wife's brand new tablet from prime day.
Received this yesterday evening and am wondering if anyone has a good idea of what this update entails. It states is security patch and stability fix, if I'm not mistaken. Probably just a regular non-major update, then?
I am in the middle of returning my tab back to stock to then update to this update... Will report back in a while. @all
If you have unlocked your bootloader to use a custom recovery DO NOT UPDATE. It will soft brick!!! I tried in vain and am having to resort to 'back to stock' as, like a pleb, I don't backup before I tinkered
Sent from my SM-G901F using Tapatalk
I happens to the best of us, man. Sorry to hear. I'm currently not rooted, but at some point will, so that possibility of messing up will ALWAYS be there.
i have just updated my yoga 830LC. But i forgot my bootloader is unlocked. It's soft brick. Can you help me how to back to stock Lollipop ROM. please help me! thanks
Do you have a backup? When I first tried to update I think it did update part of the rom. I reflashed the patched esp (which you should still have if you have unlocked you boot-loader)
It then let me in to recovery and to restore.
Try that and report back
Sent from my SM-G901F using Tapatalk
Hi. I have this update from lenovo too, my 1050F is rooted, how I do a backup ? and you flash which stock rom, before upgrading ?
If possible, I want to keep my data.
Thank you.
I think the only way to keep you data is with something like Titanium backup saved to an external source and then whenever the update is finished re-root and restore selected backed up data
If you have unlocked you boot-loader you must have flashed a customers recovery. I did a twrp back up and selected what I want to restore.
Edit - get the files you need from this post
corasman said:
Hi Rob
These files I copied from various threads on here.
They are on my g/drive,if they are any good to you or anyone else.
http://tinyurl.com/zdr92pf
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo
http://tinyurl.com/hjy4kks
http://tinyurl.com/jhrjscj
Click to expand...
Click to collapse
Sent from my SM-G901F using Tapatalk
I have the 8 inch version of this tablet (830F) and received a similar update notification.
I just used the temp recovery trick to root and disable some bloat but left it otherwise stock. The tablet is currently in the process of backing up with temp TWRP and I was thinking of unrooting and giving this update a shot.
But it's not worth losing root over it...
Did anyone apply the patch in the meantime? Were you able to root again?
Thanks.
Yeah I have rooted, unlocked the boot-loader and flash twrp... All is good.
Have you flashed the patched boot-loader? If so you will need to flash the stock 830F ROM
Soft Brick
I'm just leaving my experience in case anyone does the same mistake as I.
I tried to use de "Hide root" option of SuperSu before upgrading, I have a locked bootloader, so I thought that it would be enough but I well... it didn't even boot after de lenovo screen
So I had to returno to stock, after reading what other peole did I manage to finally flash it back to stock lollipop.
I download this stock rom from lenovo-forums.ru
1050f_s100196_151123_row_lос-50
Click to expand...
Click to collapse
[As rookie, cannot post links :silly:]
Before flashing, the flash.xml has to be edited. Find
<string>fastboot flash system $system_file</string>
Click to expand...
Click to collapse
and add -s 1G to the command
<string>fastboot -S 1G flash system $system_file</string>
Click to expand...
Click to collapse
Then, enter on bootloader mode. I did it from de Recovery Mode (PWR on, and after de "lenovo" press both volume keys)
And just flash it with Phone Flash Tool
Everything it's probably pretty obvious for many of you but I leave this here for noobies like me! :victory:
Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)
-beluga- said:
Sounds good. No I only have the temp twrp bootloader pushed from the pc. Untethered it is stock but it's rooted. I'll revert that tomorrow and give this a shot. Cheers.
Click to expand...
Click to collapse
Ok, this was a success -
1. Unroot through the SU app (just to be safe)
2. Restart
3. Apply the update through the regular system/settings UI and wait for it to finish
4. Re-root as before (using IntelAndroid-FBRL-07-24-2015 and BETA-SuperSU-v2.67-20160121175247)
Keep in mind that I was on stock bootloader and didn't alter much besides disabling crapware. Deeper modifications may cramp your style.
Cheers
---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------
dingers01 said:
I have a new 1050F which has finished churning through all the updates to get it from KitKat.
It is now at the level of this update (..S100256_160119..)
I was about to root following the "[HOW TO] Root Yoga Tablet 2 [STEP-BY-STEP] [NOOB FRIENDLY]" 1st post instructions by AndroMAN (which uses a temporary pushed recovery) but I'm now a little concerned since that will put me in exactly the position of you -beluga-.
I'd be grateful if you could let me know how you get on (or if anyone else can comment on whether attempting to root this way is now a bad idea)
Click to expand...
Click to collapse
Yes, this worked fine. See my other follow up post. Good luck.
saupiquet said:
Thank you 69PerTTu69.
Did you have keep your data partition?
I have understood you have only install system partition. Right ?
If so, I Will try to use your method.
Click to expand...
Click to collapse
Sorry for the delay, but no. Everything within the internal storage will be lost.
Hey guys,
This is almost certainly a stupid question but I would be grateful for any help. I have a Nexus 6p thats upgraded to the lastest Android O beta version of OPP2. I wanted to finally go around rooting it. I have enabled USB debugging, always allowed the PC's RSA fingerprint and checked allow OEM unlocking. Nothing else has been done before, I plan on following a step by step guide that will help me unlock bootloader, install custom recovery and root etc.
I tried googling and to my surprise I could not find any root guide for this version of Nexus 6p (maybe I am just blind?)
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Woah. Cheers mate! so i just need to plug my Nexus 6p in, execute the file and click on unlock bootloader? I assume i have to install super su after that and that will be it? :3 Sorry. I know i am asking stupid questions and you are obv a pro. Also the fact that my version is opp2.170420.019 makes no difference right?
chevycam94 said:
Just tossing this out there. Old, but should still do what you need. Now that I think about it, I should probably go ahead and update parts of it....
Android Job Box
Click to expand...
Click to collapse
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Allrighty then, ill take the plunge real soon! Thank you for all the help Any specific why I should go with TheFlash's build instead of this one: dl.twrp(dot)me/angler/? As far as I can see it only supports F2FS which I will probably not be using.
chevycam94 said:
No, shouldnt make a difference. SHOULDNT. lol
The first thing I would do is download TheFlash's TWRP build, and flash that using the tool once you have your bootloader unlocked. That can be a lifesaver. Let me know if you have any questions. Questions directly about the tool, please post in my tools release thread.
Click to expand...
Click to collapse
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
chevycam94 said:
None, specifically. But he seems to always be ahead of the curve for almost everything he does. And I really like his work. Personal preference I guess.
Click to expand...
Click to collapse
UsmanPirzada said:
Well your tool works well Bootlocker unlocked and TWRP isntalled. But i flashed the SR3-SuperSU-v2.79-SR3-20170114223742.zip and nothings happening. there is a super su app in the drawer but when i click it it says super su binary not installed. Dont suppose you would have any idea why this is?
Update: okay false alarm. installed supersu v2.8 and appears to be rooted now. although super su keeps on crashing.
Update2: actually no, not working properly. Some apps are getting root - others arent I guess
Click to expand...
Click to collapse
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
chevycam94 said:
Only SuperSU 2.79 SR4 or Magisk v13 will have functional root on Android O.
Magisk:
https://github.com/stangri/MagiskFiles
SuperSU:
https://download.chainfire.eu/1024/...-SR4-20170323220017-ODP1-5X-6P-ExtraDelay.zip
Click to expand...
Click to collapse
UsmanPirzada said:
Even more unstable lol, built for OPP1 not OPP2 apparently. Phone actually crashing now and rebooting after a few mins. Meh, srsly cold feet, am out. Going to flash it back to stock. hope that works atleast.
Click to expand...
Click to collapse
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
I flashed it to 7.1.1 N4F26T using NRT and now the it has severe lag and keeps freezing and screen isnt accepting touch commands. Since this is a fresh install I assume the RSA fingerprint and USB Debuugging option has been unchecked as well? I have downloaded the official stock image of 7.1.2. Can I apply it using recovery or something?
chevycam94 said:
It works the same on OPP1 and OPP2. But all in all, you'll have better luck with Magisk v13.
Click to expand...
Click to collapse
Okay, flashed it to 7.1.2 using recovery. Everything seems fine now. Thank god. Helpful tip to any noob out there trying to root Android O Beta 2 on your nexus 6p: dont.
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
in theory according to posts ive seen for other devices you need magisks latest beta version.
dslreports said:
I just received the OP5 yesterday and unlocked the bootloader. I got the "Android Pay can't be used on this device" message when I try to add a credit card on android pay. Does anyone know if I need twrp and magisk installed in order for android pay to work?
Click to expand...
Click to collapse
Check by Playstore>settings... you're probably uncertified...
EDIT: You need magisk to pass the safetynet...
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
EVR_PR said:
Usually deleting Play Store data and cache fixes the "uncertified" issue. It did with my OnePlus 3/3T. It didn't work for me with the OnePlus 5 however.
Click to expand...
Click to collapse
It won't unless you either 1) Use magisk as mentioned or 2) use a custom kernel with SafeyNet patches.
When you unlock your bootloader, the prop (which you can read using a terminal emulator and typing getprop) has a flag called verifiedbootstate. If it returns anything but green SafeyNet will fail.
Sent from my OnePlus 3T using XDA Labs
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
gameofdroness said:
this is probably a stupid question but it's been a while since ive used android ... can you use android pay if you don't unlock the boot loader?
Click to expand...
Click to collapse
Of course..why not...
HatRiGt said:
U need to flash latest magisk and pass the safetynet to make Androidpay to work.
Click to expand...
Click to collapse
I've flashed v. 13 (https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589) and worked as a charm!
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
oowaymike said:
I have both the newest version of Magisk and the manager, but I'm still failing safetynet, do I need to manually hide something else in magisk hide? Any help is greatly appreciated
Click to expand...
Click to collapse
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
yubimusubi said:
Try the latest stable version of Magisk. It worked for me a few days ago while the beta wasn't (beta is working for me lately though).
You might want to reflash stock boot partition before flashing Magisk, I don't know if it will make a difference...
Click to expand...
Click to collapse
Thanks for the suggestions. I tried the stable version with no luck as well. I'll wait for the next beta version, and if that doesn't do the trick ill try reflashing the stock partition. If anyone finds a custom kernel that gets around safety net I'd really appreciate it.
dslreports said:
Correct. It says uncerified for me. The only thing i did was unlock bootloader. Sigh. I guess i have to twrp and magisk. Thanks.
Click to expand...
Click to collapse
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Eric214 said:
I'm curious to know why one would unlock the bootloader if not at least to install custom recovery and root.
Click to expand...
Click to collapse
I don't know if this is OP'S reason, but you can boot TWRP without actually installing it... So you can take nandroid backups of an otherwise stock device.
Also, unlocking bootloader wipes your phone, so if you want it stock for now but think you might root in the future you won't have to deal with that...
TBH though, SafetyNet is working as advertised by failing an unlocked bootloader. We like to have our cake and eat it too.