Related
So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.
Just a little bump, not too big... no love for Tim?
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!
The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.
Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!
It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol
Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh
No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!
Hi there,
My phone has android 6.0.1 and i want it downgraded to android lollipop because ive got problems with android 6.0.1.
Im a total noob with all this stuff, so can someone please advise step by step how i can do this? I have the MOTO G 3rd Gen, SKU is "XT1541", Ram is 1GB and ROM 8GB. My current system version is 24.61.55.osprey_reteu.reteu.en.EU reteu. Build number is MPI24. 107-55. This phone will accept any phone network. Can someone please help? thanks in advance!
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
acejavelin said:
There are multiple threads discussing downgrading, it can be done if your device has the bootloader unlocked (which wipes data and voids the warranty)... There are some inherent dangers in doing so, some immediate and some long-term dealing with future updates which have the potential to brick the device.
What are the issues you are having, many times it is better to solve those then to downgrade.
Click to expand...
Click to collapse
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Ryanm353 said:
Some apps wont run well on android 6.0.1 such as facebook etc (personal and buisness use) and my phone generally ran better with the previous android version. The phone does not have a warranty on it anyway so that does not matter. Trust me, it really cudnt be much worse than it is atm, ive factory reset it and its just not up to standard as it was with android 5. I did have android 6.0 which i didnt like and then i got 6.0.1, which was putting ice on the cake, (in a bad way!). I am 1000% sure i want to downgrade my device. Can you help?
Click to expand...
Click to collapse
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Not much to it... Unlock the bootloader, factory reset, then use the lollipop factory image from the factory images thread, gpt.bin will fail, just continue to flash everything all the way through. Follow the instructions in how to flash factory images, it's all done in fastboot.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Ryanm353 said:
Thanks. But can you explain all that in more detail step by step? I need clear instructions on how to do all that as ive literally no idea about anything.
Click to expand...
Click to collapse
No offense, but this is not something to be taken lightly... there are many steps.
First, backup all your data... it will be lost.
Start by reading the first few posts in this thread... This will give the basics of what is needed to be done, what tools you need, how to do it, and the factory firmware images (you will need the correct one for your device, all the ones available are in this thread.
Next, read the first two posts in this thread... this is the instructions in detail of exactly how to flash a firmware image. Pay attention to the warnings and follow the linked threads with more information and make sure you understand all of it.
Once you have read and understand this part, you need to get fastboot working... this tool is essential to making all this work. Both of the threads I mentioned above have links to the drivers and Minimal ADB & Fastboot you will need. Install them and make sure they are working.
Now you can unlock the bootloader, this will wipe all data on your device. The instructions and process are done directly with Moto here.
Once you have unlocked the bootloader, reboot and start the bootloader and follow the instructions in the threads above, noting that the part where enter the command "fastboot flash partition gpt.bin" will likely fail because you are downgrading, but no other pieces should fail, if they do enter them again (radios are known to need to be done 2-3 times sometimes before taking), and continue all the way to the end. Pay attention to the number of sparcechunks in your image, it can will vary and you need to flash all pieces in order for your device, there could be anywhere from 5-9 pieces.
Keep a log of everything, it is much easier to tell what happened if something goes wrong by looking at the terminal log (scroll back of the terminal window) than just guessing.
TBH... I am not endorsing this method, but it generally does work, and although it is difficult to brick the Moto G 2015 it is not impossible. After you are done, you will need to root the device and freeze the updater service so you are not constantly prompted to update, and taking an OTA update can be problematic since your bootloader and/or partition table will not match the rest of the ROM correctly.
Personally I think since you have to unlock the bootloader anyway, you are probably better off just looking for a custom ROM like CM13, Resurrection Remix, or something like that since there are lots of rock solid Marshmallow aftermarket ROMs. Or if you are dead set on Lollipop, using CyanogenMod 12.1 instead of downgrading.
I know there is a downgrade utility out there, and not to take away from the developers work but I would suggest avoiding it.
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section to root, or "Do the prep" section to fix a bad root.
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting update UPDATE-SuperSU-v2.82-20170528234214.zip (version 2.82) is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
Do the prep:
Note that the hidden Do the prep section is ONLY for repairing a bad flash, SuperSU has been updated and as of version 2.79 the hidden section should no longer be needed for general purpose root on a working device, you just flash SuperSU. If you flashed an older version and are bootlooped, perform this section and continue.
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, when you have your backups and are ready to root, first go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press ENTER (there is no confirmation returned). You can verify this worked correctly by entering 'cat /data/.supersu' in the terminal and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again. Now press exit/back and press the HOME key.
After you have successfully entered the command in the TWRP Terminal you may continue
How to do it:
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
Again, this is somewhat dated information and only applies to fixing a bootlooping device when improperly rooted.
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
NOTE: I no longer own this device, but will help where I can and will keep this thread open to assist users where ever possible, but I no longer have a device to test/verify things with.
Alternate Method #1
Some users have noted that the above method doesn't seem to work, we don't know why as it seems inconsistent but we can't pin it down specifically to user error, certain model number or build, or anything else, as it works 98% of the time...
But if the above method fails, the alternative is to download and copy to SD card or internal storage SuperSU 2.62-3 ßeta version available here and flash it through TWRP like normal.
Reserved - FAQ (oops, guess I already did that)
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Jorinde123 said:
I'm so glad I found this thread! I've been procrastenating fixing my phone because of all the crappy methods. This one very easy to follow!
But still can't manage to get my WiFi working
I don't get it. But somehow my nandroid backup failed too, because it's only some 2.X MB big and I don't seem to recover anything....
So I guess I'll have to keep trying..
FYI:
1) Moto X Style 6.0
2) TWRP 3.0.2-0
3) Tried both 2.78 and 2.62. Currently running 2.62
4) SYSTEMLESS=true
Click to expand...
Click to collapse
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
acejavelin said:
Find the latest rom image for the version you have installed, and flash the radios with fastboot.
Click to expand...
Click to collapse
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Jorinde123 said:
Thanks for your quick reply. Tried that, didn't work.. The ROM i'm currently running is MPH24.49-18 btw... I'm now trying it the hard way, just reverting everything step by step. But the first step (flashing gpt.bin) is already giving me the preflash error. This is going to be a lot harder than I thought and it's been too long since I've been flashing these things.
Used to flash my Moto Milestone and my Sony X10, can you imagine.
Click to expand...
Click to collapse
Because you are not on 49-18, if you were on the latest OTA for 6.0 you were on 49-18-4. Pre-flash validation failure confirms your using the wrong version. Look in my sig for the return to stock thread, there are links to current roms and discussion of the 'preflash validation error'.
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Got the Moto X Pure a few days ago. It came with 6.0. This procedure works. Thank you!
ban.codrut said:
Wasn't systemless method only intended for not altering the system partition in such way not to break compatibility with Android Pay and such apps that don't allow root?
Maybe I got it wrong when I first saw the appearance on the scene of systemless root. From what you are saying the auto detect it's supposed to detect with which method the device is compatible (not only detects if system was already modified? let's say like by TWRP).
I wasn't able to flash SuperSu newest stable versions either, all ended up stuck at boot, except for the 2.62 version (updatable later through playstore and binaries thorugh app via normal update). Honestly I haven't tried systemless as for me I through it was a waste (as said I through it wasn't meant for other purpose).
ATM I'm using CM's own root, but I will report as soon as I will try SU again. I never had problems with modem/wifi with SU, only that it didn't boot on newer stable builds.
Click to expand...
Click to collapse
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
SouthernEvo said:
Currently Using TWRP 3.0.2.0 . Just unlocked bootloader and haven't done anything else . Recovery flash went well during the initial process of unlocking . Now Im trying to make a backup of the stock Rom , everytime I try to make one I keep getting failed at the end of the process ? Is this a known bug ? I have been doing google searches for the past hour and still unable to find anything to indicate anyone else is having this problem . Unless I didn't use the correct terms while searching . Any help would be appreciated
Click to expand...
Click to collapse
It is not a known issue... Where are you storing the backup, internal storage or SD card?
acejavelin said:
It is not a known issue... Where are you storing the backup, internal storage or SD card?
Click to expand...
Click to collapse
Was backing up to the SD Card . Been messing with it and now its working for some weird reason . I appreciate your quick response though
I used windroid to unlock the bootloader and install twrp( don't reboot system but rather boot into recovery to make twrp stick) , from there I just flashed supersu and I was good to go. Many methods out there but this worked for me.
Thank you so much for this guide. I have to say, as a new Motorola user coming from Samsung phones exclusively, this whole process made me feel like a real noob again.
I made the switch from iOS to Android back when the Galaxy S2 came out because I grew tired of the jailbreak cat and mouse games on the iPhones and iPads. Learning to root and flash ROMs on all my subsequent Samsung devices was fairly simple and very enjoyable. This Moto X Pure though was a real tasker for me. I honestly never knew about the extra steps you had to take to unlock, twrp and root this phone. I really wish manufactures would help us make this much easier.
Anyway, thank you again for your help. I'll be seeing y'all around the forums as a new MXPE user!
acejavelin said:
No, although that was one thing we thought we would gain (which we didn't), Systemless root is to get around Marshmallow security. Root is detected by SafetyNet API, and it detects pretty much any system modification, systemless or not
Click to expand...
Click to collapse
Thank you for clarifying a misconception I had on systemless root
(I intentioned to reply to you earlier, but the mad busy week made me forget about my intent )
I'm going to try right now the latest stable with systemless method (rather than flashing the older version) on a full wiped clean stock to see if it works. (Even tho I see lots of feedbacks here inspiring me to believe it would)
In what order?
acejavelin said:
It seems no matter how much this topic gets discussed, people still use old methods and they either fail, or they break something like WiFi, Mobile Data, infinite bootloop, or getting stuck on the boot logo... THIS DOESN'T HAVE TO HAPPEN and it IS repairable, usually without reflashing the entire image. The problem comes from using an old method, outdated SuperSU, or incorrect method. This guide will help you correct most issues, or help you to flash root correctly the FIRST time.
I have written rooting guides for multiple Moto device, and I have owned many Moto devices as well, so I have some idea what I am saying and I have tested these methods extensively, they work.
------------------------
This guide covers ALL Moto X 2015 models that can be bootloader unlocked and have TWRP available, it doesn't matter if it is the XT1575 or XT1572, the method is identical (untested on Chinese XT1570, but it should work). In fact, this method will work on all 2015 and 2016 series Moto phones running Marshmallow, including the Moto E, X, G3, G4, and Z with the appropriate TWRP image.
Please read completely and make sure you understand each step and how to do it, if you don't get something search the thread or ask an open question, no offense, but do not PM me with a question because you think it is too stupid to ask in public (we all started as noobs), or because you want me to hold your hand and do it for you, I will politely tell you no and ask you to post in the thread.
If you are coming here because you followed an old guide where you used a special boot.img file and now you have no service (WiFi and/or mobile data) and you don't have a TWRP backup to restore first, well, the RIGHT way to fix it is to reflash the current stock firmware image and start over... why? Because the various "help" people give to have you flash the radio files that match the kernel (ie. boot image) that was patched for the old style root method, has now put you in a mismatched firmware environment and could potentially brick on the next OTA. If you are in this situation and don't know for to properly fix it... go to the FAQ section in post #3 below (WIP-incomplete).
If came are coming here to root the first time, or you just thought you could flash SuperSU and reboot and now stuck in either a bootloop or stuck on the boot logo... Your in luck, read on, because we can fix that in a jiffy!
tl;dr version for advanced users: Skip to "How to do it" section
I am writing this tutorial because there are still lots of failed root attempts using older "standard" methods that do not work on this device. I also do not like the "one click" root methods, because they can and do fail (KingoRoot will brick a Moto X P/S, regardless of what it's web page says), and when they do people have no idea how to fix it. The manual way is not difficult, and it teaches you how to work on, fix, and use your device on a level above that of the average smartphone user.
I will only cover the details of rooting, the prerequisites are covered elsewhere in detail and I will link to reliable sources for the information. Specifics of the prerequisites are outside of the scope of this tutorial, but are open for discussion in this thread.
Prerequisites:
1) Device must have an unlocked bootloader. See Moto - Unlocking the Bootloader for more info.
NOTE: Performing this prerequisite will give you all the tools (fastboot) and drivers needed to continue, and wipe your device, meaning erase all your information and programs. Make sure to backup any important data first. This step will also permanently void your warranty once an unlock code has been issued by Moto, it doesn't matter if you even use it, your warranty is done.
2) You need to have TWRP installed or one-time booted via fastboot. CWM and other recoveries will NOT work at this time. See the official TWRP pages for clark here. I will NOT teach you how to use TWRP in this thread, if you are going to root you need to understand that your self, but if you get in a real bind I may knudge you in the right direction. I will tell you that there are two modes, flashed or booted, the later is much better if you plan to take an OTA later as long as you don't do something stupid like flash Xposed.
3) You need a copy of the latest STABLE SuperSU ZIP from Chainfire's site on the internal storage or SD card of your device, you can always fine the latest stable version here: https://download.chainfire.eu/supersu/ As of this posting SR4-SuperSU-v2.78-SR4-20161115184928.zip is the current stable version and it has been tested and verified to work.
NOTE: Unless otherwise stated, do not use a beta version for rooting Moto devices. SuperSU versions with even numbers are stable versions, while odd numbered versions are beta editions.
4) Reboot and start TWRP recovery, the method you use to do this doesn't matter (boot or flash).
5) Backup your device with TWRP to your SD card, even if you just unlocked and the phone is as blank as a printed page from a 1988 HP DeskJet printer with it's original cartridges still installed, backup... You will always have a good point to return to if the worst happens.
How to do it:
Now, the procedure is the same whether you are trying to root the first time, or you did it the old way just flashing SuperSU and are now not able to boot...
In TWRP, go to Advanced and open the Terminal, in the terminal type this EXACTLY as shown:
Code:
echo SYSTEMLESS=true>>/data/.supersu
Now press enter (there is no confirmation returned), then exit and press the Home key. You can verify this worked correctly by entering 'cat /data/.supersu' and see if it returns "SYSTEMLESS=true", if not, you did it wrong, try the echo command again.
Go to Install and select the SuperSU zip file you downloaded from Prerequisite #3 and swipe to flash it and reboot. No need to clear caches or anything else but you are welcome to if you wish. You can install SuperSU updates normally through the app going forward (as of this posting).
Why do I have to do this???
For whatever reason, the install script for SuperSU does not recognize that this device (like many others) requires a systemless root installation. By creating /data/.supersu in the TWRP recovery environment, the SuperSU install script parses the file and sees "SYSTEMLESS=true" and ignores what it auto-detects and forces a systemless root installation.
Hope this is helpful to someone!
As always, if this is the first time you have booted TWRP or attempted root... BACKUP IN TWRP FIRST!!! Once the system is modified, it cannot be undone (easily) and you will always have a known good starting place if the worst happens.
DISCLAIMER: I am not responsible for anything that happens... Your device, your responsibility, no matter what happens... Although all the information here has been tested and is known to work with no issues except where noted, things occasionally can and do go wrong and we cannot foresee every possible scenario or circumstance.
If you need assistance, we need detailed information about what what's going on and what you have tried to do... Please provide details including:
1) Device model number and Android version
2) TWRP version
3) SuperSU version
4) Output of 'cat /data/.supersu' from TWRP terminal
And a copy of recovery.log if possible, and any other pertinent information you can think of. Without specific information there is nothing that I can do to assist you and request for help may be ignored.
EDIT: Photos added showing what a proper command and flash should look like. Note that in picture 1 the exit command is not needed, you can just back out. In pictures 2 and 3 a proper flash of SuperSU is shown, note that system-less mode is specified and the boot image is patched, this is what should occur. It is normal for it to loop once or twice, but that is it, first boot could take 10 minutes plus.
Click to expand...
Click to collapse
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Iglooian said:
I really appreciate the help, but I have one question. Do I flash SuperSu and then type the command into the terminal, or do I type the terminal command first?
Thanks again for your help,
Matt
Click to expand...
Click to collapse
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
acejavelin said:
First, a little etiquette lesson, please don't quote long posts (especially the first post) for no reason, at the very least edit it down to only show the relevant parts so people don't have to scroll through a long meaningless quote.
And to answer your question, you enter the terminal command first, then install SuperSU, that is how it is ordered in the first post instructions. If you read the entire first post, it explains what the command does, and logic therefore lets you know it must be done first.
Click to expand...
Click to collapse
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Iglooian said:
Actually, it was unclear what order I was supposed to do it in; we call that a clarifying question, but thanks anyway.
Click to expand...
Click to collapse
Fair enough... I will edit the "How to do it" section to make it more clear.
So is it really so that the Xperia XZ does not have a recovery/bootloader menu?
I have unlocked the bootloader which needed the fastboot which works but now that I want to root the device and need TWRP I am getting nowhere since I can not get the device to go into recovery mode. this is annoying me badly, my phone is basically useless until I am done with this.
Any advice?
kane_1371 said:
So is it really so that the Xperia XZ does not have a recovery/bootloader menu?
I have unlocked the bootloader which needed the fastboot which works but now that I want to root the device and need TWRP I am getting nowhere since I can not get the device to go into recovery mode. this is annoying me badly, my phone is basically useless until I am done with this.
Any advice?
Click to expand...
Click to collapse
During the initial unlocking of the device of course it doesn't carry any recovery. Maybe ought to try powering down your device and press and hold the volume up key while connecting your device to the computer until the blue led is lit that's fastboot mode. Do this fastboot flash recovery recovery name.img then try accessing recovery after that. You now should have a working recovery.
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
You can find the available recovery.img on androplus website https://kernel.andro.plus/tone2.html for your corresponding firmware and androplus kernel fastboot flash boot boot.img.
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
The available instructions are posted on the website. Please make sure you have the perquisites.
Thanks.
Would you recommend running a custom rom or sticking to stock android and run xposed?
also, the first step it say boot into recovery bootloader, I don't understand how i am supposed to do that when there is none in the beginning.
I have tried everything any guide says and it just doesn't seem to work.
The adb says waiting for device as if the device is not there, the one click tool just doesn't do anything.
Idk anymore
kane_1371 said:
I have tried everything any guide says and it just doesn't seem to work.
The adb says waiting for device as if the device is not there, the one click tool just doesn't do anything.
Idk anymore
Click to expand...
Click to collapse
background (look at the date - some content is for Z3 xperias and older that do not have DM-Verity):
https://forum.xda-developers.com/crossdevice-dev/sony/noob-guide-to-sony-ericsson-xperia-t3209012
For the newer phones follow the instructions you find in the device-fora.
Here (after a full wipe) you get started following the instructions written by AndroPlus.
You need the right ROM and TWRP (recovery) for your ROM-version. Look at the changelog.
e.g.: I am on 39.2.A.0.374. There is no kernel for that right now -> I can not get into recovery -> no root for me ATM
fastboot boot TWRP_xy boots the recovery
You will become a "developer" on your device once you tapped seven times on the build number -> then you switch on adb debugging in the developer options
"When you unlock your bootloader you will lose all the DRM features on your device, this makes it valuable to have a backup of the unmodified version stowed away somewhere safe. You will need root level access to create that backup before unlocking. There is a tool called Backup TA which is widely used to create and restore backups of the TA partition. TWRP in XZDualRecovery can do the same. "
What the heck?
I need to backup TA, ok, but I need to have root to do this? ok, but to have root access I need to unlock my bootloader and flash a root boot which messes up with the TA?
It seems like every single one of these posts that I read just make things more confusing.
Why can't there just be a simple step by step that tells you what to do?
NVM, I actually flashed a recovery into the phone by using a combination of one click tool and Quickimage.
God this community need better tutorials and step by steps
Anyway now it is asking me for a password which is a surprise to me
OK past that too, did a backup and no I see that I have nothing but the recovery to boot to, hmmmm still figuring this thing out
It is amazing to imagine how **** is constantly hitting the fan.
The quick image thread has very little explanation and two screen shots which show that they are flashing the image to boot.
So I did exactly that and now I have no Boot but a recovery instead hhahahahahaha.
I am fairly depressed and desperate at this point
Well I somehow managed to install Xplayztation.
As mentioned before the only way possible for me to get a recovery installed was through flashing it on boot and loosing my access to the android at first and then installing a new rom through Twrp.
I have no idea what will the outcome for this be.
Any suggestions?
kane_1371 said:
God this community need better tutorials and step by steps
Click to expand...
Click to collapse
Go ahead!
You will find everything HERE and on
https://forum.xda-developers.com/crossdevice-dev/sony
There is more than plenty on the Z5 and Z3+ foro too...
In the Z5 forum you can really get to the technical beef if you want. The tutorial I quoted is gentle but written at a time when it was easier to root the devices.
The TA-Backup works via a vulnerability that raises the rights temporarily. This is not rooting per se since this does not survive a reboot.
Why can't there just be a simple step by step that tells you what to do?
Click to expand...
Click to collapse
Here on this forum (after a full wipe) you get started following the instructions written by AndroPlus.
or:
https://forum.xda-developers.com/showpost.php?p=70370065&postcount=7
DHGE said:
Go ahead!
You will find everything HERE and on
https://forum.xda-developers.com/crossdevice-dev/sony
There is more than plenty on the Z5 and Z3+ foro too...
In the Z5 forum you can really get to the technical beef if you want. The tutorial I quoted is gentle but written at a time when it was easier to root the devices.
The TA-Backup works via a vulnerability that raises the rights temporarily. This is not rooting per se since this does not survive a reboot.
Here on this forum (after a full wipe) you get started following the instructions written by AndroPlus.
or:
https://forum.xda-developers.com/showpost.php?p=70370065&postcount=7
Click to expand...
Click to collapse
Thanks for the links man.
Well I somehow managed to install Xplayztation.
As mentioned before the only way possible for me to get a recovery installed was through flashing it on boot and loosing my access to the android at first and then installing a new rom through Twrp.
I have no idea what will the outcome for this be.
Any suggestions?
Also I had already unlocked my bootloader when I learned about TA backup.
And then was confused that I am supposed to Root for it to work, so what are my options now?
Are the DRM keys reverseable through flashing my regions latest firmware via the flashtool?
kane_1371 said:
Thanks for the links man.
Also I had already unlocked my bootloader when I learned about TA backup.
Click to expand...
Click to collapse
You are welcome
Your TA-keys are gone. NO WAY to revover them. Do not even try - you will hardbrick your phone.
Follow the links I gave.
OK
Well I have the insurance on it, so if anything ever happens that is not reversible I will bust the phone and get a new one lol.
For now I will enjoy the stuff
It was a lot of trouble but I got what I wanted (moded Spotify app haha )
I want to root my xz too. Did you root it. If you did, how.? Plz reply
Im just gonna ask confirmation New to sony scene and never knew i had to backup the TA partion (Shouldve came here first normally would) but i assume theres no way to recovery DRM keys (i did install Androplus Kernel)
Well yes I did manage to do the work but I imagine the XZ is built in a manner that you can not root it without burning all the bridges behind you however I am basically the only person in this forum that I found to either have rooted their XZ or had to go through these many hassles.
As you can read in earlier posts I did have to backup the TA but by the time I knew about that I had already deleted the TA. The extended permission didn't work for me either so Idk if it was me doing something wrong or Sony going hard against rooters.
Also no TA is not reversible so once you do root and if you don't have the TA backed up don't even go for reinstalling the original rom because it will not work period.
I had to flash my boot and install recovery on that which is not the intended way of using recovery but I couldn't do it any other way, when you do that you basically are left with a paperweight the shape of a phone and then from there I would go to Boot instead of recover since recovery partition was empty and the recovery image was flashed on boot partition and use the recovery to install the rom.
But you should try to follow the step by steps posted in this forum by other people so maybe you won't have to endure the pain I did.
I have to say at this time I really feel like it wasn't even worth it because XZ is a pretty underwhelming phone even though I had a busted Z3 before this I never experienced such a slow phone with that.
XZ is just constantly out of ram and slows down and reboots the rom's shell which is pretty annoying.
So i followed this video: https://www.youtube.com/watch?v=yqhdq_A47DY&feature=youtu.be
I did exactly everything he does in the video, but i always ended up with the same error upon booting.
It would say something like "verification failed. unable to restart your device. the integrity verification has failed.you need to reset your device to factory default settings."
I tried the method multiple times but the same error shows up.
Any idea what could it be? Thank you!:good:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Hello andresg97,
have you tried to follow the instructions as shown in the TWRP Thread?
At least you should be able to boot into recovery, from there you can install TWRP and the the only thing you need to get a working phone back is a ROM, the Renovate ROM works fine for me.
The Tools and ROM I mentioned:
TWRP Thread: https://forum.xda-developers.com/galaxy-s8/development/recovery-twrp-galaxy-s8-exynos-t3595102
TWRP instructions for Installation: https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Renovate ROMThread: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
M3ph15t said:
Hello andresg97,
have you tried to follow the instructions as shown in the TWRP Thread?
At least you should be able to boot into recovery, from there you can install TWRP and the the only thing you need to get a working phone back is a ROM, the Renovate ROM works fine for me.
The Tools and ROM I mentioned:
TWRP Thread: https://forum.xda-developers.com/galaxy-s8/development/recovery-twrp-galaxy-s8-exynos-t3595102
TWRP instructions for Installation: https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Renovate ROMThread: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Click to expand...
Click to collapse
Thank you! It works fine, thank you very much!
To everyone else who had similar problems , FOLLOW THE GUIDE this guy is linking, it works perfectly, i followed two youtubers before asking here, one made me end up with a boot loop, and the other one made me end up with the error upon boot.
KingFoltest said:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Click to expand...
Click to collapse
I have to say I am somewhat surprised at your post. It does not reflect the general attitude that is usually so prevalent in this forum. I wonder why you even posted. All you did was condemn the guy for having tried something without offering anything supportive beyond your comment - "congratulations for having a brick." It would have been better if you just kept your thoughts to yourself if you don't plan on offering anything constructive.
Bricking a samsung device is actually pretty hard to do - and most issues can be overcome. Obviously some bricks are real bricks - but usually via Odin, there is a way to at least return the phone to full stock before either giving up or trying again.
Sorry, I don't mean to harp on you - but I just get frustrated when I see such negativity without any offer of help or support. Hope you never end up in a similar situation - and if you do, I hope whoever reads your post treats you better than you treated the OP.
andresg97 said:
Thank you! It works fine, thank you very much!
To everyone else who had similar problems , FOLLOW THE GUIDE this guy is linking, it works perfectly, i followed two youtubers before asking here, one made me end up with a boot loop, and the other one made me end up with the error upon boot.
Click to expand...
Click to collapse
I'm glad I could help, have fun with your phone
mocsab said:
I have to say I am somewhat surprised at your post. It does not reflect the general attitude that is usually so prevalent in this forum. I wonder why you even posted. All you did was condemn the guy for having tried something without offering anything supportive beyond your comment - "congratulations for having a brick." It would have been better if you just kept your thoughts to yourself if you don't plan on offering anything constructive.
Bricking a samsung device is actually pretty hard to do - and most issues can be overcome. Obviously some bricks are real bricks - but usually via Odin, there is a way to at least return the phone to full stock before either giving up or trying again.
Sorry, I don't mean to harp on you - but I just get frustrated when I see such negativity without any offer of help or support. Hope you never end up in a similar situation - and if you do, I hope whoever reads your post treats you better than you treated the OP.
Click to expand...
Click to collapse
I understand.. I must be furious at that moment how somebody could possibly do something to a brand new phone. I am sorry though, will keep my opinions to myself, if they aren't constructive.
KingFoltest said:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Click to expand...
Click to collapse
The only thing he shouldn't of done was follow a youtubers guide on rooting, all they do is read xda and make a video of it, should of came here first and asked questions, next time he'll know.
andresg97 said:
Thank you! It works fine, thank you very much!
To everyone else who had similar problems , FOLLOW THE GUIDE this guy is linking, it works perfectly, i followed two youtubers before asking here, one made me end up with a boot loop, and the other one made me end up with the error upon boot.
Click to expand...
Click to collapse
hello!
I had the same verification problem you had, and followed these steps to solve it.
I have wiped my s8, and flashed as well as initialized TWRP on my phone. Now in TWRP recovery I'm trying to transfer the Renovate flashable zip, but every time I try to transfer the file the transfer fails. Doing it by drag n drop in windows the transfer freezes midway, and then the connection to the pc is cut, and I have to reboot the phone to reestablish it. After that I have a corrupt zip in like 70 % of the actual size.
Doing it by push command in ADB gives me an error saying my device is out of space after transferring around 60-70%, even though there's ~52 gb free space.
Do any of you have any idea why this happens? I'm able to transfer other, smaller files to the phones internal storage. Is there some setting limiting what I can transfer?
mocsab said:
I have to say I am somewhat surprised at your post. It does not reflect the general attitude that is usually so prevalent in this forum. I wonder why you even posted. All you did was condemn the guy for having tried something without offering anything supportive beyond your comment - "congratulations for having a brick." It would have been better if you just kept your thoughts to yourself if you don't plan on offering anything constructive.
Bricking a samsung device is actually pretty hard to do - and most issues can be overcome. Obviously some bricks are real bricks - but usually via Odin, there is a way to at least return the phone to full stock before either giving up or trying again.
Sorry, I don't mean to harp on you - but I just get frustrated when I see such negativity without any offer of help or support. Hope you never end up in a similar situation - and if you do, I hope whoever reads your post treats you better than you treated the OP.
Click to expand...
Click to collapse
I felt exactly the same, and even irritated! Thanks for pointing it out to the guy in such a professional way
KingFoltest said:
Shouldn't have done it. The phone is less than a month old and you are expecting everyone to have everything for it. Congratulations on having a brick.
Click to expand...
Click to collapse
You must be fun at parties. You should just leave xda with that attitude. I rooted day 1, no issues.
Sent from my S8+Rooted
Brava27 said:
You must be fun at parties. You should just leave xda with that attitude. I rooted day 1, no issues.
Click to expand...
Click to collapse
Same parties you always arrive late to? Sure thing mate
Does not work for me
M3ph15t said:
Hello andresg97,
have you tried to follow the instructions as shown in the TWRP Thread?
At least you should be able to boot into recovery, from there you can install TWRP and the the only thing you need to get a working phone back is a ROM, the Renovate ROM works fine for me.
The Tools and ROM I mentioned:
TWRP Thread: https://forum.xda-developers.com/galaxy-s8/development/recovery-twrp-galaxy-s8-exynos-t3595102
TWRP instructions for Installation: https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Renovate ROMThread: https://forum.xda-developers.com/ga...ovate-ice-g950-g955-android-7-0-aqdg-t3598040
Click to expand...
Click to collapse
Hey! Can u help me please, it does not work for me! My skype is den170602
A little help please?
DKC11 said:
Hey! Can u help me please, it does not work for me! My skype is den170602
Click to expand...
Click to collapse
It doesnt work for me either... My first initial attempted install of twrp gave me a pass but the phone would not boot into twrp. It is stuck at the galaxy S8+ logo... I can boot into download mode and thats all... holding the power bixby and volume up buttons does nothing. I have tried to flash twrp several times now and keep getting a fail in odin. I have also tried flashing a stock rom several times as well but odin fails at that too... followed xda giudes for both procedures and no luck. Any ideas or help would be greatly appreciated... Thank You
Hi all,
I found this thread because I did the exact same thing.
I flashed TWRP via ODIN, and came up with that screen about data not being verified, only option was to click "Erase".
Thankfully, I powered down the phone, booted to Recovery (Samsung), and displayed:
"Appling Multi-CSC-, applied CSC-Code : TEL (Telstra Aus) blah blahblah..
Successfully verify for dmverity hash tree."
Rebooted, and all was ok again..
Nearly passed out from shock though.
I did a Helium backup of my app data, but not the other files on my phone, which I am doing right now!
Still not sure what I did wrong with flashing TWRP though. It flashed fine...
numloxx1978 said:
Hi all,
I found this thread because I did the exact same thing.
I flashed TWRP via ODIN, and came up with that screen about data not being verified, only option was to click "Erase".
Thankfully, I powered down the phone, booted to Recovery (Samsung), and displayed:
"Appling Multi-CSC-, applied CSC-Code : TEL (Telstra Aus) blah blahblah..
Successfully verify for dmverity hash tree."
Rebooted, and all was ok again..
Nearly passed out from shock though.
I did a Helium backup of my app data, but not the other files on my phone, which I am doing right now!
Still not sure what I did wrong with flashing TWRP though. It flashed fine...
Click to expand...
Click to collapse
Sounds like you didn't wipe data or flashing the dm-verity disabler. Look here for more info https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Sjant said:
Sounds like you didn't wipe data or flashing the dm-verity disabler. Look here for more info https://forum.xda-developers.com/showpost.php?p=72004368&postcount=3
Click to expand...
Click to collapse
I thought that was for new install phones only?
I don't want to wipe my phone, I want to leave all the data on it if possible.
DKC11 said:
Hey! Can u help me please, it does not work for me! My skype is den170602
Click to expand...
Click to collapse
https://forum.xda-developers.com/ga...pment/recovery-twrp-galaxy-s8-exynos-t3595102
Follow the steps exactly step by step.
Enjoy!
Do these exact steps, Do not miss.
1. Reboot to recovery.
2. Do a data wipe (WIPE>FORMAT DATA) And Say "Yes"
3.Go to Reboot and Reboot back to recovery.
4.Download DM Verify Disablerhttps://build.nethunter.com/android-tools/no-verity-opt-encrypt/ , Get the latest.
5.Copy in to the phone and flash it.
6.Go to Reboot and Reboot back to recovery.
7.Now Flash any rom as you wish.
8.Make Sure to Wipe Dalvik, Cache after.
Enjoy!!
Hi all,
Please help me to root my s8+ through TWRP. Every time when I patch this via odin my phone says 'unable to restart your phone. the integrity verification has failed. you need to reset your device to factory default settings. this will erase all your data.'. I have thoroughly read this thread but nothing resolve my issue. I have the exynos model purchased from UK.