Help, 5th gen tablet is a little bit bricked! - Fire Q&A, Help & Troubleshooting

Not really bricked, but definitely messed up. It's rooted and running the Nexus ROM, with Apps2sd to put some of the larger apps onto the SD card, and a swap partition added in /cache per @Davey126 advice. As of today, it freezes quickly and I can't open Apps2sd or Kernel Aduitor at all, and SuperSU no longer shows either of them having root permission. Play Store freezes while opening; seems like most apps do the same. Can't open FlashFire. I am able to get into recovery, but not sure what to do from there. Advice?

I set the date way back and FlashFire now tries to open, but gets stuck on "acquiring root access." Walked away for a few minutes while it was trying to do that and came back to find it had either powered down or is asleep and so frozen that I can't wake it up.

mc510 said:
Not really bricked, but definitely messed up. It's rooted and running the Nexus ROM, with Apps2sd to put some of the larger apps onto the SD card, and a swap partition added in /cache per @Davey126 advice. As of today, it freezes quickly and I can't open Apps2sd or Kernel Aduitor at all, and SuperSU no longer shows either of them having root permission. Play Store freezes while opening; seems like most apps do the same. Can't open FlashFire. I am able to get into recovery, but not sure what to do from there. Advice?
Click to expand...
Click to collapse
mc510 said:
I set the date way back and FlashFire now tries to open, but gets stuck on "acquiring root access." Walked away for a few minutes while it was trying to do that and came back to find it had either powered down or is asleep and so frozen that I can't wake it up.
Click to expand...
Click to collapse
Symptoms suggest eMMC (memory) errors which suggest pending failure. If you can access stock recovery try a factory reset. You will loose personal apps/data and (likely) root but not Nexus. If that doesn't work you will need to reload FireOS 5.3.1 and start over assuming device is responsive/stable.

Thanks @Davey126; I’ll try that. Assuming that I can successfully reset Nexus, can I just re-root from there?

mc510 said:
Thanks @Davey126; I’ll try that. Assuming that I can successfully reset Nexus, can I just re-root from there?
Click to expand...
Click to collapse
You *should* be able to re-root although I have seen reports claiming it didn't work. That said, the behavior of your device suggests a pending/progressing hardware failure which is the bigger issue.

