Related
This is just a copy of the guide on myhuawei.net.
I did this because I had some trouble finding the guide since I always look for stuff like this here on XDA.
I also decided to do this because the guide was not in English and the translations by google were not so good.
Huawei Ascend Y201 Pro U8666
Root + CWM Recovery
I am not responsible for any damage you may do to your phone by following this guide.
The files you will need, download them and extract them to a folder on your desktop:
RootY201Pro.zip
UnlockBootloader.zip
Recovery.zip
(PS: Links removed, check post attachments)
- Now, get your phone and go to Settings > Developer Tools. Make sure USB debugging is enabled.
- Also disable Fastboot in Settings.
- Connect your phone to your computer via USB and let it install the drivers. Make sure they are installed correctly. Do not select "Turn on USB storage" on your phone.
Root + Unlock Bootloader:
1. Go to the folder on your desktop where you extracted the files.
2. Right click on unlockbootloader.exe and select 'Run as administrator'.
3. Click "ROOT Your Phone", the program will work and then close on it's own.
4. In your phone, go to the apps drawer and there should be a new app called Superuser.
5. Now go to your PC, open the same program, but this time click "Unlock BOOTLOADER".
6. Let it finish, the program will close on it's own, and then power off your phone.
7. Unplug the phone from the PC and we are done.
You have now successfully rooted and unlocked the bootloader of your device!
Installing CWM Recovery:
1. Turn off your phone if it isn't already.
2. Press and hold the following buttons simultaneously for ~10 seconds: volume down + home button + power button
3. Release the buttons and your phone should not boot, it should be 'stuck'. That's what we wanted.
4. Connect your phone to the PC via USB. It should install the drivers fine.
5. Open CMD and browse to the folder in your desktop.
6. Once you are in the folder type the following commands:
6.a) fastboot erase recovery, then press Enter. Let it work...
6.b) fastboot flash recovery recovery.img, press Enter and let it work again.
6.c) fastboot reboot, and press Enter...
7. Your device is now rebooting. You can unplug it from the PC.
You have now installed CWM Recovery.
Instructions on how to boot to CWM Recovery:
1. Turn off your phone.
2. Press at the same time for ~5 seconds: volume up + power button
3. You should be now on CWM Recovery.
Don't forget to say thanks or to donate!
Good phone and good post. Thanks.
Not work for me.
canetinhas said:
Not work for me.
Click to expand...
Click to collapse
it works. you must be doing something wrong. Tell me where you're having problems.
Yes it works. Be sure to have android drivers installed. Sorry about this newbie question, what is CWM Recovery? Can you point me to a link I can read about it? Thanks.
---------- Post added at 10:30 PM ---------- Previous post was at 10:24 PM ----------
Forget it, I used the search button..
do this the unlocked sim card?
drakkeman said:
do this the unlocked sim card?
Click to expand...
Click to collapse
no it does not
It is possible to have a stock rom and flash it? Thanks.
outlawz_pt said:
It is possible to have a stock rom and flash it? Thanks.
Click to expand...
Click to collapse
yes
Can U point me direction please? Thanks.
outlawz_pt said:
Can U point me direction please? Thanks.
Click to expand...
Click to collapse
what? sorry didn't understand what you said
Sorry, can you give me some information to search for a stock rom and flash instructions? Thanks.
outlawz_pt said:
Sorry, can you give me some information to search for a stock rom and flash instructions? Thanks.
Click to expand...
Click to collapse
?? I don't think you are familiar with these terms. what do you want? you want to root your phone or install cwm?
You're right, i´m not familiar with android flashing, only with WM. I though it was similar. I rooted phone following your instructions. Tried to install cwm but process stucked..
outlawz_pt said:
You're right, i´m not familiar with android flashing, only with WM. I though it was similar. I rooted phone following your instructions. Tried to install cwm but process stucked..
Click to expand...
Click to collapse
please check if you have really rooted your phone, check if there is superuser app among your apps
Yes I have.
outlawz_pt said:
Yes I have.
Click to expand...
Click to collapse
have you disabled fast boot? make sure you follow every step
I disabled fast boot. I will try again and post feedback.
---------- Post added at 11:31 PM ---------- Previous post was at 11:09 PM ----------
Success. Thanks again for your instructions. I'm backing up my system right now. If i make a factory reset should i get a huawei clean device or with operator stuff?
outlawz_pt said:
I disabled fast boot. I will try again and post feedback.
---------- Post added at 11:31 PM ---------- Previous post was at 11:09 PM ----------
Success. Thanks again for your instructions. I'm backing up my system right now. If i make a factory reset should i get a huawei clean device or with operator stuff?
Click to expand...
Click to collapse
glad you made it! Regarding your question, I don't know.. please share your results when you finish making the factory reset I would like to know as well.
It will keep operator data. Fortunately I removed SD card. Factory reset will format card..
I have a Razr Maxx HD. I am stuck in a bootloop and cannot recovery with factory firmware. The phone was rooted but the bootloader not unlocked. I could use some help. I have tried many of the things that I have seen on online forums but have not had success.
Here is what led to the problem:
1) I rooted my phone. It rebooted fine.
2) I downloaded a modified framework-res.apk and Root Explorer (File Manager) to my phone.
3) Mounted Root Explorer in r/w mode.
4) Copied and overwrote original /system/framework-res.apk with modified file.
5) Phone rebooted and got stuck in loop.
*USB debug mode was on at time of failure.
Here is what I have tried on a Mac:
1) In Android System Recovery <3e>, I tried "Wipe cache partition" and "Wipe data/factory reset." That did not work.
2) I downloaded the Mac Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can run ADB in my terminal. However, it only shows the device when in "Recovery/Apply update from ADB " mode. When I perform "adb devices" it shows a serial number and "sideload." I use the "adb sideload" command to transfer the firmware .zip file. It reads the following after it is uploaded:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
assert failed: apply_patch_check("/system/framework-res.apk", "bunch of numbers")
Installation aborted.
This was after sideloading the package "Blur_Version.9.1.41.XT926.Verizon.en.US.zip." This was the same file I was modifying earlier. I have tried it with the fireware xml.zip files from sbf.droid-developers.org/vanquish/list.php and only got to line 3 before it aborted.
3) Tried to update from microSD card and got same result.
4) I have the original framework-res.apk file; however I don't know how to push it. I cannot get it to recognize the device in ADB outside of the Recovery from ADB sideload option. All other ADB commands return an "error : closed" reply.
5) As far as Fastboot, it reads AP Flastboot Flash Mode (S), Device is LOCKED. Status Code: 0, Battery OK, USB Connected. I got the device ID and tried the online unlock key generator on Motorola.com but it stated my device was not eligible for unlocking at this time, so it remains locked.
Here is what I have tried on a Windows 7 PC:
1) I downloaded the Windows Motorola Drivers from their website. I download and installed Android SDK and platform-tools package. I can open ADB in cmd line. However, when I perform "adb devices," it does not show a serial number, even in Recovery ADB sideload.
2) I downloaded RSD Lite 5.3.1. Selected one of the extracted sbf.droid-developers.org/vanquish/list.php .xml files. Hit start and nothing happened. "Show Device" did not bring anything up. I am guessing the PC is not detecting the device, but I uploaded the latest Motorola Drivers Package. I even tried the Google USB Driver install in Android SDK.
Can you recommend another course of action or a means of getting one of these methods to work? Please help me unbrick my phone. Thank you in advance for any advice.
..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.
mentose457 said:
..
Boot into the stock recovery by powering off the phone then holding the power button and volume up and down button. Then use the volume keys to select recovery. When it boots you should see andy on his back and a red triangle. This is the stock recovery. Now try adb devices again.
Click to expand...
Click to collapse
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?
rmp2737 said:
It does not work. No devices were listed.
The only time "adb devices" has worked is in "apply update from adb" mode, but here only "adb sideload" command works and other commands return "error : closed". So it does not seem to me to be an issue with my computer sending commands, but my phone allowing them to received?
Click to expand...
Click to collapse
Is this the case in both windowz and osx?
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Sent from my DROID RAZR HD using Tapatalk 4 Beta
---------- Post added at 06:00 PM ---------- Previous post was at 05:31 PM ----------
I cant find the article bout using a stock update zip. Though you could flash the latest ota update. It would eliminate any chance of you unlocking the bootloader and possibly obtaining root.
mentose457 said:
Is this the case in both windowz and osx?
Click to expand...
Click to collapse
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
mentose457 said:
I read on xda news that you can create your own update zip to flash in stock recovery. In theory you could have it flash the original framework file. I'll do a bit more digging on that and hey back to you.
Click to expand...
Click to collapse
Thanks. Let me know if you find it.
If you could get your phone to be recognized in adb all of your problems could be solved. You could even unlock your bootloader without being able to get into the os. If I were you id continue to try to get my computer to communicate with my phone.
---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------
rmp2737 said:
That is only for OSX. I could not even get the adb at all (even in sideload) on Windows. This makes me think it is a driver issue on the Windows computer. It is a work computer and it may be a driver install issue requiring admin access. I will try to fix the driver issue and run RSD Lite again and let you know.
Thanks. Let me know if you find it.
Click to expand...
Click to collapse
is the "apply update from adb" part of the stock recovery? Ive never encountered it.
---------- Post added at 06:09 PM ---------- Previous post was at 06:08 PM ----------
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.
mentose457 said:
Is the "apply update from adb" part of the stock recovery? Ive never encountered it.
Click to expand...
Click to collapse
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.
rmp2737 said:
Yes, it is part of the stock recovery. I cannot get adb to run at any stage outside of it.
I got fastboot working on the WIndows computer. I had to specify installing the drivers as an Admin. After that, RSD Lite could run. It was able to flash every other file in the package but it failed only on the system.img file.
Click to expand...
Click to collapse
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
mentose457 said:
Have you tried to run adb devices while the phone is bootlooping? It may get far enough in the boot process to allow you to use adb.
Click to expand...
Click to collapse
Have you tried this ^^^
---------- Post added at 07:34 AM ---------- Previous post was at 07:17 AM ----------
What method did you use to fastboot?
mentose457 said:
Try it again? If all you did was push a botched framework-res.apk to the system folder then you really shouldnt have any problems reverting back with rsd.
Click to expand...
Click to collapse
I tried it a few times with RSD Lite different file versions. They did not work. Perhaps the permissions for the folder were not reverted and this is a problem?
I have tried to connect to with ADB during the bootloop and in the recovery mode menu. It did not work.
As for fast boot, I am using the AP Flastboot Flash Mode as part of stock recovery.
Thank you for your help so far. I am lost at this point, since it seems all the typical methods are not working.
I am suspect that performing the factory reset disabled USB Debugging Mode and that is why ADB won't work. If so, I think I am stuck because it's Catch 22. I can't push the files with ADB, I cannot flash the system.img file because it is too big, I cannot flash the system.img file with RSD Lite (for what I can only assume is a permission error), I cannot erase the system.img to clear it before I flash over it because the bootloader is locked, and I can't unlock the bootloader because the exploit requires you to use ADB commands. Unless, I am missing something.
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
TROUBLESHOOTING:
If ADB Sideload gives you a Can't Read error, try these steps:
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareness and check the flag button
5. Continue on with adb sideload
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
UPDATE:
This method might not be for everyone, and if you're not interested in sticking with stock 7.0 and potentially want to roll around to other ROMs you should follow this guide instead; http://forum.xda-developers.com/moto-z/development/android-nougat-moto-z-versions-t3506342
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
dallas90733 said:
Great thank you! Question:
Will all the radio bands (T-MOBILE) still work as normal?
Have you try this out with Google Day Dream VR yet?
I had the note 7 and the Galaxy VR., Kinda of miss that.
Click to expand...
Click to collapse
Daydream works from what I can tell. Also I'm on att so I haven't checked T-Mobile bands but im assuming they work fine. I know there's an app to check which bands your device supports. I'll try downloading it and let you know
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Prfndhatrdofman said:
...
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
I did up until this
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
But when I boot up i have no wifi and I am unable to get the no command to go away to select sideload any ideas?
pieman13 said:
So I get to the point to sideload the nougat update and it always says "can't read..." I've done factory resets and everything else I could think of, still no go for me.
Click to expand...
Click to collapse
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
enetec said:
So... are you of the opinion that recovering a Nougat boot+system TWRP backup on a MM phone would cause a soft brick too?
What type of soft brick do you faced exactly?
Click to expand...
Click to collapse
Didn't work for me. As soon as the system partition was mounted R/W My device would boot loop. Could be a symptom of something else but im not sure.
Prfndhatrdofman said:
This happened to me as well. I think it came down to being an ADB Driver issue for me. I reinstalled a different set of ADB drivers and it had no issue after that.
Click to expand...
Click to collapse
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
pixelens said:
Interesting... I'm using the adb drivers from Android Studio.
---------- Post added at 02:27 PM ---------- Previous post was at 02:16 PM ----------
Tried using the ADB drivers from Minimal ADB and Fastboot, same result. Oh well.
Click to expand...
Click to collapse
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Prfndhatrdofman said:
Yeah i struggled for about 3 hours trying to get sideload to work. I dunno why but after i completely deleted the driver, rebooted, reinstalled from ADB it finally worked. Its definitely not your device or the image its just ADB being a pain in the ass. I even tried multiple versions of ADB. One guy just tried on a different computer and it worked. I dunno why
Click to expand...
Click to collapse
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
pixelens said:
Yah, I've had similar experiences in the past - been ages since I've done this though (Samsung Galaxy SII Skyrocket days) so just wanted to make sure I wasn't missing something.
Quick question though, title says "unlocked retail devices" - does that mean the bootloader has to be unlocked? Or will this work with a locked bootloader? Cheers.
Click to expand...
Click to collapse
I specifically meant network unlocked. Really just any device purchased directly from Motorola.
But yeah i think you might need to have an unlocked bootloader as well.
pixelens said:
Same here, did you find a fix? Tried re-downloading Blur_Version.24.21.46.griffin.retail.en.US.zip and got the same error...
Click to expand...
Click to collapse
Fix was I went back to my pixel and sold the Z.
Mine has unlocked bootloader. Unlocked thru Motorola's website since the first hour I got it
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
pixelens said:
Got the Nougat update to sideload (yay!) - tried a different computer that had no adb drivers installed, used the ones from Minimal ADB and Fastboot and they worked no problem.
Is it possible to lock the bootloader after the Nougat update? I tried and received "(bootloader) still require signed boot.img" message.
Click to expand...
Click to collapse
Dunno. I get the same error.
Thank you for this guide!
Prfndhatrdofman said:
Easy Flash to Nougat Tutorial (Unlocked Retail Devices)
Prerequisites:
Download RSD lite XML to Batch Script from https://www.androidfilehost.com/?fid=24651430732235266
Download ROGERS_MPL24.246-45 from https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Download Nougat firmware from https://mega.nz/#!608HGYqB!kKTc1196PhimDtVte6OdCWF6aXSWGSNLToEkvUePymE
Steps:
Unpack RSDLite XML to Batch Script to a folder on your computer
Unpack Rogers 24.246-45 firmware to the SAME folder
Run 2-rsd-flash-flashfile-windows.bat
Batch File #2 will convert the flashfile.xml file (included in Rogers zip) to a Batch file
Run flashfile.bat which will flash the Rogers firmware to your device (WILL WIPE EVERYTHING EXCEPT MICRO SD CARD)
Wait till its done!
Your device should now have Rogers 24.246-45 Firmware.
From the Bootloader, select Recovery Mode.
If you see No Command don't panic! That's normal. Press the power button for a couple seconds and press volume up or down (not sure if you need volume buttons but I always do anyway)
Once it displays on screen, Select ADB Sideload
From an adb capable command prompt, enter ADB Sideload <name and location of Nougat.zip> (minus the <> obviously)
This will take time. Leave it alone!
Once complete, simply reboot from recovery and let the device start like normal.
I've tested this process multiple times today and it should work well. Let me know if you have any trouble!
I want to mention I have had NO success backing up with TWRP and restoring after this. Something changed with Nougat and any modification to System causes a soft brick (it did for me anyway). Do not attempt to flash system mode TWRP or flash the TurboZ kernel. They don't work and they will cause a boot loop.
Click to expand...
Click to collapse
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
EDIT
after restarting my phone like 10 times in 5 minutes (rest in peace...) I finally figured it out. Now my issue is that I can't seem to get the sideload to work. I am going to try uninstalling android studio and start again. Did you guys figure out why it says * cannot read ' blur.....' * ?
I found how to fix the adb problem about being unable to read from another thread on XDA
1. Download Large Address Awareness from here https://www.techpowerup.com/forums/threads/large-address-aware.112556/
2. Download ADB from here http://forum.xda-developers.com/showthread.php?t=2588979
3. Start Task Manager and kill adb.exe if its running
4. Load the adb.exe file from Large Address Awareess and check the flag button
5. Continue on with adb sideload
---------- Post added at 09:42 AM ---------- Previous post was at 09:40 AM ----------
Porcelainfog said:
Hello
I flashed the rogers 45 firmware, but when I go to recovery mode I can't get the ADB menu to appear. I've held power and down, power and up, nothing, etc. Am I missing something? I did the rogers install, then went to homescreen, then powered off.
Click to expand...
Click to collapse
Do you see the "No command" picture after choosing Recover Mode? Once you get to that, I hold down power and tap volume up and down again and again
After a lot of struggles, we've finally managed to root the Sony Xperia E5.
If you own this device and would like to root it, this thread will guide you through the process.
Requirements:
-You must have the correct drivers installed!
You can't proceed without them as the adb interface won't recognize your device.
-The modified boot.img for 37.0.A.2.156 which you can download here
-The modified boot.img for 37.0.A.2.248 which you can download here
-Twrp recovery which you can download here
-The adb interface, google it.
-Your bootloader must be unlocked via the Sony official method. If you can't find the E5 in the list, you can use the code of the E4g.
-Supersu 2.79 zip which you can download here
-An equal kernel (boot.img) to your desired firmware version. 37.0.A.2.156+37.0.A.2.156 or 37.0.A.2.248+37.0.A.2.248.
-The no-verity encryption fix (optional): (link to be added)
-30 minutes of your time.
I'm not responsible for any possible damage caused to your phone, even though it most likely won't go wrong if you follow the instructions carefully.
I can, however, provide support if your device is stuck in a bootloop.
I won't reply to questions, of which the answers are already mentioned in this thread.
YOU MUST MAKE SURE YOU'VE DOWNLOADED THE KERNEL THAT IS MEANT FOR YOUR SPECIFIC FIRMWARE VERSION!
IF THE TWO AREN'T EQUAL, YOU'LL HARD BRICK YOUR DEVICE AND YOU'LL HAVE TO AGREE THAT I WON'T BE HELD RESPONSIBLE!
Instructions:
1. Unlock your bootloader, check out Sony's website to see how.
2. Check whether the boot unlock succeeded or not.
To do so, you can open your dialer and type *#*#7378423#*#* .
A screen will appear, tap on service info and go to configuration.
Check the rooting status:
*If it says 'bootloader unlock allowed=yes' it means your bootloader is still locked.
*If it says 'bootloader unlocked=yes' it means your bootloader is unlocked.
3. Install the correct drivers for your device, Sony adb+fastboot etc.
4. Go to the root directory of your adb folder, location depending of where you installed it.
Hold Shift and right click to show a menu.
In that menu there should be an option called 'open command prompt here', click on it and it should start adb.
5. Make sure to enable usb debugging on your device.
6. Connect your phone to your computer and type this command in adb:
Code:
adb devices
If your device shows up, it means adb recognized your device and you may proceed.
If it doesn't show up you have to double check your installed drivers in device manager.
7. Type
Code:
adb reboot bootloader
to reboot the device to fastboot.
8. Now you'll have to flash the kernel and recovery.
Put both of the files into the root directory of the adb folder and rename them to boot.img and recovery.img, type
Code:
fastboot flash boot boot.img
to flash the kernel and type
Code:
fastboot flash recovery recovery.img
to flash the recovery.
9. Unplug your device and boot into twrp by pressing the power+volume down buttons. Keep holding the volume down button and release the power button quickly.
10. When you're in twrp, head to 'wipe'->'advanced wipe'->'(user)data partition'.
This step is optional, but recommended to avoid problems with encryption.
Update: the forced encryption has proven to bring limitations and issues to the recovery and system.
The updated steps are now mandatory!
11. Now head to 'install', browse to the directory in which you saved the supersu zip file and flash/install it.
12. Flash the latest version of the encryption fixed no-verity-opt-encrypt zip file, which can be downloaded from here
At first I made my own fix zip file, but I lost it and lot's of other projects, so the above file is a workaround.
13. If the installation succeeds, you may reboot your device.
Please be patient, the first boot may take a while.
It will reboot during the initialization, so don't panic and think it's a bootloop, cause it simply isn't.
I hope this has helped people with rooting their Sony Xperia E5.
I'm here if you need support, unless it's something dumb and/or already mentioned.
UPDATE APRIL 2018
A new modified kernel is available for the latest firmware 37.0.A.2.248!
The rooting process is the same as written above, but instead of flashing the older kernel and firmware, you'll have to flash the new ones.
Be warned, you cannot flash any newer kernel on an older firmware version and the other way around!
The kernel and firmware versions always have to be equal, no exceptions.
An advantage of flashing the newer kernel is that it should support Magisk, while the previous one didn't.
If you want to root your device with Magisk, or install both Magisk and Supersu, the rooting instructions will differ.
You can find new instructions here: (Link to the thread to be added!)
~A special thanks to rrvuhpg and Tu_Angel
Thank you a lot! It worked and now I have my E5 rooted:good::good:
How is the camera quality after unlocking bootloader ?
Tried it last night and it works. Thank you!
wardonz said:
How is the camera quality after unlocking bootloader ?
Click to expand...
Click to collapse
It's exactly the same, the camera works well in all resolutions, video recording seems to be fine too.
Hello, Im stuck in the process of unlock bootloader, im doing all step by step but i couldnt resolve this error:
Code:
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot devices
RQ3001L5W7 fastboot
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x0fce oe
m unlock 0xA55381B959C2CA7B
...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Help, Thank you.
CrStN224 said:
Hello, Im stuck in the process of unlock bootloader, im doing all step by step but i couldnt resolve this error:
Code:
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot devices
RQ3001L5W7 fastboot
C:\Users\Cristian\AppData\Local\Android\Sdk\platform-tools>fastboot -i 0x0fce oe
m unlock 0xA55381B959C2CA7B
...
FAILED (remote: Command not allowed)
finished. total time: 0.029s
Help, Thank you.
Click to expand...
Click to collapse
You must enable oem unlocking in developer options.
To do this you'll have to go to settings, tap on about device and tap build number 5 times in a row.
This will enable the developer options on your device.
Now go to the developer options in settings and make sure oem unlocking is checked.
Now try to unlock the bootloader again.
It should work now, but if it doesn't, you'll have to check your drivers.
It worked perfectly, I had to restore everything because my phone turned on with fabric presets, but the technology saved me, my phone automatically did a backup this morning. Thanks!
CrStN224 said:
It worked perfectly, I had to restore everything because my phone turned on with fabric presets, but the technology saved me, my phone automatically did a backup this morning. Thanks!
Click to expand...
Click to collapse
Unlocking the bootloader always deletes all your data, I'm glad you've made a backup.
So did you manage to root it?
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
CrStN224 said:
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
Click to expand...
Click to collapse
That's odd, do you see the supersu app in your app drawer?
If not, install it from the play store and within the app update the su binary.
Also make sure that in supsersu settings, superuser is enabled and that mount namespace seperation is disabled.
Let me know if that worked out with you
I confirm you thats all ok, i dont know how to resolve the issue...
CrStN224 said:
Well, right now im officially Rooted, but unsucesfully... My device is detected by Root Checker like a rooted device, but I dont know why some apps dont recoignize it. I have two apps what works with root:
- The first one ask me for root permissions but says dont detect root...
- The another app dont ask me and dont recoignize it...
But that everything looks fine, i dont know whats the issue.
Click to expand...
Click to collapse
Hi, if you use Magisk try to disable build in Busybox and install it from Playstore app. It solve the problem on some devices.
OK, I downloaded Magisk and Busybox, I wish I have all the requirements for use any root app! I will reply again if Im done, Thank you!
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
CrStN224 said:
OK, I downloaded Magisk and Busybox, I wish I have all the requirements for use any root app! I will reply again if Im done, Thank you!
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
---------- Post added at 09:30 PM ---------- Previous post was at 09:30 PM ----------
Okay, it works at least, but the apps "CIH" and "No-frills CPU Control" doesnt work for me.
Click to expand...
Click to collapse
No-frills cpu control didn't work on mine either, I replaced it with kernel adiutor.
Besides, you can tweak a lot more in it than in no-frills
mrmarvin_16 said:
-The modified boot.img which you can download here-link
....
~A special thanks to rrvuhpg for the kernel
Click to expand...
Click to collapse
Hello.
Why do we need to flash modified kernel?
Isn't recovery just enough for installing supersu zip onto system partition?
freedom74 said:
Hello.
Why do we need to flash modified kernel?
Isn't recovery just enough for installing supersu zip onto system partition?
Click to expand...
Click to collapse
Flashing only the recovery will result into a bootloop.
As this is a newer device, some kernel patches are required due to dm-verity, bootcheck, etc.
Also make sure to first flash the kernel and then the kernel afterwards to finish the rooting process successfully.
Good luck.
Please! Need Help Fast
Need Help !!! I'm stucked at point 8. After i typed in comand 7. my phone goes into fastboot okay... but then i got two Problems: First one is that i didnt really understand where to put the two files you named.
Second one is that after i typed in command 8. the cmd says >waiting for device< and i can't type in anything anymore.
while my second problem my phone is in fastboot: the blue light in the left top corner is on and the screen is on and has the color black. please help me fast THANK YOU !!!
Wlans Theme said:
Need Help !!! I'm stucked at point 8. After i typed in comand 7. my phone goes into fastboot okay... but then i got two Problems: First one is that i didnt really understand where to put the two files you named.
Second one is that after i typed in command 8. the cmd says >waiting for device< and i can't type in anything anymore.
while my second problem my phone is in fastboot: the blue light in the left top corner is on and the screen is on and has the color black. please help me fast THANK YOU !!!
Click to expand...
Click to collapse
You haven't done anything wrong so far.
The two downloaded files must be placed in your adb folder
You must rename the kernel into boot.img and the recovery into recovery.img
Try to then re-enter the commands of step 8.
If it still says waiting for device it means you'll need to check if you have the proper drivers installed in device manager.
If you really want to turn your device off for now, you can long press the volume up+volume down+power buttons at the same time so your device will turn itself off.
I need help
After unlocking the bootloader, I can`t restore the backup.
Root for MetroPCS/T-Mobile LG Stylo 2 Plus Android 7.0 Nougat ( LGMS550 & LGK550 )
Everything you need to root your LG Stylo 2 Plus running on Android 7.0 is packed into Stylo2.zip for convenience
If the link ever goes down send me a private message, I'll have a few backups of this laying around.
This method works on MetroPCS (LGMS550) and T-Mobile (LGK550) phone models.
Stylo2.zip(35.6mb)
VirusTotal Scan
Click to read the guide
Before doing anything, on your computer you need to extract Stylo2.zip to your Desktop, and install:
minimal_adb_fastboot_v1.4.1_setup.exe (Install this into the Stylo2 folder)
PhoneDrivers.exe
1. Enable Developer Options on your phone, and navigate to the Developer Options page.
Enable OEM unlock
Enable USB debugging
Enable File Transfer
Place no-verify-opt-encrypt-5.1.zip and SuperSU.zip onto your external sd card.
2. After placing the two zip files into the root of your sd card
Enable Charging mode
Authorize your computer for USB debugging
3. Launch MAF32.exe from the Stylo2 folder
(This is Minimal ADB and Fastboot)
4. In the window that pops up type:
adb devices
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2>
5.Boot into the bootloader by typing
adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2> adb devices
List of devices attached
LGMS55010ca1cf1 device
PS C:\Users\Hyperion\Desktop\Stylo2> adb reboot bootloader
PS C:\Users\Hyperion\Desktop\Stylo2>
6. Next you will be unlocking the bootloader
(This will erase everything on the Internal Storage)
In the PowerShell window you will need to type:
fastboot oem unlock
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2> fastboot oem unlock
...
(bootloader) Erasing userdata and cache
OKAY [ 12.386s]
finished. total time: 12.389s
PS C:\Users\Hyperion\Desktop\Stylo2\Stylo2>
Your data should now begin to wipe.
7. Once finished with the data wipe, you will need to flash the recovery.img to your device.
In the PowerShell window you will need to type:
fastboot flash recovery recovery.img
It should look like this:
PS C:\Users\Hyperion\Desktop\Stylo2> fastboot flash recovery recovery.img
target reported max download size of 262144000 bytes
sending 'recovery' (15588 KB)...
OKAY [ 0.508s]
writing 'recovery'...
OKAY [ 0.406s]
finished. total time: 0.918s
PS C:\Users\Hyperion\Desktop\Stylo2>
This is where it can get tricky.
8. Turn your phone off.
Unplug your USB cable
Take out your battery
Put your battery back in
Read next step before turning your phone back on
9. You will now need to boot into TWRP, which isn't the most fun thing to do.
(This process begins after the screen prompt that says your phone can't be authorized has already came up.[if it pops up at all])
Get comfortable with this process before attempting it.
Hold Vol Down + Power (Don't let go)
Once you see the LG Logo let go of the power button briefly
Press the power button while still holding Vol Down
Don't let go until a white Factory Reset screen comes up.
Select Yes, then on the next screen select Yes again
(This should boot you into the flashed TWRP Recovery Image)
If you do not boot into TWRP, repeat Process 1-8 until success
(excluding unlocking your bootloader, once unlocked it does not need to be unlocked again.)
10. Assuming you are in the TWRP menu, you will need to wipe the device again.
Navigate to WIPE in the top right
Follow on screen instructions to wipe the device
Click Reboot, and choose Recovery
It wouldn't be a bad idea to make a Backup at this point
11. Once back at the TWRP menu again, you will need to start flashing .zip files.
Click Install
Click Select Storage in the bottom left
Select no-very-opt-encrypt-5.2.zip
Swype to confirm Flash
Press back until at the TWRP main menu again
Click Install
Select SuperSu.zip
Swype to confirm Flash
Some people have had better luck flashing no-very-opt-encrypt after flashing supersu. (I can not confirm this)
12. Reboot to system, let the thing boot loop a couple times at the MetroPCS screen
Cross your fingers until your phone boots up
Download a Root Checker
Check your root access.
If all went well your MS550/K550 running Android 7.0 Nougat should be rooted
I hope it went well xD
-Mike
Thanks to:
Danielhammons1/Reemitch (For notifying me about a missing step between steps 4 and 5)
I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).
i am stuck at fastboot oem unlock it doesnt do anything will you please contact me at [email protected]
wellsweb said:
I tried this, but when I typed " fastboot oem unlock", all I got was (waiting for device).
Click to expand...
Click to collapse
I believe between number 4 and 5, so at 4.5 you must enter the command "adb reboot bootloader" in order to enter fastboot mode.
some help please, stuck on step 4
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks
cruba001 said:
I have done everything exactly as described in the instructions, when i type abd devices in the cmd prompt i get the following message:
PS C:\Users\gunda\Desktop\Stylo2> adb devices
adb : The term 'adb' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ adb devices
+ ~~~
+ CategoryInfo : ObjectNotFound: (adb:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\Users\gunda\Desktop\Stylo2>
any suggestions or idea as to what is the problem?
thanks
Click to expand...
Click to collapse
That was completely my bad! I forgot I had setup adb and fastboot differently than in this guide, I updated the above post to reflect what you should actually be doing xD Thanks for catching that!~
Can i do this even though im an update behind?
Th3Joker2496 said:
Can i do this even though im an update behind?
Click to expand...
Click to collapse
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.
Dark Bulbasaur said:
I don't see why not, give it a shot, if it messes up let me know. I'll make a TWRP full system backup for you if it doesn't.
Click to expand...
Click to collapse
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Please help me lower fw lg stylo 2 plus ms550. thank you
---------- Post added at 04:00 PM ---------- Previous post was at 03:57 PM ----------
Please help me unlock my bootload. ms550
Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.
Dark Bulbasaur said:
Let's try directing the command towards the file instead of trying to launch it like normal. Just replace " E:/Phone/recovery.img " with what ever directory your recovery.img is in. I'll attach a photo for a better example.
Click to expand...
Click to collapse
im so lost bro you have skype?
I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?
Th3Joker2496 said:
thx for the offer but instead i updated the phone lol im about to go through with the rooting process
---------- Post added at 01:57 AM ---------- Previous post was at 01:27 AM ----------
Hey i got stuck on step 5 it just stays saying <waiting for any device>
---------- Post added at 02:27 AM ---------- Previous post was at 01:57 AM ----------
so i got past step 5 but now it says error:cannot load 'recovery.img'
Click to expand...
Click to collapse
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE
BlackGTNinja said:
How did you get past part 5 ?...Just stuck at WAITING FOR DEVICE
Click to expand...
Click to collapse
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
Reflash TWRP on CMD and remove the battery and run twrp like in the instructions. Afterwards go to wipe, select format in TWRP and type "yes" (after you type "yes" the storage will be wiped. Nothing in internal storage.) and reboot to TWRP (make sure you got a sd card or computer to install rom). After the format, install rom. I don't know how to root on stock. Running LOS 64bit 7.1.2 on my Stylo 2 Plus.
Th3Joker2496 said:
I went into the earlier comments and saw someone say to do "adb reboot bootloader" before step 5 and it worked but i couldnt do anything past that it just reset my phone so if u try this stuff just make sure to backup your phone incase
Click to expand...
Click to collapse
It was the Android Fastboot drivers was not configured right,I had to go to Device Mangager and Manually update drivers to Bootloader interface
http://visualgdb.com/KB/usbdebug-manual/
I hv searched for many websites and they said you should unlock bootloader to go further.
But on lg stylo 2 plus bootloader can't be unlocked it is not available on website .
Can anyone suggest me what i should do to forcefully unlock my bootloader.
xpurge1 said:
I got the message: "encryption was unsuccessful, the password is correct but the data is corrupt"
And then I have a button that says "reset" and that's it. When I click reset I'm taken back to TWRP. I don't know what to do from here. Am I bricked?
Click to expand...
Click to collapse
no you're not. just go into twrp, format data, mount the device, move the folders, and try flashing SuperSU BEFORE no verity.
I can't seem to flash the recovery. OEM is unlocked and everything else is correct but when i go to the step to flash, it tells me it cant be flashed.