I was trying to install Cyanogen Mod using the steps on their site(cant post the link because I am under 10 posts)
When i got to these steps 6 and 7 under installing recovery is when my TF201 appears to have become bricked
6. Flash recovery onto your device by entering the following command: fastboot -i 0xb05 flash recovery your_recovery_image.img where the latter part is the name of the file you downloaded.
7. Once the flash completes successfully, reboot the device into recovery to verify the installation.
Note: Some ROMs overwrite recovery at boot time so if you do not plan to immediately boot into recovery to install CyanogenMod, please be aware that this may overwrite your custom recovery with the stock one.
I had just run the command in step 6 and rebooted the device as described in step 7. Now my device cant even reboot. I cant get it into recovery or fastmode because holding the volume and power button does not do anything, the tablet just stays stuck on the boot menu. I had unlocked the tablet with Asus' tool earlier today so I can see the "The Devices is Unlocked." message at the top left. Any help would be much appreciated if it is possible to fix this issue without sending it to ASUS(because they will probably end up charging more than the tablet is worth in repair fees).
Some information: Before all this it was running Stock Jelly Bean 4.1.1
thanks
some more info.
I can see an APX device with a yellow exclamation mark under "Other Devices" in windows Device manager. Fastboot and ADB do no recognize any devices
Related
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
Download and install "minimal adb and fastboot"
Just type on the command line without pressing Enter:
Code:
[COLOR="Blue"][B][I]fastboot [COLOR="Plum"][STRIKE]boot[/STRIKE][/COLOR] recovery.img[/I][/B][/COLOR]
you should place your recovery image file in "minimal adb and fastboot" directory
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds - in my case the phone is restarting)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery command line
Click to expand...
Click to collapse
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
i must extract "flashrec TWRP v2.7.1.2 this file on phone or where? can u explain a
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Please explain me. idont know how to do
prxzero said:
Please explain me. idont know how to do
Click to expand...
Click to collapse
What Is your problem?
Is your phone stuck on logo screen? what were you doing to get the problem??
agsao said:
First of all I would thank Crowds he is the best reference that I've to return in case of any problem I face. (He doesn't sleep - any time I ask he immediately supports)
I bought Lenovo K910 and I've managed successfully to install new ROM "VIBEUI_v2.0_1443" and Gapps with Crowds support.
I advised two of my friends to buy this good and cheap phone. For one of them I installed the latest rom successfully. But with the other I had a big problem The phone stuck on Lenovo Logo.
I was trying to install TWRP 2.7.0.0 batch before installing my new ROM, but during installation and after the phone rebooting the batch command screen shows <Waiting for Device> and the phone is stuck on logo screen.
I tried to connect the phone to PC many times, but PC doesn't recognize the phone. When I try to turn off the phone by pressing the power buttons, the phone restart on logo screen like the shown in this video.
I've read in many site that I have to do the following:
In my case when I press and hold power button the phone is restarting on logo screen so I have to wait for battery consumption
I tried many times with TWRP images but it failed...
I tried with CWM image and it succeeded to load, but I don't have otg cable to load recovery or ROM from usb storage (The problem was in installing TWRP and my ROM should has no problem)
I want to flash TWRP on phone not only loading by "minimal adb and fastboot".
I decided to flash TWRP 2.7.1.2 batch through modifying the batch file. I just used fastboot commands
Code:
[COLOR="blue"][I]fastboot oem device-info
fastboot oem unlock
fastboot oem device-info
fastboot [COLOR="Red"][U][B]flash[/B][/U][/COLOR] recovery data/recovery.img
fastboot flash aboot data/lock/emmc_appsboot.mbn
fastboot flash rpm data/lock/rpm.mbn
fastboot flash sbl1 data/lock/sbl1.mbn
fastboot flash dbi data/lock/sdi.mbn
fastboot flash tz data/lock/tz.mbn
fastboot reboot[/I][/COLOR]
Finally I succeeded to install Recovery and phone works well in the new recovery mode and the system mode that I've not update it yet
I want to share you the problem solution in brief:
Download and extract this file "flashrec TWRP v2.7.1.2" from here
Just select without executing "flashrec_Modified.bat" file from the extracted files.
The phone should be disconnected from computer and completely off (press the Power button for 10 seconds or wait for the battery to be almost empty)
Press and hold both volume buttons, then connect the cable to the PC.
Once the phone vibrate, press Enter to execute the recovery batch file
and as me the phone start the recovery mode in TWRP and can be rebooted in system without any problem
Click to expand...
Click to collapse
Hi..
i just try to install CM12 to this device, with twrp 2.8.6.1 from master lie.
First time its working well, but suddenly this device restarting and stuck on the "lenovo" logo screen.
Every time i presh power button always restarting (like ON-OFF-ON-OFF forever).
when i connectto charger also restarting....
i cant go to twrp using vol- & pwr, when i use minimal adb cannot detected..
Can you help me...
Help
hi.
i try to do something to enable notifications on my lenovo vibe z.
i install new rom from needrom, but it didn't help. So i try to install other one, but i wipe my phone and restart without installed system.
Now when i go to twrp have just flashing teamwin logo, and only when phone is in this mode i can communicate through adb
i have checked many forums and try allot stuff to fix it but nothing works
Please Help!
U are not alone I also in same stage
Is there any one plz help
As long as the hardware is not physically broken, your K910 is unbrickable
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
nowbo said:
Is there any one plz help
Click to expand...
Click to collapse
Thanks for your reply
I will apply today. Hope for the best.
Will inform you as soon as this applied..
Have you fixed that problem?
Still at same stage
EcoDan said:
Have you fixed that problem?
Click to expand...
Click to collapse
Hi,
I am still on same stage (Black screen with lenovo logo). Try several ways but can't get out of this. Please help me If any one successful to startup this device or can get on the boot screen where I can do factory reset.
---------- Post added at 07:25 AM ---------- Previous post was at 07:21 AM ----------
wxppro said:
http://www.teamsuperluminal.org/unbrick-lenovo-k910/
I followed the guide to revive my K910. You can refer to this forum post in which I documented my experiences:
http://www.teamsuperluminal.org/forums/topic/flash-back-to-lenovo-stock-just-temporarily/
Click to expand...
Click to collapse
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks
[/COLOR]
I Try this method but can't get out from that black screen ( Lenovo logo and powered by android)
My device is Lenovo Vibe shot Z90a40. I also try with boot unlock-er but nothing sitll work. So its about 20 days can't use my Lenovo Vibe Shot.
Please help me If you know how to get out of this issue..
Thanks[/QUOTE]
You need to carefully follow each steps in the method - if you short that magic pin and then connect the USB cable (with battery disconnected), your computer will report seeing the device at either COM port 9008 or 9006. Then you can download the factory image to revive the phone. Of course you need to have the right device driver installed. Like I said, as long as the hardware is not broken, this procedure will succeed for sure.
I love you man!
I love you man! I wish you all the happiness and wealth!:victory::victory::victory::angel::angel::highfive::highfive:
I have a Nexus 9 Wi-Fi model, my PC runs Windows 8.1, and I am not new to rooting and custom ROMs. I attempted to install the M dev preview to the tablet following the instructions on Google's site. In the process, my console window showed one of the instances of "sending sparse 'system'" had FAILED. Now the device will not boot. It is stuck on the white Google logo splash screen. ADB does not recognize it, although it does appear in Windows Device Manager as "MTP USB Device". When I attempt to turn the device off or reboot it using any combination of power and volume keys, the screen will go blank for a few seconds and then return to the Google logo. I cannot turn the device off.
I've never seen this before, even with a failed flash... it's supposedly just the system partition that failed, anyway. Any ideas how I can break free of this?
EDIT: I ended up locating this post. If I hold the power button down until the screen turns off and then immediately press and hold power+voldn, it will launch the bootloader.
I've no experience with flashing M. But I have a suspicion that you flash of the system.img failed because of an obsolete fastboot on your PC. I'd suggest starting by updating your Android SDK. Then you can try fastboot flashing the M system.img again. Or fastboot flash the stock 5.1.1/factory image to return to stock.
soft bricked is all it is.
Made sure I had the latest Fastboot, ADB
Rebooted into Fastboot
Ran the Flash All batch file and it failed to install the System
I found instructions on flashing manually this from what was post is very common.
You extract all files, flash the boot, reset, and flash all the others.
Do a Google search it was easy enough to find.
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
Usually when it hangs at the Nabi logo it means you don't have the USB cable plugged in or that the fastboot driver is not installed.(Check device manager and see if fastboot driver is installed/no exclimation point). If that's not the issue then it's the bootloader which I have only seen one person have that issue. Depending on which OTA's you have ran there was an update to a Jellybean bootloader so it's possible. That can be fixed with nvflash or placing the bootloader blob in the staging partition.
Also you can always get recovery back without fastboot in Android by dd'ing the recovery over.
For example if the recovery image is on the internal SD
dd if=/data/media/recovery.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
Click to expand...
Click to collapse
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
najman9 said:
I have searched a lot on google and xda and havn't found an answer to my issue. Either I'm searching for the wrong thing or I have a very unique problem.
My basic problem is on two Nabi 2's I can't access the bootloader in order to be able to fastboot TWRP (or any other recovery). It just perpetually hangs.
Both tablets boot just fine. Both tablets are on 1.9.37. Both tablets can be factory wiped via the stock recovery.
Both tablets were rooted via TWRP 2.3.3.0 a few years ago in order to install gapps. I wanted to be able to upgrade the tablets to JB when it came out so I used Nabilablite to "return to stock". I followed all of the prompts and it appeared as though everything worked as desired. I downloaded the OTA update told it to install and never looked at the version again...I just assumed it installed. Handed the tablets back to the kids and everyone was happy. Apparently all I did was flash the stock recovery because they are still rooted and have gapps after several factory resets.
Now (a year later) I have realized I was a dufas and didn't actually effect the change I wanted.
If I hold Vol+ & Pwr buttons it loads to the recovery/boot menu with "boot normally" "fastboot protocol" "recovery kernal" and "forced recovery". If I boot normal, the tablet works fine but I can't update via OTA.
If I choose fastboot protocol it just hangs...for ever...HOW DO I FIX THIS!?!?!
If I choose recovery kernal it loads the stock recovery but still wont install any update OTA or otherwise, even from the sd card.
If I choose forced recovery nothing happens, it also appears to just hang.
If I hold Vol- & Pwr button the nabi logo flashes then the device turns off.
If I hold Vol+ & Vol- & Pwr buttons it appears to be the same as just Vol+ & Pwr.
With the tablet on and fully booted I can see it via ADB. I tried using the adb restart bootloader. The tablet reboots but then just hangs never actually loading the boot loader...
I found http://forum.xda-developers.com/showthread.php?t=2587543. But aicjofs mentions seeing a bootloader issue once before.
I have NO idea what dd'ing the recover over is...
Thank you for any help fixing this.
P.S. I have a 3rd tablet that I also used TWRP 2.3.3.0 on to root and install gapps with. I did NOT use nabilablite on that tablet to return to stock. Yesturday I used fastboot to flash TWRP 2.6(something) to flash a JB OTA update which worked fine. It was also able to download and install every other OTA update all the way to the most recent KK with no problems...
Click to expand...
Click to collapse
EDIT: OOOPPS. I didn't see this was in the XDA Assist section. I'm not suppose to answer questions(I was just searching for Nabi questions and didn't notice this was XDA assist), dedicated XDAers just point you in the right direction in this section. Please ask the question again in the Nabi2 section and I'l come help you. http://forum.xda-developers.com/nabi-2
This might help answer some questions http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
If it just hangs at fastboot protocol then the USB connection isn't good or fastboot driver isn't installed most of the time. Can you verify fastboot shows up in device manager?(I know the 3rd tabet worked OK) .
Nabilabite doesn't do anything that should change the bootloader, and fastboot should still work as it did before.
dd'ing recovery over means that you use the root access you have in Android to flash the recovery partition instead of using fastboot. IT's just another way of getting the TWRP recovery on the tablet.
The stock recovery won't install the OTA because when you added Gapps it changed some fies and the OTA sees those files as invalid and will fail.
Forced recovery always looks blank screen. It's waiting for you to give it a bootloader to run(beyond the scope here).
You should be able to get back on track once you have TWRP loaded. It's one of 3 things. Bad USB connection, fastboot driver not installed right, bootloader damage. Check the first 2 issues despite the fact the 3rd tablet had no such problems.
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
najman9 said:
One of the XDA smart guys fixed my error of posting this in the wrong section.
I'm running Windows 7 Ultimate and have installed and re-installed the drivers several times. When the tablet's are fully booted ADB has a good connection and sucessfully sends the command to reboot. So I don't believe there is a driver or USB cable error...
When the tablets hang on the fastboot protocol my computer makes the usb connecting noise but fails to install the drivers...
When I hit forced recovery I hear the unrecognized USB device sound...
These two things make me think I don't have the proper drivers installed...but I don't understand how the driver's work when the tablet is booted but not when trying to access the boot loader.
It appears as though I'm going to have to try the dd method if you are able to point me in that direction please.
EDIT: Now I'm thinking I really DON'T have the fastboot drivers installed. I just plugged the 2nd tablet that hands on the fastboot menu and fastboot failed. I also booted the tablet completly, the adb driver's installed correctly but the fastboot driver's did not...I have installed the 64 bit driver's included with nabilablite. I can't find any actual other downloads. The 15 second ADB installer didn't change anything...
Click to expand...
Click to collapse
Uninstall those nablablite and try this one. http://forum.xda-developers.com/showpost.php?p=62826514&postcount=2639
Or look at the other options in section 4 here http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
Hey, I have an Archos Helium 45 that I put a custom ROM on a while ago, but today decided to revert to the stock ROM because it was having some issues. I must have done something wrong though, and softbricked my phone. Now this would be no problem if only I could enter recovery mode, however when I boot up my phone holding down the +volume and power button, all I get is a green screen, which is the fastboot mode. On this screen there is nothing I can select (just seems to be some tiny tiny white, unreadable text on the top). I'm guessing this is because I installed TWRP over the regular recovery.
When I first installed the custom ROM, I did something wrong and softbricked my phone too, and had the same problem of not being able to select anything on the green screen, but then I was able to use the command 'adb reboot recovery' via the PC to boot into recovery mode. However, now this does not work anymore, and when using 'adb devices', it returns an empty list. I still do get a code when using 'fastboot devices' though.
Does anyone have any solution to boot into recovery mode from the fastboot mode?
I read somewhere that I could try flashing the img files from the original ROM via fastboot one by one, however the only img file in ROM's zip file is boot.img.
I also tried updating the ROM using 'fastboot update update.zip' but then it says
Code:
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt
Edit: Never mind, right after creating this thread I found out I could enter recovery mode simply by continuing to hold the +volume button and releasing the power button after the green screen... (and I also plugged it into my computer right when TWRP started, don't know if this was a requirement or coincidence) **** I spent all day looking for a fix and ended up finding it just by trying something.
I'm having issues with the stock ROM though, but at least I can install an other custom ROM and have a working phone.
Hi all,
Well, operator error is definitely at fault here... I made a series of mistakes that got me to where I am now. All I intended on doing was repairing my dad's tablet which was running atrociously slowly. I tried to follow some steps, but improvised as I was getting errors and obviously ended up making things a lot worse...
Now tuning on the tablet will directly go to a command line interface with a long series of errors and these are the last 2 lines:
Rich (BB code):
blkD :HardDisk - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0) /HD(14,GPT,80868086-8086-8086-8086-000000000008,0x646828,0x16D47D8)
blkE :BlockDevice - Alias (null)
PciRoot (0x0) /Pci (0x17,0x0) Ctrl (0x0)
Press ESC in 1 seconds to skip startup.nsh, any other key to continue.
Shell> _
In this state it cannot be interacted with and won't be detected by my PC over USB.
This happens for normal, recovery and bootloader modes. The only mode that I can access is DNX mode but attempting to boot droidboot will result in the same command line UI described above, including when trying to restore the BIOS using the PC executable (which I assume needs to enter fastboot mode, which it can't do...).
What can I do now? Any way to get anything working in the above screen or through DNX?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp.img when all I have access to on the tablet is DNX mode?
Detailed history below...:
HISTORY
1)
The tablet is a Lenovo Yoga Tab 2 1050F. It was running very slowly to the point where my dad just didn't bother to use it. I thought it would be wise to factory reset it as a first step. There is no option to do so within the Lenovo skin of Android so I started by going into recovery mode and performed a factory reset from there.
After it rebooted, the Android UI would loop back to the language selection after connecting to a WiFi network and I would get "Unfortunately Google Play Services has stopped." error message. It would just loop through the Language Selection > Connect to WiFi network pages over and over.
2)
Having installed CM on my old S3 back in the day, I thought I could go about the same process and flash a gapps ZIP file in recovery mode. That didn't work, I got an error because the zip was unsigned.
I thought I could install TWRP to flash unsigned zips, reinstall Gapps and get the tablet passed the Android UI loop.
3)
I followed this guide on XDA to install an unofficial TWRP (which involved unlocking the bootloader). It didn't work because I couldn't flash over ADB (because the tablet couldn't allow Developer Mode since it was stuck in the Android UI loop). So I flashed as many files as I could in fastboot.
I eventually flashed the TWRP recovery.img but that didn't work : when turning on to Recovery mode it would just go back to the bootloader screen.
4)
I thought I must have screwed up something up so I tried to restore the BIOS using an executable I found but I realized the tablet was already upgraded to Lollipop and the only BIOS restoration exe was for Kitkat. Sure enough it got even worse and I could no longer boot Android.
5)
I still had bootloader and fastboot though so I followed a guide to restore the tablet to the original OS (which ironically I already downloaded before trying to get TWRP but forgot about and didn't unpack). I set up Intel Platform Tools but the flash process didn't work because it went to droidboot and then lost USB connection. On the Intel program it would just stay stuck at 20% Wiping ESP. It would time out twice and then give me a final error message.
6)
So I thought to explore the flash.xml file provided to see if I could do the steps manually. I knew it was stuck at wipe ESP because in droidboot it couldn't get commands from PC. So I went into fastboot and wiped ESP manually myself! Little did I know how foolish this was to do because I was simply unable to flash the provided ESP.img again. Following this I lost access to the bootloader.
7)
I found a guide to restore a bricked 1050F here on XDA but it needs droidboot which now goes to the command line UI described at the top of this post. When attempting to restore the kitkat BIOS again, droidboot is also needed which results in the same cmd UI.
8)
Which leads me to where I am now which is that the tablet doesn't boot to: normal, recovery, bootloader/fastboot or droidboot. Which is why I am now asking for help. What can I do?
I'm thinking that a partition was corrupt in addition to me wiping the ESP is causing this. Maybe it's possible to completely format and setup all the partitions and start from scratch again? How can I flash esp when all I can get access to is DNX mode?
Thanks for reading this far and if you have any more ideas, please let me know, thanks in advance.
Hi, would anyone like to weigh in on this issue?