Edit before publishing: I started writing this for all variants other than sprint, but I'll now make a separate thread for variants that have kdzs and those that don't, otherwise this will be a mess.
Firstly, keep in mind that no one is responsible if you end up bricking your device! There is currently no way to recover from a hard brick other than sending your phone in for repair, so make sure you follow every single step carefully if you wish to proceed!
Additionally, flashing an xbl through DD may not pass randomly even if it appears that it has worked, so be aware of the risks. Only at&t users will need to flash the xbls anyway since that is the only variant other than sprint which does not have kdzs available.
Users with the AT&T variant who are stuck on pie: temp root only works on android 10, as such you will unfortunately not be able to bootloader unlock your device. The firehose may leak at some point in a few months, and you will be able to unlock (and update manually) if it does.
The process for unlocking bootloaders on models other than the sprint one (specifically At&t for this guide) is practically identical; however, it uses different xbl_config.img and xbl.img files, which need to be specific for your device from the pie firmware.
The version naming may not be the exact same for other models, but you just have to ensure that you are on the March patch or below. If you are on April, you can find the guide to switch slots and do so in order to revert to March. To STOP UPDATES, fully uninstall or disable the update center packages either with ADB or package disabler pro for LG, which you can easily find online.
So I repeat, you're going to follow the sprint g8 bootloader unlocking guide, but you have to use the xbl and xbl_config for your device rather than the ones provided in the sprint guide. The engineering abl is the same, but I'll include it here anyway so that you don't have to mess around with any of the files provided in the sprint g8 guide.
Now, steps that are to be ignored and steps that may differ slightly:
Keep in mind that I'm only mentioning what you should be aware of and what may be different, but you still have to follow the guide written by BrandonB1218 in general.
1a: Of course, you still need a vulnerable firmware, and sadly AT&T does not provide kdzs, so you cannot bootloader unlock if you are on the May patch.
You can Ignore this: I found that another method that most likely stops updates is following this guide on youtube. It's supposed to bypass frp lock, but it also gets by all the LG agreements you have to accept, so it will ask you to agree to these if you ever open up the software update option in settings and will probably not update if you don't.
2: Some people had issues with different versions of the mroot script, so try all of them before you come asking for help please. I also suggest that you just temp root without running the temp root magisk setup as you may end up bricking if you accidentally flash a module or make magisk flash a patched boot img (DO NOT FLASH ANYTHING OTHER THAN WHAT'S INCLUDED IN THE GUIDE).
I suggest running the backup script and the commands to make sure you're completely safe, but make sure you keep them separate because a lot of the partitions included in the commands that @BrandonB1218 mentioned are device specific and include your IMEI. The backup script should only backup the partitions that aren't device specific such as system, and this is probably the one you'll need if at all because you shouldn't be touching other partitions. STILL DO BOTH THOUGH
3a: Yes, you have to run the command to find out which slot you're on, but you will not flash anything from the pie or 20d sprint backup that's listed there, or else you will likely brick.
3b and 3c: This should all be the same: If your active slot is A, follow 3b, and if your active slot is B, follow 3c. The commands should also be the same, just with different files.
If your active slot is A, but the files included for your device are also named xbl_a.img, for example, you can just rename them to fit with the command.
Otherwise, you can just change this, for example,
dd if=/storage/emulated/0/Download/xbl_b.img of=/dev/block/bootdevice/by-name/xbl_b
to this:
dd if=/storage/emulated/0/Download/xbl_a.img of=/dev/block/bootdevice/by-name/xbl_b
You also need to flash the engineering laf, so either rename the file or change the command so it works. The link is embedded
Overall, its just important that you take the right file in the first part of the command and flash it to the correct partition of the correct slot in the second part.
If I remember correctly, the method to boot into fastboot is hold vol- and power until the screen goes black (while the phone is plugged into the computer) and then to let go of power as soon as that happens.
4a and 4b: You do not want to do either of these as the boot img and other partitions vary per variant. I unfortunately do not have the magisk patched At&t boot img, but you can patch it yourself from the backup you made and flash it. It might be good to do this beforehand, but you could also just temp root again and dd flash it.
Alternatively, you can flash the metaphysics 1.7 kernel with twrp and magisk included, but you still have to follow the rest of the twrp installation in the sprint g8 bl unlocking guide. TWRP is the same for all US variants.
Congrats! You should now be bootloader unlocked and ready to go at this point. If you ever find yourself unable to boot on the slot which DOES NOT have the engineering abl, you can always switch to the slot with the engineering abl, go to fastboot, and fastboot flash your backed up partitions.
Credits:
Obviously to BrandonB1218, for writing the sprint g8 bootloader unlocking guide
vl48 for basically answering all my questions and providing the needed files
j4nn for writing the temp root
Mr. Zhu for twrp
KamioRinn for metaphysics
Anyone else who contributed in telegram to get this to work!
Amazing! Can't wait to do this. I'll report back when I get this phone unlocked.
Thanks for taking the time.
Files can't be downloaded dead link
blumix said:
Files can't be downloaded dead link
Click to expand...
Click to collapse
No issues here
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Pietrobell86 said:
Hi and thanks for your job. Can I flash the lg g8 at&t with the unlocked firmware G820QM10I after that I unlocked the bootloader? Because I live in UK and At&t Ba....ds blocked the use of the 3g connection, so I cannot use at my home.... But I thought that whit an unlucked firmaware I could do.
Click to expand...
Click to collapse
No sorry. Not sure exactly what your problem is, but it might be solvable with root
Shtiff1 said:
No issues here
Click to expand...
Click to collapse
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
Click to expand...
Click to collapse
I am talking about the AT&T_G8.zip
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
@antintin zip not downloading, FYI
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
blumix said:
You said there is not issues? Since you got the files can you upload it to medafire because it not working?
---------- Post added at 09:22 AM ---------- Previous post was at 09:19 AM ----------
I am talking about the AT&T_G8.zip
Click to expand...
Click to collapse
I can't find it, sorry. I'm on Verizon
Hey, thanks for the guide. I'm rather worried about trying this as LG's newer models are so darn easy to brick. AT&T variant has no LG Bridge support which is incredibly stupid. At least we have kind people like you helping us free our phones
My LG G8 is a secondary phone right now, and as such, I'm very interested in trying this out. Unfortunately, the download link for AT&T_G8.zip give me a 404.
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Espen115 said:
Not shocking that it's still dead. Tried telling antintin on Telegram the day after he posted this that there were issues retrieving the file from here and he blew me off, telling me it was probably because of my country. Tried with home USA network, USA VPN, and UK VPN. ?
Click to expand...
Click to collapse
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
antintin said:
That's because I tried it myself along with a few others and it still worked... I only used that hosting site because I haven't made an account for any other
Click to expand...
Click to collapse
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
lightningdude said:
Would it be possible to have someone upload it to their Google Drive, or Dropbox and send the link via PM or something? That way, when the person confirms that he has downloaded it, it can be removed from the service in question.
Click to expand...
Click to collapse
Why would it have to be removed?... I'll just upload it when I get home and have time
antintin said:
Why would it have to be removed?... I'll just upload it when I get home and have time
Click to expand...
Click to collapse
Just out of consideration for space in your account, in case you were low on free space. I also didn't notice that it was a < 3MB file.
so is someone going to reupload the file or what? cant even download it from the op attachment.
does this even work with 20m or are those of us out of luck?
File Broken
Anyone has the copy of AT&t_G8.zip? Its 404 now.
MaemoToWindows said:
Anyone has the copy of AT&t_G8.zip? Its 404 now.
Click to expand...
Click to collapse
Always has been.
I have it but it won't let me add it
Can u email it to me? [email protected]
Related
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Fybere said:
Hey guys so I have a problem.
Tried to upgrade to the Nougat EMUI 5 from EMUI 4.1 on my P9. It installed but it had no camera and no keyboard installed. So I tried to do a factory reset, I did but now I'm stuck in the set up wizard, and can't even complete it because no keyboard (google voice in its place) and if I try to skip step that need input and go to the end it just loops from the beginning.
Next step I took a stock rom of 4.1 and placed it in my external SD card in dload folder and tried to do a force upgrade but no help. It immediately shows 5% and it fails with no error just a red exclamation mark. So next I tried to use fastboot to flash it but get errors saying remote command not allowed (I have HiSuite installed, but the phone doesn't show when I run 'adb devices').
Factory reset fails, erecovery fails to download anything, can't system recover with hisuite as it fails. But when I try it, the fastboot screen on the phone say 'rescue mode entered' so it's being detected.
I'm at my wits end here on how to get it back. Screw latest android, just want to use the phone. Also does this break warranty? I didn't root it or anything but installing unsupported software could be considered warranty void?
Thank you for help in advance
Click to expand...
Click to collapse
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
http://www.carbontesla.com/2016/11/downgrade-rollback-huawei-p9-nougat-to-marshmallow-europe/
Brontok said:
I believe your warranty is still valid since you havent unlocked the bootloader. After upgrading to Nougat you should have downloaded the rollback package from huawei`s page, since you cannot simply go from Nougat back to Marshmallow ( you need to flash two files, first being "an intermediate package", and second one being marshmallow update.app file, both of which can be downloaded from huawei`s official site ). Try this and see if it helps
Click to expand...
Click to collapse
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
You`re welcome. DC Phoenix is good, but you have to pay in order to use it, right ? That`s my problem, I cant pay since all my money comes from my dad . In your case I would probably try to update via huawei updater and HiSuite. As far as I`ve seen, that method has been most reliable for the majority of users.
Fybere said:
Thanks for the reply, now I know for the future.
In the mean time I fixed it with DC phoenix tool. Although now I have a problem as it set it to C900 so lock screen doesnt update, themes and icons dont work. All issues i can live but would like to fix them. All I know is that I have to unlocka the bootloader, install TWRP, install the version I want with hw and dt folders, and reboot. But everyone on forums speak like you know how to do it and can't find a good guide on how to do it.
Click to expand...
Click to collapse
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
DC Phoenix worked for me, I found myself in the same position as you (no dload, reocvery, e-recovery only fastboot) and thought my phone was unrecoverable for good. Tried every method possible. in the end bit the bullet paid the fee for DC Phoenix had my phone running in 20 minutes.
Hopefully some smart cookies can develop some freeware that works the same way.
Z-Blade said:
I dont know how much research you have done or what you have tried exactly but it sounds like you have made matters worse. I was in your situation before but was able to get past the setup wizard without a keyboard, after this I got ADB working and just installed a keyboard APK.
C900 means you have a cross flashed rom, this can cause all sorts of different issues and I believe when it comes to updates, C900 either gets no updates at all or be the very last in line to get updates. Also, being on C900 could void your warranty.
Click to expand...
Click to collapse
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
In the same situation
Fybere said:
I fixed it by using DC Phoenix to flash the B163 stock ROM but got the C900 firmware due to cross flashing. I fixed it by unlocking my bootloader, installing TWRP and rooting it. Then I just flashed the C432 OEMINFO, reboot and immidietaly got a notification that an available update is ready to be downloaded (B182). Downloaded it, installed no problem and now I'm on L09C432B182, which is what I wanted, minus all bloatware from my provider (Vodafone)
All done with SRK Tool (in the utilities menu it has for OEM fixing and even the themes not working by flashing the hw_init folders).
Overall, got it running and everything fixed
Click to expand...
Click to collapse
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
mjcaballero said:
Hi, can you tell me how to use this tool? because unfortunately I'm in the same situation.
Click to expand...
Click to collapse
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
Z-Blade said:
Awesome, good to hear. I highly recommend you upgrade to Nougat (but make sure your camera app and keyboard app is installed and working). You should be able to do this by using HiSuite and Updater 2.0.
Click to expand...
Click to collapse
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Thanks
Fybere said:
First of all, get your bootloader unlock code. To get it google how to get it (I cant post link as I don't have enough posts to have privileges). If you can't on the English, make a new account on the chinese emui page and use google translate in chrome to navigate. (if the padlock button doesnt give you a form to fill out, clear your cache and cookies or open in incognito mode)
Once you have the code, find the "SRK Tool Huawei Bootloader/ROOT/Recovery/Backup/Utility" thread on XDA and download the latest stable build, should be around 700mb. Also in the thread, the guy posted a video on how to do it.
Step 1: Unlock bootloader
Step 2: install TWRP Recovery
Step 3: Root
These 3 steps are in the video.
Once you successfully rooted, open the tool again and in the Utilities menu (7) there is an option to flash OEMInfo. Select that and choose the OEM info you want. I needed C432. It will use the superuser app to flash it, reboot and you should be on it.
If you are asking how to use DC-Phoenix, again they have both written as well as a video with instructions on how to do it. You don't need an unlocked bootloader as it will use an exploit to circumvent it. Do Method 1, if it doesn't work, do Method 2.
Good luck mate
I got into this mess in the first place by flashing the B361 and my camera and keyboard didnt work after upgrading it. But now that i know how to fix it, I might give it a shot. Is there a thread with features and testing of the Nougat emui 5 for P9? I saw a lot of threads of people rolling back due to battery issues and other stuff. Don't want to update if its not the best.
Click to expand...
Click to collapse
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
i have problem to
..
---------- Post added at 12:33 PM ---------- Previous post was at 12:27 PM ----------
please i try to install twrp but not work
---------- Post added at 12:38 PM ---------- Previous post was at 12:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
what you chose i dont know i buy buy the DC PH..
HOW
---------- Post added at 02:38 PM ---------- Previous post was at 02:33 PM ----------
mjcaballero said:
Thanks a lot for help, my phone is alive again, i use DC Phoenix to resurrect, and SRK for the update
Click to expand...
Click to collapse
PLEASE
---------- Post added at 02:40 PM ---------- Previous post was at 02:38 PM ----------
i install tswp last but not work
---------- Post added at 02:44 PM ---------- Previous post was at 02:40 PM ----------
ppppplease
---------- Post added at 02:45 PM ---------- Previous post was at 02:44 PM ----------
oooooooo
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Motorola Z2 Force users! Your issues will be resolved!
Reasons for using this method:
If you haphazardly flashed a ROM, and now can't boot.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock.
You then can update.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:
Motorola Firmware Team for the zips
Great, So you've read why you might have borked your phone!
Now, let's get it fixed! Below is the link to the only flashall bat file I currently have. This is a simple process to do. There are some requirements though.
Requirements:
Correct drivers (ADB and fastboot is included in the utilities zip if you don't have minimal adb and fastboot installed, or don't have the SDK.)
Over 4GB of RAM.
How to fix your phone:
Download the Utilities zip
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
This process can take up to 10-15 minutes depending on USB connection and your PC
Disclaimer: I did not personally test the zips below besides the Sprint and T-Mobile ones. These are the official Firmware links from the Motorola Firmware Team. My only contribution is this thread and the utilities zip.
Disclaimer 2: it is never suggested to flash a zip not intended for your device/major patch version. If you're on Oreo, DO NOT FLASH NOUGAT. (I flashed T-Mobile to my Sprint phone for testing purposes and so I can tell you what it does. I lost all sim functionality and had to do some wonky stuff to get my phone back to working shape... Word of advise: don't do it.)
Disclaimer 3: if you have minimal adb and fastboot or the Android SDK, please be sure you update to the latest fastboot. The exe files included in the zip are for those who don't have a development environment set up.
Downloads:
Flash All Utilities
AT&T Oreo Flash All
Sprint Oreo Flash All
T-Mobile Flash All (Not official download link, but official files, See here)
USC (check version) Flash All
Verizon Flash All
NOTE: yes, it's in the Z2 play folder. Motorola Firmware Team did not make another folder for our device. Check the file name. It has "Nash" specifying the Z2 force. If you ask why it's in the Play folder, I will not respond.
If you have any other official links, I will add to second post and give proper credits to who found the zip. Only perm links like the AFH ones I posted.
Uzephi said:
First: The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA. This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
This zip will fix that and put you back to stock on the "August" security patch (September update). You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits: Motorola Firmware Team for the zips
Me for modifying the zip to fix oem.img issue on B partitions and turning the xml into a simple flash all.bat
Note: I am mobile and I will clean up the OP and second post when I get time @ home
Click to expand...
Click to collapse
I was going to add yours in but kinda got busy
Thanks for this! I flashed a modified boot.img for root to get my phone unlocked, and flashed the stock kernel back, but I couldn't update to the September patch. After flashing this, updates are working fine. A bit of a lifesaver!
full circle...
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
esuormai said:
i went from stock, to rooted to soft bricked and hopefully after these download ill be back at stock... thanks for all your hard work ...payday ill buy ya beer!
Click to expand...
Click to collapse
I don't take donations, just pay it forward! Thanks for the offer though.
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
WeUseLord- said:
NOTE: make sure your computer has more than 1 GB ram when you flash this you will get a buffer error because this requires a lot of memory I MADE THIS MISTAKE
Click to expand...
Click to collapse
Added in requirements, thank you for verifying that.
Uzephi said:
Added in requirements, thank you for verifying that.
Click to expand...
Click to collapse
Okay thanks OP
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
cooleoboom5 said:
when i did this (i did this so that i could go back to stock with a locked bootloader which as of writing i just realized would work fine if i just did fastboot oem lock without anything else, goddamnit) it told me that a different operating system had been installed, even though it's (presumably) the same os. what's going on?
Click to expand...
Click to collapse
That is a "permanent" flag that triggers when you flash something unsigned and not from Motorola. I.E. custom boot image for root. Reason it's in quotes is because we don't know how to return it back or if we even can.
moto z2 force
WeUseLord- said:
Okay thanks OP
Click to expand...
Click to collapse
where do you download the bat file from
irule1977 said:
where do you download the bat file from
Click to expand...
Click to collapse
It's in the zip
So Sprint Z2 can't get GSM unlocked by flashing ROMs from other carriers? Any idea how it can be unlocked?
How to get back to software status official in bootloader menu? I did managed to do it with T-Mobile version but cant get that from this one.
Uzephi said:
Don't you hate it when you flash something and it puts you in an unrecoverable state?
Does it aggravate you to no end when you flash something and then all you can do is go into bootloader and nothing else?
Well, have no fear Sprint Motorola Z2 force users! Your issues will be resolved!
First: Our phone differences
The Sprint variant is different than the AT&T and T-Mobile phone as it is GSM/CDMA.
This means it's baseband, oem, and boot.img are different. Boot is slightly different, but oem and baseband is completely different.
Reasons for using this method:
If you haphazardly flashed a T-Mobile ROM, you might find out that after wiping oem, you cannot get mobile data to work.
If you tried flashing an audio mod and have issues getting things to work.
If you accidentally (or purposefully) deleted a file and now can't OTA.
Anything else that you can do to soft brick your device.
This zip will fix that and put you back to stock on the "August" security patch (September update).
You then can update to the "September" security update that came out in October.
If you rooted and cannot update but want the update, this will make your phone clean to accept updates again.
Now, to the meat of this thread. In post two, there is flash all zips for each patch version and instructions on what to do. This does need an unlocked bootloader.
Credits:Motorola Firmware Team for the zips
Versions currently available:
NCXS26.122-59-8-6
NCX26.122-59-8
NCX26.122-51
Versions on OTA but no firmware files available:
NCXS26.122-59-8-9
Click to expand...
Click to collapse
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
robdevil said:
Would you be able to make T-Mobile Stock? I've got flash all zips 7.1.1 but when flashing them I can't get any ota's. Every ota just failing on installation even via sideload. I've had multiple carriers ROMs installed on my device earlier looking the way to sim unlock it. Now my device unlock app failing to request unlock.
Click to expand...
Click to collapse
I would only release something I can test. I don't have TMobile service, so I won't be releasing TMobile only firmware. There is a thread by joemossjr for TMobile flashall.
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
hackenggr said:
A quick question sorry for newbie question in advance, I return to Motorola after a long years a lot changed
I got a Moto Z2 from a friend (he no have knowledge of rooting and modifying) which he got from his cousin in UK so when I got it seem it have a Tmobile sprint hybrid rom installed and google warning screen on the start, it is my guess it is Sprint's phone but I am not confirm.
XT-1789-03 is etched on the bottom near the and by search on google it is showing sprint so please if anyone can confirm -03 is sprint or not? imei is also showing the clean on the sprint site but it NOT definitely saying this phone is sprint.
Please someone tell me if I can flash this and get back to normal and get the OTA updates.
Click to expand...
Click to collapse
My Sprint model has the -03 identifier. You should be safe if the bootloader is unlocked. Needs that to flash this
Hello Huawei Honor Note 10 owners,
I've been asked by a member of the xda community to create a short and brief tutorial how to get the ROOT installed on this magnificent device. As many of you know, Huawei are not exactly very friendly releasing the unlock method for a bootloader since earlier this year, so we must be looking for other ways how to get it done ourselves.
So here we go:
1) UNLOCK THE BOOTLOADER
The only official way how to get the bootloader unlocked right now, is to pay for this type of service. I had my unlock code delivered fairly fast from the following website:
https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below
There are 2 options there, a slow one for $20 and a fast one for $23. Naturally I voted for the faster one to have my device unlocked as soon as possible. Main thing is: it works! Here are the steps how to get the bootloader unlocked for Huawei honor note 10:
a) Go to Settings -> About Phone or Settings -> System -> About Phone and tap on build number 7-8 times. You will see a message “You are now a developer”. At this point head back to Settings and you will see an option called Developer Options. Enable USB debugging on your device now.
b) download and install 15 seconds adb installer on your laptop/PC (ideally running Windows), get the file from here:
https://androidmtk.com/download-15-seconds-adb-installer
c) to ensure you have the correct drivers running for your smarthpone, you might want to install Huawei's HiSuite software found here:
https://consumer.huawei.com/minisite/HiSuite_en/
d) download the following zip package platform-tools_r28.0.1-windows from the source here:
http://mirrors.zzu.edu.cn/android/repository/?C=M;O=D
e) boot your phone into fastboot/bootloader mode.
Make sure the phone is turned on and connect it to computer using usb cable.
Open command prompt/power shell pressing SHIFT+right click (touchpad or mouse) on Windows. It will be a dark blue command screen. You must execute this step inside the platform-tools folder from step d)
Type in the following line: adb reboot bootloader. Your phone reboots to fastboot mode in a few seconds.
Now type in another line: fastboot device. Your phone will be listed as a combination of letter and numbers.
Last line to type: fastboot oem unlock **********. The stars represent your unique unlock code that was given to you from the website above.
You will see a warning message about Unlock Bootloader, use Volume buttons to navigate to Yes (highlighted in red) and Power button to select Yes.
Your device will now reboot, wipe all data and then boot back into Android. Your Note 10's bootloader has been just unlocked, congratulations!
2) FLASH TWRP recovery to HUAWEI HONOR NOTE 10
a) first you need to download the following apk as listed by bark1234: https://1drv.ms/u/s!AizwhfImY2xzgadtepfbKJ1BQqxMvg
You can open it up using winrar and just extract the twrp.img file from it. Keep this file as it is the actual TWRP. It is important that you move the twrp.img file in the platform-tools folder, don't skip this step!
b) Turn off your phone. Press and hold Power + Volume Down until you see a fastboot screen.
Or you can also boot into fastboot mode while device is on. Just connect the phone to laptop/PC using usb cable. Open command prompt/power shell from within the platform-tools folder and execute the following lines:
type the familiar line: adb reboot bootloader
next line to type: fastboot flash recovery_ramdisk twrp.img. You will see that command executed successfully in matter of second.
last line to type: fastboot reboot. As soon as you execute this last command line, remove the USB cable and keep pressing Volume UP, so the device will boot to TWRP. If you don't do it quickly enough, your phone just reboots back to system. But no worries, TWRP is already there!
3) ROOT HUAWEI HONOR NOTE 10
a) download the latest stable Magisk zip file from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445.
Have it ready there, make sure to keep it on your phone's internal memory under one of the folders (I kept it under Downloads folder).
b) Switch off your phone and reboot it by holding volume up + power button. You will boot into TWRP recovery. Be patient there, you might want to hold both buttons for a good while until you see the TWRP screen.
NOTE: In my case the TWRP was encrypted, because I had my lock screen password active (under security settings in system). To bypass this, I just switched lock screen feature completely off. This way TWRP stopped asking for the password and I could proceed with flashing procedure without a problem.
c) Once you're inside TWRP, just locate the Magisk zip file and flash it. Just like that. Then you can reboot back to system.
d) download the Magisk file manager from the same source where you download the Magisk zip file: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Now you're rooted:good:
IMPORTANT NOTE: I will not be held responsible if anyone bricks their HUAWEI HONOR NOTE 10 following this tutorial. It works for me, hopefully it will work for you, too.
Anyone has already tried that?
The site does not look very serious to me.
In addition, I would wait until there is an official firmware if something goes wrong.
I have ordered from https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below and got the code in 3-4 hours. though i ordered 1-20 mins one, buts thats okay.
Finally i can confirm the mentioned website works for bootloader unlock code.
letschky said:
Anyone has already tried that?
The site does not look very serious to me.
In addition, I would wait until there is an official firmware if something goes wrong.
Click to expand...
Click to collapse
I was able to achieve all of the above. I understand your concerns about that website's appearance. But... the unlock code works. You can pay per PayPal in case things go south.
You can download official firmware online. The latest one I was able to locate and download was the 125 build version. Although admittedly I haven't tested that version...
For now my phone is rooted, running on the latest 132 build?.
P. S. I can only imagine there will be "more trustworthy" bootloader unlocking service available in some time. And hopefully cheaper, too. Right now this is the next best thing and for those ones who are impatient to wait (like myself) can benefit from it.
Hope this helps?.
bark1234 said:
I have ordered from https://global-unlocking-solutions.miiduu.com/bootloader-unlock-codes-choose-model-below and got the code in 3-4 hours. though i ordered 1-20 mins one, buts thats okay.
Finally i can confirm the mentioned website works for bootloader unlock code.
Click to expand...
Click to collapse
Thanks for the confirmation. Feel free to root the beast now?
Now successfully Rooted. Thanks a lot guys. all because of xda camaraderie.
And i was able to get full rom 125 package. Yes i downloaded it from http://androidhost.ru/41z, so be careful while flashing, i haven't tried it yet.
Here : https://1drv.ms/u/s!AizwhfImY2xzgag8-DCUTfaIvpWcCw
7gismo said:
I was able to achieve all of the above. I understand your concerns about that website's appearance. But... the unlock code works. You can pay per PayPal in case things go south.
You can download official firmware online. The latest one I was able to locate and download was the 125 build version. Although admittedly I haven't tested that version...
For now my phone is rooted, running on the latest 132 build.
P. S. I can only imagine there will be "more trustworthy" bootloader unlocking service available in some time. And hopefully cheaper, too. Right now this is the next best thing and for those ones who are impatient to wait (like myself) can benefit from it.
Hope this helps?.
Click to expand...
Click to collapse
ok thanks
i know ,i come from the Honor Note 8 and Unlock with DC Unlocker.
23 USD it´s ok ,you can always use the code.
Where did you find the B125 firmware?
---------- Post added at 02:53 PM ---------- Previous post was at 02:41 PM ----------
bark1234 said:
Now successfully Rooted. Thanks a lot guys. all because of xda camaraderie.
And i was able to get full rom 125 package. Will share onedrive link in few hours.
Click to expand...
Click to collapse
One Question,after unlock Bootloader delete that all Data (Factory Reset)?
letschky said:
ok thanks
i know ,i come from the Honor Note 8 and Unlock with DC Unlocker.
23 USD it´s ok ,you can always use the code.
Where did you find the B125 firmware?
Click to expand...
Click to collapse
I'd be careful flashing it (haven't tried it myself), but here's the source:
http://androidhost.ru/41z
Androidhost.ru offers 3 firmware versions for Note 10, with an exception of the latest one. But I believe there's the 132 build floating somewhere around Chinese forums, but that's beyond my powers, as it requires creating accounts and point systems and so on...
And yes, bootloader unlock wipes your data, so you'll be back to a fresh system. Just make a backup from the system settings beforehand and you'll be good. Worked for me?.
7gismo said:
I'd be careful flashing it (haven't tried it myself), but here's the source:
http://androidhost.ru/41z
Androidhost.ru offers 3 firmware versions for Note 10, with an exception of the latest one. But I believe there's the 132 build floating somewhere around Chinese forums, but that's beyond my powers, as it requires creating accounts and point systems and so on...
Click to expand...
Click to collapse
Thank you Downloading..
letschky said:
Thank you Downloading..
Click to expand...
Click to collapse
No problem at all. Please keep us posted in case you decide to play with that firmware...
Cheers ?
7gismo said:
No problem at all. Please keep us posted in case you decide to play with that firmware...
Cheers ?
Click to expand...
Click to collapse
I just need them as security if something happens, but I'll do it tomorrow
---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------
ok now I have bought the unlock code, 1-20min for 23usd
letschky said:
I just need them as security if something happens, but I'll do it tomorrow
---------- Post added at 03:15 PM ---------- Previous post was at 03:11 PM ----------
ok now I have bought the unlock code, 1-20min for 23usd
Click to expand...
Click to collapse
Good stuff. Keep us updated whether it works for you or not, when you get a chance. Thanks?.
SmartPhonesFan said:
So guyz who is rooted what can you do now ? what can be done better? can you change build.prop? from china to EU ?
Click to expand...
Click to collapse
To be honest, I'm not sure if i want to go that far as I'm OK with the way I have things setup right now... perhaps the others who rooted their Notes can be of more help?
bark1234 said:
Now successfully Rooted. Thanks a lot guys. all because of xda camaraderie.
And i was able to get full rom 125 package. Yes i downloaded it from http://androidhost.ru/41z, so be careful while flashing, i haven't tried it yet.
Here : https://1drv.ms/u/s!AizwhfImY2xzgag8-DCUTfaIvpWcCw
Click to expand...
Click to collapse
Thanx for the faster Download!
---------- Post added at 10:01 AM ---------- Previous post was at 09:50 AM ----------
7gismo said:
Good stuff. Keep us updated whether it works for you or not, when you get a chance. Thanks.
Click to expand...
Click to collapse
Ok,i test it in 2-3 Hours and give the Feedback.
Ok,what i test.
Unlock Bootloader works.
Twrp works
Downgrade failed from 132 to 125 at 99% bit it shows in Settings-Phone Info 125
Update to 132 works
Update via Hi Suite from 125 to 132 works
Back to Stock with eRecovery to 132 works.
Root not testing but later
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
Update:Bootloader is locked if you downgrade from 132 to 125!Unlock again.Phone Locked,not Relocked.So original condition that's good
Uploading the Full 132 Rom maybe you can do something with it,it is from Hi Suite Update
letschky said:
Ok,what i test.
Unlock Bootloader works.
Twrp works
Downgrade failed from 132 to 125 at 99% bit it shows in Settings-Phone Info 125
Update to 132 works
Update via Hi Suite from 125 to 132 works
Back to Stock with eRecovery to 132 works.
Root not testing but later
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
Update:Bootloader is locked if you downgrade from 132 to 125!Unlock again.Phone Locked,not Relocked.So original condition that's good
Uploading the Full 132 Rom maybe you can do something with it,it is from Hi Suite Update
Click to expand...
Click to collapse
Thanks a lot for all the input, much appreciated!. When you say your bootloader got locked again, can you actually reuse the unlock code over and over again if you want to have the bootloader unlocked again, is that correct? I just wonder if we have to unlock the bootloader again in case there's a future update released from Huawei to a newer build (higher than 132).
ProCam said:
Could you provide some screenshots from Root Checker and Magisk as proof?
Click to expand...
Click to collapse
See 4 screenshots attached
7gismo said:
Thanks a lot for all the input, much appreciated!. When you say your bootloader got locked again, can you actually reuse the unlock code over and over again if you want to have the bootloader unlocked again, is that correct? I just wonder if we have to unlock the bootloader again in case there's a future update released from Huawei to a newer build (higher than 132).
Click to expand...
Click to collapse
yes the bootloader code can be used again and again
ProCam said:
Nice thx ill be the receiving the phone in a few days and was kinda bumbed out when i found out it couldn't be unlocked/rooted. its gonna cost me a little but i will be worth it for use with adaway, viper4android and luckypatcher etc.
Click to expand...
Click to collapse
Just for your information, viper4android will not run on any Huawei device from EMUI 8 and above due to 64bit audio drivers only, viper4android runs on 32bits. Just tested all versions myself listed under Magisk modules and all of them fail on driver needs to be reinstalled message
Now that we can unlock we need a port of the AOSP from openkirin.net.
Unfortunately, beyond my pay grade. An alternate OS is what this device needs outside of china.
Deleted
bubba1601 said:
Hi
I have this new device but it's not any of the versions listed here (Nora/Rhyanna)
It's the UK version XT1920-15 sim unlocked, I'm just wandering if the steps to unlock/root are the same on this device as the other versions?
Click to expand...
Click to collapse
https://www.getdroidtips.com/unlock-bootloader-moto-e5-play/
I used this guide to unlock it. I also have this phone, but mine is from latin america, and it should work for yours. :good:
Deleted
bubba1601 said:
Your device is not the same.
The American / latin American version has android 8.0, 2 GB ram and a 5.2 inch screen.
The UK version has android 8.1, 1gb of ram and a 5.3 inch screen.
All such tutorials that work for the US version DON'T work on the UK version and TWRP installation fails completely.
Please be mindful when advising users things "should" work, as it doesn't work and your device is completely different to mine, so should not be attempted from that link.
Click to expand...
Click to collapse
No my phone has 1Gb of Ram and 16gigs of storage space along with 8.1 and TWRP installed. I used that guide to unlock the bootloader the TWRP in that guide doesn't work for our phones. I managed to find the TWRP version of the phone.
Deleted
bubba1601 said:
The guide says it's for android 8.0 though?
I still can't unlock the bootloader!
Click to expand...
Click to collapse
fastboot oem get_unlock_data
"Now command will return a string which you need to copy the string to a notepad with a single line by deleting all spaceNotepad
(Note: Only copy the highlighted sections above. Do not copy the INFO or (bootloader) prefix)"
"To Get Bootloader Key for Moto E5 Play - Open the website Motorola’s unlock the bootloader site by Signing up or Log in in via Google Plus account"
Link:https://accounts.motorola.com/ssoau...ct/standalone/bootloader/unlock-your-device-b
Make an account, also check if your device can even be unlocked on the website.
"Once you click the "Can my Device be unlocked?" you will receive a mail with unlock key.
Now copy the unlock key and type the following command and enter.
fastboot oem unlock UNLOCK_KEY
Here UNLOCK_Key is the place where you have to paste the unlock key which you copied from the email.
That's it! Your device will unlock. hah! Have fun!"
That's how you unlock the boot loader
Link for TWRP for PETTYL:https://mega.nz/#!anwAACZT!MJ95FCiIDH-kkLaZLpFvnKT5j_3Fe2goU-aZmSVeCKo
I couldn't find on XDA so I uploaded it to mega.
Deleted
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
did the op get it sorted
Deleted
bubba1601 said:
I'm running stock again.
No root, no twrp and as far as I'm concerned, project treble ROMs/images are complete waste of time, especially for this device where half the posted steps don't work, supplied resources don't work or twrp images and twrp back ups supposedly for this device don't work
Worse still, I had to pay to redownload my firmware.
Click to expand...
Click to collapse
No idea why it dosent work for you I maneged to flash twrp and root it with magisek also tried linege and ResurexionRemix it works fine only xposed dosent work
Deleted
plscotland said:
Here a twrp buckup Twrp image and rooted boot for XT1920-15 if you manage to boot into twrp or try booting boot image https://drive.google.com/drive/u/0/mobile/folders/1P0yVep9l3yTN2Hzy7QiRXj3kuL_N7Dxz?usp=sharing
Click to expand...
Click to collapse
Can I flash this Recovery to XT1920-16 pettyl?
The file Moto_E5_XT1920-15-recovery.img is TWRP or STOCK recovery?
Also i'm loocking for Stock recovery for XT1920-16
Deleted
I just build custom recovery for pettyl -- ORANGE FOX , download at orangefox.tech
thanks. enjoy!
~whodat aka flash
Deleted
bubba1601 said:
There's already three different TWRPs for PETTYL.....two work one doesn't.
I made a TWRP for pettyl and it works 100% , The reason the others do not work is because they have EXT4 filesystem set to data partitions in the fstabs they were made with. Data partition is set to f2fs and thus it cannot be read. I also made a decrypt.zip for pettyl aswell, and I do not even own this device... I have only dove into android dev less than 2 months ago
Many people are already confused about twrp so do we really need another one to confuse everyone even more?
Click to expand...
Click to collapse
*triple facepalm* are you serious ?!?!
Maybe this site and android modifications is not for you bubba.
---------- Post added at 12:44 PM ---------- Previous post was at 12:32 PM ----------
bubba1601 said:
The comment you quoted says it's a TWRP file and I've not seen the stock recovery available for PETTYL .
Just bear in mind that I'm assuming the xt1920-15 that I have and txt1920-16 you have are identical, but I obviously cannot confirm that or do I know if they work the same I'm just assuming they do.
Click to expand...
Click to collapse
lol to get stock recovery file all you have to do is fastboot boot TWRP or OrangeFox and make a backup of recovery. Its that simple, but what would anyone want with stock recovery anyway?
If you really want it you can get the full stock firmware here, extract it and you will have stock recovery.img along with stock boot.img and everything else....
https://mirrors.lolinet.com/firmware/moto/pettyl/official/
Again, ENJOY!
Deleted
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
He explained y other recoveries had prob and y his wouldn't next it has added features such as built in magisk and etc. test it to see other extra features instead of being a lil upset and taking it out on ppl being nice and fixing ur recovery probs
bubba1601 said:
If you had explained what's better or different about your recovery rather than making a mocking reply I would not have asked if another custom recovery was necessary......
There's currently two working TWRPs for PETTYL and another posted on here that doesn't work at all.
Every PETTYL user that's posted here has had issues with both TWRP versions or have been unable to follow the instructions on how to install either version.
Don't tell me this site and android modding isn't for me, because when the time is right I'll decide to stop, you will not make that decision or suggest I stop because you didn't like my question - which you didn't answer.
So I'll ask you calmly and politely again.
Is it really necessary to have so many different TWRPs and custom recovery for PETTYL?
What does your orange fox offer different to TWRP?
You haven't even posted a proper link......no explanation, no proceedures, no instructions. Nothing.
Explain yourself so people understand, don't mock.
Edit.
My question was not a criticism of what you have done.
I've stopped any further modifications to my own PETTYL because it's obvious a 1gb ram android go device cannot handle 9.0 pie and in the 10 years I've been modding various devices the E5 play is the most complicated piece of S*** I've I've used.
But even worse, if the user base cannot ask a simple question of people without someone like you being rude and sarcastic in reply and telling a fellow user to go away - then I've made the right decision not to work with my E5 or this thread any longer.
The user and support base for the E5 play PETTYL has suddenly hit an all time low, and doesn't need rudeness or your sarcasm to justify its existence..
Click to expand...
Click to collapse
Don't be a d*$k lashing out at a dev who does this work FOR free using up HIS free time to make it possible for you to make this complaint. We developers have to research to gain this knowledge. Be courteous and try to search the web to find the answers you seek and to fill in the blanks. Possibly guide others users in the right direction based on the knowledge you discover.
Don't bite the hand that feeds you. Listen to some nine inch nails, you might learn a thing or two about how to properly human.
He doesn't even own that device yet goes out of his way to provide support for it just for ungrateful individuals such as yourself to lash out at him for not explaining things clearly enough. If you lack the knowledge to fill in the blanks that he may have missed, that just shows that you're at risk of bricking your device from lack of knowledge on the subject. It won't hurt you to do a bit of research for yourself.
Sincerely,
The guy helping to guide that developer you lashed out at to supporting 64bit for YOUR DEVICE.
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to my threads for OP3, OP3T, OP5, OP5T and OP6 as unbrick tools allow to (obviously) unbrick your phone but also to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
I linked to 9.0.11 , 9.0.6 and 9.0.5 packages shared by @iaTa in his thread and by @SpasilliumNexus in his AFH here, rest has been found and shared by me.
As the instructions and Qualcomm drivers are already available here , I don't feel a need to rewrite them.
You can ask questions here on how to use and issues, however I might not be able to answer immediately.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
OOS 9.0.4
OOS 9.0.5
OOS 9.0.6
OOS 9.0.11
OOS 9.0.12
OOS 9.0.13
OOS 9.0.15
OOS 9.0.16
ANDROID 10:
OOS 10.3.0
OOS 10.3.2
OOS 10.3.5
OOS 10.3.7
OOS 10.3.8
Mirror for first and last MSMs per Android version: https://onepluscommunityserver.com/
Notes for T-Mobile version owners:
It is possible to use Pie EDL packages with patched tool made by @AnonymousTipster available at https://drive.google.com/open?id=1dYuVxnf_J97KPrRt6KEBOjau1BRvtnJQ (download link come from his thread ).
According to @fullofhell , the commands "fastboot erase modemst1" and "fastboot erase modemst2" will turn off SIM lock definitely and allow OEM unlock option to stop being greyed out in developer options (behaviour introduced in OOS versions superior to 9.0.11). That will allow to unlock bootloader and then root/flash custom roms.
Credits:
@Titokhan for giving advice on how to present thread
@headsh0t95 for suggesting me to request an access to upload files on AndroidFileHost
@AndroidFileHost for the hosting
OnePlus for the device and OS
Some_Random_Username said:
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been modified before it was cool.
Hi everyone, similar to my threads for OP3, OP3T, OP5, OP5T and OP6 as unbrick tools allow to (obviously) unbrick your phone but also to rollback to specific versions of Oxygen OS I decided to search for more and succeeded in that.
I managed to find out 9.0.12 one (which is as of writing the latest available) but also the first one released for OOS 9.0.4 and linked to 9.0.11 , 9.0.6 and 9.0.5 packages shared by @iaTa in his thread and by @SpasilliumNexus in his AFH here
You can find instructions and Qualcomm drivers here.
This is not a support thread: if you have questions on how to use tool or issues please ask in the relevant thread.
Here are the files uploaded on AndroidFileHost ordered by Android version:
ANDROID 9:
DECRYPTED OOS 9.0.12
DECRYPTED OOS 9.0.11
DECRYPTED OOS 9.0.6
DECRYPTED OOS 9.0.5
DECRYPTED OOS 9.0.4
Click to expand...
Click to collapse
Decrypted. Wot?
ZeroKool76 said:
Decrypted. Wot?
Click to expand...
Click to collapse
Decrypted meaning no longer protected by passwords sorry for the confusion but if you take a look at the previous threads I made you might notice that some of the files are still password protected as OnePlus support don't give you these files already decrypted when they remote to your computer to help you to unbrick your phone -which is quite understandable as they allow to bypass Google Factory Reset Protection-.
Some_Random_Username said:
Decrypted meaning no longer protected by passwords sorry for the confusion but if you take a look at the previous threads I made you might notice that some of the files are still password protected as OnePlus support don't give you these files already decrypted when they remote to your computer to help you to unbrick your phone -which is quite understandable as they allow to bypass Google Factory Reset Protection-.
Click to expand...
Click to collapse
Awesome. Thank you for the clarification
Added 9.0.13 unbrick tool
Guys i am not that experienced on this stuff. I've bricked my 6t and dont have access to a windows computer. either mac or linux only. Anyway to run this on mac or linux?
Some_Random_Username said:
Added 9.0.13 unbrick tool
Click to expand...
Click to collapse
Where is it?!
gasroca said:
Guys i am not that experienced on this stuff. I've bricked my 6t and dont have access to a windows computer. either mac or linux only. Anyway to run this on mac or linux?
Click to expand...
Click to collapse
The tool is sadly Windows only but you could try to setup a virtual machine with USB passthrough
kermex said:
Where is it?!
Click to expand...
Click to collapse
In the first post perhaps?
Some_Random_Username said:
The tool is sadly Windows only but you could try to setup a virtual machine with USB passthrough
In the first post perhaps?
Click to expand...
Click to collapse
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Some_Random_Username said:
In the first post perhaps?
Click to expand...
Click to collapse
That DECRYPTED OOS 9.0.13 link?
Anyone ever come across an open beta msm? And FYI, if you copy Anon tipsters patched msm factory.exe to this tools working directory, it works.
Thanks man
gasroca said:
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Click to expand...
Click to collapse
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
kermex said:
That DECRYPTED OOS 9.0.13 link?
Click to expand...
Click to collapse
Yes
fullofhell said:
Anyone ever come across an open beta msm? And FYI, if you copy Anon tipsters patched msm factory.exe to this tools working directory, it works.
Click to expand...
Click to collapse
As far as I know OnePlus doesn't provide any open beta msm tool. Anon tipsters patched msm factory.exe will indeed work however as written here 9.0.11 version must be used if user wish to unlock bootloader as later versions of OOS closed the loophole that allowed T-Mobile owners to do so
Some_Random_Username said:
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
Click to expand...
Click to collapse
Yeah thanks. I've managed to fix it after almost 2 days of messing about with it its now back to normal ?
Some_Random_Username said:
Did you try maintaining power button to force it to shutdown? I don't see anything else that could be done otherwise
Yes
As far as I know OnePlus doesn't provide any open beta msm tool. Anon tipsters patched msm factory.exe will indeed work however as written here 9.0.11 version must be used if user wish to unlock bootloader as later versions of OOS closed the loophole that allowed T-Mobile owners to do so
Click to expand...
Click to collapse
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
gasroca said:
Cannot get the device off this screen, no buttons combinations, commands or anything, doesn't get recognised as device either.. Anyone, any suggestions?
Click to expand...
Click to collapse
If u haven't fixed yet, your partitions are derped. Power off and run msm. Or just run a fastboot rom to fix. When that happens just msm, it's the quickest. And if u do as I explained above u can just use the newest msm and not have to upgrade..
fullofhell said:
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
If u haven't fixed yet, your partitions are derped. Power off and run msm. Or just run a fastboot rom to fix. When that happens just msm, it's the quickest. And if u do as I explained above u can just use the newest msm and not have to upgrade..
Click to expand...
Click to collapse
facts tho i prefer fastboot method, just remove the windows related **** from the bat and copy paste.
@fullofhell where is your repo
xstefen said:
facts tho i prefer fastboot method, just remove the windows related **** from the bat and copy paste.
@fullofhell where is your repo
Click to expand...
Click to collapse
Yeah that's what I do
---------- Post added at 09:09 PM ---------- Previous post was at 08:27 PM ----------
I made a bunch of scripts for Debian bases distros.. i use newest pop os...wonder if we could port msm over somehow...lol
fullofhell said:
Yeah that's what I do
---------- Post added at 09:09 PM ---------- Previous post was at 08:27 PM ----------
I made a bunch of scripts for Debian bases distros.. i use newest pop os...wonder if we could port msm over somehow...lol
Click to expand...
Click to collapse
I typically run Arch or a derivative but its all the same, I'd help with whatever I could.
fullofhell said:
Ok just wondering about the beta. Through my extensive testing the past few months I discovered No, they only patched the loophole if one has not first converted then did fastboot erase modemst1 then fastboot erase modemst2.. then the thing that causes oem unlock to be greyed for users using msm 12 and up is disabled. Those commands turn off sim lock in the hardware.once that is done one time. Users can simply copy the patched msm exe to every new additional msm tool directory. After erasing those both at least one time after a first conversion with 9.011, u can have the device fully international and every tool allows it to work. I discovered the greying out and disabling of oem unlock starting with 9.0.12 and discussed it in various threads and people didn't pay attention to it lol. Erasing modemst1 and modemst2 simply turns off the lock. For good. Then if u check engineer mode it says sim lock off and that's even if u never used a bin. This supercedes that even. So maybe update the first post to include that is a confirmed way to cement your conversion without the issue of simlock and a voiding of the 9.0.11 bootloader unlock workaround. This is permanent and once u do so any msm furthermore works to allow bootloader unlock
Click to expand...
Click to collapse
Just to be sure, that engineer mode can be accessed from *#808# and SIM lock section is when swiping to the right, in "Others column"? It is like that on my 5T (see screenshot) but I don't know if it's same on a converted 6T