Database Develop

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.

Help needed with new phone

Hello
Just got myself a new piece today. I'm afraid to do anything wrong and afraid to use without installing a new ROM myself.
I have read on different forums that when you buy a global version they are often infested with malware and you have to do af fastboot update to remove it all.
I haven't powered the device up yet because I want to do things right the first time.
My intention is to have the newest official stable global rom on the phone. I just not sure which step i need to take.
If a helpful soul could advice me I would really really appriciate that I have found several guide but I need to know the exact right steps. It is okay if you link to a step by step guide.
Here are links that I would go with, but I'm not sure if I need to unlock and if I have to wait for 2 weeks to be approved or if there is a quicker way
http://en.miui.com/thread-432261-1-1.html
http://en.miui.com/a-234.html
Charlie Kilo

charlie_kilo said:
Hello
I haven't powered the device up yet because I want to do things right the first time.
Click to expand...
Click to collapse
Hello welcome to the yard. ?
If you're still afraid of beginning with all these great guides, better do not power on though.
Sent from my lithium using XDA Labs

Well eventually I will have to power it on - won't I
I'm not affraid to use these guides or some other detailed step by step procedure. I'm just a little confused about the order and if these guides can be used if I want newest official global stabel ROM. I guess It is more the steps than what you do in the steps - hope it makes sense
Charlie Kilo

You'll have to get it powered up and registered. Xiaomi impose a 3 day embargo on you where you cannot unlock the bootloader, I'd at least get that timer ticking away and then apply to unlock it asap.
Then you need to install TWRP. I recommend searching for the Mr Raine's version.
Pick a ROM and then off you go!

paulrgod said:
You'll have to get it powered up and registered. Xiaomi impose a 3 day embargo on you where you cannot unlock the bootloader, I'd at least get that timer ticking away and then apply to unlock it asap.
Then you need to install TWRP. I recommend searching for the Mr Raine's version.
Pick a ROM and then off you go!
Click to expand...
Click to collapse
Think they're trying to scare you, just look about phone check ROM number to see if it matches 1 of Xiaomi official ROM. I had vendor ROM and my house hasn't been stolen, just don't turn you're data on.

charlie_kilo said:
Hello
Just got myself a new piece today. I'm afraid to do anything wrong and afraid to use without installing a new ROM myself.
I have read on different forums that when you buy a global version they are often infested with malware and you have to do af fastboot update to remove it all.
I haven't powered the device up yet because I want to do things right the first time.
My intention is to have the newest official stable global rom on the phone. I just not sure which step i need to take.
If a helpful soul could advice me I would really really appriciate that I have found several guide but I need to know the exact right steps. It is okay if you link to a step by step guide.
Here are links that I would go with, but I'm not sure if I need to unlock and if I have to wait for 2 weeks to be approved or if there is a quicker way
http://en.miui.com/thread-432261-1-1.html
http://en.miui.com/a-234.html
Charlie Kilo
Click to expand...
Click to collapse
A fastboot update wouldn't remove anything that's on the device. As it sounds, it would just perform an update.
As others stated, you should get it powered on & start the unlock process through Xiaomi. You don't need to sign into your Google account, so the only thing they would have access to is the Xiaomi account you register with.
After you are able to unlock the device, get a custom recovery (TWRP) installed. You may need to try a few different ones, i.e.: The "official" one doesn't have the touchscreen when booted into it.
From there, choose a ROM, flash, & you're good to go.

Veritas06 said:
A fastboot update wouldn't remove anything that's on the device. As it sounds, it would just perform an update.
As others stated, you should get it powered on & start the unlock process through Xiaomi. You don't need to sign into your Google account, so the only thing they would have access to is the Xiaomi account you register with.
After you are able to unlock the device, get a custom recovery (TWRP) installed. You may need to try a few different ones, i.e.: The "official" one doesn't have the touchscreen when booted into it.
From there, choose a ROM, flash, & you're good to go.
Click to expand...
Click to collapse
Thanks for the help so far and good advices.
Update of the situation is that I powered the beauty up. I could see that it took me through the entire setup phase from the beginning like it is normal for a brand new and untouched phone. Shortly after it was updated twice via OTA and is now on the newest official global ROM.
Everything is working perfect and I am extremely happy with the phone.
Two days ago I requested Xiaomi to unlock the bootloader as I would like to root the phone.
/CK

