Related
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
RastaFATian said:
hello,
I buyed a moto g, it's my first smarthphone... it's a XT1069 Dual Sim
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245 ,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Click to expand...
Click to collapse
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
rafaelbrunner said:
There's no need to make multiple topics, my friend...
Remember that the TWRP IMG file must be in the same folder as your Fastboot files.
So, you can copy TWRP2801-titan-motog-2014.img file to the directory where your Fastboot is.
Or, you can type the directories correctly. For example, if your TWRP2.8.0.1 IMG file is located on your Desktop:
So, your command should be: fastboot flash recovery C:\Users\"username"\Desktop\TWRP2801-titan-motog-2014.img
Instead of typing, you can also drag-and-drop the TWRP2801-titan-motog-2014.img file into the CMD window.
Got it?
Click to expand...
Click to collapse
I'm sorry about multiple topics... my bad.... but you can erase the other in general topic....
but to flash i need to be in recovery mode at boolloader, no?
i can do this command in bootloader menu?
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Fastboot and recovery are two different things. If you can get to Fastboot (bootloader) mode you should be able to flash recovery from there as stated by rafaelbrunner.
Hi Guys !
I'm facing a problem on rooting my Moto G 2014.
I've easily unlocked the bootloader but i can't flash the TWRP recovery.
I've read everything I could read about the process and I think I'm doing it the right way (the recovery file in the adb folder, etc...) and everything seems to be ok.
I've just a purple line at the end of the TWRP flashing procedure saying:
Mismatched partition size (recovery)
This post says that it's not really a problem: http://forum.xda-developers.com/showpost.php?p=48294073&postcount=6
Then, when I reboot the recovery, the phone reboots and the system starts normally (instead of restarting with the custom recovery ?). When I switch it off and switch it on in recovery mode, I still have the stock recovery.
Tried several times with TWRP 2.8.0.1
I can't say if it's because of a problem with TWRP (it's said here that it is buggy) or because I'm doing something wrong that I don't succeed.
I saw that there was a 2.7.1.1 release of TWRP for Moto G 2014 but it's no more available anywhere for now. I would have liked to try it...
Do you know if there's some known issues about flashing the Moto G 2014 recovery or can you help in any way ?
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWAP2801 titan-motog-2014.img
target reported max download size of 536870912 bytes
sending 'recovery' (9738 KB)...
OKAY [ 0.344s]
writing 'recovery'...
OKAY [ 0.353s]
finished. total time: 0.700s
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot recovery
error: device not found
C:\Program Files <x86)\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
magmatik said:
Hi guys !
I'm still investigating my problem and still trying to root the phone.
Here is what I get with adb:
The device seems to be seen when it's about writing the file on the storage but it's no more found when it's about rebooting the recovery...
Can someone help ?
Click to expand...
Click to collapse
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
2987
jbanti said:
First of all Uninstall ur old Moto Usb Drivers and fastboot drivers and Reboot your Pc And Again Install Ur Usb Drivers.
Click to expand...
Click to collapse
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
magmatik said:
Hi !
Thanks for your answer !
What do you mean exactly ? I didin't have any "old Moto usb drivers before". I installed them for the first time few days ago to unlock my bootloader.
Do I still have to uninstall these drivers (that are not that old) and install again the same ones ?
Click to expand...
Click to collapse
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
1932
eskamhl said:
You can use "adb reboot recovery" only if the phone is turned on in normal android os ( in bootloader mode it'll only recognize fastboot commands ), and you must be sure also to have debug usb option enabled under settings/developer settings.
Click to expand...
Click to collapse
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
magmatik said:
Hi eskamhl,
I warmly thank you for trying to help me.
I'had enabled usb debbug, no problem about that.
I"m not sure I understand what you mean when you say that the phone has to be " turned on in normal android os". I thought that the device had to started in recovery mode to install TWRP.
I tried to install TWRP with adb reboot recovery and with the phone turned on in normal android os.
adb says <waiting for device> when i paste and execute flash recovery TWRP2801-titan-motog-2014.img
Click to expand...
Click to collapse
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
eskamhl said:
Adb is one thing, fastboot is a different one.
If you give a "fastboot command" from the command prompt the phone must be in bootloader mode, instead if you give an "adb command" you must have the phone normally turned on.
Having said that, I didn't understand what's your problem... are you tryin' to boot into recovery mode or trying to flash twrp recovery?
It seems that you already flashed/installed a custom recovery ( TWRP ) from what you wrote, isn't it?
Click to expand...
Click to collapse
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
magmatik said:
That's the point, I'm trying to flash a custom recovery (TWRP) in order to be able to flash SU.
I'm sorry about my poor english. I'm french and I confess that I'm absolutely comfortable in english.
For now the only thing I succeeded to do is to unlock the bootloader.
What I understand is that I have now to install TWRP with adb, am I right ?
Click to expand...
Click to collapse
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
eskamhl said:
No, you're not
You already did the installation of the custom recovery since you said that you received this message "Mismatched partition size (recovery)", now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select ).
If it won't boot maybe you should check the md5 of the downloaded recovery .img, probably it's a corrupted download.
Click to expand...
Click to collapse
When I try to boot into recovery from the bootloader (what I already did before), the screen turns black, 1 sec later the led switch on for half a sec and nothing else happends.
So, as you say, the recovery I downloaded was maybe corrupted. I'll check.
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
magmatik said:
Guys, I've found the solution !
I think everything was ok from the beginning. The only thing that I did not understand was that I have to press vol- in fastboot to focus on "recovery" and to press vol+ to launch the recovery.
I didn't read it anywhere, i just see this in this video : https://www.youtube.com/watch?v=jr14wNgazOw&hd=1 (see at 7"15).
Anyway, thank you for trying to help me and see you soon for all the good things coming for this phone !
Click to expand...
Click to collapse
My friend... a few posts above
eskamhl said:
now from bootloader menu you should boot into recovery ( volume down to scroll thorugh the options and volume up to select )
Click to expand...
Click to collapse
I successfully installed twrp recovery system but I can't do any backup, the system reboot in the process...
eskamhl said:
My friend... a few posts above
Click to expand...
Click to collapse
You're right... my bad
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".
It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img
Rename file
Did you rename the file? You need to rename it before flashing.
IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.
cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.
Try the last TWRP release, should work!
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.
Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...
cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...
adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers
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, I have some problems on my Mi A2. I rooted the device in August to enable Camera2API (getting stuck in the security update of the same month.). I installed Magisk and everything was going well. Then came a notification regarding the October update. I clicked to upgrade and by the time it was done, the device was working perfectly until the moment it completely discharged its battery. After that it gets into Bootloop on the Android One boot screen. I would like some suggestions for the solution. Thanks.
until the moment it completely discharged its battery
Click to expand...
Click to collapse
same here! I am not rooted and not unlocked.
Exactly the same here...
fly23 said:
same here! I am not rooted and not unlocked.
Click to expand...
Click to collapse
This was 2 days ago. It worked again after about 150 reboots. Or i pushed a special button combination, I don't know.
In betweet I did one "fastboot reboot".
Now I have the same problem again after empty battery. Bootloop.
This is the worst android phone I ever bought after HTC desire, Galaxy Nexus, Nexus 5, 5X. I will never again buy a budget phone or a xiaomi.
I did a factory reset this morning, and itgot stuck on an Android One screen. I am trying to figure out how to reflash it, but it doesn't seem to like the firmware. Not sure if I have to unlock the bootloader? I am not family with any of this stuff. I was supposed to ship the phone to the buyer today, but I guess I may have to kill the deal and refund them. This may be the last Xiaomi I buy.
https://imgur.com/a/5J51w3D
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
Yeah, I wonder that as well.
The arrow down + power button combination just keeps the phone frozen on a fancy picture with "fast boot" written at the bottom of the screen.
clocks11 said:
How do you change slot? The fastboot screen does not have any options/menu for me. It is just a picture.
Click to expand...
Click to collapse
You need PC for that
Boot into fastboot (vol - + PWR)
Then use fasboot from terminal
First look which slot is active by typing
fastboot getvar current-slot
Then we can change active slot using this commands
fastboot --set-active=a
or:
fastboot --set-active=b
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Aerobatic said:
Unfortunately, to be able to switch booting slot one needs fully unlocked phone (bootloader and critical partitions in our case).
Being fully unlocked, one can boot device in fastboot into TWRP, and from there:
- change slots
- wipe Dalvik/Art cache (and other Cache partition if present) - which in turn very often helps to recover from OTA-generated bootloop
Click to expand...
Click to collapse
I think this is why my phone is completely bricked. It does not have an unlocked bootloader, so it seems I can't flash firmware on it. I will likely never buy Xiaomi again after this. I just was doing a factory reset since I had sold the phone.
[email protected] said:
for me helped that thing
1. boot manually into fastboot mode
2. Change slot, reboot to fastboot
3. Change slot again.
4. After that reboot to system completed succesfully
but that sh*t came back again in a week for me
Click to expand...
Click to collapse
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
ngohoainam said:
this method works perfectly to me :good: ! my Mi A2 update to Oct 5 2019 patch okk. but i want to restart my phone. after restart, my phone is bootloop then luckily i found this usefull guide. thanks you very much again! Android One on Xiaomi is really sh*t.
Click to expand...
Click to collapse
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
clocks11 said:
I'm still not clear how to change slot. Does the the phone have to be unlocked for this? Is special PC software needed? My A2 has been a brick for almost a week now.
Click to expand...
Click to collapse
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
ngohoainam said:
yes. you need your phone to be unlocked Bootloader and Critical Partition to use fastboot. more info here ( read Prerequisites carefully )
after you unlocked your phone and unlock Critical Partition. turn off you phone and after that press both Power and volumn down button at the same time. then your phone is booted to fastboot mode.
in fastboot mode. type fastboot getvar current-slot . after that the system will return your current slot. example: b
then you type fastboot --set-active=a
then you disconnect your phone to PC and then reboot again.
then you turn off your phone again and turn your phone to fastboot mode. then you type this command again: fastboot --set-active=b
then you disconnect your phone and boot your phone normally. after that your phone is fixed from bootloop.
ps: remember to download the driver and minimal fastboot so that your pc recognize your phone is connected to your pc
Click to expand...
Click to collapse
Unfortunately, I think I am screwed, as the phone was not unlocked prior to my boot issue. So I am not sure there is anything I can do. I can get to fastboot though.
Hi all,
I'm encountering a very annoying issue with my brand new Zenfone 8.
I wanted to install the last LineageOS image, but now my phone seems stuck.
Here are what I did:
- Unlocked the bootloader: success with the ASUS APK after a few tries (error 11000 and 11006 ans eventually worked).
- Rebooted to bootloader
- Entered into recovery
- Used fastboot to flash the vendor partition.
At this point, everything looked OK. But then.... :
- Powered off the phone and restarted to bootloader.
- Tried to enter into recovery to flash the Lineage Recovery
But at this point, I had a ASUS logo stucked on the screen.
I can't do anything with adb or fastboot commands.
I tried the method explained here (https://www.asus.com/Content/Android-13-Beta/) to rollback to stock Android 12, but nothing happened too: I looked at the shell script (I'm on Linux) and I reckon that it stucks on fastboot command (the phone is in the bootloader).
Any idea about what failed? The last command used (vendor partition flash) said "OKAY".
And especially, what can I do now? Any way to reinstall the ASUS recovery?
Thanks in advance guys.
Not quite sure what your status is if you say "can't do anything with adb or fastboot commands". I've flashed Zenfones a couple of times (my household has 3 Zenfone 8's on LineageOS) and I had one that went into ramdump. I recovered from that using fastboot to manually reflash all 19 firmware partitions, in both slots. That got the phone out of ramdump, and I got to continue the upgrade to the new LineageOS. So: if you can boot to the fastboot environment, then that would be a road that might leaed you out. But if you can't even get a response to the command "fastboot devices" then I don't know of a course of action for you.
To use fastboot commands I had to run the phone into bootloader mode, then to "recovery" and eventually "fastboot" (I'm note 100% sure but it's what I remembered).
Without that, I was unable to use any fastboot commands like device or flash.
And now the issue is that I'm not able to go to recovery/fastboot again, because I have just the ASUS logo and nothing else.
It looks like that the stock recovery was dead, but I don't know why - and I don't know how to fix/reset it.
From the bootloader you should be able to flash the raw image again, it should flash everything
Adaoh said:
From the bootloader you should be able to flash the raw image again, it should flash everything
Click to expand...
Click to collapse
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
semurel said:
Good to know - but with which commands/tools?
As I said, I was unable to use fastboot commands from my computer on the Zenfone bootloader.
On the bootloader page, I just have "waiting for devices" and noting else. I had to go into the recovery > fastboot to make the commands work.
Click to expand...
Click to collapse
On Linux and maybe macs too you need to run fastboot commands as Root (sudo fastboot devices) for example. The raw image script should ask you for your Root password for this reason
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
semurel said:
Yes I know - I well used sudo for all commands.
The ASUS script asks me for password but then does absolutely nothing - not even a print. I waited a few minutes and finally canceled.
For you, fastboot commands should work on the bootloader screen? (I ask that because the script starts by a fastboot command).
Click to expand...
Click to collapse
Yes, they work from the bootloader, I always run the script from the BL too. Ironically, I had issues running fastboot commands from fastbootd for installing Omnirom, so I did it all in the bootloader and all worked fine.
I am not sure I can help you more at this point, it looks like it maybe got interrupted mid flashing and now something is wrong somewhere. Maybe if you look inside the bash script file you can find the command that it got stuck on and run that manually if you manage to get fastboot command access.
Strange - they have never worked from the bootloader. I tried that before according to the LineageOS wiki. I thought it was a mistake and use the recovery > fastboot to do that. I dont like that - I hope it's not a local version of the Zenfone or something like that.
I'm not at home tonight but yes I'll try to find commands not requiering the fastboot command.
Unfortunately all commands from the script are using fastboot. And as "fastboot devices" sees nothing, I can't do anything.
I've tried from the bootloader screen (with start, recovery, poweroff option) - from the start screen showing unlocked bootloader warning and from the ASUS logo when I try to start the recovery. I've tried the commands/scripts with Linux and Windows: same result.
So :
- I can't use any fastboot commands.
- I don't have the ASUS recovery.
Speaking of the ASUS recovery, I've found screenshots on internet and they don't have a "fastboot" submenu (I'm not sure it's a Zenfone 8). May had I a different version?
I don't like that. If I don't have others option, I guess that the warranty doesn't work because the phone is unlocked?
I eventually found a solution! I've tried with my old OnePlus cable and fastboot commands start working from the bootloader screen.
I have no idea why my other cable was faulty (it can charge the phone and executes commands from the Recovery > Fastboot menu - but not on the BL screen).
Anyway my problem is now fixed.
Thanks all for help and support.