Database Develop

[Q] 7.3.1 auto installed, I lost root, having other issues...help

I was rooted on 7.3.0 from the day I got my replacement kfhd less than a month ago. I forgot to turn off automatic updates and yesterday 7.3.1 installed and immediately I'm having problems. Some apps I had installed are gone, like No Lock and Apex Launcher (I'm almost positive that's which one I was using) for starters. I tried to reinstall No Lock since I have Nova Launcher working and I'm sick of unlocking twice. Downloaded No Lock, went into ES File Explorer to move it, and there is NOTHING in /data/app to move.
I'm almost afraid to see what other problems there are. I downloaded a root checker and it says I'm not rooted anymore. Well that explains a lot. However Google Play has hung around problem free, which you did need root for.
How should I proceed? I fried my fiancee's kfhd a month ago after I rooted it. I was attempting to install TWRP, screwed up, and bricked it. She went out and bought another tablet. I called Amazon and told them it just died for no reason so they sent a replacement which became mine. If I brick another kfhd I don't think Amazon is going to want to replace it again.
I know 7.3.1 was just sent OTA and not to everyone a few days ago (found that info on the forum somewhere) so has anyone re-rooted after getting it? What other things can I safely try?

It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.

MightyBraeburn said:
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
Click to expand...
Click to collapse
Rooting it again would probably work from what I know about rooting phones. I'm kinda hoping someone else has already done it so I know for certain that it's gonna work before I do it.
Maybe I have to be the person who finds out if simply rooting again fixes the issue.

Rooting again should fix the problem. I would try that first.
Worst case scenario it doesn't help and you have to do a factory restore or re-flash in which case you can simply restore a clean copy and then either disable the OTA updates or else, better yet, let it update all the way to 7.2.3 and then root the latest version.

Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.

SGoatS said:
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
Click to expand...
Click to collapse
It's not hard as long as you follow the instructions... It works flawlessly on mine.

Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
-a- said:
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Click to expand...
Click to collapse
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.

SGoatS said:
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
Click to expand...
Click to collapse
You're welcome.
Sent From my Kindle Fire HD running CM10.1

If phone doesn't boot...

Well, I was browsing around the market and my n5 just abruptly shut itself off. It hasn't been able to turn back on since. I've tried every key/charge/magic trick in the book so its DEAD!
Happy to jump in the RMA line at this point but was wondering if any others can confirm DEAD devices. The RMA thread is kinda full of nitpick issues but a dead device is a dead device.
This was the only discussion chain I could find on the issue but maybe someone from google will comment on dead devices. lol
https://productforums.google.com/forum/#!msg/nexus/lI6A3fA8bvw/d3eQlqEqabEJ
EDIT:
so it appears holding down both volume buttons + power while it's plugged in to the charger (not USB to PC) will temporarily boot the phone. You can then do a restore to stock and issue gets fixed. :good:

Damn. That blows.
Sent from the jaws of my Hammerhead!

mrro82 said:
Damn. That blows.
Click to expand...
Click to collapse
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Since I was able to get it booted tethered to the power I'm going to have it drain the battery to dead and see if it resets itself or something. Maybe a bad idea but I guess I don't care at this point it's already RMAd and I don't know what else to try. lol

Zenoran said:
Ya I got an RMA setup but I've been tryin to turn it on ever since. I managed to figure out it will turn on ONLY when it's plugged in and holding down BOTH volume buttons and power. It will bring up the bootloader and from there I can go into recovery, START (os) but reboot options freeze it again. It's really weird, it won't start by doing the same procedure without the power plugged in. It's like it doesn't want to boot on its own cuz it thinks it's dead? Funny thing is the battery says 100%+ in TWRP.
Click to expand...
Click to collapse
Do you have a backup you can attempt to restore?

Have you tried to adb into it?

Delete damn it

I would never install twrp.

There is a stock rom in here somewhere. Flash it boot loader and see what happens.

Synyster06Gates said:
Do you have a backup you can attempt to restore?
Click to expand...
Click to collapse
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.

Zenoran said:
Ya I restored backed up stock but its same boot issue. Factory reset = same issue. I will try full restore from stock to see if that does anything.
Click to expand...
Click to collapse
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701

caribouxda said:
I would never install twrp.
Click to expand...
Click to collapse
Why wouldn't you? In situations like this, it is extremely helpful. Do you expect him to install CWM or something? From my understanding, at least when I first got my phone and flash a custom recovery, CWM wasn't booting. If you are here to try and press your opinion on which custom recovery you prefer, go to their official thread.
Sent from my Nexus 5 using XDA Premium 4 mobile app

floxrin said:
hope you figured it out til now.
if not, maybe you should just flash the factory image and see how it goes:
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.

