Related
At&t HTC one, bootloader is already unlocked. As far as i can tell from CMD flashing recoveries completes successfully, as does clearing the cache but after rebooting the bootloader still does not list the phone as tampered and selecting recovery just boots the phone. Any help would be greatly appreciated.
After the flash of the rom, clean the cache:
Code:
fastboot erase cache
Now, you can boot into recovery.
P.s. Flash TWRP recovery, is better then CWM
Guich said:
After the flash of the rom, clean the cache:
Code:
fastboot erase cache
Now, you can boot into recovery.
P.s. Flash TWRP recovery, is better then CWM
Click to expand...
Click to collapse
I did that, also i have tried flashing both TWRP and CWM with neither working. Thank you for your reply though.
NoL1m1tZ said:
I did that, also i have tried flashing both TWRP and CWM with neither working. Thank you for your reply though.
Click to expand...
Click to collapse
Try flashing this one, do a 'fastboot erase cache' first...
http://goo.im/devs/Flyhalf205/M7/Recovery/openrecovery-twrp-2.5.0.0-m7.img
redbull123 said:
Try flashing this one, do a 'fastboot erase cache' first...
http://goo.im/devs/Flyhalf205/M7/Recovery/openrecovery-twrp-2.5.0.0-m7.img
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As far as i can tell everything completed properly, but the bootloader still does not say the phone has been tampered with and choosing to boot into recovery in the bootloader just boots the phone.
EDIT: Link failed. https://www.dropbox.com/s/ug9gm1ve90hj1vg/Failed Flash.PNG
I'm having the same problem. No matter what I do, even if it looks successful, it's just booting into the ROM and not into recovery. I'm about to cry. And yes, I've ran "fastboot erase cache" about 10 times.
yokken said:
I'm having the same problem. No matter what I do, even if it looks successful, it's just booting into the ROM and not into recovery. I'm about to cry. And yes, I've ran "fastboot erase cache" about 10 times.
Click to expand...
Click to collapse
try these back to back
fastboot erase recoveryw
fastboot flash recovery recovery.img
prunzzz said:
try these back to back
fastboot erase recoveryw
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Says "FAILED (remote: not allowed)" when i attempt to erase the recovery.
yokken said:
I'm having the same problem. No matter what I do, even if it looks successful, it's just booting into the ROM and not into recovery. I'm about to cry. And yes, I've ran "fastboot erase cache" about 10 times.
Click to expand...
Click to collapse
NoL1m1tZ said:
Says "FAILED (remote: not allowed)" when i attempt to erase the recovery.
Click to expand...
Click to collapse
fastboot erase recovery
fastboot flash recovery recovery.img
not fastboot erase recoveryw
fastboot flash recovery recovery.img
i wrote w mistakenly
prunzzz said:
fastboot erase recovery
fastboot flash recovery recovery.img
not fastboot erase recoveryw
fastboot flash recovery recovery.img
i wrote w mistakenly
Click to expand...
Click to collapse
I know, i caught that, but still it says failed. Any other ideas?
I think you have operator specific version HBOOT, you need specific recovery.version.
Thats for the One x, wont there be problems from flashing that?
EDIT: Also attempted flashing a custom recovery though goo.im's app using the open recovery script but that also didnt work even though it threw a toast notification that it installed successfully.
I'm sorry for my carelessness, and wrong link.. you don't need to flash it!
I didn't find any specific recovery for at&t. My assumption most likely the wrong.
NoL1m1tZ said:
I know, i caught that, but still it says failed. Any other ideas?
Click to expand...
Click to collapse
hey i have read on another thread that one more user faced this problem
later he relocked and then reunlocked the bootloader and then flashed recovery and was then successful doing this
hope it works for you
hit thanks if i helped you
Hey guys,
I have a EVA-L09 and got into a bootloop.
My phone has an unlocked bootloader and I can access fastboot and twrp.
I wanted to flash the full stock firmware on my phone, but everywhere I look I just find the method with the dload folder on my sdcard. I tried it several times, with "force flash" and it doesn't work.
Is there a place I can find flashable zips or IMG files?
EDIT:
I found the program Huawei Update extractor and got the following screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What do I need to extract to flash everything what came with the stock rom?
Regards,
Samusaranish
Samusaranish said:
Hey guys,
I have a EVA-L09 and got into a bootloop.
My phone has an unlocked bootloader and I can access fastboot and twrp.
I wanted to flash the full stock firmware on my phone, but everywhere I look I just find the method with the dload folder on my sdcard. I tried it several times, with "force flash" and it doesn't work.
Is there a place I can find flashable zips or IMG files?
EDIT:
I found the program Huawei Update extractor and got the following screen:
What do I need to extract to flash everything what came with the stock rom?
Regards,
Samusaranish
Click to expand...
Click to collapse
In fastboot u can flash Boot.img, Recovery.img, System.img, Cache.img, Cust.img, Userdata.img
Addymore said:
In fastboot u can flash Boot.img, Recovery.img, System.img, Cache.img, Cust.img, Userdata.img
Click to expand...
Click to collapse
thanl you, I flashed those and it works. Youu made my day a big THANK YOU
Addymore said:
In fastboot u can flash Boot.img, Recovery.img, System.img, Cache.img, Cust.img, Userdata.img
Click to expand...
Click to collapse
Sorry Sir. Can you write full command in CMD to me ? My Phone is Brick and I can flash with Fastboot. Thanks :crying:
otong123ABC said:
Sorry Sir. Can you write full command in CMD to me ? My Phone is Brick and I can flash with Fastboot. Thanks :crying:
Click to expand...
Click to collapse
fastboot flash boot boot.img
fastboot flash recovery recovery.img
.......
You just type like that... And flash all the images in the order given up...!
Addymore said:
In fastboot u can flash Boot.img, Recovery.img, System.img, Cache.img, Cust.img, Userdata.img
Click to expand...
Click to collapse
Whit that sequence can I relock the bootloader and remove TWRP?
Hi there, i am having an issue when flashing RECOVERY or any .IMG into my phone... It is in fastboot mode And i am getting an error when flashing img file , Error : Command Not allowed ...... YES i know what ur going to say (Enable OEM unlock)or(Enable usb debugging in setting) But the problem is that I cannot boot into OS nor recovery, I am stuck on the (Your Device is unlocked and can't be trusted (1)Press power key to continue ECT..... Is there any way Beside Enabling OEM unlock method to fix this or enabling me to gain access to flash recovery or any img file without Command not allowed error ?Ive recently Installed this rom https://forum.xda-developers.com/p9/development/rom-ncs-rom-v1-1-08-16-2016-t3440269 idk if that is part of the Issue Would be Much appreciated for the help
Forgot to mention that doing the 3 buttom method to restore using DLOAD , I get stuck on the HUAWEI logo and doesnt seem to boot into the Updating state.
JaayTee said:
Hi there, i am having an issue when flashing RECOVERY or any .IMG into my phone... It is in fastboot mode And i am getting an error when flashing img file , Error : Command Not allowed ...... YES i know what ur going to say (Enable OEM unlock)or(Enable usb debugging in setting) But the problem is that I cannot boot into OS nor recovery, I am stuck on the (Your Device is unlocked and can't be trusted (1)Press power key to continue ECT..... Is there any way Beside Enabling OEM unlock method to fix this or enabling me to gain access to flash recovery or any img file without Command not allowed error ?Ive recently Installed this rom https://forum.xda-developers.com/p9/development/rom-ncs-rom-v1-1-08-16-2016-t3440269 idk if that is part of the Issue Would be Much appreciated for the help
Forgot to mention that doing the 3 buttom method to restore using DLOAD , I get stuck on the HUAWEI logo and doesnt seem to boot into the Updating state.
Click to expand...
Click to collapse
check drivers windows - p9 or try flash recovery from linux. I used manjaro. You try manjaro live
Wysłane z mojego EVA-L09 przy użyciu Tapatalka
Check my guide post #7 and leave feedback and a thanks!
https://forum.xda-developers.com/showpost.php?p=74169408
sorry fellos , It worked out all well at the end :confused; :silly:,
Thank you btw for replying :]
I am always getting an error command not allowed when I Enter the commands in cmd (Fastboot flash recovery recovery.img) ERROR:Command not allowed ... this time I can now access the dload recovery screen now
JaayTee said:
I am always getting an error command not allowed when I Enter the commands in cmd (Fastboot flash recovery recovery.img) ERROR:Command not allowed ... this time I can now access the dload recovery screen now
Click to expand...
Click to collapse
Follow my guide by flashing the right firmware with fastboot! See the link above!
I Have followed your guide but i am unable to Flash in fastboot ,
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (14980 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.501s
I Have extracted the UPDATE.app files .IMGS but that is the eerror i get when i flash through fastboot
JaayTee said:
I Have followed your guide but i am unable to Flash in fastboot ,
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (14980 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.501s
I Have extracted the UPDATE.app files .IMGS but that is the eerror i get when i flash through fastboot
Click to expand...
Click to collapse
unlock your bootloader first
Boot loader is unlocked , Even if it was locked i still wouldnt be able to unlock it because i need my serial , and other software details which i didnt save , You think dc phoenix will unlock ?
JaayTee said:
Boot loader is unlocked , Even if it was locked i still wouldnt be able to unlock it because i need my serial , and other software details which i didnt save , You think dc phoenix will unlock ?
Click to expand...
Click to collapse
You don't need DC Phoenix. Waste of money.
What phone do you have, model, single or dual sim, European version, Asia?
Post your base firmware! EVA-********
EVA-L09 European version
Unlock your bootloader by running:
fastboot oem unlock <code>
Download L09C432B386 firmware for your L09 (http://update.hicloud.com:8180/TDS/data/files/p3/s15/G753/g104/v84409/f1/full/update.zip) and use that instead of the L19 fw file. Follow my guide using this update.zip file instead of the one for L19.
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
jaaytee said:
eva-l09 european version
Click to expand...
Click to collapse
eva-l09c432xxxx ???
sorry i recently installed a rom with a c900b182 here's the link to it https://forum.xda-developers.com/p9/development/rom-ncs-rom-v1-1-08-16-2016-t3440269 my previous version was dload-huawei-p9-eval09-eva-c432-b136 i tried flashing again with dload but this time i get an error at 8%
JaayTee said:
I Have followed your guide but i am unable to Flash in fastboot ,
C:\adb>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (14980 KB)...
OKAY [ 0.485s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.501s
I Have extracted the UPDATE.app files .IMGS but that is the eerror i get when i flash through fastboot
Click to expand...
Click to collapse
I have same case, bootloader is locked and Cell is still in Warranty so i dint want to break the warranty. how i can install stock recovery ?
I have unlocked my bootloader and i am still unable to flash through fastboot REMOTEcommand not allowed) still getting no permission to flash ...... You were telling me to unlock my bootloader ? How do i unlock my bootloader when i have no access to the os to get my software details , I also download the l09 firmware followed your guide and still unable to flash
fastboot flash boot.img
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
fastboot flash system system.img
I continued with the guide and downloaded the roll back package extracted to dload , Attempted the three button method
(VOL DOWN + VOL UP + POWER)
But its stuck at the huawei logo , Did not know what els to do.. I appreciate your help that ur giving me bro
JaayTee said:
I have unlocked my bootloader and i am still unable to flash through fastboot REMOTEcommand not allowed) still getting no permission to flash ...... You were telling me to unlock my bootloader ? How do i unlock my bootloader when i have no access to the os to get my software details , I also download the l09 firmware followed your guide and still unable to flash
fastboot flash boot.img
fastboot flash recovery recovery.img
fastboot flash recovery2 recovery2.img
fastboot flash system system.img
I continued with the guide and downloaded the roll back package extracted to dload , Attempted the three button method
(VOL DOWN + VOL UP + POWER)
But its stuck at the huawei logo , Did not know what els to do.. I appreciate your help that ur giving me bro
Click to expand...
Click to collapse
Use your computer and go to en.ui.vmall.com/plugin.php?id=unlock and enter the information you can get from your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you're not able to obtain that information, flash the rollback firmware. Did you do that already?
If not, flash the L09 rollback firmware and try to boot your phone in your OS.
Post back!
---------- Post added at 09:31 AM ---------- Previous post was at 09:28 AM ----------
JaayTee said:
sorry i recently installed a rom with a c900b182 here's the link to it https://forum.xda-developers.com/p9/development/rom-ncs-rom-v1-1-08-16-2016-t3440269 my previous version was dload-huawei-p9-eval09-eva-c432-b136 i tried flashing again with dload but this time i get an error at 8%
Click to expand...
Click to collapse
Dis you unlock your bootloader?
Did you follow the guide and flashed the right firmware for your phone?
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
sunnymodh said:
I have same case, bootloader is locked and Cell is still in Warranty so i dint want to break the warranty. how i can install stock recovery ?
Click to expand...
Click to collapse
You will not lose the warranty by unlocking your bootloader. Having a brick by flashing a wrong firmware, as you did, BREAKS your warranty.
Unlock your bootloader first, follow the guide by flashing the right firmware for your phone, update it via sytem update and THEN relock the bootloader, if you're so afraid about warranty issues!
Hi.
I wanted to upgrade to Oreo manually, but mistakenly downloaded files for P10 Plus VKY-L29C432. The Update was successful and I had a phone with P10+ firmware (DPI was way off).
After update I successfully flashed TWRP over stock recovery. Then I tried to flash the correct Oreo update for VTR-L29C432 but it did not work.
Now I am stuck in ERROR MODE.
Fastboot is working and bootloader is unlocked.
Flashing TWRP does not work.
Is there any way to recover P10 firmware?
https://forum.xda-developers.com/p10/help/help-please-error-mode-recovery-t3757571
This guy successfully flashed recovery by flashing kernel.img first. But there is no kernel.img after extracting Oero`s update.app.
There is a kernel image in the update.app from the update.zip.
There is a kernel.img in P10+ update.app, but not in P10 (Oreo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So nothing has helped so far.
Flashed kernel first then TWRP, but I cannot boot into it.
Is there a way I can flash all those IMGs from UPDATE.APP from bootloader?
Hi Cesedy, I'm in the exact same situation as you (https://forum.xda-developers.com/showpost.php?p=75791054&postcount=36) and am out of ideas. I even tried manually flashing the system.img via fastboot but not joy.
There must be a way of recovering the device, but I'm not sure where to go next...:crying:
Hi.
I am out of options as well.
But, there is a saying in this forum, that if bootloader is unlocked and fastboot is working, there is a way out.
Still waiting for it.
Anyway, I opened a thread in this forum too - https://forum.hovatek.com/thread-22218.html
Are we having the same problem?
Thread
I found the kernel.img in the update.app of the FULL-OTA of the oreo update but it was not helpful nor a solution!
The same.
Out of curiousity? does everybody get their previous version for fastboot oem get-build-number?
maybe we should update the bootloader?
Update and a suggestion from the manual updating thread: https://forum.xda-developers.com/showpost.php?p=75800881&postcount=40.
martindoublem said:
Out of curiousity? does everybody get their previous version for fastboot oem get-build-number?
maybe we should update the bootloader?
Click to expand...
Click to collapse
I get:
Code:
D:\>fastboot oem get-build-number
...
(bootloader) :System 8.0.0.046(062P)
OKAY [ 0.003s]
finished. total time: 0.004s
martindoublem said:
Out of curiousity? does everybody get their previous version for fastboot oem get-build-number?
maybe we should update the bootloader?
Click to expand...
Click to collapse
I get this with that command:
Code:
(bootloader) :System 8.0.0.046(04W5)
OKAY [ 0.008s]
finished. total time: 0.010s
grockstar said:
Update and a suggestion from the manual updating thread: https://forum.xda-developers.com/showpost.php?p=75800881&postcount=40.
Click to expand...
Click to collapse
Aw, man, that is not good. Should never lock bootloader if phone is not working.
cesedy said:
Aw, man, that is not good. Should never lock bootloader if phone is not working.
Click to expand...
Click to collapse
Yeah, desperation took over from brains. However no harm appears to have done as the bootloader is actually still unlocked (if the warning splash screen is to be believed).
I've now also managed to get back into fastboot after letting the battery drain completely.
That command is not for locking the bootloader, it is for finding the version. Pretty harmless but useful to find which version we have.
The funky Huawei Unbrick tool did the trick for me on this one. I know it is a pay option but for $50 seems to be worse it.
I was able to boot in the system again, Grockstar was able to get into erecovery so that was progress in both cases!
If anyone needs, can use my DC-Phoenix account, I don`t need it anymore.
Your username is: cesedy
Your password is: dnL4eHEm
After much thinking, I decided to root my new phone, but things did not go well. I unlocked the bootloader and everything went well, but at the time of installing twrp everything went to hell. Now I try to install the official ROM via miFlash and via Fastboot but I always get errors.
In myFlash tool I get: error: FAILED (remote: GetVar Variable not Found)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In fastboot I get: sending system_a
FAILED
"Flash system_a error".
I have bootloop and I can not turn off the device. Can somebody help me?
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
minnuss said:
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
Click to expand...
Click to collapse
Hi, I followed the steps but I can't flash system. I got the same error: "Flash system_a error" in "a" and in "b" FAILED (remote: GetVar Variable not Found)
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Yes something strange with the latest fastboot rom. I could flash it but tried a LOT.
use ./fastboot flashing unlock_critical
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
djmitza222 said:
Boot the phone in edl mode (fastboot oem edl) from the fastboot mode and then flash the rom with MiFlash.
Click to expand...
Click to collapse
I tried, flash some images well, but in boot.img just shows flashing but doesn´t continue. I had waiting long time.
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
djmitza222 said:
Replace the boot.img from Images folder with patched_boot.img from this forum and see if it works. If not, flash the entire ROM without boot.img by deleting that image and then flash it with fastboot flash boot_a boot.img and fastboot flash boot_b boot.img.
Click to expand...
Click to collapse
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
behzad.bz said:
Download this one: Android 8.1.0 [V9.6.9.0.ODIMIFE]
It will flash System_a or System_b without problems. then update via OTA.
I had the same issue with flashing rom. I think u need too much free ram. First close all apps include chrome then try it again. If again failed then try this version Android 8.1.0 [V9.6.9.0.ODIMIFE] it will flash
[V9.6.9.0.ODIMIFE] http://bigota.d.miui.com/V9.6.9.0.O...0.ODIMIFE_20180723.0000.00_8.1_53f18f370a.tgz
Click to expand...
Click to collapse
Doesn't work! :/ i got the same error in slot a and b. I tried flash handly, but the problem continues just in system.img. other images flashed well.
Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
meltbanana said:
I noticed the same, got random feedback from fastboot, command doesn't exist, at the 5th attempt or so it worked, etc. wasn't even able to flash anything, no progress, it just hung. returned the device.
Click to expand...
Click to collapse
:crying: Seriously? your warranty was avoid?
Antolinetz said:
:crying: Seriously? your warranty was avoid?
Click to expand...
Click to collapse
after 2 hours playing with that faulty phone I clearly decided not to open it and sent it back. I suspect there's hardware (RAM?) issues with some Mi A2 devices. as I wrote I wasn't even able to load a kernel. it did weird things and gave me strange fastboot feedback. atm I'll stick with tissot but I'm unsure about xiaomi's latest smartphones .
Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
same occured with me. Try this:
./fastboot flash system_a system.img
./fastboot flash system_b system.img
Antolinetz said:
I tried, boot was flashed well. But I cant flash system_a or system_b. In "a" the error is just FAILED. in "b" FAILED (remote: GetVar Variable Not found).
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
download the 1.0.2 version, it has an unbrick option that takes care of most softbricks
YOU MUST RUN the unlock oem unlock, flashing, and unlock flashing_critical options (options 1 2 and 3) before trying the unbrick option. If the unbrick option does not work, try the revert to stock option.
For any others getting in a bootloop from TWRP, download the 1.0.1 version and run the Launch TWRP option it will overwrite the boot.img to a usable one. TWRP is really buggy right now so FOLLOW THE INSTRUCTIONS.
And for those who have a bootloop because they tried to install xposed, run the revert to stock option. Unfortunately ATM there is no way to keep your data unless you put the https://magiskroot.net/uninstall-magisk-module-twrp/ zip on your device.
Hi guys, finally whith EDL mode, after hours and hours flashed well!
fastboot oem edl
or
fastboot-edl-v2
I have reviewed each .img file and I also found that apparently the system.img file was not decompressed correctly. Then I went to the always reliable Total commander and was decompressed fine.
Thank you all!
people try:
1- Another usb port
2- Another usb cable
3- Another PC
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
woofwoof75 said:
I've hard bricked my 6X. Been days it never wake up... I can see Qualcomm 9008... Tried Mi Flash, Qfil, MiracleBox all doesn't work. Have to wait till I goto China next. Back to my old slow Mi 5.
Sent from my Nokia 8 using XDA Labs
Click to expand...
Click to collapse
but how?