What it says in the title. I got the phone from a guy, who I assume got it from aliexpress (because it had gifts with it) or imported some other way. The phone came in fully packed up, in all kinds of stickers and protective thingies and in it's box, with all the equipment packaged. Even has the protective thing (can't remember the eng word) over the screen still, so I'm pretty sure the phone is new and not used.
Anyway, if I'm not wrong the bootloader shows its already unlocked. Now my first goal is to root it, and I saw a lot of guides, and decided to follow these here but theres separate guides for officially unlocked and unofficially. My phone came like this so I don't know which is it.
{
"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"
}
So questions:
1. How can I know whether its officially unlocked or unofficially?
2. Did I decide to follow the right guide or is there better ones?
3. My MTP and other drivers isn't working. I have Windows 7 Ultimate. EDIT: After installing a bunch of drivers I found, including the Mi PC Suite, universal adb drivers, and what not, MTP appears to be working, I can access the phone just fine and theres no exclamation mark over it like in "Devices and Printers". But I have some exclamation marks in device manager, as seen on screenshot. I'm not sure if "Unknown Device" is related. It could have been there before the phone, but ADB is new.
4. Are these exclamation marks an issue for following the guides to root and flash? The fastboot commands from screenshots work fine.
Phone Info:
- Android Version 5.1.1
- MIUI Version MIUI Global 7.3 | Stable
Sorry for the long post.
ChrisBunny said:
What it says in the title. I got the phone from a guy, who I assume got it from aliexpress (because it had gifts with it) or imported some other way. The phone came in fully packed up, in all kinds of stickers and protective thingies and in it's box, with all the equipment packaged. Even has the protective thing (can't remember the eng word) over the screen still, so I'm pretty sure the phone is new and not used.
Anyway, if I'm not wrong the bootloader shows its already unlocked. Now my first goal is to root it, and I saw a lot of guides, and decided to follow these here but theres separate guides for officially unlocked and unofficially. My phone came like this so I don't know which is it.
So questions:
1. How can I know whether its officially unlocked or unofficially?
2. Did I decide to follow the right guide or is there better ones?
3. My MTP and other drivers isn't working. I have Windows 7 Ultimate. EDIT: After installing a bunch of drivers I found, including the PCSuite, universal adb drivers, and what not, MTP appears to be working, I can access the phone just fine and theres no exclamation mark over it like in "Devices and Printers". But I have some exclamation marks in device manager, as seen on screenshot. I'm not sure if "Unknown Device" is related. It could have been there before the phone, but ADB is new.
4. Are these exclamation marks an issue for following the guides to root and flash? The fastboot commands from screenshots work fine.
Phone Info:
- Android Version 5.1.1
- MIUI Version MIUI Global 7.3 | Stable
Sorry for the long post.
Click to expand...
Click to collapse
1. If you buy it new the boot loader should be LOCKED , according to your screenshot it has been unlocked either by the seller or who knows but it's unlocked.
2. that guide is for installing twrp (custom recovery) not unlocking- but yeah to root you need to install twrp then supersu
https://download.chainfire.eu/969/SuperSU/
3. to get the correct drivers install MI PC Suite it has mostly everything you need for this device.
4. you shouldn't have any exclamation marks, try installing Mi Pc Suite.
otyg said:
1. If you buy it new the boot loader should be LOCKED , according to your screenshot it has been unlocked either by the seller or who knows but it's unlocked.
2. that guide is for installing twrp (custom recovery) not unlocking- but yeah to root you need to install twrp then supersu
https://download.chainfire.eu/969/SuperSU/
3. to get the correct drivers install MI PC Suite it has mostly everything you need for this device.
4. you shouldn't have any exclamation marks, try installing Mi Pc Suite.
Click to expand...
Click to collapse
1. Yes but the problem is I don't know whether its officially unlocked or unofficially unlocked, and its important because the guides for rooting and flashing twrp are different. That's what I'd like to know, but don't know how.
2. Yep. Like I said I'd like to root it, and later probably flash a CM rom, but I need TWRP first.
3. Already installed Mi PC Suite (forgot to write "Mi" in the Mi PC Suite, I'll correct that), and its working. Kind of. I can't make a backup, and sometimes it tells me theres an update when I plug the phone in (I'm reluctant to update atm), but when I press the "Update" it says the firmware is up to date. The rest of the functions seem to be working, like screencast or viewing the storage.
4. The exclamation mark is related to ADB, I don't know if Mi PC Suite should be installing that too, but anyway its there.
@ChrisBunny
There is no way to tell what method was used to unlock your phone. More than likely it is unofficial.
Your getting exclamation marks because some drivers haven't been installed properly, you may have to uninstall and reinstall to get the right versions installed.
What is the reported MIUI version in settings about phone? If your not getting something with four numbers (X.X.X.X). You could possibly have a vendor rom. Which may have spyware etc and you won't get updates.
corkiejp said:
@ChrisBunny
There is no way to tell what method was used to unlock your phone. More than likely it is unofficial.
Your getting exclamation marks because some drivers haven't been installed properly, you may have to uninstall and reinstall to get the right versions installed.
What is the reported MIUI version in settings about phone? If your not getting something with four numbers (X.X.X.X). You could possibly have a vendor rom. Which may have spyware etc and you won't get updates.
Click to expand...
Click to collapse
I'm assuming its unofficial too. If its from aliexpress I doubt they wait for official unlock for each phone they ship.
Also it came with Google Apps and MIUI apps. Didn't see chinese kanji on any apps or menu.
The MIUI version is "MIUI Global 7.3 | Stable" and under it says "7.3.6.0.0(LHOCNDD)".
Most aliexpress redmi note 3 pro pages say something like "we will open the original box to check the phone and install Multi-language ROM and Google play store,If you have special requests about the original box,please leave us a message" and also "And Many Multi-language ROM not support OTA Update" whatever OTA Update is. Over-the-air I assume. Which means the built in "Update" app shouldn't work. Which is fine, my old phone LG Optimus L7 II Prime didn't support OTA either. I didn't tap it yet in case it started updating right away, and I don't want to change anything without first backing up the entire rom, just in case, but don't know how to do that yet.
ChrisBunny said:
The MIUI version is "MIUI Global 7.3 | Stable" and under it says "7.3.6.0.0(LHOCNDD)".
Click to expand...
Click to collapse
That is definitely a Vendor Rom.
https://www.reddit.com/r/Xiaomi/wiki/roms/unofficial
Sort out your drivers first.
Then flash an official global developer rom, which might re-lock your bootloader and then unlock officially.
https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
I assume you don't have the mediatek version of RN3?.
corkiejp said:
That is definitely a Vendor Rom.
https://www.reddit.com/r/Xiaomi/wiki/roms/unofficial
Sort out your drivers first.
Then flash an official global developer rom, which might re-lock your bootloader and then unlock officially.
https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
I assume you don't have the mediatek version of RN3?.
Click to expand...
Click to collapse
"also adware and bloatware, which are annoying and slow the phone down. This ROM is also buggy and unoptimised, so some things might not work (e.g. battery showing negative percentage or the rear LED not working at all), you might encounter issues and inconsistencies (e.g. freezing, lagging)" funny I'm not experiencing any of that. No bloatware except a couple Mi stuff and usual system apps you'd find on the phone like Calendar and explorer and what not. The only new thing I didn't see on other phones is "Security" app. It appears to be a very clean vendor rom then. Its super fast and smooth I'm impressed.
Yes the phone is Pro version, with Snapdragon. Are the pictures I posted not visible?
If its already unlocked unofficially, should I be relocking it and then applying for an unlock? Isn't it simpler to just follow the unofficial guide for flashing?
ChrisBunny said:
Yes the phone is Pro version, with Snapdragon. Are the pictures I posted not visible?
If its already unlocked unofficially, should I be relocking it and then applying for an unlock? Isn't it simpler to just follow the unofficial guide for flashing?
Click to expand...
Click to collapse
I didn't notice the third image posted.
DO NOT lock it while on a vendor rom.
Is it up to yourself, if you want it unlocked officially or not. You just need to be careful when flashing.
I still get rid of the vendor rom. If you want future updates and to avoid unknown/unseen future bugs.
corkiejp said:
I didn't notice the third image posted.
DO NOT lock it while on a vendor rom.
Is it up to yourself, if you want it unlocked officially or not. You just need to be careful when flashing.
I still get rid of the vendor rom. If you want future updates and to avoid unknown/unseen future bugs.
Click to expand...
Click to collapse
Yeah but is there any disadvantages to having an unofficial unlock over official? If not then I guess I'll just be careful following the unofficial guide for flashing. If there is disadvantages then I'll apply for official unlock and just wait.
I do want to get rid of this rom at some point and try CM if theres a fully functional one, but for now I'd just like TWRP and root on it.
ChrisBunny said:
Yeah but is there any disadvantages to having an unofficial unlock over official? If not then I guess I'll just be careful following the unofficial guide for flashing. If there is disadvantages then I'll apply for official unlock and just wait.
I do want to get rid of this rom at some point and try CM if theres a fully functional one, but for now I'd just like TWRP and root on it.
Click to expand...
Click to collapse
With unofficial unlock you have to be very precautious while flashing MIUI based rom else hard brick later is not the case for official unlock
Related
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
yoyohoho said:
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
Click to expand...
Click to collapse
HDX Nexus 4.0.5 was likely rooted. Regardless, it's an older/discontinued build that should be updated.
You can install TWRP on any rooted 3rd gen HDX by following step #2 (only) in the OP in this thread; steps #1 and #3 pertain to unlocking the bootloader.
Please note that while the above procedure has been sucessfully executed by dozens of HDX owners there is risk involved that could easily lead to a bricked device. Basically if anything goes wrong the device is toast.
Once TWRP is available you can flash the HDX builds of CM 11 or Fire Nexus HDX (successor to v4.0.5). Be sure to follow the flashing instructions in the relevant ROM thread OP. You will need to unlock the bootloader to install any other custom ROM.
Unlocking bootloader
Thank you, thank you, your simple instructions worked liked a charm. Only took about 10 minutes to complete, yet I spent 4 hours searching forums for an answer....ackkk.
Anyhow, at some point I'd like to upgrade to CM12 since there are a couple apps that require Android 5.1 or later. So I need to get my bootloader unlocked. I followed the posting by ONYXis, but it kept saying that unlock code is incorrect. My question is: Would the procedure work if I installed FireOS (maybe 4.5.2)? Or am I missing some other step?
Thank you, thank you again
yoyohoho said:
Thank you, thank you, your simple instructions worked liked a charm. Only took about 10 minutes to complete, yet I spent 4 hours searching forums for an answer....ackkk.
Anyhow, at some point I'd like to upgrade to CM12 since there are a couple apps that require Android 5.1 or later. So I need to get my bootloader unlocked. I followed the posting by ONYXis, but it kept saying that unlock code is incorrect. My question is: Would the procedure work if I installed FireOS (maybe 4.5.2)? Or am I missing some other step?
Thank you, thank you again
Click to expand...
Click to collapse
Unlock code and application procedure works on any rooted 3rd gen HDX with a vulnerable bootloader regardless of installed ROM, recovery, etc. Most likely you have a typo in one of the input values or the concatenated string fed to the code generator is not in the proper format. Look carefully at required format in the OP along with your manfid and serial to insure everything is to spec.
If still no joy post your manfid and serial in the other thread (referencing this discussion) and request someone generate an unlock code on your behalf. I am travelling this weekend with no access to my Windows box until Monday.
Be aware unlocking poses no risk to your device; it will either work or not. Also try a different USB port and/or cable. I know it sounds far fetched but amazing how many times that "fixes" fastboot weirdness.
Solved
Davey126 said:
Unlock code and application procedure works on any rooted 3rd gen HDX with a vulnerable bootloader regardless of installed ROM, recovery, etc. Most likely you have a typo in one of the input values or the concatenated string fed to the code generator is not in the proper format. Look carefully at required format in the OP along with your manfid and serial to insure everything is to spec.
If still no joy post your manfid and serial in the other thread (referencing this discussion) and request someone generate an unlock code on your behalf. I am travelling this weekend with no access to my Windows box until Monday.
Be aware unlocking poses no risk to your device; it will either work or not. Also try a different USB port and/or cable. I know it sounds far fetched but amazing how many times that "fixes" fastboot weirdness.
Click to expand...
Click to collapse
Many, many thanks to you, Davey126, for your encouragement and patience with my noobness.
I knew my unlock file was OK since I verified with OpenSSL... cable, ports and drivers were OK too.
The solution for ME was to switch over to a WinXP box from a Win10 box, and it worked flawlessly. I admit though that I still use XP as my main system so I'm very familiar with it, however, when I started this endeavor things like Android SDK needed a 64-bit box.
Anyways, thanks again for your support and score one for WinXP
yoyohoho said:
Many, many thanks to you, Davey126, for your encouragement and patience with my noobness.
I knew my unlock file was OK since I verified with OpenSSL... cable, ports and drivers were OK too.
The solution for ME was to switch over to a WinXP box from a Win10 box, and it worked flawlessly. I admit though that I still use XP as my main system so I'm very familiar with it, however, when I started this endeavor things like Android SDK needed a 64-bit box.
Anyways, thanks again for your support and score one for WinXP
Click to expand...
Click to collapse
Glad you got everything working! Sometimes good old XP still shines bright.
I too have got the same device as yours with the same HDX nexus ROM installed which has glitches like you mentioned (automatic startup of apps etc), managed to root it and managed to install twrp but just can't make fastboot execute unlock probably windows fastboot driver issues. I am working on it, may be i will try with win xp on a virtual machine. By the way, i wanted to know which ROM did you try and which one did you find to be working well with this device with buttery smooth experience and no glitches and that all those glitches were settled after bootloader unlock and flashing of a ROM? kindly do suggest some ROM and if possible the drivers that you used to unlock or any other details necessary. thanks
Same here, but i can't to root my device
I tried kingroot and towelroot, but didn't works
ybridos said:
Same here, but i can't to root my device
I tried kingroot and towelroot, but didn't works
Click to expand...
Click to collapse
same here, refubrished device from ebay, Nexus Rom, stock recovery, and unable to root it, kinroot didn't work :crying:
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Hey, im just rooted it! All what needed were Factory reset and mobile Kingroot. Hope this will work for other preople!
xob0t said:
same here, refubrished device from ebay, Nexus Rom, stock recovery, and unable to root it, kinroot didn't work :crying:
---------- Post added at 10:43 AM ---------- Previous post was at 10:11 AM ----------
Hey, im just rooted it! All what needed were Factory reset and mobile Kingroot. Hope this will work for other preople!
Click to expand...
Click to collapse
I have tried with Kingoroot and it is worked on first try. May be helpful to you, good luck
I have same device with #Davey126
I wanna install TWRP and then root my KF,
so, Is this step below is good for me?
2. Flash old vulnarable aboot and cubed twrp (just in case). Check that all these commands executed without errors. If you'll get one - read second post below. If your firmware <=13(14)3.2.3.2 skip this step.
Download aboot and twrp for Thor (Kindle Fire HDX 7) https://drive.google.com/open?id=0B2...GxXMUZPZTlZTUk or for Apollo (Kindle Fire HDX 8.9) - https://drive.google.com/open?id=0B2...zJDQkczNzRLaHM - and put this two files (twrp_cubed.img and aboot_vuln.mbn) into root of your kindle internal storage.
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now you have working twrp recovery. It already works even without unlocked bootloader. You could boot into it by holding volUP during grey kindle logo. But no need to flash anything until unlock. At this point this is just emergency tool if something goes wrong =)
Click to expand...
Click to collapse
Quoted from https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
yoyohoho said:
Howdy,
I bought a refurbished HDX 7" (thor) off Amazon, it came with HDX Nexus ROM (v4.0.5 @ ggow), Android 4.4.4 already installed. It has a few hick-ups (like the updated Play Store always stops, and some apps, like Dialer, will startup themselves), anyways I'd like to switch to CM or at least get a fresh install of Nexus. Rooting was easy with KingRoot, the bootloader is locked and all attempts to unlock have failed (Unlock code is not correct).
From what I understand, I can't install TWRP without unlocking the bootloader and I can't install SafeStrap since I don't have FireOS installed.
Any ideas?
Thanks a bunch.
Click to expand...
Click to collapse
Can anyone help me unlock bootloader?
my KF HDX 7 ís same #yoyohoho with 4.4.4 installed.
I searched few days, but cant find exactly way, because my english is so bad
Hey yoyohoho, can u help me?
Mark2014 said:
Can anyone help me unlock bootloader?
my KF HDX 7
Click to expand...
Click to collapse
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
I read it before but not sure. tks
Davey126 said:
https://forum.xda-developers.com/ki...ing-bootloader-firmware-t3463982/post75284993
Click to expand...
Click to collapse
i'm follow your link but stucked after go into [fastboot]
image attached below.
{
"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"
}
KF screen alway show Ready without step:
5. On the Computer go to Device-Manager and change driver in "Other Android" to "Fire Devices - Android Adb Composite Driver" . It should say "Ready" on the Kindle.
it shows "waiting for device" and I wait a half of hour but nothing happen.
Iam using win7 64b, and usb driver already installed.
What should I do next?
hi there, i have similiar situation, yet a little bit different. from Fire OS (don't remember version number) i went to this ROM: https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 and i have Bootstrap on my device. it means, that my BL is locked. may i use this steps https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006 to unlock BL?
miguelm75 said:
hi there, i have similiar situation, yet a little bit different. from Fire OS (don't remember version number) i went to this ROM: https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931 and i have Bootstrap on my device. it means, that my BL is locked. may i use this steps https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006 to unlock BL?
Click to expand...
Click to collapse
Yes. Linked procedure does not care how the device is currently configured.
Davey126 said:
Yes. Linked procedure does not care how the device is currently configured.
Click to expand...
Click to collapse
thanks. i have one problem - where should I look for drivers to change drivers to "Fire Devices - Android Adb Composite Driver"? because when i try to change to drivers installed to c:\Program Files (x86)\Amazon.com\Fire_Devices\, system says "I cannot install Android device".
my operation system is Windows 10
miguelm75 said:
thanks. i have one problem - where should I look for drivers to change drivers to "Fire Devices - Android Adb Composite Driver"? because when i try to change to drivers installed to c:\Program Files (x86)\Amazon.com\Fire_Devices\, system says "I cannot install Android device".
my operation system is Windows 10
Click to expand...
Click to collapse
Install the Motorola Device Manager (here) which contains compatible drivers for HDX devices that work on a wide variety of platforms. You don't need to run the manager, just install it. One click goodness that actually does something userful.
Davey126 said:
Install the Motorola Device Manager (here) which contains compatible drivers for HDX devices that work on a wide variety of platforms. You don't need to run the manager, just install it. One click goodness that actually does something userful.
Click to expand...
Click to collapse
still no luck
this is strange - when Kindle is powered on, is visible in "Device Manager" as "Android Adb Composite Driver", but when i reboot it to BL, it's "Other devices"/"Android" and it cannot be changed
and i installed Motorola drivers. should i restart system?
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
87lwrdr said:
Sorry I posted this in the wrong area earlier and as you can probably guess I am very new to this. I have looked around on different sites and tried a few things with no success. I have an S4 Galaxy SCH-I545 v.I545VRSGPL1 and I want to upgrade it from it's present status of 5.0.1 to 7.1.2 or better and I have a few questions. 1) Does the phone have to rooted in order to do this and if so what do I use. From what I've read (and I hope I'm wrong) this particular phone from Verizon seems to be a difficult one. 2.) What would be the best performing upgrade for the phones hardware. Thanks to all for their help.
Click to expand...
Click to collapse
1) This phone has a locked bootloader and has to remain on Touchwiz. Rooting methods are posted in the General section. You're stuck on Lollipop with this device, however you can flash other ROMs with Flashfire.
2. That would be software. Hardware is things such as the speaker, Home button, or the device itself.
{
"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"
}
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
87lwrdr said:
Again, being new to this, what can I actually do to this phone? You say I'm stuck on Lollipop for the OS and Touchwiz for an interface what can I use to increase it's functionality and performance ability? I read where Marshmallow doesn't have as many significant changes from Lollipop as the changes were from KitKat to Lollipop but I always thought having the most current OS would aid you in using programs and security designed for newer OS's, just like with computers. What about security and update issues, will they stop supporting Lollipop leaving vulnerable? Or is that the idea, forcing you into buying a newer phone.
Click to expand...
Click to collapse
Pretty much, after 18-24 months companies just stop putting out new software (to get you to buy a new phone), that's part of the reason for using custom ROMs. This device is much older than that and has a locked bootloader, keeping you from doing a lot of things, like using a ROM with an unofficial kernel, so the latest software is not possible. The Sprint and TMo versions of this phone do not have locked bootloaders and are able to use Marshmallow and Nougat, etc. So root the phone using the one methods outlined in the General section (you need to use one that uses SuperSU to use Flashfire) of this forum and then use Flashfire to flash a custom ROM in the Android Development. New features and better functionality. I also recommend removing apps you don't use to decrease RAM consumption and increase performance.
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
87lwrdr said:
Are you saying I can root this version of my S4 (Galaxy S4 SCH-I545 v.I545VRSGPL1) and then install a custom rom to it using either SuperSU or Flashfire, right? For this version of phone are there any custom roms you would suggest using that are designed more for it? Sorry for all the questions, I just don't want to do something I'll be sorry for or can't reverse or fix.
Again, thanks for all your help and guidance.
Click to expand...
Click to collapse
SuperSU is required to use Flashfire, but yes. I would Odin OF1 first or WiFi won't work, I would suggest Stanglitre's ROM it was the most stable I tried for the short time I had this device.
What do I use on build LRX22C.I545VRSGPL1?
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
87lwrdr said:
I have seen other roms on the site but how do I know if they will work for my build of phone? I try to read as much as I can but the way some people talk and explain things in some of the posts it might as well be in a foreign language. lol. I hope in time I'll be able to understand all the meanings, but right it's a little tough and I don't want to mess things up because I wasn't sure of something. Are the roms made for specific builds or can any be used?
Click to expand...
Click to collapse
Yes they are for specific builds. You really picked one of the worst phones to start with. Do you have a PC?
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
87lwrdr said:
Yes, I have a PC. I didn't know anything about this phone when I got it much less the problems I'm facing with it now. I just don't like these phone companies or anyone else backing you into a corner and forcing you to buy something newer because they quit taking care of that product when it's only a couple years old.
Click to expand...
Click to collapse
This device is more than a couple years old... But I would recommend downloading the OF1 firmware from wwe.sammobile.com and using the Odin program to flash it. Then you can use a few of the ROMs on here.
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
87lwrdr said:
I believe I've flashed the phone successfully. The Baseband Version was - I545VRSGPL1 and now it is - I545VRUGOF1 The Android Version is still 5.0.1 At this point what can I do with or to it now? Thanks
Click to expand...
Click to collapse
You can now root it and flash a ROM. Just follow the rupturing instructions in the General section of the forum.
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
87lwrdr said:
Not sure what happened but here goes. I flashed the phone to OF1 and then tried to root it so I could put on a new rom. I used kingoroot to root the phone and it showed rooted but could not load flashfire. tried a couple times but kept getting a message that the bianary was occupied and after that when I tried to boot it the phone would freeze on the verizon red boot logo. I tried to re-flash OF1 and now it's stuck on "software update failed" with a yellow triangle and under that it says " your device didn't update successfully". I'm gonna guess that all of this isn't a good thing and hope there is a possible fix for this. Any insight and help would be greatly appreciated.
Click to expand...
Click to collapse
Reflash OF1 with Odin and start over. I told you SuperSU was needed for Flashfire to work right. You need to use a root method that uses SuperSU. There is a couple guides in the General section of this forum.
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
87lwrdr said:
It won't re-flash. I can boot the phone to d/l mode, then start odin, load the of1 file, it checks it successfully and when I hit start it starts working and stops in about ten seconds while trying to load "system.img.ext4" and shows FAILED
Click to expand...
Click to collapse
Try OC1 tar instead.
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
87lwrdr said:
After numerous times of trying and using different cables and com ports it finally took the OF1 firmware successfully. I don't know if it was using a different port or cable or just a combination of all, but it worked. I used a root checker and it says it's not rooted. Now, do I root with SuperSU then use FlashFire to install the new rom?
Click to expand...
Click to collapse
Yes
Hi tell us how it was please...I am with the same trouble can not pass from lollipop don't have any rom mod nothing
This is the Honor View 10 's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"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"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
I used this on 5T and it did work super.
But i am wondering if this is working for view10 or not... V10 requires a unique code to unlock BL, where do we provide that code here?
Also rooting v10 requires an img to be flashed. Is this tool working?
Anyone tested all these features on View10??
venreddy said:
I used this on 5T and it did work super.
But i am wondering if this is working for view10 or not... V10 requires a unique code to unlock BL, where do we provide that code here?
Also rooting v10 requires an img to be flashed. Is this tool working?
Anyone tested all these features on View10??
Click to expand...
Click to collapse
I have tested it on my honor view 10, to unlock your bootloader you still need of huawei unlock codes, always remember this tool automate process not bypass it (except it is not specified). This tool can't root the phone directly
EDIT: there is a little bug when you try to unlock the bootloader and your phone is in powered on and recognized in adb mode, i'm releasing a new version to fix it at this moment
EDIT 2: update released
mauronofrio said:
I have tested it on my honor view 10, to unlock your bootloader you still need of huawei unlock codes, always remember this tool automate process not bypass it (except it is not specified). This tool can't root the phone directly
EDIT: there is a little bug when you try to unlock the bootloader and your phone is in powered on and recognized in adb mode, i'm releasing a new version to fix it at this moment
EDIT 2: update released
Click to expand...
Click to collapse
Hi
Thanks for excellent tool. I have installed it and watched the videos you posted for OnePlus. You have used SuperSu in case of OnePlus. But for Honor View 10 I want to use Magisk. Can you please let me know the step?
vku369 said:
Hi
Thanks for excellent tool. I have installed it and watched the videos you posted for OnePlus. You have used SuperSu in case of OnePlus. But for Honor View 10 I want to use Magisk. Can you please let me know the step?
Click to expand...
Click to collapse
The videos are not made by me, i found it on youtube and i added the link to tool description. To root your device you need to see this guide: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
mauronofrio said:
The videos are not made by me, i found it on youtube and i added the link to tool description. To root your device you need to see this guide: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Click to expand...
Click to collapse
Thanks for response. So far I unlocked the boot loader (really easy with your tool one click only thanks for it). For root
how to install Magisk Manager using your tool. Which button to use
1. Recovery flasher
2. Recovery Zip flasher
Bear with me if it sounds naïve this is first time I am trying to root
vku369 said:
Thanks for response. So far I unlocked the boot loader (really easy with your tool one click only thanks for it). For root
how to install Magisk Manager using your tool. Which button to use
1. Recovery flasher
2. Recovery Zip flasher
Bear with me if it sounds naïve this is first time I am trying to root
Click to expand...
Click to collapse
You can't root your phone with this tool, you need to follow that guide
You can installa magisk manager through "apk installer"
Just for info, Files are available for V10 now on firmware finder.
shashank1320 said:
Just for info, Files are available for V10 now on firmware finder.
Click to expand...
Click to collapse
link?
mauronofrio said:
link?
Click to expand...
Click to collapse
On app here it is. Can give you link if want
shashank1320 said:
On app here it is. Can give you link if want
Click to expand...
Click to collapse
The problem is i have the bkl-l04 version and for it there are not stock firmware available so i can't test it for now
just 2 questions - does it work for Honor 10 (not v10)? can I do recovery backup here?
PeterMarkoff said:
just 2 questions - does it work for Honor 10 (not v10)? can I do recovery backup here?
Click to expand...
Click to collapse
Honor 10 is not supported officially, you cant do a recovery backup with this tool
Hi guys.
I'm looking forward for Honor View 10 or Honor 10, and as I'm with Samsung S8, I'm trying to understand if these Honor devices can receive a recovery consol or be rooted in a way that can be restored to stock without being noticed from official assistance in case I'll need to go for an assistance in warranty.
Second, as I'm with Samsung since years, I've always seen to need a recovery consol and a root package to flash (as standard classic methods) for having complete access to phone, while here I read about unlocking and unlocking cuts from Honor (that I'm reading now it seams that they stopped to release easily the code needed), recovery, bootloader and other things that I'm completely lost in reading
I'm not speaking of the strict interest in flashing alternative roms, but at least to have the possibility to clean the phone deeply once in a while manually with SD-Maid, RootExplorer and other apps (maybe you know of more professional...) so for it not to get fat and more fat in time, with the possibility to clean corps and old unused system files without the need of a wipe, so to have a slim internal sd-card as much as I can (specially if I'll go for the Honor 10)
So please explain me a bit of what is this Honor world as I'm really willing to they one even tomorrow!!
Thanks to allall.
Sent from my SM-G950F using Tapatalk
Work this for mate 9...?
PIRATA! said:
Hi guys.
I'm looking forward for Honor View 10 or Honor 10, and as I'm with Samsung S8, I'm trying to understand if these Honor devices can receive a recovery consol or be rooted in a way that can be restored to stock without being noticed from official assistance in case I'll need to go for an assistance in warranty.
Second, as I'm with Samsung since years, I've always seen to need a recovery consol and a root package to flash (as standard classic methods) for having complete access to phone, while here I read about unlocking and unlocking cuts from Honor (that I'm reading now it seams that they stopped to release easily the code needed), recovery, bootloader and other things that I'm completely lost in reading
I'm not speaking of the strict interest in flashing alternative roms, but at least to have the possibility to clean the phone deeply once in a while manually with SD-Maid, RootExplorer and other apps (maybe you know of more professional...) so for it not to get fat and more fat in time, with the possibility to clean corps and old unused system files without the need of a wipe, so to have a slim internal sd-card as much as I can (specially if I'll go for the Honor 10)
So please explain me a bit of what is this Honor world as I'm really willing to they one even tomorrow!!
Thanks to allall.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Honor and huawei devices can be unlocked, there are available twrps and you can do what you want. They can be restored to stock.
mataflakitas said:
Work this for mate 9...?
Click to expand...
Click to collapse
Mate 9 is not officially supported, if it has kirin 970 you can try to select honor view 10 and use the tool
Hey buddy, thanks for this amazing tool. I need to know, if there's need of the Bootloader Code for unlocking it on a Honor V10?
Also, if I need to add a phone that's in similar state as this phone (LG Stylus 2 Plus, currently not supported by LG for unlocking with their tool), can I send everything that you may need for making the tool compatible with it?
Thanks in advance!
i tried today on my honor view 10 to unlock bootloader, cant work
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"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"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Gordster said:
I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
Click to expand...
Click to collapse
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thank you sd_shadow. I appreciate your very detailed response and answer. I will try your methods and hopefully be able to return to Android 10. Android 11 seems to currently have a lot of bugs at least with the Moto G Power phone. Wish I had stayed on Android 10.
sd_shadow said:
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.
First Unlock the bootloader
[Guide]Un/locking Motorola Bootloader
UnLocking and ReLocking Motorola Bootloader https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a Moto Bootloader Unlocking site Re-Locking see Post #4 More about bootloader UnLocking Post #2 Can my...
forum.xda-developers.com
Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...
You can find your firmware here
lolinet mirrors - firmware, software, iso etc.
lolinet mirrors - powered by h5ai
mirrors.lolinet.com
download. and Unzip it
Check if your device uses fastbootd
Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
There is no guarantee that either method will work, but it should.
On the phone
Toggle off "install updates" option in Dev Options
Click to expand...
Click to collapse
Thanks a lot sd_shadow
I tried Flash Option 2 using LMSA. Replaced all the Android 11 ROM files in the default download directory folder with official Android 10 ROM files, and then used the rescue option to flash the Android 10 files to the Moto g Power. Everything worked perfectly. I now have Android 10 back on my phone. I keep getting the notification that there is an Android 11 update available but just have to ignore this. Thanks again for your help.
Gord
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
darko454 said:
HEY im trying to flash stock rom using LMSA manually but a popup says cannot match current firmware ...
Is there somthing i can do to select and flash a downloaded firmware for lolinet?
thanks
Click to expand...
Click to collapse
Seems that lmsa doesn't work for some software channels, or if the baseband and the channel don't match.
What does getvar all say?
Code:
fastboot getvar all
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:
{
"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"
}
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
JackDHopper said:
Curious.
I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:View attachment 5375851
However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.
Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
Click to expand...
Click to collapse
Magisk Hide should be able to hide the bootloader status
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
It''s a game of cat and mouse, google introduces new security measures, magisk devs get to working a way around it... There is even a module now that lets you pass full safetynet with xposed and microg.
JackDHopper said:
Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).
Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.
THANK YOU VERY MUCH, sd_shadow.
Click to expand...
Click to collapse
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
jhford said:
@JackDHopper. I don't want to brick my Moto G8 Power 2020 running the Havoc 4.8 Android 11 ROM by screwing up a downgrade to Android 10 so I can flash LineageOS 11. So, can you please explain how you did it?
Thanks. Much appreciated.
Click to expand...
Click to collapse
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
Beetle84 said:
You dont need to downgrade again. You only downgrade if you flashed stock 11 again. Simply format data and flash the new rom from another custom rom.
Click to expand...
Click to collapse
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
jhford said:
@Bettle84 thanks for the reply. I'm running TWRP 3.5.0_10-0. I flashed the img files with fastbootd when i initially installed Havoc and when i upgraded to 4.8. So, do you mean that I can flash the LOS ROM in TWRP on top of Havoc without using fastbootd?
Thanks again
Click to expand...
Click to collapse
Yeah you should be able to
Beetle84 said:
Yeah you should be able to
Click to expand...
Click to collapse
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
jhford said:
OK. LOS is installed, but I can't find a GAPPS that works. Suggestions?
Thanks
Click to expand...
Click to collapse
No idea, i havent flashed anything on my g8 in a while
does this work with moto g power 2021, android 11 aint working for me either, always get the systen ui has stopped error and certain apps stop working
this is my model number just to make sure
Hi all!! I been trying to downgrade my moto g power 2021 to Android 10 from 11 and I been reading in this thread. At first I tried the second method of flashing that sd_shadow suggested and it seems after 32% a message that says "flash single partian, flash failed" pops up.
Then I tried the first method. I tried making the flashall.bat file and put it in the sdk tools directory as the steps said in the fast boot forum. It didn't work when I double clicked so then I put my supposed firmware zip files (that I got from the lolinet website above) inside the sdk tool directory (unzipped) and Android 10 actually installed. I skipped all the steps after factory reset so I can go into devmode and turn off automatic updates. However when I tried turning on my WiFi, the phone would crash and restart and it would do that everytime it tried to connect to the WiFi. Even after I factory reset my device again the same problem persisted. I managed to use lmsa to go back to 11. What can I do to fix this downgrade issue?
After 1.5 full days of many attempts to downgrade from A11 to A10, fastbootd is the answer! I used Motorola-XML-To-Batch-Script-master with stock firmware from bootloader with nothing but boot loops. went into fastbootd just for the hell of it and ran the bat and boom! back to stock 10!
I go into further details here: https://forum.xda-developers.com/t/how-to-downgrade-android-11-to-10.4283809/post-86614163