hi guys i need your help..I've flashed last flyme 5.0.10.0 G via TWRP but iìve forgot to replace in update.zip the recovery and bootloader img. Now my phone not have nothing recovery and the bootloader is again lock...Solutions?
You have to unlock the bootloader again. You can flash that daily update that let you unlock the bootloader from Flyme's file system explorer, IIRC.
Solitario88 said:
hi guys i need your help..I've flashed last flyme 5.0.10.0 G via TWRP but iìve forgot to replace in update.zip the recovery and bootloader img. Now my phone not have nothing recovery and the bootloader is again lock...Solutions?
Click to expand...
Click to collapse
No solutions exist :crying:
Really?? And the flash tool??
Inviato dal mio PRO 5 utilizzando Tapatalk
I am in the same situation. Unfortunately there is no way to get the token signed which is required to unlock the bootloader.
Sent from my SM-920F using Tapatalk
Solitario88 said:
Really?? And the flash tool??
Inviato dal mio PRO 5 utilizzando Tapatalk
Click to expand...
Click to collapse
With a Meizu phone, forgetting 1 or more steps in a modding procedure is equal to trash the phone. I'm really sorry
crime_of_heart said:
I am in the same situation. Unfortunately there is no way to get the token signed which is required to unlock the bootloader.
Sent from my SM-920F using Tapatalk
Click to expand...
Click to collapse
And for original recovery? This is big problem... However about the flash tool?? Work or not?
Inviato dal mio PRO 5 utilizzando Tapatalk
What I don't understand is how the recovery becomes corrupt.
If you flash the update.zip, the following gets updated:
bootloader on [sdb] [unlockable ONLY if on the 5.6.1.19.daily rom]
ldfw on [ldfw]
dtb on [dtb]
logo.bin on [bootlogo]
boot.img on [bootimg]
recovery.img on [recovery]
system.new.dat on [system]
The only way i see is if you flash a non-signed recovery after you flash the update.zip and then reboot.
Is this correct or do people have other experiences ?
st0rm77 said:
What I don't understand is how the recovery becomes corrupt.
If you flash the update.zip, the following gets updated:
bootloader on [sdb] [unlockable ONLY if on the 5.6.1.19.daily rom]
ldfw on [ldfw]
dtb on [dtb]
logo.bin on [bootlogo]
boot.img on [bootimg]
recovery.img on [recovery]
system.new.dat on [system]
The only way i see is if you flash a non-signed recovery after you flash the update.zip and then reboot.
Is this correct or do people have other experiences ?
Click to expand...
Click to collapse
Or get a tool to sign the recovery imge with correct key. The multitool exists but the key is missing to sign the file.
Sent from my SM-920F using Tapatalk
Solitario88 said:
Really?? And the flash tool??
Inviato dal mio PRO 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Sign up (link)
the only way i see, u cannot lose recovery and get locked bl with normal update file, only if u deleted recovery and bl files from zip and forgot to put there your's. This is happens because before update, phone is deleting everything by the command in update.zip, in this case recovery gonna be deleted, but not reinstalled again. This is my opinion how it's gonna be.
that is impossible that you have no recovery in your phone.Try to enter the recovery by push the volume button.If it is not work,then try to enter the bootloader with the volume button and unlock the bootloader again.But in fact i am not sure if a special situation happend on your phone because this brand of phone is extremely weird.
afraid to loose recovery
st0rm77 said:
What I don't understand is how the recovery becomes corrupt.
If you flash the update.zip, the following gets updated:
bootloader on [sdb] [unlockable ONLY if on the 5.6.1.19.daily rom]
ldfw on [ldfw]
dtb on [dtb]
logo.bin on [bootlogo]
boot.img on [bootimg]
recovery.img on [recovery]
system.new.dat on [system]
The only way i see is if you flash a non-signed recovery after you flash the update.zip and then reboot.
Is this correct or do people have other experiences ?
Click to expand...
Click to collapse
Hello
I am afraid to loose recovery while flashing a new sock ROM...
In a stock image, should we really remove recovery.img OR replace it with your TWRP_3.0_m86_patched_st0rm77.img file to be sure to keep TWRP running ?
As said p82maarj
in https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
Isn't it simplier to perform those steps in TWRP :
flash rom zip, flash unlocked bootloader zip and flash TWRP zip
Click to expand...
Click to collapse
?
Thanks in advance for your input.
EDIT : indeed all is well working smoothly without modifying the ROM if you flash the 3 zips in that order.
patco06 said:
Hello
I am afraid to loose recovery while flashing a new sock ROM...
In a stock image, should we really remove recovery.img OR replace it with your TWRP_3.0_m86_patched_st0rm77.img file to be sure to keep TWRP running ?
As said p82maarj
in https://forum.xda-developers.com/meizu-pro-5/development/recovery-twrp3-0m86patchedst0rm77-t3469296
Isn't it simplier to perform those steps in TWRP :
?
Thanks in advance for your input.
EDIT : indeed all is well working smoothly without modifying the ROM if you flash the 3 zips in that order.
Click to expand...
Click to collapse
IDK the best approach but If you replace recovery and end up with a locked boot loader twrp wont be booted. This can soft-brick your phone, esp if the stock image wont boot either.
Thankfully there is this ugly guide on here to restore the unlocked bootloader + recovery. Ugly because you have to install a 32 bit windows in vmware player, fully update that installation and then you can use the tools there to repair your phone.
Related
I made it (OTA US Global) NO REPACK / OFFICIAL OTA
The bootloader is the problem (you need to flash the 4.3 boot loader)
Warining: (thx to @Entropy512)
Flashing bootloaders is a dangerous operation - it's one of the few ways you can hardbrick your device.
THIS IS TEMPORAL , you take the risk.
The steps:
Flash bootloader.img of android 4.3 (us global) / mfastboot.exe flash motoboot motoboot.img
4.3 bootloader -> http://www.mediafire.com/download/7i75m96r692rp78/bootloader-downgrade.zip
Flash the Custom Recovery / mfastboot.exe flash recovery recovery.img
Install superSU zip from the recovery
You can come back to 4.4 Bootloader / But you can't use the recovery
4.4 bootloader -> http://www.mediafire.com/download/wd4rhkqbo7797r0/bootloader4.4.zip
Minimal Adb : https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
mfastboot : http://www.4shared.com/zip/ijBhKGjk/mfastboot-v2.html?cau2=403tNull&ua=WINDOWS
Firmware US GLOBAL : http://sbf.droid-developers.org/download.php?device=14&file=127
Thx to fibblesan who gave me the idea
(Sorry for my bad english)
THIS METHOD IS NO LONGER NECESSARY
just flash CWM and SuperSU -> http://forum.xda-developers.com/showthread.php?t=2563599
Enviado desde mi XT1032 mediante Tapatalk
With the 4.3 boatloader, you can actually flash the recovery permanently instead of just booting from it. If you want. But yeah. I did this with the official 4.4 OTA and it worked perfectly. Thanks for doing a guide for others.
Sent from my XT1034 using Tapatalk
Do anyone have the 4.3 stock recovery or where do we get out from?
Sent from my XT1034 using Tapatalk
I tried but I'm getting a boot failed error in the bootloader screen
Enviado desde mi XT1032 mediante Tapatalk
Thanks this method works great got cwm and root on official kitkat ota. I flashed the US motoboot.img, then flashed cwm recovery, and finally flashed su. All is working great for me!
Attached is the bootloader from 4.3 and mfastboot. You will want to flash the bootloader using mfastboot instead of just regular fastboot. You need to make sure you have ADB setup.
Just extract these files to the folder where ADB is located, then open a command prompt to that same folder and run this command:
mfastboot flash motoboot motoboot.img
Click to expand...
Click to collapse
Then you can flash CWM recovery and it will work just fine for you. The first time you reboot from CWM, it will ask if you want to disable the stock recovery flash. Make sure you chose "yes".
jmoore4294 said:
Attached is the bootloader from 4.3 and mfastboot. You will want to flash the bootloader using mfastboot instead of just regular fastboot. You need to make sure you have ADB setup.
Just extract these files to the folder where ADB is located, then open a command prompt to that same folder and run this command:
Then you can flash CWM recovery and it will work just fine for you. The first time you reboot from CWM, it will ask if you want to disable the stock recovery flash. Make sure you chose "yes".
Click to expand...
Click to collapse
Thanks for the boot.img
... To gain root, can we download and install Super Su from the play store...or do we have to flash a version of su via cwm?
Sent from my XT1034 using Tapatalk
Worked for me too. Thanks!
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash recovery recovery.img
[select recovery on phone]
You'll need to flash supersu in CWM.
Sent from my XT1034 using Tapatalk
jmoore4294 said:
You'll need to flash supersu in CWM.
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
Ok...I'll see if I can find it...
Sent from my XT1034 using Tapatalk
dupe post
What happens if you flash 4.3's bootloader, then say you want to flash 4.4 bootloader again?
I'll go a week without root, and come back if I miss it so see you all in a week!
Sent from my XT1034 using Tapatalk
SamsungAdmire said:
What happens if you flash 4.3's bootloader, then say you want to flash 4.4 bootloader again?
Click to expand...
Click to collapse
You can just flash the 4.4 bootloader after. Unless we find some major issues running kitkat with the older bootloader then it's probably best to stay with the older one as you cannot use any custom recovery with the newer bootloader.
Here are the bootloaders:
4.3 http://www.mediafire.com/download/7i75m96r692rp78/bootloader-downgrade.zip
4.4 http://www.mediafire.com/download/wd4rhkqbo7797r0/bootloader4.4.zip
Both zips contain the moto fastboot which you need to use to flash them to your device.
Cooptx said:
I'll go a week without root, and come back if I miss it so see you all in a week!
Sent from my XT1034 using Tapatalk
Click to expand...
Click to collapse
I missed it on the very first boot. No root, no Titanium Restore and no Gravity Box. Reason enough to do the easy step outlined here, worked just fine.
Can this be used for United Kingdom Moto G too?
nupi said:
I missed it on the very first boot. No root, no Titanium Restore and no Gravity Box. Reason enough to do the easy step outlined here, worked just fine.
Click to expand...
Click to collapse
Do I have to unlock bootloader first? I am lost D: mfastboot commands are not working, it is just sitting at [waiting for device]
flibblesan said:
You can just flash the 4.4 bootloader after. Unless we find some major issues running kitkat with the older bootloader then it's probably best to stay with the older one as you cannot use any custom recovery with the newer bootloader.
Here are the bootloaders:
4.3 http://www.mediafire.com/download/7i75m96r692rp78/bootloader-downgrade.zip
4.4 http://www.mediafire.com/download/wd4rhkqbo7797r0/bootloader4.4.zip
Both zips contain the moto fastboot which you need to use to flash them to your device.
Click to expand...
Click to collapse
Thx for the 4.4 bootloader
Updating...
Enviado desde mi XT1032 mediante Tapatalk
Cooptx said:
Do I have to unlock bootloader first? I am lost D: mfastboot commands are not working, it is just sitting at [waiting for device]
Click to expand...
Click to collapse
Answer yes. And there is no way to get out of it without voiding warranty Oh well, maybe in a year
oasoas014 said:
I made it (OTA US Global) NO REPACK / OFFICIAL OTA
The bootloader is the problem (you need to flash the 4.3 boot loader)
The steps:
Flash bootloader.img of android 4.3 (us global) / mfastboot.exe flash motoboot motoboot.img
4.3 bootloader -> http://www.mediafire.com/download/7i75m96r692rp78/bootloader-downgrade.zip
Flash the Custom Recovery / mfastboot.exe flash recovery recovery.img
Install superSU zip from the recovery
You can come back to 4.4 Bootloader / But you can't use the recovery
4.4 bootloader -> http://www.mediafire.com/download/wd4rhkqbo7797r0/bootloader4.4.zip
Minimal Adb : https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
mfastboot : http://www.4shared.com/zip/ijBhKGjk/mfastboot-v2.html?cau2=403tNull&ua=WINDOWS
Firmware US GLOBAL : http://sbf.droid-developers.org/download.php?device=14&file=127
Thx to fibblesan who gave me the idea
(Sorry for my bad english)
Enviado desde mi XT1032 mediante Tapatalk
Click to expand...
Click to collapse
when you talk about cannot use recovery, do you mean that you will only be on the stock recovery instead of the custom recovery you installed? and what superuser zip and custom recovery to use?
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
It has a fasboot mode, for now I can only access it via adb (adb reboot bootloader). It shows a black screen with fastboot mode at the bottom.
It also has a stock recovery mode, shows 'no command' but can be activated by pressing power button.
After you've activated it:
Vol+ to select
Vol- navigate down
Power to go back
Adb No devices found , idk why my Laptop doesn't detect my desire 820s
wil try now just installed htc sync manager
okay it worked and i went to fastboot mode , when i give a cmd order it says waiting for device
eg..... fastboot oem info
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Nc.netcat said:
Same here
fastboot oem unlock
FAILED (remote: unknown command)
fastboot oem get_identifier_token
FAILED (remote: unknown command)
any idea ?
Click to expand...
Click to collapse
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
Mohamed Yaser said:
Is this real ? i really cant access boot loader , just the recovery with the no command screen
can you confirm ??
if so then what i think that this device is already dead
Click to expand...
Click to collapse
You are right, Mediatek HTC devices dont have bootloader. Infact mediatek htc phones can be flashed with SP Flash tool just like micromax phones. I know this is true for htc 816g.
sziraqui said:
Mediatek Htc devices do not need bootloader unlocking, you can flash anything from fastboot mode
.
Click to expand...
Click to collapse
hhmm
fastboot flash recovery recovery.img => partition 'recovery' not support flash
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
It works. How about flashing a RUU?
Gibz97 said:
It works. How about flashing a RUU?
Click to expand...
Click to collapse
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
sziraqui said:
Can mention on which device you have checked it, does it has locked bootloder (if exists)?
RUU in mediatek? i dont think mediatek phones have RUU, (try "fastboot oem rebootRUU" to check)
But if it does, you can extract rom.zip from the RUU THEN EXTRACT system.img, boot.img and recovery.img
Then keep copy this to your firmware folder (containg scatter file)
load scatter file
Uncheck everything except system,boot and recovery in sp flash tool
Click download and connect your powered off device to pc holding vol down
Click to expand...
Click to collapse
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Gibz97 said:
I've done that but the phone usually cannot boot into the system.
BTW I am on Kitkat 4.4.4 without Sense and I want to flash Lollipop 5.0.2 Sense 7.
The RUU is from a Taiwanese variant 820ys which runs Lollipop 5.0.2 and Sense 7 out of the box, same models(htc_a50ml_dtul)
The problem is that the Kitkat Firmware has smaller partitions compared to the lollipop one. An example is the Kitkat system partition which is about 1.4Gbs while Lollipop has about 4.9Gbs, so I cannot flash with the same scatter file.
So I edit the scatter file to inflate the partitions in order to accommodate the big Lollipop files (sytem.img,recovery.img and boot.img) and perform firmware upgrade.
What could be stopping it from booting? Is it due the fact that the Lollipop boot and recovery are verified? Thanks in advance
Screenshots for Kitkat and Lollipop firmware files below
Click to expand...
Click to collapse
well this question will take the thread off topic. I would request you to create a new thread regarding this issue under "q&a,help and troubleshooting". Chances of your problem getting solved are higher if you do so. I will post my views regarding your issue in that thread. And i apologize to OP, because i only started answering questions irrelevant to his thread.
i totally accept off topics if they are helpful
sziraqui said:
but flashing recovery with SP flash tool will work for sure.
1. Put your custom recovery in the firmware folder,
2. del stock recovery.img,
3. rename your custom recovery as recovery.img,
4. load scatter file,
5. uncheck everything except recovery
6. click download and then connect your powered off phone to pc while holding vol down
someone Please confirm if this works with 820s, without worrying about bootloader
Click to expand...
Click to collapse
Hi.
It worked, but pressing Vol UP, not down. Anyway i've installed Recovery but when i try to access it from bootloader the device stopped me tellig that is for Android developers. I think that is because at the top of bootloader screen it tell "LOCKED". Any solution?
htc desire 820 softbrick not connecting with fastboot
Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?
please help I can't buy another phone it's urgent...
p181153 said:
Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?
Click to expand...
Click to collapse
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.
@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?
haky 86 said:
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.
Click to expand...
Click to collapse
Tell me where I said you are responsible of bricks ? I followed the steps you described, If you don't want to help just don't say anything
neondragon1909 said:
@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?
Click to expand...
Click to collapse
This is I want to know. He don't said it but I tried to flash oreotwrp from nougat and it said partition error using recovery_ramdisk. And the nocheck didn't work, so I took another nocheck for this TWRP and put the update_package command and then this
I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.
haky 86 said:
I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.
Click to expand...
Click to collapse
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update
p181153 said:
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update
Click to expand...
Click to collapse
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
Thanks any detailled guides for that so I'll not make the things worst ?
neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use fastboot flash recovery recovery.img not recovery_ramdisk
neondragon1909 said:
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
Use fastboot flash recovery recovery.img not recovery_ramdisk
Click to expand...
Click to collapse
I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything
p181153 said:
I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything
Click to expand...
Click to collapse
Try unlocking bootloader again
neondragon1909 said:
Try unlocking bootloader again
Click to expand...
Click to collapse
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...
p181153 said:
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...
Click to expand...
Click to collapse
please help me can't restore my phone when I want to flash boot of a nougat firmware it say partition length error.....
when I want to flash recovery same...
I can't do anything I need my phone it's 3 days already I miss important calls...
This forum is called xda-developers but there are no developers or someone who really know how android works. I can't found anyone who can help me even on other forums. I have access to something which can save my phone but NOBODY know how to use it. How disapointing.
why
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
die.henrique said:
every time I do the procedure to install the gcam with temporary root, when uninstalling the magisk, my mi a1 gets stuck in the "no command" screen, I saw in several sites that this happens when the magisk does not make a backup correct boot.img, has anyone gone through this?
Click to expand...
Click to collapse
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
but will not this reset the device? can I flash the stock boot.img without erasing the data?
die.henrique said:
but will not this reset the device? can I flash the stock boot.img without erasing the data?
Click to expand...
Click to collapse
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
emiljano539 said:
Yes, but you can keep the data by selecting to flash only the system.
And you can also flash only the stock boot.img with command "fastboot flash boot boot.img"
Click to expand...
Click to collapse
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
die.henrique said:
Omg, thanks for the answers, just one more thing, the boot.img do I have to download from the internet or do a backup of my current device?
Click to expand...
Click to collapse
You should download the boot.img for mi a1 which corresponds with your update. For ex. boot.img of january rom.
device not found in adb fasboot after uninstall magisk
emiljano539 said:
Mine too, had to flash the original rom with mi flash. Get the og boot.img then when you're in fastboot mode type : "fastboot boot boot.img" the boot.img needs to be the stock unpatched boot image
Click to expand...
Click to collapse
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
caan90 said:
[HELP] after uninstalling magisk, my mi a2 stuck at no command and does not found in adb (device not listed in fastboot). what should i do? i want to flashboot.
Click to expand...
Click to collapse
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
emiljano539 said:
Because you have lost the stock boot.img. find the stock boot img of your patch then flash it via fastboot directly
Click to expand...
Click to collapse
Thank you so much... it work.. my mi a2 just come back to life..
caan90 said:
Thank you so much... it work.. my mi a2 just come back to life..
Click to expand...
Click to collapse
I'm glad it worked. Make sure you leave a like in my comment if it was useful . Peace
my mi a2 is not detect in adb and in fastboot too what can i do
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery