Related
[Q&A] How to root LG-P875 (Optimus F5) using motochopper [apply also to F3, F6? & F7]
Well, dear LG Optimus F3/5/6?/7 owners, you can root your device right now WITHOUT unlocking the bootloader Simply download the attached file below, extract its content and place it in a single directory. This tool works under Windows, Linux and Mac OS X :highfive:
Thanks a lot to goofyextreme for F3 & platinumpresto for F7 feedback :good:
Positive feedback needed for the F6
Non specific device rooting procedures for motochopper under supported OS's are available HERE -> original thread by the author of this tool ... Thanks a lot djrbliss !
My Optimus F5 was preloaded with JB 4.1.2 and i run Ubuntu x64 : Running motochopper on my device rooted it in about 1 min. or 2 !!!
Theorically you do not need something else than the extracted files from the provided archive and it's true for all motochopper supported OS's : Windows, Linux and Mac OS X : adb executable is embedded into this zip for these three operating systems !
Then, to be sure you have a working setup, please run :
Linux
From a terminal, please cd into the extracted archive directory and type :
Code:
# sudo ./adb.linux devices
... it must output something like this in your terminal :
Code:
# sudo ./adb.linux devices
List of devices attached
yourdeviceserialnumberhere
If you see the serial number of your device listed then you're ready to go further ! Ubuntu x64 works that way out of the box but recently i switched to another x64 Linux distribution and the above command failed, because of an incompatibilty problem beetween the motochopper adb executable and OS librairies ... if you're running a Linux distro and you do not have a correct output from the above command THEN install the adb package from the repository of your choice for your operating system ... after that is done you'll need to edit and modify slightly the motochopper Linux script (run.sh) in order to use the adb executable you've just installed instead of using the one provided by the zip file attached below when running the tool ! ... if you don't know how to modify this script, just let me know and i'll tell you what you need to do
Windows
First of all you'll need to install LG United Mobile Driver, then REBOOT, and type from an elevated command prompt ("launched as an administrator") :
Code:
# adb.exe devices
... it must output something like this in your terminal :
Code:
# adb.exe devices
List of devices attached
yourdeviceserialnumberhere
If you see the serial number of your device listed then you're ready to go further ! Otherwise check than you have enabled USB debugging in the "Developper Options" tab and that the USB connection mode is properly set on your phone (in the Windows device manager you must see an item which mention that an ADB Interface is installed on your system ... the real name on your system may vary from mine so i do not give an exact interface name ...)
Only when you have seen your device serial number in the output of the command "adb devices", you're OK to launch the motochopper tool :
Check that you're inside the extracted motochopper directory and please type :
Linux
Code:
# sudo ./run.sh
Windows
Code:
# run.bat
The tool will take 1 min. or 2 to complete ... and when your phone has rebooted, it's rooted It is safe to try it in my opinion because i don't think this tool can brick your phone in any way, in the worst case it will fail BUT please note this little disclaimer with care : i am not the developper of this great tool and if you decide to use it, then it's at your own risk ...
Happy rooting
NOTE : For Mac OS X users please refer to the original thread by the author of motochopper (link at the beginning of this post) because i don't know much about Mac OS ...
IMPORTANT NOTE : Some of the LG Optimus Fx Series models recently gained an OTA update ! THE motochopper tool apparently DOES NOT WORK AT ALL if you upgraded your ROM with the OTA update ! It seems to be USELESS to try it in such conditions BUT i think it is still HARMLESS to test the tool -> in the worst case it will fail ... if so, reset your device to factory settings from the Android menu and please try another way to root your phone; THAT SAID I REPEAT THE TOOL IS PROVIDED AS IS AND IF YOU DECIDE TO USE IT, IT WILL BE AT YOUR OWN RISK ...
INFO : As of 2014-03-10 i close this topic because it is useless => motochopper do not work anymore on LG Optimus Fx Series
See you around,
Bye
ne0zone75 said:
Of course on Windows, Linux and Mac YOU MUST HAVE a working Android Tools setup BEFORE running motochopper or it will fail !
Click to expand...
Click to collapse
In fact adb executable is embedded in the motochopper package for supported OS's so maybe you could try running it without properly installing Android Tools on your machine but i've not tested motochopper that way ...
Also, note that the motochopper package i used to root my LG-P875 install superuser (i switched to supersu after running the tool because i prefer that one ...) and busybox ...
Sent from my ASUS Transformer Pad TF300T with Tapatalk HD
NOTE : this message is obsolete please read the updated Q&A from the updated first post ... thank you !
worked on the F7
platinumpresto said:
worked on the F7
Click to expand...
Click to collapse
Happy to learn that
Sent from my LG-P875 with Tapatalk 2
I tried Motochopper with my LG F5 and it didn't work. It just says:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
And it just stays there. Other people seem to have this same problem with Motochopper. I assume I have my USB drivers installed, as when I first attached my F5 to my PC, it installed drivers automatically and I can copy files over to the phone.
I don't know what you mean about "Android Tools". Which android tools? I downloaded Android Developer Tools "adt-bundle-windows-x86_64-20130717", but nothing actually gets installed in any system directories for other programs to find, it's just an SDK.
Motochopper already has adb.exe included. I tried running as administrator and in XP compatibility mode and there was no change. I'm using Windows 8.
EDIT:
I finally got it working. I had to download the LGMobile Support Tool which was a chore itself, since the main download from the LG site is corrupt, so I had to find another version. Once that program was finally installed (it sits there doing nothing for the first 10 minutes of installation...I realized it must be downloading data from LGs SLOW server), it then updated itself to the latest version, which took another half an hour to download from the slow LG server.
Finally, from that program I could install the custom USB driver for the LG F5 (which is called P875 in the program just to confuse you). It downloaded and installed the USB driver not once, but twice (god knows why), and then told me the second time that the driver was already installed. What a piece of sh__ program.
Anyway, I ran the Motochopper afterwards, and it rooted my phone with no problems.
Works great!
I really appreciate this! I just downloaded the .zip file and ran the "run" executable. You hit enter, and wait until it's done rooting and rebooting. Then, you're rooted! By the way, this was on the LG Optimus F3. It seems as though this method works on the F3, F5, and F7 (at least that's the information that I've gathered so far). Again, thank you!
I've updated the Q&A today. Thank to all of you for providing feedback on the LG Optimus F Series and the compatibility with the motochopper tool !
Have a nice day
Someone have the contacts provider from their rooted F3?
Thanks for this guide -- I was able to root my Optimus F3 phone.
I do have one small problem, though: I accidentally deleted my contacts provider. Now certain apps aren't working at all. If someone has a rooted F3, it would be great if they could take the time to upload their contacts provider APK (located in /system/app) for me. (One from the F5 or F7 might work also.)
If you're on StackExchange, I have a bounty on Android Enthustiasts (android.stackexchange.com/q/52125/40230) for whoever can help me. Thanks!
Unlocking bootloader
It seems strange to me that this phone has been out for a few months now and no one has managed to unlock the bootloader. Does anyone know of any progress on this?
rt94 said:
It seems strange to me that this phone has been out for a few months now and no one has managed to unlock the bootloader. Does anyone know of any progress on this?
Click to expand...
Click to collapse
In fact there is a possible solution ... another tool also developped by djrbliss (motochopper author) which is named loki could do the job but at the moment the Optimus F5 is not supported by loki (Optimus F3/F7 are ). I've opened a ticket on the GitHub loki page for adding F5 support to loki but i have no answer for the moment ... may be you can do the same ...
You might be interested by these links ... :
Official loki thread on XDA Forum ...
Official loki GitHub page ...
Best regards
Super easy
Just rooted my brand new LG Optimus F5 with the motochopper. I haven't seen anything easier than this. One click button all done, piece of cake compared to rooting my previous few other android devices.:good:
.
Rooting failure
For some reason it won't work wotk my new LG Optimus F5 .
Everything seems to be just fine, until it outputs [-] Failure. at one point.
Code:
[*]
[*] Motochopper: Android root exploit (Windows version)
[*] v1.0
[*] by Dan Rosenberg (@djrbliss)
[*]
[*] Tested on the Motorola Razr HD, Razr M, Razr Maxx HD, and Atrix HD.
[*] Supports lots of other devices as well. ;)
[*]
[*] Before continuing, ensure that USB debugging is enabled, that you
[*] have the latest USB drivers installed, and that your phone
[*] is connected via USB.
[*]
[*] WARNING: This will likely void the warranty on your device. I am
[*] not responsible for any damage to your phone as a result using this
[*] tool.
[*]
[*] Press enter to root your phone...
Aby kontynuować, naciśnij dowolny klawisz . . .
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing exploit...
2766 KB/s (1283460 bytes in 0.453s)
[*] Pushing root tools...
2866 KB/s (366952 bytes in 0.125s)
3154 KB/s (1867568 bytes in 0.578s)
3946 KB/s (1578585 bytes in 0.390s)
pkg: /data/local/tmp/Superuser.apk
Success
[*] Rooting phone...
[+] This may take a few minutes.
[-] Failure.
[*] Cleaning up...
[*] Exploit complete. Press enter to reboot and exit.
Phone reboots and i end up with a Superuser app that won't install(no root access).
Tried on Lubuntu 13.04 as well as Windows XP SP3. Same results.
USB debugging enabled. Device serial number was shown on the list.
Any help on that?
nCom said:
For some reason it won't work wotk my new LG Optimus F5 ...
Click to expand...
Click to collapse
The good news is that your device is new like you said, so there are many chances that there is almost no really important personal data stored on your cellphone ... i say that because in my experience when motochopper encountered a problem, the easiest way to make it work is to perform a factory reset from the Android settings menu as STEP 1 !
BEFORE DOING ANYTHING, ensure to backup your personal data on your external micro sdcard if you have one ...
-> STEP 1 : perform a factory reset from the Android settings menu ... when the process is complete and you're back into Android ... go further
-> STEP 2 : follow instructions as described in the first post of this thread BUT do not ever plug your device to a USB hub (even a powered one), plug it when needed to a true USB port directly on your computer !
Also, in your case nCom, as you have both Linux and Windows platforms, prefer Linux for motochopper : i can confirm that the tool works on Ubuntu 13.04 !
Another important thing : i've noticed that when motochopper fails once THEN you have to perform a factory reset from the Android settings menu to have a chance to make it work ... 1 motochopper failure => factory reset ...
The causes of the failure in your case nCom are not clear for me : before trying motochopper another time, please double check that all the required conditions are fullfilled as described in the first post of this mini HowTO + check that the USB connection mode of your device is set to 'Charge only' or 'LG Software' + connect your device to a true USB port when needed (like already said above ... try different ports if it keeps failing)
Let me know if this helped you out !
Have a nice day and happy rooting
Tapatalked from my TF300T
ne0zone75 said:
when motochopper encountered a problem, the easiest way to make it work is to perform a factory reset from the Android settings menu as STEP 1 !
Click to expand...
Click to collapse
Thanks for your reply, just tried factory resetting before rooting and unfortunately it didn't help :/. Still failing on the same step.
I even tried running the commands one by one instead of a batch script - as explained in this thread - and it always seems to fail on:
Mr.Parkinson said:
adb shell /data/local/tmp/pwn
Click to expand...
Click to collapse
With the output being:
Code:
[+] This may take a few minutes.
[-] Failure.
Any further input/help with my case appreciated.
@nCom
It's strange that you're facing such difficulties with this tool and it's also far away the limits of my knowledge... the best i can do for now is to give you the link of the official motochopper support thread, there you'll certainly find a solution to your problem : http://www.droidrzr.com/index.php/topic/15208-root-motochopper-yet-another-android-root-exploit-412/
Also check if there is any official thread for motochopper on XDA... djrbliss is the author of this great tool... as far as i know there is not such a topic.
Good luck
Tapatalked from my LGP875
ne0zone75 said:
@nCom
It's strange that you're facing such difficulties with this tool and it's also far away the limits of my knowledge... the best i can do for now is to give you the link of the official motochopper support thread, there you'll certainly find a solution to your problem :
Also check if there is any official thread for motochopper on XDA... djrbliss is the author of this great tool... as far as i know there is not such a topic.
Good luck
Tapatalked from my LGP875
Click to expand...
Click to collapse
Do you know of any roms that are compatible with this phone? I'd like to get cyanogenmod on it. Perhaps roms from a similar phone??
SubNoizey said:
Do you know of any roms that are compatible with this phone ...
Click to expand...
Click to collapse
At this point i think there is none ! In addition the Optimus F series is partially supported by loki (another program by djrbliss ...) which is one of the only tool to bypass the bootloader of these phones (F5 is not, F3 & F7 are !) in order to flash a custom recovery and a custom ROM on it.
I think we'll have to wait untill somebody has unofficially ported CyanogenMod to the F5 (and to the whole F series ...) because some files in a ROM are device specific : in order to compile a custom ROM you'll have to get a device / kernel source tree and a proprietary tree ... all these are mandatory otherwise your ROM will be useless ... trying another ROM from a similar device is a hazardous job ...
If you successfully manage to get a working custom ROM like CyanogenMod on your cellphone you'll be welcome if you let me know :thumbup:
Have a nice day !
Tapatalked with my TF300T
ne0zone75 said:
At this point i think there is none ! In addition the Optimus F series is partially supported by loki (another program by djrbliss ...) which is one of the only tool to bypass the bootloader of these phones (F5 is not, F3 & F7 are !) in order to flash a custom recovery and a custom ROM on it.
I think we'll have to wait untill somebody has unofficially ported CyanogenMod to the F5 (and to the whole F series ...) because some files in a ROM are device specific : in order to compile a custom ROM you'll have to get a device / kernel source tree and a proprietary tree ... all these are mandatory otherwise your ROM will be useless ... trying another ROM from a similar device is a hazardous job ...
If you successfully manage to get a working custom ROM like CyanogenMod on your cellphone you'll be welcome if you let me know :thumbup:
Have a nice day !
Tapatalked with my TF300T
Click to expand...
Click to collapse
Yeah i've requested support on the cyanogen mod forums
ht tp://forum.cyanogenmod.com/topic/79412-request-lg-optimus-f-series (sorry new user, can't link.
if you want to post/bump. I'm looking into how difficult it is (probably far too difficult for me). I find it odd that the L series has a custom scene but the F series doesn't. Are the F5's only in Australia?
I might run around to a few aussie sites like miui au and what ever else i can find and see if they can help/lead me in the right direction.
@SubNoizey
I agree with you about the Optimus F series custom ROM support ... afaik the F5 is sold worldwide (at least in France for sure) but strangely it does not seem to attract the interest of the DEV community like other devices (there is no dedicated subforum on XDA for the Optimus F lineup for example ...) ; in my opinion it's a shame because the F5 is a good LTE budget cellphone.
Good luck in your quest
Tapatalked with my TF300T
ne0zone75 said:
@SubNoizey
I agree with you about the Optimus F series custom ROM support ... afaik the F5 is sold worldwide (at least in France for sure) but strangely it does not seem to attract the interest of the DEV community like other devices (there is no dedicated subforum on XDA for the Optimus F lineup for example ...) ; in my opinion it's a shame because the F5 is a good LTE budget cellphone.
Good luck in your quest
Tapatalked with my TF300T
Click to expand...
Click to collapse
Yeah, getting custom ROM support would be fantastic for this device. Count me in if you guys intend to start a bounty to generate some interest.
[Guide] How to install TWRP & root Lenovo Vibe B A2016A40 (single & dual SIM version)
Here's how I rooted my phone. This assumes some previous knowledge of using ADB and TWRP. If you need to, I strongly recommend SIM-unlocking your phone BEFORE you do this - I used this ebay service which cost £1.99 and I received the codes 36 hours later.
Please note that although this worked on my phone, I accept no responsibility if you brick your phone doing this
1. Update your ROM to the latest version, open Settings -> About and tap on Build Number seven times to enable Developer options then check USB debugging & OEM unlocking of the bootloader.
2. Connect your phone to your PC, start ADB and type adb devices - this will bring up a prompt on your phone that you need to respond to. Type adb reboot-bootloader
3. Once in bootloader mode, type fastboot oem unlock. Hit the Volume Up key to confirm.
4. Disconnect the phone from the PC and pull the battery for at least 3 seconds.
5. Download the SuperSU flashable zip https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip and copy it to a microSD card and insert it in the phone.
6. Download TWRP recovery to your PC http://www.mediafire.com/file/4hb66m26kfkw9qt/twrp.img and copy it to the same folder as your ADB (I use Minimal ADB & Fastboot https://androidmtk.com/download-minimal-adb-and-fastboot-tool ).
7. Start the phone in bootloader mode by holding the Power and Volume Up buttons together until you see white text on the screen. Use the Volume Up button to navigate to Fastboot then select it by pressing Volume Down. Connect the phone to your PC.
8. Type fastboot flash recovery twrp.img
9. Disconnect the phone from the PC and pull the battery for at least 3 seconds.
10. Start the phone in Recovery mode by holding the Power and Volume Up buttons together until you see white text on the screen. Use the Volume Up button to navigate to Recovery then select it by pressing Volume Down.
11. You should then see TWRP starting. Tick the box to agree then swipe the blue button to the right.
12. Tap on Wipe then Format Data. Do not miss out this step or TWRP won't be able to mount the /data partition.
13. Tap the Back button then Factory Reset and swipe the blue button to start.
14. Tap the back button then Install then Select Storage -> microsd card then your SuperSU file then swipe the blue button to the right to flash it.
15. Tap on Reboot System and your phone should boot to your newly rooted OS! Don't panic if the first boot takes 5 or 10 minutes. If it gets stuck, pull the battery & try again.
16. Make sure you disable System Updates as they will no longer work with the non-stock recovery. Hopefully it shouldn't be too long until there's an AOSP or LineageOS ROM for this phone
Thank you
This worked like a charm - although I was hesitant knowing there would be no way back, would it?
It *should* be possible to extract the stock recovery from a recent stock firmware - I just haven't found any (my phone came with S219, and was upgraded to S235 prior to rooting). That in theory would open the path to a stock upgrade, if one would like to have it.
Re LineageOS: There's an unofficial build for a codename 'al732row' but I'm in doubt this would match a dual-sim A2016a40. I'll wait for another update or two (three releases within 72 hours, then 2 weeks silence?).
For now I won't complain: this was a bargain even without LinOS - those dirt cheap devices often get stuck with Lollipop.
Another edit: The Nougat LineageOS ROM by CarlosArriagaCM (http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/) seems to be limited to the LATAM version of the B (aka A2016b30). For A2016a40 (EMEA version) no cigar
steve8x8 said:
This worked like a charm - although I was hesitant knowing there would be no way back, would it?
It *should* be possible to extract the stock recovery from a recent stock firmware - I just haven't found any (my phone came with S219, and was upgraded to S235 prior to rooting). That in theory would open the path to a stock upgrade, if one would like to have it.
Re LineageOS: There's an unofficial build for a codename 'al732row' but I'm in doubt this would match a dual-sim A2016a40. I'll wait for another update or two (three releases within 72 hours, then 2 weeks silence?).
For now I won't complain: this was a bargain even without LinOS - those dirt cheap devices often get stuck with Lollipop.
Another edit: The Nougat LineageOS ROM by CarlosArriagaCM (http://www.cyanogenmods.org/forums/topic/lineage-os-14-1-vibe-b-al732row-nougat-7-1-rom/) seems to be limited to the LATAM version of the B (aka A2016b30). For A2016a40 (EMEA version) no cigar
Click to expand...
Click to collapse
You can flash the dual-SIM stock ROM using SP Flash Tools so you're never going to end up with a bricked device
Thank you much. I rooted, installed twrp and i updated TWRP to 3.1.0-0
https://forum.xda-developers.com/android/development/recovery-3-1-0-0-lenovo-vibe-b-t3603304
Any custom rom available for Lenovo Vibe B (A2016A40 version)?
Best Regards,
Vlad
@dwl99 ?
Vlad Paul said:
Thank you much. I rooted, installed twrp and i updated TWRP to 3.1.0-0
https://forum.xda-developers.com/android/development/recovery-3-1-0-0-lenovo-vibe-b-t3603304
Any custom rom available for Lenovo Vibe B (A2016A40 version)?
Best Regards,
Vlad
@dwl99 ?
Click to expand...
Click to collapse
Not that I can find. There is one for the a2016b30 but the camera doesn't work.
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
Hi! Do you have a2016a40 model? Wich TWRP you have installed, 3. 1.0-0 ? Not working latest rom build?
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
@Carlos Arriaga replied me will release a new fixed build soon. I hope will working on our model of phone a2016a40.
Look his reply here:
https://forum.xda-developers.com/showthread.php?p=72692660
steve8x8 said:
There's a new (20170614) release. Still there's "E3004: This package is for device: al732row,A2016b30" in the updater-script. Should we invite Carlos to Europe?
(And there should be a ROM thread for this device. Last time I checked there was none.)
Click to expand...
Click to collapse
New build release on 19.06. 2017. Working on model a2016a40?
Short answer: No, no change between 0614 and 0619.
Long answer: You may check this yourself: Open the ZIP file in your favourite archiver tool, and extract the file META-INF/com/google/android/updater-script, then inspect the first line (assert()) for A2016a40.
Disclaimer: Even if the new ROM would be accepted by an A2016a40 I couldn't test it right away (no access to the device anymore / yet again).
steve8x8 said:
Short answer: No, no change between 0614 and 0619.
Long answer: You may check this yourself: Open the ZIP file in your favourite archiver tool, and extract the file META-INF/com/google/android/updater-script, then inspect the first line (assert()) for A2016a40.
Disclaimer: Even if the new ROM would be accepted by an A2016a40 I couldn't test it right away (no access to the device anymore / yet again).
Click to expand...
Click to collapse
Thank you for reply @steve8x8 . No luck for a2016a40 users
assert(getprop("ro.product.device") == "al732row" || getprop("ro.build.product") == "al732row" || getprop("ro.product.device") == "A2016b30" || getprop("ro.build.product") == "A2016b30" || abort("E3004: This package is for device: al732row,A2016b30; this device is " + getprop("ro.product.device")
Click to expand...
Click to collapse
I hope to help us @Carlos Arriaga
I'm somewhat afraid there'll be only one way to get @CarlosArriaga to support the a40 variant: purchase one (70€), send it to him (almost same amount). Any volunteers?
steve8x8 said:
I'm somewhat afraid there'll be only one way to get @CarlosArriaga to support the a40 variant: purchase one (70€), send it to him (almost same amount). Any volunteers?
Click to expand...
Click to collapse
Sorry, im homeless, i don't have 1 dolar to eat something.
I found a comparison of the two sub-models: http://www.phonemore.com/compare/phones/lenovo-vibe-b-a2016b30-vs-lenovo-b-a2016b40/4710928 - most prominent difference is 3G and LTE bands, but I'd presume this would be handled by the modem part of the firmware (which isn't part of LineageOS).
If I could get my hands on FCC documents (although I'm in doubt that a40 and b30 would have separate ones) I'd have a closer look.
Any pointers to stock firmware are welcome (but if that comes in MTK format I'm lost I'm afraid).
If I were @CarlosArriaga I'd check too for the model of phone I know, even with a disclaimer in 96pt.
But: nobody stops you from modifying the updater script to include the other model (and as the OP said, with MTK flash tools recovery from a bad flash would be easy - if you got the stock firmware, that is).
Due to lack of the actual hardware (for yet a few months) I'm limited to speculating and using a magnifying glass on the code itself - if time permits.
Does the ZTE Blade A510 look very similar to the Vibe B? Almost identical characteristics, same CPU type? There are rumours about LineageOS support planned for the Blade.
Answering myself: an A510 scatter file I came across shows more partitions than the Vibe has, so this may be close but not close enough.
ZTE has a device called A2016 though. Coincidence?
steve8x8 said:
Does the ZTE Blade A510 look very similar to the Vibe B? Almost identical characteristics, same CPU type? There are rumours about LineageOS support planned for the Blade.
Answering myself: an A510 scatter file I came across shows more partitions than the Vibe has, so this may be close but not close enough.
ZTE has a device called A2016 though. Coincidence?
Click to expand...
Click to collapse
Nothing new for our model a40? No chance to develop @Carlos Arriaga a LineageOS build for this model? The developer is very quiet.
Hello,
Sorry my english I use a translator.
TWRP & root Lenovo Vibe B A2016A40, instructions very good.
But there is no unofficial Android 7 for Lenovo Vibe B A2016A40?
For Lenovo Vibe B A2016A30 gives Android 7. I know that.
Unfortunately, my smartphone Lenovo Vibe B A2016A40 does not.
Twrp error reports installation. Error 7.
TWRP (3.1.0-0 at least, I didn't upgrade to 3.1.1) installed properly on the A2016a40. The check for the model in the updater script is what gives you an error (is there a translation table to lookup the value of 7 you got?).
As had been said before, it's possible to change the updater script to skip the check and repackage the zip, but nobody knows yet what will happen to your phone, and whether it can be restored using SP Flash Tool. We all are keen to learn about this...
(reply removed)
About
Hi there,
I created this guide not so much as a substitute for the other guides or because this would be the best way to do it.
When I looked into rooting my new Axon 7 (international) I studied all the other guides first, but then did it very differently, mainly
because
- I am on Win 7 32-bit and some of the tools used in the other guides don't work for that
- since the other guides were created the Axon7Toolkit came along - that simplified a lot of steps.
The guide is actually very similar to this one for the 2017U:
https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128
Only now with the toolkit it pretty much works for the 2017G as well without the need for tenfar's TWRP (see comments). In case I left out anything, this guide will be of help, too.
So this guide is for you if
- You want to root or flash a custom rom and don't mind unlocking the bootloader OR
- You are on Win32 and cannot use the axon7tool command line tool OR
- You want to use the Axon 7 Toolkit for the job to keep things simple
Please read all the notes below before attempting anything...
Disclaimer
- This worked well for me - no claims it does for anyone else. For the record: I was on Stock 6.0 MM B08 A2017G, no fingerprint/lock etc and went straight to RR.
- Use at your own risk, if you are unsure what you are doing stay stock - I'm not responsible for bricked devices, dead SD cards, Donald Trump, or you getting fired because the alarm app failed...
Regarding Drivers
- Qualcomm ones for MiFlash (link below)
- QUSB_BULK if going with eg the axon7tool commandline version (edl mode)
- You can use the Toolkit to install (some of) the needed drivers
- ZTE drivers - phone is set up to install them upon connect to the PC. Don't.
- Uninstall incorrect drivers, just installing the correct ones won't necessarily do the trick.
MiFlash
- right click & 'run as admin' (flashing didn't work for me without this)
- Correct driver: Qualcomm HS-USB QDLoader 9008 when in edl (check with device manager open)
Boot modes
- power phone down and boot into
- EDL by holding Volume UP/DOWN & POWER simultaneously
- recovery/TWRP (once installed) by holding Volume UP & POWER simultaneously
- fastboot: Not enabled in A2017G Stock
Windows
- 32-bit: MiFlash needed, commandline axon7tool not working
- The toolkit seems to run on Mac/Linux using a Windows emulator/virtual machine (not tested, Wine helps I guess)
TWRP
- versions: Signed tenfar TWRP 3.0.2 that is used in a lot of other guides is buggy and can do a lot of harm - not needed if you unlock
the bootloader first. You can (and should) use the latest official TWRP version.
- dm-verity: https://twrp.me/devices/zteaxon7.html
- USB OTG: Axon 7 supports this, so does TWRP - no need for SD cards. Simply use a thumbdrive with a OTG cable (with included Adapter if needed), boot into TWRP (thumbdrive needs to be connected beforehand) and click 'Mount' in TWRP, then select USB storage
Bootloader
- Afaik DO NOT lock again with custom rom installed or rooted (brick)
Root/Unlock
- Can create problems with Android Pay, playstore etc - see https://www.xda-developers.com/tag/safetynet/
- Root disabled by default in Lineage, needs flashing Magisk or SU - see other guides
- Some features root provides on Android 6.0 MM won't work in Nougat (so far anyway, eg xposed)
Links
- Axon7Toolkit: https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
- TWRP: https://twrp.me/devices/zteaxon7.html
- Zadig (if needed): http://zadig.akeo.ie/
- Qualcomm driver: https://build.nethunter.com/misc/axon7/Qualcomm_QUSB_BULK_Drivers.zip (link from https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514)
- Lineage Os thread: https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-14-1-zte-axon-7-t3545679
- Modem & bootloader from Lineage Os thread: https://www.androidfilehost.com/?w=files&flid=148464
- OpenGApps: http://opengapps.org/?arch=arm64&api=7.1 (arm64 version for OS version to flash, e.g. 7.1 Nougat)
Thanks
bkores (for the tool), dnlilas (help in the forum), DrakenFX, Unjustified Dev, Controllerboy & all the guide/rom creators etc in this forum. (And the poor souls who came first and discovered all the ways not to do it, preventing my fall)
1) Prep
- Note down IMEI(s) from your settings/about phone/status/... just in case
- Unlock developer options (Phone settings > "About Phone" > Click "Build Number" 7 times...)
- Check "Allow OEM unlock" and "USB Debugging" there
- Connect your Axon 7 to your PC with the original USB cable - do not disconnect with MiFlash/Toolkit running.
- Open device manager to check your drivers (will show up differently depending on the boot mode)
- Run Axon7Toolkit
- Select Option 1 - Install/Test Drivers
2) Unlock
- This will RESET your device, did you save your data? (using Toolkit etc)
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
- The unlock files the Axon7Toolkit offers are in a folder 'A2017U_FASTBOOT_UNLOCK_EDL' - works for A2017G
(- Axon7Toolkit preview version offers different folder content to flash - have not checked that)
- One can restart MiFlash (e.g. to 'run as Admin') anytime and try again, but after the flash was succesful, do not disconnect the phone but
- Finish off with the Toolkit 'press a key to continue' (or one will have only fastboot enabled)
- A message will appear on the phone: Confirm that you want to unlock the bootloader (using volume & power buttons to navigate)
- Done. From now on you will get an annoying message on booting the phone about your device being unlocked. Just ignore and wait for a re-boot...
3) TWRP
- Unlock developer options - AGAIN etc as device was reset. And - again - enable debugging...
- In the toolkit (main screen) go to '11 Advanced Options', select <Flash boot/bootloader/modem/recovery<choose recovery partition
- In 'Open' dialog select C:\Axon7Development\Axon7Toolkit\twrp\twrp-3.1.0-ailsa_ii.img (or newer version)
- Flash as 'recovery'
- Reboot, check system boots up fine
4) Flash Custom Rom etc.
- Generally: Follow instructions provided with the custom rom you are going to flash (as they might differ)
- Boot into recovery/TWRP (Volume UP + Power after shutdown)
- No need to swipe to 'Allow system modification' - this can actually brick things...see https://forum.xda-developers.com/axon-7/help/a2017u-stuck-zte-screen-boot-factory-t3584062
- Mount/Select storage (for OTG USB)
- Backup boot, recovery, data(if needed), HLOS, System image or System (image was recommended but that did not work in my case, so I backed up system)
- Wipe/Format
- ***If you like to avoid your data partition to be encrypted, follow that thread: ( format your data partition to ext4 instead of f2fs (wipe -> advanced)????)
- Install Bootloader & then modem (or Nougat won't install if coming from MM) - A2017X_B15_Universal_Bootloader.zip & A2017G_N_Modem.zip
- Rom & Magisk/SuperSU
- GAPPS (version)
- Re-boot: Unlocked message, long first time boot - After RR, my phone show up as 2017U... well, who cares...
Any comments to correct errors in this guide or fill out any blanks are highly appreciated...
I dunno why now one has thanked this yet, it is a well written guide imo and useful for those not yet unlocked.
THANKS SOO MUCH FOR THIS!! The timing could not have been any better. I literally just bought this phone from a guy on craigslist for $270 (Couldn't pass that up coming from an LG G4) less than a hour ago. Quick question. It's a 2017u with build B25. Will the toolkit work with it. I don't see an option for this build
Hi Senny,
thanks a lot - I hope the guide is helpful, as mentioned it worked for me. Hopefully I included at least most of the pitfalls one could encounter...
Hi raphi809,
The toolkit should work fine with the 2017U (it should detect your version).
To be sure, also have a look at the toolkit thread (https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108) and the thread linked above (https://forum.xda-developers.com/axon-7/how-to/complete-guide-to-unlocking-installing-t3561128), as it is more specific for the 2017U.
The main thing I am not 100% sure with the 2017U is (as I am on a 2017G and started from Android 6.0 MM), if you have to downgrade from Nougat/certain versions before unlocking etc.
If someone could shed some light on this, that would be great!
Whoooo? said:
About
- Select option 6-unlock on toolkit main screen -
- MiFlash launches and one has to select the folder with the files to flash, following the instructions of the toolkit
- Check Device Manager lists your Axon 7 as Qualcomm HS-USB QDLoader 9008, if not uninstall wrong drivers and install Qualcomm ones
Click to expand...
Click to collapse
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Volumetrik said:
Hi Whoooo?, first thank your for your time to write this guide.
I tested your procedure and I remain stuck at the same point than the others guides. After Axon7Tool / 6-Bootloader Unlock, MiFlash.exe doesn't launch because I am not under 64bits system. So, after a successful Xiao MiFlash package, I launch it manually (admin rights): my device (in edl mode) is not seen, whatever the driver used (Qualcomm, QUSB...).
If I understand correctly the right procedure to install LineageOS 14.1 & TWRP, Axon 7 must be unlocked in its bootloader by flashing A2017U_FASTBOOT_UNLOCK_EDL?
Click to expand...
Click to collapse
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Whoooo? said:
Hi Volumetrik,
For me the MiFlash version that came with the Toolkit originally didn't work either (as Win32, too).
Instead I used the installer that came with the beta version of the toolkit (v1.2 - there was an installer in the MiFlash folder).
The installer created two applications (MiPhone and MiFlash or similar) - one of them worked for me if run as admin.
Also make sure the right driver is actually used by windows (by checking what is used in the device manager when the phone is connected in edl mode) - Windows is sometimes funny if more than one driver is installed...
Hope that helps
Click to expand...
Click to collapse
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi there,
Obviously I have not tried this myself, so I only can refer to these two posts from the Toolkit thread:
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71673370#post71673370
https://forum.xda-developers.com/ax...on7toolkit-t3573108/post71861250#post71861250
...stating that 'Bootloader mode is disabled in G variant with Nougat update' and one has to either
- revert to MM or
- flash a different Unlock package with MiFlash (linked in the second post)
(There is also a note in the instructions saying that the toolkit's Bootloader unlock with MiFlashdoes not work on A2017U B25)
marcus.linkenbach said:
It's now a few days ago since this guide has been published and I wonder why nobody seems to share any experiences. Has nobody tried to follow these steps so far? I am interested whether it is possible to start from Nougat or is MM recommended?
Click to expand...
Click to collapse
Hi Marcus,
I tried to find some time to reply and explain how I used this guide and two others to get my device unlocked, twrp'ed and LineageOS. It's running like a charm.
I started with a A2017G device basis with MM B03. My device was updated to the latest official update available via MyFavor network. I didn't try to update OTA.
I Used Axon7ToolKit v1.1.1 + Update_Install.bat / Qualcomm Drivers / A2017U_Bootloader_EDL. I worked under windows x64, because I experienced too many troubles to get Axon7toolkit working properly under 32bits. The only one differences I experienced and not written in the threads:
- I saw a FTM mode (Factory Test Mode) displayed in a white square centered on the device screen after unlocking bootloader. In my memory, it disappeared after TWRP flash.
- I got a problem with Flashlight, didn't work, associated with a problem to call (sms working). I flashed the modem firmware once again, it solved the problem after reboot.
- At the end, LineageOS installed, LineageOS updater strangely saw the same update version installed on the device. The only difference was the"signed" at the end of the update name I launched the update and installed it succesfully, without issue. No more update after that (until a new one of course)
Hope this will help someones
Volumetrik said:
Hi Whoooo?
Thank you for swift reply. In fact, I decided to work under x64 environment, so I made a fresh install. Then, I combined your guide with the others in this part in the forum.
I must say I thank you so much, for your work. For a N00b, it's difficult to sort the main steps to complete the process... even if I already did this on different devices before.
I'll explain in the LineageOS thread how I completed this conversion from a full stock A2017G B03 (MM). It's slightly similar with yours.
Once again, Thank you. :good:
Click to expand...
Click to collapse
Hi, when are you planning to release your complete guide? This would really help me.
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
still_living said:
Bootloader is unlocked. Drivers are okay, toolkit recognises the phone connected. But every time I try to flash twrp or root it says 'FAIL'.
Can someone please help?
Click to expand...
Click to collapse
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Apocalypse12345 said:
I am trying unlocking the bootloader on B11
When I try flashing bootloader unlock in MiFlash it says:
Lenght cannot be less than zero.
Parameter name: lenght
Tried restarting MiFlash, installing it again and restarting PC. Does anyone know what am I doing wrong?
EDIT: Managed to unlock using Controllerboy guide that didn't work for me at first (why I used toolkit). But I am still curious why that error in MiFlash happened...
Click to expand...
Click to collapse
Hi there,
I think (memory blanks setting in) that's the error I got when MiFlash was not running as admin.
Whoooo? said:
Hi,
Sorry for the late reply -
just to clarify, are you stuck after point 2 of the guide (as root is the last step of the guide/only mentioned there)?
Personally I did root not via the toolkit but via TWRP when I flashed the custom rom (as described eg in the lineage os thread).
Problems with flashing TWRP I could think of:
- bootloader unlock not successful
- debugging/developer option not enabled
- TWRP not flashed as recovery
At what point does the toolkit report fail (maybe your problem is also worth posting in the toolkit thread)?
Alternatively TWRP could also be flashed with MiFlash (did NOT try myself - but there should be guides around somewhere).
Click to expand...
Click to collapse
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
still_living said:
Hello. Yes I have posted it there and the questions and answers section to which bkores (the one who made the axon7toolkit) replied and asked me to do a command in which I followed and replied to him with the results and he didn't reply after that. Also, bootloader is unlocked. This is what happens:
Checking ADB/fastboot connectivity...
ADB device connected!
Rebooting to bootloader...
Checking fastboot connectivity...
Fastboot device connected...
Flashing twrp...
And within a second an error message pops up with a red cross 'Flash failed!'
Sorry, I forgot to say that I couldn't follow your guide entirely because I think we are on different versions of the toolkit. I am on the latest version 1.2.0 (stable), so I don't have the option 11 to go to advance settings to install the twrp. I have just the option 6 to install directly(you can see in the thumbnail of axon7toolkit post).
Click to expand...
Click to collapse
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
Only stock recovery for me. No twrp unfortunately. Really want to change from miflavour
djona12 said:
Thank you so much for this guide ! Had the phone back in october and i unlocked it using tenfar tool but since it was stolen in march, i bought a new one last week and this is so much simpler and safer !
Did you try booting to recovery after the failed flash attempt ? I had the same issue with the fail message (toolkit 1.2.0) but twrp was running fine.
Click to expand...
Click to collapse
HURRAY! ! !
Well no it didn't work until today I tried the option to restore from bricked device to b10. Out took me to miflash and asked me to unlock bootloader? Dunno why, it's already unlocked, anyway , after that was successful I went back to the option page of the toolkit and selected 'install twrp', and this time it flashed! It didn't stop on the 'failed to flash twrp' message but still gave me a 'flash to boot into twrp' then I followed your advise to go to twrp directly from there and it had installed. I'm so happy thanks loads dude. :laugh:
Worked like a charm! Thanks for posting the guide
Edit: Went from locked Nougat to Unlocked Lineage.
Whole process took me about 2 hours, but if you are better at following the steps than me you'll probably be able to do it in 1 hour.
I have made some Boot Logos for Motorola phones and would like to share them with the community.
Although the project was initially for Moto G5 Plus (Potter), I have made all versions with the text motorola on the boot images.
Features :
N/A hidden
Redesigned bootloader menu
Some other minor changes in boot logo images
These Boot Logos can also be flashed to other Motorola Devices with 1080X1920 screen resolution like:
Moto G4
Moto G4 Plus
Moto G5
Moto G5s
Moto G5s Plus
Moto X4
Moto Z2 Play
Other Motorola phone users may use the version of the boot logo with motorola written on the image instead of moto g5 plus.
Use VX.0_BL_9-3_by_4 Zip for Moto G5 Plus.
Use VX.1_BL_9-3_by_4 Zip for other Motorola devices.
The file names with DT at the end stand for Boot Logos suited for Dark Theme.
All Boot Logos have been posted on SOURCEFORGE and more would be added in the coming future. The designs have been separated into two folders and further organized inside each folder by version numbers starting with V1. All the zips are functionally the same and you can flash whichever version you like. The only difference is in the text shown on the Boot Logo image. Head down for viewing previews and downloading the boot logos.
How to Install (via Custom Recovery)
Download the desired ZIP file to your phone
Boot to your Custom Recovery
Go to Install
Go to the location where you have saved the ZIP file
Install the ZIP file and reboot
How to Install (via Fastboot)
Download the desired ZIP file to your PC
Extract logo.bin from the zip file into your adb folder on your PC
Boot to Fastboot
Enter these commands in adb: fastboot flash logo logo.bin
Reboot
Boot Logo Previews
Boot Logo Downloads
If you are unable to download from SOURCEFORGE on your phone, request desktop site from your browser menu to enable download.
Credits: Thanks to the versatile tool made by CaitSith2 for enabling users to customize their phones for all these years.
Disclaimer: Motorola Logo and Batwing Logo is owned by Motorola Inc. Some of the artworks are not entirely my own creation.
Nice work boi
marshmello_61 said:
Nice work boi
Click to expand...
Click to collapse
Thank you bro!
It may be me, but I've been searching your files for the correct one with no luck. Been wanting your dark version for the Moto G5s Plus, but can only find moto g5 plus... which are not compatible. Potter will not install on a Sanders phone. This is the Sanders forum.
Can you please link me to the dark version boot logo for Moto G5s Plus (Sanders)? Thank you so much
Edit: 9-3_by_4_V3.1DT.zip is not available on Sourceforge desktop site.
JJ5150 said:
It may be me, but I've been searching your files for the correct one with no luck. Been wanting your dark version for the Moto G5s Plus, but can only find moto g5 plus... which are not compatible. Potter will not install on a Sanders phone. This is the Sanders forum.
Can you please link me to the dark version boot logo for Moto G5s Plus (Sanders)? Thank you so much
Edit: 9-3_by_4_V3.1DT.zip is not available on Sourceforge desktop site.
Click to expand...
Click to collapse
No, it is not your fault. I have revised the entire catalogue and changed the original post too. My naming scheme had become too convoluted. Also some zips were not flashing so I pulled all files and uploaded fresh. The file you are searching is this: https://sourceforge.net/projects/pr...ola Series/V3/V3.1DT_BL_9-3_by_4.zip/download
Functionally boot logo for moto G5 plus is same as that of Sanders. But since non Potter users won't like moto G5 plus written on boot screen, I made one with Motorola for everybody to use.
The ones you need are in Motorola Series folder on sourceforge. You can visit via the links on original post.
The imgur post has been updated to reflect the correct names. Thanks for pointing it out.
Announcement
New Boot Logo Added : V5
Preview (Light Theme): https://imgur.com/VXyH5c3
Preview (Dark Theme): https://imgur.com/0BXYqfF
Download from SOURCEFORGE: https://sourceforge.net/projects/project-9-three-by-four/files/Boot Logo/Motorola Series/V5/
Hello dear gurus.
Purchased a Motorola (Lenovo) moto G6 smartphone on the Anroid 8.0 Oreo platform.
Performed OTA security updates.After that, it was suggested to upgrade to Anrdroid 9.0 Pie.Updated.
Next, I installed a custom recovery (TeamWin Recovery Project (TWRP)) on a new loader,and created a backup system for this recovery.
Next, I tried to fill in a new custom (Amateur) firmware (ViperOS), but TWRP refused to install this firmware.
So I tried about 10 different firmware versions,including official ones that were compatible with my Moto G6 device.
In the end, through trial and error, I turned a brand-new phone into a Hard Brick.
Currently, neither the recovery, nor the system,nor even the PBL,aboot, or SBL bootloader chain is running.
The only way the phone is detected (after installing specific drivers for my device and processor) in the system is Qualcomm HS-USB Qload 9008. That is, Emergency Download mode (EDL mode).
To convert the device to SoftBrick (9006) - a light brick.I need to restore the entire loader chain, starting with the SBL of the secondary loader.
There is a special BlankFlash_PPS29.26 utility for my device (see Attachment) that runs automatically when Blank_Flash is started.bat, re-marks MBR partitions, creates a partition table, and restores the entire chain of loaders.
But there is one significant "BUT", this utility completely refuses to ReWire the chain of device loaders, giving an I/o error in the logs (see Attachment).
After talking with smart people from the forward, I realized that for a successful firmware of my device, the OTA security update is not suitable,what is in the utility later, and what is newer and more secure on the device and the singleimage configuration file.the bin located in this utility is not suitable.
If there are people who can write the correct script for .bash for my firmware and security version and embed it all directly into singleimage.bin, then please respond.
Data for unbrick 1925-5 RU_ru.
This is archive for unbrick XT1925-5 on version Android 8.0 Oreo.
Someone, help me with the development blankflash on version Android 9.0 Pie.
reply
ZulC_Silence said:
This is archive for unbrick XT1925-5 on version Android 8.0 Oreo.
Someone, help me with the development blankflash on version Android 9.0 Pie.
Click to expand...
Click to collapse
rescue_and_smart_assistant_v5.2.0.10_signed_setup and nothing to add .
mickelek said:
rescue_and_smart_assistant_v5.2.0.10_signed_setup and nothing to add .
Click to expand...
Click to collapse
Please tell us in more detail how can I restore my smartphone via LMSA if I have rubbed all the bootloaders except the primary one (PBL) and in this utility it is absolutely not detected?