charlie_kilo said:
Thanks for the help so far and good advices.
Update of the situation is that I powered the beauty up. I could see that it took me through the entire setup phase from the beginning like it is normal for a brand new and untouched phone. Shortly after it was updated twice via OTA and is now on the newest official global ROM.
Everything is working perfect and I am extremely happy with the phone.
Two days ago I requested Xiaomi to unlock the bootloader as I would like to root the phone.
/CK
Click to expand...
Click to collapse
Let me know how it goes when you do, & what you end up flashing. I'm done the latest MIUI Beta & now the Pixel Experience 8.1 ROM, & I keep losing voice call server. Looks like I can still text, but no outgoing or incoming calls. I'm running on Project Fi too. With all these issues, I'm considering a switch to the Essential Phone. Arriving today for me to test out.

Veritas06 said:
Let me know how it goes when you do, & what you end up flashing. I'm done the latest MIUI Beta & now the Pixel Experience 8.1 ROM, & I keep losing voice call server. Looks like I can still text, but no outgoing or incoming calls. I'm running on Project Fi too. With all these issues, I'm considering a switch to the Essential Phone. Arriving today for me to test out.
Click to expand...
Click to collapse
Well don't use pixel experience, I didn't have any problems like that, just flashed latest epic and everything works perfectly and I mean everything.

james1089 said:
Well don't use pixel experience, I didn't have any problems like that, just flashed latest epic and everything works perfectly and I mean everything.
Click to expand...
Click to collapse
Yeah, thanks. I switched to AICP & those issues were fixed. Now just an issue with camera focus.

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

Lost system on A partition, how to get back?

Totally stock pixel 5. Tried to sideload 12, and due to crappy instructions on XDA, that failed to mention the need to do the OEM unlock step, I ended up with a ADB sideload flash that failed at 94% and resulted in a empty A partition and a phone that failed to boot, so it switched to the backup system partition.
I'm now booted on the B partition (Android 11).
How can I fix my phone, so it's got 2 good system partitions?

Enable OEM unlocking, unlock bootloader, then use the Android Flash Tool to flash 12 Beta 5. Wiping /data shouldn't be necessary; however, if this fails and you have to force flash all partitions, a /data wipe will be required.
I highly recommend you keep the bootloader unlocked while using beta firmware, because it makes it a LOT easier to downgrade back to production firmware.
If you intend to root, don't forget to disable dm-verity and vbmeta-verification.
Detailed instructions on using the Android Flash Tool
Tip: When you get to the step of selecting which build to flash to your device, click the pencil icon to change options. Make sure you leave Relock Bootloader unchecked,

V0latyle said:
Wiping /data shouldn't be necessary
Click to expand...
Click to collapse
But unlocking the bootloader will wipe the phone.....
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it

xunholyx said:
But unlocking the bootloader will wipe the phone.....
Click to expand...
Click to collapse
Correct, but it's still necessary to install the beta (and downgrade)
xunholyx said:
EDIT: I'm assuming there is a wipe data option with Android Flash Tool?
I don't know. I've never used it
Click to expand...
Click to collapse
There is indeed. It's actually quite comprehensive.

I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,

Chr1stOnABike said:
I don't want to unlock the bootloader. I just want to get a system partition back, I do t want root or any modifications,
Click to expand...
Click to collapse
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work. Requires unlocked bootloader
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.

V0latyle said:
In that case, I believe the only option for you is to attempt to sideload the OTA via recovery.
Download the beta OTA here
Follow the instructions to apply the OTA here
If this does not work, you can try using the Android Flash Tool after enabling Developer Options and USB Debugging. You can choose not to wipe your device in the tool options. No guarantee this will work.
I will say this: Running beta software on a locked bootloader is not only highly inadvisable, it's foolhardy. Beta software is EXPERIMENTAL, you use it AT YOUR OWN RISK, meaning it is YOUR responsibility to fix it if something goes wrong. Keeping your bootloader unlocked means your ability to fix it is limited, if not impossible.
Click to expand...
Click to collapse
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)

Chr1stOnABike said:
Flash tool doesn't work, as it expects to go i to recovery, and it doesn't it comes up with the no system error.
Click to expand...
Click to collapse
Ah. Well, you can fix this, but it will require unlocking the bootloader.
You can always relock it after you're done.
Chr1stOnABike said:
So when android 12 releases in a couple of weeks, will it just flash it to the other partition, to retain 11? In other words,will this fix itself in the fullness of time.
Click to expand...
Click to collapse
Don't know. Given that you can't boot into recovery, you can't sideload the OTA to test this theory. I personally doubt it. You can either wait and see, or you can just bite the bullet and fix the issue.
Chr1stOnABike said:
Also, who is going to fix the crappy XDA blog post that was poorly checked that caused this mess. I can't be the only one (I know the flawed instructions have been copied by the usual churnalists 9to5google Android authority, Android police)
Click to expand...
Click to collapse
Link to the post? You may not be the only one, but the majority of folks (including myself, I was in the Marine Corps for 9 years so you can guess my mental acuity) have been able to use the instructions to our success.

Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?

