Related
From many many different threads and frankly confusing instructions I think I have puzzled together the following solid guideline for my kindle fire hdx from basic root to custom rom. Currently my firmware is 13.3.1.0.
Could someone take a look at this and tell me if I got this right or if I need to do stuff differently (or could do them better)? Don't assume that something is obvious, if it isn't written down, don't be shy to mention it. I would be ever so grateful .
Edit: I'm updating my experience as I move along the list and get more info just in case this might be useful to someone who is just as lost as I was in the beginning
Obligatory disclaimer: this is just a step-by-step guideline that worked for me. I'm not responsible if you chose to follow any of these steps and damage or brick your device.
Guideline:
-Download firmware version 3.2.3.2 and upgrade directly from any of the previous version by putting the file into the internal storage of the kindle, going to settings>device>system update on the kindle and installing the update from there.
-Root with Towelroot in the HDX toolkit downloaded from here (Edit: I got various error messages at this step but got it to work in the end. The 3rd post here shows what I did to get it working after getting error message 2 and 3 at various times)
-block OTA also with the tool in the HDX toolkit (is there a way to safely check that this worked? Edit: It worked )
-connect to wifi and install Flashify from the playstore (Edit: I ended up installing File Expert and flashify on another android device, backing up the flashify apk and sideloading it with ES File Explorer from the amazon app store to the kindle, I guess I could have also download the apk somewhere but I have trust issues.)
-download the img of TWRP 2.8.5.0. and put it in internal storage of kindle (had no problems)
-use flashify to save original stock recovery (had no problems)
-Use flashify to flash TWRP (had no problems)
- Boot into recovery mode via flashify to see if it worked (had no problems)
Now either A)
-download CM11 image and gapps and put the zip files on internal storage
-Edit: disconnect Kindle from USB afterwards
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- flash cm11 image and gapps (under install and then find them in the files)
- reboot
-Edit: I had the wifi not connecting problem that some people have with CM11 but a reboot took care of it.
-Edit 2: I couldn't get the kindle app to work on CM11 (it wouldn't synch my books, the device wasn't recognized by amazon and it would crash every time I logged in.) so I ended up replacing it with the Nexus rom. If the chance of this happening doesn't bother you then CM11 seems to still be a good choice.
or B)
- download HDX thor nexus rom and gapps and put the zip files on internal storage
- go into TWRP recovery mode (by powering off kindle and then pressing power and volume at the same time)
- make backup of original stockrom under backups and save copy on your Computer
- wipe system, data, cache and dalvik cache under wipe/advanced (all except internal)
- Edit: disconnect Kindle from USB afterwards
- flash nexus rom and gapps (under install and then find them in the files)
- reboot
- Edit: I'm very happy with it, it works flawlessly. Since it's based on Jelly Bean I may try replacing it with another rom sometime in the future, but I'm in no hurry
Mostly correct, you can update directly to 3.2.3.2 no need for incremental steps. The only way to know if ota blocker worked is to check for update but there's really no need, as soon as you've run towel root just disable WiFi as it won't be needed anymore.
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
uhraman said:
Where is unlock bootloader? As I know, you cannot flash TWRP without unlocking bootloader?!
Click to expand...
Click to collapse
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
derpadoodle said:
You can flash a cuber signed TWRP on a locked bootloader, as long as you're below 3.2.4.
Click to expand...
Click to collapse
Thanks for your replies! Is the method uhraman hinted at the better one?
snorklm said:
Thanks for your replies! Is the method uhraman hinted at the better one?
Click to expand...
Click to collapse
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
derpadoodle said:
Fully unlocking your bootloader is definitely worthwhile but it's quite a complicated endeavour and not required for running the current custom recoveries and ROMs. I'd recommend you stick with your current method and read up on the unlocking process once you're more conformable working with this device.
Click to expand...
Click to collapse
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
snorklm said:
Could I bother you to give me a few examples on *why* it is worthwhile? Thanks!
Click to expand...
Click to collapse
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Davey126 said:
- more robust recovery options when recovery (TWRP) is damaged/inaccessible; better chance of reviving a bricked device
- some custom roms install/operate better with unlocked BL (technically should not be needed but sometimes seen in early builds)
- some DRM aware apps on custom roms work better with unlocked BL(eg: playstore, prime)
Guidance form derpadoodle is sound. Enjoy what you have achieved thus far; revisit BL unlock when you are more comfortable with device/technique.
Click to expand...
Click to collapse
Thanks for the sound advice, I will probably never feel comfortable enough for that , especially because I haven't achieved much at all yet. I haven't even flashed TWPR yet.
Yay, I did it. CM11 seems to be working as intended! Thanks again for everyone who replied and also to everyone who put so much work into making and improving all the tools and software necessary to make this kind of thing even possible, I appreciate it!
What firmware were you on to begin your process mate... ?
B3NJY said:
What firmware were you on to begin your process mate... ?
Click to expand...
Click to collapse
I was on 3.0.5 when I got the device. Amazon didn't upgrade the firmware at all before sending it out, then I upgraded to 13.3.2.3. Why do you ask?
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
snorklm said:
Hmm, I have now noticed that the kindle app is not working properly. I can sign in (though every time I sign in or deregister my account the app crashes) but it's not synching any of my books. They don't show up at all. The device (named android device 2 in the kindle app settings) does also not show up under my devices on amazon. Anyone know what the problem could be because this is a bit frustrating. Is this a bug with CM11 or with the amazon app?
Click to expand...
Click to collapse
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Davey126 said:
Can't say definitively but I would lean towards CM11 as all Amazon apps (kindle/prime/shopping/video) work fine with the Nexus ROM (v2.0.5) which is layered on the same hw/fw base as CM11. Don't get me wrong; CM11 (and the devs who adapted to the HDX) are great! But there may still be a few hiccups with native Amazon apps.
Click to expand...
Click to collapse
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
snorklm said:
Thanks for the opinion! I couldn't find any solution to the problem anywhere online and therefore just finished replacing CM11 with the Nexus rom, now the kindle app works perfectly fine and I'm very satisfied with what I've got. I will keep an eye out on rom development but for now I'm resting on my laurels :victory:. Considering that I was helplessly lost when I first came to the board I'm very happy with how smoothly everything went. But I really needed that step-by-step list I made and the assurance from the pros that it was correct, otherwise I would have probably made a careless mistake :silly:. Maybe it will be useful to a few other newbies as well. Not sure I will ever dare to fully unlock the bootloader like some suggested I might want to do at a later point in time, but we will see . Thanks again for the help!
Click to expand...
Click to collapse
Glad to hear everything is working well! My daily driver is on Nexus and I could not be happier. Everything works as it should. No need to unlock the bootloader unless you plan to do more modding. Enjoy your device!
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
johnwaters said:
Nice. I think everybody needs this kind of guide. Whenever a question is asked it just kind of trails off most of the time.
I'm still working on the downgrade piece.
Click to expand...
Click to collapse
Agreed, I was overwhelmed by all the different threads and possibilities at first. I ended up approaching it like any other research project for a paper or presentation and dumped every solid (and recent) piece of good advice into Evernote and sorting it out there. But writing and updating guides (especially with the fast development I have observed) would be a lot of work, I understand completely why no one would volunteer to do it and everybody would rather answer questions on a case by case basis.
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
dynein said:
First of all thank you very much! I was looking for something like this, since i am also new to rooting devices and this stuff...
I got a new fire hdx 7 with 13.3.02
I haven't tried anything yet, I am still reading threads and i got some questions here:
http://forum.xda-developers.com/kindle-fire-hdx/general/update-1314-4-1-1-probably-sangria-t2901813
-> I can only find 3.2.3.2 here, which is the firmware u used? Or did you mean another one?
http://forum.xda-developers.com/show....php?t=2665683
-> the second link for hdx toolkit isnt working
How do i get the playstore on my device?
are there anywhere more informations regarding flashify? since i have no idea what this is...
thank you!
Click to expand...
Click to collapse
First thing you want to do is block OTA (over the air updates) or your device may be upgraded by Amazon to a level that gives you less options. Suggest using HDX Toolkit (here) to both root and block OTA. Then install twrp (here). From there you can opt to replace Fire OS will several different roms including Nexus, CM11 or CM12.
Flashify is an app that allows flashing recovery and roms from from within Android vs adb or a recovery environment. You can grab it from the Play store or another market. It's a dangerous tool; use with extreme caution.
Be aware that any of the above actions, if executed incorrectly, can permanently brick your device with little/no hope of recovery (guess that's the definition of permanent). Read, read and read some more before taking any action. Be sure to keep WiFi off on your device until OTA is blocked to prevent auto-updates.
Hi. I'm new here & registered in the hopes of finding a working solution since I've been trying for days.
I'm trying to root my Kindle Fire HDX 7" that's running OS 4.5.5. I've read a lot about needing to downgrade or rollback to version 3.2.8 first to be able to root. I downloaded the Thor bin file on my Kindle, but am not sure what to do with it or where to go from here. So I haven't gotten very far in the process & am stuck. Any help would be greatly appreciated!! And when responding, please bear in mind that I know very little about doing this sort of thing.
Thank you!!!!
gr8fuldee said:
Hi. I'm new here & registered in the hopes of finding a working solution since I've been trying for days.
I'm trying to root my Kindle Fire HDX 7" that's running OS 4.5.5. I've read a lot about needing to downgrade or rollback to version 3.2.8 first to be able to root. I downloaded the Thor bin file on my Kindle, but am not sure what to do with it or where to go from here. So I haven't gotten very far in the process & am stuck. Any help would be greatly appreciated!! And when responding, please bear in mind that I know very little about doing this sort of thing.
Thank you!!!!
Click to expand...
Click to collapse
My suggestion is you keep reading through the HDX forums to increase your knowledge of techniques, procedures and potential pittfalls that can permanently cripple your device (bricking). This is exceptionally easy to do. I understand you are new and seeking guidance but everything you need to know is here. The lack of responses reflects the reluctance of experienced contributors to pen yet another custom response. Post specific questions as they arise. You'll typically get a prompt response provided you have done your homework.
Thank you for your reply. I feel like I have spent a huge amount of time trying to root my kindle by researching and dowloading this or that. So, here's where I'm currently at. I have been following the directions on gizmag. I backed everything up & am using a computer running Windows 8. I enabled the ADB & downloaded the ADB files (from this site, I believe). When I ran the .exe file, the installation wizard gave me this error: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed".
That's as far as I've gotten. I hope the additional information will help users to assist me.
Thank you!
gr8fuldee said:
Thank you for your reply. I feel like I have spent a huge amount of time trying to root my kindle by researching and dowloading this or that. So, here's where I'm currently at. I have been following the directions on gizmag. I backed everything up & am using a computer running Windows 8. I enabled the ADB & downloaded the ADB files (from this site, I believe). When I ran the .exe file, the installation wizard gave me this error: "The device driver installation wizard did not update any of your software for your hardware devices because it was not better than the software you currently have installed".
That's as far as I've gotten. I hope the additional information will help users to assist me.
Thank you!
Click to expand...
Click to collapse
Regarding adb you can obtain the highly regarded 'Minimal ADB and Fastboot here:
forum.xda-developers.com/showthread.php?t=2317790
Install and make sure you can access your device via adb before proceeding. Use Google to learn basic adb commands as needed.
Take the gizmag article with a grain of salt. While there is good content much of the material is dated and likely not applicable to your device. HDX forums on XDA are your best resource for the most current info.
I managed to get the first 2 steps done from a thread I found on here, which were to downgrade to 3.2.8, then upgrade to 4.5.2. The next step says to "use Kingroot or another method". Does Kingroot work for the kindle hdx 7, do you know? I've tried downloading it & keep getting an error that says "Failed - Network error". What are the other methods available? Thanks again!
gr8fuldee said:
I managed to get the first 2 steps done from a thread I found on here, which were to downgrade to 3.2.8, then upgrade to 4.5.2. The next step says to "use Kingroot or another method". Does Kingroot work for the kindle hdx 7, do you know? I've tried downloading it & keep getting an error that says "Failed - Network error". What are the other methods available? Thanks again!
Click to expand...
Click to collapse
Kingroot works with all HDX models running FireOS v4.5.2. You can grab it from here. A brief network connection is required during the rooting process. Be prepared to flip WiFi on; run Kingroot and then immediately disable WiFi. Leave it on too long an you will likely receive an OTA update that will plug the vulnerability that permits rooting. If that happens you'll have to redo the rollback/upgrade procedure.
I have a Kindle Fire HDX 8.9 4th Generation (Saturn) which is rooted (Kingroot) everything works fine on the device however I can't seem to manually or automatically install the latest or any for that matter system updates. Automatic - Device options --> System updates --> check now sees and downloads the update but then fails. If I manually download the update and install it the system reboots and I get a Kindle Fire Fastboot screen. Please help. I love my tablet and really would like to be able to update it. Any help is greatly appreciated.
bnbliss
bnbliss said:
I have a Kindle Fire HDX 8.9 4th Generation (Saturn) which is rooted (Kingroot) everything works fine on the device however I can't seem to manually or automatically install the latest or any for that matter system updates. Automatic - Device options --> System updates --> check now sees and downloads the update but then fails. If I manually download the update and install it the system reboots and I get a Kindle Fire Fastboot screen. Please help. I love my tablet and really would like to be able to update it. Any help is greatly appreciated.
bnbliss
Click to expand...
Click to collapse
This seems to be an artifact of rooting with Kingroot. Not enough information (yet) to understand what happens. I assume you took no steps to manually block OTA updates.
Updating a rooted device, especially Fires, carries an increased risk of bad outxomes. I suggest using Super-SUme (paid app) to remove Kinguser and install SuperSU. While your device will remain rooted there is a better understand of how SuperSU operates on this device.
Guessing you are on FireOS v4.5.5.1 and looking to update to FireOS v5. Correct?
I am on 4.5.3 I downloaded and paid for Super-SUme doesn't seem to run on my Kindle for some reason. I have a sneaky suspicion that permissions may have gotten messed up on whatever folder recovery image goes to
Davey126 said:
This seems to be an artifact of rooting with Kingroot. Not enough information (yet) to understand what happens. I assume you took no steps to manually block OTA updates.
Updating a rooted device, especially Fires, carries an increased risk of bad outxomes. I suggest using Super-SUme (paid app) to remove Kinguser and install SuperSU. While your device will remain rooted there is a better understand of how SuperSU operates on this device.
Guessing you are on FireOS v4.5.5.1 and looking to update to FireOS v5. Correct?
Click to expand...
Click to collapse
bnbliss said:
I am on 4.5.3 I downloaded and paid for Super-SUme doesn't seem to run on my Kindle for some reason. I have a sneaky suspicion that permissions may have gotten messed up on whatever folder recovery image goes to
Click to expand...
Click to collapse
Probably too late now but you can usually snag a refund on Super-SUme within a couple hours of purchase. Small potatoes in the grand scheme of a misbehaving Saturn.
Do you have an in-warranty return/exchange option? Messing with FireOS permissions is above my pay grade on this device given limited recovery options should something go wrong.
Recovery lives in a dedicated partition that is risky to modify, not to mention finding the correct image for this device. You can't just drop in anything (eg: cw/twrp). It must be a signed Amazon image appropriate for this device.
Davey126 said:
Probably too late now but you can usually snag a refund on Super-SUme within a couple hours of purchase. Small potatoes in the grand scheme of a misbehaving Saturn.
Do you have an in-warranty return/exchange option? Messing with FireOS permissions is above my pay grade on this device given limited recovery options should something go wrong.
Recovery lives in a dedicated partition that is risky to modify, not to mention finding the correct image for this device. You can't just drop in anything (eg: cw/twrp). It must be a signed Amazon image appropriate for this device.
Click to expand...
Click to collapse
Thanks for reaching out with your suggestions. For now it looks like I'm stuck on 4.5.3 and can't upgrade or restore.
bnbliss said:
Thanks for reaching out with your suggestions. For now it looks like I'm stuck on 4.5.3 and can't upgrade or restore.
Click to expand...
Click to collapse
Given the device is rooted check to make sure the app overseeing OTA updates has not been renamed; see here for details.
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.
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.