Related
Hi guys,
Just wondering if I can get root without unlocking the bootloader. Seems that I;m hearing that this isn't possible, which makes no sense. I know Verizon is Verizon when it comes to locking things down(They were even blocking free games on dumbphones back in the day so that you would have to buy them, even when the manufacturer included them for free), but it seems that gaining root access is completely different than flashing a new ROM. Am I correct here?
Also, would towelroot work for this phone? I know it's a nice simple solution, but I believe their claim is for phones manufactured before Jun '14.
Lastly, would a solution like Safestrap work here? It's what I used on my last phone (S3), when Verizon locked THAT down.
I know it is a battle fighting Verizon on this, and I know it takes time, I was just wondering if I am reading this right, or if I could root, but run the standard ROM, just with the extra access... Really, the phone is working so well that I just want better control for things like deleting/disabling/freezing stock apps and such.
Thanks for any help!! Sorry if this is in the wrong thread, seemed appropriate.
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
Code:
D:\V10\LG_Root>Send_Command.exe \\.\COM8
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0p51 of=/data/media/0/system.img
FAIL
#ls
FAIL
#
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Where did you get you system.img file? if you are using the one from the g4 it will not work. The file needs to be rooted for your device and then injected.
ivangundampc said:
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
Code:
D:\V10\LG_Root>Send_Command.exe \\.\COM8
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#dd if=/dev/block/mmcblk0p51 of=/data/media/0/system.img
FAIL
#ls
FAIL
#
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Click to expand...
Click to collapse
ivangundampc said:
I am a user of H961N and it is also cannot be rooted.
I think root injection may be the answer.
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
This is the related thread in G4 forum. I have tried this method. However, I have encountered a problem shown below during the process:
It keeps returning "FAIL" to me no matter what command i enter. I have asked about this in the thread in G4 forum but no one answer me, sad
I think that you may try it and it may work, as the above problem may not due to the phone but my computer.
Click to expand...
Click to collapse
I'm curious, the 'Fail' just means that it fails to work, right? Phone works fine after that and all? No bricking or need to restore? If so, that's a safe risk. Thanks for the suggestion.
Mikey1969 said:
I'm curious, the 'Fail' just means that it fails to work, right? Phone works fine after that and all? No bricking or need to restore? If so, that's a safe risk. Thanks for the suggestion.
Click to expand...
Click to collapse
Yes, the phone is working fine after I have tried this. So it is a safe risk.
---------- Post added at 12:08 PM ---------- Previous post was at 12:06 PM ----------
spidey44 said:
Where did you get you system.img file? if you are using the one from the g4 it will not work. The file needs to be rooted for your device and then injected.
Click to expand...
Click to collapse
That's why I am trying to clone the system partition but it shows fail
Good luck with this but I have a feeling that unless someone has an exploit laying around, you'll need an unlocked bootloader.
Sent from my LG-H901 using Tapatalk
Should this be in the Q and A sections as this is not development?
Don't have an LG v10 yet, but found this:
www.droidviews.com/how-to-root-lg-v10-with-supersu-v2-56/
Thought I'll share if someone would like to give this a shot.
(try at your own risk, that's all I can write to that, since i can't try myself.)
Thanks for this.....but i was reading that article...it says you root it by flashing the superuser zip in TWRP recovery....um....you cannot flash custom recovery without root....or am i missing something. Im not bashing you for posting the article. I thank you very much for posting it! More like questioning the articles validity.
in99flames said:
Thanks for this.....but i was reading that article...it says you root it by flashing the superuser zip in TWRP recovery....um....you cannot flash custom recovery without root....or am i missing something. Im not bashing you for posting the article. I thank you very much for posting it! More like questioning the articles validity.
Click to expand...
Click to collapse
you need an unlocked bootloader
http://www.droidviews.com/how-to-unlock-bootloader-on-lg-v10/
and adb & fastboot tool, not root
To install a custom recovery
http://www.droidviews.com/how-to-install-twrp-recovery-on-lg-v10-h901/
That's how I usually would do it, the way it's described in the articles, since I still have to get my v10 from Far East can't test it.
And don't worry, I don't feel like you are bashing.
Life's too short to take anything too personal.
Awesome thank you for clearing that up!! I was totally confused for a second there.
GerManiac said:
you need an unlocked bootloader
http://www.droidviews.com/how-to-unlock-bootloader-on-lg-v10/
and adb & fastboot tool, not root
To install a custom recovery
http://www.droidviews.com/how-to-install-twrp-recovery-on-lg-v10-h901/
That's how I usually would do it, the way it's described in the articles, since I still have to get my v10 from Far East can't test it.
And don't worry, I don't feel like you are bashing.
Life's too short to take anything too personal.
Click to expand...
Click to collapse
What you've mention is only working for tmobile V10, since it's bootloader can be easily unlocked while the other are not.
ivangundampc said:
What you've mention is only working for tmobile V10, since it's bootloader can be easily unlocked while the other are not.
Click to expand...
Click to collapse
Thanks for clearing that up. Didn't know that and didn't see that on the article.
Cheers
I think if LG release a genuine ROM file, we could replace recovery parition with rooted one and flash it to our phone, that the only way open but LG hasn't released any ROM file yet.
phillymade said:
Should this be in the Q and A sections as this is not development?
Click to expand...
Click to collapse
Sorry, wasn't sure, as I was asking about development.... Sometimes this is like a scene form the movie Big Trouble... At the airport, "Arrivals or Departures"? "Well, we're arriving at the airport, but then we're going to be departing.".
Trying to root Nougat (Android 7)? Then read the comments at the bottom please...
I will first state I do NOT own a Moto G4, I own the G3 and the X Pure which are both 3rd Gen devices, but I was requested to write this tutorial by a few users here due to lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto G3/4, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread. Remember, I do not own this device although the methods used are the same as similar devices.
Prerequisites:
0) Be running Marshmallow (Android 6.x) stock ROM, at this time Nougat (Android 7.x) is not working via any method.
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: As of 7/18/2016, Amazon ad-subsidised Moto G 4th Gen devices cannot be bootloader unlocked, therefore they cannot be rooted. Sorry, Lollipop and newer Android security changes pretty much put an end to that.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See TWRP's Moto G 2016 page
3) You need a copy of the latest stable SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device. SR1-SuperSU-v2.78-SR1-20160915123031.zip is the lastest version verified to work with this method.
Note: Do NOT use any 2.77 version, it was a beta intended specifically for the SG Note 7 and will not work, it does not harm but fails to root.
4) Reboot and start TWRP recovery, and PERFORM A COMPLETE BACKUP IN TWRP (Nandroid)!!!
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Notes on Nougat/Android 7... At this time this method of rooting does not work properly on the official Nougat ROM for this device, it causes WiFi issues and interface problems (settings crashes, etc) and with no complete factory image there is no work fix other than to restore your Nandroid backup to pre-root status. If you wish to play with this method and try it, your on your own, I will try to assist but as I stated earlier I do not own this device. To my knowledge as of this posting, there is no working root on stock Android 7 on this device.
I can confirm this worked on my formerly-amazon XT1625 16GB G4. You will get an error about not being able to mount /data, but it proceeds and works anyway.
This is exactly what was missing! I rooted as normal with the latest SuperSU expecting it to just work like on other phones/tablets, but yeah. Before specifying systemless, it hung on boot. After following your instructions it booted right up. Thanks!
Also if you setup adaptable storage with your SDcard, so it works like internal storage, TWRP can't find any files on the SDcard. You will need to revert to non-adaptable storage for TWRP to find the supersu ZIP file.
And make sure you're using the latest SuperSU-- I accidentally tried a very old version which did not work!
Scared Noobie
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Appreciate this. I miss the old days where it was all simple. Everything was flashable. Never had to flash back to something or re flash.
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
cuvtixo said:
I should probably be posting this on some noobie forum, but I read Motorola's "Unlock Your Bootloader" and it scared the **** out of me. Can someone give me a ballpark figure of the chances of bricking the phone? (I know this particular phone is new, but I'm just looking for a rough estimate. How common is it generally to brick a phone just from unlocking the bootloader?)
Click to expand...
Click to collapse
Very rare...all you need is read, read, read and follow the instructions. Good luck
Very nice and just what I needed. Worked perfectly on my Amazon Moto G4 with ads. I got no errors or messages but booted fine-got caught in a boot loop once as the SuperSU file explains after it installs. Boots in less then a minute first time.
Marty
acejavelin said:
It's about as common as bring bricked from performing a factory reset, because that is the only part that really does much... So extremely rare, but the possibility is always there. Remember to have patience, the resets and wipes can take what seems like forever.
The dangerous part is what you do after the bootloader is unlocked.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Tomsgt said:
Hey i wiped this up based on your post it should really help. it completely automates the process check it out if you want to and you can also ad it to the OP if you want to.
DOWNLOAD TOOL HERE Root-moto-g-4th-gen
Click to expand...
Click to collapse
cheers mate
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
zipjay said:
I signed up for xda just to give you props! I rooted my phone using instructions not from here and i was suck in a boot loop. your little command there fixed it! I freakin love you.. wish i could buy you dinner! Thanks a million
Click to expand...
Click to collapse
Your welcome... Just give click thanks on the first post, but if you feel absolutely compelled to buy me dinner, there is the Donate button.
Sent from my MotoG3 using Tapatalk
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
mikeruss said:
I rooted my G4 in the normal way using supersu 2.46, and now boot hangs on the white Moto screen. (advice from another site)
I am waiting for a SD card to update to 2.76 with the systemless command.
Is there anything else I can do in the interim, I tried deleting the contents of /supersu from Twrp and that hasnt made any difference. I have also wiped data and caches.
thanks .. Mike
Click to expand...
Click to collapse
Can't you just use MTP mode of TWRP to copy the latest SuperSU to internal storage then flash after creating the config file?
Sent from my MotoG3 using Tapatalk
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
mikeruss said:
thank you, worked fine.
would I be right in thinking I need the sdk23, arm, 64 bit version of xposed ?
Click to expand...
Click to collapse
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
acejavelin said:
I don't know... I don't own the G4 *yet* but possibly in the near future now that I know the Amazon version can have the ads striped out easily enough... I would do a nandorid and try it, if it fails, restore and use the 32-bit version.
Someone else may have a better answer for you.
Click to expand...
Click to collapse
32 bit
Sent from my Moto G (4) using Tapatalk
thanks, xposed works fine
Well, I was planning on joining all of you with your Moto G4's soon, or possibly the G4 Plus... but since the Amazon version can't be unlocked anymore I got cold feet, and today Best Buy was running a special on the Moto X Pure 32GB edition for $249 (My Best Buy Elite members only), I pulled the trigger on that one instead. No change in helping though, I didn't have the device to begin with so I will continue to assist with this thread as I can.
Good day everyone.
Please, give me an advice. How to unlock FRP HONOR 5X (Android 6.0.1, EMUI 4.0, Kiw-L21) ????
Thank you for your advice
Tatrox said:
Good day everyone.
Please, give me an advice. How to unlock FRP HONOR 5X (Android 6.0.1, EMUI 4.0, Kiw-L21) ????
Thank you for your advice
Click to expand...
Click to collapse
remove your google accounts from the phone reboot
You can follow this guide to successfully unlock your phone.
Hope this helps you.
Did you ?
Hey !
Did you succeed unlock FRP ?
I have the same problem to be able to flash a stock recovery...
I have no access to the Stock Custom and I'm not able to remove any google Account (my Phone has no rom).
If you did something for this, please keep me inform
And excuse my language : I'm french.
Cheers
Did some searching around and found this thread.
http://forum.xda-developers.com/honor-5x/help/unlock-bootloader-issues-kiw-t3411032
The information is here:
tohc1 said:
To answer my own problem/ for anyone else having problems it is necessary to remove the factory reset protection (frp) to do this you need to remove all pin/password/fingerprint locks, then remove all google accounts and finally do a factory reset.
Then the usual adb/fastboot commands work fine.
As linux33it says the bootloader can be unlocked without the option in the developer options.
Click to expand...
Click to collapse
While this works for some - it failed to work for me. Maybe because I didn't enable a little option on the screen about allowing OEM unlock. Maybe. But I (stupidly?) ended up where I was sent in this external guide.
http://www.modaco.com/forums/topic/...our-honor-5x-official-and-unofficial-methods/
Basically went to this site and used their tool (cost me USD$16) to wipe the FRP.
https://www.dc-unlocker.com
Maybe if you enable the option about the OEM unlock in Developer Mode this isn't necessary..........
Hopefully this helps someone. So to outline - let me show what I did - including errors.
Wipe the phone / factory reset.
Reboot and ensure everything is removed. Factory reset again.
Tried the commands - got error.
Did search for FRP unlock and found site.
Followed instructions on site which led me to download DC Unlocker and pay for their FRP unlock.
Reboot and setup phone (with no accounts or password or fingerprints).
Enabled "OEM UNLOCK" in developer options (which I didn't see before.........)
Run commands (they all now work).
Bootloader unlocked successfully.
Device factory resets.
Setup device again skipping accounts/password/fingerprints.
Follow instructions for flashing TWRP and finishing up.
Complete.
Again - hopefully this helps someone.
id recomend official one.. seems easy
thilak devraj said:
id recomend official one.. seems easy
Click to expand...
Click to collapse
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
Look at the twrp thread in android development section..
There is a detailed guide how to
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
It's a worthwhile effort. Appreciate it buddy.
khat17 said:
Explain please? What I'm putting forward is some information for persons that may not be as mobile tech inclined. Or persons over-eager like myself (actually bricked the phone and brought it back from boot-loop). While some information may be common knowledge for persons who do this often (or devs), persons just getting into it may make mistakes. Don't want them to do stuff and end up bricking the device.
Click to expand...
Click to collapse
Even newbies can do it right. Provided that they strictly follow the steps.
Sent from my Galaxy Tab 3 using XDA Labs
I agree. But I don't recall seeing anything in the original instructions about the FRP which shows / states ensuring OEM unlock is checked. Unless I missed it. I DO recall seeing it somewhere else in another thread where someone mentioned it. But I still don't know if the case is enabling it means you don't need to use the DC Unlocker program.
thilak devraj said:
id recomend official one.. seems easy
Click to expand...
Click to collapse
adriansticoid said:
Even newbies can do it right. Provided that they strictly follow the steps.
Sent from my Galaxy Tab 3 using XDA Labs
Click to expand...
Click to collapse
khat17 said:
I agree. But I don't recall seeing anything in the original instructions about the FRP which shows / states ensuring OEM unlock is checked. Unless I missed it. I DO recall seeing it somewhere else in another thread where someone mentioned it. But I still don't know if the case is enabling it means you don't need to use the DC Unlocker program.
Click to expand...
Click to collapse
you dont need dc unlocker, unless you have not checked "oem unlock" option in dev. options..(thats also only case if you were on lollipop)
and if you are on mm, you dont even need to check that option,
Thanks for that info. Next one I get my hands on will try that out and see.
thilak devraj said:
you dont need dc unlocker, unless you have not checked "oem unlock" option in dev. options..(thats also only case if you were on lollipop)
and if you are on mm, you dont even need to check that option,
Click to expand...
Click to collapse
khat17 said:
Thanks for that info. Next one I get my hands on will try that out and see.
Click to expand...
Click to collapse
what happened with the current one??
thilak devraj said:
what happened with the current one??
Click to expand...
Click to collapse
I had basically bricked it and brought it back. Think the one I got had some issues, because I couldn't update it at all. Even before rooting it wouldn't update. Then I realized that when the update was running it rebooted into TWRP - so I flashed back the stock recovery and tried again. No luck. This was done with disabling OEM unlock as well and still nothing. So I got an UPDATE.APP as well as a nandroid that I believe was supposed to be able to update the phone. None worked.
khat17 said:
It's a little bit of both. Those are the steps I followed to get root access. However, I don't recall seeing anything about the FRP in any of the previous guides.
As for my specific issue, I can't update regardless of what I try. After de-bricking the device I got it to this stage. I'll upload the screenshots shortly.
*EDIT*
So this is my phone now. Partly upgraded it seems. The device is now at B331 instead of B151, but still on EMUI 3.0
And what I want to point out is - after enabling DEVELOPER MODE - ensure you check the OEM UNLOCK option.
Because I can't confirm at this point if doing that will prevent having to pay for the FRP unlock.
Click to expand...
Click to collapse
But now that you've confirmed that there's no need to pay for the bootloader unlock, I would go ahead and do some experimenting if you suggest. For science. But I'm a little reluctant to try and re-lock the bootloader and then unlock it again. If you can confirm or even partly guarantee that it works however, I'll do some messing around with it. For science. Otherwise, I've managed to get the device to a working state now - wouldn't want to mess with it much.. Only if I can try something else to get EMUI 4 on it.
khat17 said:
I had basically bricked it and brought it back. Think the one I got had some issues, because I couldn't update it at all. Even before rooting it wouldn't update. Then I realized that when the update was running it rebooted into TWRP - so I flashed back the stock recovery and tried again. No luck. This was done with disabling OEM unlock as well and still nothing. So I got an UPDATE.APP as well as a nandroid that I believe was supposed to be able to update the phone. None worked.
.
Click to expand...
Click to collapse
thats something wiered,, you shouldve got it into service center before rooting, saying that it wasnt updating....
thilak devraj said:
thats something wiered,, you shouldve got it into service center before rooting, saying that it wasnt updating....
Click to expand...
Click to collapse
I live outside of the country of purchase. Doubt I can send it back now anyways. And I got it working so it's fine.
I like it better than the BLU and the Samsung I had. FAR easier to root. Even with the issues I had.
khat17 said:
I live outside of the country of purchase. Doubt I can send it back now anyways. And I got it working so it's fine.
I like it better than the BLU and the Samsung I had. FAR easier to root. Even with the issues I had.
Click to expand...
Click to collapse
how did you manage to get working??
thilak devraj said:
how did you manage to get working??
Click to expand...
Click to collapse
I posted it in this other thread.
khat17 said:
Hi all. I'd like to put forward some suggestions to be placed in the first post. I literally paid cash to learn and figure some stuff out. Even if you're good at following instructions or partially experienced in these things, when you're eager to get it done or impatient (like me) you find the fastest route.
Here are some links in case someone wants to just go through the whole thing themselves.
http://forum.xda-developers.com/honor-5x/how-to/unlock-frp-t3444584#post69917735
So here's what happened. I got the phone and was very eager to just get my stuff on it right away. Rooting is the first thing I wanted to do and looked that up to get it done. Made a mistake in the process and ended up paying cash to learn. Hopefully others will read this and not suffer the same fate.
What I Did (Including Mistakes)
Wipe the phone / factory reset.
Reboot and ensure everything is removed. Factory reset again.
Tried the commands - got error about FRP protection.
Did search for FRP unlock and found site.
Followed instructions on site which led me to download DC Unlocker and pay for their FRP unlock.
Reboot and setup phone (with no accounts or password or fingerprints).
Enabled "OEM UNLOCK" in developer options (which I didn't see/enable before.........)
Run commands (they all now work).
Bootloader unlocked successfully.
Device factory resets.
Setup device again skipping accounts/password/fingerprints.
Follow instructions for flashing TWRP and finishing up.
Complete.
Some other things to ensure you note - if you're migrating from any Samsung device, don't do restore of Samsung stuff like XPOSED to the Huawei. And don't just arbitrarily do a restore from Titanium either. Select only the apps you want to use, or do the longer process of getting them from Google then restoring the data after.
Something else I noticed on my KIW-L24 is that I can't update. At all. I tried using different methods including the UPDATE.APP file for the phone, but it just gets stuck in a boot-loop. Currently going to load the B151 UPDATE.APP and see if I can de-brick it. Will edit and update the thread.
*EDIT1*
And just my luck. Didn't work. So stuck in a boot-loop. Working on it and will update when done or I give up.
*EDIT2*
So during the boot-loop I held VOL-DOWN+PWR and it went to a FASTBOOT+RECOVERY option. From there I flashed TWRP back to it and the system is now up and working. So lesson learned there. No idea why my own won't go to 6 though. Don't mind 5, but wanted to go up to 6..............still - better to have it working than not working. So happy there.
Click to expand...
Click to collapse
Yeah. So after TWRP was flashed, I did a restore from a backup I found online. And that's how I managed to get it up. The restore was for 151 not 331.
khat17 said:
I posted it in this other thread.
Click to expand...
Click to collapse
anyway, nice to see that youve got it working,...
So I need help badly! And of course, I've even asked if I could pay someone. I'm new to phones/tablets/android. Very comfortable with all things computer though. I bought the Amazon Kindle Fire HDX 8.9 for the second time off Ebay that Amazon did not want to register without a receipt from my seller's purchase. I wanted this tablet for the specs and also we do a lot with Amazon. I've been customizing my computer for years and I don't care the specs of the $50 fires that are coming out in 2017. However both my sellers were honest and gave me everything but their social security cards and said they had it registered in their name and called Amazon as well. It seems almost like Amazon is finding a way not to register these secondhand Fires that are discontinued without a receipt from the original owner for "security". So this is when I found out about rooting while googling my problem. I have the 4.2 OS. And I've read a lot of warnings about this particular model. Most of the advice is over two years old so I want to know what can currently be done to turn this tablet into an Android. Is it possible?
And can I get simple detailed instructions so that I don't "soft brick" or "hard brick" my device.
I got full refund from my first seller. The second one told me he would give me partial credit if I kept it and tried to root it. If it bricks he says he will refund me completely. He is under the impression that rooting isn't difficult.
Can someone please help me?
Wendy
justyermama said:
So I need help badly! And of course, I've even asked if I could pay someone. I'm new to phones/tablets/android. Very comfortable with all things computer though. I bought the Amazon Kindle Fire HDX 8.9 for the second time off Ebay that Amazon did not want to register without a receipt from my seller's purchase. I wanted this tablet for the specs and also we do a lot with Amazon. I've been customizing my computer for years and I don't care the specs of the $50 fires that are coming out in 2017. However both my sellers were honest and gave me everything but their social security cards and said they had it registered in their name and called Amazon as well. It seems almost like Amazon is finding a way not to register these secondhand Fires that are discontinued without a receipt from the original owner for "security". So this is when I found out about rooting while googling my problem. I have the 4.2 OS. And I've read a lot of warnings about this particular model. Most of the advice is over two years old so I want to know what can currently be done to turn this tablet into an Android. Is it possible?
And can I get simple detailed instructions so that I don't "soft brick" or "hard brick" my device.
I got full refund from my first seller. The second one told me he would give me partial credit if I kept it and tried to root it. If it bricks he says he will refund me completely. He is under the impression that rooting isn't difficult.
Can someone please help me?
Wendy
Click to expand...
Click to collapse
Device can be rooted w/o registering and install the custom ROM of your choice. But it will take some work, patience and tech experience. I can point you to the technical documents early next week if interested. Travelling with limited/no network access this weekend.
Davey126 said:
Device can be rooted w/o registering and install the custom ROM of your choice. But it will take some work, patience and tech experience. I can point you to the technical documents early next week if interested. Travelling with limited/no network access this weekend.
Click to expand...
Click to collapse
:angel: So I really appreciate the quick response, and you have renewed my hope for this situation. That would be absolutely great. I once had Linux OS on a used computer I bought and quickly reformatted so I could install Windows. I found it to be not very user-friendly. However, while I'm waiting for next week to come, should I study the Linux OS or is there anything I should read or concentrate on learning, off the top of your head, to make my journey a little bit easier? Thanks again.
jymama
WAITING Patiently for Direction to root/flash Blacklisted Kindle Fire 8.9
justyermama said:
:angel: So I really appreciate the quick response, and you have renewed my hope for this situation. That would be absolutely great. I once had Linux OS on a used computer I bought and quickly reformatted so I could install Windows. I found it to be not very user-friendly. However, while I'm waiting for next week to come, should I study the Linux OS or is there anything I should read or concentrate on learning, off the top of your head, to make my journey a little bit easier? Thanks again.
jymama
Click to expand...
Click to collapse
Still Waiting to find out how to turn my blacklisted fire hdx 8.9 4th gen into a usable tablet. When I found out it was possible, I decided I would give it a shot and accepted $50 of the $130 I paid and kept it. Anyone who can help someone who is good with a computer, but I have no experience/knowledge with androids, I'm willing to learn if someone could point out the way. This particular model of tablet is supposed to not be easy to do, and please take into consideration my inexperience with this, I am willing to put time and effort if I could get the information/specific directions. I'm willing to compensate someone for their time. Please help.
Thank you, Wendy
jyermama
justyermama said:
Still Waiting to find out how to turn my blacklisted fire hdx 8.9 4th gen into a usable tablet. When I found out it was possible, I decided I would give it a shot and accepted $50 of the $130 I paid and kept it. Anyone who can help someone who is good with a computer, but I have no experience/knowledge with androids, I'm willing to learn if someone could point out the way. This particular model of tablet is supposed to not be easy to do, and please take into consideration my inexperience with this, I am willing to put time and effort if I could get the information/specific directions. I'm willing to compensate someone for their time. Please help.
Thank you, Wendy
jyermama
Click to expand...
Click to collapse
Hi - as noted in my original response time, patience and some technical expertise will be needed to root the device via the 'bulk mode' approach. Unfortunately, time is not an abundant resource at present so you're pretty much on your own outside responding to specific questions. Below is the initial technical document which will undoubtedly seem overwhelming on initial inspection. You will likely want to read through the next few posts to adsorb guidance from the author (@draxie). Better yet, scan/search the thread for the word 'bulk' for related posts. Also see this post for links to a couple 'tools' that you will need to install on a Windows host before getting started. Good luck; ask questions as they arise.
bulk mode doc: https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
main bootloader unlock thread: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
auxiliary thread (lots of good info): https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
Davey126 said:
Hi - as noted in my original response time, patience and some technical expertise will be needed to root the device via the 'bulk mode' approach. Unfortunately, time is not an abundant resource at present so you're pretty much on your own outside responding to specific questions. Below is the initial technical document which will undoubtedly seem overwhelming on initial inspection. You will likely want to read through the next few posts to adsorb guidance from the author (@draxie). Better yet, scan/search the thread for the word 'bulk' for related posts. Also see this post for links to a couple 'tools' that you will need to install on a Windows host before getting started. Good luck; ask questions as they arise.
bulk mode doc: https://forum.xda-developers.com/showpost.php?p=71430759&postcount=736
main bootloader unlock thread: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
auxiliary thread (lots of good info): https://forum.xda-developers.com/kindle-fire-hdx/general/thor-4-5-5-2-easy-to-root-unlock-t3571240
Click to expand...
Click to collapse
I have done all the step in the link of bulk mode you post. It works very well with many KFHDX7 I have done but one of mine can't flash any ROMs although it can boot to recovery and bootloader. Could you help me?
P/s: It stuck at the white kindle fire logo after I flash any ROMs but I can boot to TWRP and fastboot.
Chatchum said:
I have done all the step in the link of bulk mode you post. It works very well with many KFHDX7 I have done but one of mine can't flash any ROMs although it can boot to recovery and bootloader. Could you help me?
P/s: It stuck at the white kindle fire logo after I flash any ROMs but I can boot to TWRP and fastboot.
Click to expand...
Click to collapse
Be sure to wipe storage before attempting to flash a new/different ROM:
- make sure the latest TWRP build is installed (link)
- boot into TWRP
- tap Wipe followed by Advanced Wipe
- tick all partitions EXCEPT 'Internal Storage'
- execute wipe (may take a few seconds)
- return to main menu and flash ROM of your choosing
- only ROMs customized for this device can be flashed
- some require a GAaps package and/or SuperSU; read ROM OP for details
If the above fails perform a comprehensive wipe that includes all partitions. Then reboot device into TWRP, re-download ROM and supporting packages and attempt to flash again.
Davey126 said:
Be sure to wipe storage before attempting to flash a new/different ROM:
- make sure the latest TWRP build is installed (link)
- boot into TWRP
- tap Wipe followed by Advanced Wipe
- tick all partitions EXCEPT 'Internal Storage'
- execute wipe (may take a few seconds)
- return to main menu and flash ROM of your choosing
- only ROMs customized for this device can be flashed
- some require a GAaps package and/or SuperSU; read ROM OP for details
If the above fails perform a comprehensive wipe that includes all partitions. Then reboot device into TWRP, re-download ROM and supporting packages and attempt to flash again.
Click to expand...
Click to collapse
I forgot unlock bootloader before flash ROMs on that HDX7. Do you think it made that problem?
These ROMs are work very well, because I flash 3 HDX7s by the same way with this HDX7 but there is no problem.
Please help me!
Chatchum said:
I forgot unlock bootloader before flash ROMs on that HDX7. Do you think it made that problem?
These ROMs are work very well, because I flash 3 HDX7s by the same way with this HDX7 but there is no problem.
Click to expand...
Click to collapse
Wipe and flash this ROM. Work? If so proceed with bootloader unlock using Fire Nexus as a temporary base.
Chatchum said:
Please help me!
Click to expand...
Click to collapse
This ^^ is both annoying and unnecessary.
Davey126 said:
Wipe and flash this ROM. Work? If so proceed with bootloader unlock using Fire Nexus as a temporary base.
This ^^ is both annoying and unnecessary.
Click to expand...
Click to collapse
It works very well.
Chatchum said:
It works very well.
Click to expand...
Click to collapse
Great! You should now be able to generate an unlock code specific to your device (step #1) and unlock the bootloader (step #3), possibly with the help of these drivers to enable fastboot communications from a Windows host.
I flashed wrong TWRP file, and now my HDX7 couldn't boot to recovery or bootloader by press power + up (down) button and it stuck in white logo.
Chatchum said:
I flashed wrong TWRP file, and now my HDX7 couldn't boot to recovery or bootloader by press power + up (down) button and it stuck in white logo.
Click to expand...
Click to collapse
You're in a world of hurt if device can not be placed into fastboot mode via <power>+<vol-down>. Your may need to attempt a recovery via 'bulk mode' which is neither easy nor assured.
https://forum.xda-developers.com/ki...isted-kindle-fire-hdx-8-t3636657/post73104157
Davey126 said:
You're in a world of hurt if device can not be placed into fastboot mode via <power>+<vol-down>. Your may need to attempt a recovery via 'bulk mode' which is neither easy nor assured.
https://forum.xda-developers.com/ki...isted-kindle-fire-hdx-8-t3636657/post73104157
Click to expand...
Click to collapse
I have tried to do via bulk mode but I can't boot to fastboot to do all of it
Chatchum said:
I have tried to do via bulk mode but I can't boot to fastboot to do all of it
Click to expand...
Click to collapse
Sorry this happened. Bulk mode is the last option short of replacing boards.
Hello very friendly helping people!
Im a 10 year iPhone user, but over time i came to hate all the restrictions and so i got myself a K30 Ultra and later today it should finally arrive!
Unfortunately i found out that it doesnt check the Google SafetyNet thingy and i can't use Google Pay with it. That kinda sucks, I never thought about stuff like this on iOS, but I'm confident there is a solution for it.
I found out about rooting my device, but it somehow isn't possible because of the Mediatek chip. But then I also found out that apperenty there IS a way to use the program/thingy that makes the phone pass SafetyNet (Magisk) without the need of a custom ROM.
I'm sorry if im confusing words like rooting im very noobish about all this.
So here are my questions in short form:
1. Can I make Google Pay Work in any way on my Redmi K30 Ultra?
2. Does this also affect my banking apps (I'm using DKB and Kontist) and can this be solved, too?
3. Could you link me some guides how to do it?
4. Is there any danger doing it (like deleting my phone if it doesnt work) and is there a possibility to safe my device on the PC or something like this to be safe?
5. Are their any safety concerns doing "it" (not sure what the solution will be) and should I install an anti virus program on the device? I just read about the cerberus trojan and its kinda scary. I think iOS systems were always pretty safe against those.
6. Anything else i need to know?
Thank you so much! I appreciate it a lot that there is a place where i can go to get help on those things! <3
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
jwoegerbauer said:
Google Pay and any other banking apps refuse to work when a rooted Android gets detected by them. BTW: SafetyNet API doesn't purely check whether the device's Android is rooted, as the API is designed to check the overall integrity of device's Android.
Click to expand...
Click to collapse
Hey, thanks for your post!
Are you implying that there is no way around that and its doomed to forever not work on my device?
To clarify things: SafetyNet is run by an app that has implemented this API, it's not run by Android OS itself. Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
FYI: Any app not having SafetyNet API implemented easily can check whether Android got rooted / tampered or not. The app simply runs functions like
Code:
isRootNative
isDetectedDevKeys
isDetectedTestKeys
isFoundBusyboxBinary
isFoundDangerousProps
isFoundHooks
isFoundResetprop
isFoundSuBinary
isFoundWrongPathPermission
isFoundXposed
isNotFoundReleaseKeys
isPermissiveSelinux
isSuExists
isMagiskSUExists
isFoundMagisk
isFoundRootCloakingApps
what can't get prevented by Magisk.
jwoegerbauer said:
Yes, Magisk allows you to lever out this test by manipulating device's fingerprint so you will possibly be able to use Google Pay etc.pp
Click to expand...
Click to collapse
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Mirardt said:
Ok, perfect. Would you be able to link me to a guide that shows me how to install Magisk on my device? It has a Mediatek chip so a custom ROM isn't possible (as far as I understand).
Click to expand...
Click to collapse
How to install Magisk without a Custom ROM is explained here.
If a Custom ROM like TWRP isn't officially made public for your device then you have to compile TWRP at your own.
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
JaboJG said:
This is TWRP and Magisk for the latest firmware on the K30 Ultra. https://mifirm.net/downloadtwrp/166
Click to expand...
Click to collapse
Oh wow how cool is that, that is custom for the K30 ultra
And do I install that with the guide linked above or do I need some certain skill and experience to do that. It says it isn't tested yet. If I do a mirror of my phone before nothing really bad can happen right?
Google Pay on a rooted device with Magisk installed /is/ possible, my Galaxy Note 9 with Dr. Ketan's ROM works with Google Pay and I believe it's due to the CTS Profile fix which is available in its ROM Tool app. So there's going to be some way to make it work with the K30 Ultra.
Click to expand...
Click to collapse
Nice!!!
Yeah the only think that failed SafetyNet Test is the "CTS profile match". But I can't use those roms for my K30 ultra, right, so I just do it with Magisk?
Thanks so much!!
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
JaboJG said:
You need to unlock your bootloader with the Mi Unlock tool then flash TWRP over fastboot, and in TWRP make the appropriate backups and flash Magisk. There's many guides and it's relatively straight forward.
K30 Ultra is basically a brand new phone, it's like a month old. It'll be a while but keep an eye on XDA Forums, on the internet, and on YouTube. Somebody will eventually describe or figure out how to fix the CTS Profile.
I think I'm not gonna modify mine and I'll just wear my Apple Watch to use it for contactless payments.
Click to expand...
Click to collapse
Alright, so I read 12384 guides and had a very tiny sense of it. The Mi Unlock tool stopped me, though, and now I'll have to wait another 6 days.
As I understood it, my data will be erased, but can be just be restored by MIUI if backed up before. I'm gonna let you know how it worked after I'll do it in about a week.
Probably I won't have to patience to wait. Google Pay is a really nice to have, but neither voLTE, nor voWifi works on my device, so I for sure have do hack that some weird way, because i have no mobile network at all at home and absolutely need voWifi.
Thank you very much for your kind help! <3
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
JaboJG said:
No problem at all.
I'm not sure if Wifi-Calling (voWifi) works with my carrier as I've turned it on with the carrier and in the phone, and it doesn't seem to be making calls over wifi. Not a big deal for me though as I've got Unlimited calls with my carrier.
Please let us know if and when you do flash the TWRP as I'd like feedback before flashing it myself.
Click to expand...
Click to collapse
Yeah, me too, but I have a very bad connection in my flat so I do need voWifi anyway. I will let you know and hope I won't brick my device. But as I understand it, bricking the device just by flashing twrp is very unlikely, right?
MerlijnD said:
Do your banking apps refuse to work or is it only google pay that fails due to the safetynet fail?
Click to expand...
Click to collapse
Only Google Pay, both of my banking apps work perfectly. I couldnt scan the security bar code though, some internal google app wouldn't allow it. So i had to put in both the (very long) idendification and security numbers in manually.
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
MerlijnD said:
Alright thanks. Another thing im interested in is if Snapchat works when safetynet fails. Did you do any tests regarding that?
Click to expand...
Click to collapse
Not using Snapchat, but I just installed it and it starts without problems. Didn't made an account though.
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Mirardt said:
So I'm gonna be able to flash twrp and Magisk in exactly 14 hours and have some questions i would really appreciate an answer to <3
Using this: https://mifirm.net/downloadtwrp/166
1. The thing i want to flash first is twrp and it is the file called "recovery.img" in the downloaded folder, is that correct?
2. Just flashing twrp is "relatively" safe and if I do a backup and the device bricks by installing Magsik after, i can recover it through twrp, correct?
3. Should I not install todays new security update to MIUI or does that not matter at all?
edit: 4. Do I need/want to have "USB debugging", "Install via USB" and "USBebugging (Security Settings)" enabled or just "OEM unlocking"?
Thank you so much! I'm very nervous since i didn't read any experiences of rooting the K30 Ultra before and I'm scared of killing it.
Click to expand...
Click to collapse
JaboJG said:
Hey Mirardt, good luck. Let us know how you get on!
1. Yeah, you'll use fastboot to flash the recovery.img for TWRP.
2. Do a full backup with TWRP and you should be safe.
3. Doesn't matter, it's just the September Android security update.
4. Yeah turn on USB Debugging and connect your phone to your computer - it will ask you if you want to allow this computer to debug your phone, choose accept and always (or something similar to those words.) Do this before flashing TWRP.
Click to expand...
Click to collapse
Hey Jabo, nice, I'm gonna do just that! Just for clarification, I use Mi Unlock Tool first, THEN twrp, then backup, then magisk?
I'll let you know and thanks for the good luck!
edit: so the command would be "fastboot flash recovery recovery.img", right?
I'm VERY sorry for the noobish questions.
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Hey guys (especially JaboJG). quick update: Flashing twrp and Magsik both just worked perfectly. no brick. Thanks for your help!!
The only issue is that it didnt help in passing Google Safety Check. I tried almost everything there is and will post my logs of MagiskHide Props in their thread soon.
Also, now some apps don't work anymore because they detect the root. I hope we will find a fix.
macrett said:
I'm going to quickly use this thread to ask how to actually unlock the K30 Ultra Bootloader. I did everything the guides said, but Mi Unlock still doesn't recognize the phone when it's plugged in. Any Advice?
Click to expand...
Click to collapse
No idea, sorry. It just worked for me.