Zenoran said:
Yep all good now. No explanation to why this happened but recreating the fs and flashing stock seems to have resolved the issue.
Click to expand...
Click to collapse
That's good to hear man. I couldn't imagine how I'd feel if that happened to me. Thankfully XDA us the place that it is and the members, for the most part, have the ability to help us troubleshoot most of our issues.
Sent from my Nexus 5 using XDA Premium 4 mobile app

[Q] Installing 2nd Bootloader led to Kindle not turning on

Hello,
I recently asked about how to root the kindle fire hd 7 (2nd generation), which I got to work. I was able to root it and start messing around with it.
I wanted to flash a rom onto my kindle, but after following the steps on this tutorial: http://forum.xda-developers.com/showthread.php?t=2128848
the thread said if everything was followed correctly, then you wouldn't have a problem. I did follow everything as far as I know, but when I waited for the reboot part of installing the bootloader and stuff, it simply stayed black.
I have tried turning it on and charging it and other things, and it just doesn't come on. I figured I could reinstall the partition back to FireOS, but I can't even get to fastboot in the first place unless it's able to turn on.
Any help with this?

You probably hard bricked it, the 2013 models can't have twrp+2nd bootloader on them, the exploit isn't compatible, so if you downgraded the bootloader to one from the previous generation's kindles, then you hard bricked it.
Sent from my Amazon Kindle Fire HD using Tapatalk

Is there no recoverable form of hard-brick?

XboxOmac said:
Is there no recoverable form of hard-brick?
Click to expand...
Click to collapse
I don't think we have the process completed yet, but more or less it involves soldering a sdcard reader to the kindles emmc contact points on the motherboard, i think someone was mapping them out but hasnt mapped them all out yet. The process to map them out involves taking the emmc off the kindle so not too many people are into doing it. But the actual fix is not that complicated, you just have to be decent with a soldering iron, and flash the original bootloader from a linux os like ubuntu. It's been done on the kf2 and hd 8.9" models.

[FIXED] Baffled about shutdown

