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?
Related
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
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
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
dgindra said:
Device: Nexus 9 (Wi-Fi), Bootloader Unlocked
Computer: Windows 10 (Bootcamp on a Retina MacBook Pro)
After and unsuccessful attempt to install CM 12.1 on my Nexus 9 (Wi-Fi) using TWRP, I tried using this method to return to stock:
http://forum.xda-developers.com/nexus-9/general/guide-nexus-9-to-stock-guide-unbrick-t2975668/
I thought it had worked perfectly, but the tablet still would not boot. I went back and looked at the command prompt log and realized I had made a grave error: I had flashed everything except for the system image. I re-entered fastboot in an attempt to fix it by flashing the system, but now the tablet will not connect to my computer at all. I have tried to remove and reinstall the ADB drivers, but it doesn't show up at all in Device Manager. I tried booting into recovery via fastboot, but got an image of the android mascot knocked-out with an exclamation point, presumably since I over-wrote it with the method above.
Any ideas on how to restore the fastboot/adb connection with my computer? If I can accomplish that I can presumably just flash the system image and that would restore the stock ROM.
Any insight at all would be much appreciated.
Click to expand...
Click to collapse
Hello,
I have reported this thread to be moved to right Q&A section in order to get expertise help.
-Vatsal
Have you ever tried to connect your tablet to another computer?
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
dgindra said:
Turns out I forgot to actually press the button in fastboot that enables the USB connection (I feel even more stupid now). Was able to return to stock, albeit with the "This device is corrupt" message during boot.
Click to expand...
Click to collapse
I got the same message yesterday after I returned to stock kernel from a custom one. What I did to get rid of that warning message was to flash all img file(boot, cache, recovery, system, vendor) in MMB29K factory image. (Bootloader is optional) [After that I also performed a factory reset but this step might be unnecessary, do it if the message still exist after flashing stock images] If you don't like that warning you can try these procedures.
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !