Related
I need to know more about ADB I guess, like how to get it to stay open when I double click the app if thats even how I open it. Instead the window keeps closing as soon as it opens.
My friend (the one who owns this forum account) just downgraded my G1 from RC33 to 29 and now its asking me to sign in but I can't. Apparently my girlfriend can't either on her phone and we didn't do anything with hers but I just signed her in through wifi since it wasn't on the setup screen like mine was. I on the otherhand am stuck at the beginning and need a way to get around it, I don't know why we lost the data plan we had all of a sudden but I'm not going to bother with that and instead will keep moving forward with an alternative.
I'm completely noob to all things command promp so I don't know what an SDK is, just found out what the ADB is and dled that and the drivers but can't start anything up as of yet. I know my android is at RC29 because of the reboot test on the how to bypass the registration thread.
EDIT: Lmfao I guess I picked a bad time to modify my G1, at the time of this post there is a global outage of T-mobile's internet, everything west of the mississippi river is out so thats why I couldn't sign in before, if this thread gets locked or ignored then its ok, I can just wait it out, but just goes to show murphy's law is the real deal, the day I decide to finally start editing stuff this happens.
I'm not really an expert and I had to learn as I went, but here's how I went through the same problem.
Basically, you don't run ADB as a normal program, you open a command prompt (for vista and xp go to run and type cmd) and then you have to navigate to the folder that ADB is in, so if you have the SDK on your desktop youd type something like
"cd c:\users\yourusername\desktop\SDK\tools" (for vista)
yours will probably differ, but use "cd" to navigate to the folder ADB is in. Then assuming you have your phone and the drivers setup properly, when you're navigated to that folder you can type commands that start with adb or whatever and they should work.
If that doesn't work then your phone may not be setup properly, in which case you need to follow the steps in the registering without a data plan thread, although I had a sim so I skipped the disabling of the insert sim screen. The rest is fairly simple, assuming you've got past the insert sim screen somehow you need to type on your phone
<enter>setprop persist.service.adb.enable 1<enter>
I did this in the email box of the signup so you can actually see what you've typed because you won't know if it's worked until you actually try it. After that again type
<enter>telnetd<enter>
which will allow you to get root access to the phone temporarily, then we connect to your phone from your computer.
In a command prompt on your computer do what I said up top by navigating to the folder ADB is in (c:\users\yourname\desktop\sdk\tools or whatever depending on which version of windows you're on and where the SDK is) and type
adb shell
this will probably say the daemon is not currently running, start the daemon etc.... this is good. If it then gives you a hash (#) at the start of the line you are now accessing your phone from your computer. If not, type
adb devices
and see if it gives you anything under where it says "List of devices attached" in the command prompt. If not it's not recognising your phone so you need to get it to do that first.
Last step when you have this, on your computer type
am start -a android.intent.action.MAIN -n com.android.settings/.Settings
which should bring up the page on your phone to enable and manage wifi connections... Connect to your wifi like normal, check it says connected on the settings page and press back and you can register over your wifi.
Hope this helps, I'm no pro but this is how I did it and it worked fine.
So this is my first ever Android device, and coming from an iPhone, I must say I like it a lot. I am used to iOS, but it was not a difficult switch.
However, as with iOS, I am looking to tinker with the phone and get the most out of it. The 3 things that intrigue me the most about rooting my Inspire 4G is the updated radio flash, the fixed audio, and the overclocking ability. The phone flies as it is, but I always like to get the most out of my devices.
My biggest handicap, is coming from iOS, I have had it all handed to me on a silver platter. It had its twists and turns, especially on the iPhone 4, but it was basically click and go to jailbreak the device.
Not so easy on my Inspire.
I have read, re-read, and re-re-read all the tutorials I could, and I have downloaded quite a few files, but I stop myself time and time again. I am in fear of turning my phone into a brick.
Anyone care to give me some pointers? I am fairly technologically inclined, but I am also cautious as well when treading on new grounds.
The only pointers I can give you is to set aside about half your day just in case. I've heard of people doing it under an hour and I've heard of people trying to do it all day so it just depends on how everything goes. Try using bubby's method, he did a really god job on bringing all the stuff you need into one exe file. Also, download the Inspire hack kit just in case you get lost on a part. I used both of them when rooting my Inspire. Good luck, if you get lost check out the sticky at the top of the forum. One last tip, go through those 2 threads and read, read, read and read.
P.S. this section is for development.
I promise once your done and get used to the platform, apple ios will seem like a joke .
The hack kit is not hard to follow at all with the included instructions. Set up adb, create gold card, run scripts and follow directions.
It's hard to brick your phone if you follow instructions. You can also return it to stock condition if you choose to. One important step that I recommend is make sure you turn off any antivirus/antimalware program before you download/install/run the program or scripts. Also, follow the suggestions that were given previously.
I recommended the hack kit, over the one click personally. People have been running into a lot of problems using the one click.
Use the hack kit, its easier
Sent from my Inspre 4G using XDA Premium App
So following the hack kit, I successfully created a Gold Card, and began the process of downgrading the ROM. However, when I initialize the "hackerize-ace setup-downgrade" prompt, I get a "The system cannot find the path specified" although I do get the infamous # that is supposed to give me the "go-ahead"
When I try to go ahead and run the prompt "hackerize-ace install-downgrade" I get the pushing rom info, but nothing happens.
I have tried this as the instructions dictate to do with the phone on charge-only and debugging mode on. I disabled fast boot, also tried to re-enable it.
I'm lost...
neurodave said:
So following the hack kit, I successfully created a Gold Card, and began the process of downgrading the ROM. However, when I initialize the "hackerize-ace setup-downgrade" prompt, I get a "The system cannot find the path specified" although I do get the infamous # that is supposed to give me the "go-ahead"
When I try to go ahead and run the prompt "hackerize-ace install-downgrade" I get the pushing rom info, but nothing happens.
I have tried this as the instructions dictate to do with the phone on charge-only and debugging mode on. I disabled fast boot, also tried to re-enable it.
I'm lost...
Click to expand...
Click to collapse
Be patient. It takes a while for the ROM to be pushed to your SD. I didn't think it was working the first time either, but I just let it go and it worked fine.
neurodave said:
So following the hack kit, I successfully created a Gold Card, and began the process of downgrading the ROM. However, when I initialize the "hackerize-ace setup-downgrade" prompt, I get a "The system cannot find the path specified" although I do get the infamous # that is supposed to give me the "go-ahead"
When I try to go ahead and run the prompt "hackerize-ace install-downgrade" I get the pushing rom info, but nothing happens.
I have tried this as the instructions dictate to do with the phone on charge-only and debugging mode on. I disabled fast boot, also tried to re-enable it.
I'm lost...
Click to expand...
Click to collapse
i hope you figured this out already, but an issue i had is that my computer lost connection with my phone after 4-5 commands in cmd. try rebooting your pc. hope that helps!
This has happened to me half a dozen times now. I receive or place a call while the phone is connected to hands-free bluetooth in my car, I switch to 'HTC One X' to carry on the conversation using just the phone, not the bluetooth, and soon after (sometimes as little as 20 seconds or so, sometimes after a few minutes) I discover that I've lost the connection. I take the phone away from my ear to look at it and then realize that, not only have I lost the connection, the phone has turned off completely! At one point, I had a fairly long conversation with my sister (maybe a total of 45 minutes) and during that one phone call, I had to call her back 4 times because the phone kept turning off. Anyways, I already created a thread on HTC's official forums hoping maybe they'll create a fix, but I've always found XDA to be much more helpful in helping me find solutions to issues...
P.S. Couple other things of note: I can't recall this ever occurring when I'm NOT connected to bluetooth, it doesn't happen every time, but often enough that if I ever stop hearing the other side of the phone call, the first thing I assume is that my phone's turned off.
bikeracer4487 said:
I receive or place a call while the phone is connected to hands-free bluetooth in my car, I switch to 'HTC One X' to carry on the conversation using just the phone, not the bluetooth, and soon after (sometimes as little as 20 seconds or so, sometimes after a few minutes) I discover that I've lost the connection. I take the phone away from my ear to look at it and then realize that, not only have I lost the connection, the phone has turned off completely!
Click to expand...
Click to collapse
It's really tough to diagnose problems like this without details. If possible, next time this happens capture a logcat log and attach it to this thread. With a few eyes on it someone may spot the root problem.
Capturing a logcat is a little inconvenient though. If your phone is rooted, try this:
Install "Terminal Emulator" from Google Play: https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
Wait for the problem to occur (call drop and/or device power down during call)
As soon as possible after the problem occurs, launch Terminal Emulator
Enter this command in Terminal Emulator: su (you will probably be prompted for root/superuser access; grant access)
Enter this command in Terminal Emulator: cd /sdcard
Enter this command in Terminal Emulator: logcat -d -v long -f logcat.main.txt
Enter this command in Terminal Emulator: logcat -d -v long -b radio -f logcat.radio.txt
You can now close Terminal Emulator. There will be 2 files, logcat.main.txt and logcat.radio.txt, in the root directory of your SDCard; attach these two files to this thread. Note that you may want to scan them and scrub any personal information first.
Alternately, especially if your device isn't rooted, you can connect the device to your PC and run the "adb" command from your PC. To do this you will need to install the Android SDK. Here is some starter material for using adb via the Android SDK:
Android SDK Download: http://developer.android.com/sdk/index.html
Adb Command: http://developer.android.com/tools/help/adb.html
Logcat Command: http://developer.android.com/tools/debugging/debugging-log.html
How to find the MSL for your Photon Q
chrisngrod posted a tool for getting the MSL from logcat (http://forum.xda-developers.com/showthread.php?p=31765156) but is in the form of a .bat script, which isn't very useful for Mac or Linux users. I'm a decently regular reader, but I guess I've never posted. So sorry that this isn't in the dev section.
I'm assuming a couple things here
You have the android SDK installed, or at least adb available to you
You have a Motorola Photon Q (on Sprint?) plugged into your computer and appropriate drivers installed (if needed--not sure)
USB Debugging is enabled on your device
You know what a terminal is, or at least how to use one
You are in the current directory of adb. If it's in your path, omit the "./"
Make sure your computer sees your phone
Code:
./adb devices
You should see something like
Code:
List of devices attached
T*******Y device
where *'s are numbers. If you don't see any devices, make sure nothing else is interfering (tethering apps on computer, etc)
Now, go to the dialer on your phone, and dial ##DATA#. A menu should pop up, tap on Data Profile, then the three dots at the top right, and finally Edit. Enter 6 random digits, and click Verify.
Now go back to your computer and run this
Code:
./adb logcat -b radio -d | grep "grde"
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Test it out by going back to your phone and typing it in.
This worked for me, and I haven't found anywhere else that talked about doing it for the Photon Q, so please correct any incorrect information.
asinginglamp said:
How to find the MSL for your Photon Q
Now go back to your computer and run this
Code:
./adb logcat -b radio -d
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Click to expand...
Click to collapse
I was able to do this with only the phone and connectbot. Putting in a false code and then looking over logcat for the NV Read 32, Mine was also hanging out with a group of 3s.
KitsunePaws said:
I was able to do this with only the phone and connectbot. Putting in a false code and then looking over logcat for the NV Read 32, Mine was also hanging out with a group of 3s.
Click to expand...
Click to collapse
Nice. I tried doing it with aLogcat, but didn't see anything. Didn't think to try connectBot.
with me it was between the 3's, i copied the msl.bat to the ADB-platform tools folder what i use for compiling-decompiling apk's, and it worked.
This Is Cray
Gojira-r32 said:
with me it was between the 3's, i copied the msl.bat to the ADB-platform tools folder what i use for compiling-decompiling apk's, and it worked.
Click to expand...
Click to collapse
err
i tried this method the only thing i see on the transcript using adb logcat is checksubsidylockpasswrdcomplete<>errorno=RIL_OEM_CDMA_GENERIC_FAILURE..
Like ive tried everything, any suggestions..besides call sprint
batzluminatti said:
err
i tried this method the only thing i see on the transcript using adb logcat is checksubsidylockpasswrdcomplete<>errorno=RIL_OEM_CDMA_GENERIC_FAILURE..
Like ive tried everything, any suggestions..besides call sprint
Click to expand...
Click to collapse
Do you get anything with adb logcat?
???
asinginglamp said:
How to find the MSL for your Photon Q
chrisngrod posted a tool for getting the MSL from logcat (http://forum.xda-developers.com/showthread.php?p=31765156) but is in the form of a .bat script, which isn't very useful for Mac or Linux users. I'm a decently regular reader, but I guess I've never posted. So sorry that this isn't in the dev section.
I'm assuming a couple things here
You have the android SDK installed, or at least adb available to you
You have a Motorola Photon Q (on Sprint?) plugged into your computer and appropriate drivers installed (if needed--not sure)
USB Debugging is enabled on your device
You know what a terminal is, or at least how to use one
You are in the current directory of adb. If it's in your path, omit the "./"
Make sure your computer sees your phone
Code:
./adb devices
You should see something like
Code:
List of devices attached
T*******Y device
where *'s are numbers. If you don't see any devices, make sure nothing else is interfering (tethering apps on computer, etc)
Now, go to the dialer on your phone, and dial ##DATA#. A menu should pop up, tap on Data Profile, then the three dots at the top right, and finally Edit. Enter 6 random digits, and click Verify.
Now go back to your computer and run this
Code:
./adb logcat -b radio -d | grep "grde"
Hopefully you'll only see one line. If there's more than one, look for one that looks like this
Code:
09-21 21:56:38.837 360 360 E RIL-MOTEXT: NV Read 32, length 6, data length 6, grde - 313934333230
The last set of numbers is what we care about. Your MSL is encoded in the even digits (in counting i.e. 2, 4 ,6 ,8 ..). Mine happened to be hidden in some 3's. So this phone's MSL is 194320.
Test it out by going back to your phone and typing it in.
This worked for me, and I haven't found anywhere else that talked about doing it for the Photon Q, so please correct any incorrect information.
Click to expand...
Click to collapse
The first command works..Recognizes dev, then the logcat command works ONLY when i leave off at the -d. When i do the process i see the RI-MOTEXTem Hook header type 0, requestcode 0x2000016...blah blah blah..how do i write the second part of the comand..?
msl
I ran into that error- OEMRequestunlock thingy.... I tried looking through myself with alogcat, but nothing... at the time I thought I fixed it by downgrading the android OS... then the .bat still didn't work... I figured out that that was because of the path statement not including the location of findstr.exe (grep in this linux example) but now I think that maybe the .bat file didn't work originally because of the path statement and I maybe didn't have to downgrade the OS, but if you're straight up doing it by typing the command into terminal and with grep no less and encountering the problem, then I'll bet it was necessary to downgrade the OS.
So what I'm saying is- you probably have to downgrade the Android OS to one that has the MSL in the ril. Also, it might not be showing up in aLogcat because you'd have to tell it to read the radio log (which is what the -radio switch does)
Hope this helps
I made one phone call to Sprint tech support and simply asked for my MSL, and the lady gave it to me. No questions asked.
tl;dr: I managed to soft-brick my Fire HD 10 (7th Gen) by trying to use the KingoRoot APK. I've managed to mostly recover, but it was a pain in the neck.
THE SITUATION: There's a popular thread at the moment showing how to get root access on your Kindle Fire HD 10 (7th Gen). This sounded pretty exciting to me because I had a 5th gen HD 10 that I rooted soon after I got it, and one of the few things I felt was missing from the new toy I bought myself for Christmas was root access.
There was one hitch, though. The root process Bibikalka describes in his tutorial requires you to download, install and run a Windows version of the KingoRoot rooting app. All well and good for the many people out there who have Windows machines, but I am a dedicated Linux and Mac user and don't have access to a Windows computer. Kingo doesn't have a version for those platforms.
It does, however, have a version for Android itself, so I decided what the heck, I can give that a try. Odds are good that if they have a rooting solution for Windows, it's present in the Android version, right?
Right??
THE SETUP: So I removed my SD card for safekeeping (nothing on it but tunes, books and videos) and plugged in my USB cable. I'd done a fair amount of ADB work before so the tablet was already set up for USB debugging and to accept APKs from unknown sources. I successfully installed the KingoRoot APK after downloading it from their site, launched it and sat back to watch what happened.
KingoRoot seemed to progress about like I would have expected, except that it stalled three times, once at 40%, once at 70% and once at 90%. When it hit 90% I waited for a few minutes to see if it would give me any kind of yea-or-nay as to whether the tablet was rooted (it never did), and then went back to the ADB window and opened up an ADB shell session to see if I could figure out what was going on.
Code:
adb shell
[email protected]:/ $ su
[email protected]:/ #
Success! I had a root prompt! I immediately started following some of the steps in the tutorial and contemplating how I was going to accomplish some of the other steps I'd done on other Fires, like replacing Amazon's launcher with my beloved Nova.
After about fifteen minutes, though, I began to wonder why KingoRoot was still showing 90%. Surely it should have finished by now? so I used ADB to reboot the tablet. That's where the fun started, and by "fun" I mean "pain."
THE SINKING FEELING: I rebooted the tablet, watched the Amazon logo come up, followed by the Fire logo. And I watched the Fire logo. And I watched it cycle through its animation for at least five minutes. At the same time I opened another ADB session, and I could still get a root prompt by running the "su" command, and some other onboard commands like "ps" and "du" worked fine, but once I returned to ADB I found that I couldn't install or uninstall APKs, just to use an example. The command would launch but then hang, and I would have to control-C out of it to get back to my Mac shell prompt.
After about fifteen minutes I started getting this sinking feeling that I had just reduced my nice, big, shiny toy to a thin plastic box that did the visual equivalent of screaming its name over and over again.
THE RECOVERY: By this time I was pretty sure I had hosed my tablet, so nothing ventured, nothing gained. I downloaded the latest Fire HD 10 firmware update from Amazon, watching all the while as it continued to cycle through the Fire logo. When the update was downloaded I booted into the recovery menu, sideloaded the update, and watched nervously as the tablet updated, restarted and . . . went right back to cycling through the Fire logo animation. Head, meet desk.
Then, suddenly, the message that my tablet was optimizing its programs! I have never been so happy to see that particular piece of annoying information. About ten minutes later after re-registering the tablet and completing setup I was right back where I had started when I first bought the device. No Google Play Store, no Nova Launcher, no Ticket to Ride or other favorite games, but it was working.
That sudden gust of wind you heard was my exhaling a sigh of relief.
LATHER, RINSE, REPEAT: Now that I had a blank slate, as it were, and knew that I could recover when I needed to, I decided to try the process once again just to make sure I hadn't missed any steps or done something out of sequence. Long story short, I ended up with an unusable tablet again and had to reload the Fire firmware update.
THE TAKEAWAY: I am posting this as a cautionary tale. I was lucky in that all of my music files, videos and downloaded books live on my SD card so all I lost in this process was some time and customization. It could have been much, much worse.
Until someone can document success with it and explain how they did it, please don't try to root your Kindle Fire HD 10 (7th Edition 2017) using the APK version of KingoRoot. Use the desktop version of the software documented elsewhere in the forums. You'll be happier and more likely to succeed.
Best of luck to you!
I am posting this to share my experience with HD8 (7th Gen) OS 5.3.3.0 using KingoRoot APK.
The purpose is to share the experience that : when KingoRoot stuck at 90%, it might take as long as 30 minutes for KingoRoot to finish.
Here is my note from 12-23-2017:
https://root-apk.kingoapp.com
Kingo ROOT APK version v.4.3.4
(1). Un-check “Install recommended app”
(2). Tap “One Click Root” at the bottom of the screen
(3). In 10 seconds, the status indicator reached 90% and stuck there.
(4). After 30 minutes, it finished with tablet screen displaying: ROOT FAILED & Error Code: 0x1323F7
Dan_firehd said:
I am posting this to share my experience with HD8 (7th Gen) OS 5.3.3.0 using KingoRoot APK.
The purpose is to share the experience that : when KingoRoot stuck at 90%, it might take as long as 30 minutes for KingoRoot to finish.
Here is my note from 12-23-2017:
https://root-apk.kingoapp.com
Kingo ROOT APK version v.4.3.4
(1). Un-check “Install recommended app”
(2). Tap “One Click Root” at the bottom of the screen
(3). In 10 seconds, the status indicator reached 90% and stuck there.
(4). After 30 minutes, it finished with tablet screen displaying: ROOT FAILED & Error Code: 0x1323F7
Click to expand...
Click to collapse
I will admit to the possibility that I was impatient.
Let me try it again. I mean, I do have a clean tablet at the moment . . .
NerdFire said:
I will admit to the possibility that I was impatient.
Let me try it again. I mean, I do have a clean tablet at the moment . . .
Click to expand...
Click to collapse
Please do let us know whether you are successful.
Best of luck.
NerdFire said:
tl;dr: I managed to soft-brick my Fire HD 10 (7th Gen) by trying to use the KingoRoot APK. I've managed to mostly recover, but it was a pain in the neck.
THE SITUATION: There's a popular thread at the moment showing how to get root access on your Kindle Fire HD 10 (7th Gen). This sounded pretty exciting to me because I had a 5th gen HD 10 that I rooted soon after I got it, and one of the few things I felt was missing from the new toy I bought myself for Christmas was root access.
There was one hitch, though. The root process Bibikalka describes in his tutorial requires you to download, install and run a Windows version of the KingoRoot rooting app. All well and good for the many people out there who have Windows machines, but I am a dedicated Linux and Mac user and don't have access to a Windows computer. Kingo doesn't have a version for those platforms.
It does, however, have a version for Android itself, so I decided what the heck, I can give that a try. Odds are good that if they have a rooting solution for Windows, it's present in the Android version, right?
Right??
THE SETUP: So I removed my SD card for safekeeping (nothing on it but tunes, books and videos) and plugged in my USB cable. I'd done a fair amount of ADB work before so the tablet was already set up for USB debugging and to accept APKs from unknown sources. I successfully installed the KingoRoot APK after downloading it from their site, launched it and sat back to watch what happened.
KingoRoot seemed to progress about like I would have expected, except that it stalled three times, once at 40%, once at 70% and once at 90%. When it hit 90% I waited for a few minutes to see if it would give me any kind of yea-or-nay as to whether the tablet was rooted (it never did), and then went back to the ADB window and opened up an ADB shell session to see if I could figure out what was going on.
Success! I had a root prompt! I immediately started following some of the steps in the tutorial and contemplating how I was going to accomplish some of the other steps I'd done on other Fires, like replacing Amazon's launcher with my beloved Nova.
After about fifteen minutes, though, I began to wonder why KingoRoot was still showing 90%. Surely it should have finished by now? so I used ADB to reboot the tablet. That's where the fun started, and by "fun" I mean "pain."
THE SINKING FEELING: I rebooted the tablet, watched the Amazon logo come up, followed by the Fire logo. And I watched the Fire logo. And I watched it cycle through its animation for at least five minutes. At the same time I opened another ADB session, and I could still get a root prompt by running the "su" command, and some other onboard commands like "ps" and "du" worked fine, but once I returned to ADB I found that I couldn't install or uninstall APKs, just to use an example. The command would launch but then hang, and I would have to control-C out of it to get back to my Mac shell prompt.
After about fifteen minutes I started getting this sinking feeling that I had just reduced my nice, big, shiny toy to a thin plastic box that did the visual equivalent of screaming its name over and over again.
THE RECOVERY: By this time I was pretty sure I had hosed my tablet, so nothing ventured, nothing gained. I downloaded the latest Fire HD 10 firmware update from Amazon, watching all the while as it continued to cycle through the Fire logo. When the update was downloaded I booted into the recovery menu, sideloaded the update, and watched nervously as the tablet updated, restarted and . . . went right back to cycling through the Fire logo animation. Head, meet desk.
Then, suddenly, the message that my tablet was optimizing its programs! I have never been so happy to see that particular piece of annoying information. About ten minutes later after re-registering the tablet and completing setup I was right back where I had started when I first bought the device. No Google Play Store, no Nova Launcher, no Ticket to Ride or other favorite games, but it was working.
That sudden gust of wind you heard was my exhaling a sigh of relief.
LATHER, RINSE, REPEAT: Now that I had a blank slate, as it were, and knew that I could recover when I needed to, I decided to try the process once again just to make sure I hadn't missed any steps or done something out of sequence. Long story short, I ended up with an unusable tablet again and had to reload the Fire firmware update.
THE TAKEAWAY: I am posting this as a cautionary tale. I was lucky in that all of my music files, videos and downloaded books live on my SD card so all I lost in this process was some time and customization. It could have been much, much worse.
Until someone can document success with it and explain how they did it, please don't try to root your Kindle Fire HD 10 (7th Edition 2017) using the APK version of KingoRoot. Use the desktop version of the software documented elsewhere in the forums. You'll be happier and more likely to succeed.
Best of luck to you!
Click to expand...
Click to collapse
You can easily install kingoroot pc on a virtual box windows vm (freely available from Microsoft for testing IE) and root that way. I too only have a Mac and it works fine.
NerdFire said:
I will admit to the possibility that I was impatient.
Let me try it again. I mean, I do have a clean tablet at the moment . . .
Click to expand...
Click to collapse
Why not do something actually useful with your life (err.. tablet)?
Once you get root prompt in adb (#), start my guide from Step 13.
You may need to figure out the exact name of the Kingoroot app, run the command below and then figure out which app names to feed to "adb uninstall":
Code:
adb pm list packages -3
You can run this command before installing Kingoroot apk, so you have the baseline.
The impact I'd be hoping for is that before Kingoroot finishes, you'd already uninstall it (how is that for a nice twist?). A working 'su' that it leaves behind could be sufficient for SuperSu to install itself, and you'll be in business (without needing a PC to run Kingoroot).
bibikalka said:
Why not do something actually useful with your life (err.. tablet)? .
Click to expand...
Click to collapse
Sure, why not, I mean there's a first time for everything.
bibikalka said:
Once you get root prompt in adb (#), start my guide from Step 13.
You may need to figure out the exact name of the Kingoroot app, run the command below and then figure out which app names to feed to "adb uninstall":
Code:
adb pm list packages -3
You can run this command before installing Kingoroot apk, so you have the baseline.
The impact I'd be hoping for is that before Kingoroot finishes, you'd already uninstall it (how is that for a nice twist?). A working 'su' that it leaves behind could be sufficient for SuperSu to install itself, and you'll be in business (without needing a PC to run Kingoroot).
Click to expand...
Click to collapse
That's a nifty command. Maybe it can help me get a handle on what Kingo is doing so I can undo just enough of it to keep it from preventing me from running "adb install" or "adb uninstall" once I've achieved root.
By the way, THANK YOU for posting the tutorial. I hope eventually to get to where either I can use the APK to root my tablet (which I will happily document if I can get it figured out) or use some other workaround like the Windows Virtualbox VM trick.
UPDATE 1-5-2018 1850 UTC: Well, it was worth a try, and this time for whatever reason I managed to obtain root access much faster than I had before. Unfortunately that's still where the process comes to a screeching halt. Step 13 works (I'm able to remount /system as RW instead of RO) but I am still unable to install SuperSU, or run "adb shell pm" or indeed do anything that has to do with package management, including "adb install", "adb uninstall", "adb shell pm" or "ad shell am". Something is still blocking any such processes from completing, whether run from adb or on the tablet itself, which I'm sure is why the tablet never gets past the Fire logo after rebooting.
I'm still investigating but also leaning heavily toward just running the process from a Windows Virtualbox once I gather all the pieces I'll need, like a Windows version of ADB.
Blaiser47 said:
You can easily install kingoroot pc on a virtual box windows vm (freely available from Microsoft for testing IE) and root that way. I too only have a Mac and it works fine.
Click to expand...
Click to collapse
Easy?? Ha-ha, it is to laugh. I've been fighting with my virtualbox setup all morning and can't get it to recognize the Fire as anything other than an MTP device.
I'm sure it's a driver issue. Should I be using driver files other than the ones that came with the standalone ADB in the OP? And if so, what files do I need?
NerdFire said:
...
By the way, THANK YOU for posting the tutorial. I hope eventually to get to where either I can use the APK to root my tablet (which I will happily document if I can get it figured out) or use some other workaround like the Windows Virtualbox VM trick.
Click to expand...
Click to collapse
No problem! I hope you can use it at some point !
NerdFire said:
UPDATE 1-5-2018 1850 UTC: Well, it was worth a try, and this time for whatever reason I managed to obtain root access much faster than I had before. Unfortunately that's still where the process comes to a screeching halt. Step 13 works (I'm able to remount /system as RW instead of RO) but I am still unable to install SuperSU, or run "adb shell pm" or indeed do anything that has to do with package management, including "adb install", "adb uninstall", "adb shell pm" or "ad shell am". Something is still blocking any such processes from completing, whether run from adb or on the tablet itself, which I'm sure is why the tablet never gets past the Fire logo after rebooting.
I'm still investigating but also leaning heavily toward just running the process from a Windows Virtualbox once I gather all the pieces I'll need, like a Windows version of ADB.
Click to expand...
Click to collapse
Good test! I remember now rooting something else with Kingroot apk, and it'd have similar unpleasant behavior, I think I ended up having to do a factory reset to get rid of it. I guess Kingoroot apk hangs the package manager, and then it's all downhill from there. If one could hunt down the corresponding process, there could be a way to kill Kingoroot. But who knows ...
NerdFire said:
Easy?? Ha-ha, it is to laugh. I've been fighting with my virtualbox setup all morning and can't get it to recognize the Fire as anything other than an MTP device.
I'm sure it's a driver issue. Should I be using driver files other than the ones that came with the standalone ADB in the OP? And if so, what files do I need?
Click to expand...
Click to collapse
Yes. I can't remember exactly where but there are explicit directions for fire specific drivers. If memory serves me correct it is all on Amazon's website. Try searching there. If you can't find it let me know and I can try to find it again
Edit. Found it quickly. Follow this and see if you can get the to recognize it...
https://developer.amazon.com/docs/fire-tablets/ft-set-up-your-kindle-fire-tablet-for-testing.html
Can you report back the results of VIrtual Box? I am a Mac user too
I had gone the same process and soft bricked the tablet.
Updated 31 May 2020
I had done the adb sideload process and successfully solve the issue.
Yikes!
I just did the same thing on my device HD 10 7th Gen.
It will not bootup and my head is spinning around around as all I wanted to do was install lineageOS.
Can you please tell me exactly what I would need to sideload to get this device back up and running. I am using a Mac to do adb commands. My device is not rooted, I have no twrp recovery, I cannot boot up to the desktop.
Thank you friend