hi all,
i'm somewhat nervously attempting to root my moto edge 20 fusion, and i have a few questions please.
my most recent experience with rooting a phone was an older moto phone about 5 years ago, which i managed with the help of these forums (as a lurker).
anyway, my edge 20 fusion bootloader is already unlocked. this is confirmed with 'fastboot getvar all' showing 'securestate: flashing_unlocked'.
the phone is booting fine and running fine with the stock rom. android 11, security patch 2022-01-01, software channel retapac, build number RRKS31.Q3-19-97-3.
after reading as much as i could find in the forums here, i've made this pastiche of notes below and added my questions to it:
step 1: obtain the boot.img
- i have obtained a boot.img (size 41,943,040 bytes, last modified 2021-12-30) from the unzipped 'stockrom.net_KYOTO_RETAIL_RRKS31.Q3-19-97-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml' (2022-01-21 version downloaded from https://androidfilehost.com/?fid=17825722713688274049) is that the right file i need?
- does the region of the retail rom above matter for this rooting process? i'm not sure how to determine the region of that rom from that website or from the files themselves. i'm in australia using a locally bought variant of edge 20 fusion, if it matters.
i also found this comment: 'find boot.img under "C:\ProgramData\LMSA\Download\RomFiles\" or "C:\ProgramData\RSA\Download\RomFiles\"'
- i'm guessing i don't need to worry about that since i already have a boot.img file from the previous step? although i'm also wondering if this means i should have the LMSA software tool installed already, or if it means i will need to use it somewhere along the rooting process?
step 2: install magisk
- do i just follow this guide? https://topjohnwu.github.io/Magisk/install.html
- which version of magisk should i install? i'd heard that some of the newer versions don't have the hide function anymore, is there a recommended version number to use in order to best pass safetynet?
- should i install magisk on the phone itself or should i add an sd card first and install it on that?
- i'm guessing the magisk home screen once installed should read "ramdisk: yes"?
- looking inside the stock rom zip where i found the boot.img i can also see vbmeta.img, although it's only 4kb in size. does that mean i should also patch the vbmeta partition as per the magisk install guide?
step 3: patch boot.img with magisk on the edge 20 fusion
- should i check the "patch vbmeta in boot image" or not?
step 4: copy the 'magisk_patched_xxxxxx.img' to the pc via adb
- do i do this while still loaded in the android OS? or do i reboot to fastboot to do this?
- should i backup anything at this point to help with rescue / restoring later on if something goes wrong? i remember from rooting an old moto phone that i needed to back up the 'persist' folder as it would be very hard to recover from a mistake without it.
- will the next step cause any data loss from formatting, similar to how unlocking the bootloader does?
step 5: flash to boot_a and boot_b in fastboot
'fastboot flash boot_a magisk_patched_xxxxxx.img'
'fastboot flash boot_b magisk_patched_xxxxxx.img'
'fastboot reboot'
- is it the exact same file that gets flashed to both boot_a and boot_b, without any changes at all? just like a mirrored backup?
and then it should all be done, right? after that it's only setting up magisk from within android OS to be hidden, and enable zygisk, and check safetynet?
sorry for all the questions, i know most of these answers will probably seem obvious to many others here but i just want to be on the safe side. maybe it will help some others too who like me aren't as experienced! with my last phone 5 years ago i didn't do the magisk setup correctly, and google pay would not work. hoping to learn from my mistakes.
p.s. the above info all mostly came from these threads:
Great Device for the price (Root Acheived too)
Hey All, had this device for a week now - and I am quite impressed. I was finally able to allow OEM Unlocking in Developer settings after 3 long days, during which; I requested my unlock code found my firmware to download online, from where I...
forum.xda-developers.com
Root Possibilities? - What has been tried and tested...
Hi All. Yesterday I bought this thing and as with everything, I immediately attempted to begin rooting the damn thing. Update: 6th of November 2021 I re-enabled Developer Options and OEM Unlocking became selectable. Don't know how. NOTE #1...
forum.xda-developers.com
and @sd_shadow 's thread here: https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
trevtdogg said:
hi all,
i'm somewhat nervously attempting to root my moto edge 20 fusion, and i have a few questions please.
my most recent experience with rooting a phone was an older moto phone about 5 years ago, which i managed with the help of these forums (as a lurker).
anyway, my edge 20 fusion bootloader is already unlocked. this is confirmed with 'fastboot getvar all' showing 'securestate: flashing_unlocked'.
the phone is booting fine and running fine with the stock rom. android 11, security patch 2022-01-01, software channel retapac, build number RRKS31.Q3-19-97-3.
after reading as much as i could find in the forums here, i've made this pastiche of notes below and added my questions to it:
step 1: obtain the boot.img
- i have obtained a boot.img (size 41,943,040 bytes, last modified 2021-12-30) from the unzipped 'stockrom.net_KYOTO_RETAIL_RRKS31.Q3-19-97-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml' (2022-01-21 version downloaded from https://androidfilehost.com/?fid=17825722713688274049) is that the right file i need?
- does the region of the retail rom above matter for this rooting process? i'm not sure how to determine the region of that rom from that website or from the files themselves. i'm in australia using a locally bought variant of edge 20 fusion, if it matters.
Click to expand...
Click to collapse
The boot.img needs to be the exact same that's currently on the device.
Same Device Model #, Codename, and Software Channel.
The safest way to do this is to Use LMSA's flash rescue option
Flash the firmware with LMSA, then find the boot.img and patch it with Magisk.
trevtdogg said:
i also found this comment: 'find boot.img under "C:\ProgramData\LMSA\Download\RomFiles\" or "C:\ProgramData\RSA\Download\RomFiles\"'
- i'm guessing i don't need to worry about that since i already have a boot.img file from the previous step? although i'm also wondering if this means i should have the LMSA software tool installed already, or if it means i will need to use it somewhere along the rooting process?
step 2: install magisk
- do i just follow this guide? https://topjohnwu.github.io/Magisk/install.html
- which version of magisk should i install? i'd heard that some of the newer versions don't have the hide function anymore, is there a recommended version number to use in order to best pass safetynet?
Click to expand...
Click to collapse
There are other Hide Mods for Magisk, just use the current version of the app.
trevtdogg said:
- should i install magisk on the phone itself or should i add an sd card first and install it on that?
- i'm guessing the magisk home screen once installed should read "ramdisk: yes"?
- looking inside the stock rom zip where i found the boot.img i can also see vbmeta.img, although it's only 4kb in size. does that mean i should also patch the vbmeta partition as per the magisk install guide?
step 3: patch boot.img with magisk on the edge 20 fusion
- should i check the "patch vbmeta in boot image" or not?
step 4: copy the 'magisk_patched_xxxxxx.img' to the pc via adb
- do i do this while still loaded in the android OS? or do i reboot to fastboot to do this?
Click to expand...
Click to collapse
The patched boot.img will just on the device like other user files, just make a note of the name and location.
Connect the device to the PC and look for it with file explorer.
trevtdogg said:
- should i backup anything at this point to help with rescue / restoring later on if something goes wrong? i remember from rooting an old moto phone that i needed to back up the 'persist' folder as it would be very hard to recover from a mistake without it.
- will the next step cause any data loss from formatting, similar to how unlocking the bootloader does?
step 5: flash to boot_a and boot_b in fastboot
'fastboot flash boot_a magisk_patched_xxxxxx.img'
'fastboot flash boot_b magisk_patched_xxxxxx.img'
'fastboot reboot'
- is it the exact same file that gets flashed to both boot_a and boot_b, without any changes at all? just like a mirrored backup?
Click to expand...
Click to collapse
Yes
trevtdogg said:
and then it should all be done, right? after that it's only setting up magisk from within android OS to be hidden, and enable zygisk, and check safetynet?
sorry for all the questions, i know most of these answers will probably seem obvious to many others here but i just want to be on the safe side. maybe it will help some others too who like me aren't as experienced! with my last phone 5 years ago i didn't do the magisk setup correctly, and google pay would not work. hoping to learn from my mistakes.
p.s. the above info all mostly came from these threads:
Great Device for the price (Root Acheived too)
Hey All, had this device for a week now - and I am quite impressed. I was finally able to allow OEM Unlocking in Developer settings after 3 long days, during which; I requested my unlock code found my firmware to download online, from where I...
forum.xda-developers.com
Root Possibilities? - What has been tried and tested...
Hi All. Yesterday I bought this thing and as with everything, I immediately attempted to begin rooting the damn thing. Update: 6th of November 2021 I re-enabled Developer Options and OEM Unlocking became selectable. Don't know how. NOTE #1...
forum.xda-developers.com
and @sd_shadow 's thread here: https://forum.xda-developers.com/t/...-unlocked-bootloader-non-twrp-method.4222583/
Click to expand...
Click to collapse
thank you for the reply and answers!
sd_shadow said:
The safest way to do this is to Use LMSA's flash rescue option
Flash the firmware with LMSA, then find the boot.img and patch it with Magisk.
Click to expand...
Click to collapse
i'm doing this now. just to check, i'm assuming i don't really need to flash the firmware to my phone at this step... did you mean instead just download it using the rescue option, get the boot.img to patch from the rom that way and then continue - without flashing my phone?
trevtdogg said:
thank you for the reply and answers!
i'm doing this now. just to check, i'm assuming i don't really need to flash the firmware to my phone at this step... did you mean instead just download it using the rescue option, get the boot.img to patch from the rom that way and then continue - without flashing my phone?
Click to expand...
Click to collapse
The biggest issue with rooting moto devices with a patched boot.img is a mismatched boot.img.
The easiest way to avoid that is just by flashing the full firmware before flashing the patched boot.img
It's not required, if you have the correct boot.img, but it's pretty easy to use the wrong version.
i understand.
so i just used the LMSA rescue option to download the correct rom, edited the flashfile.xml to take out the erase userdata option, flashed the firmware. LMSA said success, phone rebooted by itself, but is stuck in bootloop.
should i try flashing it again with the erase userdata back in? but i can't remember exactly which line it was, either before or after the erase metadata line i think...
edit - i ran a getvar all and compared it to the one i saved from before i flashed the rom. the only differences i can see are:
old-
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: yes
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 1
now-
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: No
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 0
(bootloader) slot-retry-count:_b: 6
does that help work out what happened?
edit 2 - tried it again with erase userdata added after erase metadata, still got boot loop after successful flash. getvar now shows this:
(bootloader) slot-successful:_a: no
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 2
(bootloader) slot-retry-count:_b: 7
edit 3 - tried a third time with erase userdata before erase metadata, and it worked! booted fine. getvar shows this now:
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-bootable:_a: Yes
(bootloader) slot-bootable:_b: Yes
(bootloader) slot-retry-count:_a: 1
(bootloader) slot-retry-count:_b: 7
does the parts not yet restored to the original settings mean i still need to flash it 'properly'?
not sure if erase userdata position or inclusion had anything to do with it or not, maybe it just wasn't properly flashing and had some files not copied properly?
maybe i should get a new pc data cable? the phone didn't come with one (only came with a usb-c to usb-c cable), so i'm using a pc to usb-c cable that came with some bluetooth headphones for charging them.
edit 4 - bought a new cable, re-flashed it, same result as in edit 3. it boots and appears to run fine, but 'fastboot getvar all' still shows '(bootloader) slot-successful:_b: no".
despite slot b showing unsuccessful in 'fastboot getvar all' (though still bootable), and with no further warnings or advice from others here, i went ahead with the steps and rooted with magisk.
all done! google pay looks like it will work (i'll test it later today) worked, and YASNAC shows all tests passing
slot b still shows the error as above on fastboot, but the phone appears to be working fine. i followed this guide for setting up magisk and it worked great! https://forum.xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/post-86321923
thank you @zgfg, @sd_shadow, @CFKod, @TakaSZK, and @AshleyJackson your posts helped a lot! and hopefully this all might help other inexperienced people like me who try to do the same.
a magisk update has come out, 25.1 (i'm still on 24.3).
are there any special steps i need to take to safely update magisk while rooted, or do i just press the big update button and follow the prompts?
Related
This place has gotten a bit messy with all of the threads out there and it's especially confusing for those who are new to unlocking and rooting. Or, heck, to those who weren't around as the threads were being written and referenced. I've reposted my consolidated step-by-step list half a dozen times so far - and the steps seem to be working for folks - so I'm going to post it here. You're still going to have to visit the original threads, but hopefully this will serve as a clear outline for you.
Maybe we can also try to keep general unlocking and rooting questions ("I don't know where to start, help me!") to this thread to avoid cluttering up the other ones. Reserve questions in those threads for those specifically related to the OP ("I received ABC error after doing XYZ, what does it mean?"). If anyone sees general unlocking or rooting questions in other threads, maybe direct them here as a place to start. Make sense?
A list of FAQs can be found here in the second post.
Many thanks to @tenfar and @DrakenFX (among others with their help and suggestions!) for the tools and files they provided to make all of this happen.
Unlocking and Rooting your Axon 7
This set of steps has worked successfully for multiple folks (including myself) on the US/NA variant (A2017U) and stock B29. Folks with EU/global variant (A2017G) may have issues and as of right now, should proceed with caution. If you see any problems and/or have a different variant and need additional (or different) steps added, let me know. I will update the thread as necessary.
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Backup your boot and recovery (just in case) using the tool found here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Using the same tool as above, flash TWRP (recovery) found in that thread. You do not need to flash the boot image!
Unlock the bootloader: http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash the bootstack and ROM for your variant: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Boot phone, set it up, whatever
Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, fully functioning TWRP (no data encryption issue), and a rooted phone. You will no longer be able to receive OTAs!
Putting Your Axon 7 Back to Stock
If you want to revert back to stock and re-lock your bootloader (eg. sending the phone in for warranty work or are selling it), you should be able to do that using the steps below. It worked for me, anyway, exactly as written below.
Copy everything off your internal storage that you don't want to lose. If you're not rooted (so already stock, but with unlocked bootloader), skip to step 6 below. Otherwise, continue.
Grab the "StockSystem" zip for your variant from this thread and place on your microSD card: http://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Reboot into TWRP and wipe system, data, dalvik, and cache
Flash the StockSystem zip and power off (doing so will restore stock boot but does not appear to restore recovery)
Boot into EDL mode and flash stock recovery only: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
Power off the phone, plug from computer, and then boot into stock recovery (hold Vol+ and press Pwr, continue holding Vol+ until recovery comes up)
Select "Wipe data / factory reset" and then "Yes"
After that finishes, select "Reboot to bootloader"
Plug in your phone into your computer and do: fastboot oem lock (see second post if this doesn't work and says <waiting for device>)
Your phone will reboot and should have been totally wiped (including internal storage) by doing the above
This should leave you with a stock, locked, and unrooted phone that can take OTAs. Note: it's possible (in fact, likely) that an OTA could break the ability to unlock your bootloader and gain root again, so be careful about going back to stock if you think you'll want to unlock/root later on!
If you need any stock files for B20 or B27 (stock recovery for re-locking, for example), you can get them here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
What does disemmcwp do and why should I do it?
disable emmc (internal storage) write protection is what allows changes to system (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
I only see B27 files and not B29. Help!
If you're in any of the threads referenced in the OP that only have files marked as B27, you can use those even if you're on or upgrading to B29. If the thread has B29 files, use those.
Fastboot can't find my device.
If fastboot oem lock returns <waiting for device> or fastboot devices doesn't show anything, the most likely culprit is that Windows is using updated ADB drivers and you need to roll back. You can do this via Device Manager > right-click Android Device (or Kedacom USB device) / Android Bootloader Interface > Update driver > Browse my computer for driver software > Let me pick... > Choose older version (in this case, v9)
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
xtermmin said:
For #3, you might want to emphasize that only TWRP is needed, and that people can skip flashing a boot.img. I've seen people who want to unlock their bootloader asking where to find the modified boot.img for B29, which isn't needed.
And of course, thanks for the guide!
Click to expand...
Click to collapse
Excellent point. Done!
It would be nice if someone can post a video on YouTube. That would make it that much easier.
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Also it would be nice a guide how to go back to stock and update to latest OTA.
Sent from my ZTE A2017G using Tapatalk
tasar said:
I have set up my phone now (with fingerprint security) and want to make a full backup in twrp. Is it true, that i must disable fingerpint and/or pin before i make an backup because when i restore backup with security enabled, that the phone was locked?
Click to expand...
Click to collapse
Yes you must disable your screen lock due to the encryption issue in MiFavor. If you do not disable your screen lock and restore your data, your pin/password/pattern would become wrong and your only option would be to factory reset. Fingerprint would still work but I wouldn't risk it.
dejikocv said:
Thanks for your guide.
It will be good to post also the steps to lock it again, in case that we need to send the phone for warranty. Because this method does not void warranty, does it?
I think that it is only to push the backup fastboot and 'fastboot oem lock'
Click to expand...
Click to collapse
razorsbk said:
Also it would be nice a guide how to go back to stock and update to latest OTA.
Click to expand...
Click to collapse
I've updated the OP with the relevant information. I haven't done it myself so I can't say what the exact screens are, but the steps should be pretty close and you should be able to figure it out.
If no one confirms (or corrects) the steps as I've written them, I'll go through the process before installing CM and update the steps to more accurately describe the process.
@rczrider
I'll updating my sticky thread/guide/info to direct everyone who want to unlock/root their devices, here to your thread....instead of having an outdated one with old info.
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
kodrnusa said:
Can you also make a guide for g model with 05 update for unlocking and rooting and istalling twrp.
Click to expand...
Click to collapse
This will be very helpful
Do I have to rollback to B20 or B27 to unlock bootloader?
@rczrider
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Orlando1193 said:
I have tested the back to stock steps for you on the US model and for now those steps do not get you back to stock. I have wiped the right things and flashed the StockSystem zip multiple times but twrp lives through the wipe and StockSystem install. I'll try to get it working and report back.
Click to expand...
Click to collapse
I was under the impression that @DrakenFX's StockSystem zip would overwrite boot, but I could be wrong in that. Have you tried doing the same process, but manually replacing recovery using @tenfar's tool and your own original recovery image?
If you don't have your original recovery, it (among other files for B20 and B27) can be found here: http://forum.xda-developers.com/axon-7/development/untouched-b20-boot-recovery-files-t3443818
baconboy said:
Thanks for the great guide!
So, if I do this, no OTA updates. Can I just download the updates and flash them? Are they available anywhere? Or no updates, period, right now?
Click to expand...
Click to collapse
Correct, no updates at all for the moment. As it stands, I believe we would need a modified/merged full zip that included the OTA's content. You definitely won't be able to receive OTAs officially.
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Great thread. Just wish this post was up 2 days ago. I just flashed B29 to my Axon from B20_Boot (which I now have read was a bad move. I just found out call audio & mic arent working). Good thing you put this post up. I have been scrambling through the threads to figure a solution. Just gonna flash back to B20 stock using TWRP :good:
Kevinkuensken said:
Everytime i want unlock bootloader i get this error
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
You probably haven't enabled OEM Unlock in Developer Options.
After i updated the Firmware of my Moto Z XT 1650-03 i cant use Wifi and Bluetooth anymore and my MAC Adress is bit funny 02:00:00:00:00:00 .
I tried to flash a Firmware through RSD Lite but im getting the Error gpt validation failed.
After i removed the string in the .xml file the software is working till flashing boot.img and than i get the Error Phone Retourned Error.
What can i do ?
dubist said:
After i updated the Firmware of my Moto Z XT 1650-03 i cant use Wifi and Bluetooth anymore and my MAC Adress is bit funny 02:00:00:00:00:00 .
I tried to flash a Firmware through RSD Lite but im getting the Error gpt validation failed.
After i removed the string in the .xml file the software is working till flashing boot.img and than i get the Error Phone Retourned Error.
What can i do ?
Click to expand...
Click to collapse
So unhappy you!
Same here, i give to Moto warranty but they said need replace motherboard with more 400USD, and i taked it back.
Now bought oneplus 5 for replacement, it much better, can root, flash, upgrate any rom, kernel ... freely no problem.
Will never buy any Lenovo.
dubist said:
After i updated the Firmware of my Moto Z XT 1650-03 i cant use Wifi and Bluetooth anymore and my MAC Adress is bit funny 02:00:00:00:00:00 .
I tried to flash a Firmware through RSD Lite but im getting the Error gpt validation failed.
After i removed the string in the .xml file the software is working till flashing boot.img and than i get the Error Phone Retourned Error.
What can i do ?
Click to expand...
Click to collapse
I noticed the same thing with the wifi MAC when I flashed ElementalX kernel to my otherwise stock but rooted Moto Z.
Restoring from my TWRP backup resolved the issue and the MAC address displays correctly again.
Is your Moto Z bootloader unlocked and do you have TWRP installed? If not, maybe you can go down that route to flash a custom ROM. (unfortunately I don't think the official firmware is available)
no my Bootloader is still locked.
No possibility?
If your bootloader ia still locked, you probably still have warranty.
Contact lenovo for that, they are your best bet.
Byte_76 said:
I noticed the same thing with the wifi MAC when I flashed ElementalX kernel to my otherwise stock but rooted Moto Z.
Restoring from my TWRP backup resolved the issue and the MAC address displays correctly again.
Is your Moto Z bootloader unlocked and do you have TWRP installed? If not, maybe you can go down that route to flash a custom ROM. (unfortunately I don't think the official firmware is available)
Click to expand...
Click to collapse
Can you share your backup TWRP ROM?
Tks!
Can I get copy of the correct rom from someone. Received a phone with the wrong one and don't have a backup to return to. Thanks.
I have the same issue. This happened after I tried flashing back the previous build on my Moto Z force. It flashed some partitions, but failed for the rest (For obvious reasons), so I need to figure out which partition has a mismatch and put it back to 7.1.1... Problem is, I need a full firmware to do this and it's not available online yet.
I'm pretty sure from my experience that it's just the modem which needs flashing. If someone is running a Moto Z unlocked on 7.1.1, can you do this in ADB in root and run the following command:
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin
Then upload the modem somewhere for us?
karendar said:
I'm pretty sure from my experience that it's just the modem which needs flashing. If someone is running a Moto Z unlocked on 7.1.1, can you do this in ADB in root and run the following command:
dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/modem.bin
Then upload the modem somewhere for us?
Click to expand...
Click to collapse
I think that this modem will work
https://www.androidfilehost.com/?fid=889764386195921696
It is for 7.1.1 stock
Download and extract then
fastboot flash modem NON-HLOS.bin
lollyjay said:
I think that this modem will work
https://www.androidfilehost.com/?fid=889764386195921696
It is for 7.1.1 stock
Download and extract then
fastboot flash modem NON-HLOS.bin
Click to expand...
Click to collapse
You my friend, just saved my phone. Wifi and BT is back. Thanks a million!
@Op, boot to safe mode:
Turn off phone
Hold vol down + Power
Connect phone to PC
Make sure fastboot is properly installed
fastboot flash modem NON-HLOS.bin
Reboot phone
Wifi and BT will be back up and running.
karendar said:
You my friend, just saved my phone. Wifi and BT is back. Thanks a million!
@Op, boot to safe mode:
Turn off phone
Hold vol down + Power
Connect phone to PC
Make sure fastboot is properly installed
fastboot flash modem NON-HLOS.bin
Reboot phone
Wifi and BT will be back up and running.
Click to expand...
Click to collapse
Glad I could help. The modem zip was prepared by erfan.
lollyjay said:
Glad I could help. The modem zip was prepared by erfan.
Click to expand...
Click to collapse
Hi,
I've got the same Problem with WLan MAC 02:00:00:00:00:00 after updating.
I download the NON-HLOS.bin file.
but it is for 7.1.1 can i still use it?
I followed these steps:
-> Turn off phone (check)
-> Hold vol down + Power (check)
-> Connect phone to PC (check)
-> Make sure fastboot is properly installed (Fastboot? Ok, i am downloading the Adroid Studio with fastboot)
-> fastboot flash modem NON-HLOS.bin (check not yet)
-> Reboot phone (check not yet)
-----
wlan mac: 02:00:00:00:00:00
Android 7.0
Baseband_Version: M8996_1239.53.01.126R SRS
Build-Nummer: NPLS25.86-31-5
reteu
-----
I don't have any backup or experience with these things
A my phone is unrooted.
What does this line on the bootscreen mean -> "AP Fastboot Flash Mode (secure)"
These situation is just a little bit overwhelmed for me
minotaurus81 said:
Hi,
I've got the same Problem with WLan MAC 02:00:00:00:00:00 after updating.
I download the NON-HLOS.bin file.
but it is for 7.1.1 can i still use it?
I followed these steps:
-> Turn off phone (check)
-> Hold vol down + Power (check)
-> Connect phone to PC (check)
-> Make sure fastboot is properly installed (Fastboot? Ok, i am downloading the Adroid Studio with fastboot)
-> fastboot flash modem NON-HLOS.bin (check not yet)
-> Reboot phone (check not yet)
-----
wlan mac: 02:00:00:00:00:00
Android 7.0
Baseband_Version: M8996_1239.53.01.126R SRS
Build-Nummer: NPLS25.86-31-5
reteu
-----
I don't have any backup or experience with these things
A my phone is unrooted.
What does this line on the bootscreen mean -> "AP Fastboot Flash Mode (secure)"
These situation is just a little bit overwhelmed for me
Click to expand...
Click to collapse
This works only for phone with unlocked bootloader.
lollyjay said:
This works only for phone with unlocked bootloader.
Click to expand...
Click to collapse
Ah ok thank you
is there any other Option to fix this problem without unlocking it? (have my phone now for 1.5 months).
Yes i know i have guarantee
If i unlock it is there any fool-proof tutorial?
minotaurus81 said:
Ah ok thank you
is there any other Option to fix this problem without unlocking it? (have my phone now for 1.5 months).
Yes i know i have guarantee
If i unlock it is there any fool-proof tutorial?
Click to expand...
Click to collapse
I am not aware of any solution other than wait for the next OTA.
As long as you know that your warranty is void after unlocking the bootloader, the procedure is well detailed on the Motorola website.
lollyjay said:
This works only for phone with unlocked bootloader.
Click to expand...
Click to collapse
No, that's not true. Flashing the GPT, the bootloader, the modem partition, the BT partition and DSP partition works fine in a locked bootloader phone. The only partitions that can't be flashed in a locked bootloader status is system, recovery and boot.
His issue is not the same as mine though, as mine occurred when I attempted to roll back to 7.0. He seems stuck on 7.0. So he would need the proper NON-HLOS.bin for his version and flash it.
@minotaurus81 did you update your phone to 7.1.1 and did it fail? Because that's the only way I think it could have messed up your phone. I strongly suggest that if you don't have the technical knowledge to fix this to return your phone for warranty repair. You might mess things up even further if you don't do the right thing...
lollyjay said:
I am not aware of any solution other than wait for the next OTA.
As long as you know that your warranty is void after unlocking the bootloader, the procedure is well detailed on the Motorola website.
Click to expand...
Click to collapse
Just to clarify, waiting for next OTA might not solve anything. OTA packages usually have .p (patch) files instead of the entire file to update with in order to save space. If it detects that a different modem is flashed on the device, it will simply fail and not flash anything else.
Hey guys,
my phone has the same issue. I tried to flash the modem but that did not work, still no Wifi and Bluetooth. I did not unlock my phone yet since karendar stated there was no need for that.
My phone got wet a couple of months ago (which is why there is no warranty anymore) but it worked fine until I updated to 7.1.1 recently. So I'm pretty sure the issue is due to the update.
This is what happened when flashing the modem:
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:modem: not found
target reported max download size of 536870912 bytes
sending 'modem' (81729 KB)...
OKAY [ 1.766s]
writing 'modem'...
OKAY [ 1.110s]
finished. total time: 2.892s
Does that look alright or should I unlock my phone and try again?
Thanks for your help
I have the same issue, but at least i have WiFi. Bluetooth not working anymore after 7.1.1. Tried everiything !!!!
Enviado desde mi XT1650-03 mediante Tapatalk
Hello developers,
I bought a Huawei P20 lite a few days ago after verifing, that lineage is possible to install on those phones.
Now, after struggling for 3 days to install lineage, I decided to post here.
First some information about my phone:
Device: Huawei P20 lite dual SIM, 4GB RAM, 64GB internal (ANE-L21, i guess?)
Fastboot Info (I ran those commands when creating this post):
fastboot oem get-build-number: ANE-LX1 9.1.0.257(C432E6R1P7) (from what I understood, ANE-LX1 and ANE-L21 Firmwares are the same?)
fastboot oem get-product-model : ANE-LX1
fastboot getvar version: FALED, Command not allowed
fastboot getvar vendorcountry: HW/EU
When I got the phone, I got my bootloader unlock code first.
I then successfully updated the phone to the newest version (the official Huawei approach, using HiSuite).
After that, I unlocked the bootloader with no problems and flashed TWRP.
I needed to try a few versions to find one that's working as the official ones for that phone kept freezing, I finally found one by Pretorian08 that's working).
Then I formatted to get rid of encryption, did the wipe procedure, cleared the cache, data and system partition and installed the newest lineage build and GAPPS.
After rebooting, the Phone showed me the usual "your device has been unlocked and can't be trusted"- dialog, and tried to boot then.
From here on, nothing happened.
I tried every build I could find, including the most actual one from tonight (lineage-16.0-20201214-nightly-anne-signed.zip).
Some builds would reboot after some time and show the shortened warning message, then boot directly into Recovery.
I totally bricked my phone somewhere on the way (multiple times I think), but could unbrick it by flashing rescue_recovery_kernel, rescue_recovery_ramdisk and rescue_recovery_vendor with appropriate img files extracted from a "Anne-L01 Anne-L21 9.1.0.132(C432E5R1P7T8)" - Firmware and then going back to zero by installing a stockrom via dload and unlocking the bootloader again.
I then tried several other custom Roms, but the outcome is always the same: The phone just freezes with the warning message still visible while trying to boot up, or it boots into TWRP.
ROMs I've tried (I'll write the filenames to provide more info):
- Havoc OS-v3.2-20200215-ARM64AB-GSI.img
- Resurrection Remix ARM64_AB_20191205.img (this is the only custom ROM that will do ANYTHING at all: It will show the Red RessurectionMix Bootlogo, but sadly it won't boot past that point)
- Treble AOSP losq-v224-201017-arm64-bvN.img
With the above 3, installing GAPPS is not possible because "not enough free space in system partition"
- Every possible lineage build for that phone
As stated before, I'm struggling with the phone for 3 days now, so I followed a whole bunch of threads and advices, flashed multiple firmware files using different methods and tried like 7 different TWRP versions. With other words: I did a lot of things, which yould possibly mess up the phone and maybe I did something wrong at some point.
Maybe, I flashed a wrong Firmware while trying to unbrick or something like that. Can you guys help me understand what I'm doing wrong?
I don't like it if people post questions in a forum and then don't share what they figured out, so I'll post 's a little update after 6 days:
Here's a serious advice, if you're considering to buy this phone because there are lineage builds available: forget it.
I mean in most cases it seems to work somehow (from what I read), but from my experience I can say now, that there are phones where it apparently just doesn't work.
I've wasted over one week of my holiday working nonstop on that phone, I've downloaded about 50GB of different firmware files, recoveries, patches and custom Roms and flashed my firmware like 40 times. Best thing I could archieve is an indefinitely looping bootlogo in AOSP, lineage won't even get to that point.
I've tried every lineage build available, i've tried EMUI versions from 9.1.0.0X up to 9.1.0.200 (it is stated multiple times that the .200 will definitely work), no chance. I even tried a rollback to EMUI 8 via Hisuite and using old lineag builds in the end.
The fact that I didn't get any advice in this forum leads me to the conclusion, that no one has an Idea on what the problem is here either.
As I don't feel good with using a phone that still has original google stuff and huawei spy/bloatware installed, the only option that is left to me is just throwing it away and using some old phone. That's sad and a real waste of material and time, as the phone is brand new, but using the stockrom is no option to me. I really don't know what went wrong, I've already successully installed lineage (and cyanogenmod before) on more than 8 other devices, always without any problems.
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
user_name_duplicate said:
So even if you (think you) know what you're doing, I can't recommend buying this device with the intention of using lineage.
Click to expand...
Click to collapse
P20 lite is not so bad, maybe you are doing something wrong...
I've installed without problems Havoc, LOS 16.0, LOS 17.1unofficial, AOSP 10, losq-v224-201017 etc. etc...
P.S.: If you "hate" Google and Google's bloatware (like me ) only, you can simply rebrand your phone to chinese Nova 3e.
Or, choose Custom ROM based on Stock with KangVip settings , stable enough to be used as your daily driver." ( e.g. https://forum.xda-developers.com/hu...m-emui-8-0-kangvip-p20-lite-catuva21-t3813564
https://forum.xda-developers.com/hu...-emui-8-0-0-huawei-p20-lite-dual-sim-t3813604) . Using KangVip settings you can disable completely GAPPs .
(My primary phone is at the moment Mate 10 lite rebranded to chinese Maimang 6 (to get away from GAPPS ) . Among other things, better battery life, lower data consumption (using FUT) etc.)
Hi -Alf-, thank you for replying.
-Alf- said:
P20 lite is not so bad, maybe you are doing something wrong...
Click to expand...
Click to collapse
You're right, it's not the phone, it's me. I guess I am doing something wrong, but I don't have the slightest clue what that is.
Any suggestions?
I've already invested a lot of time and have more or less resignated, but thanks to covid lockdown I'm basically trapped inside the house and might aswell give it another try.
Rebranding is an option, you're right. I already have downloaded a nova 3e Firmware, if nothing else works, I might try that.
Also, I'll have a look at the KangVip Roms, haven't heard of them before.
But to be honest, I think I wouldn't be satisfied with those options, at least not for a long time.
Getting lineage running on that phone is a task, the problem solver inside me is really commited to accomplish, because that was the intention I bought the phone with. Also, not being able to accomplish something that hundreds of other people already have done and that is proven to work is driving me nuts. I wouldn't have bothered trying to get it working for 10 days otherwise.
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Try Havoc 2.9 (requires EMUI 8)
Havoc 2.9
Hi -Alf-,
-Alf- said:
Try Havoc 2.9 (requires EMUI 8)
Click to expand...
Click to collapse
Tried that now, after downgrading to EMUI 8 via HiSuite, I did exactly what you wrote in that thread. The outcome is the same as with every other ROM I've tried: I see the "your device has been unlocked and can't be trusted" screen, then after a while it tells me that "my device is booting now" and just does nothing except rebooting every 10 or so minutes.
Luckily those devices seem to be fairly indestructible, as long as the Bootloader is open and FRP is disabled, so I'll give it some more tries.
-Alf- said:
Unfortunately, availability of custom ROMs for Kirin devices is scarce.
Click to expand...
Click to collapse
I bought the phone because I thought it was officially supported:
LineageOS Downloads
download.lineageos.org
Was that assumption wrong, is there some hint or exception, that I'm not seeing?
The phone was delivered some weeks late because the seller was out of stock. I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
user_name_duplicate said:
I guess it came directly from china. Is it possible, that I got a new hardware revision, which is not yet supported?
Click to expand...
Click to collapse
It may be a fake, try to verify the authenticity on linked website
imei24
user_name_duplicate said:
I guess it came directly from china
Click to expand...
Click to collapse
Exactly, I saw for example Huawei P20 Pro with MediaTek proc.
Btw., I have installed this Havoc 2.9 three times without problem, so it's really very strange...
In fastboot mode run commands :
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
fastboot oem get-build-number
fastboot getvar vendorcountry
fastboot oem get-product-model
fastboot getvar rescue_version
and post the results please.
Some might fail, so don't worry about it.
You can also download "Device Info HW" apk and check your SoC (Kirin 659) Vendor (HiSilicon), ABI (arm64-v8a) etc.
On imei24, the device is listed as "Huawei P20 Lite" for both imeis, blacklist status is "clean". Recognized Serial is the same for both Imei numbers.
Only thing that's not clear to me is the warranty status:
Warranty start: 2018/7/23
Warranty end: 2018/8/6
So it can't be that new, at least not factory new, right?
I bought it on real.de, so I have no further information where it comes from. China was just my assumption because they where out of stock and delivered 2 or 3 weeks late. I can't really imagine that real is selling fake phones (on purpose). That really wouldn't help their image if people found out.
I ran the commands you provided:
fastboot oem oeminforead-CUSTOM_VERSION: FAILED
fastboot oem oeminforead-SYSTEM_VERSION : ANE-LX1 8.0.0.180(C432)
fastboot oem get-build-number : ANE-LX1 8.0.0.180(C432)
fastboot getvar vendorcountry: hw/eu
fastboot oem get-product-model: ANE-LX1
fastboot getvar rescue_version: rescue0.6
I will download the Device Info apk as soon as my device boots again (I will reflash the stock image once again).
Edit: Device Info HW is telling me I'm using a Kirin 659 SOC.
Okay, most of custom ROMs require lower build number, that's why I wrote that I tested Havoc 2.9 on .126. If you are running latest build number, it may cause your problems.
IMO it is time to clean your phone, extract from Oreo firmware (it doesn't matter which build number) ramdisk.img , kernel.img, recovery_ramdisk.img and erecovery_ramdisk.img and transfer to the SD card.
Download .126 Service ROM
8.0.126
unpack it and transfer dload file to the SD Card (without unpacking it)
Install
TWRP
over eRecovery, boot into TWRP, select Flash image and flash 4 files. Go back to main TWRP's panel > Reboot > Power Off.
Use three button combo to flash the ROM. This process will erase all your data and lock the bootloader again!!!
Unlock BL and try Havoc 2.9 . It must work!
Good luck.
Edit: I found on my MEGA :
https://mega.nz/#!o8FUVR6T!-1fl6TviRtgGbssuG9LgyssCJg4dwxa84luJmrnvSCg
https://mega.nz/#!gkdgnLBa!O8LVZF4J0NiEB78c9z4_FxASN0vWx3rOAIQdmhApAOQ
https://mega.nz/#!xpViTTSC!Q_5ieeEL0gpKROj35cvjc_TRddmkFTMsIxvOT6lS23Y
https://mega.nz/#!EhM2lZqK!yphxvKNUQueIryop44DmPflp7Iwi9c8ExeaCRqA-iY4
Hello Alf, thanks for your last reply!
Downgrading worked, that was the last thing I've tried before christmas.
I wanted to continue today, but found this thread you've posted in.
I thought I'd give it a try and now I'm running on lineage (which is what I initially wanted), sadly only the 15.1 version, but I don't need the newest version.
WiFi is working and, until now, it's running stable. I've installed 8.1. nano gapps (might try pico in the future) and magisk v21.
Maybe I'm lucky and in the next few weeks or months I'll find a working build of an android pie lineage.
I think with installed TWRP it should now be possible, to do a complete backup, mess around with the system (i.e. upgrade Android/Flash ROMs) and then restore it to my now working state, is that correct?
If that's the case, I'll try some other ROMs, including the havok ROM I've already downloaded.
Which partitions must be included in my backup to perform such operations?
For anyone else encountering my problem, here is what finally did the trick:
Code:
- downgrade to .126, following alfs procedure
- Flash TWRP by pretoriano80 (on recovery_ramdisk partition)
- do a wipe (format data to get rid of encryption, then via advanced wipe format cache partitions and system)
- install lineage 15 (link), last build is from 2020-10-27, so it's not an abandoned build
- install GAPPS 8.1
- install magisk v21
- wipe cache/Dalvik
- boot to system
Booting for the first time took a few minutes, but since then, it's running smooth and without any problems.
The only thing that's still an enigma to me is, why the LOS builds I initially tried (with EMUI 9.0.0.200) didn't work, even though other people don't seem to have a problem with ANE-LX1 and LOS16. If anyone is reading this and has an answer to that question, please post!
For now, I'm happy with LOS 15. Thank you many many times, Alf! Greetings to Melmac!
user_name_duplicate said:
Thank you many many times, Alf!
Click to expand...
Click to collapse
No problem...
user_name_duplicate said:
Greetings to Melmac!
Click to expand...
Click to collapse
I'm currently struggling with the same issue. Tried every combination of TWRP with lineage 16 and gapps. Some roms I can get to boot but then not enough space for h gapps. I have tried to wipe system, data and cache to resize system partition which ends up in phone booting directly to TWRP. Other times I get to warning screen and end up with boot - loop. So I'm well a are off your frustration. However I have decided that I'm not gonna settle for version 15. I'm trying for 17 but much have to settle with lineage is 16..
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Link575 said:
Nice, first thanks for the hard work you're putting in. Second, is there an advantage to converting first to DE2117 then installing lineage as opposed to just installing lineage from DE2118 that you know of? I know in the other post you answered my other question stating that the Lineage will install on either so I wasn't sure if I'd get any benefit from starting over and converting my DE2118. TIA
Click to expand...
Click to collapse
Lineage is using own kernel and boot.img on A11 so in the short run it is not going too make any difference, but when Lineage moves forward to A12 the OEM Firmware has newer drivers and is updated sooner, has more OEM features and bugfixes as well as no carrier bloatware.
It is possible that OP will neuter the Carrier firmware with an OTA update to prevent cross flashing device away from the Carrier rom in the next OTA update by preventing fastbootd from flashing the us oem from a carrier phone.
They have already removed fastboot boot command to boot a boot image without flashing it for test before you flash and to allow Magisk to make a backup of the original boot.img before adding Magisk.
I would convert NOW, before they decide to slam the door on this ability with a future OTA that will not allow you to downgrade and prevent this as they are under contract with the carriers to not allow this to be done.
Ok, thank you for the explanation. Guess I'll back everything up and convert it.
scanman0 said:
Lineage installation on N200 REQUIRES that you are running Android 11 or phone will soft loop after installing the Lineage boot.img
If you are updated to Android 12 firmware and want to install Lineage, you MUST downgrade first to:
DE2117 OEM Android 11 FINAL OTA
WARNING: This WILL erase all user data.
1. Place the firmware .zip file in the user root of internal phone storage.
2. Sideload OnePlus firmware Downgrade Tool on phone and use tool to flash the Android 11 firmware.
There is an Emergency Firmware install tool that OnePlus posted to the OP forum that does NOT check root status when the need to downgrade back to A11 was first acknowledged due to modem issue with first A12 OTA release.
This file was removed in a few days when they posted the official Downgrade tool replaced it.
I have used this tool to upgrade DE2117 C_16 to DE2117 C_17 while rooted and the built in upgrade tool failed at 37%.
Click to expand...
Click to collapse
This worked perfectly after following your convert guide and upgrading to 12. Downgraded back to 11 so I could install lineageOS. Thanks again!
This reddit post has a link to an English version of the downgrade apk which makes it a little easier.
keeps saying verification failed
weirdfate said:
keeps saying verification failed
Click to expand...
Click to collapse
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
I m trying as well .. but stuck with verification failed message just as scanman0 I m on stock android12 no root if anyone know how to fix it ... please assit
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
radekmazur said:
I just downgraded. Make sure you remove root via magisk. Then proceed to rollback to Android 11. Everything worked fine. I'll install lineage tonight when I get home.
Click to expand...
Click to collapse
I did not have to remove root. I used the version posted that does not check for root but maybe there's a different reason.
Does the downgrade apk have to be sideloaded via ADB?
T3CHN0T33N said:
Does the downgrade apk have to be sideloaded via ADB?
Click to expand...
Click to collapse
Just place apk in phones working directory, same path where your downloads folder is. Then install from there like any other apk and run. I also kept the FW file in the same directory but I'm not sure if that was necessary.
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
T3CHN0T33N said:
So, just to confirm, I press "local install" and select the firmware zip and it closes? Is the tool supposed to do anything else or am I good to flash LineageOS?
Click to expand...
Click to collapse
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Link575 said:
Ummm if I remember correctly hit local install and then it will prompt to point towards which FW to use. After you hit it, it will go back to the previous screen, I think verify and unpack it, then install it. Mine did appear like it was doing nothing after picking the FW and so I picked again which screwed things up so just wait after picking, it should start.
After its done it will give a message saying to restart phone I think for it to take effect, then after you restart it should ask to wipe phone, then restart again and you'd be in A11 presumably. Once in A11 your good to follow the normal procedure to install Lineage. This is all from memory though so I MAY have missed something but I don't think I did.
Click to expand...
Click to collapse
When you say "screwed things up" what do you mean? How did it effect the install?
T3CHN0T33N said:
When you say "screwed things up" what do you mean? How did it effect the install?
Click to expand...
Click to collapse
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Link575 said:
Nothing major, caused the UI to glitch out and made it seem like the process was stuck at 81% but when I closed the app and tried to do it again it jumped to 100 and said to restart the device.
I've downgraded a second time (I'm very indecisive on which OS I want to use) and that one went as expected since I knew to give it a second to start doing its thing.
Click to expand...
Click to collapse
Weird, for me it just closes the app and does nothing, both the official and emergency ones. I even tried adding it to magisk's deny-list.
But I just restored the boot image via magisk (didn't restart) and it works now...
scanman0 said:
Did you remove root (Restore boot.img) and then factory reset?
You will loose all data doing this anyway.
Click to expand...
Click to collapse
Yes I factory restored the phone and tried again. Still fails every time
Has anybody had any luck figuring out the verification failed message? I too have tried both the official and emergency apps, of course I can't read the actual message in what I presume is Chinese, but it doesn't do anything and the other version says verification failed. Have not rooted. Kind of at a loss right now and all I want to do is install Lineage! I've already got my unlock token from OnePlus, but my understanding is that the phone still needs to be on A11 before installling Lineage.
I'd like to start by saying after 2 weeks of researching and piecing guides together to unbrick my phone was hell. But once i found the right route it took me less thank 10mins all from a simple tool called Fastboot Enhanced V1.3.0. Now this Nifty little tool took me from bricked phone which was saying "Your img(Boot, Recovery) have been destroyed please flash the right files or contact customer service to fix this problem to Unbricked in less than 10 minutes. It took me 2 weeks of researching but it's finally done. Now most of you will say well you could have use MSMTool or the MTK or even SP Flash Tool. Those are all fine and dandy and all but one problem with those. YOU have to SCOUR the internet to TRY to find files you need to actually be able to use them. I been over several guides. I had when a guide basically says this 1) DO THIS SKIP SKIP SKIP important parts 2) NOW DO THIS. Like WTH was i supposed to do in between 1 and 2. Todays guides lack thoroughism and complettioin. Guides these days take Half Ste;ps and then thrown together.
I will also leave a step by step instructions on how to use the Fastboot Enhanced V1.3.0 in DETAIL on how to get your phone from what mine did to Unbricked state. I will also attack Nord N200 5G DE2118 .img FIles for those who have a hard time scouring the internet for things. I for one get agitated and aggravated as hell when searching the internet for things. Especially when you have to pc things together. I will leave files if it's Fine by staff. Now these files have come directly from my OnePlus Nord N200 DE2118 extracted less than 2 hours ago 10:04 p.m. EST September 10th 2022. Can Only attach One File? and i can't even remove the accidental clicked bmp pic of COD BO Cold War Zombies.
Guide For Using Fastboot Enhanced V1.3.0
1) Download Fastboot Enhanced Tool from: https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ from XDA Which is how I came across it. . The Tool is a WINDOWS ONLY Tool. (How many guides i came accross that didn't state whether it's for Windows or Linux) I use Dual Boot so I have both.
2) Install Fastboot Enhanced V1.3.0 and wait for it to finish. Now you will only have to be in Fastboot Mode to do any of this. I can't believe how a semi hard problem was fixed really easy
3) Now you will Have to Have a Payload.Bin File which can be found with any OEM Firmware for Your specific Phone. The Payload.bin allows you to be able to do a Payload Dump Using Fastboot enhance it is at this point if any of your partitions are missing or corrupt you will find out because it will tell you if you can understand the way it's explains it.
4) This Nifty little tool will tell you your device naem whether your phone is using secure boot or not, current slot your phone is using if you have an a/b partition scheme and the update Status. This is Listed Under basice properties. AGAIN MAKE SURE YOUR IN FASTBOOT MODE.
5) Next tab is the Partitions Tab which will List all your partitions currently on your phone . To the right of your listed partitions you will have and ACTIONS Tab. This is the tab where you can flash, erase, delete, create, and Resize your partitions. With this tool You CAN Flash Important Partions So be careful what you flash.
6) Next Tab Over is the Payload Dumper. This is the Tab where you need the Payload.bin File for your specific phone. this will give you payload version manifest size, metadata signatures size Metadata Signatures (Base64), data blobs, singatures size signatures (Base64) Fuill package Yes or No. Timestamp and block size. also under payload dumper tab another tab shows up called the Dynamic Partition Metadata. Now this will list your REALLY IMPORTANT Dynamic Partitions These are the partitions you don't want to flash anything over them. It will give you the Partition group size, which partitions are included and tells you wheter snapshot is enabled or not.
7) Under The payload Dumper tab the partitions tab gets a different Actions box. This time i'ts a box that let's you extract your .IMG files from your phone it allows for incremental as well as to ignore unknown operations and ignore checksums also under this partitions tab it gives you a checksum for each and every one of your partitionss. Ok now on to the Simple but yet comprehensive guide.
8) Now to start you want to add the Payload.bin to the Payload Dumper and then click on the Partitions tab. Once under this tab you will select each partition and hit the extract button and extract it to a folder named something like Flash FIles.
9) you hace to do this for each partition. Once done you will have your .IMG files from your exact phone for future use as well. You then want to click on the Fastboot Visualization tab and then click on Partitions.
10) Once under the partitions tab here, you will want to start flashing your .IMG files to the partitions. it should take you around 10 to 15 mins total to finish flashing everything.
11) Once your finished flashing you want to do a quick Terminal and do a FASTBOOT -W and then Fastboot Reboot and watch your phone start working again.
FEEL FREE TO LEAVE ANY COMMENTS SUGGESTIONS ON WHAT COULD HAVE BEEN BETTER OR IF IT'S NOT ENOUGH DETAIL. I TAKE CONSTRUCTIVE CRITICISM WITH A GRAIN OF SALT. THIS WAS MY FIRST GUIDE I EVER PUT TOGETHER. LOL THIS GUIDE TOOK ME LONGER THAN IT DID UNBRICKING MY PHONE.
BELOW YOU WILL FIND .IMG FILES FOR ONEPLUS NORD N200 DE2118
Thanks so much man. This phone has been an absolute pain in my ass to unbrick, the issue Ive had with Fastboot enchance is that all the firmware versions Ive found seem to contain images it doesnt recognize for the phone.
Do you have the original OTA for these , or the un-extracted payload.bin youd possibly be able to post?
So I went through the process without success, the only abnormalities I noticed were that my device did not have a partition for "my_carrier.img" , so that wasnt flashed.
And upon using the fastboot -w command, it did execute but at the end was given the message "Erase successful, but not automatically formatting.
File system type raw not supported."
Silent_Song1982 said:
Thanks so much man. This phone has been an absolute pain in my ass to unbrick, the issue Ive had with Fastboot enchance is that all the firmware versions Ive found seem to contain images it doesnt recognize for the phone.
Do you have the original OTA for these , or the un-extracted payload.bin youd possibly be able to post?
Click to expand...
Click to collapse
I found the way MSMTool works too. I'm going to probably write a guide for that too. MSMTool is so much easier.
Silent_Song1982 said:
So I went through the process without success, the only abnormalities I noticed were that my device did not have a partition for "my_carrier.img" , so that wasnt flashed.
And upon using the fastboot -w command, it did execute but at the end was given the message "Erase successful, but not automatically formatting.
File system type raw not supported."
Click to expand...
Click to collapse
I had a lot of issues with Fastboot Enhance too until I realized I was the one causing errors. Any logical partition it doesn't recognize you can create an empty partition wiht that name and it will resize it then copy it over. Also make sure whatever slot you're on, so say slot a, your logic paritions would be system_a, system_ext_a, vendor_a, product_a and odm_a except I dont see odm.img in the list of file by OP so I'm not sure if that will even help.
and now i have ran into HARD BRICKED mode trying to flash a custom from. phone will only load EDL and everytime I try msmtool I get the error Check OCDT CDT file empty please redownload it. and I scoured the internet for 4 days now and all I can find is stuff like What is .CDT extension but nothing about having and empty CDT file for android. getting frustrated with it now
Link575 said:
I had a lot of issues with Fastboot Enhance too until I realized I was the one causing errors. Any logical partition it doesn't recognize you can create an empty partition wiht that name and it will resize it then copy it over. Also make sure whatever slot you're on, so say slot a, your logic paritions would be system_a, system_ext_a, vendor_a, product_a and odm_a except I dont see odm.img in the list of file by OP so I'm not sure if that will even help.
Click to expand...
Click to collapse
here is the ODM file. if you might be able to post a cdt file much apppreciated
sorry took so long to upload it for you
MiniNinja2024 said:
here is the ODM file. if you might be able to post a cdt file much apppreciated
sorry took so long to upload it for you
Click to expand...
Click to collapse
Hey I appreciate it but I didn't need it I was just informing the poster above that the ODM file was missing and that might cause an issue when using Enhanced Fastboot. Not really sure what a cdt file is though, sorry.
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
hitsndc said:
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
Click to expand...
Click to collapse
my phones being recognized as a Oneplus A5000 for some reason now. and it's a Nord N200 i've also been stumped by the attached pic and my phone is stuck in EDL mode
hitsndc said:
Im in the US and have the unlocked N200, to unbrick mines i used the MSM tool and selected MetroPCS as my carrier. then after i had phone functionality i put the correct rom on my phone.
Click to expand...
Click to collapse
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
vipermark7 said:
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
Click to expand...
Click to collapse
this is my version
DE18CB_T-Mobile-MetroPCS_OxygenOS_11.0.1.7.zip | by Scanman0 for OnePlus Nord N200 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
also my phone is stuck in EDL mode and it registers as an android oneplus a5000 tablet for some odd reason i've tried just about every single n200 file out ever since my phone got stuck in EDL mode and evertime same result cdt file
also i had some with same version that i know personally send me his cdt file and same thing says it's empty
and my phone is the Metro-by Tmobile
vipermark7 said:
Can you link me to the MSM tool you used? I think there might be a few different versions of it floating around for the Nord N200. Mine was purchased unlocked
Click to expand...
Click to collapse
and i'm in Florida
Can someone please dump the firmware from this phone & upload it please?
cryptojoe37 said:
Can someone please dump the firmware from this phone & upload it please?
Click to expand...
Click to collapse
I gave up on this phone. no long working on it. Was having major pains with it.
I need the loader from the firmware
cryptojoe37 said:
I need the loader from the firmware
Click to expand...
Click to collapse
the loader ? bootloader?
michaelwaycraig67 said:
the loader ? bootloader?
Click to expand...
Click to collapse
abl/xbl partitions. perhaps some other.
zmashine said:
abl/xbl partitions. perhaps some other.
Click to expand...
Click to collapse
uploading now will give a link after uploaded
zmashine said:
abl/xbl partitions. perhaps some other.
Click to expand...
Click to collapse
2.74 GB file on MEGA
mega.nz
MiniNinja2024 said:
I'd like to start by saying after 2 weeks of researching and piecing guides together to unbrick my phone was hell. But once i found the right route it took me less thank 10mins all from a simple tool called Fastboot Enhanced V1.3.0. Now this Nifty little tool took me from bricked phone which was saying "Your img(Boot, Recovery) have been destroyed please flash the right files or contact customer service to fix this problem to Unbricked in less than 10 minutes. It took me 2 weeks of researching but it's finally done. Now most of you will say well you could have use MSMTool or the MTK or even SP Flash Tool. Those are all fine and dandy and all but one problem with those. YOU have to SCOUR the internet to TRY to find files you need to actually be able to use them. I been over several guides. I had when a guide basically says this 1) DO THIS SKIP SKIP SKIP important parts 2) NOW DO THIS. Like WTH was i supposed to do in between 1 and 2. Todays guides lack thoroughism and complettioin. Guides these days take Half Ste;ps and then thrown together.
I will also leave a step by step instructions on how to use the Fastboot Enhanced V1.3.0 in DETAIL on how to get your phone from what mine did to Unbricked state. I will also attack Nord N200 5G DE2118 .img FIles for those who have a hard time scouring the internet for things. I for one get agitated and aggravated as hell when searching the internet for things. Especially when you have to pc things together. I will leave files if it's Fine by staff. Now these files have come directly from my OnePlus Nord N200 DE2118 extracted less than 2 hours ago 10:04 p.m. EST September 10th 2022. Can Only attach One File? and i can't even remove the accidental clicked bmp pic of COD BO Cold War Zombies.
Guide For Using Fastboot Enhanced V1.3.0
1) Download Fastboot Enhanced Tool from: https://forum.xda-developers.com/t/...enhance-payload-dumper-image-flasher.4310553/ from XDA Which is how I came across it. . The Tool is a WINDOWS ONLY Tool. (How many guides i came accross that didn't state whether it's for Windows or Linux) I use Dual Boot so I have both.
2) Install Fastboot Enhanced V1.3.0 and wait for it to finish. Now you will only have to be in Fastboot Mode to do any of this. I can't believe how a semi hard problem was fixed really easy
3) Now you will Have to Have a Payload.Bin File which can be found with any OEM Firmware for Your specific Phone. The Payload.bin allows you to be able to do a Payload Dump Using Fastboot enhance it is at this point if any of your partitions are missing or corrupt you will find out because it will tell you if you can understand the way it's explains it.
4) This Nifty little tool will tell you your device naem whether your phone is using secure boot or not, current slot your phone is using if you have an a/b partition scheme and the update Status. This is Listed Under basice properties. AGAIN MAKE SURE YOUR IN FASTBOOT MODE.
5) Next tab is the Partitions Tab which will List all your partitions currently on your phone . To the right of your listed partitions you will have and ACTIONS Tab. This is the tab where you can flash, erase, delete, create, and Resize your partitions. With this tool You CAN Flash Important Partions So be careful what you flash.
6) Next Tab Over is the Payload Dumper. This is the Tab where you need the Payload.bin File for your specific phone. this will give you payload version manifest size, metadata signatures size Metadata Signatures (Base64), data blobs, singatures size signatures (Base64) Fuill package Yes or No. Timestamp and block size. also under payload dumper tab another tab shows up called the Dynamic Partition Metadata. Now this will list your REALLY IMPORTANT Dynamic Partitions These are the partitions you don't want to flash anything over them. It will give you the Partition group size, which partitions are included and tells you wheter snapshot is enabled or not.
7) Under The payload Dumper tab the partitions tab gets a different Actions box. This time i'ts a box that let's you extract your .IMG files from your phone it allows for incremental as well as to ignore unknown operations and ignore checksums also under this partitions tab it gives you a checksum for each and every one of your partitionss. Ok now on to the Simple but yet comprehensive guide.
8) Now to start you want to add the Payload.bin to the Payload Dumper and then click on the Partitions tab. Once under this tab you will select each partition and hit the extract button and extract it to a folder named something like Flash FIles.
9) you hace to do this for each partition. Once done you will have your .IMG files from your exact phone for future use as well. You then want to click on the Fastboot Visualization tab and then click on Partitions.
10) Once under the partitions tab here, you will want to start flashing your .IMG files to the partitions. it should take you around 10 to 15 mins total to finish flashing everything.
11) Once your finished flashing you want to do a quick Terminal and do a FASTBOOT -W and then Fastboot Reboot and watch your phone start working again.
FEEL FREE TO LEAVE ANY COMMENTS SUGGESTIONS ON WHAT COULD HAVE BEEN BETTER OR IF IT'S NOT ENOUGH DETAIL. I TAKE CONSTRUCTIVE CRITICISM WITH A GRAIN OF SALT. THIS WAS MY FIRST GUIDE I EVER PUT TOGETHER. LOL THIS GUIDE TOOK ME LONGER THAN IT DID UNBRICKING MY PHONE.
BELOW YOU WILL FIND .IMG FILES FOR ONEPLUS NORD N200 DE2118
Click to expand...
Click to collapse
I still do not understand what I have to flash to get an OS back on this device. All I have is fastboot... soft bricked. I have de2117 ( "best buy" model). Reading all these instructions and I am still very confused