Related
LG G Stylo (T-Mobile/MetroPCS) ROOT (5.0.2 & 5.1.1 ) - TWRP Recovery - Unbrick Guide
DO THIS AT YOUR OWN RISK
WARRANTY IS NOW AVOID IF YOU PROCEED WITH ROOT AND TWRP
Windows Machine/OS Only
----------- Lets Proceed on to Rooting LP 5.1.1 (One Click Method) -----------1- Click Here and Download LGGSTYLO_LP511_OneClickRoot.zip File
2- Click Here and Download LG USB Drivers ( Thanks @GameTheory. )
"NOTE: skip Drivers if you have them already install"
4- Enable USB Debugging via Developer Option.
5- Decompress LGGSTYLO_LP511_OneClickRoot.zip on Root C: drive for easy access or any convenient location.
6- Now lets head over where we decompress that zip file and just double " LG_Root_Script.bat "
7- LET the script run to FULL COMPLETION, Your Device will Reboot twice so be patient.
IF YOU HAVE YOU DEVICE WITH LOCKSCREEN CODE / SWIPE CODE NEED TO UNLOCK SCREEN ON EACH REBOOT FOR THE SCRIPT TO PROCEED
Check Image for the whole process - CLICK TO SHOW CONTENT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8- when the process say
Code:
ui_print - Done !
press Ctrl+C
press N then ENTER
( Check Image - CLICK TO SHOW CONTENT )
- And you are done your device is now Rooted
- Phone will Reset and you need to wait till phone is fully Rebooted to system it may take a few minutes so be patient.
NOW YOU CAN PROCEED TO FLASH CUSTOM RECOVERY (TWRP)
-----------------------------------------------------------------------------------------------------------------------
THIS METHOD ONLY WORKS IF YOU ARE IN LP 5.0.2
----------- Lets Proceed on to Rooting LP 5.0.2 -----------
First of all Thank you @avicohh for LG One Click Root GUI/Script base on his Guide I Have successfully Rooted the Stylo using and Following some steps from there just adding some thing you may see in the progress of rooting:
Original LG One Click Root Guide and File Download -CLICK HERE-
After getting all necessary files this is what i did
1- Install LG drivers if they are not installed yet. (VERY IMPORTANT)
2- Download the LG One Click Script Root file above and extract to some folder. (double click on the 7z exe file)
3- Enable Usb debugging on your phone. (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (THIS IS VERY IMPORTANT STEP)
4- Connect your phone to pc. (it will install driver when connected just wait till is done)
5- Switch to MTP when drivers are full install
6- Double click on the LG Root Script.bat file (the Script will run)
7- Follow the instructions.
*Please leave your feedback if it worked for you
Many Many Thanks to @avicohhfor the LG One Click Root
P.S. I'm not a Dev. I just followed the original guide and the only thing i haven't install is Custom Recovery.
If you came across some Fail attend messages just wait a few more seconds, if that doesn't work try again in my case the first try work and 2 fail attends messages came up so just wait a few sec. if that happen
BE PREPARED. First boot can take a while!!! can stay on logo for up to 3 to 5 minutes or sometimes little more before it goes into Optimizing Apps. Have patience. Subsequent boots a pretty speedy.
------------------------------------------------------------------------------------------------------------
TWRP (Custom Recovery) for LG G Stylo T-Mobile (H631) and Metro (MS631) Variant ONLY
------------------------------------------------------------------------------------------------------------
- Download Custom Recovery File from TWRP 2.8.7.0 v10j Click HERE (Thank you @Unjustified Dev and @fix-this! )
After Rooting your device (T-Mobile or Metro Variant)
1- Check -Enable OEM Unlock- under Developer Option (Skip this part if you are 5.0.2)
2- download Flashify from Google Play Store
3- Open Flashify.
4- Do a Stock Recovery Back-up (Recommended)
5- Flash Recovery Image.
6- Will ask to Reboot System and will take you to TWRP Custom Recovery.
7- Now you are done just Reboot System from Recovery or do a FULL BACK-UP
NOTE : This New TWRP (Custom Recovery) have the new fix (Showing Half Screen only) for the new LG G Stylo Hardware Panel.
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
LG G Stylo Update Firmware | Unbrick Guide by @GameTheory.
IF YOU ARE USING @GameTheory. v10i UPDATE ZIP DON'T FLASH v10j UPDATE ZIP , I REPEAT DON'T FLASH v10j UPDATE ZIP YOU'LL END UP WITH BOOTLOOPS/SOFT BRICK
-------------------------------------------------------------------------------------------------------------
Just Follow step from link below - Thank you @GameTheory.
http://androidcreations.weebly.com/lg-g-stylo.html
------------------------------------------------------------------------------------------------------------
Every KDZ Release for T-Mobile and Metro can be found here :
http://forum.xda-developers.com/android/development/read-trying-to-root-kdz-files-kdz-tmo-t3152531
------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
Full v10j Stock Restore / Update
Use this guide if you are on @GameTheory. v10i or want to deleted all trace of root and twrp (Back to Stock)
Full v10j Stock Restore / Update
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
i just picked up the tmob version yesterday, nice device. not the greatest screen ive had but not bad. im also rooted, we just need twrp so we can use xposed.
waiting on TWRP
As previously posted, I am also waiting on a conduit to get xposed installed.. a device without it and all the benefits it brings feels unreal to me..
i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.
fix-this! said:
i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.
Click to expand...
Click to collapse
+100 on that (Battery life + dedicated section for the phone) i have to agree with the battery life pretty neat and i'm sure is because CPU is doesn't have higher clock and screen is not so power hunger, other thing i'm satisfied is the memory management no matter what i do i haven't seen going lower than 1gb of ram always i been having between 1.2gb to 1gb free never had that before so pretty neat and i do have a lot of apps install most of them run in the background,
How can be make a request about making a Dedicated Section for the LG G STYLO? where do i need to sign if that happen i'll be posting some Bootanimations for this phone porting some old ones i created for the G2 and probably making some new ones.
I am pretty impressed with the device. I just bought it for my wife, which she doesn't care what phone I give her as long as it doesn't break the bank. Not able to do that with any of the flagships. Decided to give it a try risking not having the dev support. Hopefully more people takes the risk so we can have custom roms to play for. (not sure if my wife would like that) LOL
Ah, good, a T-Mobile Stylo thread. I just posted my thoughts in the thread for the Boost (Sprint) version, but anyway, I'm mostly liking this phone (except that the camera app doesn't offer manual exposure controls). I'm not sure I'm going to root mine just yet (hell, I still haven't rooted my Avant!), but it's nice to see that a root is available.
i'll leave this here First Custom Boot Animation for the Stylo
https://www.youtube.com/watch?v=wP5EZfmE-oQ
This is really a Lollipop issue, rather than a problem with the phone itself, but I found that the Embware call blocker (which disappeared from Google Play, go figure) doesn't work on the Stylo. It turns out, most of the call blockers out there aren't working on Lollipop.
What I particularly want is a pickup/hangup type of block, so Rachel from Card Services can't even leave a voicemail. I had this capability with the Embware blocker on the KitKat-equipped Galaxy Avant, even before I got around to rooting it. It looks like Google tweaked Lollipop to prevent pickup/hangup blockers from working. #&^%$%^!!!
Extreme Call Blocker claims to work on L, but I'm wary of forking over the cash for it.
There is a built-in reject list under the Call Settings menu, but it's just a straight-to-voicemail reject. I don't want to waste my time deleting spam voicemails, though Visual Voicemail is at least quicker than calling in.
I suppose I could just call T-Mobile and see if they could turn off voicemail entirely. That would at least make the native call blocker useful.
Timberwolfhusky said:
,
Click to expand...
Click to collapse
i found this post to open a new phone section if we show support for the STYLO we may get a Section for it and people can just go there for Q&A, Themes,Dev work and so on, i know the Phone still brand new in everyone eyes but early support doesn't hurt
http://forum.xda-developers.com/show....php?t=1660354
P.S. @Timberwolfhusky you are the only person not in Boost Mobile thread so
I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?
guest_2011 said:
I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?
Click to expand...
Click to collapse
is to early to say it but i have seen a lot of activity and a lot of people are interested on this device, some user with the Zmax are going to be upgrading to the Stylo, we have a pretty good start phone is 100% Rootable as you can see on the 1st post and @fix-this! is working getting the TWRP (Custom Recovery) so i would say we are getting good support so far, Not a lot of support but good.
P.S. this Device is Brand new just got release.
I've also seen some articles that indicate that outside of North America, it's being marketed as the "G4 Stylus" - and also in the international market there's also a G4c model with similar specs; like the Stylo, it has a 720p screen, but it has a smaller form factor than the flagship G4, no stylus, and an 8MP camera.
The T-Mobile G Stylo seems to be the best of the bunch, though: double the RAM and double the storage of the Boost version. Having been a T-Mobile subscriber for a while now, I'm glad to see that they bumped up the specs. It also has the unlock app baked-in, so if you're eligible to unlock it, there's no need to call in or fumble around with unlock codes. I used the unlock app on my Avant before I bought the Stylo, and it worked smoothly and easily. If you're not eligible to permanently unlock it, you can still get a 30-day unlock for international travel.
I'm finding that I like this phone a LOT, in spite of the lack of manual camera settings and the Lollipop-related call blocker issues. The HDR mode seems to be able to handle backlit subjects well enough that the lack of manual exposure control isn't as big a deal as I was thinking it would be.
So far, battery life looks to be in the "outstanding to exceptional" range. It reminds me of the F3 in that respect, but this is a vastly better phone than the F3 could ever hope to be. At least somebody is listening when it comes to battery life!
I'm going to hold off on rooting mine for now, though, at least until I can SIM-unlock it. In any case, I've always been a bit cautious about modding my primary phone.
How's the battery life compared to the tmo zte zmax?(for those that had the zmax)
Also, does this have the "feature" that when the phone reaches certain temps it lowers and prevents you from turning up screen brightness?
Sent from my Z970 using XDA Free mobile app
Will it work (root guide) with Metropcs? I just ordered one. Is metro also the same model LG-H631? I see LS770 on the web, not sure if same phone or something else. Anybody tested USB OTG with Stylo?
Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.
fix-this! said:
Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.
Click to expand...
Click to collapse
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.
guest_2011 said:
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.
Click to expand...
Click to collapse
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.
Is it possible to unroot?
fix-this! said:
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.
Click to expand...
Click to collapse
agree with you this phone needs his own section i'm sure will be good success from LG i have friend that have the Zmax and they are going to be getting the Stylo, we just need someone with the MetroPCS Variant to verified if is rootable the same way the T-mobile variant is.
guest_2011 said:
Is it possible to unroot?
Click to expand...
Click to collapse
the SU app have an Option to Unroot, i personally haven't try it but maybe someone else know if that works.... never had the need to unroot a phone so i have no idea about that
Hello. I have a few questions on rooting this phone. (My first time rooting)
First off, Is this the same model as the ze550kl (I assume so but not 100% sure). I have attempted to root this phone through the instructions provided in posts on this website for model ze550kl but I must be doing something wrong with the programs ect. I have never rooted a phone and so this is my first try and I would really like a full in detail screenshot follow through if available to do with the programs once downloaded and any other programs you may need on windows 10 to get to where I need to be. I dislike the zenui so much that is my main reason to root the phone is to remove this and other bloatware as well as some of my friends have some apps that are pretty neat that I would like that are only available through root.. I have also tried other methods posted on YouTube but I think I'm doing something wrong on all of my attempts. I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.). In relation to the screenshots if there is any files that have to be placed on the phones hard drive from something I download off the internet please state this specifically, I believe that one or 2 ways I have seen required this but it seems vauge and I don't think it was done correctly by me. I am great at following detailed instructions but I don't know what exactly it is I need to do as I have never done this before so if something has to have a specific name please note that.
Thank you for the help.
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
HampTheToker said:
My ZF2L should be showing up any minute now, so I'll let you know when it gets here. I'm no expert, but I've been rooting my Android devices since 2009. I think I can help you out.
Click to expand...
Click to collapse
Thank you, I think I'm just missing an important step. The zenui just isn't my style. Will be nice to be able to remove
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 02:07 PM ---------- Previous post was at 01:28 PM ----------
Yeah, I think you just need more comprehensive instructions. It happens from time to time. From what I can tell so far, it's a pretty straightforward process for those that are familiar with root, but to a beginner it can be a bit much. As soon as mah lazah is dunna chargin' I'll walk you through the steps I took to root it, install custom recovery, and make a backup of your entire system just in case you ever need to restore your phone to a stock-rooted-but otherwise unmodified state. I should have something up in the next couple hours ?
Updated, rooted, and installed custom recovery. I'll post a short write-up shortly.
First off, I'm going to answer your questions since I didn't previously.
Sorvas33 said:
First off, Is this the same model as the ze550kl (I assume so but not 100% sure).
Click to expand...
Click to collapse
No, they're different, but I'm not entirely sure by how much. I'm 100% sure that they're probably maybe 90% or so compatible, but there are differences. I just don't know them without checking. I wouldn't go flashing anything that doesn't explicitly state that it's for the 551 or is compatible or has had a 551 user test and report success. There are some things that are kind of universal (and we'll get into that a little), but for now let's just stick with using caution.
Sorvas33 said:
I would also like to know if there is a way to make a backup of the original files prior to rooting so I can send my phone in because I have a 2 year warantee if something was to happen (dropped, broken, ect.)
Click to expand...
Click to collapse
We'll make a backup using TWRP, but you'll have to be rooted. A TWRP backup (or nandroid backup) is like a snapshot of your current system. You can customize it and only backup certain parts of the system as well as restore certain parts, but I wouldn't worry about that. Most of the time you'll want a complete backup, anyway. But, to answer your question, no, you'll have to be rooted, but you can always unroot from the phone using the Supersu app. If the damage is physical an unrooted backup wouldn't matter anyway.
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
HampTheToker said:
So, here's my (hopefully) brief write-up to acquire root, install recovery, make a backup, and ,optionally, install the Xposed framework. Before getting started be sure to have plugged your phone into your computer for Windows to download and install drivers for your ZF2L. Also, you will need to download and install adb in order to use command prompt to flash files to your phone. This link will take you to a thread here at XDA for Minimal ADB and Fastboot. This is the easiest way to install and use adb and fastboot on your computer. Once you have it installed you can proceed to the next steps.
First, you'll need to unlock your bootloader using the app found here. It's in a .zip files for whatever reason, so you'll need to use 7zip or WinZip or WinRAR or something on your computer to extract it and install to your phone. You can plug your phone in and place the extracted app on your external or internal storage or use a cloud storage app like Dropbox or Google Drive to transfer it to your phone. If you plug it in and place on your internal or external storage, then you'll need to use File Manager (it's a stock app) to find and install it. Once installed just run the app. It's extremely user friendly and straightforward. Your phone will reboot when it's done.
Next, you'll have to temporarily boot a modified boot.img using Minimal adb and fastboot. Once this step is completed and the phone boots up you'll need to go to the Play Store and install Supersu as well as Busybox if you want your root apps to work properly.
Go here on your computer and download the modified boot.img named boot_200007.img and place it in the Minimal adb and fastboot folder. As you can see in this screenshot:
my adb and fastboot folder is located at C:\Windows\Minimal ADB and Fastboot. Once you have the boot.img copied to the right folder go ahead and connect your phone, if it isn't already. Hold the power button and restart the phone. As soon as the screen goes off hold the volume up button until the phone boots into fastboot mode. If you have trouble with this, you can just turn the phone off, and then press and hold power and volume up until it boots into fastboot mode. Right click the Minimal adb and fastboot icon and select run as administrator. As long as it's installed correctly, the following commands shouldn't give you any error messages. Before we go further, let me briefly explain what we're doing at this point. We have two options: we can flash the boot.img which will physically write it to the proper partition on your phone, or we can simply boot the phone while the modified boot.img remains on your computer and unwritten to the phone, which is what we want to do in this case. To do this we enter the following command:
fastboot boot boot_200007.img
Your phone should reboot on it's own and once it does open the app drawer and check to see if Supersu is installed. If it isn't, open Play and install it, as well as Busybox. Open Supersu and make sure you have root. Once your done, open Busybox and install Busybox to /system/xbin and reboot when finished. At this point, you can disconnect your phone and ensure the Supersu does give you any errors. Test it by installing your favorite root apps, and since you're new to root, I'll give you some suggestions. You can do a google search to find Adaway. It isn't available in the Play Store because it's an adblocker and ads are Google's bread and butter, but it sure is nice to use apps without intrusive apps trying to sell you something no matter where you go. Root + Adaway have been solving that problem for years. Next we have Root Explorer which is my root file manager of choice. Another community favorite is ES File Manager. Both are great. Titanium Backup, Flashify (install it for the next step), and Viper4Android (not in Play search XDA) are all must have apps for root users. Install and open some of those (especially Flashify) just to verify that they work and let's move on the next step.
Download TWRP here and place it on either internal or external storage. Open Flashify and select Recovery Image and then find and select recovery551_200431.img. This will write the TeamWinRecoveryProject custom recovery to the recovery partition of your phone which will allow you to view, backup, restore, and modify all the relevant partitions that make up the Android operation system. At this moment, it's important to understand that you are now more than capable of completely and totally bricking your phone...but you're also capable of recovering from most problems that can arise from flashing mods and using root apps. This is where we'll make a complete backup for just that very reason.
After you've flashed TWRP using Flashify, you'll be prompted to reboot. Do so, and your phone will reboot into recovery. You'll see a message one the first run with a check box to disable modifications to system or something along those lines (can't remember exactly what it says lol), just don't check it. Leave the box uncheck and swipe the bar to allow modifications to system. Now, you should see the main menu. Select Backup and make sure that Boot, System, Data, and Cache are selected and rename the backup to something along the lines of "stock_rooted" or "stock_backup" if you wish and you're ready to create a nandroid backup. Swipe the button and give it a few minutes. Once done, just reboot and you're good to go.
Now to install Xposed, you'll first need to install the Xposed Installer .apk on your phone from here. To flash Xposed, reboot into recovery (turn off then hold power + volume down) and select Install then select the Xposed .zip package xposed-v80-sdk21-arm64.zip that you downloaded and placed on your internal (preferrably) or external storage beforehand. Once finished just reboot and you're done. Be warned that the first boot after installing Xposed will take a long time (approx. 5-10 minutes). Greenify, Gravitybox (LL), Youtube Adaway, Flat Style Bar Indicators, MaxLock, and NotifyClean are just a few of my favorite Xposed modules. Be sure to read the descriptions for these modules carefully and do not forget that Xposed modules can be tricky and cause problems if they're not compatible with your phone. Honestly, you should ask here before installing any modules that I haven't already mentioned.
Anyway, that's my brief write-up lol. Hopefully, that isn't too hard to follow. Don't hesitate to reply back if you encounter a problem, have any questions, or simply want to report your success and ask for tips. I'll leave you with this little tip: don't give up on ZenUI. It definitely doesn't hold a flame to stock Android, but if you use a third party launcher like Nova Launcher and use Developer Options to increase animation speed to .5 seconds (or turn them off entirely) it's really not so horrible, in my opinion. It's damn sure not TouchWiz.
Click to expand...
Click to collapse
Thank you man, I will try this when I get a chance (working 14 hour days ATM) but I will let you know how it goes.also what model member do you have. Because the box I have is we're I got my model number. I can't find the one listed on my box in the device itself.
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
HampTheToker said:
Exact same model...ZE551KL.
In About Phone the model number is ASUS_Z00TD.
Click to expand...
Click to collapse
Exactly what I have. Sweet. I'll update you once I'm done. Thank you for your help and assistance. Any app advice? For uninstalling and cleaning hdd/ram. And theme?
Come on, bro...I gotta know if that's friendly enough to get you squared away...
HampTheToker said:
Come on, bro...I gotta know if that's friendly enough to get you squared away...
Click to expand...
Click to collapse
I should have time either tomorrow or next weekend all depending and I'll let you know then. Depends on how much I have to work. I check this post about once to twice a day. Thank you for your effort and time. I really do appreciate it.
Now I do have one more question on my mind. Does the Asus zenfone that we have keep a flash tracker? Meaning that it keeps track if a phone was rooted. The reason I ask is that I have a 2 year warantee and I know that this will "void" it unless I flash it back. But if they have a tracker then I need to make sure there is a way to reset that as well. From what I have read personally it is only Samsung that is keeping track in this way. Thanks for your help Mr.Toker
Yeah, that's mostly a Sammy thing. I'm coming from a Galaxy S4 that's been passed down to my six year old. I'm all too familiar with flash counters and KNOX security. Thankfully, I don't believe Asus has anything like that. That's one of the many reasons I chose this phone over anything Cricket had to offer. I don't care how good the hardware is, if it can't be unlocked and rooted, then I don't want it.
But, to answer your question more directly, no, I don't believe your warranty will be affected.
Also, I'm going to paste this warning from the developer that built TWRP for us.
Warning
Do not try to fix permission, if you do not know exactly what this is ?
Home > Advance > Fixpermission
Click to expand...
Click to collapse
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
CKtheProblem said:
Just figured I'd add that I believe I read unlocking your boot loader voids the warranty. As of right now, I'm pretty sure there's no way to root without unlocking it, and no way to re-lock it after unlocking.
Sent from my ASUS_Z00TD using Tapatalk
Click to expand...
Click to collapse
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
HampTheToker said:
"oem relock bootloader" should do the trick, but I haven't tried it. Sure, technically unlocking your bootloader and rooting voids your warranty, but it's not like either sends a message to Asus in the background stating that you've voided your warranty. The only way they'd know is if you sent it to them for a claim while still rooted. Even then, if it's bricked, it's bricked. They still won't know. If it's not bricked and it's just hardware, then you should be able to unroot.
Honestly, rooting your device has always been a risk to your warranty, but I've yet to have any issues with it since I started rooting my devices in 2009.
Click to expand...
Click to collapse
Yeah you're probably right. Luckily, I've never had to send a phone I rooted back in for repairs so I can't say anything about the process.
Sent from my ASUS_Z00TD using Tapatalk
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
tmjm28 said:
Thanks for those root/recovery instructions, just got this same phone and model number yesterday and just now found the files needed ! You rock! What roms do you suggest?
Click to expand...
Click to collapse
at present we have only stock rom, no custom rom is available for zenfone laser.
Warning: This is dangerous! Even if you do everything according to the following description, your phone may end up damaged! There are no warranties!!
As we know we could change the single sim z play to dual sim by mod the "persist.radio.multisim.config" in TWRP, like showing below:
https://forum.xda-developers.com/moto-z-play/how-to/guide-to-enable-dualsim-singlesim-t3570601
However it will not be functional after you re-flash the firmware.
So inspired by the moto z dual sim mod thread of @benzinerwin:
https://forum.xda-developers.com/moto-z/how-to/guide-dual-sim-mod-signle-sim-moto-z-t3606528
I fingered out the same way on moto z play:
1, Pull the partition controls the "dualsim: false / true" flag:
Code:
adb shell "dd if=/dev/block/mmcblk0p50 of=/tmp/mmcblk0p50.bin"
adb pull /tmp/mmcblk0p50.bin
2, Use a hex editor to change "6661 6C73 6500" to "7472 7565 0000":
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3, Write the partition back:
Code:
adb push mmcblk0p50_edit.bin /tmp/mmcblk0p50_edit.bin
adb shell "dd if=/tmp/mmcblk0p50_edit.bin of=/dev/block/mmcblk0p50"
adb reboot bootloader
4, Erase the partitions modemst1, modemst2 and cache, reboot again.
Code:
fastboot oem hw
fastboot erase modemst1
fastboot erase modemst2
fastboot erase cache
fastboot reboot
After all above steps you can relock the bootloader, go back to stock again, this mod is compatible with future moto OTAs, and it will stay no matter which firmware you have.
Enjoy!
Do you need to be root?
---------- Post added at 02:29 PM ---------- Previous post was at 02:28 PM ----------
I'm on Android Oreo Soak, do you think it would work?
No need to root, but you need to unlock the bootloader, use TWRP to dump the partition, modify it, write it back.
Then you can relock the bootloader.
Yes I was on 8.0 soka also, it works.
Basically you're changing something out of the rom.
Sent from my XT1635-02 using Tapatalk
Just did this on my Moto Z Play, works great on Android Oreo!
tutorial
I would like to know where I find a guide or video guide to perform the procedure without making mistakes, because I would like to leave my motorola z play dual sim
me gustaría saber donde encuentro una guía o vídeo guía para realizar el procedimiento sin cometer errores, porque me gustaria dejar mi motorola z play dual sim
Anything to back up to make this safe and avoid chance of wiping out IMEI like the other thread?
ralphodog said:
... and avoid chance of wiping out IMEI like the other thread?
Click to expand...
Click to collapse
What are you talking about? Why do you refer to another thread without linking it? Which wipe imei?
It just works fine. That's my experience. Did the mod, got two sim displayed.
Hi, @benzinerwin mentioned to backup the stock recovery partition in order to be able to flash the stock recovery after the modification.
I managed to unlock the bootloader and boot (not flash) into TWRP. However, the recovery partition is not among the partitions TWRP offers for backup.
Can anyone help?
will it restore everything after flash original firmware?
Thanks, this worked like a charm!
I didn't flash TWRP, just booted it from ram and then followed the guide
Code:
fastboot boot twrp-3.2.2-0-addison.img
Slightly off-topic, but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
danton47 said:
..., but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
Click to expand...
Click to collapse
For relock you need signed images. Procedure is, you say "start relock", then flash all important partitions with images signed by Lenotorola, then say "end relock". If signature is fine, relock will succeed.
This means you need signed images you want to flash for relock. It's a bad idea to downgrade, especially Moto devices which like to hard brick on OTA after downgrade, so you would need signed Oreo files for relock.
The Dual-SIM mod should be fine and compatible with relock, but that is just a guess by me.
Why do you want to relock? Afterwards you won't be able to start twrp and do Nandroid backup or restore, you are aware of this feature loss?
tag68 said:
Why do you want to relock? Afterwards you won't be able to start twrp and do Nandroid backup or restore, you are aware of this feature loss?
Click to expand...
Click to collapse
The only reason to relock would be to make some security-sensitive software like Google Pay happy. I'm using some corporate software which I thought might refuse to work on a device with an unlocked bootloader. Fortunately, this turned out not to be the case, so I'm good for now. Still, this may change with a future upgrade, so I'm a bit undecided. Maybe I should go through the pain of re-flashing/re-locking while signed images are still available for the OS version I'm currently running.
Anyway, thanks a lot for your detailed response, much appreciated!
You also may use Magisk and Magisk Hide which hides the unlocked state of your phone and usually makes SafetyNet (Pokemon Go, Google Pay etc.) happy. Your phone then is rooted, but if you never give any app the approval to make use of that power, it shouldn't do any harm.
danton47 said:
Thanks, this worked like a charm!
I didn't flash TWRP, just booted it from ram and then followed the guide
Code:
fastboot boot twrp-3.2.2-0-addison.img
Slightly off-topic, but could someone point me to a guide to re-lock the bootloader? I couldn't find anything that wouldn't require re-flashing a ton of images. I'm completely stock on Oreo, with this dual-sim mod being the only modification.
Click to expand...
Click to collapse
Hi, I tried to do the mod the way danton47 did it, which means by only booting twrp instead of flashing it. However, I did not manage to pull the mmcblk0p50.bin file. This is what I did so far:
Starting point:
- the phone runs on Stock-Android 8.0.0, Build number OPNS27.76-12-22-3;
- The Stock recovery was still in place
- the phone was NOT rooted
- the bootloader was locked
What I did then was:
- installation of adb, fastboot and the USB drivers on my computer (I am operating on Windows 7)
- enabling of the "developer options", "USB debugging" and "OEM unlocking" in the stock OS settings of the phone
- unlocking of the bootloader using adb and fastboot and getting the unlock key from the motorola website
-> Having done all this I assume that my adb and fastboot setup is complete and fully functional - otherwise I wouldn't have come so far. Please let me know if I am wrong with that.
- Download of twrp
- copy of the twrp bin file into the same directory in which the adb and fastboot exe files are
- reboot of the phone into bootloader
- boot of twrp from ram
Here the problems started. Initially I tried to use TWRP to backup the (Stock-) recovery partition so that I can then flash twrp, execute the dual-sim modification and then go back to stock-recovery (for the same reason as danton47: the only modification I want ot do to this phone is to enable the dual sim feature).
However, twrp does not offer the recovery partition for backup. I made quite some reasearch for that issue but did not find any solution.
Therefore I was very happy to see that danton47 managed to unlock the dual-sim functionality without flashing twrp. As I understood it this means that the modification can be executed without changing anything else than the affected bin file. So I booted into twrp (same version as danton47 used) again:
Code:
fastboot boot twrp-3.2.2-0-addison.img
However,
Code:
adb devices
does not show me any device! I also tried to enable the "adb sideleoad" in twrp, hoping that this would allow adb to access the phone while TWRP is running (just tell me if this is completely useless at this point). No success neither.
When activating the adb sideload, I get the options "Wipe Dalvik Cache" and "Wipe Cache". I didn't use these options as I don't know what would be wiped.
Can anyone help me with either
- getting twrp to backup my stock recovery so that I can try again by flashing twrp
or
- enabling adb to access the phone whil twrp is booted from ram?
Thanks in advance!
derBorg said:
- enabling adb to access the phone whil twrp is booted from ram?
Click to expand...
Click to collapse
For adb you do not start twrp. Just enter fastboot mode.
tag68 said:
For adb you do not start twrp. Just enter fastboot mode.
Click to expand...
Click to collapse
Thanks for the quick response!
However, I don't get ahead with it. What I read so far is that adb is not used in fastboot mode (which is the same as the bootloader, right?), but when android (or eventually twrp) is running. Please correct me if I'm wrong. At least it didn't work when I tried right now. When the phone is in fastboot mode <adb devices> does not show any device, while <fastboot devices> does.
Here the code I entered with the output I got (serial number edited), starting with android booted, the usb connection established and usb debugging enabled:
Code:
adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
ZY12345678 device
adb reboot bootloader
adb devices
List of devices attached
fastboot devices
ZY12345678 fastboot
adb devices
List of devices attached
Allright, I got it done. Now I want to close my issue on this thread and share my experience.
I could solve the problem that adb did not work in TWRP by hints I found in this thread:
https://forum.xda-developers.com/galaxy-nexus/help/adb-twrp-recovery-t1968989
Apparently it was some sort of driver issue (on Windows 7). When the stock Android was booted, the adb driver worked perfectly and in the device manager I got an entry "Android device/Motorola ADB Interface". After rebooting into bootloader and booting (without flashing) into TWRP using the command:
Code:
fastboot boot twrp-3.2.2-0-addison.img
The phone did not show up at the same place in the device manager any more. Instead, it appeared as "Andere Geräte/ADB Interface", which translates to something like "Further devices/ADB Interface" (I don't know for sure the exact english wording MS uses at this place). Moreover, "ADB Interface" could not be installed properly. This was the reason, why ADB did not work with TWRP booted.
To solve this issue, I pushed Windows to find a driver for the ADB interface. It also found one but not quite the correct one. It found a driver from Samsung and the phone with TWPR booted appeared as "SAMSUNG Android Phone/Android Composite ADB Interface". With this driver installed and TWRP booted "adb devices" finally found my phone. However, I wasn't really comfortable using a not completely adequate driver for modifying my phone, so I uninstalled the driver again an tried to find the corresponding motorola driver. Unfortunately, the only one I found was the driver I already had installed and which allowed me to run adb on Android, but failed on TWRP. Finally, I let windows install the Samsung driver again and (after making a final backup of my contacts and data) executed the dualsim modification described above, which finally was the easiest part of all.
Thanks again to lanyao1920 and benzinerwin for posting how to do the modification and thanks to danton47 to point out that it is not required to flash TWRP for this purpose!
I finally got around to doing this mod. Started last night, and was struggling with things not going quite as described. Couldn't get adb push/pull to behave, screwed around with chmod'ing the files, and some other random crap. Was able to get the mmcblk0p50.bin out and hex edited, but every time I tried dd'ing it back to dev/block/ it wouldn't write correctly. mmcblk0p50 was nearly blank when I looked at it in Xplore's hex viewer. Phone seemed to be functioning fine in this condition, however, albeit with only one sim.
It might have been the couple of imperial stouts I was having, but when I woke up this morning I tried again. And everything worked exactly as described with no issues.
What was I doing wrong? I'll tell you - I was trying to do the ADB commands with the device fully running last night, rather than in recovery.
There is a brief mention in post 2 that apparently didn't click with me last night (maybe cause beer?) that you need to be in recovery. I might have caught this a few years ago when I was messing around more, but I haven't done much of this stuff for a while. I'd like to recommend to OP to add a comment in the OP to make sure others are aware all the adb commands must be done from recovery. Or maybe not needed since I'm the only one who seems to have had issues.
My experience so far: I am US user, using a carrier unlocked device on August 2018 security patch of RETUS stock software. I'm bootloader unlocked, and rooted. I happen to already have a dual-sim tray for my device sold as single sim - I ordered it a couple years ago for travelling abroad, just to have a non-usable place to stash my US sim safely while I was using a local prepaid one on my trip. I have so far tested only my postpaid ATT sim. It appears to be working for both data and calling in both sim slot 1 and sim slot 2, even though slot 2, as advertised, indicates IMEI of 0. My only testing so far, however, has been on my ATT microcell, so I'm not sure if that makes a difference or not. I was actually not expecting the device to connect to the microcell using slot 2, as all devices have to be manually registered to it using IMEI. I'll post back with any further info, as I've seen very limited info anywhere about what actually works and what doesn't in the US in this type of situation. I expect to be able to test a verizon sim and a freedompop sim shortly.
Big thanks to the OP for finding this solution!
For me it worked fine on first try, except that Dual SIM is not working as expected:
- If you activate "always use SIM1 for phone" - it still asks which SIM to use when calling someone
- If you click when calling "remember decision for this contact" when clicking SIM1, you STILL get asked which SIM to use on next call
- If you are using Android Auto and making a call, it displays the question which SIM to use on the phone display
I'm using Android 8.0.0 patch dated August 2018. Is there some possibility to correct the behavior?
tag68 said:
For me it worked fine on first try, except that Dual SIM is not working as expected:
- If you activate "always use SIM1 for phone" - it still asks which SIM to use when calling someone
- If you click when calling "remember decision for this contact" when clicking SIM1, you STILL get asked which SIM to use on next call
- If you are using Android Auto and making a call, it displays the question which SIM to use on the phone display
I'm using Android 8.0.0 patch dated August 2018. Is there some possibility to correct the behavior?
Click to expand...
Click to collapse
It appears that I am seeing the same behaviors so far. Not a huge deal in my use case, but I can see how that would be irritating in many use cases.
Complete wild guess here: firmware from an originally dual sim device might fix this? No idea if this would really work, or present other issues...
Thank you in advance to those who respond
will not long ago I want to root my smart phone is a Huawei P10 Lite released model WAS-LX3 with EMUI and Android version 8.0.0
When trying to root, I opened the bootloader without problem, and install a version of TWRP that apparently was for the P10 lite but when it had the version of android Nougat, in my country was just unlocked Oreo, I do not know if there was the problem but when wanting to install supersu or magiskV I got an error and in the end it was not possible
when I stop trying after a while I keep getting updates, but I have not installed them for fear they will not, find out if they try to root the phone, attached image of the update
by the way now every time I restart the mobile I get a black screen, image also below, with a link to try to enter but said that the page was not available
finally my question is
It will cause some problem if I install the updates, I want to do it, but I am afraid that I will wrap my cell phone or leave it unusable, I really do not know if it is serious or not, but I prefer to avoid problems if they can arise, The update is the WAS-LX3 8.0.0.364 (C605) says that they are google security patches.
my current version is WAS-LX3 8.0.0.360 (C605)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The black screen say something like "Your Phone is unlocked"?
If is that, you don't need to worry, is because you unlock the bootloader.
Fire Spirit said:
Thank you in advance to those who respond
will not long ago I want to root my smart phone is a Huawei P10 Lite released model WAS-LX3 with EMUI and Android version 8.0.0
When trying to root, I opened the bootloader without problem, and install a version of TWRP that apparently was for the P10 lite but when it had the version of android Nougat, in my country was just unlocked Oreo, I do not know if there was the problem but when wanting to install supersu or magiskV I got an error and in the end it was not possible
when I stop trying after a while I keep getting updates, but I have not installed them for fear they will not, find out if they try to root the phone, attached image of the update
by the way now every time I restart the mobile I get a black screen, image also below, with a link to try to enter but said that the page was not available
finally my question is
It will cause some problem if I install the updates, I want to do it, but I am afraid that I will wrap my cell phone or leave it unusable, I really do not know if it is serious or not, but I prefer to avoid problems if they can arise, The update is the WAS-LX3 8.0.0.364 (C605) says that they are google security patches.
my current version is WAS-LX3 8.0.0.360 (C605)
Click to expand...
Click to collapse
Sorry, but it's a little hard to understand you.
Anyway when you have a custom Recovery installed then you can't install OTA updates, but if you have a stock recovery then they should work without problems even when your bootloader is unlocked. And that screen appears when you have unlocked your bootloader as Ret-Zero said already.
Also your images don't work. Use the preview post option to see if they work or not before posting. I have personally used Imgur for inserting images and have never had a problem with it.
RE: about suggestion and correction
Thank you for helping me, and I'm sorry if it was for the grammar, I'm Spanish speaking so I use a translator, and if it was because I did not understand ... I'm sorry hehe
I just updated, thanks for the suggestion of imgur
that is the screen that appears when starting
does not have the factory recovery installed a modified TWRP, and that's the update that I get
I knew that technically, via OTA, they should not come to me because they opened the bootloader, but maybe I'm wrong
RE: Ret-Zero
and update the post by uploading the image of the screen that appears, thanks for answering
Fire Spirit said:
Thank you for helping me, and I'm sorry if it was for the grammar, I'm Spanish speaking so I use a translator, and if it was because I did not understand ... I'm sorry hehe
I just updated, thanks for the suggestion of imgur
that is the screen that appears when starting
does not have the factory recovery installed a modified TWRP, and that's the update that I get
I knew that technically, via OTA, they should not come to me because they opened the bootloader, but maybe I'm wrong
Click to expand...
Click to collapse
Yes that is the screen that you get when your bootloader is unlocked. When you press the power button it will boot you into android and when you press volume up then it should boot you into the stock eRecovery no matter what, even when you have a custom recovery installed. To boot into the custom recovery reboot the phone while holding volume up.
I don't think that unlocking the bootloader will prevent you from getting OTA updates, it will just give you the ability to flash custom images whether it be custom recovery, kernel or an entire OS.
Also your images are so big that they don't fit onto my laptop screen. When you choose an image in Imgur, in the same window that has all the different links, it also has options for changing the size of the image.
DeathBell said:
Yes that is the screen that you get when your bootloader is unlocked. When you press the power button it will boot you into android and when you press volume up then it should boot you into the stock eRecovery no matter what, even when you have a custom recovery installed. To boot into the custom recovery reboot the phone while holding volume up.
I don't think that unlocking the bootloader will prevent you from getting OTA updates, it will just give you the ability to flash custom images whether it be custom recovery, kernel or an entire OS.
Also your images are so big that they don't fit onto my laptop screen. When you choose an image in Imgur, in the same window that has all the different links, it also has options for changing the size of the image.
Click to expand...
Click to collapse
Thank you, good if I give you volume up if you start with the stock.
that was my doubt, is that I wanted to avoid any inconvenience if a bad installation arose because I was touching the cell haha
and with imgur, I will learn later hahaha thank you very much
DeathBell said:
Yes that is the screen that you get when your bootloader is unlocked. When you press the power button it will boot you into android and when you press volume up then it should boot you into the stock eRecovery no matter what, even when you have a custom recovery installed. To boot into the custom recovery reboot the phone while holding volume up.
I don't think that unlocking the bootloader will prevent you from getting OTA updates, it will just give you the ability to flash custom images whether it be custom recovery, kernel or an entire OS.
Also your images are so big that they don't fit onto my laptop screen. When you choose an image in Imgur, in the same window that has all the different links, it also has options for changing the size of the image.
Click to expand...
Click to collapse
help, I think the update has gone wrong or not
as no longer supposedly there were no problems of errors, I gave him to install the update
and I reboot the cell phone, normal, always does it when installing updates
but I started the custom TWRP, now that I give it a reboot and I want to reboot the system or just turn off the disositive
A message appears in blue saying: "No OS Installed! Are you sure you wish to power off?"
if I reboot the system, it puts me back into the TWRP
and if I turn off the phone and then turn it on normally
puts me in the system
what happened??
it could not be that I deleted the OS ... if it was just an update, and if it was, how to install the stock again
Fire Spirit said:
help, I think the update has gone wrong or not
as no longer supposedly there were no problems of errors, I gave him to install the update
and I reboot the cell phone, normal, always does it when installing updates
but I started the custom TWRP, now that I give it a reboot and I want to reboot the system or just turn off the disositive
A message appears in blue saying: "No OS Installed! Are you sure you wish to power off?"
if I reboot the system, it puts me back into the TWRP
and if I turn off the phone and then turn it on normally
puts me in the system
what happened??
it could not be that I deleted the OS ... if it was just an update, and if it was, how to install the stock again
Click to expand...
Click to collapse
You had a custom recovery installed while performing the update so it couldn't install it. To unbrick you phone use HuRUpdaterhttps://www.google.ee/amp/s/forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279/amp/. It may be a little difficult to set up especially since you use a translator.
I'll give you clearer instructions when I have more. time
Fire Spirit said:
help, I think the update has gone wrong or not
as no longer supposedly there were no problems of errors, I gave him to install the update
and I reboot the cell phone, normal, always does it when installing updates
but I started the custom TWRP, now that I give it a reboot and I want to reboot the system or just turn off the disositive
A message appears in blue saying: "No OS Installed! Are you sure you wish to power off?"
if I reboot the system, it puts me back into the TWRP
and if I turn off the phone and then turn it on normally
puts me in the system
what happened??
it could not be that I deleted the OS ... if it was just an update, and if it was, how to install the stock again
Click to expand...
Click to collapse
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
DeathBell said:
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
Click to expand...
Click to collapse
Thank you very much, yes, what I do is first translated and read it, and then see it in English hahaha, I can read English, what costs me too much is ecrbirilo
I have a question, I have seen how to install the custom ROMS that you are in XDA, it is very easy and I only need the TWRP
but, is there a problem if I install one of those? because it would take advantage and put one that already has root available
DeathBell said:
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
Click to expand...
Click to collapse
Thank you very much, yes, what I do is first translated and read it, and then see it in English hahaha, I can read English, what costs me too much is ecrbirilo
I have a question, I have seen how to install the custom ROMS that you are in XDA, it is very easy and I only need the TWRP
but, is there a problem if I install one of those? because it would take advantage and put one that already has root available
Fire Spirit said:
Thank you very much, yes, what I do is first translated and read it, and then see it in English hahaha, I can read English, what costs me too much is ecrbirilo
I have a question, I have seen how to install the custom ROMS that you are in XDA, it is very easy and I only need the TWRP
but, is there a problem if I install one of those? because it would take advantage and put one that already has root available
Click to expand...
Click to collapse
I would get the stock rom working first and have a way to always go back to stock on my sd-card in case something goes wrong or you just wish to go back to stock. Otherwise installing custom roms is easy as long as you follow the instructions, I have seen many times that newer members say that their phones are bricked because they wiped every single partition or something like that while trying to install a custom rom. Usually you only have to wipe data, system, cache and dalvik cache.
There's no point to installing pre-rooted roms if these even exist on huawei devices. When you wan't to root just install the latest version of magisk and you are good to go.
Also your device is C605 and not C432(European version). I am almost certain that you don't have to rebrand to C432 when installing custom roms especially treble roms but I am not entirely sure
Also you can find lots of treble roms that work for our devices in the p8 lite (2017) development forum
DeathBell said:
I would get the stock rom working first and have a way to always go back to stock on my sd-card in case something goes wrong or you just wish to go back to stock. Otherwise installing custom roms is easy as long as you follow the instructions, I have seen many times that newer members say that their phones are bricked because they wiped every single partition or something like that while trying to install a custom rom. Usually you only have to wipe data, system, cache and dalvik cache.
There's no point to installing pre-rooted roms if these even exist on huawei devices. When you wan't to root just install the latest version of magisk and you are good to go.
Also your device is C605 and not C432(European version). I am almost certain that you don't have to rebrand to C432 when installing custom roms especially treble roms but I am not entirely sure
Also you can find lots of treble roms that work for our devices in the p8 lite (2017) development forum
Click to expand...
Click to collapse
you're right, better keep the stock so you do not go unloading every time you ruin it hahaha
I only need to download the HuRUpdater tool
I'll see how it goes thanks:dedos cruzados:
DeathBell said:
Ok, i'll give you step by step instructions. Hopefully your translator doesn't ruin the translation. Also I'm assuming your using Windows. When you are using linux then I'll probably have to give you the firmware files myself since Firmware Finder isn't for Linux.
1. Install Huawei Firmware Finder for Windows and open it.
2. Click on the tab that says "Common Base" and search for Was-LX3C605
3. Click filelist on the Was-LX3C605B364 firmware MAKE SURE THAT THE TYPE IS FULLOTA-MF
4. You should see 3 links. Copy them to your browser and download those 3 files. Their combined size is about 2.5 GB.
5. Put the 3 zip files that you downloaded into an empty folder.
6. Rename
"update_full_WAS-L23_hw_la.zip" to "update_all_hw.zip"
"update_data_full_public.zip" to "update_data_public.zip"
Don't rename "update.zip"
7. Download "HuRUpdater_0.4.zip" and put it also into the folder that you crated.
8. Boot to TWRP and move the folder into your phone's SD-Card.
9. Then flash only "HuRUpdater_0.4.zip". After flashing you'll have to press volume down otherwise it will abort the script.
Then you will need to wait a little. It will also show 3 unknown command errors written in red text. Ignore those because they don't mean anything.
When the installation failed then there is probably a problem with you Custom Recovery. When it worked then you should be able to boot into Android and also have the latest firmware.:fingers-crossed:
Click to expand...
Click to collapse
friend did not work, gave error, right now attached images
I think it's because of the message that says, Inf no recorey.img
Now I will try to install one called CypheroOS
and if it does not work I will try with the method of this video;
https://www.youtube.com/watch?v=jRu7fz5GFdI
I do not know what to do :crying::crying: :crying::crying:
Fire Spirit said:
friend did not work, gave error, right now attached images
I think it's because of the message that says, Inf no recorey.img
Now I will try to install one called CypheroOS
and if it does not work I will try with the method of this video;
https://www.youtube.com/watch?v=jRu7fz5GFdI
I do not know what to do :crying::crying: :crying::crying:
Click to expand...
Click to collapse
That video wouldn't work because it's for EMUI 5 only.
Try to boot to TWRP then select mount and make sure that cache, cust, data, system, vendor are mounted(have checkmarks next to them.
When it still doesn't work then boot to fastboot and check if phone and frp are unlocked when they are install this TWRP(use the 0.2 test version) then try again
Edit: I would also like to know what recovery are you using. Can you give me the link please
DeathBell said:
That video wouldn't work because it's for EMUI 5 only.
Try to boot to TWRP then select mount and make sure that cache, cust, data, system, vendor are mounted(have checkmarks next to them.
When it still doesn't work then boot to fastboot and check if phone and frp are unlocked when they are install this TWRP(use the 0.2 test version) then try again
Edit: I would also like to know what recovery are you using. Can you give me the link please
Click to expand...
Click to collapse
A summary of what happened:
I turned off the cell because I needed the SD, and when I started it again
Instead of starting with TWRP, start with the stock recovery
And well there you only get 3 options, which is an Android start, turn off and I do not remember the last
I gave it to start system
And I start the phone all normal
Honestly I do not know what happened hahaha but I already have a cell phone
Now if I still have the custom recovery or the bootloader open I do not know it hahaha at the moment I do not want to keep touching more things
And about the version I had, I do not remember, at that time I think there was not for Android oreo, or for the p10 lite
I think I installed one of an honor 9
Is that in the official listings on the TWRP page did not appear p10 lite
Then lower the honor
I do not know if there is already TWRP that works well
I remember that I could not install supersu nor magisk before
And about the data, cache, no, those were demarcated.
I do not know why, nor did I know what it was for
Fire Spirit said:
A summary of what happened:
I turned off the cell because I needed the SD, and when I started it again
Instead of starting with TWRP, start with the stock recovery
And well there you only get 3 options, which is an Android start, turn off and I do not remember the last
I gave it to start system
And I start the phone all normal
Honestly I do not know what happened hahaha but I already have a cell phone
Now if I still have the custom recovery or the bootloader open I do not know it hahaha at the moment I do not want to keep touching more things
And about the version I had, I do not remember, at that time I think there was not for Android oreo, or for the p10 lite
I think I installed one of an honor 9
Is that in the official listings on the TWRP page did not appear p10 lite
Then lower the honor
I do not know if there is already TWRP that works well
I remember that I could not install supersu nor magisk before
And about the data, cache, no, those were demarcated.
I do not know why, nor did I know what it was for
Click to expand...
Click to collapse
I have no idea why your phone booted suddenly. The reason your installation failed is because the TWRP that you were using wasn't able to mount the required partions for some reason, the same probably happend when you were trying to install magisk.
Also yes that TWRP is for the honor 9 lite. But the honor 9 lite, p8 lite(2017), p10 lite, mate 10 lite just to name a few are all hi6250 devices so their recoveries, kernels and roms should work for all hi6250 devices. The good thing about this TWRP is that it works both in stock and custom roms but it has some minor bug.
Or you can also use this TWRP. This works perfectly for stock roms, but when you use custom roms then it doesn't even boot, it just hangs on the TWRP logo. One time It didn't even boot when I were on a stock rom but had wiped system, dalvik, data and internal storage and frp was also locked itself for some reason so I bricked my phone and payed 20€ for dc-phoenix to fix it. Back then I had no idea what I was doing anyway. You will also have to remove your screenlock password before using this TWRP because it checks for it when you boot into it, but even when you type the right password it still doesn't work and then it fails to unmount data.
I've used them both and they work really well, also I have no idea what I am writing about since I'm very tired. It's 00.40 AM for me.
DeathBell said:
I have no idea why your phone booted suddenly. The reason your installation failed is because the TWRP that you were using wasn't able to mount the required partions for some reason, the same probably happend when you were trying to install magisk.
Also yes that TWRP is for the honor 9 lite. But the honor 9 lite, p8 lite(2017), p10 lite, mate 10 lite just to name a few are all hi6250 devices so their recoveries, kernels and roms should work for all hi6250 devices. The good thing about this TWRP is that it works both in stock and custom roms but it has some minor bug.
Or you can also use this TWRP. This works perfectly for stock roms, but when you use custom roms then it doesn't even boot, it just hangs on the TWRP logo. One time It didn't even boot when I were on a stock rom but had wiped system, dalvik, data and internal storage and frp was also locked itself for some reason so I bricked my phone and payed 20€ for dc-phoenix to fix it. Back then I had no idea what I was doing anyway. You will also have to remove your screenlock password before using this TWRP because it checks for it when you boot into it, but even when you type the right password it still doesn't work and then it fails to unmount data.
I've used them both and they work really well, also I have no idea what I am writing about since I'm very tired. It's 00.40 AM for me.
Click to expand...
Click to collapse
do not worry, it's serious thank you for all your help, I still have a lot to learn
This is a last request, answer when you can
I would like you to give me a link or the post where the best TWRP is for the p10 lite, the one that works with both stock and personalized rooms, now I want to see if I can change rooms
and on the partitions, I remember that in a twrp area I said mount, and the partitions where I got an error, they were disassembled, they were not marked
It was not me, I guess that was the case since I installed the twrp,
That and how you installed the twrp, maybe that's why the one I have did not do things well, I installed the one I tell you of honor, with Huawei MultiTool, from the same channel of the video that I was going to follow
install the honor because it was the only one that worked, all others gave me error, I do not know if it was because the tool because in other forums I read that when it was updated to support EMUI 8, I made many errors when installing twrp, so it was with me
______________________________________________
REPAIR HTC U11 - CORRUPT - RELOCKED - S_ON
______________________________________________
I run a phone repair shop,
Customer brought a HTC U11 in to repair,
was soft bricked with an attempted custom rom installation then relocked the bootloader without flashing a working OS to it,
The os version was there but when the device booted a message appeared the device is corrupt cannot be trusted and will not boot,
this tutorial is how I managed to revive the dead device please read below.
Device specs on this model were :
______________________________________________
Fastboot oem readmid
2PZC10000
Fastboot oem readcid
htc_039
______________________________________________
hTc download mode
***relocked***
***production***
htc_ocnuhl PVT S-ON
LK-1.0.0.0000
Radio-8998-002772TOV-1712061121
OpenDSP-V11.6.00347.CB8998_0711
OS-2.33.710.9
Dec 8 2017,21:29:54 (1002308)
_____________________________________________
Bootloader displayed killswitch enabled please disable,
Killswitch/frp
Killswitch/oem unlock
Killswitch/bootloader
when trying to unlock with provided original unlock_code.bin that was provided with the phone & returns not allowed on production build in bootloader, could not flash any stock recoveries or TWRP back to the device, also couldn't receive the unlock code
_____________________________________________
I used tried the following programs to flash :
•htc_fastboot.exe
•minimal adb and fastboot 1.7msi
•power shell on windows 8.1
•minimal adb & fastboot
•fastboot binaries from htc_dev.com
couldn't get anything to flash to the customers phone with any of these so dont bother.
____________________________________________
NOTE
I downloaded the OTA's & firmware from the google spreadsheet it had no file for the 2.33.710.9 section there the page it went to was 404 so I just downloaded all of the files with the same CID htc_039 in this case, so just download all relevant files with your matching CID main version shouldn't be an issue as it wasnt for me.
_____________________________________________
REPAIRING THE HTC U11
NOTE
☆Links are at the bottom of tutorial☆
#1 Go through the files in spreadsheet then download all with the same CID as you have even though the main versions might be different,
#2 try to flash them all with normal fastboot to see what is a signed or close to signed zip and what isnt, (you will know by the RUU errors you face anything but RUU security fail zip from USB command or RUU main version fail ) means it probably won't work but try anyway,
NOTE
I narrowed it down to a few but the one that did end up working was main version 1.11.710.5, but this main Verision was 2.33.710.9 ??? Dont ask me how it worked twice as it needed to be flushed first time it said but it did,
#4 Now the only flash tool that works for downloading to the device in RUU mode is the HTC 10 batch tool.
#5 Place the .zip into the "com" folder which is located where ever the batch tool is installed, in my case was C://Android/com
#6 Open the batch tool with administrator privledges,
select option 3 to open fastboot terminal with the purple screen
NOTE
when entered location of the terminal should be "example" C://android/com on the screen this is where you placed your RUU.zip file.
#7 boot U11 to download mode, with device off hold,
•Power
•Volume down
NOTE
plug the device into the computer & make sure drivers are installed properly and working.
#8 Type into the terminal "fastboot oem rebootRUU",
phone will reboot to RUU mode.
#9 type into terminal "fastboot flash zip <file_name.zip>
NOTE
do not add " " or < > into the command syntax simply drag and drop the file if you do not wish to type the entire filename out.
it flashed all 28 zips twice in my case as it needed to be flushed the first time, these same files would not work on any other fastboot terminal I would only ever receive RUU error zip from USB command or RUU error main version fail,
so there you go this helped me and now I hope it can help you all out with your broken U11 fix please enjoy and if this tutorial has helped you please dont forget to hit the thanks button
_____________________________________________
NOTES
when using the HTC 10 batch tool fastboot terminal you can use either standard "fastboot" syntax or the "htc_fastboot" syntax both work.
WINDOWS 10 USERS :
you MUST disable driver signature verification or you will not be able to install any drivers for your U11.
_____________________________________________
FASTBOOT COMMAND SYNTAX
_____________________________________________
STANDARD SYNTAX
fastboot oem rebootRUU
fastboot flash zip "<example.zip>"
HTC SYNTAX
htc_fastboot oem rebootRUU
htc_fastboot flash zip "<example.zip>"
_____________________________________________
LINKS
_____________________________________________
HTC 10 batch tool (credits to sneakyghost ),
http://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
_____________________________________________
Google spreadsheet for your RUU (credits to 5m4r7ph0n36uru),
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
_____________________________________________
HTC drivers for your U11 (fastboot adb & mtp)
http://gsmusbdriverzone.xyz/download-htc-u11-usb-drivers-official.html
____________________________________________
☆☆☆EDIT☆☆☆
I have noticed in download mode OS VERSION is 2.33.710.9 still,
But in the OS system settings in about phone & also HTC sync manager the OS VERSION is 1.03.710.7,
BUT it can also receive and install OTA updates up until 1.29.710.9 version before it will not install any higher updates,
So may be best to unlock the bootloader & flash a newer RUU version to your device to OTA update.
Very strange indeed but just thought I'd better add it.
Thanks
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Sent from my coconut frond hut using Tapatalk
mauiblue said:
Mahalo OP for your posts. I'll give it a try. I got my phone back from HTC and it is still not operating correctly. I mistakenly relocked the phone, bricked it, sent it back to HTC and got it back the other day. When I turned it on and got the OTA update and the phone is rebooted, I got a corrupt OS error message and would not boot. Had to use Fastboot reboot to get the phone to boot up.
Click to expand...
Click to collapse
Hey mate,
No problem at all
Firstly though I would strongly suggest to flash the Unlock_code.bin you got from HTC dev to unlock your bootloader while you have a functional OS,
enable OEM unlock in developer settings then flash unlock code via bootloader or download mode, will save you the big headache of what I was going through when the bootloader is re locked only signed firmware can be flashed but if unlocked can flash unsigned firmware to the device,
I'd say HTC has not repaired the device correctly at all, I'd be pursuing reimbursement for any money you have paid to them,
not even I have had re corruption or anything works like brand new just my OS version in download mode is 2.33.710.9 but zip I flashed in RUU mode was 1.03.710.7 but let me OTA all the way up to 1.29.710.9 before it stopped installing them it downloads it just wont install it,
I'd switch OEM unlock on, flash unlock_code.bin to get unlocked bootloader will stop you from getting the corruption error, I'd also change the OS also just to see if HTC havent flushed something out of the device properly.
Just please whatever you do do not lock the bootloader without a functional OS
Hope this helps mate, if you need any more help dont hesitate
Thanks
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
korom42 said:
Thank you for sharing you experience, I just want to clarify something here because I don't understand why someone want to relock their bootloader
- For warranty ? it will show up as re-locked so they know you did something anyway
- For OTA ? You can still get OTA on unlocked bootloader. Just restore your untouched system image backup and original reovery or flash RUU then apply the OTAs
If for some reason someone still wants to relock the bootloader you must flash the exact correct RUU first to restore your original system and recovery!
Click to expand...
Click to collapse
No problem mate ,
I'm not sure why,
but the customer locked his bootloader before having a workable OS, he had a viper rom with TWRP on it & from what he told me he wanted the oreo bootloader and modem so tried to flash a firmware package that did not flash, but did not take a nandroid backup prior with TWRP then locked the bootloader allowing only signed firmware to be flashed, dont asky me why lol, as even re locking the bootloader it stills shows as modified in bootloader mode, possibly he thought that it would go away if he re locked it I cant be certain he wasnt to sure what he did,
I also had to re lock the bootloader after unlocking it to receive the OTA Updates from 1.03 - 1.29 as they wouldnt install they would download but not install as soon as I re locked it again I could OTA all the way up to 1.29.710.9 before the same would download but not install,
But in my personal reference to everyone you would be better of keeping the BL unlocked your device wont corrupt
As for the re lock of the bootloader snd the exact ruu version as mentioned in the post OS this was corrupted and would not boot, had no recovery only fastboot, download & RUU , could not flash token or receive unlock code, main version on device was showing version 2.33.710.9 as oreo firmware but ruu that I got to successfully flash with the HTC 10 batch tool was nougat 1.03.710.5, which was also giving me RUU error main version in normal and HTC fastboot but same file worked in the batch tool fastboot with or without htc-fastboot syntax I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would , main versions and SDK were both diff and it definitely works I recreated and flashed the device over and over again just to be sure before originally posting
mauiblue said:
I ended up using the SD card method to reflash the stock OS to my bricked phone. I tried using ADB but I was not getting anywhere. Finally I noticed that when I attempted to flash the latest RUU zip file using the SD card method the process got to a point where it almost completed but there was a couple error messages. So I decided to flash a earlier OS and that worked! The phone booted right up. I still was a bit cynical that the phone wasn't completely out of the woods so I did the process of updating the OS via the software update menu. The phone did take the two earlier OS updates and finally was updated to the latest OS and booted up without any issues. Awesome.
Click to expand...
Click to collapse
Have to use fastboot to flash device, or sd card,
Fastboot is diff from adb, but glad everything is working well now for you mate and you shouldn't hopefully have anymore problems with it
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
mauiblue said:
Matty1993;77934110<snip>
I spent 3 weeks tinkering the batch tool is the only fastboot terminal that will flash to the device with a relocked BL and S-ON not even the HTC fastboot.exe would said:
You have more patience than me. Ha! I was so frustrated after I relocked the bootloader and I wasn't able to boot up the phone after a few days. My first mistake was that I DIDN'T RESEARCH AND READ BEFORE I DID ANYTHING. I was a bit perturbed when the OTA update nag screen was coming up so often that I wanted it to go away. Well now I know better that relocking the phone was not the route to go in receiving the OTA update. I should have just calmed down and read and researched more before I shipped off the phone to HTC for 5 weeks for nothing cause they didn't do anything to the phone.
Click to expand...
Click to collapse
Haha patience probably not lol I'm surprised the phone ever started working again after some of the things it got called , no I'm just persistent in everything I do if I cant repair it I make it my goal to repair it ,
That's what I explained to the customer also never lock a bootloader when they system doesn't function as it should only bad things can happen,
I kept getting the OTA notification pop up to but you cant turn it off on HTC like you can with Samsung
I just flashed oreo and kept BL unlocked and no problems again so far
But it does pay off to read that is very true, I learnt the hard way when I first started out with mobiles I had a brand new S3 when they just came out and ended up flashing an S2 kernel to it and literally burnt the touch controller out on the board and made the touch non functional, I've always read up on everything ever since before attempting repair modification or customisation and havent gone wrong since pretty much,
Speaking of HTC did they charge you a fee to supposedly "repair" your device, as I could tell just from what you mentioned something wasnt flushed right in it, which makes you entitled to a refund, I'd file a dispute with them for the work order and reimbursement on the postage and what not as to be honest I've even been all over HTC websites in aus and America and spoken to they're tech support also (usless might i add) even they state that sometimes they cannot even fix this exact issue, and they charge more for the fact the bootloader is modified to repair them,
Click to expand...
Click to collapse
Aloha M. Fortunately HTC has didn't charge me anything. The frustrating thing is that they didn't include with my phone documentation on what they supposedly had done to the phone. Obviously they were able to get the phone to boot up at least once. But it seems like they didn't even test the phone so that it would consistently boot up. Flashing the latest OS update wouldn't have taken much time. I really like HTC phones and their GUI but their customer service SUCKS donkey balls.
Aloha!
Sent from my HTC U11 using Tapatalk
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
mauiblue said:
Aloha Matty. No, HTC didn't charge me for "no services rendered". They were able to get the phone to boot but they didn't make sure that all issues was completely resolved. They just placed the phone in a shipping box and sent it back to me with no documentation to what they did to the phone. BTW today makes a whole day since I was able to get my phone working and rooted. I've got all the main apps I normally use installed and signed on. So far so good. I'm now working on my U12+ and tweaking that phone as I notice the battery life is not as good as the U11.
Click to expand...
Click to collapse
That's great mate, glad it didnt cost you anything then, apart from the 5 week wait though that must have been terrible,
I would have thought they would package it up a bit better but then again they have never been good for service,
Anyhow everything must still be working well then and all issues seem to be gone, , I'm yet to receive a U12 into my work for repair but I do agree battery is pretty good on the U11 I can charge it and it last me 2 days almost before I have to charge it again, but then again I've had it open aswell and the battery takes up 3/4 of the phone under the hood it's a very big battery even in actual size,
Anymore problems with U11 or any other makes and models feel free to contact me through pm or post if you need help and I'll get back as soon as I can
Thanks Matty. All the best!
Sent from my HTC U11 using Tapatalk
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any ideas or advice would be appreciated.
RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
Hey mate,
Yeah somethings going wrong with your OS
What version of android is it using ? 7.0 or 8.0,
As the bootloader is unlocked please KEEP it unlocked dont relock it under any circumstances if relocked only a very specific version of firmware can be reflashed and if flash fail the device will be bricked completely until the correct RUU is flashed
S-ON shouldnt be a problem when BL is unlocked and you can flash most firmwares that match your HTC u11 MID & CID
Recovery should boot without an SD card so if say recovery is corrupted aswell as part of the system is also,
What you need to do is plug it into the PC and using fastboot type the command,
fastboot getvar mid
fastboot getvar cid
with the device in download mode if you can,
If it wont boot to download mode with the button combination
Turn USB debugging on & connect to pc now your going to be using adb
Type this command to try and reboot to download mode to use the fastboot command to obtain your device info
adb oem reboot-download
Or adb reboot-download
It should reboot you to download mode now where you can obtain the necessary info with the fastboot getvar command,
Once you have that info head over to the google spread sheet and download the firmwares that match your MID & CID and then use the tutorial one page 1 to flash the phone,
Remember do not lock BL under any circumstances bad things will happen if the flash goes wrong.
RWSDH said:
So, I think I'm going to have to try this. I've been having some weird issues with my phone. It's a Sprint version that I'm using on Tmobile. My bootloader is unlocked and I have S-on.
So here's a rundown of a couple issues I'm having. I've read up on the SD card issue and mine still says corrupt even when I reformat it with a PC or another phone. I bought a brand new card and it still doesn't work.
I cannot boot to recovery at all (assuming it's because of the lack of SD card) and oddly enough I can not power down my phone or reboot it when I'm anywhere past the lock screen. When I'm at the lock screen I AM able to reboot or power down.
Any ideas or advice would be appreciated.
Click to expand...
Click to collapse
I had an nearly similar problem with my SD Card it always was seen corrupt from the system even after formating the SD Card. Then I did a factory reset, that did the trick for me.
It may take some time to set up the phone again, but for me it was the only way to make it reusable again.
Try to use different hardkey combinations, there are more then one to get into bootloader or downloadmode and even with the ADB commands you can treat your device to do what you want!
I hope this will help you.
So the links that I posted don't work because I don't have enough posts. I have factory reset the phone a few times in an attempt to get things working properly again. Here's the info since I can't put up the screenshots:
Android version:
8.0.0
Security level:
June 1, 2018
Software:
Bad Boyz US unlocked U11 v3.8 (I have a feeling I may have used the wrong one here)
Kernel:
3.3.78-perf-gbd700a6
[email protected] #1
SMP PREEMPT
Baseband:
8998-002772-1712182056
Build:
2.42.617.7 9.0_g CL1011554
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
kajfux said:
Why when I run the command "fastboot flash zip ruu.zip" a message pops up that can not open a zip file?
Wysłane z mojego Redmi Note 3 przy użyciu Tapatalka
Click to expand...
Click to collapse
Have you tried the htc_fastboot command syntax mentioned in the tutorial also with the batch tool ? If so and its still not working Its 100% to do with the zip your trying to flash id say it contains header errors,
Has it given you an error somewhere along the lines of "
a terrible mishap happened with the original ret lens 0" thats another common error to receive to indicate that your .zip is no good,
Try another .zip that matches your PID & CID dont worry about the main version the htc batch tool fastboot command promt for bypasses bootloader security to allow rollback of the bootloader,
I successfully took mine back to nougat from oreo with a locked bootloader which couldnt be re unlocked due to all killswitches being on & S-ON, no recovery or working OS, only download, bootloader & RUU mode,
Deffo the .zip trust me sorry for the late reply aswell didnt get notification but i hope this helps you out a bit.