Related
Hey,
I am running the exodus rom on my oneplus 3 and after todays update I got a huge problem. My screen fails to wake up, the phone works normal I think but the screen is just black..
How do I solve a problem like this?
I have tried turning it on and off again, it did not work
Fast And Pro said:
Hey,
I am running the exodus rom on my oneplus 3 and after todays update I got a huge problem. My screen fails to wake up, the phone works normal I think but the screen is just black..
How do I solve a problem like this?
I have tried turning it on and off again, it did not work
Click to expand...
Click to collapse
dirty flash?
may be clean flash will help
JumboMan said:
dirty flash?
may be clean flash will help
Click to expand...
Click to collapse
Idk what happend
but the screen works again but my phone is now bricked and the usual guides to unbrick do not work.
This is the status of my 1+3
Bootloader: unlocked and I can boot in the bootloader
my device is recognized by my pc
I cannot enter TWRP and I cant flash TWRP.
When I try to flash it CMD says that its flashed but I still cant boot in twrp, I get a random screen with md5 checksum and some fails.
Can someone help me?
Fast And Pro said:
Idk what happend
but the screen works again but my phone is now bricked and the usual guides to unbrick do not work.
This is the status of my 1+3
Bootloader: unlocked and I can boot in the bootloader
my device is recognized by my pc
I cannot enter TWRP and I cant flash TWRP.
When I try to flash it CMD says that its flashed but I still cant boot in twrp, I get a random screen with md5 checksum and some fails.
Can someone help me?
Click to expand...
Click to collapse
I don't have answer for question.
it looks like you have some serious problem with your phone.
may be some experienced user will help you.
I think you should approach Naman bhalla as he made guide to unbrick so he may know in detail
JumboMan said:
I don't have answer for question.
it looks like you have some serious problem with your phone.
may be some experienced user will help you.
I think you should approach Naman bhalla as he made guide to unbrick so he may know in detail
Click to expand...
Click to collapse
I found a fix on the forum and this explained what my problem was
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Fast And Pro said:
I found a fix on the forum and this explained what my problem was
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Click to expand...
Click to collapse
Its good.
Self help is best help
You may find that you need to return to stock/locked bootloader for various reasons. You can find how to do this by digging throughout various threads on this forum. decided to simplify things and bring it together in a single thread. After restoring you will be able to do OTA updates as well.
FLASHING FACTORY 5.8.019S
STEP 1: Download the backup
-- Source Thread: https://forum.xda-developers.com/le-pro3/how-to/le-pro-3-lex727-twrp-backup-eui-5-8-019s-t3504761
-- FILE: https://drive.google.com/file/d/0B5xyvHc4wgEVWHFKMWZqLWEyTTg/view?usp=sharing
Note: There is a TWRP backup for 20s currently on this forum. I do not recommend using it. Many have had issues booting after restoring it (me included).
STEP 2: Setup TWRP Backup Directory
If you download it to your PC use adb to push it to your device. You should have an existing directory within /sdcard/TWRP/BACKUPS/ that holds your backups. I believe the directory is your device id.
If the directory does not exist, you need to get the info from your device.
Code:
Run adb devices
It will be the hash listed by your device. Make a directory in TWRP/BACKUPS/ with the device id. Mine is "6293eaef".
For example, any backups that I want to restore to my device from TWRP need to be located in a sub-directory within: /sdcard/TWRP/BACKUPS/6293eaef/
At that point you should have the directory you need to copy the backup into.
STEP 2: Copy the Backup (originally named TWRP.zip) to /sdcard/TWRP/BACKUPS/6293eaef/stock
Do the following if you downloaded it to your computer:
Code:
adb push TWRP.zip /sdcard/TWRP/BACKUPS/DEVICE_ID/stock/
adb shell
cd /sdcard/TWRP/BACKUPS/DEVICE_ID/stock/
unzip TWRP.zip
If you downloaded to your device, you just need to move the zip file to the TWRP backups directory and extract it.
STEP 3: Restore in TWRP
Boot into TWRP recovery (if not already there).
Code:
adb reboot recovery
OR
Code:
hold volume up and press power button
RESTORE the backup.
I selected everything. This will install default recovery and remove TWRP.
Do a FULL wipe AFTER flashing. Be sure to wipe the data partition to clear any encryption.
[OPTIONAL] RESTORE LOCKED BOOTLOADER X727
This should not be necessary for X720 devices because the bootloader comes unlocked. I would only suggest re-locking if you need to return your device for warranty support.
To lock the bootloader you need to flash emmc_appsboot.mbn and xbl.elf from an OTA
Step 1: Get 5.8.020s OTA
-- File: https://www.androidfilehost.com/?fid=457095661767124419
After downloading extract 5.8.020S_sta.zip.
Inside the firmware-update folder are 2 files: xbl.elf, and emmc_appsboot.mbn. You need to flash both of these files in the bootloader to relock it.
Step 2: Boot to fastboot
Code:
adb reboot bootloader
OR
Code:
From power off, hold volume down and then press the power button.
Step 3: Flash stock bootloader from OTA zip
Run the following commands while in the firmware-update folder you extracted from 5.8.020S_sta.zip
Code:
fastboot flash xbl xbl.elf
fastboot flash aboot emmc_appsboot.mbn
The bootloader is now locked again.
Run
Code:
fastboot reboot bootloader
and then
Code:
fastboot oem device-info
to verify.
NOTE: I found that after using this method to re-lock the bootloader I could no longer use the guide for persistent bootloader unlocking.
If you want to unlock the bootloader again later, you need to manually flash the emmc_appsboot.mbn from the file in this thread:
https://forum.xda-developers.com/le...7-model-persistent-bootloader-unlock-t3500388
FILE: https://www.androidfilehost.com/?fid=313042859668275431
I hope that some of you find this helpful. Please let me know if there is any additional information that I should add to this thread. I will update it as needed.
Cheers!
STEP 1
file in google drive not found
Sorry, the file you have requested does not exist.
Make sure that you have the correct URL and the file existed.
ajegile said:
STEP 1
file in google drive not found
Sorry, the file you have requested does not exist.
Make sure that you have the correct URL and the file existed.
Click to expand...
Click to collapse
Fixed! That's what I get for copy/pasting the text vs the actual URL.
Hi, sorry to bring up an old thread. I plan to restore my leeco (US version ) running lineage back to stock. Will this method still work?
neozengar said:
Hi, sorry to bring up an old thread. I plan to restore my leeco (US version ) running lineage back to stock. Will this method still work?
Click to expand...
Click to collapse
Yes, this method will still work. It should also work for restoring to newer versions of stock (if needed).
Thank you so much. I notice the boot loader file is for le1. Are they same as that for Le eco pro 3?
neozengar said:
Thank you so much. I notice the boot loader file is for le1. Are they same as that for Le eco pro 3?
Click to expand...
Click to collapse
Yes
Will this work with Lineage 14.1?
Cuvillier said:
Will this work with Lineage 14.1?
Click to expand...
Click to collapse
This will take you back to stock regardless of what ROM you are currently running.
Ok, do you will update the tutorial with new files ? As newer firmware is now 23s version.
Cuvillier said:
Ok, do you will update the tutorial with new files ? As newer firmware is now 23s version.
Click to expand...
Click to collapse
Ill try to get some time to find links for the newer firmwares and update for those. We just had a new little one join the family so I'm pretty busy and tires nowadays .
Regardless, you can always update once you get back to stock in this guide.
Ok thank you.
This will work on x720 too ?
new small ota update for x720 just came out
Cuvillier said:
This will work on x720 too ?
Click to expand...
Click to collapse
Yes
slgooding said:
Yes
Click to expand...
Click to collapse
bootloader in x720 is already unlocked from LeEco
Hello folks,
I am using T.A.R.S. 21S EUI 5.8 USA version and TWRP 3.1.0
How do I return to stock? stock recovery, locked bootloader, and stock ROM so that I can get OTA updates?
I already tried:
https://forum.xda-developers.com/le-...oader-t3539513
I am able to restore successfully, but I am not able to install any OTA update with this and device is stuck with 19S only. I tried both local update and OTA update. UE boots into EUI recovery and says "Installation failed". I tried both 20S and 21S updates.
I think latest is 23S now.
Thanks
Brar
What device?
Hello. I want to return to stock x720 ROM. I won't to flash US version, so I need CN backup? Or how to do?
I flashed custom Recovery (TWRP), Kernel (BlackScreen), OS (AICP) and Root (Magiskv12). Should I flash trough recovery lastest official OS version?
I had to send the phone back to LeEco for repair, so needed to go stock.
Glad I found this post, thanks OP.
I tried the steps, all seemed to work okay, but now I am stuck at the leeco boot logo.
I can get to bootloader:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
I can also get to stock recovery, wipe data and update with update.zip
I think the phone is missing OS or something.
Please help.
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.
Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..
mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.
Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:
Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are
Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.
Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising
IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"
Hi folks,
I guess I did something really stupid. I flashed the Lineage OS 15.1 (unofficial) (https://bit.ly/2w1yVm4) directly on my HTC10 with Lineage OS 14.1 running via TWRP. I did this a few weeks ago already but figured out that there were too many bugs for me present.
Now I found out that my Home Button isn't working and that is obviously a known bug. I decided to go back to 14.1 but after flashing the phone doesn't recognize my SIM card.
Now I'm running through tons of threads and trying to find out what the next steps would be. A do have a full backup of the stock rom, which was created before the phone got rooted. The phone is S-on. Currently, I don't want to stay on 15.1 because of the bugs, which are still in it.
Is there an explanation what happens, if the 15.1 is being installed? Why is it different from switching between other roms?
Thank you in advance for kind help.
Cheers
Joe
chaos_since_78 said:
Hi folks,
I guess I did something really stupid. I flashed the Lineage OS 15.1 (unofficial) (https://bit.ly/2w1yVm4) directly on my HTC10 with Lineage OS 14.1 running via TWRP. I did this a few weeks ago already but figured out that there were too many bugs for me present.
Now I found out that my Home Button isn't working and that is obviously a known bug. I decided to go back to 14.1 but after flashing the phone doesn't recognize my SIM card.
Now I'm running through tons of threads and trying to find out what the next steps would be. A do have a full backup of the stock rom, which was created before the phone got rooted. The phone is S-on. Currently, I don't want to stay on 15.1 because of the bugs, which are still in it.
Is there an explanation what happens, if the 15.1 is being installed? Why is it different from switching between other roms?
Thank you in advance for kind help.
Cheers
Joe
Click to expand...
Click to collapse
Hint :
ERASE THE PERSIST PARTITION.
https://forum.xda-developers.com/ht...mei-signal-downgrade-oreo-8-0-t3748999/page21
Mr Hofs said:
Hint :
ERASE THE PERSIST PARTITION.
https://forum.xda-developers.com/ht...mei-signal-downgrade-oreo-8-0-t3748999/page21
Click to expand...
Click to collapse
Thank you for the hint. But for some reasons it worked perfectly when I did the same **** a few weeks ago when I tried 15.1 the first time. I reinstalled the 14.1 and everything was working perfectly.
What happend, when I installed the 15.1? Was the firmware somehow updated automatically? How do I find out, on which version my HTC10 is running right now?
Sorry for all this noobish questions. :angel:
Cheers
chaos_since_78 said:
Thank you for the hint. But for some reasons it worked perfectly when I did the same **** a few weeks ago when I tried 15.1 the first time. I reinstalled the 14.1 and everything was working perfectly.
What happend, when I installed the 15.1? Was the firmware somehow updated automatically? How do I find out, on which version my HTC10 is running right now?
Sorry for all this noobish questions. :angel:
Cheers
Click to expand...
Click to collapse
Boot to download mode and tell me what's written in the OS line ?
Hi Mr. Hofs,
This line says: OS-1.95.111.4
Is it possible to upgrade the firmware afterwards to an Oreo-compatible version without wiping the phone? Because the Lineage OS 15.1, which is currently running is fine so far, except these two anoying bugs Missing Loudspeaker and the Missing Homebutton (which might get solved with the correct firmware?)
One more question: The Hint above says: ERASE THE PERSIST PARTITION. The link shows on the first page of the thread a command for S-ON: "dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist", which duplicates a partion but does not delete it. At least that is what it does under Linux. So how do I delete this persistent partition?
chaos_since_78 said:
Hi Mr. Hofs,
This line says: OS-1.95.111.4
Is it possible to upgrade the firmware afterwards to an Oreo-compatible version without wiping the phone? Because the Lineage OS 15.1, which is currently running is fine so far, except these two anoying bugs Missing Loudspeaker and the Missing Homebutton (which might get solved with the correct firmware?)
One more question: The Hint above says: ERASE THE PERSIST PARTITION. The link shows on the first page of the thread a command for S-ON: "dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist", which duplicates a partion but does not delete it. At least that is what it does under Linux. So how do I delete this persistent partition?
Click to expand...
Click to collapse
That's a darn old firmware. My opinion :
Get the NOUGAT RUU (like 2.41.111) if you can locate it, Flash it (it will wipe the phone which is pretty much inevitable anyway) update to oreo and flash the latest Oreo based custom roms
Mr Hofs said:
That's a darn old firmware. My opinion :
Get the NOUGAT RUU (like 2.41.111) if you can locate it, Flash it (it will wipe the phone which is pretty much inevitable anyway) update to oreo and flash the latest Oreo based custom roms
Click to expand...
Click to collapse
Unfortunatelly, the phone does not find the 2PS6IMG.zip file, which is placed directly in the root of my SD-Card. It says "File /mnt/media_rw/ext_sd/2PS6IMG.zip not found". I have no idea whereelse I could store that file.
chaos_since_78 said:
Unfortunatelly, the phone does not find the 2PS6IMG.zip file, which is placed directly in the root of my SD-Card. It says "File /mnt/media_rw/ext_sd/2PS6IMG.zip not found". I have no idea whereelse I could store that file.
Click to expand...
Click to collapse
If the download mode is not detecting the zip file it's not named correctly because it should auto detect it. Make sure you didn't name it zip.zip
Mr Hofs said:
That's a darn old firmware. My opinion :
Get the NOUGAT RUU (like 2.41.111) if you can locate it, Flash it (it will wipe the phone which is pretty much inevitable anyway) update to oreo and flash the latest Oreo based custom roms
Click to expand...
Click to collapse
Mr Hofs said:
If the download mode is not detecting the zip file it's not named correctly because it should auto detect it. Make sure you didn't name it zip.zip
Click to expand...
Click to collapse
No, it's definitely named correctly.
chaos_since_78 said:
No, it's definitely named correctly.
Click to expand...
Click to collapse
Then it's the wrong RUU maybe? What file exactly do you want your download mode to flash?
The first file I tried: 2PS6IMG-RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5.zip
The second file I tried: 2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4_release_519849.zip
I renamed them accordingly to 2PS6IMG.zip and placed them in the root of my sd card.
What is kind of strange is that the HTC Sync tool does not recognize my phone when it's connected to a Win 10 PC. I can access the sd card and it's listet in the device manager under "portable devices" where it is supposed to be.
When I execute the RUU as exe the installer starts but closes after filling the status bar without any message.
I also executed this command earlier:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/persist
from the thread: https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
chaos_since_78 said:
The first file I tried: 2PS6IMG-RUU_PERFUME_WL_M60_SENSE80GP_NA_Gen_Unlock_1.53.617.5.zip
The second file I tried: 2PS6IMG_PERFUME_UHL_O80_SENSE90GP_MR_HTC_Europe_3.16.401.2_R4_release_519849.zip
I renamed them accordingly to 2PS6IMG.zip and placed them in the root of my sd card.
What is kind of strange is that the HTC Sync tool does not recognize my phone when it's connected to a Win 10 PC. I can access the sd card and it's listet in the device manager under "portable devices" where it is supposed to be.
When I execute the RUU as exe the installer starts but closes after filling the status bar without any message.
I also executed this command earlier:
from the thread: https://forum.xda-developers.com/htc-10/how-to/solution-imei-signal-downgrade-oreo-8-0-t3748999
Click to expand...
Click to collapse
As I've said.....you need a 2.41.111 RUU or similar to that, you are ABSOLUTELY flashing the wrong files. Please don't believe you can "just" flash any file out there.....oh dear.
I already told you to look for a 2.41.111 RUU out there. I didn't tell you to flash a 3.16.401 RUU neither a 1.53.617 RUU!!! No idea why you would come up with those files.
STOP immediately what you are doing until we found the correct RUU!!!
---------- Post added at 11:19 PM ---------- Previous post was at 11:13 PM ----------
Look what i got for you
https://www.androidfilehost.com/?fid=890129502657598118
Now try again......just this one, nothing else
Sorry, to bother you. I renamed it and moved the file to the sd card. Same sh*t again. But it still complains about "Failed to mount '/persist' (invalid argument)" I don't know if this has anything to do with all these problems.
chaos_since_78 said:
Sorry, to bother you. I renamed it and moved the file to the sd card. Same sh*t again. But it still complains about "Failed to mount '/persist' (invalid argument)" I don't know if this has anything to do with all these problems.
Click to expand...
Click to collapse
Can you perform the "erase persist" command first, reboot to bootloader, reboot back to download mode and try again.
Mr Hofs said:
Can you perform the "erase persist" command first, reboot to bootloader, reboot back to download mode and try again.
Click to expand...
Click to collapse
Thats a tricky one, isn't it? I followed the instructions given in this video: https://www.youtube.com/watch?time_continue=1&v=vJrNEsWVyOc Instead of the metioned RUU I used the one you pointed me at. At least I could get the "/persist" problem solved.
Now it still does not find the 2PS6IMG.zip file. However, the error message has changed just to "SD mounted OTG NOT MOUNTED File NOT FOUND".
But I'm not sure if the flashing of the RUU has really work. There were tons of error messages:
E:\HTC\platform-tools>fastboot flash zip E:\HTC\OUT_2PS6_2.41.111.42\2PS6IMG.zip
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 979745195 is not a multiple of the block size 4096
Sending sparse 'zip' 1/2 (1048572 KB) error: write_sparse_skip_chunk: don't care size 979745195 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 979745195 is not a multiple of the block size 4096
OKAY [ 37.875s]
Writing sparse 'zip' 1/2 (bootloader) HOSD CL#857212
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_V
(bootloader) 2J4b7
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
Finished. Total time: 57.082s
The phone showed the status bar and I could flash Lineage OS 14.1 afterwards. However, radio and the fingerprint are still not working.
I'm close to bite into this stupid thing. :crying:
Not quite sure what to think at this point.
1: if the RUU flashed properly it would have put the firmware to 2.41.111
2: if the RUU flashed properly it would have replaced TWRP with the stock recovery
This situation is a complete firmware / software incompatibility. The 1.95 firmware is a marshmallow firmware. Try to flash a rom if you can grab one.
I know that when you flash a oreo rom over a nougat firmware you lose radio and vice versa. Not sure what happens exactly when you do this with a marshmallow firmware. I can check back in about 2 days. I'm on holiday but the subject intrigues me.
Cheers.
Is there any other way to flash this RUU?
Okay... Got some news. I used TWRP 3.2.3.0 to restore my backup, which was created when I first got the phone and rooted it. This restore ended with only one error saying "the system partition cannot be mounted" or something like that. I tried to boot the phone but it only showed the HTC logo for an hour or so. I restartet the phone into recovery and flashed just for fun the LOS 14.1 and et voila, I got radio back and the home button/fingerprint sensor are working again.
Question is now: On which firmware am I running? Should I risk to upgrade it. How do I upgrade it and to which version. Aim would be to get on LOS 15.1. Is it worth all the trouble?
Anyway, THANKS A LOT for your patience. I have some experience in computers but these phones are such crap in this manner! Why can't that be more easy? I think it's made so complicate with purpose! Damn vendors!
chaos_since_78 said:
Okay... Got some news. I used TWRP 3.2.3.0 to restore my backup, which was created when I first got the phone and rooted it. This restore ended with only one error saying "the system partition cannot be mounted" or something like that. I tried to boot the phone but it only showed the HTC logo for an hour or so. I restartet the phone into recovery and flashed just for fun the LOS 14.1 and et voila, I got radio back and the home button/fingerprint sensor are working again.
Question is now: On which firmware am I running? Should I risk to upgrade it. How do I upgrade it and to which version. Aim would be to get on LOS 15.1. Is it worth all the trouble?
Anyway, THANKS A LOT for your patience. I have some experience in computers but these phones are such crap in this manner! Why can't that be more easy? I think it's made so complicate with purpose! Damn vendors!
Click to expand...
Click to collapse
The answer you need is already in this thread. Your actual firmware is in download mode - OS line. It's (since the last time) 1.95.111 so that means it's a t mobile firmware. That's why i handed you the 2.41.111 RUU, that RUU still should flash just fine with the SD card method. It's the most used method around.
Cheers.
Ok. I guess I celebrated a bit early. My TWRP is now 3.1.1.0 which is pretty old. I tried to flash the latest one 3.2.3.0 but in download mode fastboot doesn't recognize the phone anymore. It just says "waiting for any device". Maybe I should get drunk first before I proceed.
PC reboot help! Sorry!
Hello, my phone was stolen a year ago, and now the police recover it, so I do a factory reset, then login with my MI account but it keeps me asking a code to unlock after factory reset that I don't have, I try to log in also with my Gmail account linked to the device but still keeps me asking a code to unlock, I try with the xiaomi chat support but no luck, they told me that write an email to account-service at xiaomi.com , but I've been waiting a week and still no answer, so I hope someone helps me, thanks a lot
MaEdCo said:
Hello, my phone was stolen a year ago, and now the police recover it, so I do a factory reset, then login with my MI account but it keeps me asking a code to unlock after factory reset that I don't have, I try to log in also with my Gmail account linked to the device but still keeps me asking a code to unlock, I try with the xiaomi chat support but no luck, they told me that write an email to account-service at xiaomi.com , but I've been waiting a week and still no answer, so I hope someone helps me, thanks a lot
Click to expand...
Click to collapse
Search on XDA forum, how to flash persist partition. It will delete all mi accounts, etc.
Or do factory reset under recovery, thats easier.
Good luck.
drnightshadow said:
Search on XDA forum, how to flash persist partition. It will delete all mi accounts, etc.
Or do factory reset under recovery, thats easier.
Good luck.
Click to expand...
Click to collapse
So I go for this option, find how to do that, I have to download all the fastboot ROM MIU10 that is the version already installed on the phone, just the get the persist.img file of my phone, then install adb tools, then I get the "Press any key to shut down" error on fastboot, switch to USB 3.0 port to USB 2.0 port and run this bat file:
JerryLF said:
try this solution：
use a USB 2 port
create a new txt file,write code in the { } below
{
@Echo off
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
pause
}
then save this file and rename it as a .bat file
right click and run as administrator.
after that the issue can be fixed
Click to expand...
Click to collapse
then:
Code:
C:\WINDOWS\system32>fastboot erase persist.img
erasing 'persist.img'...
FAILED (remote: Anti-rollback check failed)
finished. total time: 0.004s
then
Code:
C:\WINDOWS\system32>fastboot getvar anti
anti: 4
finished. total time: 0.001s
then read this topic:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
Code:
C:\adb>fastboot flash antirbpass dummy.img
target reported max download size of 536870912 bytes
sending 'antirbpass' (8 KB)...
OKAY [ 0.004s]
writing 'antirbpass'...
OKAY [ 0.001s]
finished. total time: 0.009s
C:\adb>fastboot flash recovery twrp-3.2.3-2-whyred.img
target reported max download size of 536870912 bytes
sending 'recovery' (36616 KB)...
OKAY [ 0.797s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.802s
C:\adb>fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.003s
then try to unlock through MiFlash Utility and I get:
In the Developer options, go to the “Mi Unlock Status” and tap on “Add account and device” in order to authorize Xiaomi to unlock the device associated with the account.
Click to expand...
Click to collapse
but I can't do that 'cause it keeps me asking a code after factory reset
drnightshadow said:
Or do factory reset under recovery, thats easier.
Good luck.
Click to expand...
Click to collapse
could you please elaborate?
MaEdCo said:
So I go for this option, find how to do that, I have to download all the fastboot ROM MIU10 that is the version already installed on the phone, just the get the persist.img file of my phone, then install adb tools, then I get the "Press any key to shut down" error on fastboot, switch to USB 3.0 port to USB 2.0 port and run this bat file:
then:
then
then read this topic:
https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
then try to unlock through MiFlash Utility and I get: but I can't do that 'cause it keeps me asking a code after factory reset
could you please elaborate?
Click to expand...
Click to collapse
Try here
https://forum.xda-developers.com/re.../tutorial-fix-sensors-wifi-bluetooth-t3823622
drnightshadow said:
Try here
https://forum.xda-developers.com/re.../tutorial-fix-sensors-wifi-bluetooth-t3823622
Click to expand...
Click to collapse
I guess you did not read my whole post, I have the Bootloader locked and I do not have Twrp installed
so I can not do the steps you mention
MaEdCo said:
I guess you did not read my whole post, I have the Bootloader locked and I do not have Twrp installed
so I can not do the steps you mention
Click to expand...
Click to collapse
You can patch original MIUI fastboot ROM to overwrite persist partition... yeah you need to figure it out how to do it... unlock bootloader is a must to do so....
Ok, can you try to boot it in recovery mode (vol + POWER I think or try vol - and power) and than do factory reset...
Its a long time ago I have same problem (cca 2,5 years ago and it was my phone who locked me out)...
Ill check my repos on my PC tomorrow at work if I still have all the info how I did it. Solution I found is on XDA forums.
Stay tuned...ill try to help you out ....
drnightshadow said:
You can patch original MIUI fastboot ROM to overwrite persist partition... yeah you need to figure it out how to do it... unlock bootloader is a must to do so....
Click to expand...
Click to collapse
trust me I read a lot but still I do not how to unlock the bootloader
drnightshadow said:
Ok, can you try to boot it in recovery mode (vol + POWER I think or try vol - and power) and than do factory reset...
Click to expand...
Click to collapse
thats what I did on first place, boot on recovery mode (stock recovery) and then factory reset, wipe all data, and then the phone ask me for a code
drnightshadow said:
Its a long time ago I have same problem (cca 2,5 years ago and it was my phone who locked me out)...
Ill check my repos on my PC tomorrow at work if I still have all the info how I did it. Solution I found is on XDA forums.
Stay tuned...ill try to help you out ....
Click to expand...
Click to collapse
I hope so, thanks
MaEdCo said:
trust me I read a lot but still I do not how to unlock the bootloader
thats what I did on first place, boot on recovery mode (stock recovery) and then factory reset, wipe all data, and then the phone ask me for a code
I hope so, thanks
Click to expand...
Click to collapse
Ok I think I remembered something... you are saying bootloader is locked and for flashing you need code...
read this MIFLASH METOD
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
But that's just 1st step... download patch and ROM...In your case.. BE CAREFUL!!! DOWNLOAD ABR 4 ROMS ONLY!!!!
Edit 1: You can also read this ,I linked tread just because of video in 2nd post
https://forum.xda-developers.com/re...ccessful-redmi-note-5-pro-bypass-edl-t3843173
I'll remember... yes I will :laugh:
Edit 2: Than you need also patch xml to flash persist partition.. will find this to
damn it I'm old lool.
Edit 3: Ha ha I found it
https://forum.xda-developers.com/redmi-note-5-pro/how-to/remove-mi-account-redmi-phone-t4063921
that's 2nd step.
Now all you need to do is flashing MIUI ROM(patched/modified) with MI FLASH TOOL... I would recommend for 1st try only step 2 (last link) and if it wont work than combine 1st and 2nd step.
Good luck and stay safe.
drnightshadow said:
Ok I think I remembered something... you are saying bootloader is locked and for flashing you need code...
read this MIFLASH METOD
https://forum.xda-developers.com/redmi-note-5-pro/how-to/fix-arb-bricked-device-qfil-t3841780
But that's just 1st step... download patch and ROM...In your case.. BE CAREFUL!!! DOWNLOAD ABR 4 ROMS ONLY!!!!
Edit 1: You can also read this ,I linked tread just because of video in 2nd post
https://forum.xda-developers.com/re...ccessful-redmi-note-5-pro-bypass-edl-t3843173
I'll remember... yes I will :laugh:
Edit 2: Than you need also patch xml to flash persist partition.. will find this to
damn it I'm old lool.
Edit 3: Ha ha I found it
https://forum.xda-developers.com/redmi-note-5-pro/how-to/remove-mi-account-redmi-phone-t4063921
that's 2nd step.
Now all you need to do is flashing MIUI ROM(patched/modified) with MI FLASH TOOL... I would recommend for 1st try only step 2 (last link) and if it wont work than combine 1st and 2nd step.
Good luck and stay safe.
Click to expand...
Click to collapse
thanks a lot, but can not find the patch0.xml file on the post
I use the Mi Flash Tool 2018 and the 10.3 fastboot room, patched with edited rawprogram0.xml file and prog_emmc_firehose_Sdm660_ddr file
and I get this:
Flash xbl error
MaEdCo said:
thanks a lot, but can not find the patch0.xml file on the post
I use the Mi Flash Tool 2018 and the 10.3 fastboot room, patched with edited rawprogram0.xml file and prog_emmc_firehose_Sdm660_ddr file
and I get this:
Flash xbl error
Click to expand...
Click to collapse
Ohh, that bootloader error
Reset device and try again (try multiple times)
Yah I had some weird errors to. Sometimes its working on a 1st try and sometimes in a xxx times.
Just one question.. was your phone opened ? Check it really close... if it was than EDL mode was used.
Hope you'll solve this soon.
Edit 1: patch0.XML is for QFIL METHOD. I never used it.
Good luck!
drnightshadow said:
Ohh, that bootloader error
Reset device and try again (try multiple times)
Yah I had some weird errors to. Sometimes its working on a 1st try and sometimes in a xxx times.
Just one question.. was your phone opened ? Check it really close... if it was than EDL mode was used.
Hope you'll solve this soon.
Edit 1: patch0.XML is for QFIL METHOD. I never used it.
Good luck!
Click to expand...
Click to collapse
so I tried multiple times with Mi Flash Tool with no luck
si I tried with the QFIL Method, after a lot of reading, finally get to do the test point, and with this method I was able to flash the MIUI 9 rom with the persist.img file, but still the phone is locked:crying: so strange, I believe the old persist.img file was erased but it is not
MaEdCo said:
so I tried multiple times with Mi Flash Tool with no luck
si I tried with the QFIL Method, after a lot of reading, finally get to do the test point, and with this method I was able to flash the MIUI 9 rom with the persist.img file, but still the phone is locked:crying: so strange, I believe the old persist.img file was erased but it is not
Click to expand...
Click to collapse
So you used EDL MODE... did you flashed with MI Flasher? If you used QFIL it's just for reviving the phone.
Use patched(persist) ROM with MI Flasher and use EDL mode.
drnightshadow said:
So you used EDL MODE... did you flashed with MI Flasher? If you used QFIL it's just for reviving the phone.
Use patched(persist) ROM with MI Flasher and use EDL mode.
Click to expand...
Click to collapse
so if EDL Mode is do the test point, and wait the pc detects it as qualcom loader and some COM port yes
yes I also used Mi Flash Tool from 2018, yes I used the patched ROM with the persist.img file and still the same, the phone is locked, keeps me asking the MI Accounts credentials and then the unlock code after factory reset
edit found this
https://miui.blog/redmi-note-5/fix-arb-bricked-without-edl-whyred/
I think the MI account finally gets removed, and now it keeps me asking for a Google Account, I tried with all accounts I have but I keeps me for a propietary gmail account
MaEdCo said:
edit found this
https://miui.blog/redmi-note-5/fix-arb-bricked-without-edl-whyred/
I think the MI account finally gets removed, and now it keeps me asking for a Google Account, I tried with all accounts I have but I keeps me for a propietary gmail account
Click to expand...
Click to collapse
Google it for FRP remove/bypass. :fingers-crossed:
Or unlock bootloader and go with custom ROMs.