Lenovo Tab2 A10-30 (tb2-x103f), I have messed it up. - General Questions and Answers

Hi all,
When installing TWRP on my daughters tablet I have accidentally flashed boot instead of the recovery with the TWRP image on the tablet using fastboot.
After I realised the error I have flashed TWRP to the recovery partition and rebooted the tablet to access TWRP.
When I was in TWRP I have wiped the data partition and flashed the lineage os rom for this tablet.
First error I noticed was E: legacy property environment did not init successfully, properties may not be detected.
Installation appeared to run properly but in the end I got a lot of E:Unable to stat '/data/.........' messages.
When rebooting TWRP asks to install SuperSu which also shows the same kind of error messages.
At startup I get the Lenovo logo and afterwards only a black screen which is turned on (in the dark you can see that it is active)
I am currently unable to access the fastboot environment, when rebooting using power and volume down it looks like the tablet is in fastboot mode, but when connected to the laptop it shows up as MTP device.
Fastboot or adb itself does not show any connected devices.
When rebooting after the Format data option in TWRP and installing an image I get the following errors :
E:Unable to find partition size for '/recovery,
E:Mount: Unable to find partition for path '/emmc'
E:UnMount: Unable to find partition for path '/emmc'
E:Mount: Unable to find partition for path '/emmc'
I have tried to flash the tablet back to stock rom with the Lenovo/Qualcomm downloader tool but that tool hangs at the Sahara stage and does not proceed after detecting the tablet.
Does anyone have an idea I can try or is the tablet bricked ?
TWRP version is 2.8.7.0 and I am able to access the recovery.
ROM's tried are lineage-14.1-20170520-UNOFFICIAL-x103f.zip and RR-N-v5.8.5-20171113-x103f-Unofficial.zip
USB debugging and bootloader were unlocked in the developer options on the tablet.
I ave rebooted to the bootloader from TWRP after trying another flash, still having a black screen.
In device manager I am now showing Lenovo-HS-USB Diagnostics (COM20), Lenovo HS-USB NMEA (COM21) and Lenovo HS-USB Modem Phone.
Still no luck with adb or fastboot.
Hope someone can help,
Kind regards,
Klaas-Jan

To revert to Stock
You could try the method indicated in this post. Please read the post thoroughly before proceeding.
Note that in step 4 you should be looking for the model number of YOUR tablet.
I have not tried this method myself yet, so I don't know if it works. As always you do this at your own risk, but as your tablet is not working, you may wish to give it a try.
Good luck.

Baldyiskaal said:
Hi all,
When installing TWRP on my daughters tablet I have accidentally flashed boot instead of the recovery with the TWRP image on the tablet using fastboot.
After I realised the error I have flashed TWRP to the recovery partition and rebooted the tablet to access TWRP.
When I was in TWRP I have wiped the data partition and flashed the lineage os rom for this tablet.
First error I noticed was E: legacy property environment did not init successfully, properties may not be detected.
Installation appeared to run properly but in the end I got a lot of E:Unable to stat '/data/.........' messages.
When rebooting TWRP asks to install SuperSu which also shows the same kind of error messages.
At startup I get the Lenovo logo and afterwards only a black screen which is turned on (in the dark you can see that it is active)
I am currently unable to access the fastboot environment, when rebooting using power and volume down it looks like the tablet is in fastboot mode, but when connected to the laptop it shows up as MTP device.
Fastboot or adb itself does not show any connected devices.
When rebooting after the Format data option in TWRP and installing an image I get the following errors :
E:Unable to find partition size for '/recovery,
E:Mount: Unable to find partition for path '/emmc'
E:UnMount: Unable to find partition for path '/emmc'
E:Mount: Unable to find partition for path '/emmc'
I have tried to flash the tablet back to stock rom with the Lenovo/Qualcomm downloader tool but that tool hangs at the Sahara stage and does not proceed after detecting the tablet.
Does anyone have an idea I can try or is the tablet bricked ?
TWRP version is 2.8.7.0 and I am able to access the recovery.
ROM's tried are lineage-14.1-20170520-UNOFFICIAL-x103f.zip and RR-N-v5.8.5-20171113-x103f-Unofficial.zip
USB debugging and bootloader were unlocked in the developer options on the tablet.
I ave rebooted to the bootloader from TWRP after trying another flash, still having a black screen.
In device manager I am now showing Lenovo-HS-USB Diagnostics (COM20), Lenovo HS-USB NMEA (COM21) and Lenovo HS-USB Modem Phone.
Still no luck with adb or fastboot.
Hope someone can help,
Kind regards,
Klaas-Jan
Click to expand...
Click to collapse
The errors look like the ones I got when I installed the TWRP posted here. There's something better available. Have a look on my post

