Related
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
I tried everything in this thread:
http://forum.xda-developers.com/p8lite/general/hand-fixing-bootloop-t3464740
to no avail. One thing I noticed is that the link given in the Fastboot menu links to a Chinese (?) website - http://zh.ui.vmall.com/emotiondownload.php?mod=restore - I'm not sure if this is indicative of me having a device for the East Asian markets and if there are any software differences?
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
GfIsGonnaKillMe said:
Sorry for the triple post - now I actually managed to boot into TWRP (the trick is disconnecting the USB cable before booting into recovery), I wiped everything, re-tried the flash all from the Mega thread, and it's still not working - Huawei logo is shown, then black screen/power off(?).
Click to expand...
Click to collapse
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
XePeleato said:
Hi, when you power on your device to boot into EMUI, does it just show the red Huawei logo, or does it also show the boot animation (the same logo dancing and moving on the screen and then becomes static)?
Click to expand...
Click to collapse
Just the very static image, it doesn't even go into the animation.
Edit: this is a newly bought P8 Lite, the Box says Android 5.0, don't know if relevant?
by now I've wiped stuff with TWRP more times than I can count, and tried manually flashing the boot, recovery, cust and system of b132, b170, b190, and b564 to no avail
GfIsGonnaKillMe said:
Just the very static image, it doesn't even go into the animation.
Click to expand...
Click to collapse
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
XePeleato said:
Alright, so, since you can get into TWRP, inside TWRP go to Advanced > File manager and get this file: /sys/fs/pstore/console-ramoops and paste it to the internal storage or the sdcard, then via USB paste it to your computer and upload it somewhere, I'd like to check it.
Click to expand...
Click to collapse
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
GfIsGonnaKillMe said:
http://pastebin.com/Hchyjqcz
I hope I did everything right! Currently flashed 132 boot, system and cust with TWRP in recovery
Click to expand...
Click to collapse
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
XePeleato said:
Yes, I found what I wanted, the kernel panics. What have you exactly done to the device? That would definitely help to know how to solve it.
Click to expand...
Click to collapse
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
GfIsGonnaKillMe said:
I wish I knew! I tried to root it the same way I rooted my other P8 Lite, which worked fine in the beginning (unlocking bootloader) and ****ed up somewhere between pushing SuperSU to the device and executing it. Then I tried to flash stockrecovery.img back, and suddenly the device was broken. Next thing I did was follow the guide in the Mega Thread (I think resetting to b052) which didn't help either. Then worked my way through the suggestion in the other thread. :silly:
edit: judging by my google history, the problems started when the recovery returned a segmentation fault instead of installing SuperSU as it would've been supposed to.
Click to expand...
Click to collapse
[ 8.389146s][pid:1,cpu1,init]BUG: failure at /cloud/jenkinswh/ci/workspace/Alice_Channel_ANDROID/android_code/kernel/drivers/video/hisi/hi6220/balong_compose.c:613/vpu_on_notice_ade()!
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
XePeleato said:
This is suspicious, ADE is related to graphics, I don't really know how could that happen jsut by flashing a couple of things, but I'll look into it, I just need some time.
Click to expand...
Click to collapse
It is very nice of you to look into this! Worst case scenario, the device was broken from the start and has now lost its warranty (though I booted it up once without problems right in the beginning).
For the main problem - which is my gf - I simply factory reset my own P8 Lite and put the stickers from the new one on it. Now I don't have a phone, but at least I get to keep my relationship
ninja edit: checking my terminal history, I remember trying to fix the not-installing SuperSU by trying fastboot -w and fastboot format cache as recommended elsewhere, but both failed
Playing around with it again, it seems the only fastboot commands working are fastboot flash and fastboot reboot, everything else is giving a "FAILED (remote: Command not allowed)" error, even for things like getvar
flashing b564 allows me to get into stock recovery, will try dload update now!!
EDIT: IT WORKS!!!
Things I learned from this:
- it is important to flash right update version
- use dload if you can boot into stock recovery
- recovery will only be loaded if not connected via USB, otherwise EMUI crap will launch
- vendors do not always have correct information on device package!!
GfIsGonnaKillMe said:
P8 Lite, I can boot into Fastboot&Rescue, normal boot gives a black screen after the Huawei logo. Recovery and force download from SD does not work.
I can boot into EMUI recovery by holding Vol Up in Fastboot, which gives me the options of Reboot, Shutdown and "Download new version and recovery" (which fails).
I tried the Unbrick steps from the Mega-Thread, and also flashed the Huawei P8 Lite version of TWRP to recovery - but it still only loads the EMUI Huawei eRecovery. Bootloader is unlocked.
Any ideas on what to do next before my girlfriend is going to kill me?
Click to expand...
Click to collapse
delete
For unbrick, its easy if your bootloader is unlocked.
Just need time and flash few files by adb (downgrade)and update your device's to the android version you want.
If you want I have all the necessary files.
After your device's is like at his first boot.
Sent from my SM-N9005 powered by QS-N9005-LP
Step 1 (Unlocking bootloader) :
Make sure you have adb and fastboot .
get your serial number.
Code:
adb shell getprop ro.serialno
calculate md5 of the serial number of device ( i used this https://passwordsgenerator.net/md5-hash-generator/).
Reboot bootloader.
Code:
adb reboot bootloader
Unlock using key (md5code=md5 of your serial number).
Code:
fastboot oem key md5code
Code:
fastboot oem unlock
Step 2 (flashing twrp fixing encryption problem):
Download twrp :=https://www.androidfilehost.com/?fid=1322778262903986803
Reboot bootloader by connecting power button + usb cable + volume down and type
Code:
fastboot flash recovery TWRP-3.2.3-TwrpBuilder-2018-08-21_14.img
.
Reboot recovery by using power button + usb connected + volume up at same time .
Download fstab:=> https://gist.githubusercontent.com/androidlover5842/e5fccc739251bb75ad7cf1d8ddc36e0d/raw/a4646983b481c02462cd0cfbf8decb9edf4f2ac9/fstab.mt6735 and go to mount menu in twrp => mount vendor and update fstab using this commnd .
Code:
adb push fstab.mt6735 /vendor/etc/fstab.mt6735
make backup of boot using backup option and flash stock recovery as boot (you can get stock recovery from here )
reboot system and it should reboot into stock recovery
wipe data using stock recovery
reboot back to twrp by pressing power + usb + volume button.
restore boot and flash magisk.
XDA:DevDB Information
Unlocking / Rooting Nokia 1 stock rom, Tool/Utility for the Nokia 1
Contributors
androidlover5842
Version Information
Status: Stable
Created 2018-08-21
Last Updated 2018-08-21
unlock failed
it seems the key did not work. Maybe imei is involved in generating key? (my Nokia 1 is dual sim)
---------- Post added at 11:44 PM ---------- Previous post was at 11:26 PM ----------
slim404 said:
it seems the key did not work. Maybe imei is involved in generating key? (my Nokia 1 is dual sim)
Click to expand...
Click to collapse
SOLVED.
I had to allow OEM unlocking in Developer Settings
androidlover5842 said:
Step 2 (flashing twrp fixing encryption problem):
reboot system and it should reboot into stock recovery
Click to expand...
Click to collapse
Hmm all good till this step, but the device stuck doesn't reboot into stock recovery but bootloop TWRP
Obviously i messed up something and i wonder what it is
ObviousSimple said:
Hmm all good till this step, but the device stuck doesn't reboot into stock recovery but bootloop TWRP
Obviously i messed up something and i wonder what it is
Click to expand...
Click to collapse
I got the same problem. I found out the recovery file he linked to was that of a single SIM Nokia 1 (TA-1060) mine is a Dual Sim Nokia 1 (TA-1047)
I downloaded the TA-1047 original firmware (I googled it)
I used it to reflash boot and recovery. Then redid everything using this time the right original recovery.bin from the TA-1047 firmware and it worked
Android Downgrade
I'm planning to buy this phone but I don't like the software. Can I install Android Kit Kat on it?
Hi! I have soft-bricked Nokia 1 ta-1047(recovery bootloop). How can i unlock bootloader without checkin OEM unlock in dev settings? Thks!
Hi! I had some trouble understanding the instructions. Step 1 worked without a hitch but I ran into some problems in step 2. I'd be really grateful for some help.
Do I copy the text in the link, paste it into a .txt file and then save it to "ftsab.mt6735" in the Minimal And Adb Fastboot folder on my pc?
Do I press cancel when twrp asks me for a password? Or do I need a password? I pressed cancel.
When I go into "mount" in twrp and click on "vendor" do I then go the command window on my pc (from the adb fastboot folder) and type "adb push fstab.mt6735 /vendor/etc/fstab.mt6735"? This is what I did and it might have come with an error I'm not sure.
What is the backup of boot for? I guess it's just a safety measure. For some reason I couldn't do that because it said something about encyption (I think, unless I'm getting mixed up with before) so I had to skip that step and go onto flashing the recovery. The instructions now say "flash stock recovery as boot (you can get stock recovery from here)". Is the stock recovery the "recovery.bin" file and do I put that in the adb and fastboot folder? I did that and typed "fastboot flash recovery recovery.bin" in the command window. Was that right or not?
The instuctions say "restart the system" Is that from the twrp menu? I restarted the phone via twrp but it didn't restart into stock recovery it restarted into the normal operating system. I knew then that I'd done something wrong. I then turned off the phone and tried accessing the stock recovery by pressing the volume up and power on and it started in twrp! Am I getting confused? Please can someone help me! Thank you!
anhadsingha said:
I'm planning to buy this phone but I don't like the software. Can I install Android Kit Kat on it?
Click to expand...
Click to collapse
No you can't and why would you want KitKat. Kitkat was good 5 versions ago
---------- Post added at 03:20 PM ---------- Previous post was at 03:17 PM ----------
mountainair said:
Hi! I had some trouble understanding the instructions. Step 1 worked without a hitch but I ran into some problems in step 2. I'd be really grateful for some help.
Do I copy the text in the link, paste it into a .txt file and then save it to "ftsab.mt6735" in the Minimal And Adb Fastboot folder on my pc?
Do I press cancel when twrp asks me for a password? Or do I need a password? I pressed cancel.
When I go into "mount" in twrp and click on "vendor" do I then go the command window on my pc (from the adb fastboot folder) and type "adb push fstab.mt6735 /vendor/etc/fstab.mt6735"? This is what I did and it might have come with an error I'm not sure.
What is the backup of boot for? I guess it's just a safety measure. For some reason I couldn't do that because it said something about encyption (I think, unless I'm getting mixed up with before) so I had to skip that step and go onto flashing the recovery. The instructions now say "flash stock recovery as boot (you can get stock recovery from here)". Is the stock recovery the "recovery.bin" file and do I put that in the adb and fastboot folder? I did that and typed "fastboot flash recovery recovery.bin" in the command window. Was that right or not?
The instuctions say "restart the system" Is that from the twrp menu? I restarted the phone via twrp but it didn't restart into stock recovery it restarted into the normal operating system. I knew then that I'd done something wrong. I then turned off the phone and tried accessing the stock recovery by pressing the volume up and power on and it started in twrp! Am I getting confused? Please can someone help me! Thank you!
Click to expand...
Click to collapse
If you're phone booted fine into system and you can access twrp then just flash magisk as you've done ok and the phone and twrp are working
How to "flash stock recovery as boot" ?
How to "flash stock recovery as boot" ? I went to fastboot mode and flashed recovery.bin then rebooted to recovery and it showed "no commands". No options were there.
ttocs99 said:
If you're phone booted fine into system and you can access twrp then just flash magisk as you've done ok and the phone and twrp are working
Click to expand...
Click to collapse
Thanks. But I'm still not sure. I confess I'm a novice. I actually ended up bricking my phone because I went on to do something wrong. I'll get another phone this week to try and root again, hopefully successfully this time. Isn't the step to make a backup of the boot really important because we have to flash that boot near the end? I thought it was necessary. I also wonder whether I should have typed "fastboot boot recovery.img" instead of "fastboot flash recovery recovery.img" because the instructions say "flash stock recovery as boot"? Edit: Perhaps I'm wrong again
madmax786 said:
How to "flash stock recovery as boot" ? I went to fastboot mode and flashed recovery.bin then rebooted to recovery and it showed "no commands". No options were there.
Click to expand...
Click to collapse
Did you manage to get a backup of the boot?
I can have no access in the udev/ etc.... Can you please explain the following steps how to do it? is it a linux command that needs to be done on a linux running computer or does it works on Windows too?
i was indeed happy that it completed the backup to my external SD Card made with Magisk a patched boot image, but doesn't seem to be rooted after all, what next? it says every time Magisk is not installed do i have to flash it in minimal ADB
Sincerely
Des.Coene said:
I can have no access in the udev/ etc.... Can you please explain the following steps how to do it? is it a linux command that needs to be done on a linux running computer or does it works on Windows too?
i was indeed happy that it completed the backup to my external SD Card made with Magisk a patched boot image, but doesn't seem to be rooted after all, what next? it says every time Magisk is not installed do i have to flash it in minimal ADB
Sincerely
Click to expand...
Click to collapse
Rooting this for now is a gamble there is only 1 stock ROM to flash and it's for the UK single SIM varient of the Nokia 1 only thing you can have is root and twrp and maybe flash a gsi but most of them are still buggy if you can flash stock and stay that way untill further development.
ttocs99 said:
Rooting this for now is a gamble there is only 1 stock ROM to flash and it's for the UK single SIM varient of the Nokia 1 only thing you can have is root and twrp and maybe flash a gsi but most of them are still buggy if you can flash stock and stay that way untill further development.
Click to expand...
Click to collapse
There seem to be buggy , certainly when 2 different chip sets are used in several Nokia 1 series
the mt6737 as i have & the mt6735 there's what i've been struggling with.
Thanks anyways for the advice
Sincerely
Des.Coene said:
There seem to be buggy , certainly when 2 different chip sets are used in several Nokia 1 series
the mt6737 as i have & the mt6735 there's what i've been struggling with.
Thanks anyways for the advice
Sincerely
Click to expand...
Click to collapse
I have the mt6735 but shouldn't be long for a custom ROM as root and twrp have been achieved.
madmax786 said:
How to "flash stock recovery as boot" ? I went to fastboot mode and flashed recovery.bin then rebooted to recovery and it showed "no commands". No options were there.
Click to expand...
Click to collapse
Hi,i got the exact same problem
ramnus said:
Hi,i got the exact same problem
Click to expand...
Click to collapse
Hi, try holding the power button for a few seconds and then releasing it and pressing volume up.
For the record, I managed to root my ta 1060 phone. Thanks everyone. I think I had a problem initially because twrp asked for a password due to phone encryption and I ignored it. I managed to bypass that password screen by not rebooting after flashing twrp, instead going straight into twrp and following the instructions.
I've now got a problem getting usb otg to work. I've added the files android.hardware.usb.host.xml, handheld_core_hardware.xml and tablet_core_hardware.xmls. It's showing as enabled in all the app checkers but Usb Otg Helper says E: Mount directory could not be created, E: This app will not work, OTG mass storage not supported?, NTFS write support failed(no fuse). That's not a topic for here though. If anyone can help, can they pm me please
Nokia 1 root
mountainair said:
Hi! I had some trouble understanding the instructions. Step 1 worked without a hitch but I ran into some problems in step 2. I'd be really grateful for some help.
Do I copy the text in the link, paste it into a .txt file and then save it to "ftsab.mt6735" in the Minimal And Adb Fastboot folder on my pc?
Do I press cancel when twrp asks me for a password? Or do I need a password? I pressed cancel.
When I go into "mount" in twrp and click on "vendor" do I then go the command window on my pc (from the adb fastboot folder) and type "adb push fstab.mt6735 /vendor/etc/fstab.mt6735"? This is what I did and it might have come with an error I'm not sure.
What is the backup of boot for? I guess it's just a safety measure. For some reason I couldn't do that because it said something about encyption (I think, unless I'm getting mixed up with before) so I had to skip that step and go onto flashing the recovery. The instructions now say "flash stock recovery as boot (you can get stock recovery from here)". Is the stock recovery the "recovery.bin" file and do I put that in the adb and fastboot folder? I did that and typed "fastboot flash recovery recovery.bin" in the command window. Was that right or not?
The instuctions say "restart the system" Is that from the twrp menu? I restarted the phone via twrp but it didn't restart into stock recovery it restarted into the normal operating system. I knew then that I'd done something wrong. I then turned off the phone and tried accessing the stock recovery by pressing the volume up and power on and it started in twrp! Am I getting confused? Please can someone help me! Thank you!
Click to expand...
Click to collapse
Have you found password ?
Help please
Des.Coene said:
There seem to be buggy , certainly when 2 different chip sets are used in several Nokia 1 series
the mt6737 as i have & the mt6735 there's what i've been struggling with.
Thanks anyways for the advice
Sincerely
Click to expand...
Click to collapse
Buddy is there anyway I could get stock or custom rom to bootup my bricked MT6737 TA1056 ??
I’m stuck in a blank screen and vibration
xdakanwal said:
Have you found password ?
Click to expand...
Click to collapse
No, when I found it asked for a password I realised I shouldn't have rebooted the system and so I wiped the data and flashed twrp again and no more password.
My TA-1066 is basically dead. Unlocked, doesn't boot into recovery, flashing the ROM fixed it last time this happened. Now it doesnt. In a bootloop with the NOKIA logo.
Help would be really appreciated.
---------- Post added at 07:23 AM ---------- Previous post was at 07:23 AM ----------
My TA-1066 is basically dead. Unlocked, doesn't boot into recovery, flashing the ROM fixed it last time this happened. Now it doesnt. In a bootloop with the NOKIA logo.
Help would be really appreciated.
Hi guys, i need some help pleeease!
I was with the November security patch on my cell phone, I unlock the bootloader and went to use the friend tool (https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585) to activate the camera2api.
But it gave problem and the cell phone did not turn on, it was locked in the screen of android one.
So I downloaded the patched_boot.img from the version I was in and put it via fastboot. did not work.
Now, my phone is in this situation: I tried to use MiFlash (three versison: 2018528, 2017720 and 20151028) and they fail in the middle of the process, accusing "FAILED (command write failed (Unknown error))".
And: when I try to connect the cell phone normally, it shows the unlocked bootloader warning and goes straight to the fastboot, even without my request. This is strange. Perhaps because the system is damaged by the miflash unfinished
Obs: bootloader are unlocked and i can access twrp
If anyone can help me I will be very grateful and happy
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
AsItLies said:
What exactly did the "tool" do? I mean if you don't know that, pretty difficult to diagnose what's wrong...
Click to expand...
Click to collapse
Hi.
The tool (her topic link is up there) promised to activate camera2api without root my device (allowing OTAs in the future).
I believe she did a "temporary root" with a "temporary" boot.img just to activate the camera2api, and when it rebooted, it would return to normal boot.img without root. I do not know if I could explain it well.
The current issue is that it seems that the system is currently "destroyed or corrupted". Can not I reinstall the entire system through TWRP? Or something like this
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
AsItLies said:
Like I said, you don't know what it actually did. What it promised is one thing, what it did... another
That's the problem with 'tools'.
Have you tried doing a factory reset? Hold Vol up and power until it gets to Recovery (hopefully), if you do a quick press of vol up, that gets past the 'no command'. Then use vol up and down for selection and press power when on 'factory reset'.
It might work
Click to expand...
Click to collapse
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
erickxd said:
You are right, friend.. this is the problems with tools! I never use tools with my A1 and past phones.. just this time :crying:
I tried the factory reset now. And it did not work, unfortunately. On the first attempt (I was in fastboot mode) he showed a white circle with the writing "ERASING" and then went back to the screen of Android One, and then I tried again Vol Up + Power and he appeared "No command" , and after I rebooted and tried again, nothing appears, it just restarts to the static screen of "Android One"
Another ideas?
Click to expand...
Click to collapse
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
AsItLies said:
The only other thing I can think of would be to change the current slot. If that works you would be booted into the prior version of the OS vs the latest update you did.
In fastboot, do fastboot getvar current-slot
Depending on what that slot is, change it to the other one (can only be a or b)
thus fastboot set_active a (or b, whichever is not the current one)
then fastboot reboot - and hope it boots.
Click to expand...
Click to collapse
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
erickxd said:
Well... fastboot don't recognize this command, he show the list of avaible commands
And i don't know why, but for now i can't boot in twrp.img
i'm going crazy :crying::crying::crying:
Click to expand...
Click to collapse
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
AsItLies said:
That's probably because you have an old version of fastboot installed. Upgrade to the newest version, which should recognize dual slots.
dual slots are quite new.
Click to expand...
Click to collapse
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
erickxd said:
Fastboot updated now! I changed the slot from B to A.
But doesn't work, unfortunately. After reboot, the phone can't boot and appears the screen asking between Try Boot Again or Factory Reset. I tried Factory Reset, but don't work =( return to the same screen.
What seems very strange to me, is the Miflash doesn't work. With my Mi A1 miflash ever save me
Click to expand...
Click to collapse
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
AsItLies said:
I've never used miflash, so no help there.
I'd try flashing the correct boot.img (for your software version). You can find the various boot images in the following link (don't forget to thank user ckpv5 for uploading these).
https://sourceforge.net/projects/others/files/Xiaomi_MiA2/
you would do fastboot flash boot_b boot.img
I'd suggest using b slot, as that was originally active. After flashing, set it back to active, try to reboot... then cross your fingers
Click to expand...
Click to collapse
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
erickxd said:
Doesn't work man.. I went to twrp and checking there in the "WIPES session", I saw that the SYSTEM partition is 0kb used and 0kb free. Appears to be entirely empty
Do not have a way to install the whole system via twrp?
Click to expand...
Click to collapse
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
ckpv5 said:
Since now your fastboot is working why don't you use miflash to flash official stock ROM
1. You need unlocked bootloader which you already have.
2. Run these command to unlock critical partition
fastboot flashing unlock_critical
3 . Download the official fastboot V9.6.14.0 ROM from
https://forum.xda-developers.com/mi-a2/how-to/ota-v9-6-5-0-odimife-t3823445
Or here
http://en.miui.com/getrom.php?r=353&m=yes&app=false
4. Install with miflash (you already know the how-to)
5. Once up & running, do OTA to latest
Later .. redo what you want to do like enable camera api2 with proper guide.
E.g: https://forum.xda-developers.com/mi-a2/how-to/how-to-enable-cam2api-simply-ota-t3858861
Click to expand...
Click to collapse
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
AsItLies said:
No, I don't. But I can tell you, twrp is a recovery app. It shouldn't be in the boot slot. And, with dual slot configurations, there is no recovery partition. The other slot is now used to do a recovery.
In other words, the way we *used* to use twrp doesn't work on dual slot phones. I think that's a big part of the confusion people are having. While the boot images do have a small recovery part to them, it's not a separate partition.
If you're flashing boot.img, and setting that slot active, I've no idea how you're getting into twrp.
Click to expand...
Click to collapse
I can access twrp when I flash ''fastboot boot twrp.img" in powershell, so until the next reboot I have access to twrp
erickxd said:
Hello.
I've tried using Miflash several times (3 different versions), but it never ends, it end up with an error every time that he will copy the file system.img to the mobile phone (I analyzed the log).
The miflash divides the file system.img into 5 or 6 smaller parts to be able to transfer to the mobile phone, and in some of these parts gives error, everytime :crying:
Click to expand...
Click to collapse
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
ckpv5 said:
When I read your post here - https://forum.xda-developers.com/showpost.php?p=78085858&postcount=188
"flashing is not allowed for critical partitions" usually due to critical partitions not unlocked. So .. if you already run "fastboot flashing unlock_critical" and you still have error using miflash .. nothing much I can offer to help. Hopefully you'll be able to fix it.
Click to expand...
Click to collapse
Hmm thanks for the answer!
Even when the operation fails after transfer a couple of archives before the system.img??? (on the Miflash)
If my phone was locked, Miflash could transfer these couple of archives before the operation fails?? Or if bootloader is locked, zero files can be passed by Miflash, and the error is apresented at the beginning of the operation?
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
prokaryotic cell said:
Have you successfully unlocked critical partitions?
If yes, try to run flash_all.bat from the official stock image you downloaded. No need to use MiFlash.
Click to expand...
Click to collapse
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
erickxd said:
well... When I just run flash_all.bat from the stock image folder, the .bat file will recognize that I am running it for the connected mobile?
how exactly should I run flash_all.bat? just double clicking it in stock image folder? or should I copy the .bat to /adb folder and open power shell prompt in adb folder and execute the .bat from there? sorry for my ignorance
Can you show me, please?
Click to expand...
Click to collapse
Before someone can explain that, why don't you answer the question asked .. in fact at least 3 people was asking/telling ...
"Have you successfully unlocked critical partitions?"
Without the proper answer from you, not easy to help.
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
sabbath88 said:
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
Click to expand...
Click to collapse
Just flash a custom recovery, the device even had the offical twrp. So?? Just not into fastboot and then flash the recovery by the -- command
fastboot flash recovery recovery.img
(You have to rename the twrp file to recovery or whatever, just write the image file name instead of recovery in the second one. Ex fastboot flash recovery 123.img)
Then command
Fastboot reboot
(Hold the power up button for booting into twrp before hitting enter)
Download a miui recovery rom for your device from anywhere, I don't know I'm lazy.
And before flashing, go into mount select vendor and system if not selected.
And then select wipe
Advanced wipe
Select vendor system data cache.
Swipe to clean
Move the rom to your device
(If your device does not show up in your pc, then go into mount (twrp) select enable MTP if it's disabled, if it shows disabled then enable it again)
After that just flash your rom and then a permissive patch you can ask anyone. Or just flash pitchblack recovery. Fixed my problem of not not booting.
Sorry for the wrong format, wrote it on mobile, as I am a lazy bum.
Wut bruh.
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
ChakibDEV said:
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
Click to expand...
Click to collapse
thanks so much, that helped
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse
mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."
mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.