Hi, this is my first post so don't be surprised if I don't ask the right questions/give the right information
Long story longer than needed, I rooted my Fire HD 6. Then I factory reset it, and my root access was gone. So I kept trying to get Kingroot, the app I used, to get me root access, but it couldn't really decide if I had root or not. What I mean by that is sometimes it would go to the Kingroot homepage but then say that root access was gone, and when I tried to root it again with Kingroot, it would always fail. So I brought in another app, Kingoroot or Kingaroot I think it was called, and it worked! But when I opened an app I use, Lucky Patcher, it said that something went wrong and the device needed to reboot. I did it and from then on it has been stuck in a bootloop, but I can get into recovery mode, but I can't get my PC to recognize it. That's not entirely true, it will recognize it in ADB, but instead of the device name it has a bunch of numbers and says the device is unauthorized.
I've tried everything I can think of, looked around online a lot, but nothing has seemed to work, so if anyone can help, greatly appreciated.
I am running stock Fire OS version 5.1.2
Related
Hey guys, first off, I got a new Kindle Fire HDX 8.9 from BestBuy yesterday and of course I had to mess with it. I do it to every new tech I buy haha.
Well, stupidly I didn't realize there was a recovery option for the 8.9 just yet, so I went ahead and rooted my Kindle Fire and attempted to install the GAPPS and remove the signature verification inside the Kindle Fire. This all went okay but then I noticed I could no longer download files from the Amazon store nor did the Google Play store work for me. So I attempted to reset the Kindle back to factory settings thinking it would just wipe it all and I could start anew. I removed root access through SU and all that before resetting it to it's default settings.
After it finished, I realized it didn't get rid of the Google play store or any of the apps and I still couldn't download any files from the Amazon store. So I used ADB to install some files like ES File Explorer, SU, Busybox, etc.
After all that I noticed something was wrong with my Root access, I couldn't fully use any of the applications that required Super User. I couldn't modify the build.prop to attempt at resetting the Kindle Fire to it's full stock form, so instead I modified it on my computer, then pushed it through to ES.
After I had it on ES I deleted the original Build.prop, saving a back-up of course, and then putting in the new one. Low and behold, after doing this, I reset my Kindle and now I'm stuck at a gray Kindle Fire screen for about 10 or so seconds then it just goes black with the light still coming through. I can boot into recovery mode, but only have two options, to reset to factory, or reboot.
I did reset it to factory here, thinking it would do some good, but nothing came out of it. Either way, ADB didn't recognize my device, even before I reset it to factory settings via recovery mode.
So I'm at a loss now. I can't get ADB to recognize my device and I have no idea how to get it to. Any help on this matter is greatly appreciated.
I am running Windows 7 64-bit right now and am in the process to dual booting Ubuntu in an attempt to see if I can get it to find my device. I am new to Linux so I'm not sure how that will go.
Amazon, being the amazing company they are, is sending me a replacement, but I would like to get this one to work so they don't have to fork out another Kindle for my stupid mistake. Again, any help or information on what I can do to proceed from here would be amazing.
Thank you for taking the time to read this and look forward to some responses!
Fataldelay said:
Hey guys, first off, I got a new Kindle Fire HDX 8.9 from BestBuy yesterday and of course I had to mess with it. I do it to every new tech I buy haha.
Well, stupidly I didn't realize there was a recovery option for the 8.9 just yet, so I went ahead and rooted my Kindle Fire and attempted to install the GAPPS and remove the signature verification inside the Kindle Fire. This all went okay but then I noticed I could no longer download files from the Amazon store nor did the Google Play store work for me. So I attempted to reset the Kindle back to factory settings thinking it would just wipe it all and I could start anew. I removed root access through SU and all that before resetting it to it's default settings.
After it finished, I realized it didn't get rid of the Google play store or any of the apps and I still couldn't download any files from the Amazon store. So I used ADB to install some files like ES File Explorer, SU, Busybox, etc.
After all that I noticed something was wrong with my Root access, I couldn't fully use any of the applications that required Super User. I couldn't modify the build.prop to attempt at resetting the Kindle Fire to it's full stock form, so instead I modified it on my computer, then pushed it through to ES.
After I had it on ES I deleted the original Build.prop, saving a back-up of course, and then putting in the new one. Low and behold, after doing this, I reset my Kindle and now I'm stuck at a gray Kindle Fire screen for about 10 or so seconds then it just goes black with the light still coming through. I can boot into recovery mode, but only have two options, to reset to factory, or reboot.
I did reset it to factory here, thinking it would do some good, but nothing came out of it. Either way, ADB didn't recognize my device, even before I reset it to factory settings via recovery mode.
So I'm at a loss now. I can't get ADB to recognize my device and I have no idea how to get it to. Any help on this matter is greatly appreciated.
I am running Windows 7 64-bit right now and am in the process to dual booting Ubuntu in an attempt to see if I can get it to find my device. I am new to Linux so I'm not sure how that will go.
Amazon, being the amazing company they are, is sending me a replacement, but I would like to get this one to work so they don't have to fork out another Kindle for my stupid mistake. Again, any help or information on what I can do to proceed from here would be amazing.
Thank you for taking the time to read this and look forward to some responses!
Click to expand...
Click to collapse
I think you can contact Amazon, asking them How to get into the fastboot mode or ADB mode, the stock recovery mode can do nothing good. I think the only way to fix it is via ADB mode.
I need help rooting this tablet that I got for my birthday in march.
I've tried alot of places, towelroot, kingo, almost everything but no success.
It runs android 4.4.2 jellybean and the model (as i placed in tittle) is a DP7856K
Hello XDA. I've been a long time reader of these forums and would now like to learn how to root. I have a dp7856k tablet purchased from walmart and would like to start with this before trying to root my LG G Vista. I have not found anything regarding this tablet and I hope y'all can help. Thanks in advance!
Sent from my DP7856K using XDA Free mobile app
I was able to root my DP7856K with Kingo Root, although now every reboot results in a near factory reset, root remains intact, but data and apps are wiped, signing into google starts the download process. What I've read so far is that the location of busybox is/may be wrong.
ButtersCast said:
I need help rooting this tablet that I got for my birthday in march.
I've tried alot of places, towelroot, kingo, almost everything but no success.
It runs android 4.4.2 jellybean and the model (as i placed in tittle) is a DP7856K
Click to expand...
Click to collapse
Don't know if you're still having problems or not, but the Kingo apk worked for me, although proceed at your own risk, rooting my DP7856K resulted in a factory reset with every reboot, even after moving busy box to /system/bin from /system/xbin as suggested by this forum. I've been forced to keep it on and charged up, or reload everything if the battery gives out unexpectedly.
Hi everyone,
i have a rooted Kindle Fire HDX 7" which is kind of softbricked. Maybe even hardbricked but my knowledge doesnt reach that far to determine.
Here's the thing. I already got in touch with Amazon, they checked my Amazon Account and were pleased to send me a new Kindle since i still got warranty on it.
Okay so far so good.
But here comes the real deal.
I'm pretty sure my warranty doesnt really cover the whole root -> brick story.
I told the Lady that after a factory reset the Tablet keeps trying to start the Setup over and over again. Which is indeed the case. I did not mention anything else.
So. My plan was, since i'm still able to go into safestrap recovery, to delete everything that could point out that the Tablet was rooted. Atleast on the first view.
TL.DR:
Is it possible to delete Safestrap/TWRP via the Terminal Command?
I know you can browse through the Tablet, but i couldnt find where the Folders are located.
Even if the Tablet doesnt Boot at all after deletion, i wouldnt mind.
Cause then i could still keep my new Tablet and hope they cant find anything on the broken one.
Hope anyone can help me.
If it is hard to understand what i meant i can give you further informations.
It's kind a hard for me to describe such technical things in a foreign language.
If you can access safestap, you can unbrick your device mate.
Well i kind of tried everything possible.
It's not on topic but i can describe what i did, maybe it helps other to not do the same mistake.
I had my Kindle rooted on 13.3.2.4 with the HDX Toolkit.
Everything worked fine since one day the Google Store stopped working.
Well at that time i wasnt using the Tablet on a daily basis so i didnt mind much and got a little off touch with the whole rooting thing, and the do's and dont's.
Then after a couple of weeks i got a bit frustrated over the fact that the integrated Prime Video Streaming is so out of date, that you cant even watch movies USK18 or switch languages within the Movie.
So i decided to use the Kindle as it was meant to by amazon and remove everything.
I really shouldve read more about the prodecure, i know that now.
But here's what i did:
1. Wiped and Removed my non-StockROM
2. Booted on StockROM and did a Factory Reset
3. Sh#t got weird so i went into recovery and wiped the StockROM aswell
4. Now i can still go into Recovery, but when i try to Boot i kind of dont have a FIrmware installed. It trys to re-do the Setup where you have to choose ur language over and over again.
So by now i already know what i should've done instead.
But at this point; my Kindle doesnt get recognized by my PC nor by ADB.
And i dont know what i can do with the Safestrap Recovery at the beginning.
So far, any more ideas?
Should i still try to unbrick it or just wipe my fingerprints off of it and hope i can keep the new one.
KDroidB said:
Well i kind of tried everything possible.
It's not on topic but i can describe what i did, maybe it helps other to not do the same mistake.
I had my Kindle rooted on 13.3.2.4 with the HDX Toolkit.
Everything worked fine since one day the Google Store stopped working.
Well at that time i wasnt using the Tablet on a daily basis so i didnt mind much and got a little off touch with the whole rooting thing, and the do's and dont's.
Then after a couple of weeks i got a bit frustrated over the fact that the integrated Prime Video Streaming is so out of date, that you cant even watch movies USK18 or switch languages within the Movie.
So i decided to use the Kindle as it was meant to by amazon and remove everything.
I really shouldve read more about the prodecure, i know that now.
But here's what i did:
1. Wiped and Removed my non-StockROM
2. Booted on StockROM and did a Factory Reset
3. Sh#t got weird so i went into recovery and wiped the StockROM aswell
4. Now i can still go into Recovery, but when i try to Boot i kind of dont have a FIrmware installed. It trys to re-do the Setup where you have to choose ur language over and over again.
So by now i already know what i should've done instead.
But at this point; my Kindle doesnt get recognized by my PC nor by ADB.
And i dont know what i can do with the Safestrap Recovery at the beginning.
So far, any more ideas?
Should i still try to unbrick it or just wipe my fingerprints off of it and hope i can keep the new one.
Click to expand...
Click to collapse
So you can open safestap ? If you can, then try ADB on a Linux/Mac machine. It will work. Windows has a problem with the drivers. Also I am not sure about this, but if you access the stock kindle recovery and do a factory reset from there, you might wipe safestap.
Well, I just got this phone this week. It was actually a gift in fact since I broke my last phone a week before this.
As soon as I got used to the new phone. I started playing with it's guts. I rooted it with Kingroot, since it has never failed me before. Installed Xposed Framework, and flashed the 5.1.1 stuff for it to run. I had to flash TWRP to flash the Xposed Framework stuff (for some reason I couldn't get the sideload to work). Got a few modules for it. Got all my usual apps such as Facebook, ES FM, Instagram, etc. Got a few games. Spent some hours playing the games. You know, all the stuff you do when you get a new phone.
Then, I decided it was time to switch from Kingroot to SuperSU, as I do with every phone I root with Kingroot (and there were a few). I did it the same way as I have before, using w0lfdroid's method (I can't post links yet). The Kingroot app didn't automatically uninstall, but SuperSU was working. So, I uninstalled Kingroot manually with ES FM. That caused a lot of "unfortunately, com.kingroot.kinguser has stopped" dialogs that never stopped coming, and I decided a reboot might fix it.
I was wrong, the reboot did NOT fix it. It turns on, goes to the LG logo screen, goes to the Metro PCS screen, dims the background, [all of that within a minute and then] vibrates once, and then no sign of anything else. However, the phone does seem to be alive. When I plug it into USB the MTP starts working. It's also listed in adb's devices list. I can even use adb. I used adb to boot it into bootloader/fastboot, and it's even listed in fastboot's devices. It does still charge.
That damned Kingroot, I'll never use it again to shortcut through rooting. It has always worked, and I've been able to swap it with SuperSU everytime before this one. I just don't want to risk this happening again.
I'm lost on what I should do about this. What would you fella's do?
_____________________
I do have a warranty on it, but I've obviously voided that above. I could lock the bootloader back with fastboot (using "fastboot oem lock") so they don't see anything significant right away, but they could always dig in to see that I've done a lot of changing. Hell, all they would have to do is boot into recovery and see TWRP... xD
Well, I just locked it back ("fastboot oem lock" ) and I think my phone is actually coming back on, it's currently on the "Android is starting" screen optimizing app 12 of 151.
I'm just hoping the lock command doesn't reset my device like the unlock command obviously does... I guess I'll edit this with my results in like an hour when this is done (not literally an hour)!
EDIT 1: 10 minutes later, it seems to be stuck on "Starting apps." after it finished optimizing.
EDIT 2: 10 more minutes later, I'm pretty sure it was indeed frozen on "Starting apps.", so I took the battery out. I turned it back on only to see it still freezing on the Metro PCS screen... Well damn.
EDIT 3: Yet another 10 minutes later, still stuck on the Metro PCS screen...
EDIT 4: I no longer have USB debugging access, since I re locked the bootloader (which seems to have reset it, again). So now I also do not have access to fastboot. I think I screwed myself...
unbricking
@ goatitalone can help you unbrick your device. I still have the files if he is OK with it I can help you too or if he can write a tutorial on here that would be great. @ goatitalone?
I have same exact problem howisit fixed?
Magik1 said:
I have same exact problem howisit fixed?
Click to expand...
Click to collapse
do you still have adb? if you do i can send a twrp backup
its been listed kingroot will brick you, currently the oneclick is compatible with our devices. you should have done some searchign before tinkering with your device in my opinion, if youre smart enough to unlock your bootloader .. you should be smarter in researching root methods.
youll have to reflash your device, contact goitalone - as noone that he's helped will help you with getting those files.
as for it being an ms3302 device.. i havent seen that device under our series.
Use this to unbrick http://forum.xda-developers.com/android/development/stock-firmware-rom-unbrick-lg-k7-k330-t-t3432878
I've rooted phones before with no issue. I've had to get a new phone recently.
Phone is an Alcatel Pixi Theatre. Root worked on first try with KingRoot. I go to start to download files to do a custom recovery and my phone randomly restarts and root is gone. This has happened on 2 phones now. I go to KingRoot and root again and it works but I know it will be gone when phone reset.
I know it has something to do with Knox or Bootloader. I've tried getting rid of the bootloader but I cannot get the phone into download mode. The buttons are weird and power up puts me into install, wipe, etc and power down starts the phone.
Phone needs to be rooted to set up custom recovery. Yet, every time I go to set it up I lose my root. Am I missing some steps or something? I'm about to lose my mind. Just trying to get Xposed on my phone. I can't even get SuperSU to show me my apps. Keeps saying binary occupied. Does that need to be downloaded before I root?
Thanks
Can anybody help? thanks
Does the same for me I read that I should use supersume and its supposed to change it from kinguser to superuser but I couldn't get it to work