Related

Stuck on BlissPop loadscreen. Help.

Hello! I installed BlissPop on my tablet before getting the new one from the callback program. This worked fine for several months, until suddenly the tablet decided not to boot.
The current situation:
The tablet boots onto the Nvidia logo, stays there for about 3 mins, then starts booting BlissPop. The boot is then stuck at the BlissPop animated loading screen. (It does not freeze the tablet or anything like that)
The tablet is not bricked (I think). I do not get the bricked error when checking on serial number. I dont remember which version of BlissPop i flashed over half a year ago.
What I have tried:
1) Flash a new custom ROM through Recovery, installing from zip through adb. I get an error while installing from zip:
- mount: failed to mount /dev/block/platform/sdhci-tegra.3/by-name/UDA at /data: Invalid argument.
- unmount of /data failed; no such volume.
- Patching system image unconditionally
Also, I cannot mount /data or /cache from CWM. Is my partition table messed up?
2) Flash to stock recovery image, through fastboot.
These steps always end up in the same way, nothing has happened during the flashing or installation. The device is still in the same state.
3) I tried installing another recovery type (now using CWM v.6.0.5.0), but I always end up with the old one.
What seems to be the common result on whatever I try, is that nothing happens. I even tried erasing all the data from the tablet, but nothing changes. Still boots into BlissPop and is stuck there. It seems like I cannot write anything to the tablet. Recovery mode (CWM) is also VERY slow, and it takes about 3 mins to get into CWM from fastboot bootloader screen.
Does anyone have any idea what I'm doing wrong, or have any tips for new things to try out?

twrp or CWM saying cant mount any partition TF300T

