176C Stuck on UEFI, Need some help - MeMO Pad 7 Q&A, Help & Troubleshooting

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

Related

Every option in recovery mode loads fastboot

So I recently tried to flash TWRP onto my HTC 626 and it seems like everything went well except a completely random group of inputs just loads my phone into fastboot list as follows:
Trying to enter recovery mode from menus
Trying to enter recovery mode from adb
Trying to perform a factory reset from menus
Plugging the device into a pc while powered off
The phone can still boot into the os and it runs just like normal. I have been frantically googling the problem but I have no idea what is going on.
I would have just done a reset but it just loads into fastboot.
DrLolCat said:
So I recently tried to flash TWRP onto my HTC 626 and it seems like everything went well except a completely random group of inputs just loads my phone into fastboot list as follows:
Trying to enter recovery mode from menus
Trying to enter recovery mode from adb
Trying to perform a factory reset from menus
Plugging the device into a pc while powered off
The phone can still boot into the os and it runs just like normal. I have been frantically googling the problem but I have no idea what is going on.
I would have just done a reset but it just loads into fastboot.
Click to expand...
Click to collapse
Guess what? I just might be able to save the day, mighty mouse style. Are you ready for this?
Try this out and see if it works for you like it worked for me.
But before you do this, I am on the MM-update android 6.0.1...this was what I used for this particular os. If you've update to Marshmallow already, please continue with the following......
Download these files first to your pc.
Twrp recovery - https://goo.gl/sO4Huz
BETA-SuperSU-v2.62 - https://www.androidfilehost.com/?fid=24269982087018189
Credit to my buddy IsaacGuti for the files.
fastboot flash the recovery
Make sure to either rename the Twrp recovery image to "recovery.img" before flashing or be sure to type the exact name of the twrp image file name verbatim. I'd suggest renaming it to "recovery.img just to be on the safe side.
in command prompt, it should look like this when you type it in "fastboot flash recovery recovery.img" without the parenthesis
( "<----These guys to the left....don't add those in)
To make it easier, just copy and paste what's in the parenthesis into the command prompt.
flash the supersu.zip in recovery. (Meaning after the flashing of the recovery is successful, then reboot into TWRP recovery to flash BETA-SuperSU-v2.62) But Don't forget to move the BETA-SuperSU file to your internal sd on your device.
If you've done all of this, you should have success. Just send me a virtual HI-5 and we're all good:highfive:

Need Help. ADB, Recovery and Fastboot/Download Mode don't work

Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
Click to expand...
Click to collapse
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Try connecting your phone to usb and then holding power+volume down until it boots to fastboot mode.
Huawei phone won't boot into recovery if system and twrp don't match but it should boot to fastboot allways.
What is the last rom you had on your phone while it was working?
Ogameplayer said:
Hey xda community,
last night i run into a tricky situation.
First, I explain what I did
I bought me the P9 EVA-L09 via Telekom Germany.
cause i don't want the Telekom **** on my device i decide to TWRP, Root, and flash P9 stock Rom on it.
Unlocking and install TWRP with the SRK Tool works fine. Install the Root was a bit more tricky, because windows lost the correct ADB connection when i go into TWRP Sideload Mode. Because that does not work, i decide to flash the P9 Stock ROM without Root to come forward.
While flashing, (i don''t now anymore which method i choose to flash) an error appers, and the flash process canceled.
The Device don't boot anymore. After a loot of googeling and testing, i've found out that the problem was the encryption of the /Data Partition.
TWRP was unable to mount it, same for the /cust and one more.
After reading about other Methods to get the Phone work again i try this Method i've found on xda.
http://forum.xda-developers.com/p9/development/stock-rom-dload-file-p9-eva-l09-b136-t3382818
Unfortunately the "press all buttons on the phone" Method don't work.
I also tried out the Huawei Update Extractor to flash single image files to the partitons of the phone. I used the dload file form the previous Method
http://forum.xda-developers.com/showthread.php?t=2433454
http://www.modaco.com/forums/topic/372688-re-partition-stock-partition-tool/ (using the answer on the bottom)
Download from xda huawei update extractor and extract img files from the update.
Turn off the phone, then press vol- and power key, you are in fastboot mode.
Then, flash img files from extracted rom with:
Fastboot flash system SYSTEM.IMG
fastboot flash boot BOOT.IMG
And do the same with the others...
When you finish, fastboot reboot
But that don't work. fastboot already replies with "Remote Command not allowed"
i changed the Method a bit. I've put the BOOT.IMG and RECOVERY.IMG an an SD card and flash it via the Install IMG Funktion of TWRP.
That workes very well and expect the /data partition every partition was mountable again.
Then i used the "Fastboot flash system SYSTEM.IMG" again, and tada it works without errors.
The device is booting again to Android, but it reports that the /Data Partition Decryption failed and i have to enter the Recovery Mode and do a factory reset to unlock the partition. If i reboot for get rid of this error the phone does not boot into the Recovery, it boot to the eRecovery which is useless for that because it only provide the eRecovery function instead of also a normal factory reset (how dump is this )
Now the state is, phone boots normal, reports the /Data is not decryptable, reboot to eRecovery, shutdown or reboot. It does really nothing else.
I can't get into the Fastboot/Download Mode, it ignores the Key Combination Volume down + Power. If i press this it starts normal.
I also can't get into the recovery / TWRP Mode, it ignores the Key Combination Volume Up + Power. If i press this is starts normal.
I've also noticed that the Phone is not conecting to the ADB on my computer, only the virtual CDROM from wich the HiSuite is installable connects.
I've also noticed that the eRecovery is not able to starts WIFI on the phone. It errors with "Starting WIFI failed!"
I also tryed out another time the dload function. This changed nothing. Phone boots still normal and run into the Decryption problem.
And i tried out to boot into fastboot or recovery after a cold reset, battery empty
Now it's on you. Has anybody an idea how i can solve one of the above problems. I think when one is solved the others will disappear via flashing new TWRP or so
Click to expand...
Click to collapse
Try this.
http://forum.xda-developers.com/p9/how-to/tools-huawei-p9-firmware-updater-t3432457/page1
Sent from my HUAWEI VIE-L29 using XDA Labs
I see two possibilites for this behavior:
1) The phone only pretents to reboot but makes a kind of warm start (never running the code to branch to recovery/boot) -> if the phone seems powered off and you attach usb cable, do you see standard battery laoding animation (that's what it should be) or black screen / boot logo?
2) You flashed a wrong boot.img and/or recovery.img or flashing got screwed up
If you have wrong images, fastboot should still work as edint3000 said.
For the unlikely case (1) with non removable battery you have to wait until battery is drained before you can boot into fastboot after connecting USB cable. Edit: oops just saw you did that.
I had another phone that at some point decided to go only in fastboot with volume down and no power button, when powered up with USB power. But I had never such an issue with a Huawei phone. However, playing around a bit costs nothing (but time).
I see no reason why fast boot should not work. How did you find out, that everything is fine after flahing with TWRP and before flashing system with fastboot?
Did you do anything else than flashing the system.img with fastboot?
Chilli
Same problem here...Phone not boot/not enter fastboot mode/not enter recovery mode...just stuck "your device booting now" screen...any solution?
Hello Mossyhand
you should search for the recovery Method with an "dload" ROM. This are kind of special Roms wich are able to "selfflash" onto the phone.
You have to put the right file onto your SD Card and then you have to press some keys when i remember right.
Sadly i've forgot, when i solved my problem, to reply how i did that exactly ._.
But if you do search in the dload method you will figure a way out i guess
If you don't find an right file, i can upload you my file, i have it still on my computer
had the same problem
go into the erecovery, it will tell you the data partition has been damaged. u can wipe it from there. go into trwp again, install rom and stuff. voila, works
cheers

