Related
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
yahboyvictorr said:
Hello, I am new to xda, so if this is in the wrong place, I apologize. Also, I am new to this rooting stuff, so I do not now much about it.
Anyway, I have a just rooted Xperia Z3 D6653 Android Device and I was in the middle of installing TWRP (which successfully installed) and my phone got stuck in a boot loop. I have searched every where for a fix but nothing is working. I tried to factory reset and wipe the dalviq cache on recovery mode, but it says it always fails. I still try to reboot the phone into the system, but it keeps looping. Could someone please help me out? Any help would be really appreciated.
Also my bootloader is unlocked
And I am running Lollipop.
Thanks
Click to expand...
Click to collapse
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Jkay7 said:
Fist of all: welcome to xda and thanks for actually posting in the right thread
Now, your problem: what did you do exactly?
You downgraded to 4.4.4, rooted, and then installed recovery? Which guide did you follow and what programs did you use?
Generally speaking what you should be able to do:
Turn phone off (long vol+ & power press)
Prepare flashtool by selecting your .ftf of choice (recommendable to use 4.4.4 so you can get it right then) and checking clear data and cache
Then let it prepare everything
Hold down vol- when asked tip and plug your phone in
You'll get a fresh start!
Best of luck!
Just one thing: you first unlocked your phone and then rooted it? If so that'd be a pitty, cause that'd mean you lost DRM keys and functions. Why did you exactly unlock it if I may ask?
Edit: you said you are on LP, therefore I assume you are unrooted, which would show why it didn't work
I advise you to follow this guide: http://forum.xda-developers.com/showthread.php?t=3017056
As it shows everything really well
Click to expand...
Click to collapse
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
yahboyvictorr said:
Well I tried what you said, but I cannot find a link. So I just downloaded a random one (its the right version) but in flashtool it just keeps coming up with errors. I followed the steps from these 3 websites
http://howtorootmobile.com/root-sony-xperia-z3-easy-steps/#top_ankor
http://howtorootmobile.com/unlock-bootloader-sony-xperia-z2/
http://howtorootmobile.com/guide-install-twrp-recovery-sony-xperia-z3/
What I was installing TWRP and the last step was to type in fastboot reboot on the command window, that is when my Xperia Z3 got stuck in a boot loop. I dont really know what a ROM is and how to properly flash stuff, so I probably made a mistake while installing TWRP and thats why I get errors trying to wipe files using it.
Also, I did not downgrade before I rooted and unlocked bootloader and installed TWRP. I didnt even know you had to downgrade. Would that be a reason why the bootloop occured?
Click to expand...
Click to collapse
Yes it is definitely a reason. Follow the steps from the guide I linked you step by step, it works 100%
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.
First off, i'm sorry if the title is misleading and/or belong in the wrong part of this forum.
So, I'm late to the party, just got myself a Z5 E6653 and when I look for guides on how to obtain root they kind of out-of-date. So i'm here to make sure the path I choose to follow will be the correct one as I dont want to lose my TA partition. As far as I know, according to this guide to back up my TA partition I have to downgrade to Lollipop, but I found something interesting about backing up TA partition on Marshmallow using dirtycow method (sorry Nougat users).
So, the steps I'm proposed is, if my device is already on stock MM unrooted, locked bootloader.
1. Go here Sony cross-devices development and download file called backupTA_v2.zip this shouldnt makes us need to downgrade
2. Run the BackupTA.cmd file if you're on windows
3. There will be errors about dirtycow failed but the script automatically retry, me myself got screen-full of retries before the script actually backed up my TA partition and you'll be presented with .imgfile called TA_devicemodel_somenumbers_timestamp.img about 2MB in size (am i correct so far? this is why i want to make sure this will work)
4. Save your file in a very secure place.
That concludes the Backup TA part of rooting process am I on the right path so far?
To get unlocked bootloader according to this :
Given that you have downloaded flashtool and installed the drivers in the \drivers folder in flashtool installation
!!THIS WILL WIPE ALL DATA!!
1. Click the BLU button at top then open Sony developer website
2. Select device and follow instruction until you get a key
3. Paste the key to flashtool
4. THAT'S IT?
Now after this we can use fastboot command to flash kernel and the kernel includes recovery.
Are these steps correct so far?
I might as well add these here.
To get kernel and recovery up and running, I'll be taking androplus kernel for example, I'm assuming it works with stock ROM.
1. Get the kernel .zip here at Androplus homepage
2. And download latest TWRP recovery from androplus download page, at this time of writing it should be TWRP-3.0.2.2-e6653.img
3. Notice that it's in .zip format which we cannot use yet since we don't have custom recovery.
4. Open the zip file you just downloaded and you should see boot.img That's your brand new shining kernel, extract it outside put it in a folder along with your favorite fastboot.exe file
5. Go to fastboot, as far as I know you go to fastboot by turning off the device -> hold volume down then plug USB cable. (see note)
6. First, according to Androplus page, flash the kernel first using the command
Code:
fastboot flash boot boot.img
7. Then the recovery
Code:
fastboot flash recovery TWRP-3.0.2.2-E6653.img
8. Reboot by unplugging the USB cable
Note: some interesting thing I found while trying to enter fastboot or flashmode that it might not work if your USB port is powered How to tell if your port is powered? I'm not sure. You will have to change port and hope for the best ^_^
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
sceryavuz said:
Yes. Explained many times. Not hard to do.. 4-5 minutes then WHOLA!
Click to expand...
Click to collapse
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
webslasher said:
Ahaha, sorry. Those guides are "old" in android way of changing things very fast, and I haven't seen a guide which includes backup TA partition on marshmallow so I wasn't sure it'd work correctly. Now that I know it worked, I can proceed to unlock my bootloader.
Any tips or Kernel/Rom I should use for first time flash?
Click to expand...
Click to collapse
LineageOS, CarbonROM, eXistenZ, SunKernel..
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
sceryavuz said:
LineageOS, CarbonROM, eXistenZ, SunKernel..
Click to expand...
Click to collapse
I will try Existenz as I want to keep it stock looking, thanks!
bosquarid said:
Dear both,
I was just doing quite the same, so it was nice to read the short summary. Honestly, I'm doing these "Flash ROM stuff" very rarely, so I'm not 100% confident how to bring back those DRM/TA. I recorded it - the device came with Android LP 5.11, so this was easy done by iovyroot.
Anyway, I have the TA-backup - so I'm also going to unlock the Boot Loader now. :good:
Good to know I spend a day on reading so many related stuff, and it could be done in 4-5 min
Click to expand...
Click to collapse
I'm glad to find someone that is going to go through these procedures too! I will also proceed to unlock my bootloader what rom and kernel do you plan to flash?
Hi, thanks for this. I just got the Z5 today so my first port of call was coming here and finding out how to root it. I previously had the Z2 and Z2 tablet which I rooted last year with the help of the members here, I hope the process for this isn't too different for this one. I think I forget more than I remember so the guide is helpful.
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I never thought that this would happen, especially after 6 years of being an ardent flashaholic but here I am like another noob requesting for guidance.
So it started a few days back when the Flashaholic in me wanted something to divert my mind from the monotonicity of a good ROM.I was using "[8.1.x][WEEKLIES] CarbonROM | cr-6.1 [bacon]" Rom on my 3 year old bacon happily when I decided to try "Crdroid ROM for OnePlus ONE crdroid-4.6".
As mentioned in the instructions I followed the steps to each word i.e. wipe,flash rom and then gapps (using modded twrp-3.2.1-K2-bacon.)and the ROM booted fine.I setup it as usual post boot however I faced few reboots which made me doubt myself so i thought of reflashing the same ROM again but the butter fingers got the best of me and while selecting partitions to WIPE( I guess) I selected some incorrect partition and after the flash my phone went into bootloop..
I tried to boot into recovery but I wasnt able to so but I knew I could boot into recovery using Fastboot so I reflashed the recovery while in fastboot mode and ran fastboot boot TWRP.img as I wasnt able to boot into recovery with VolumeDown+Power.I tried to fetch the nandroid backup but to my astonishment it was gone and my /data partition was wiped clean.I blame myself as I must have done something wrong as I was panicked.
Since then(last sunday)my phone has been in bootloop and doesnt start in recovery unless I boot recovery from fastboot. I have spent countless hours to fix it and the things I have tried already are mentioned below
1)Flash Stock rom (CM11,CM12,CM13)
2)Erase and flash persist.img
3)Flashed CM13 snapshot or bacon_firmware_update_2015_05-15_DI.3.0.c6-00241.zip followed by RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
4)Flashed coloros and then stock rom(CM11,CM12,CM13) or RR 5.8.5 ,RR 6.0 ,Carbon rom 6.1 and c-droid 4.6
I have gone through this awesome guide ultimate-answer-to-bacon-flavored- by @Timmmmaaahh ,other noob friendly guides indexes , compilations ,threads on softbrick and hardbrick topics and used almost every tool created for one plus one.
I have ruled out below
1)Volume button not working as I can boot into fastboot fine using VolumeUp+Power button
2)Battery not working as my phone can stay in fastboot for pretty much a day with 50% battery or bootloops throughtout the day
I am really out of my depth and I am trying to find where I had kept my nandroid backup on Laptop/Drive but I dont think even that can help me now.I have lost a lot of precious and Important data due to my panicking and wouldnt want to lose my phone so any help and guidance would be really appreciated.
Hopefully I am posting in the correct place and havent breached any XDA rules!Aplogies in advance if I have
you are sure, that you have flash thr TWRP and not only load TWRP via sideload into the ram?
please post the command, which you have send to the phone
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Stupid thing it seems but try different micro usb cable
vedanth123456 said:
So I use below command to install the twrp from fasboot
fasboot flash recovery <path/twrp file>
Also I've tried to flash twrp in recovery from twrp by selecting image file option but it doesn't boot into recovery ever
I've tried twrp 2.7,2.8,3.0,3.1 and 3.2 as well on every rom that I've flasher given the compatibility.
to boot into recovery as it's not accessible I use below command
Fastboor boot <path/twrp file>
Click to expand...
Click to collapse
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Because I had bricked my phone a few months ago and I changed my USB cable and it worked perfect
kallum7 said:
Stupid thing it seems but try different micro usb cable
Click to expand...
Click to collapse
Thanks mate..I did try that but it didn't endure fruitful results
Timmmmaaahh said:
Okay, let's optimize your environment first. Make sure the path to your adb is c:\adb (don't flash stuff like "c:\users\dinky doodle\my awesome downloads\android shizzle\recovery manizzle"). Use the amazing 15 seconds adb installer and let it install the drivers as well. @kallum7 makes a good point, do try that.
Use the TWRP recommended in my guide and follow the clean flash steps (including CM13 step again).
More importantly: check md5 hashes on all your downloads. You really want to avoid flashing a corrupted recovery download. Only continue flashing ROMs once you have a stable TWRP installation going. If it's not properly booting to TWRP, do not bother flashing anything else.
When successfully booted in TWRP, make sure MTP is enabled under mount and connect it to your PC. Browse for possible backups via your computer. If you can't find any, you've probably wiped internal memory. If you didn't make a copy to your computer, the data is most likely gone forever (sorry).
Panicking is indeed a bad idea, we've all been there and it's an excellent learning process (you'll appreciate your failures later, lol). It's better to work step by step slowly, make sure you read everything thoroughly. When in doubt, just post here and we'll follow up. We'll get there, don't worry.
---------- Post added at 08:51 AM ---------- Previous post was at 08:47 AM ----------
Oh and rename the recovery file to recovery.img and place it in your adb folder to avoid any complications. Less = more!
Click to expand...
Click to collapse
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
vedanth123456 said:
Hi mate,So I pulled an all nighter yesterday and was somehow magically able to boot in TWRP.I don't remember what I did but I booted into TWRP 2.8.7.0 and the first thing I did was check if any nandroid backup was there but I was disappointed to see my /data with free 55326 MB also no backups on my drive.All my data is gone and I can't curse myself enough for that,moving on so I did manage to gather my sense and flashed TWRP 3.2.1-K2 and flashed RR-O-v6.1.0 but the phone goes into boot loop again and again.
Since then my phone is displaying some weird behavior so if I unplug my device and start my phone the phone won't boot and wont go past oneplus one splashscreen so I thought my battery is gone but if I can go in fastboot mode or TWRP mode while being plugged in and unplug my device but my phone wont die,it'll be in the respective mode for ages.
I do have a clean setup (K:\oneplus\adb\) that's how I stayed away from this mess since ages but I guess I got too cocky.
I have religiously followed your thread and it has helped me a lot so once I am home I will check the TWRP part again and get back with the results.
Once again..thanks for your guidance.
Click to expand...
Click to collapse
This is weird I just restarted my phone to see if it magically starts but it went into bootloop(displaying splashscreen not boot logo) in contrast to earlier when it died instantly when not plugged in also I can't boot into my recovery now!
Once I am plugged in and the phone is on bootloop and if I hold the volumedown+Powerkey it boots into TWRP properly..
This is just weird and I havent seen this behavious in the past three years of using my old lovely bacon
Try using the color os toolkit https://steemit.com/oneplus/@delusionalgenius/how-to-unbrick-oneplus-one-bacon and even though it says do not use if it is soft bricked use it this helped me
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Timmmmaaahh said:
Sorry for getting back rather late (again). I'm in the middle of organizing an event and it's leaving very little XDA time. Anyway...
Isn't a hardbrick tutorial kinda agressive? I mean, I've used it before, and it's excellent, but then my device was actually hardbricked. I'd rather go for the 'back to stock' method first, setting the system back to CM13, which is a much better base for further flashing compared to ColorOS.
@vedanth123456 if you didn't take any action yet then I suggest following this thread (skip step 4!!).
The deal is to flash all images from fastboot. This will – naturally – wipe every single partition on your device!
I suggest doing the fastboot flashing manually (copy paste each command one by one) to avoid your device getting its bootloader locked. You DO NOT want to lock the bootloader on a OnePlus One if you ever wish to unlock it again.
When you successfully booted CM13, go though its initial setup, [disable recovery protection in system or developer settings] (it's been so long since I've experienced this process that I'm not sure if this option was present in CM13; if you can't find it, don't mind), get back to fastboot mode and flash K2 TWRP. First thing to do at this point: create a full nandroid backup of your working CM13 setup and copy it externally. ROM flashing should now be successful. If not, I'm afraid your hardware is failing. Do try several ROMs.
Don't forget to check those md5 hashes!
By the way, your /data is supposed to be empty after a factory reset. /data merely contains settings and app data (user added information). Backups and user media go to the /sdcard partition, which is known as internal memory. If I may suggest a ROM, go for CrDroid. It's more stable compared to RR, it's still actively developed and it has similar features.
Click to expand...
Click to collapse
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
vedanth123456 said:
Hi mate
Apologies for not acknowledging your message and not replying back earlier. I've been traveling using a spare phone and things just aren't the same on it.
To give u an update, I tried the steps mentioned in the link (which I had tried previously as well) but the phone didn't boot. Same bootlooping and issue with the twrp.
So I went through other forums and links and finally found an exe that worked.!!!!!! So the exe seems to be an modified version of the one mentioned in the hard brick method and has been created by someone else (NOT ME!!)
My phone after many moons has booted and its on the good old cyanogen CM 11.0 XNPH44S. I've tried numerous roms on this bad boy but there is some beauty in the simplicity of the good old roms.
My phone battery is charging pretty slowly and wifi is not turning on so I'm still tensed but the fact that it booted is a small victory. I would want to upgrade to a stable rom once my phone is charged and not displaying erratic behavior so I'll wait for a day and see how it works but I'll want to upgrade to a slightly latest rom probably not a battery hogging one.
I believe I'll have to first install an old twrp followed by nandroid backup(save on every goddammed devices I own), then some CM snapshot and finally the rom but please can you confirm and suggest.
Click to expand...
Click to collapse
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Try bacon root toolkit you can perform most of the things very easily.
chineel said:
Try bacon root toolkit you can perform most of the things very easily.
Click to expand...
Click to collapse
Hey man, thanks for pinching in. I'm personally not a fan of these toolkits as one can accidentally lock the bootloader and I prefer manual style because it's educational and you see more of what's going on. It's like I preferred DOS over Windows 3.11 back in the day. That's pretty much the same, right?... ?
Timmmmaaahh said:
Heya!
Well, this is legacy material so I kinda forgot what TWRP worked best for the older ROMs (2.8?). The latest TWRP should be backwards compatible and support CM11 so you can give that a whirl first. You're just making a backup (no write actions) and TWRP's are easily replaced with other version so there ain't much to lose. Anyway, glad you got it running! I'd still go with the CM13 flash before moving to one of the modern ones. If you encounter more bootloops, that same exe should recover it for ya. By the way, can you PM me a link to that exe? Who knows, it might come in handy one day.
As a stable up-to-date ROM I can really suggest crDroid. I've been using it myself for a few weeks now. @chineel is a talented and devoted dev.
Click to expand...
Click to collapse
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
kallum7 said:
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
---------- Post added at 05:34 PM ---------- Previous post was at 05:20 PM ----------
you are going to have to use the colour os toolkit to get the imei info back there is nothing else you can do
Click to expand...
Click to collapse
Mate ,can you please help me with the link ?
I know I can google it but I just dont want to take chances anymore
vedanth123456 said:
Hi Mate,
My perils seem not to end.So after the last update I tried to start my phone and it started but as soon as I removed the power cord the phone switched off.
I realized that the issue was with the battery so I got it replaced in one of the OnePlus Authorized service center.
The new battery with only one month warranty started just fine and I could see the phone hold power without the charger attached.So I reached home and did the below
1)Flash Twrp
2)Flash CM 13 snapshot
3)Flash cdroid and gapps
4)Reboot phone
Everything seems to work as expected other than the goddamn network and the wifi.My phone has no IMEI and ofcourse I have no EFS backup stored cause of my previous fiasco.
Any ideas mate,I see forums where itts told to install color os and then cm11 and then something but I dont want to risk anything anymore .
Any advice ?
Click to expand...
Click to collapse
I'd hate to say I told you so ?
Don't worry too much. The cool thing about flashing with Android is that there's always other ways to get to a working system. Plus, having a fizzled up system is how you'll learn the most about how this all works. You'll be a pro in no time. I personally got seriously into troubleshooting with a hard bricked OPO that had a wasted flash chip. Believe me when I say that's a whole other world of pain.
One question: did you wipe system/data/caches between the CM13 and the crDroid flash? That's kind of important. It would also be useful to mention the versions of everything.
I have no first person experience with broken EFS partitions but according to what I've read you'll indeed have to get ColorOS running. You could try wiping everything again and flash CM13 to see if that boots fine (with working connectivity) but I'm afraid you'll have to go through the whole works: wipe all, flash or fastboot flash ColorOS, get it running (verify IMEI), flash TWRP and backup EFS (MAKE AN EXTERNAL COPY), wipe all again, flash CM13, get it running, wipe all again, flash crDroid + Gapps, wipe caches and boot to a (hopefully) working system. If EFS broke again you can simply restore the backup made earlier instead of starting over.
Mind that when I say wipe all, it doesn't have to include internal memory or you'll be wiping backups you might need later on.
Alright, here goes your 27th attempt. Good luck! ?
mate here is the link https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 even though it says do not use on soft brick devices in your case you are going to have to