hELLO,
I tried installing twp and cwm versions from xda/twrp.me/cwm website for T300T and flashed them successfully from FASTBOOT but after I boot into recovery and then, when I try to wipe data/ factory reset, do anything in twrp or CWM, I get error "unable to mount /system /cache/ and every other partition, so I can not flash anything, can not mount any partition or sdcard or emmc or anything and can not copy flash files into tablet from PC while in TWRP CWM or external SDcard. I already enabled USB debugging and everything else in tablet settings but I am unable to mount anything or format anything from TWRP or CWM.
TWRP shows internal memory as 00mb :S
HOw to get pass that error "unable to mount" ??
how to mount so that I can flash custom roms/
REgards
Device info Asus tf300t
Android 4.2.1
Build number JOP4OD.JP_epad-10.6.1.27.5-20130902
Administr4tor said:
hELLO,
I tried installing twp and cwm versions from xda/twrp.me/cwm website for T300T and flashed them successfully from FASTBOOT but after I boot into recovery and then, when I try to wipe data/ factory reset, do anything in twrp or CWM, I get error "unable to mount /system /cache/ and every other partition, so I can not flash anything, can not mount any partition or sdcard or emmc or anything and can not copy flash files into tablet from PC while in TWRP CWM or external SDcard. I already enabled USB debugging and everything else in tablet settings but I am unable to mount anything or format anything from TWRP or CWM.
TWRP shows internal memory as 00mb :S
HOw to get pass that error "unable to mount" ??
how to mount so that I can flash custom roms/
REgards
Device info Asus tf300t
Android 4.2.1
Build number JOP4OD.JP_epad-10.6.1.27.5-20130902
Click to expand...
Click to collapse
If your fastboot still works, please try Kang TWRP 2.8.7.2 from here: http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479.
if the other recovery does not work, you would probably need to reflash stock rom from the asus website, this is due to recovery not being able to identify the partitions without a full boot, if you wiped it from bootloader the whole partition table is messed up and you want to reflash that by using the stock rom. If you need any help on that just pm me.
I have the exact same problem. Not sure about fastboot as so far it has not installed anything. I have twrp 2.5.0.0 .... adb does function and have actually installed KK 6.0 and works fine, but on restart it is back to recovery and no OS.Any help appreciated.
using fastboot all I get is waiting on device and a blinkng cursor.
How can I get Kang twrp on the tf300 with adb commands?
Sorry to sort of hi-jack the OP thread, but my problem is very similar. Here is where I am now tablet sitting at Starting fastboot usb download protocol ... 3 icons with RCK blinking. I ran the following From my sdk platform tools folder.
adb reboot bootloader
it was followed by;
" daemon not running. starting it now on port 5037"
"daemon started successfully"
I then ran the following:
fastboot -i 0x0b05 flash recovery twrp_tf300t_kang_2.8.7.2.img
it was followed by:
sending 'recovery' (7126 kb)...
followed by a white blinking cursor and it just sits there,
Same results if I run it all the same except substituting the blob file instead of the img file.any ideas?
Many Thanks
Many Thanks, go out to gs-crash-24-7 as well to the forums here at XDA, I now have my tf 300 back up and running on the stock JB 4.2.1 rom. Still isn't recognizing my Micro SD card, but that is a problem I think should be easier to solve.
Again, many thanks all.
Took forever to get it to be recognized as a fastboot device with windows 10, but once that happened ( I won't lie, I erased everything many times) well that and me switching to a little 3 ft cord (after so many attemps at adb>fastboot flash staging blob) it is going for now.
Good advice below if your TF300T seems bricked.
gs-crash-24-7 said:
if the other recovery does not work, you would probably need to reflash stock rom from the asus website, this is due to recovery not being able to identify the partitions without a full boot, if you wiped it from bootloader the whole partition table is messed up and you want to reflash that by using the stock rom. If you need any help on that just pm me.
Click to expand...
Click to collapse
Still isn't recognizing my Micro SD card, but that is a problem I think should be easier to solve.
Click to expand...
Click to collapse
Man was I ever wrong about that statement .... still no success getting the tablet to once again recognize external storage at all.
If anyone can help me with the MicroSD/External Storage not being recognized problem, please take a look here.
Thank you all, its all good and working now with recovery file you posted above.
Cheers!
Administr4tor said:
Thank you all, its all good and working now with recovery file you posted above.
Cheers!
Click to expand...
Click to collapse
You are welcome! Good to hear that the issues are solved with the recommended Kang TWRP.
BTW, using the thanks button is greatly appreciated.

Bricked Mi4i - Encryption Unsuccessful

I was on AospExtended V4.1, suddenly apps started force closing therefore I rebooted to find a " Encryption Unsuccessful" screen so I booted into TWRP to only realise I couldn't factory reset or do wipes because every time this error will pop "Failed to mount system, cache and data (invalid argument)". The partititons size are 0 and after trying to change the file system nothing got fixed. In fact now I can't get the " Encryption Unsuccessful" error the phone boots into fastboot.
Flashing the fastboot rom or anything else like the stock recovery doesn't seem to work... any leads about what can I do?
Phone's status now
Now the phone doesn't boot recovery or fastboot and now when I connected to the computer It's detected as Qualcomm HS-USB Diagnostics 9006. I am able to flash the firmware of MIUI witth MiFlash2016.03.30(64bits) as the new beta of MiFlash stopped detecting the device.
I think somehow my phone started to encrypt data, I rebooted It which lead into partition corruption. When I had access to recovery the partition were ****ed so I got a message about failing to mount /data /system /cache. Because of this I decided to try this . After restoring the stock patition the phone enter this qualcomm mode the screen is black and is detected as Qualcomm HS-USB Diagnostics 9006.
I tried some unbrick methods and here are the results:
QFIL(Qualcomm_Flash_Image_Loader_v1.0.0.3): Download Fail:
Switch to EDL FailFailed to Switch to Emergency Download mode
ToolStudio doesn't even start on windows 10.
eMMC_DL_Tool fails to write file (NON-HLOS.bin downloading)
GNQC DownLoad Tool V1.7.1.0 can't start error
Qualfast_v1.0.2 doesn't start
GN Qcom Download Tools V2.2.0.0 it starts but Phoneplatform set error!
[/COLOR]
I got most of the software from here
Same here
Efniak said:
I was on AospExtended V4.1, suddenly apps started force closing therefore I rebooted to find a " Encryption Unsuccessful" screen so I booted into TWRP to only realise I couldn't factory reset or do wipes because every time this error will pop "Failed to mount system, cache and data (invalid argument)". The partititons size are 0 and after trying to change the file system nothing got fixed. In fact now I can't get the " Encryption Unsuccessful" error the phone boots into fastboot.
Flashing the fastboot rom or anything else like the stock recovery doesn't seem to work... any leads about what can I do?
Phone's status now
Now the phone doesn't boot recovery or fastboot and now when I connected to the computer It's detected as Qualcomm HS-USB Diagnostics 9006. I am able to flash the firmware of MIUI witth MiFlash2016.03.30(64bits) as the new beta of MiFlash stopped detecting the device.
I think somehow my phone started to encrypt data, I rebooted It which lead into partition corruption. When I had access to recovery the partition were ****ed so I got a message about failing to mount /data /system /cache. Because of this I decided to try this . After restoring the stock patition the phone enter this qualcomm mode the screen is black and is detected as Qualcomm HS-USB Diagnostics 9006.
I tried some unbrick methods and here are the results:
QFIL(Qualcomm_Flash_Image_Loader_v1.0.0.3): Download Fail:
Switch to EDL FailFailed to Switch to Emergency Download mode
ToolStudio doesn't even start on windows 10.
eMMC_DL_Tool fails to write file (NON-HLOS.bin downloading)
GNQC DownLoad Tool V1.7.1.0 can't start error
Qualfast_v1.0.2 doesn't start
GN Qcom Download Tools V2.2.0.0 it starts but Phoneplatform set error!
[/COLOR]
I got most of the software from here
Click to expand...
Click to collapse
HI...
Did you get any success.. Please share.. I have MI4I.. and stuck in same situation...

failed to mount vendor (invalid argument) -- SOLVED

Updating partition details... Failed to mount vendor (invalid argument)
The error above is one I faced today and I resolved. I decided to share this in case anyone else runs into a similar issue. There are very few ways you could end up unable to correctly boot a partition but the most common is a bad flash. In my particular case, it was my own stupidity, and it could have been a lot worse given that I mistakenly flashed a vendor image file to /vendor/ except it was for a completely different device and not meant for the Moto x4 (basically got confused between files from another project).
The result of this was that my phone could not technically boot on its own. Neither into a GSI/ROM or into Recovery either. I saw the first "Android One" logo, followed by the message warning that my phone was unlocked, followed by the second "Android One" logo, which was all normal up to that point, but I would remain forever stuck at that screen. I could thankfully reach the bootloader screen, but again, since I could not boot at all, I could not even boot into Recovery from the bootloader screen.
Thankfully, because I could still reach bootloader I could temporarily load into TWRP using fastboot
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
From here I uploaded "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view and installed
Rebooted back to bootloader and while at bootloader, I loaded the Android 8.1 firmware - courtesy @ptn107 https://androidfilehost.com/?fid=890278863836292604
From bootloader, I reloaded the bootloader again
This alone did not resolve my issue. I once used fastboot to temporarily load TWRP
Code:
fastboot boot '/your_path_here/twrp-X.X.X-X-payton.img'
Installed TWRP https://dl.twrp.me/payton/
Installed LineageOS ROM -- It must be a full ROM and not a GSI. It must be specifically made for Moto x4 and not just a generic GSI (stock rom for example)
Reinstalled TWRP
Reboot
During the installs, you may still see the error. Ignore them as they will go away after the reboot. This will resolve such issues should you ever face them.
MotoX4 said:
From here I uploaded "Copy Partitions Zip" - courtesy of @filipepferraz https://drive.google.com/file/d/1oir...t2eSGKt0F/view and installed
Click to expand...
Click to collapse
Fix google drive link, pls
Comby_sk said:
Fix google drive link, pls
Click to expand...
Click to collapse
Fixed in post #1 and full URL without text formatting is also here too
Code:
https://drive.google.com/file/d/1oiry9UfP2tf-5A6nQBF7pn2t2eSGKt0F/view

[HELP] Remove boot loop without root & USB debugging?

Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Hørk said:
Hi,
this is my first post on this forum, so please let me know if you are missing any information …
My problem: I'm experiencing a boot loop with my Nexus 5 after having changed its damaged battery. I didn't use it for a long time because of this damage. Now, it does start the boot sequence again, but only to the "circle" animation which it keeps showing indefinitely.
The circumstances:
I never tried to root the phone
USB debugging is not (and cannot be) enabled
I'm completely sure the problem is not caused by the power button (seems to be a common cause)
stock recovery is reachable
an old version of ClockWorkMod Recovery (from this thread) is bootable
three tested versions of TWRP won't boot
What I tried:
I unlocked the bootloader. With both the stock recovery and CWM, I tried to
wipe the device / the cache partition
flash a stock image (directly downloaded from the Google developer page)
flash a ResurrectionRemix image
None of these worked. It seems that the recovery systems are not able to write on or even to mount the necessary partitions. As the stock recovery apparently needs access to /cache for adb sideload, any attempt to flash anything results in an error message. CWM is able to sideload the zip file, but writing the image fails.
I furthermore tried the "factory" (not OTA) image from Google with its flash-all.sh script which tries to also update boot loader and other things via fastboot – every single one of these update attempts failed as well.
So, my question is: Does anyone of you know of a way to get my phone working again?
Many thanks in advance, best regards
Hørk
Click to expand...
Click to collapse
Ever fix it?

Categories

Resources