How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.

Chr1stOnABike said:
Isn't unlocking and relocking bootloader detectable in soft fuses and an instant warranty void?
Click to expand...
Click to collapse
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
Chr1stOnABike said:
How to install Android 12 and 12L on Google Pixel and other Android devices
Google has just released Android 12L beta for the Pixel lineup. Here is how you can install Android 12 (or 12L) on your smartphone!
www.xda-developers.com
Someone in the comments also broke their phone by following the untested Instructions.
Click to expand...
Click to collapse
I have updated my phone using both of these methods and can personally confirm the instructions are correct. The only difference I would point out is that I'm comfortable enough using adb and fastboot commands that I manually type them and don't use the batch file.
It is your responsibility to understand the instructions and follow them. You flash and modify your device at your own risk. If you do not fully understand the instructions, it is also your responsibility to either find the details you need, or ask for help.
This may seem rather condescending or apathetic, but the situation is this:
- You tried to run experimental beta firmware on your device despite your concerns for the warranty
- You did not ask questions before doing so, and if you did read any of the multiple threads on this issue, you would have been acutely aware of the recommendation to unlock your bootloader before you proceed
- You are now left with few options to fix your device because you decided to ignore experienced advice and do things your own way
As I stated previously, the responsibility for fixing things is yours and yours alone. If you were that concerned with your warranty, you should have kept your phone completely stock and avoided installing the beta.
I have one last recommendation for you:
Disenroll from the beta program and wait for the OTA to take you back to A11 public release. A data wipe will be required.
You have been told in detail what you can do to fix your device. What you do now is completely up to you.

V0latyle said:
I'm not sure. But that raises a question for you: Why are you running beta firmware if you're worried about the warranty?
I have updated my phone using both of these methods and can personally confirm the instructions are correct. .
Click to expand...
Click to collapse
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.

Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
Click to expand...
Click to collapse
Yes - I unlocked and rooted my phone the day I got it, and I bought it full price direct from Google. Your point?
Chr1stOnABike said:
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
Click to expand...
Click to collapse
Yes, it's always worked for me. I've been trying to work with you here and give you options that do not require OEM Unlock or unlocking the bootloader. The reason I thought the Android Flash Tool might work is because it's literally a tool provided by Google, and though it uses ADB, I figured they might have some sort of security to allow recovery of locked phones.
What exactly is it you don't think I understand? As I've pointed out, you decided to install beta software on your device despite your concerns for warranty. As I ALSO pointed out, if warranty was that much of a concern for you, you should have stayed on stock public release firmware and not messed with anything at all.
I will admit that the guide you linked does not mention needing an unlocked bootloader. I think it's generally been assumed among us in the community that modifying your device requires an unlocked bootloader. I will talk to the mods and see if we can get a note added to the post. However, you seemed to miss the big warning that advises against using the beta on your daily driver.
Chr1stOnABike said:
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
Again, how so? If you're going to call me ignorant, you had better explain how.
OEM Unlock simply sets a flag: "unlock-ability" to 1. It's an on/off switch that corresponds to the 1 or 0 set for the "unlock-ability" flag. It has no other function.
When someone attempts to unlock the bootloader, the device checks that flag. If it's 0, the bootloader cannot be unlocked. If it's 1, it can.
Unlocking the bootloader disables security features that prevent you from flashing partitions on your phone, or booting images sent via ADB. The reason why this is important when running custom or experimental firmware is because it allows the user to reflash corrupted partitions (like in your case). It allows a lot more freedom over what you can do with your phone.
I've been doing this for years - more than 10 years in fact. I would be careful about making accusations like "you don't understand the difference" or "you don't know what you're talking about'" to someone who is trying to help you. I understand you're frustrated, but you're going to have to swallow your pride here and admit, at least to yourself, that you screwed up. It seems pretty clear to me that you either did not fully understand the risk of trying to modify your device with a locked bootloader (yes, installing the beta counts as a modification), or you ignored the risk and tried to do it anyway. Yet you come here and impugn my credibility? As they say, "check yourself before you wreck yourself". You screwed up and got yourself into this mess. You alone are to blame. No one has to help you, and believe me, I've been quite tempted to tell you to pound sand. The least you can do is show a little gratitude for someone who's trying to help, and respect for experience and knowledge far beyond your own.
I have one more option for you: Rescue mode.
Reboot your phone into bootloader (hold power + volume down, release power but keep holding volume down when screen turns off)
Use volume buttons to select rescue mode on the right side, then press power to select
Google Pixel Repair Tool
This probably won't work because the repair tool only works if the firmware on your phone is older or equivalent to the firmware the repair tool has.