I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
EDIT:
Not sure what the exact issue was, but I downloaded the Droid Turbo OEM from HERE. Waited 8 hours to download (original links don't work anymore and the mirror is stupid and charges for a fast download), unzipped the file, then ran the VRZ_XT1254_SU4TL-44_44_CFC.bat and it booted right up and has been working fine. I then simply installed TWRP, flashed SuperSU, then edited the build.prop to get hotspot working.

flametail2518 said:
I have a Sunshine unlocked Turbo that has recently began randomly shutting down. I have tried a few roms to see if there was any difference, but couldn't get anything to work. I also tried installing a stock, unmodified rom to no avail (kept getting an error on the install). I could get CM12.1 installed the best, but after a couple of minutes it would shut down again. I tried wiping everything off the phone through TWRP (system, cache, dalvik, and internal storage) to no avail. I was able to get it to run longer on CM without GAPPS, about 10 minutes or so before the shutdown. Any ideas?
Click to expand...
Click to collapse
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.

TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.

GreaterLesser said:
Mine just shuts off around 13~17% percent battery without warning. Not sure why though.
Click to expand...
Click to collapse
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.

TheSt33v said:
It's a long shot, but you might want to try a battery calibration app. You phone could be reading 13-17% when it's actually at 0%. I think it's more likely that it's some sort of hardware issue, though.
Click to expand...
Click to collapse
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.

GreaterLesser said:
Even though the percentage aforementioned is read from the bootloader? I get this percentage when my phone is off and I plug in the changer it read the battery is charged to 13~17%.
Click to expand...
Click to collapse
Honestly, I have no idea.

I agree yes try recalibrating the battery. Or do a clean flash. It should recalibrate the battery when you do this.
The calibration is simply a file based on battery reads.

TheSt33v said:
When it shuts down, does it immediately power off, or do you see the "shutting down" message?
If I were you, I would try using the Verizon Upgrade Assistant to repair the phone. It won't affect your unlocked bootloader, and it will ensure that all the software on your phone is stock.
Click to expand...
Click to collapse
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.

flametail2518 said:
It is immediately shutting down without a warning.
I'll try the VUA tomorrow and see how that goes. Hopefully a fresh, OEM install will fix the issue so I can get CM12 installed.
Click to expand...
Click to collapse
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.

My phone likes to shut down around 1-8% without warning, but it does say Powering down as it does it. It's kind of annoying, but I'm sure that's not similar to what you're experiencing.

TheSt33v said:
Hmm. That sounds like a hardware issue to me, but you'll find out once you run the upgrade assistant.
I had a problem once where the phone seemed like it was powering off, but it was actually just never waking up when the screen went dark. Reflashing all images didn't help. I ended up sending it in to Motorola for a warranty replacement, which was a surprisingly easy process.
Click to expand...
Click to collapse
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.

flametail2518 said:
I can't get VUA or the Repair Assistant to even recognize the device. Are there any guides to flashing the stock firmware? I can't seem to find one online and it's a bit of a pain. I'm glad I have a N5X to use instead.
Click to expand...
Click to collapse
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.

TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
See previous post. I got it fixed today.
Sent from my SHIELD Tablet using Tapatalk

TheSt33v said:
If you have a Nexus 5X, I'm assuming you know how to use fastboot.
1. Download this: http://www.rootjunkysdl.com/getdown...o/Firmware/VRZ_XT1254_SU4TL-44_44_CFC.xml.zip
2. Extract it somewhere.
3. Right click on the .bat file and select edit.
4. Find the entry for Quark.
5. Boot into bootloader mode and connect to PC.
6. Use the commands listed in the Quark section to flash the images.
Click to expand...
Click to collapse
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.

flametail2518 said:
If I just double click the .bat it automatically flashes everything. Is that the wrong way? There's no "entry for Quark" in the .bat.
It worked for about 48 hours this time before it did another shutdown.
Click to expand...
Click to collapse
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.

TheSt33v said:
Sorry, I missed a step. Yes, double clicking on the .bat file should work fine. I got confused. If doing that didn't fix it, you might want to think about getting a warranty replacement if possible, or a new phone. Motorola has an option where you pay $25 and they ship you a new phone without inspecting the old one. It even comes in the original packaging, which makes me suspect that it's actually new, not refurbished. This is the option I chose when I replaced the phone that I had modified with Moforoot. The process went smoothly despite my "modified" system status.
Click to expand...
Click to collapse
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk

flametail2518 said:
I'll have to try that. I dropped my VZW insurance when I got the N5X since Nexus Protect is better and cheaper than VZW. Do I just go through Motorola's site for it?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.

TheSt33v said:
Here you go: https://motorola-global-portal.custhelp.com/app/mcp/service/session/
Click on "request a repair" and follow the prompts. You won't even have to interact with a person.
One caveat though: I read recently that someone tried to do this and they tried to give him a Droid Turbo 2 as a replacement. I'm not saying that will happen, but it's something to be aware of.
Click to expand...
Click to collapse
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.

flametail2518 said:
Thanks for this! It was covered and I can get it done for free since I don't need my Turbo.
Click to expand...
Click to collapse
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!

TheSt33v said:
I avoided the free option since I got the impression that they inspect your phone first to ensure that nothing is wrong with it that would make its warranty void. Like, say, an unlocked bootloader. But it could be that they just check for physical damage. I dunno. Good luck!
Click to expand...
Click to collapse
The free option said they look for physical damage first then go on to the repair.

Recovering Amazon Fire with only Fasboot? Help!

So long story short, I was messing with my Fire after it sitting for a few months, trying to put Xposed Modules on it, I ended up flashing a bad custom recovery. Now, I am stuck with a bootloop and no recovery whatsoever. If I hold Vol Down + Power, all I get is the fire logo, but nothing with it. It will sit for hours. Only thing I can get into is fastboot, but I'm not sure where to go from there. Any help would be great! It should still be rooted, since I haven't modified any of that. I was running Slim LP rom from December. So I'm on old FW. Thanks for any help ya'll can provide.

camistotle said:
So long story short, I was messing with my Fire after it sitting for a few months, trying to put Xposed Modules on it, I ended up flashing a bad custom recovery. Now, I am stuck with a bootloop and no recovery whatsoever. If I hold Vol Down + Power, all I get is the fire logo, but nothing with it. It will sit for hours. Only thing I can get into is fastboot, but I'm not sure where to go from there. Any help would be great! It should still be rooted, since I haven't modified any of that. I was running Slim LP rom from December. So I'm on old FW. Thanks for any help ya'll can provide.
Click to expand...
Click to collapse
At preaent there is no reasonable recovery from this condition unless your bootloader is 5.0.1 (which permits booting twrp).

Davey126 said:
At preaent there is no reasonable recovery from this condition unless your bootloader is 5.0.1 (which permits booting twrp).
Click to expand...
Click to collapse
I may be possible that I am.. I can't remember. Got the link to it? I'll give it a shot. Not like I can do much more harm. Thanks.

camistotle said:
I may be possible that I am.. I can't remember. Got the link to it? I'll give it a shot. Not like I can do much more harm. Thanks.
Click to expand...
Click to collapse
This thread should prove helpful (obtaining and booting twrp image):
http://forum.xda-developers.com/amazon-fire/orig-development/twrp-recovery-t3242548/page1