So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
virusdunil said:
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
Click to expand...
Click to collapse
I can have the phone in fastboot and run adb reboot bootloader and it says no devices found although the huawei HiSuite can detect the device being plugged in as it loads up when I plug the phone in
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
virusdunil said:
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
Click to expand...
Click to collapse
Not going to lie I am slightly out of my depth here, could you explain that further? I'm assuming I need to download an update.app but I have no idea where from or extracting the kernel from it
thanks
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
virusdunil said:
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
Click to expand...
Click to collapse
That Didn't work i just got:
C:\Users\jamie\Desktop\platform-tools>fastboot flash recovery KERNEL.img
target reported max download size of 471859200 bytes
sending 'recovery' (24576 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.537s
im assuming its due to the bootloader not being unlocked. and in the meantime im running a deepscan on my hard drive to see if I can recover my unlock code which was lost when cloning to a new ssd. It has a few hour left though
you have it wrong...
its fastboot flash kernel KERNEL.img
virusdunil said:
you have it wrong...
its fastboot flash kernel KERNEL.img
Click to expand...
Click to collapse
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
virusdunil said:
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
Click to expand...
Click to collapse
I have android studio, how do I flash the img with it?
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
virusdunil said:
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
Click to expand...
Click to collapse
exactly the same :
C:\Users\jamie\AppData\Local\Android\Sdk\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.533s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.542s
Is it maybe worth seeing if I can get the serial number product emei and product id without the os?
Jyndon said:
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
Click to expand...
Click to collapse
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
kwaichang said:
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
Click to expand...
Click to collapse
I don't know that I do have access though as the device doesn't appear in adb devices list and the bootlaoder is locked.
Although I think I may have found a way of flashing a new bios without bootloader by using the huawei recovery installation.
The default one that uses wifi obviously doent work because its crap but while the device is off I can hold vol+ vol- and power and it loads into an installation screen that shows installation failed but i found that it maybe possible to flash the bios this way by putting the update.app onto the sd card. However the problem I'm having is that windows says the file is too big to copy and unzipping it inside of the sd card doesnt work either. Any ideas as to how I might be able to do it like this? (similar to this: https://android.stackexchange.com/q...are-installation-failed-error-when-booting-up and this too https://forum.xda-developers.com/p9-plus/help/software-install-failed-updating-p9-t3587676)
SOLVED
I managed to get most of the information to unlock the bootloader from the box which I luckily kept, then for the product ID I used https://imei24.com/warranty_info/Huawei/865545034273084/ and it worked perfectly!
Bootloader unlocked and then I used the common HWOTA to rebrand it back to its original firmware.
Thanks to those who helped.
Jyndon said:
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Click to expand...
Click to collapse
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
I know this is late but none the less, using the emei code I was able to request my code to unlock the bootloader through hwota. You cannot request this code anymore a way so you have to pay for dc unlocker which can rip the unlock code from the device.
petr.hybler said:
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
Click to expand...
Click to collapse
Is your bootloader unlocked?
If not you have your bootloader unlock code?
If not then you will need to pay for some software to get that code.
From there you can unlock the bootloader and use adb/fastboot again
Related
Hi there! So, I unlocked my bootloader yesterday and I've been trying to install a custom rom, no luck at all, it doesn't boot. It just stays in a bootloop. I think that's because I wiped the system and data instead of just wiping data then performing a factory reset, how it told me in the installation guide. Now, I have a european EVA-L09 with a unlocked bootloader and TWRP installed. What can i do to get it boot up? Thanks in advance
Try with HWOTA by installing the same stock ROM you had before messing up
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Btw, Huawei portal for Bootloader codes was down for days - was it up now again or you paid for DC Unlocker
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
zgfg said:
Try with HWOTA by installing the same stock ROM you had before messing up
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Btw, Huawei portal for Bootloader codes was down for days - was it up now again or you paid for DC Unlocker
Click to expand...
Click to collapse
I paid for DC Unlocker. I'll try it out. Ummm, I bought mine from UK, what version should I get? I had the latest EMUI 5.0.1 (Naugat 7.0) Stock ROM. It was my mistake that I didn't backed it up, had no storage left on my SD Card... Stupid me
fler_tb said:
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
Click to expand...
Click to collapse
Hi there! I'll try it out!
fler_tb said:
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
Click to expand...
Click to collapse
Code:
C:\Users\Whiskey\Desktop>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (449861 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 20.379s
well, this is what happens...
BlazedMC said:
Code:
C:\Users\Whiskey\Desktop>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (449861 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 20.379s
well, this is what happens...
Click to expand...
Click to collapse
Sorry for late answer. Maybe your bootloader is locked so you can't direct flash it trough fastboot...?!
fler_tb said:
Sorry for late answer. Maybe your bootloader is locked so you can't direct flash it trough fastboot...?!
Click to expand...
Click to collapse
I solved it a long time ago, the same day. Thanks anyway!
BlazedMC said:
I solved it a long time ago, the same day. Thanks anyway!
Click to expand...
Click to collapse
How did you??
pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
babyshark1983 said:
pls help my phone brick not start stuck on your device is booting now...
please any help
dlord not work
Click to expand...
Click to collapse
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
zgfg said:
How can be helped if not provided which ROM you had (full build model, cust nunber), what you did (wrong), and such details - bootloader unlocked, TWRP installed, etc?
What is 'rescue' mode - you mean Recovery (or eRecovery)?
Click to expand...
Click to collapse
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
babyshark1983 said:
first hi
my phone is p9 eva-l19 nougat version 390
i have twrp but i flash new version of recovery 3.2.1.0 and it stuck
in twrp i wipe everything because the version was auto delete battery and usage data and another options
my phone was rooted and unlocked
so now i cant do anything i try lot of thing fastboot and srktools
and in both give me( failed (remote command not allowed)
Click to expand...
Click to collapse
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
zgfg said:
MM, N and O (corresponding EMUI version) each has different organization of partitions (O even differently named two partitions) and different encryption of Data and Internal mem
Flashing wrong TWRP causes brick (even worse if you then proceeded by DLOAD or something with that inappropriate TWRP
Few users already reported similar bricks here but nobody reads on time ;(
TWRP for Huawei directly from their site is (maybe) good for Huawei MM but not for N or O
Use only 3.1.1-1 'endorsed' for Huawei Nougat !!! from
https://forum.xda-developers.com/p9/development/twrp-t3565703
or even better, little newer/extended version from
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
Try if you can unbrick by flashing proper TWRP fron Fastboot and by DLOAD afterwards.
If you need, download corresponding (must be FullOTA) update.zip from Firmware Finder (it's possible from PC since your P9 does not boot or use any other Android phone), unzip, use Huawei Update Extractor (PC app, search on XDA for) to extract Recovery.img
If still not working, use HWOTA method from
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
or HWOTA7 from (find and download appropriate ZIPs from Huawei Finder, do not use ones and don't proceed by rebranding to AL10 until you fix as L19 !!! and/or if you don't want to use Chinese Oreo)
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or eventually you can try by HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
Click to expand...
Click to collapse
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
babyshark1983 said:
thx i will try
i was have n version.
C:\Users\mich\Desktop\Huawei Fastboot Flasher GSM HELP\adb\adb>fastboot flash re
covery RECOVERY.IMG
target reported max download size of 471859200 bytes
sending 'recovery' (35732 KB)...
OKAY [ 1.025s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 1.035s
not work from twrp and from huawei official
Click to expand...
Click to collapse
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
zgfg said:
In the Fastboot mode, are both Phone (=Bootloader) and FRP red, showing Unlocked?
If not, you can not flash anything
Click to expand...
Click to collapse
hi just bootloader unlock
frp locked
thx
babyshark1983 said:
hi just bootloader unlock
frp locked
thx
Click to expand...
Click to collapse
That is the problem - to flash you need both Bootloader and FRP unlocked but with wrong TWRP or so, you locked FRP
To unlock FRP you would need to boot to System and check OEM Unlock under Developer Options - but if you ccannot boot to System, it is bricked
IMO, no other way now but to buy 15 EUR credit for DC Phoenix, they can unlock (TG, I didn't need to use DC Phoenix , hence cannot help about, you can ask them over their page)
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
You can also search here on XDA, there were other users who un-bricked by their tool, if I recall there was also somebody with a similar brick: FRP locked but cannot boot to System
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
I need help :'(
I had that.
Phone was completely dead, needed a new board.
chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!
You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.
benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??
How to unlock the OEM when I could not activate the developer options, because the device does not turn on?
It is not possible to flash a ROM because it says: flashing_locked
In short, the device only goes to Fastboot.
------------------
I manage to do the following. I did a temporary boot via Fastboot.
fastboot boot "Original ROM file or Boot.img Patched with Root"
More information I have I will be putting it here.
An application to use adb and fastboot without a computer.
Bugjaeger or Bugjaeger Premium
ps: requires otg support on the device you are going to control.
I'm out of results at the moment, I couldn't recover my Moto G7 Plus.
I've already lost almost 100% of the hopes that I can manage.
I think I will have to send it to a Motorola Official Technician or buy another device, as it is not worth me to have it fixed. because the stores are far from my city.
I was able to start the device, but I still can't activate oem unlock.
it is already a progress.
I used a modified boot.img and started the device using:
fastboot boot boot.img
the problem I have to use this command to turn on the device without...
if i get more news i will talk here.
Anrito Kun said:
if i get more news i will talk here.
Click to expand...
Click to collapse
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
------------------
I don't know how to send files here.
I have no new results, but I will try to send the boot.img that could connect the device.
wfsmnt said:
Did you manage to solve it, or did you have any progress?
Could you send the boot.img file you used?
Click to expand...
Click to collapse
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
I haven't been able to do anything new yet.
I think that only specialist technicians will know how to fix the device.
Anrito Kun said:
Boot.img: https://mirrorbits.lineageos.org/recovery/lake/20201222/lineage-17.1-20201222-recovery-lake.img
Click to expand...
Click to collapse
------------------
After downloading use the command: fastboot boot file.img
This managed to start the device, but I couldn't get into Recovery ... At least I couldn't.
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Anrito Kun said:
Does anyone know how to patch a boot.img file? most have to sign almost the same kernel signature.
Click to expand...
Click to collapse
------------------
I think it may be possible to join TWRP with the system's Boot.img. As if it were a magched patched, only instead of magisk it is TWRP.
delete
delete
poog said:
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....tried 2 things that fail
C:\adb>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
(bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote failure)
finished. total time: 0.510s
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
Click to expand...
Click to collapse
------------------
You're using the Moto G7 plus, right?
the command has to be this to use the file:
fastboot boot "file name".img
poog said:
I can boot to fastboot, but I cannot flash anything. I cannot get a proper return with "fastboot devices"
I cannot get RSD LITE to recognize my device. (win 10). I have read to try win7
Device Manager (windows 10) can only show the device as "Motorola ADB Device". I have not figured out how to force it to show as Qualcom ..............if that will make a difference or not. qualcom drivers are installed.
Before I messed it up I was able to load the device as a qualcom device on the right port and blankflashed after I hardbricked with nothing on screen.
Ability to boot to fastboot but not flash anything seems it is effectively dead for now.
Click to expand...
Click to collapse
------------------
There is no point in trying Flash on the device when the device is Flashing Locked.
My phone is in the same situation after I tried to re-lock the bootloader. Please do follow up on your progress.
hey I have the same problem have you found a solution?
Unfortunately, no.
I managed to brick a moto G7 plus to the point of not being able to recover from it (locked bootloader, no twrp, boots to fastboot)
I wanted to go back to 100% stock but failed badly.
My device is odd one. RETLA stream with XT1965-T hardware. Lenovo Rescue apparently don't work on these devices.
1) I flashed stock RETLA latest rom from Lolinet using a flash.bat I made
2) worked and booted fine.....twrp was still intact
3) I did factory reset when booted in.
4) To relock I flashed boot.img and sent lock command a few times
5) Bootloader is now locked but only boots to fastboot and get (YOUR DEVICE HAS LOADED A DIFFERENT OPERATING SYSTEM.
6) I cannot unlock with code because adb says says I need developer option etc.
To repeat: this is BOOTLOADER LOCKED, JUST BOOTS TO FASTBOOT and gives "your device loaded a different operating system) which is not the issue and I expected that.
Bankflash didn't do anything. I mostly get oermission denied with mostly flashing anythiine else.
Any suggestions on how to just get this thing at least bootable again to use?
Thanks.
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Anrito Kun said:
I have the same problem, but I found a way to at least start the device.
I gave "fastboot boot file.img" with a boot.img patched via Magisk.
But then it stopped working, so I changed the boot.img file to LineageOS.
Click to expand...
Click to collapse
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Anrito Kun said:
------------------
I was only able to do what is here: https://forum.xda-developers.com/t/...oem-at-developer-option-moto-g7-plus.4201169/
Click to expand...
Click to collapse
Thanks for replying to my post. I tried your patched boot.img but when I try to flash it I get " (bootloader) fllash permission denied "
renamed it to boot.img and then....
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (21845 KB)...
OKAY [ 0.465s]
writing 'boot'...
(bootloader) flash permission denied
FAILED (remote failure)
finished. total time: 0.479s
PROBLEM SOLVED. See my post.
https://forum.xda-developers.com/t/moto-g7-plus-no-service.4201229/post-84335207