Hello guys, I had root when I had androd 4.4.4 but uprading it to 5.0.1 made my root ineffective. When I open my app list I can still see there is SuperSU but when I try to open, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upraded to android 5.0 you need to manually re-roo - consult the relevant forums for your device."
Well thats why I'm here. I googled the "how to root android 5.0.1 on linux" term but there wasnt any way to do it.
I hope you guys can help me.
Conixcit said:
Hello guys, I had root when I had androd 4.4.4 but uprading it to 5.0.1 made my root ineffective. When I open my app list I can still see there is SuperSU but when I try to open, it says "There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upraded to android 5.0 you need to manually re-roo - consult the relevant forums for your device."
Well thats why I'm here. I googled the "how to root android 5.0.1 on linux" term but there wasnt any way to do it.
I hope you guys can help me.
Click to expand...
Click to collapse
Download the SuperSU zip file (google for it) an then install it from recovery. I assume you have a custom recovery and the android sdk(adb + fastboot) on your linux desktop.
Other option is to install a custom ROM with the SuperSU already installed. I am running Cataclysm rom.
Hope it helped!
nunojsa said:
Download the SuperSU zip file (google for it) an then install it from recovery. I assume you have a custom recovery and the android sdk(adb + fastboot) on your linux desktop.
Other option is to install a custom ROM with the SuperSU already installed. I am running Cataclysm rom.
Hope it helped!
Click to expand...
Click to collapse
A small correction:
nunojsa said:
I assume you have a custom recovery and the android platform-tools (adb + fastboot) on your linux desktop.
Click to expand...
Click to collapse
(To get adb/fastboot, most Linux distros have them packaged outside the android-sdk - android-sdk is mostly used by app devs. Most people will only use adb or fastboot, thus have no need for the sdk, which brings heavy java deps)
@Conixcit , http://forum.xda-developers.com/google-nexus-5/#root - easy enough.
At least for Ubuntu based distros you can
1. Install adb and fastboot by going the terminal and entering:
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
(Edit: that is supposed to be a colon followed by a p)
sudo apt-get install android-tools-adb android-tools-fastboot
2. Enable debugging in developer options
3. Type in the terminal:
sudo adb start-server
adb reboot-bootloader
fastboot oem unlock
4. Download the latest version of twrp and the supersu.zip for the nexus 5 (hammerhead)
5. Rename the twrp file "recovery.img" and move it into your home folder
6. Type into the terminal:
fastboot flash recovery recovery.img
7. Let it do its thing and then turn it on. Drag your supersu.zip into a folder on your phone (somewhere where you find it)
8. Type into the terminal:
adb reboot-bootloader
9. Use the volume buttons to scroll down to recovery then short press the power button. Once booted into recovery, choose install, find SuperSU and swipe to install
9. Power on the phone and go into SuperSU and check if the binaries need to be updated and if they do say yes and when it asks you to reboot, do so.
Hope that helps
awsumatt said:
At least for Ubuntu based distros you can
1. Install adb and fastboot by going the terminal and entering:
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
(Edit: that is supposed to be a colon followed by a p)
sudo apt-get install android-tools-adb android-tools-fastboot
2. Enable debugging in developer options
3. Type in the terminal:
sudo adb start-server
adb reboot-bootloader
fastboot oem unlock
4. Download the latest version of twrp and the supersu.zip for the nexus 5 (hammerhead)
5. Rename the twrp file "recovery.img" and move it into your home folder
6. Type into the terminal:
fastboot flash recovery recovery.img
7. Let it do its thing and then turn it on. Drag your supersu.zip into a folder on your phone (somewhere where you find it)
8. Type into the terminal:
adb reboot-bootloader
9. Use the volume buttons to scroll down to recovery then short press the power button. Once booted into recovery, choose install, find SuperSU and swipe to install
9. Power on the phone and go into SuperSU and check if the binaries need to be updated and if they do say yes and when it asks you to reboot, do so.
Hope that helps
Click to expand...
Click to collapse
Any debian based distro .... their, fixed that for you .... ubuntu is based and built from debian.
Sent from my rooted RCT6203W46 using xda-dev app
awsumatt said:
At least for Ubuntu based distros you can
1. Install adb and fastboot by going the terminal and entering:
sudo add-apt-repository ppahablet-team/tools && sudo apt-get update
(Edit: that is supposed to be a colon followed by a p)
sudo apt-get install android-tools-adb android-tools-fastboot
2. Enable debugging in developer options
3. Type in the terminal:
sudo adb start-server
adb reboot-bootloader
fastboot oem unlock
4. Download the latest version of twrp and the supersu.zip for the nexus 5 (hammerhead)
5. Rename the twrp file "recovery.img" and move it into your home folder
6. Type into the terminal:
fastboot flash recovery recovery.img
7. Let it do its thing and then turn it on. Drag your supersu.zip into a folder on your phone (somewhere where you find it)
8. Type into the terminal:
adb reboot-bootloader
9. Use the volume buttons to scroll down to recovery then short press the power button. Once booted into recovery, choose install, find SuperSU and swipe to install
9. Power on the phone and go into SuperSU and check if the binaries need to be updated and if they do say yes and when it asks you to reboot, do so.
Hope that helps
Click to expand...
Click to collapse
Here is the question, will I lose my data after step 6 ?
Second ;
Can I install SuperSU. zip directly command line without twrp. I don't like recovery things.
My meaning is ; can I install the SuperSU.zip with "fastboot flash recovery SuperSU. Zip " or something like that. I've installed Android L manually, so first 5 step is already done.
Conixcit said:
Here is the question, will I lose my data after step 6 ?
Second ;
Can I install SuperSU. zip directly command line without twrp. I don't like recovery things.
My meaning is ; can I install the SuperSU.zip with "fastboot flash recovery SuperSU. Zip " or something like that. I've installed Android L manually, so first 5 step is already done.
Click to expand...
Click to collapse
"fastboot oem unlock" is what wipes the /data partition. Flashing a recovery only replaces the recovery.
You can't flash a zip in fastboot, and sideloading the zip probably won't work if you're on the stock recovery. It's best to flash a custom recovery anyways since it lets you do backups (important if you have root access) and flash other things that you may want to.
Elluel said:
"fastboot oem unlock" is what wipes the /data partition. Flashing a recovery only replaces the recovery.
You can't flash a zip in fastboot, and sideloading the zip probably won't work if you're on the stock recovery. It's best to flash a custom recovery anyways since it lets you do backups (important if you have root access) and flash other things that you may want to.
Click to expand...
Click to collapse
Well we have a problem here: I wanna root my phone but as you say I need to install custom recovery first. But as you said again I need rooted phone.
So : how I'm gonna do that ?
As I said before ' I've already did "fast OEM unlock" step.
So my question is :
will I lose any data while installing custom recovery via adb (terminal)
I'm saying that again : fast OEM thing is already done.
Conixcit said:
Well we have a problem here: I wanna root my phone but as you say I need to install custom recovery first. But as you said again I need rooted phone.
So : how I'm gonna do that ?
As I said before ' I've already did "fast OEM unlock" step.
So my question is :
will I lose any data while installing custom recovery via adb (terminal)
I'm saying that again : fast OEM thing is already done.
Click to expand...
Click to collapse
Huh?
- You need an unlocked bootloader to flash a custom recovery (which you do, fastboot oem unlock)
- You need a custom recovery to flash SuperSU for root access
I already answered your question in my previous post. Again: fastboot oem unlock is what wipes the /data partition, flashing a recovery using fastboot does not.
I rooted my phone on 5.0.1 without problems. Maybe try a different version of CF-Autoroot or do it on a computer running Windows.
Sent from my Nexus 5 using XDA Free mobile app
KodRoute said:
I rooted my phone on 5.0.1 without problems. Maybe try a different version of CF-Autoroot or do it on a computer running Windows.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Windows is not necessary since adb and fast boot are available on all platforms.....
#stayparanoid
Elluel said:
Huh?
- You need an unlocked bootloader to flash a custom recovery (which you do, fastboot oem unlock)
- You need a custom recovery to flash SuperSU for root access
I already answered your question in my previous post. Again: fastboot oem unlock is what wipes the /data partition, flashing a recovery using fastboot does not.
Click to expand...
Click to collapse
Use this app won't wipe data and can also reset tamper flag
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
Use this app won't wipe data and can also reset tamper flag
https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Except you need root access to use that in the first place.
His bootloader is already unlocked.
That app is for those that already have root access, but want to relock and unlock the bootloader from within Android for possible security reasons.
Elluel said:
Except you need root access to use that in the first place.
His bootloader is already unlocked.
That app is for those that already have root access, but want to relock and unlock the bootloader from within Android for possible security reasons.
Click to expand...
Click to collapse
I used two apps to unlock and flash recovery. I'm trying to remember what the other was. My kid broke my laptop and I unlocked n rooted without a PC.
Sent from my Nexus 5 using XDA Free mobile app
31ken31 said:
I used two apps to unlock and flash recovery. I'm trying to remember what the other was. My kid broke my laptop and I unlocked n rooted without a PC.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Towelroot was used to gain root access via a kernel exploit. It has long since been patched and is now irrelevant. The only methods now require you unlock the bootloader.
Damn it, Elluel already told the OP what he needs to do.
Everybody else stop. You're causing more confusion by saying **** like "towelroot" or "cf auto root".
There's nothing simpler than flashing a custom recovery, and then the supersu flashable zip.
If OP needs to help to learn how to push a file to the device... that's has been answered in other threads a thousand times in this forum.
Hello Again,
Almost 3 months has passed and now my device on android 5.1
And again I have to root my device I found guide exatchly for me but somehow It didn't gone fine.
Guide : http://www.androidpit.com/how-to-root-nexus-5-on-android-lollipop
Well I even done CWM step, I was in CWM I did install SuperSU 2.46.zip and I did fix the root question.
But Root Checker says My Device isn't rooted. What is I'm doing wrong ?
@beekay201
@Elluel
Conixcit said:
Hello Again,
Almost 3 months has passed and now my device on android 5.1
And again I have to root my device I found guide exatchly for me but somehow It didn't gone fine.
Guide : http://www.androidpit.com/how-to-root-nexus-5-on-android-lollipop
Well I even done CWM step, I was in CWM I did install SuperSU 2.46.zip and I did fix the root question.
But Root Checker says My Device isn't rooted. What is I'm doing wrong ?
@beekay201
@Elluel
Click to expand...
Click to collapse
Tell you what, my hammerhead is still at 5.1 stock, non-rooted yet. In like 2 or 3 hrs I'll be home, and I'll write down the steps I'll use to root.
Related
ok guyz
I have this phone (with CM11S updated) since a month and finally, only from yesterday, I managed to get access to the fastboot command.
Via windows 7-64 there was no way do do this.
I've installed a windows 8 virtual machine and it works fine.
Installed adb+fastboot
downloaded bacon image (renamed twrp.img)
installed universal naked drivers
downloaded supersu zip
I followed the classic procedure to root the phone and
http:
//s29.postimg.org/nwypa3lfr/Catturaz.png
as per the screenshot, the result seams to be "OKAY", but when I reboot on recovery, I have already the original and unrooted "simple recovery"; then I cannot install supersu
why the hell !!!
Settings > About phone > Tap on Build number 7 times to enable Developer options.
Then go back to Settings > Developer options > disable Update recovery with system updates
Holy Cow!!!1!!
I think i've solved
I think just have solved, by a simple trick:
No needed to flash the recovery; simply when in fastboot, do not flash the recovery but reboot loading the new (and temporary) recovery. Whit this simple trick you are able to install the supersu.
then summing up:
enter on the command line adb reboot bootloader
(wait for a second and on the phone screen appears ###fastboot...)
enter on the command line fastboot boot twrp.img
(wait 5 to 10 seconds and appears the teamwin bacon recovery)
press install and load the supersu zip previously loaded on the phone
reboot
enter on the supersu app and DEselect "Respect CM’s root Policy"
et voilà
Of course the teamwin recovery is NOT installed on the phone and you already have the OLD simple recovery , but the phone is rooted and YOU HAVE THE POWEEEER!!!1!
luasso said:
Holy Cow!!!1!!
I think i've solved
I think just have solved, by a simple trick:
No needed to flash the recovery; simply when in fastboot, do not flash the recovery but reboot loading the new (and temporary) recovery. Whit this simple trick you are able to install the supersu.
then summing up:
enter on the command line adb reboot bootloader
(wait for a second and on the phone screen appears ###fastboot...)
enter on the command line fastboot boot twrp.img
(wait 5 to 10 seconds and appears the teamwin bacon recovery)
press install and load the supersu zip previously loaded on the phone
reboot
enter on the supersu app and DEselect "Respect CM’s root Policy"
et voilà
Of course the teamwin recovery is NOT installed on the phone and you already have the OLD simple recovery , but the phone is rooted and YOU HAVE THE POWEEEER!!!1!
Click to expand...
Click to collapse
that won't keep the custom recovery forever though mate. you need to fastboot flash recovery recovery.img
Artem said in another thread that you have to go into developer settings and uncheck the update recovery one. then you can flash the recovery and it will stick permanently.
BTW: it works on windows 7 64bit for me. i have the full sdk installed though.
MontAlbert said:
that won't keep the custom recovery forever though mate. you need to fastboot flash recovery recovery.img
Artem said in another thread that you have to go into developer settings and uncheck the update recovery one. then you can flash the recovery and it will stick permanently.
BTW: it works on windows 7 64bit for me. i have the full sdk installed though.
Click to expand...
Click to collapse
That's an option I unchecked before doing everything. That's why I have not replied to Chromium.
And i've tried also with the SDK complete installed on Win7.64.
It doesn't work for me; I dont know why (yet), but by now with this workaround i'm satisfied.
By the way, the OnePlus One is a very goooood phone
Hi,
Is it possible to install TWRP v3.0.0.0 on a LG Nexus 5 HAMMERHEAD v6.0.1 (MMB29Q) without rooting? Not that it's something I absolutely need to do but by browsing through different sites and tutorials, it seems possible although my own tests prove the contrary...
Firstly, on TWRP official website, it's written that you can:
Fastboot Install Method (No Root Required):
You will need the platform-tools from the Android SDK on your computer. Find the SDK Only section on the page linked and install the SDK and download only the platform-tools to get adb and fastboot binaries.
Windows users will need proper drivers installed on your computer. You can try the Naked ADB drivers or the Universal ADB drivers if you don't already have a working driver installed
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type:
adb reboot bootloader
You should now be in fastboot mode. Download the correct image file and copy the file into the same folder as your adb and fastboot binaries. Rename the image to twrp.img and type:
fastboot flash recovery twrp.img
fastboot reboot
Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.
Click to expand...
Click to collapse
I tried this method but it didn't work at all:
After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP.
Click to expand...
Click to collapse
Even I booted directly to TWRP recovery mode after I manually flashed it, it obviously didn't patched the stock ROM since after I later booted the phone normally in Android system and rebooted in recovery mode, the stock recovery mode was back, no TWRP!
Secondly, when I used Nexus Root Toolkit (NRT) v2.1.4, I had no choice but to root if I wanted to flash the custom recovery (TWRP). I successfully rooted and installed TWRP permanently using the tool.
Therefore, is installing TWRP without rooting some kind of myth that maybe worked with previous Android build and TWRP versions or is there actually really a way to do so?
I just did it yesterday on the March patch but had to flash twrp twice. The first time it bypassed recovery and booted into the os. After booting back into the bootloader and flashing twrp again it did boot into twrp.
Sent from my Nexus 5X using XDA Free mobile app
To install TWRP, the phone needs to have an unlocked bootloader, not root.
You can flash TWRP using fastboot commands. After flashing TWRP in fastboot, use the volume and power button to boot directly into recovery.
Hallo there,
at first sorry for the nearly 10th post about this topic, but as you can see I'm in a different position than the most of you. I'm on Arch Linux here and I don't rly want to root my phone with a windows box.
I got adb and fastboot installed, but I can't find a general guide how to flash recovery and root with them, because there are always these click-click-shiny-shiny gui .exes for windows, which take some tasks.
I did root my Droid 3, but this was years ago, and I did never get into this stuff so deep it would help me now. I am a lil exhausted from the day, and don't rly want to puzzle my way through the google search results, which as described above lead to a .exe with a gui at some point.
Anyone here, who knows the basics and is willing to give me a hand here?
As I said I'm a Linux aka a terminal user so you don't need to be soft on this, I just need it compact but complete.
Thanks in advance
p.s. What I think will be relevant at some point, based on the search results so far:
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/showpost.php?p=66546853&postcount=53
Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.
Mother_Teresa said:
Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.
Click to expand...
Click to collapse
aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
And there is another question. The part after
NOW LETS GET XPOSED AND LUCKY PATCHER WORKING
Click to expand...
Click to collapse
is not necessary if I use a different launcher than EMUI, or is it?
EDIT: A VM is not an option, would be the same for me than using a physical windows box.
quote: aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
sounds good to me, so now it is twrp and not cwm?
And there is another question. The part after "NOW LETS GET XPOSED AND LUCKY PATCHER WORKING" is not necessary if I use a different launcher than EMUI, or is it?
it allows customizing advanced settings and is implemented in boot. not necessary
EDIT: A VM is not an option, would be the same for me than using a physical windows box.
if you have recovery etc just flash supersu for root
Okay, good was just checking, if it's the way I puzzled it together. Don't want to wipe me phone.
Mother_Teresa said:
sounds good to me, so now it is twrp and not cwm?
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
What's the difference between twrp and cwm?
Mother_Teresa said:
it allows customizing advanced settings and is implemented in boot. not necessary
Click to expand...
Click to collapse
Okay, nice.
Mother_Teresa said:
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
Just like in the guide i guess. Thx.
This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?
pepper-jk said:
This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?
Click to expand...
Click to collapse
Yay well done and also on posting the solution. I reread what I typed and couldn't make sense to why I mentioned cwm and twrp (same stuff, diff developers or so) so maybe I mixed up bits of another topic
This thread will guide you to flash a custom recovery, Root the device, flash custom ROMs. Firstly, read the entire post and then start your work.
I am a noob. But I have a little experience of rooting and flashing. This device gave me nightmares which are less than as compared to the Xperia Sola which I bricked some years back.
My device has a problem. It does not help install twrp with the traditional ways we know like we can see in the Official TWRP website using "dd" method, the Cyanogenmod link using fastboot commands, the Flashify method, the RecoveryApp method whose apk I never found and the Recovery Installer Utility.
I came to know that either my phone don't have the recovery partition or the phone is overriding all the commands.
Using fastboot commands would give the error like in this post.
Using Flashify would tell me there's no recovery partition found. Rashr would complete the flash process but after booting to recovery, there was no TWRP, just the stock Android recovery.
If you read carefully on the twrp page of XL, there's a line which caught my attention late enough.
It means that TWRP may not work on your device unless you install other custom software as well.
Click to expand...
Click to collapse
Flashing custom kernels with flashtool is easy and they come with recovery pre-installed and lots of amazing stuff, but they won't do any good with the stock ROM. I've tried the Extended stock kernel, the Phantom Kernel and the Thunderzap 4.15.
After surfing the web and forums of other devices, I found that there is a chance I can fix things by updating/repairing software via PC Companion. But something happened and repair also failed.
I can't tell the reason why this happened. And I didn't store the logs. But with trial and error I found some workarounds.
Actual Methods start here
Rooting the device
If you only want to root your device for various reasons, then you will need nothing but a Rootkit. Check out this post about Rooting Xperia L.
But if you are planning to install custom ROMs for your device, then skip this rooting step. It won't be necessary for this condition.
Flashing custom recovery
*Try this method only if above-mentioned method fails*
1. Download TWRP 3.2.1 img. The 3.2.2 and 3.2.3 versions work perfectly but they caused the screen to flicker like hell on my device. Rename the file to 'twrp.img'
2. Download and install adb and fastboot drivers system-wide.
3. Connect your device to PC via USB cable and enabling USB-debugging mode.
4. Open Windows Powershell/Command Prompt in the twrp download directory by pressing Shift and clicking right mouse button.
5. Use fastboot command on stock ROM without root and Unlocked Bootloader. Instead of flashing twrp image to recovery, flash to boot. Use the code:
Code:
adb devices
adb reboot fastboot
Wait for device to boot into fastboot mode. A blue LED will flash when connected.
Code:
fastboot flash boot twrp.img
fastboot reboot
After reboot, don't boot to system. Boot to recovery by pressing volume up repeatedly when pink LED glows. Stop when device vibrates and LED color changes
Flashing custom ROMs
Once the recovery is installed, everything becomes easy. you can find different custom ROMs on the device page here on XDA.
My favorite one is The resurrection Remix Nougat. It is stable enough to be your daily driver. You can head to that page and follow their instructions. But I will also provide steps here.
When in TWRP after the last step, move the downloaded zip file of the ROM and GApps you want to install to the storage of the device by simply connecting via USB.
After that, in TWRP click on Wipe->Advanced->Tick on System, Cache, Dalvik cache. Then Do swipe to begin wipe.
After wipe, go back to main menu. Tap on install, select from the list the ROM zip. then tap on Add more zips and select the GApps zip and then Swipe to start flashing.
After flashing, reboot to system. The first boot takes time. Don't panic if it won't boot.
Install TWRP to FOTAKernel
After booting to your new ROM, you can install the TWRP to your FOTAKernel.
This can be done as following:
Get the downloaded TWRP img file and push it to the device using command line. Open command prompt in the TWRP directory and type,
Code:
adb root
adb wait-for-device
adb push twrp.img /tmp/twrp.img
Now extract the TWRP image to the FOTA partition code,
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
Now reboot to recovery
Code:
adb reboot recovery
Note that custom ROMs often come with Root access inbuilt. If your ROM happened to be not, and your ROM is based on Lollipop or later version of Android, you can root with Magisk. Just read carefully before proceeding.
Comments are welcome!
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devicesadb reboot fastboot "
I think my Sony Xperia L C2105 does not have the fastboot mode.
Here's what I did:
Drivers for Xpleria L are installed.
The bootloader is unlocked (I think!)
1 - installed 15-second ADB
2 - open Windows power shell
3 - Command: adb devices
Response is: "List of devices attached: ZH8001ADB3 device"
4 - Command: adb reboot fastboot
Response is: long pause, phone booted but in normal mode, and light is red ...!
5 - Command: fastboot flash boot twrp.img;
Response is: "<waiting for device>";
- phone still running in normal mode and the light is red.
- few minutes later, the phone is charging with green light present.
I think the phone is rooted.
I used the code provided by the Sony website to unlock the bootloader.
Using the Root Checker Basic app, I get the info: "Congratulations! Root access is properly installed on this device!"
But if I type in the dialer *#*#7378423#*#*, and go to Service info > Configuration > Rooting status is "Boootloader unlock allowed" !!
Is that why it does not work?
I tried switching it off and doing Boot into Xperia L Fastboot Mode Using HARDWARE BUTTONS, but the phone is dark, with no picture, and the led turns blue.
Using the command:
PS C: \ adb> adb devices
List of devices attached
PS C: \ adb>
I've been trying to do that for a few days now and I still have not managed it, even using other advice.
Can someone tell me what to do?
Thank you in advance.
Everterra said:
Hi.
I'm following this thread and I'm stuck on the fifth step "... flash to boot. Use the code:
adb devicesadb reboot fastboot "
I think my Sony Xperia L C2105 does not have the fastboot mode.
.......
Click to expand...
Click to collapse
1. When in fastboot mode, you should type in cmd "fastboot devices" to check the device connectivity. If you can't, then connect using hardware keys.
2. Blue light indicates that you are in fastboot mode. If list of attached devices are blank, that means drivers are not installed (properly). Connect your phone again in fastboot mode and check your drivers page, Win+X > M (I am assuming you must be on windows). There must be a tiny yellow triangle on your device's name. Right click on it and uninstall it and remove device. Try again installing drivers from the flashtool's folder. Disable driver signature enforcement if you are having trouble going the straight way.
3. Your bootloader is still locked because if it had unlocked then the message displayed would have been, "Bootloader Unlocked: Yes" or something like that. Try flashing your stock ROM via Flashtool. Wipe cache and data while flashing. After flashing stock Rom, try unlocking bootloader again. I believe you are using Flashtool.
4. If you are rooted, then you must have any SuperSU app installed on your device. And it's all good even if you are rooted.
Hi All,
I had a previously rooted 8142, but it crapped out on me last week, so I've just bought a new one. I'm trying to root it now. I've unlocked bootloader, and installed the TWRP app, but I can't figure out how to root it.
I was running windows and used Xperifix when I did my last one, but now I'm using Ubuntu, and there's not really any software (like Xperifix or One Click Root) available.
I've been using FlashTool, and can get it to show root privelages, but I have no idea how to flash a recovery image using it.
I tried using Platform Tools via the terminal and I think I was able to flash a TWRP recovery image to the device, but the TWRP app isn't seeing it, nor can I boot into recovery mode.
I tried to download a recovery image via the TWRP app, but even when it's downloaded, the TWRP app isn't finding any recovery images despite pointing the app to my downloads folder.
TWRP is also showing "No Root Permissions"
I can't flash SuperSu or any other ROM's without being able to boot into TWRP recovery menu.
Maybe I'll have to install windows to use the rooting software. Does anyone have any ideas? Been messing around with it 6 hours now and still can't boot into recovery.
Thanks for any ideas.
first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot
ricardo99831390 said:
first I dont know if youre using fastboot so do "sudo apt install android-tools-adb android-tools-fastboot" then open a terminal were twrp is located and type fastboot flash recovery "name of twrp".img and then you are ready to go. I dont know if you can use this phone without a specific driver so that can be a problem. If you cant do it that way i recommend you using a virtual machine with windows and run fastboot (platform tools trough there) so you dont have to remove ubuntu.
Also remember how to access fastboot
Click to expand...
Click to collapse
Thanks! I'll try both of those methods over the weekend and report back.
tombow said:
Thanks! I'll try both of those methods over the weekend and report back.
Click to expand...
Click to collapse
well i forgot to mention, the fastboot flash recovery command depends on your android version so take that in count.