Chr1stOnABike said:
The instructions only work if you have previously done the unmentioned OEM unlock step, which you must have done.
The fact you don't understand this, it limits your credibility. Just because something worked for you, doesn't make it correct.
It also sounds like you don't understand the difference between OEM unlock and a bootloader unlock.
Click to expand...
Click to collapse
I haven't had time to read much of this thread yet, but why insult the one person I see who's trying to help you?
I've seen this before and other users who may know what to do, usually just walk away as they don't want to help someone who may just insult them or are clearly unappreciative of the help given.
Everyone let's all keep it civilized.
If you have issue with a post, please hit report button and walk away.
Positive vibes, all.
--andybones

@Chr1stOnABike I am indeed trying to help you, as I understand your situation is frustrating. I also understand that it may be frustrating to be told to do what you didn't want to do in the first place, but the reason why I'm telling you to do it is because it'll be of the most help to you.
Losing your data sucks. I get it. But fortunately the Pixel 5 is great about backing everything up to your Google account. Just make sure your photos are backed up and you'll be fine. Setting it back up after a wipe is a pain in the ass, but again, I'm recommending the bootloader unlock because I believe it's your best chance at recovery.
As far as that goes, I'm still trying to be flexible and provide you with different options. Be aware that if these other options don't work, you have no other choice. I'm not saying that to be rude, that's just the reality of it.
And lastly, I would very much appreciate you making the distinction between thinking I'm wrong because you have evidence to the contrary, vs thinking I'm wrong simply because you don't like my recommendations. If you sincerely believe I'm incorrect and can demonstrate how, please feel free to do so.
My only objective here is to help people the best I can with the knowledge and experience I have.

For those who ever get stuck like I did. When I got stuck in a bootloop, I realized I could 'fastboot boot twrp.img' and was able to save my internal storage from being lost by backing up to PC with TWRP, then move it back onto internal after the factory reset. Did I lost app data in these cases, yes. But that's my own fault for not regularly backup app data up with something like Swift or AppDash.

@Chr1stOnABike just checking in to see if you were able to get your problem resolved?

Question US Unlocked but using T-Mobile SIM - How to Root safely, many ??s

Long story, but after travails with an Amazon-purchased Oneplus 9 Pro due to it being locked (T-Mobile!) and them refusing to unlock it....
I went to OnePlus and got myself a OnePlus 10 Pro Unlocked. Still have the T-Mobile sim, though.
My question....
I have been out of the rooted phone scene for some time. I had a Oneplus 2 rooted and a Samsung Note 4 and 5 rooted. But things are different now, I'm gathering. Plus this is a new phone and I don't want to toss away hundreds of dollars by bricking it.
I used TWRP back in the day. Flashed many a custom rom back then. But with this OnePlus, I already unlocked it which... is that the same as rooting it? And what are the benefits of rooting / flashing roms vs just going with what is currently on this US phone (Oxygen 13 but not 13.1 yet)? I kinda want to see TWRP on here, and back up my whole set up into files I can then copy to my computer(s) for safety's sake. At least I liked that feature when I had it w/ the OP 2 and others.
Trying to get back up to speed in the world of rooting as it stands now.
Thanks.

TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.

Prant said:
TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.
Click to expand...
Click to collapse
Thanks for this.
I got as far as unlocking the phone and installing Magisk. But haven't gone further until I understand what the next step is.
Can I root non-destructively? Or is the phone wiped?

If you're unlocked and have Magisk installed, rooting is as easy as booting a patched boot image, then using Magisk to install it to your boot image. You have the choice of finding a matching one in one of the guides or pulling your own from a full zip.
It must match the firmware revision, I know for a fact personally that region matters little in case of NE2215/3, as you're only doing a one time boot.
I recommend @g96818 's guide here, you can find almost every firmware's boot image posted there if you prefer patch it yourself using Magisk or just boot an already patched one.

I have a 10 Pro (NE2215) rooted as a daily driver using TMO US.
Unlocked means 2 things in the android phone scene. Either it's carrier unlocked and can take any sim from any phone company or it bootloader unlocked which is needed to root and load custom roms.
There aren't any custom roms for the 10pro because of the lack of a full recovery system. Basically the ability to force full flash a stock rom in case the custom ROM soft bricks the phone. So that leaves rooting as the reason to unlock your bootloader.
I suggest reading the guide for rooting this phone, it's relatively easy. TWRP is unnecessary as it doesn't offer much without custom ROMs. Also you should back up everything on the phone that you don't want to lose because during the rooting process a factory reset will occur (android safety feature).