Ok so I was going about Trying to flash TWRP it wouldnt go. Tried a few times etc, nothing, so i gave up.
Now when i reboot or turn off and power up, i get a N/A in the top corner for a few seconds but then it boots up fine. But i cannot do a backup & reset, and i cant get into recovery now.
I get a start up failed your devices didnt start up successfully use the software repair assiant on your computer,
bottom says ap fastboot flashmode secure
error: failed to load kernel
fastboot reason: fall-through from recovery boot mode
but i can toggle to Start and it boots fine.
Computer now does not see the phone when i plug it in, it dont make a sound and is not in the device manager, also when i reboot to fastboot, it still isnt seen at all. flashing_unlocked so i can flash. but cant use adb since pc wont reconize phone now, and i cant reset.
So i can use the phone like normal atleast, but cant reset or access recovery. its like it just inst there
any ideas???
Thanks
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Jtaxel said:
Ok so the computer don't even ding when ya plug the phone I to it. On any computer I use. Is there a corrupted file that the phone uses when connecting to a computer... ?
Phone works fine.. just recovery is missing.. and with no way use to use adb... Is there any way to get the recovery back on?
Click to expand...
Click to collapse
It would help to know what model your device is for one thing. Also, what command exactly did you use to flash the recovery? It almost sounds like you flashed the recovery to the wrong place or you did the erase command before trying to flash and borked the recovery partition.
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Jtaxel said:
ok,
Moto e4 plus, andrid 7.1.1
I did unlock the boot loader.
Security Patch - July 1 2018
Owens
xt1775
The TWRP on this site from git hub was only a zip file not in .img format, so i went TWRP official site and downloaded the one for the moto e4 plus
Put all files where they supposed to. did the adb,
first typed fastboot flash recovery.img that didnt work nothing at all, then did the right way,
fastboot flash recovery recovery.img, didnt work it was able to boot to recovery from adb, but not flash it.
tried a few times, no go, so after that, wheni reboot my phone, it goes straight to the bootloader screen and and says,
start up failed
your device didnt start up successfully use the software repair assisant on your omputer to repair your device.
ap fastboot mode ( secure)
error failed to load kernel!
fastbootReason: Fa;;-through from recovery boot mode
i can arrow down to start and it will start fine ( boot phone up normally )just goes to the n/a in top left for about 10 seconds then starts up normal. But i can NOW adb into my phone again and its reconized by the computer.
did i flash the wrong twrp?
Thanks
switch tools mode
ap fastboot mode (secure)
flashing_unlocked
gives cou emmc dram all that info also
Click to expand...
Click to collapse
Try this twrp. It should work fine. Change the name to recovery.img and flash it
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-08-21_14-10
Jtaxel said:
The TWRP on this site from git hub was only a zip file not in .img format,
Click to expand...
Click to collapse
You unzip to extract the img file.
ST Dog said:
You unzip to extract the img file.
Click to expand...
Click to collapse
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
That is the source not the image. Click on the link that ends with .img not .tar and you'll get an img
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Jtaxel said:
now if i try to fastboot boot recovery.img it boots to recovery but hangs on the recovery loading twrp screen.
and this error in adb now with any code i send
Click to expand...
Click to collapse
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Jason M. said:
You need to type in fastboot flash not fastboot boot. Boot will only "boot" the recovery but won't flash it onto your phone.
Click to expand...
Click to collapse
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Jtaxel said:
yep i know, first time i tried this, it would boot when i type boot. BUT when i tried to FLASH it, it wouldnt flash and stay.
Now i cant even boot TWRP, just hangs on the TWRP logo screen. I let it sit for 5 mins, before it ould only take a few seconds.
BUT i am using the one from the offical site, not the one on github thats only a zip file.
unless someone has the img file from github.
BUT STILL like i said i get that error you see in CMD screenshot.
Click to expand...
Click to collapse
First of all that error is normal. Second, the img is right there on the page I posted the link to. I even posted a screenshot of me downloading it from there. I don't see any reason why I could download the img and you can't. I give up.
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Jtaxel said:
OK, sorry didnt see the link. I downloaded that, i flashed it. IT worked. But now when i reboot it goes straight to recovery. But i reboot to bootloader and start that way, no big deal.
Never seen those errors before, but yea it worked now, must have been the wrong TWRP. Works now. THank you
But whats the default password in TWRP
Click to expand...
Click to collapse
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Jason M. said:
Np. That's why we have a thanks button though. To fix your booting problem you can try connecting your phone to your PC and booting to the bootloader and run this command with fastboot:
fastboot oem fb_mode_clear
That should do it.
Click to expand...
Click to collapse
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Jtaxel said:
tried a couple times, no go, thats ok tho.
But i cant flash nothing because its asking for a password to mount.
Click to expand...
Click to collapse
Ok, try:
fastboot erase DDR
That should solve your booting problem. I knew it was one or the other. Ignore the twrp asking for password and click on the mount settings and you'll see a little check box that says "mount system read only". Uncheck that box
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Jtaxel said:
password fixed, i flashed the no verify and super, and it wiped my phone, is that normal, just wondering ,
yes i made a backup
Click to expand...
Click to collapse
If you flashed the force encrypt noverity zip yes. If you don't want enryption or want it to be optional to encrypt use the one that says opt encrypt. This is all gone over possibly hundreds of times in numerous threads. You should do a little searching and reading.
Jtaxel said:
yep downloaded zip, extracted folder, just shows all the files, in a folder, not an image file
Click to expand...
Click to collapse
My bad. Often a .img file is zipped because .img gets treated as a picture.
And you can also extract .img files from flashable zip releases.
Didn't think you might have grabbed a source code zip.
Related
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
_-..zKiLLA..-_ said:
Okay so i unlocked my bootloader, that went well (as if thats hard)
and then i used Modacos superboot to root, it rooted (except for some reason the super user application opens to just a black screen). After that i continued to flash the recovery so that i can flash Cyanogen. When i try to flash the recovery i keep on getting the error 'cannot load'. i've tried like 4 different recovery roms. Not sure what im doing wrong
Oh and this has been tried on 2 different computers. One win7 and one XP. both gave the same output
Click to expand...
Click to collapse
what commands are you using to flash Amon_RA's recovery image? i also assume you're at the white bootloader screen when trying to flash Amon_RA's recovery image. also, to confirm root access, download the N1 Torch app and if it works, you're rooted.
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Cannot load what - fastboot or the ROM .img file? Do you have fastboot-windows.exe in the same directory as the rom image?-(not necessary if fastboot command works for you)
Type fastboot devices to double check your link between pc and phone. If not check usb cable & drivers.
Make sure ur unlock is right before flashing Amon. If you've rooted then you should see an unlocked-lock image (the the google Xscreen) while booting, or the N1 torch app method as mentioned above.
_-..zKiLLA..-_ said:
Yes the screen is white. And i am using "fastboot flash recovery recovery-RA-nexus-v1.7.0-cyan.img"
Click to expand...
Click to collapse
Make sure you got to that white screen by pressing the trackball and not the volume rocker.
I renamed the recovery image to "recovery-RA-nexus-v1.7.0.img"
Code:
fastboot flash recovery recovery-RA-nexus-v1.7.0.img
Make sure you check
Code:
fastboot devices
and get your device number and also make sure you put it in the tools folder of the Android SDK
Make these steps
Boot ur phone into bootloader
1 Rename the img to recovery.img
2 Place the file in ur toolfolder where u have ur fastboot
3 Rightclik on toolfolder+Shift choose open cmd here
4 write fastboot devices to be shure u are connected
5 then write fastboot flash recovery recovery.img
hi,I have the problem too.I try many times but still stuck TRIANGLE WITH !.when I do recovery image
the screen come up "sending 'recovery"3948 kb.....ok
writing' recovery'......ok
sending 'recovery"3948 kb.....ok
writing' recovery'......ok
Click to expand...
Click to collapse
Code:
fastboot reboot
Finally got Amon_Ra's recovery to install
I started with a stock N1 with froyo
had a few stumbles along the way and lots of searching...lots and lots lol
using the how-to on the cyanogen page I went to the letter as ive never used ADB
So I installed the Latest Android SDK to get the ADB and Fastboot.
verified connection with "adb devices" command and so on
when I tried to flash amons the first time I got an error saying it couldn't open the file.
I checked to see if i had Super user with the LED flashlight app and I did not so I downloaded Super boot and it worked like a charm
tried again and got the same cannot open error.
I renamed the recovery image back to the original file name and triple checked everything else which didnt help.
at this point it was late and i was exhausted so my memory is fuzzy
but i had a few more issues and finally I installed the clock work app and installed clockwork recovery i then used that to flash amons because that is what i was familiar with from my G1 days.
I do remember I had to go into fast boot and select clear storage. I think thats what caused my N1 to hang on reboot after the ROM was flashed.
But It may have even been what caused my issues with the recovery image.
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
Hello everyone,
So, one day my tablet decided to get stuck on Fastboot 123 etc.
I followed a method that used the fastboot flash osloader efilinux.efi and fastboot boot droidboot.img and then sideloading the official firmware, that fixed it. Worked fine for awhile.
Now, I haven't been using the tablet much, so after like a month I try and see if it still works, turn it on, and it boots straight into UEFI where I can't do anything.
So, I went into DNX mode by holding down all the buttons, do the commands above again, and it boots into droidboot where I can select recovery, the problem is after I hit "OK" on recovery, when the device reboots it goes straight back into UEFI mode.
I've been reading for hours now and some people fixed it doing the above, but they can actually reach recovery, I can't.
Where do I go from here? What can I try?
Everything is stock btw, never rooted or unlocked bootloader.
Thanks
What exactly is "UEFI mode"? Do you mean the UEFI setup page? If you can get into Fastboot/Droidboot I'd suggest that you load a temporary TWRP recovery session using https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and then install the full system backup from http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip
lambdadroid said:
What exactly is "UEFI mode"? Do you mean the UEFI setup page? If you can get into Fastboot/Droidboot I'd suggest that you load a temporary TWRP recovery session using https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 and then install the full system backup from http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.36-user.zip
Click to expand...
Click to collapse
Yes, the UEFI setup page where you can't do anything, looks like a windows bios.
Will try that, thank you.
Habz said:
Yes, the UEFI setup page where you can't do anything, looks like a windows bios.
Will try that, thank you.
Click to expand...
Click to collapse
It won't help much in this case, but FYI it is possible to navigate in the UEFI setup page but only if you have a powered USB OTG hub and attach an USB keyboard. You just can't navigate using touch controls.
no need for otg, its unnecessary.
Turn off the tablet, then press all the buttons at same time, it should boot to DnX mode.
Do fastboot flash osloader efilinux.efi (the .efi file should be inside the esp.zip that is present in .36 update
then do fastboot boot droidboot.img (found in .36 update)
then simply load temporary recovery session and flash stock rom.
Ruben Craveiro said:
no need for otg, its unnecessary.
Turn off the tablet, then press all the buttons at same time, it should boot to DnX mode.
Do fastboot flash osloader loader.efi (the .efi file should be inside the esp.zip that is present in .36 update
then do fastboot boot droidboot.img (found in .36 update)
then simply load temporary recovery session and flash stock rom, or if you have twrp, boot twrp normally and flash from there the latest .36
Click to expand...
Click to collapse
Will try that as well, thank you for the answers
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery
Code:
adb reboot recovery
. When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Which twrp you flashed? Check the correct twrp in my signature for honor 5C repository.
TassiloBalbo said:
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery . When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Click to expand...
Click to collapse
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
hassanjavaid8181 said:
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
Click to expand...
Click to collapse
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Meaning you can boot to fastboot but your pc doesn't recognise it?
Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Did you try all method to going in fastboot.by adb fastboot command or by pressing vol- and power button?
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Glad that you fix your device.
If it is not bothering you let it be and enjoy using your phone.
Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
TassiloBalbo said:
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
Click to expand...
Click to collapse
Try removing the usb cable and then try to biot to fastboot. What about erecovery
shashank1320 said:
Try removing the usb cable and then try to biot to fastboot. What about erecovery
Click to expand...
Click to collapse
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
TassiloBalbo said:
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
Click to expand...
Click to collapse
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
shashank1320 said:
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
Click to expand...
Click to collapse
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
TassiloBalbo said:
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
Click to expand...
Click to collapse
Meaning the fastboot is accessible.
Now you have firmware zip, extract it amd you will get few files. Use dload method as given in my signature and you are good to go.
Else use Huawei extractor and browse to update.app you just got in above downloaded zip. You will get boot, recovery, system img you need.
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
TassiloBalbo said:
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
Click to expand...
Click to collapse
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
shashank1320 said:
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
Click to expand...
Click to collapse
NEM-L31 but I don't know the build number
TassiloBalbo said:
NEM-L31 but I don't know the build number
Click to expand...
Click to collapse
Build number is necessary to get right files..
hassanjavaid8181 said:
Build number is necessary to get right files..
Click to expand...
Click to collapse
I know. So do you think it's dead?
TassiloBalbo said:
I know. So do you think it's dead?
Click to expand...
Click to collapse
You should try huawei service center....
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.