Op3t fastboot cannot install twrp

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

Moto e 4 issue with recovery and other

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.

Question Phone stuck in boot loop, unable to get to FastBoot

Hi,
Sequence of steps:
1. Extracted the boot.img from payload.bin and flashed it to the phone. At this point I was able to get into Fastboot
2. While in Fastboot I went into advanced and wiped the "System Settings", and that's when the trouble started - now the phone is stuck into a boot loop forever, I do however get the options to "Power Off" and "Restart"
3. But none of the options above in Step 2 is able to bring me back to Fastboot (and hence into fastbootd either)
Question: How can I get the phone into Fastboot Mode - have tried MSM Tool v4 as well, but that doesn't even recognize the phone
Edit - This seems to have been resolved now, think I had to press Vol Down + Power instead of Vol Up + Power
Was able to enter into Fastbootd as well, will try to proceed with unbricking the phone with a fresh mind tomorrow
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
VoltaGe86 said:
FYI for others reading I was able to install magisk by booting the patched file (dump the payload using the python script mentioned above). Running the command Fastboot boot filename boots into the operating system and then magisk can be installed using the direct method.
I assume running this command the phone doesn't actually flash the boot image but could be wrong
Click to expand...
Click to collapse
Thats right, "fastboot boot <file_name>" loads temporarily your custom recovery of choice. After rebooting your phone, the custome recovery is gone.
Otherwise, the command "fastboot flash <file_name> recovery" flashs permamently your custom recovery of choice to your device.
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Zekedw said:
Hi I have a oneplus 8t and I tried flashing a payload.bin file using fastboot enhanced. after the operation completed I tried to reboot but the phone only shows the logo and then the bootloader unlocked warning message and then turns off briefly, then it does it again and the screen goes black. When connected to the PC, the PC recognizes the devices as android adb recovery devices but i can't do anything from there. Tried the volume up+power combo and it just does the same thing. tried the volume down+power combo and absolutely nothing happens. If i could at least get to the bootloader I could unbrick it but I just can't get there. Any advice
Click to expand...
Click to collapse
I have exactly the same issue, on a nord 2
How about vol+/vol-&power all together? When stuck that gives me some screen that allows start, recovery (the one where you can enter advanced settings I expect from your description) and bootloader booting.

Categories

Resources