I guess I bricked my iconia...
I installed Recovery, etc. But when I rebooted my device it starts up, and shows my initial display screen. But it locks on the display (it is past the Android, and Acer screen).
So I tried to recover the device using the unbrick procedures described in this forum, and others. But it seems whenever it tries to process any update.zip file including the unbrick the little android man either stops turning or displays a sign indicating things did not work out as they should have.
I have clockwordmod backup from my system. How do I use that backup? When I use my phone the device automatically boots into xrecovery and allows me to restore. How do I get that with the Iconia?
first of all your device is not bricked as long as you can boot into any type of recovery.
second you obviously have cwm installed, but anyhow even if you don't have it i hope you have an external sd-card.
dl any of the stock rom's from the dev section, basically best is to choose the rom made for your country.
extract the update.zip and put it on your external sd-card.
then install it with cwm if you still have it, or with acer recovery (volume - and power simultaneously until the recovery text shows up).
and then take it from there.
also good idea is to clean dalvik cache and data cache before restarting if you use cwm.
then you can reinstall root and cwm.
zoubidou said:
first of all your device is not bricked as long as you can boot into any type of recovery.
second you obviously have cwm installed, but anyhow even if you don't have it i hope you have an external sd-card.
dl any of the stock rom's from the dev section, basically best is to choose the rom made for your country.
extract the update.zip and put it on your external sd-card.
then install it with cwm if you still have it, or with acer recovery (volume - and power simultaneously until the recovery text shows up).
and then take it from there.
also good idea is to clean dalvik cache and data cache before restarting if you use cwm.
then you can reinstall root and cwm.
Click to expand...
Click to collapse
Thanks... The problem is I can't boot into anything.
How do I boot into cwm? I can't boot into the operating system as once it hits the display screen with my picture the system freezes and tries to power down?
I have been playing around with acer recovery, but all of the updates I downloaded will not load onto the system. It tries to install, gets about 1/3 through and then gives me an error.
Hence why I was thinking that maybe my backup has something?
push volume - (left volume button) first and power and keep your fingers on it until it displays the recovery text message on top left of the screen
If you are getting into recovery. And flashing. A rom give you errors or does not complete. This issue is a bad d/load.or a bad currupt SD card.I would say format your SD card again.redownload the correct rom again.don't use a download manager.then decrypt. Unzip then put the update.zip on your SD card turn off your tab install SD card.
Reboot
Holding down volume up and power until you see the 4th line of txt. It should take you to cwr. Or flash your device
good luck
Yep.. use vol-down and power to boot into cwm. Keep holding vol-down until you see tiny white text in upper left corner.
Then do full restore. When it's done, if you don't see "Backup Succesfull!" message, you'll need to restore flexrom from the advanced restore menu. This is because it failed trying to restore .android_secure.img and caused cwm to restart before flextrom was restored.
Alternatively, you can delete the .android_secure.img file from your backup set before doing the full restore.
Good luck.
Sent from my A500 using Tapatalk
Thanks guys for all of your feedback.
However, when I hold down the buttons you mentioned I do get those text items you mention. The problem is that unlike my android phone it does not pop up the recovery menu. It goes straight into the Acer Recovery procedure (The android with turning gears).
Could it have been that upgrading to a specific ROM the recovery procedure is shortcircuited????
What I am trying to figure out is how to get the recovery menu.
Same deal!
I have the exact same issue. The Update.zip will not take and the Android Gears screen gets to 1/3 before the yellow triangle. Any further help would yield loud THANKS!
your update.zip should preferably be those 3.1 full. cos I believe it does not check anything for it to fail.
Thanks Kenny that does help and explain a few things.
Hey guys,
Last night, I unlocked, rooted (with perm cust recovery - TWRP) my N7 which was successful.
I installed custom ROMS and it was really doing great, until I made a mistake.
In TWRP, I accidentally formatted SYSTEM without having a ROM zip file to flash in the internal storage (/sdcard).
I restarted and it was just sitting in the google splashscreen (with unlock icon) - no matter how to I try to reboot it it was just going stuck there. I manged to make it boot to TWRP (press volume keys + power) again and tried to PUSH a rom using adb command line.
When I pushed a ROM file (Cookie's and Cream 1.0) as soon as I pressed enter, it looks like it is doing the push. But I've been waiting for 45 mins and it was still on the same progress, so I had to unplug it while it was doing that in the command line.
When I restarted, I tried to go to TWRP again but I can't anymore no matter what I do. So I had no choice but to reboot to bootloader instead.
This time I used the tools (nexus toolkit 1.5.3 (GUI) and the other version (2.0) in XDA - command line looking).
On both instances on both tools, when it is pushing - it just gets stuck with a blinkng cursor and it does not continue to the next step. As if the file is not being pushed.
There was also a point that when I go to recovery (i think it was stock), the android picture had a red triangle with exclamation point.
Anyway, I managed to make it work by manually by doing the guide [GUIDE] Flashing a Factory Image with fastboot / return to stock
Again, when i was doing it, when it is sending the image file to the N7 it was just stuck with a flashing cursor. I waited for 30 mins and when I rebooted, it WORKED - booted to N7 screen etc .. all good.
But I was worried why about that pushing error - maybe my Nand flash got borked like bad sectors etc? Is there a way for me to check if my flash storage is still good?
TL;DR
I messed up flashing a custom ROM on my N7 and accidentally formatted system. I managed to recover using recover to stock using fastboot and it worked.
Now, when I'm pushing files and it is big, it just gets stuck, either in recovery or when it is booted up.
Is there a way for me to check if I made badsectors or borked my internal flash storage?
So far everything looks fine but I just want to make sure since I still have 20 days to return it.
Thanks!
EDIT: When pushing from Recovery it says "error: protocol fault (no status)"
keplenk said:
Hey guys,
Last night, I unlocked, rooted (with perm cust recovery - TWRP) my N7 which was successful.
I installed custom ROMS and it was really doing great, until I made a mistake.
In TWRP, I accidentally formatted SYSTEM without having a ROM zip file to flash in the internal storage (/sdcard).
I restarted and it was just sitting in the google splashscreen (with unlock icon) - no matter how to I try to reboot it it was just going stuck there. I manged to make it boot to TWRP (press volume keys + power) again and tried to PUSH a rom using adb command line.
When I pushed a ROM file (Cookie's and Cream 1.0) as soon as I pressed enter, it looks like it is doing the push. But I've been waiting for 45 mins and it was still on the same progress, so I had to unplug it while it was doing that in the command line.
When I restarted, I tried to go to TWRP again but I can't anymore no matter what I do. So I had no choice but to reboot to bootloader instead.
This time I used the tools (nexus toolkit 1.5.3 (GUI) and the other version (2.0) in XDA - command line looking).
On both instances on both tools, when it is pushing - it just gets stuck with a blinkng cursor and it does not continue to the next step. As if the file is not being pushed.
There was also a point that when I go to recovery (i think it was stock), the android picture had a red triangle with exclamation point.
Anyway, I managed to make it work by manually by doing the guide [GUIDE] Flashing a Factory Image with fastboot / return to stock
Again, when i was doing it, when it is sending the image file to the N7 it was just stuck with a flashing cursor. I waited for 30 mins and when I rebooted, it WORKED - booted to N7 screen etc .. all good.
But I was worried why about that pushing error - maybe my Nand flash got borked like bad sectors etc? Is there a way for me to check if my flash storage is still good?
TL;DR
I messed up flashing a custom ROM on my N7 and accidentally formatted system. I managed to recover using recover to stock using fastboot and it worked.
Now, when I'm pushing files and it is big, it just gets stuck, either in recovery or when it is booted up.
Is there a way for me to check if I made badsectors or borked my internal flash storage?
So far everything looks fine but I just want to make sure since I still have 20 days to return it.
Thanks!
EDIT: When pushing from Recovery it says "error: protocol fault (no status)"
Click to expand...
Click to collapse
My computer did that in windows, but switching to Linux and it all worked fine for me
Sent from my Nexus 7 using xda premium
lbbooga said:
My computer did that in windows, but switching to Linux and it all worked fine for me
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks. Good thing I still have my Arch Linux box still up and running.
So is this a known issue?
Right now, I did it again and it worked.
It is like 80% chance it will get stuck while pushing thru adb and 20% it will just work successfully.
Just right now, I just did restore it using the tools. I didn't work for at least 5 times. The 6th time it worked. (Windows 64 bit)
I'm going to try linux and see if it will be better.
UPDATE:
It looks like it could be adb drivers in Windows.
OS X works fine. I haven't tried with Linux.
But is there a software to check if Flash storage has bad blocks?
Thanks!
Hi guys, getting kinda desperate here, appreciate any advice.
I've been mucking around with my phone trying to install some of the mod roms from here, but always get stuck in an endless reboot sequence or on the 'huawei' screen. Havent been able to get CM10.1 or 7 installed and working.
I have followed the instructions, including the partition size mod....
This is not my current issue, however, just the background.I was at a loss so after giving up last night I tried to copy b162 to my sd card, but was read only for some reason - showed up as CD rom on my PC.
Out of desperation I formatted the sd (in CWM) and tried again, but couldnt even get CWM, only pink or blue screen.
Pink screen I tried copied recover.img to the one available drive on my PC (windows), no luck. It copies over, but will not enter CWM with vol up + power.
Went out and bought a card reader this AM, have tried to install the stock roms B162 and B136.
I can copy the .app files to the SD card (root/dload), but my phone when going to pink screen does not start updating, just stays in pink screen.
Have formatted the card in windows (fat32) checked for errors etc. Does anyone know if the 'allocation file unit' during formatting makes a difference? I have left it as standard at 32kb....
The current rom boots as far as the animated huawei (splashing stars thing) logo then cycles.
Cant get shell access with ADB on pink or blue screen.
Never really used linux but Im willing to try anything to save my phone.
I have some experience with microcontrollers and think there are some jtag pads on the back of the phone that might be useful but am reluctant to try this as I fear I will make things worse....
Many thanks in advance!
To add ? volume label important?
Just managed to get into the stock recovery screen, selected 'apply update from sdcard and got reply 'failed to mount /sdcard (no such file or directory).
I cant swap out the recovery.img file in the purple screen, I dont have acess to that part of the memory from purple screen, perhaps wrong version of android on previous install?
Was wondering if volume label should be something? I just left it blank, and have tried again as 'sdcard' still no luck.
Thanks again....
OK I did a factory reset from within the stock recovery sftward (couldnt even get this before) and it will now boot heh.
Oh well, thanks for listening! Will have another crack at aurora now =)
AucklandMatt said:
Just managed to get into the stock recovery screen, selected 'apply update from sdcard and got reply 'failed to mount /sdcard (no such file or directory).
I cant swap out the recovery.img file in the purple screen, I dont have acess to that part of the memory from purple screen, perhaps wrong version of android on previous install?
Was wondering if volume label should be something? I just left it blank, and have tried again as 'sdcard' still no luck.
Thanks again....
OK I did a factory reset from within the stock recovery sftward (couldnt even get this before) and it will now boot heh.
Oh well, thanks for listening! Will have another crack at aurora now =)
Click to expand...
Click to collapse
so have you fixed ur phone sir ? tell me how to do that sir bcoz same problem here
Hi everybody.
TL;DR
Recovery hangs upon booting and fastboot mode doesn't show up ADB interface on my PC. How to flash the phone?
Long version:
I wonder if you can help me. My old faithful Note 3 is badly misbehaving. Yesterday I filled almost all its internal memory with some movies before heading out on a trip, but some time later when I reset the phone after unusually long boot all user settings were lost. Well, something went wrong, couple of hours later there was reset after reset so I wanted to restore previous backup... but couldn't. TWRP was showing error messages (TAR something something, 255) very shortly into restoring process. It couldn't restore backup but also couldn't make new one as well (similar error with TAR and code 255 when trying to backup user data).
Something was very wrong, so I thought maybe I will flash newer TWRP 3.0 and give it a try but suddenly after next reset I couldn't even get into recovery anymore - TWRP gives me black screen after several seconds into booting it. No icons, no reaction to key presses, nothing. Even holding power button does nothing.
Ooooookay, it's time to enter fastboot mode then and flash new recovery manually. So I enter it, connect phone to my laptop and... nothing! No ADB interface. Some kind of samsung driver is installing, but the most important one, for ADB, just doesn't show up. It's really weird. Reinstalling drivers doesn't help, only the same one device that shows up gets different names, but that's it - no ADB interface, and, effectively, I can't flash anything because fastbot and ADB can't see any device. Odin can't see the phone too.
What's going on? Is the internal flash dying or what? But if so what does it have to do with ADB not showing up? Do you have any ideas that I can try out in this situation? I checked my laptop with a tablet that I have on hand and it shows up its ADB interface without problem in fastboot mode even though it's the first time I connect it to this laptop, so laptop and it's system are fine.
If nothing helps then, well, One+ 3, here I come.
EDIT: Problem solved. Turns out f2fs on data partition crashed and therefore TWRP couldn't start at all. I managed to flash Philz CWM via Odin somehow (after messing with drivers for some more time) which told me there is something wrong with /data because it couldn't mount it at all. It couldn't format it either. Fortunately SlimLP managed to start and after throwing up some errors I managed to do factory reset which formatted the internal memory back to ext4. Then flashing TWRP, formatting data back to f2fs, restoring backup and voila! It works again. Good, I'll wait until Note 8 if there ever will be one.
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
jaysonic88 said:
I haven't run into this on my V20, but a couple times on my V10 when i'd softbricked my device and couldn't seem to revive it (even with ToT or KDZ files on LGUP) i was able to recover with LG bridge. Basically you go to the third tab titled "software update" but instead of selecting software update, select the "update error recovery" link at the bottom right. It takes awhile but i think it downloads and restores files (or maybe partitions) that other recovery methods don't. Give it a try and let us know if it worked.
Click to expand...
Click to collapse
LG Bridge doesn't see my device either =(
alane708 said:
LG Bridge doesn't see my device either =(
Click to expand...
Click to collapse
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
jaysonic88 said:
When you plug it in does it even show up in Device Manager on your computer? If so what does it show up as?
Click to expand...
Click to collapse
Yeah windows sees it as a Portable Device (Attached), I can transfer files to it.
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
slayerh4x said:
This is very similar to what happened to me, I couldn't get into TWRP though.
I could not find a resolution then and still havent, but I did return my phone for a new one.
Click to expand...
Click to collapse
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
alane708 said:
Now I wish it was hard bricked so I could exchange for new one.. I don't think they can do it now since it shows I modified it
Click to expand...
Click to collapse
Mine showed the bootloader message and they still took it back.
slayerh4x said:
Mine showed the bootloader message and they still took it back.
Click to expand...
Click to collapse
I guess I can only wait for a custom ROM now
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
mrbigdrawsz said:
I'm having the same issue. I've tried every step here. I've flashed multiple ROMS, just hoping one would boot and every one keeps booting right back into TWRP after showing the "your device software cannot be checked for corruption...".
PLEASE HELP! LOL...not sure what else to do. I'm, using the latest version of TWRP and I can get into bootloader.
Tried running the "EasyRecowvery.cmd" and it loads fine. I go into twrp and do the format data and then attempt to run any of the options and I get a "This Device doesn't look like a T-Mobile V20. Proceed anyway? I stop and can't get anything. But when it initially ran it said SUCCESS when locating adb .exe and found the device as well omni_h918.
No matter what it continues to go into TWRP. ANY ANY ANY additional help would be great. I want to return this device to T-Mobile before my 14 days is up. Please help out if you can.
Click to expand...
Click to collapse
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
alane708 said:
Hi Guys,
Long story short, I got the root to work at first, but I was having issues with PlayStore as I couldn't install most of the apps. Then I tried wipe data and restored TWRP backup which didn't fix the problem and lost SuperSU. I tried to reflash SuperSU and failed. Lastly, I did a factory reset via the OS's settings menu and my phone would never boot into System again. I tried using LGUP tool to flash the TOT tool, but it doesn't find my device. My phone is now officially softbricked. Any help is appreciated. I will donate if that is needed
Thanks
Click to expand...
Click to collapse
What variant are you using?
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
WishRyder said:
You, sir, are a lifesaver. I jumped through all the same hoops as you and was actually starting to panic a little, as the last time I got into a similar string of unsuccessful fixes, I managed to hard brick my Note 2. This worked like a charm on my Verizon variant (the backup part was seemingly unnecessary, as my backup was toast by this point). You definitely have my thanks!
Click to expand...
Click to collapse
Awesome. I was getting a little worried myself when I was stuck in TWRP because I was trying everything I could think of.
I didn't think the backup part was necessary but it's one of those things where you mention everything you did just in case.
check this out https://forum.xda-developers.com/v20/help/lg-v20-access-to-fastboot-t3557328
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
^ This 100% worked for me after my h918 got stuck in recovery after I got a system update message and accidently selected "reboot & install".
Thank you imucarmen!!!!:good::highfive:
OMG thank you so much. Merry Christmas to me. It worked like a charm. Tytyty
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had the same issue after rooting with Dirty Santa and have been sweating it for the past hour. Stumbled upon your solution and voila! THANK YOU!!
imucarmen said:
I had this issue on my Verizon variant the other day and I tried everything I could think of. I flashed roms, restored backups, redid the dirtysanta method several times, flashed the boot images in fastboot, and nothing worked. What finally did work (can't make any promises but this worked for me): steps below
*restore your full stock backup (if you have one)
*after the backup is restored, in TWRP, go to mount, and mount the system. Check the box and press the mount USB storage button
*power off device
*use the button combo to boot into TWRP. It's volume down + power, as soon as you see the LG logo let go of power for a breif moment and press and hold it until a white screen comes up. Choose yes for the next two options. This will bring you back into TWRP.
*now go back to mount and check system, and press the mount button, and reboot system.
This got me out of TWRP and booting normally. I haven't had an issue since.
Click to expand...
Click to collapse
I had some trouble following this at first but it indeed worked.
My v20 was stuck in TWRP (3.0.2-1) after forgetfully hitting OK on the System Update, it was running H91810q and was previously rooted.
I first backed up my phone in TWRP to my SD card and then copied that to my laptop.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
I held Power+VolumeDown, released Power while still holding volume down and I got the white Factory data reset screen. I choose Yes on the next two options to perform the factory reset.
Then it restarted and went back into TWRP. I choose Mount, selected System, pressed Mount USB Storage, then Unmount, Reboot, System.
It booted and took a while since I also flashed the H91810t rom to do an upgrade at the same time from here:
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
0m3ga said:
I had some trouble following this at first but it indeed worked.
In TWRP: Mount > System, I have 3 buttons on the bottom: 'Mount USB Storage', 'Select Storage', and 'Disable MTP'. If I choose 'Mount USB Storage' it goes to the next screen and the only button is Unmount. I cannot get it to shutdown without pulling the battery.
What is missing here is to press Unmount go back to the main TWRP menu, then Reboot > Power Off.
https://forum.xda-developers.com/v20/development/rom-h91810q-stock-rom-twrp-flashable-zip-t3681312
Interesting all my apps, and settings were still on the phone.
THANK YOU FOR SAVING MY PHONE, TIME AND $ !!!
Click to expand...
Click to collapse
Glad you got it working. As far as the issue with the instructions that could be down to a change in the newer versions of TWRP. I posted this 16 months ago and many new versions of TWRP have come out since. I remember trying to be extremely accurate in my instructions but it is possible I screwed up. Been too long ago and I can't remember now.