Allrighty, that went very well; I even still have root! At the moment the device seems to be working great, even much snappier than before (but perhaps only because I haven't reloaded all of my apps). I'll be prepared for it to act up again, given the chance of failing memory, but for now it's good. Thanks greatly for the help!
This might be a good time for me to start thinking about what new tablet I'll want to purchase as a replacement.

Related

[Q] KFHD (2012) rooted?

Hi Everyone:
I am attempting to root and install cm11 on my son's KFHD. I am a bit of a noob, but I have successfully rooted my nook color in the past and read MANY threads on how to root, but I'm kind of at a loss.
The problem is that I followed the thread on how to root and I had a bunch of trouble. I finally was able to get through the steps, but the command box closed before the KFHD rebooted successfully. In an attempt to "fix" it, I restored the device to factory settings. It seems to be working just fine with stock os, but there is a superuser app which has requested access to apps.
I downloaded an app from Mobile1 to check that there is root access and the app indicates that I do indeed have root access. Should I go ahead and try to install a rom?
I would like to root it because my son is using it for school and is having a hard time adjusting to the stock os. (Which I hate, too).
Thank you so much!!!!
-NDH
1. Super User is the app that lets apps have access to root. (easy way of understanding it)
2. You need to Install Twrp and 2nd bootlander before installing the rom.
go to this video and follow the directions carefully. http://www.youtube.com/watch?v=a1bLCuQN0-U
3.Go to this video to install cm 11 rom for 2012 version. http://www.youtube.com/watch?v=0ODVX_EYaVY
4. once intalled new rom go to settings-about tablet-cyanogenmod updates and then update to latest version. IMPORTANT
thank you
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
ndharvey said:
Thank you for the advice. I appreciate it.
I've run into a new problem today, however. The device powered itself off and won't reboot at all. (It had a full charge). So I am off to do some research on how to fix this problem. UGH.
-NDH
Click to expand...
Click to collapse
Did you flash anything before this happened?
nope
SafinWasi said:
Did you flash anything before this happened?
Click to expand...
Click to collapse
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
ndharvey said:
I didn't flash anything - just tried to root. After several hours of trying lots of fixes and googling like crazy, I was able to get the device to turn on. My WIN7 laptop was not recognizing the KFHD. I tried a different usb port on my laptop and it installed all of teh drivers and recognized the device.
I did go ahead and order a fastboot cable - and I'm glad I did. The day after I got the KFHD working again, it turned itself off again and would not reboot.
I spent several hours today trying to understand fastboot and how to use the cable and a few minutes ago, I was able to restore a system image and get it back to stock. I am waiting for it to charge up a bit and then I'll set it up again. I think it worked because there are no apps or anything installed as of now.
All I really want to do is have access to the Play Store and install an alternate launcher, so it looks and feels comfortable for my kid. He's had the kindle for almost a year, but doesn't feel very comfortable using it and its something he needs to use at school (where I can't help him). Once its charged up, I will re-root - following directions very closely!!!!!
Thanks for your help!
NDH
Click to expand...
Click to collapse
I would recommend you to install a custom ROM like CyanogenMod. Trust me,you'll love it. AOSP is much better than Amazon OS.

Randoom Reboots on Lollipop, multiple ROMs with the same issue

Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
KingBeef said:
Ok, I have been searching for a couple of weeks now but I have not found a soulution. I recently recieved a replacement Note 4. I updated it to Lollipop, then rooted and flashed Rapture.
Ever since, I have been experiencing random reboots and the occasional loss of data. This is not a Rapture problem it appears. I have had the issue with both versions of the Rapture Lollipop builds, DarthStalker, and stock Deodexed COD6. I did not have this problem on my last Note 4 which had the first Rapture build on it.
I have factory reset, I have Odined back to stock and repeated the rooting process, following the guides posted here to the letter and I still have the problem. Any help in resolving this issue is greatly appreciated.
Click to expand...
Click to collapse
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
I have not tried a stock run without third party apps installed. I will try a fresh install of stock COD6 with root and see how that fairs. It normally happens the first time within an hour of flashing so it won't take long to see if it happens I believe.
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Jammol said:
Seeing that it's happening on so many different Roms; it's something you're installing on your device.
Does it happen on a fresh stock rooted COD6 with nothing installed 3rd party?
Click to expand...
Click to collapse
So I tried stock rooted without third party apps installed. Got 2 reboots but no loss of data. Seems like it's something with the device itself or should I try just running without root?
dkb218 said:
I was getting one or two random reboots a day after updating to LP. I noticed most reboots happened after I finish or during use of Google All Access. I have a lot of tracks stored on my SD cards. Once I refreshed the tacks [in all access settings], I haven't has a reboot since.
Click to expand...
Click to collapse
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
KingBeef said:
I wish it was something that simple. The only consistency I am getting in terms of reproducing it is trying to multitasking and possibly having too many apps running in the background, but sometimes it happens with just 2 or 3 apps running so I am not sure.
What's really annoying about it all is the first unit I had ran flawlessly, even after the 5.0 update.
Click to expand...
Click to collapse
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Jammol said:
Does your device get really hot right before it does the random reboots? Could be thermal function of the Note 4. 805SOC is a very hot chip albeit not as bad as the 810 but pretty dang close if you ask me!!! If no heat issues then see below
Give this a try:
This will require you to Odin to COD6 Stock NO ROOT!!!
Shut down and take out your External SDCard.
Boot into TWRP or Flash TWRP if you don't have it on there right now
Do a FULL WIPE: Factory Reset 3x, Advanced Wipe(Everything there) 3x, and finally Format Data(where you have to type yes) 3x
Power off your device and start it up into Download mode and Odin COD6 Stock Firmware(the full one not the partial)
Let it do it's thing and then simply use the device for a few hours on just pure stock.
DO NOT INSERT YOUR SD CARD!!! Why? We want to make sure it isn't something on your card causing Indexing to hang and force reboot.
If you get no reboots then go ahead and shutdown and insert your SDCard and use your device. Still no reboots? Then go ahead and Root. Still no reboots? It's resolved.
This process of elimination is lengthy but it is effective.
Click to expand...
Click to collapse
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
KingBeef said:
I can't say that I have noticed it in the past, however, it froze up shortly after I read the email notification of your response and was quite warm towards the top half. I pulled the battery expecting it to reboot anyway. Is there anyway to mitigate the thermal affect if it is indeed the culprit?
I will try the second method this evening and see if there's any change in behavior and report back sometime tomorrow. Thank you for your assistance with this.
Click to expand...
Click to collapse
Yes but it is not recommended. Using Synapse from the playstore will do such a thing but it requires a custom Kernel. If it is a thermal issue your device may be defective seeing that it's spiking so much so quickly and just crashing.
Definitely give the process of elimination a try that I suggest in my previous post. If it fails at the first step of being pure stock no SDCard then I'm afraid you need a new device.
Hi KingBeef,
Unfortunately, I have the exact same issues you do. Except I've tried literally everything. Even Odin back to stock KitKat. Seems to reboot or randomly shut off if more than 3-4 apps are running at completely random times. No SD card as well to confirm it's not that. The only difference I see with your situation is my phone will degrade after 3rd day of use. First 2 days are flawless, then almost like a failing hard drive, things start to domino progressively worse. My last attempt was to run it only in wifi mode, no SIM card.
The only thing left is to consider unfortunately is swapping again under warranty. I myself am waiting until I go back to the US (Cad user here) to swap with TMo for another handset.
Good luck!
Sent from my D6503 using Tapatalk

Dead Turbo?

So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
When I had my Razr Maxx I had an issue that was similar and nothing I tried would fix it. Factory reset cache wipe flashing different roms nothing. Finally I decided to factory restore it with RSD Lite and after that the problem went away and I was able to do everything again like normal. I don't know why a factory reset wouldn't fix it and that did but it did.
Thanks. That is my next step. Do you know where I can find the RSD image?
Is this what I need? http://forum.xda-developers.com/dro...quark-stock-firmware-moto-maxx-droid-t3063470
Do I need to worry about flashing radios and stuff back to 4.4.4?
Seems to be. Honestly I've used it on many Motorolas in the past but I haven't read much about using RSDlite on the turbo. I would just do some googling around I'm sure you'll find it
my2cents said:
So I was running CF 1.3 base for quite a while with no issues. Two days ago my phone shut down on me and would not boot. I wipe everything multiple times. I wiped cache. I did a factory reset, nothing... I wiped again. Nothing.
It gets past the Motorola logo and then just sits at the boot screen. A couple of times it would say updating android, it would finish, but then it would go right back to the boot screen. After about 8 hours it finally booted and I used it all day yesterday. This morning my issue is back. I've flashed different images to see if it has something to do with 1.3. It's all the same. I think I might try to go back to kit kat. It seems to be a software problem, but I am starting to think that something most be wrong with my hardware.
I found this thread: https://forums.motorola.com/posts/b0021413e7
I think my phone is shot... Any ideas?
Click to expand...
Click to collapse
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
my2cents said:
That makes sense. Like an idiot, after I finally got mine going, I updated Moto Actions and it crashed again. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Click to expand...
Click to collapse
I did get it booted again. I flashed the kitkat update (not the stock, stock update 1, which is what you should be on if you're using mofo) file on the firmware thread that was posted here using the version of RSDlite that was posted there. The key is just to wait a really, really long time. Even if the screen goes black, it could potentially still be booting, especially if the back of the phone gets warm. I left it plugged in, let it get to the boot animation and left the house for several hours, and when I got back it appeared to be functional, but things were slow and choppy at times and my home button didn't work. The settings menu from the pull down menu didn't work either. I had to access settings from the app drawer. I tried a factory reset from the settings menu, and that just re-broke everything. So now I'm back at square one. I re-flashed the same image using RSDlite again, and now I've waited about 10 minutes and I'm still looking at the boot screen, which at this point is normal since the problem occurred.
I got a hold of an old copy of the Motorola Sensor Services apk. As far as I can tell, this is the apk that is replaced by Moto Actions, which according to Google Play is only compatible with 5.0 and above. My plan for tonight is to wait until the thing decides to boot, attempt to start the stock Sensor Services app and get it to do the sensor firmware uninstall that I mentioned in my other post. If that doesn't work, I'm going to try to install the apk that I found and see if I have any more luck with that. I'll report back here when I get a chance to do that. Let me know if you figure out a solution.
---------- Post added at 03:48 PM ---------- Previous post was at 03:33 PM ----------
my2cents said:
That makes sense, after I finally got mine going, I updated Moto Actions and all the other apps it crashed again in about 12 hours. If I can finally get it to boot again, I think I am going to test your theory. If you figure out how to get it booted again, please share!
Edit, which rootjunky image did you flash? SU2-12?
Click to expand...
Click to collapse
Yeah, I used SU2-12.
I followed the procedure outlined here to go back to stock. https://www.youtube.com/watch?v=6avEPGWB8E0 I used the SU2-12 file, but I lost everything... Thanks for the help. I hope there is a fix for this soon! I'll test your idea about MOTO Actions and report.
Edit: Well, I thought my phone was booting when I wrote the above, but it has been 30 minutes and it has not booted...
So, I can get it to boot - although it is not easy and it takes me like 30 minutes and I haven't found a full proof method yet, but after it goes to sleep I have to start the process all over. It has been a frustrating 3 days.
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.
Click to expand...
Click to collapse
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
my2cents said:
I think you are onto something. I'm currently on 4.4.4 and it is bone stock. When I go into the Play Store it shows that I have Moto Actions installed, but when I click on the app it says that it is not compatible with my device. I've tried wiping the data from the app, force closing it, and clearing the cache. None of that has prompted me to uninstall the sensors. By the way, I found the Moto sensors app and tried doing the same thing, no luck.
So, I think I have the 5.1 Moto Actions installed still, which is causing the 4.4.4 image to freak out. I've thought about trying to go official 5.1 and see if that fixes it, but since I have a replacement on the way, think I might just leave it be - unless someone (like you) figures this thing out.
Click to expand...
Click to collapse
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
TheSt33v said:
I ended up getting a replacement from Motorola too. If it has 5.1 on it, I'll sell it and get one with 4.4.4. Thanks a lot for the tip, by the way. I might still work on it just as a hobby, but I'm out of ideas. Of all the many, many devices I've tinkered with, this is the first one that I ever permanently messed up, so I'd like to fix it as a matter of pride, but I now only have 48 hours to do so. After looking at logcats, the partition table of the phone and the androidmanifest.xml of the motorola sensor services apk, I'm pretty much certain that this app writes those sensor drivers to a partition other than the ones that get flashed when we up/downgrade (ie system, boot, recovery, etc.), which is why these processes don't fix the problem. Theoretically, if I knew which partition that was, I could find someone with a working Turbo who could dump that image, and if I get lucky and it's a partition that isn't sig checked by the bootloader (like the radios, for example), I could flash that and be good to go. I have no idea how to figure out which partition that would be, though. The obvious choice was the "firmware" partition, but that partition has a lot of drivers that seem to relate to lots of different important things, so messing with that seems scary. I also don't know anyone who is knowledgeable enough to generate that image (myself included), so it's a moot point.
Click to expand...
Click to collapse
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
GeoFX said:
My question is why hasn't anyone else's device gotten borked since the update? I've had it since the update was distributed with no issues and use Moto Actions continuously. Seems like if it really is a combination of writing drivers to a partition that isn't compatible it would be a universal issue. If only 2 people who have a mofo'd 5.1 IMG (out of probably hundreds) experienced issues my bet is on some weird glitch that occured when you initially flashed the updated firmware to get 5.1 working on the mofo'd device, rather than some general driver incompatibility.
Click to expand...
Click to collapse
I agree. Either it was a corrupt driver installation that worked just well enough for the app not to realize it, or the firmware update happens silently only when requested (similar to Google play services), and we're all one chop chop flashlight away from a phone apocalypse. Hopefully it's the former.
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
my2cents said:
So, I went ahead and updated my device to official 5.1 and the problem is still there. The moto actions app that is installed still says that it is not compatible with my phone. I have cant figure out how to clear it or delete it or anything. And when I think I have it, I let the phone sleep and I can't bring it back to life again without waiting for a 15 min+ boot. Oh well, at least the bootloader says "official" now rather than "modified." So, Motorola should not complain about it. Thanks for trying to figure it out @TheSt33v
Click to expand...
Click to collapse
Good to know. I picked the $25 option specifically because the free one requires an inspection, but I'll probably update it anyway. I'm not surprised that it didn't solve the problem though. When we flash those upgrade/downgrade images, we're basically just doing manually what RSD lite/Verizon upgrade agent does automatically.
ctopher4
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUO​TE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
This just happened to me yesterday. Long story short, I have a strong suspicion that something about the recent Moto Actions update is breaking our phones for reasons that I describe here: http://forum.xda-developers.com/droid-turbo/help/complicated-problem-restore-doesnt-help-t3184251. I managed to fix it, but I re-broke it because I'm an idiot and the method I used before isn't working. If you get it fixed and get your 1.3 CF image back up and running, I would strongly recommend against allowing the Moto Actions update. I have a feeling that we're going to be hearing more about this soon from other people.[/QUO​TE]
you called it! Just spent 2 hours reflashing 1.3 first repeated V4A, then Base. flashing sick Android upon Recovery attempt, FAIL. reflashed radios and such and with different "vol& pwr" sequence was able to get in to wipe cache. Not hat it would help me but i viewed chche Logs and im wondering if, to the right person, it would help to have copies of them?? It's a bunch of pages tho and and not sure if it would help.
My plan it to, in Recovery, Factory wipe, then reboot to Bootloader and attempt to flash base. W/ all sys.img's, then wipe caches again. ihave read the whole thread early yesterday morning but i fell asleep prob 20 times during. it was like 3 ishi think SO, i'll now go re read probably to find that you've already ruled out "my plan"
Click to expand...
Click to collapse
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
TheSt33v said:
ctopher4 said:
Damn. I was hoping I was wrong. Yeah, I did what you suggested many, many times. If you end up reflashing 4.4.4 and you see the message to uninstall the sensor firmware, do it and FLASH NOTHING ELSE until a solution is found. If not, it's really easy to get a new one from Motorola.
Click to expand...
Click to collapse
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
ctopher4 said:
TheSt33v said:
O Jeez, xda gave me a " token timed out message" but only after I hit post reply and, it was a novel! I have to get at least 2.5 hours sleep tonight because that been normal lately. Besides setting up Moto functionality, I'm golden and I do have their updates blocked best I can anyway. Hope all is working.
Click to expand...
Click to collapse
Awesome! Well I managed to fix it too, Moto functionality included!!!! I'll explain on my other thread.
Click to expand...
Click to collapse
What was the solution that found? I'm going through the same problem.

LG Optimus L90 Root problems. HELP

Hello all. I Recently attempted rooting my phone, running on 5.0.2, and it seemed to have worked. But then after attempting to use SuperSU to add root permissions to an app, my screen went black, and the only thing visible was the top status bar, which had some animations still running (Like the battery icon filling up or the signal bars changing), but thats it. It wasn't responsive to any of my button presses, and then it shut off. It keeps doing this over and over, and i cant keep the phone on for more than 5 mins maybe 10. How would I fix this? I used this "tutorial". - andromods .com/news-root/lg-g3-g-flex-2-g2-lollipop-one-click.html - (Stupid thing wont let me post links)
I would like to solve this without factory resetting, as I have apps that have data on them that needs to be transferred from one phone to another, and i dont have a second phone to transfer to at the moment.
Thanks in advance.
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
lfom said:
As far as I know, flashing kdz with LG Flash Tool following the tutorial to "unroot" won't delete your data, but you will lose root, of course. If you don't have custom recovery nor root, there is little else you can do. Do you have adb root (shell)? If yes you can try re-flashing system partition...
Click to expand...
Click to collapse
I'm very new to this, and probably shouldnt have attempted this without knowing more, so I have no idea what you are asking me. What is ADB root (shell)? I probably dont have it. And I didnt do any sort of custom recovery. But it seems that me messing around with SuperSU (clicking the uninstall root/turning of superuser once or twice) seems to have stopped the crashing all together. Ive been using my phone since and it hasnt crashed. Whether or not that's fixed the real issue, I don't know. And I'm not sure I want to mess with it further. :crying:

I Think I Trashed my Tab S2 T713

I am coming with hat in hand fully expecting to find out that there is no solution and I am out the $$$ it will cost me to replace. After having this device for close to 2 years, I decided I would root it. I have 5 other devices currently that are rooted and numerous others that I have rooted over the years (including Samsung). Admittedly, I dislike Odin and a lot of other things about rooting Samsung devices. That is part of the reason this was the only device that I ever kept unrooted for more than a month or two. I installed twrp_3.1.0-1_sm-t713_14417n with Odin with no issues. I had SuperSU 2.82 in internal. When I got into TWRP to install it, I saw nothing but directories in internal and it became clear to me that it was encrypted. Attempts to mount, wipe and even reset data all ended up with me booting back to TWRP. I'm sure frustration set in the more things I tried, but now I can't even shut the device down from TWRP or by long pressing power and volume down. Even that just goes back to TWRP. Obviously, I can't get into download mode or system. I just get the recovery booting set warranty bit: recovery message when it starts back up to TWRP. Can't say I have ever seen a device that can't even be forced to shut down, LOL. Thanks in advance if anyone can help.
*I've made some progress. I managed to back door my way into download mode by installing the boot.img from the external SD card. That didn't fix anything, but after that I was able to hold down power down and volume and spam the home button until I got to the download screen. I was able to get back into Odin, but the full firmware file I tried to install errored out at the end with a rev check fail. Hopefully, it was because it thought it was downgrading, so I am downloading the newest file now. The samsung-firware.org D/L is brutally slow. Has a few more hours to go, and I am not positive if it will work yet. Cross your fingers, and throw out any ideas if you have them.
Well, it's alive. Everything is back to normal (except needing to reinstall). Time to root now, LOL!
OK, tried again and ended up restoring the full image again (minus D/L time at least). I am ready to scrap root on this device. I have tried to do everything in the [TWRP 3.1.0-1][ROOT] Galaxy Tab S2(2016) - SM-T713/SM-T719/SM-T813/SM-T819 - 1/4/17 thread. https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627 I would have tried installing no verify, but no matter what I do not see the SU and no verify files on the tablet either after format data without reboot or after rebooting into TWRP. After the format, it shows that data is mounted. Looking at the pictures in the thread, I think maybe it needs the work done on the external SD but the instructions say nothing about that. Time to sleep on it, and maybe someone smarter than me can think of what I might be missing and maybe better step by step instructions are available. At least it is up and running, KNOX trips be damned. I'll post to the TWRP/ROOT thread. BTW, the OS version I am running is XAR-T713XXU2BRB2_T713XAR2BRB2-20180206.
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
sliding_billy said:
Well, thanks to some middle of the night assistance from ashyx and about 3 hours sleep in the past 48 hours, I am not only restored and working but now rooted with TWRP 3.1.0-1 and Magisk 17.1! Time for a nap.
Click to expand...
Click to collapse
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
rholm said:
I am thinking about rooting my T713. Are there better instructions? What did you have to do differently?
I'd like to get it a go, but the instructions aren't as good as for the many devices I've rooted in the past.
Thanks!
Cheers,
Rich
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
The instructions in the TWRP thread are OK, but they could be a little clearer in some places. Take a look at the interaction between ashyx and I towards the end of the TWRP thread.
https://forum.xda-developers.com/tab-s2/development/twrp-3-0-2-1-galaxy-tab-s22016-sm-t713-t3390627

Categories

Resources