Related
Hello XDA-Developers Community,
I've a Big Problem With My Toshiba Folio 100.
I Bought It, and Today I Try To Install The FolioMod v1.4.
I've Made Everything Right.
When Appears The "!" Symbol, I've Clicked On "Home" Button, And Selected The "Apply sdcard:update.zip" Option.
It Gives Me An Error:
E:Can't mount /dev/block/mmcblk1p1
E:Can't mount SDCARD:command
E:Can't mount DEFAULT_PATH
Finding update package...
E:Can't mount /dev/block/mmcblk1p1
(no such file of directory)
E: can't mount SDCARD:/update.zip
Formatting MISC:...
And I've Discovered That The Answer To That Problem Is Use a 1GB or 2 GB SD Card (Usually With a Size More Than 2GB Have That Error).
So, After I Received That Error, I Select "Home" Again, and Choose The Option To Reboot The System.
After That The LCD Turns Black, and Never More I Could Turn On The Tablet.
The White Light On "Power/Battery" Is Always On. And I've Tried Everything To Reboot The Folio 100.
The Only Think That I Haven't Did Yet, Was Waiting That Battery Be at 0% and Folio 100 Turns Real Off, And Then Try To Turn It On. (I Didn't Do It, Because I'm Waiting For The Loss of Battery, That Will Be Much Time).
Can Someone Help Me?
Sorry For My Bad English.
Kind Regards,
Micael de Sousa.
mklive69 said:
Hello XDA-Developers Community,
I've a Big Problem With My Toshiba Folio 100.
I Bought It, and Today I Try To Install The FolioMod v1.4.
I've Made Everything Right.
When Appears The "!" Symbol, I've Clicked On "Home" Button, And Selected The "Apply sdcard:update.zip" Option.
It Gives Me An Error:
E:Can't mount /dev/block/mmcblk1p1
E:Can't mount SDCARD:command
E:Can't mount DEFAULT_PATH
Finding update package...
E:Can't mount /dev/block/mmcblk1p1
(no such file of directory)
E: can't mount SDCARD:/update.zip
Formatting MISC:...
And I've Discovered That The Answer To That Problem Is Use a 1GB or 2 GB SD Card (Usually With a Size More Than 2GB Have That Error).
So, After I Received That Error, I Select "Home" Again, and Choose The Option To Reboot The System.
After That The LCD Turns Black, and Never More I Could Turn On The Tablet.
The White Light On "Power/Battery" Is Always On. And I've Tried Everything To Reboot The Folio 100.
The Only Think That I Haven't Did Yet, Was Waiting That Battery Be at 0% and Folio 100 Turns Real Off, And Then Try To Turn It On. (I Didn't Do It, Because I'm Waiting For The Loss of Battery, That Will Be Much Time).
Can Someone Help Me?
Sorry For My Bad English.
Kind Regards,
Micael de Sousa.
Click to expand...
Click to collapse
Power off can be performed after long press on power button - led will stop blinking, red or white that does'nt matter, device will be switched off.
While device is in boot cycle, pressing power later vol_up - should bring You to very simple memu with really few choises
- vol up = reset
- vol down = ignore and boot
after vol up:
- vol up = factory reset
- vol down = install update.zip from sd card which must be fat32 formatted
If device was rooted then update.zip can contain any update, if not then bootloader will check for its (update.zip) validity - in most cases proper rsa signature.
m32
m32 said:
Power off can be performed after long press on power button - led will stop blinking, red or white that does'nt matter, device will be switched off.
While device is in boot cycle, pressing power later vol_up - should bring You to very simple memu with really few choises
- vol up = reset
- vol down = ignore and boot
after vol up:
- vol up = factory reset
- vol down = install update.zip from sd card which must be fat32 formatted
If device was rooted then update.zip can contain any update, if not then bootloader will check for its (update.zip) validity - in most cases proper rsa signature.
m32
Click to expand...
Click to collapse
My first folio can't properly perform factory reset - even from settings menu, I have returned it to seller, next one have tilll today, and now with cm 7.1 rc1, cm-nightly, foliomod14 or any other rom - is just cooool
m32
Try to erase system partition from fastboot:
To go to fastboot mod press 3x power button and 1x volume down button at toshiba logo.
Connect Folio with pc via usb(you need drivers for that on windows and fastboot binary for linux and mac. Go here => http://forum.xda-developers.com/showthread.php?t=1119507 to set things that you need )
Now, open terminal and and type:
fastboot erase system
and then:
fastboot reboot
After that, go to recovery and reflash.
Hood luck!!!
fastboot reboot
Hello,
Thank To Everyone That Reply To My Main Topic, It Have Help Me a Lot
Now, I'm Trying To Install The FolioMOD v1.4 on My Toshiba Folio 100.
So, Turn On The Device, Power + VOL+ . Then I Press VOL+, VOL-, VOL+ To Make an System Update.
When Appears The "!" Symbol I Select "Home" Button, and Then I Select "wipe data/factory reset".
After That, I Select "Home" Again, and Then I Select "apply sdcard:update.zip"
And It Appears The Following Error:
Code:
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
Formatting MISC:...
And I'm Sure That My Toshiba Folio 100 is Rooted.
It Was Rooted By Myself With SuperOneClick 2.1.1.
Can Someone Help Me?
I Really Want To Have Access to Android Market, Gmail and a Lot of other Features of Google Services on My Device.
Kind Regards,
Micael de Sousa.
You have the lastest Toshiba softer update on your Folio. You have to change your recovery. Go to FolioMod 1.4 page and find on it something like "and for users that installs lastest update go here..." and go there or just install via fastboot or you can sing it.
Jon2555 said:
You have the lastest Toshiba softer update on your Folio. You have to change your recovery. Go to FolioMod 1.4 page and find on it something like "and for users that installs lastest update go here..." and go there or just install via fastboot or you can sing it.
Click to expand...
Click to collapse
espentan said:
You need to add the directory containing the "AdbWinApi.dll" to Windows' path under Environment Variables, so Windows know where to look for the necessary files when you enter commands in the shell.
For this exercise I'm going to assume that you have installed the Android SDK in the directory called "android-sdk-windows" on your C: hard drive. If you have it installed somewhere else, change the path I'm mentioning below accordingly.
Go to the Windows "Control Panel".
Click on "System and Security".
Click on "System".
Click on "Advanced system settings" in the left column of the window you're in.
Find the button called "Environment Variables" in the window that opens (it's at the bottom on the first tab).
Scroll down in the "System variables" box until you find "Path".
Select "Path" and click the "Edit" button.
At the very beginning of the input field called "Variable value" enter the following:
"C:\android-sdk-windows\platform-tools;" (without the quotes).
Do not remove any of the other paths, and make sure you have a semi colon at the end of the new path you're adding.
Reboot.
Click to expand...
Click to collapse
Hello,
Thank For Your Help.
Now That I Could Install FolioMod v1.4 I've Another Problem.
After The Installation, My Toshiba Folio 100 Rebooted.
Them, In The First Starts, It Is On "Android Logo" Screen at More Than 15 Minutes...
It Is Still On That Screen... But Is This Normal?
Kind Regards,
Micael de Sousa.
Did you erased system partition and installed via fastboot??? Or you can post logcat(./adb logcat>logcat.txt)
Jon2555 said:
Did you erased system partition and installed via fastboot??? Or you can post logcat(./adb logcat>logcat.txt)
Click to expand...
Click to collapse
Hello,
I Resolved The Problem By Myself.
I Reboot My Folio 100, Then I Selected The "Reset System" Option.
When The Folio Started, It Have The FolioMod v1.4 Installed.
Thank You Anyway.
Kind Regards,
Micael de Sousa.
mklive69 said:
Hello,
I Resolved The Problem By Myself.
I Reboot My Folio 100, Then I Selected The "Reset System" Option.
When The Folio Started, It Have The FolioMod v1.4 Installed.
Thank You Anyway.
Kind Regards,
Micael de Sousa.
Click to expand...
Click to collapse
Allways use clear data/cache/system- this iwnt neccesary but helps resolving any issues, system reset -aka factoryreset isnt nothing more
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery <3e> with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
[UPDATE]
1. I purchased a jig(link further down) and the jig got me into "Downloading..." mode
2. Once in download mode I flashed a ROM and pit file as from Hyperrunner's thread(again, link further down)
3. Using Yaph's experience on AnythingButIpod I flashed Steve's kernel again and gained access to CWM
4. I tried using the restore I was making before the bootlooping started and it went through but I am still stuck in CWM
[UPDATE 2]
All fixed. Big thanks to everyone, especially Zaclimon!
SGP4isokay said:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
Click to expand...
Click to collapse
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.
Link: http://forum.xda-developers.com/showthread.php?p=23290249
Sent using Tapatalk
klin1344 said:
Adb should work in recovery; type Adb reboot download and you should be in download mode. In download mode you have to flash zaclimon's full recovery rom for the 4.0.
Link: http://forum.xda-developers.com/showthread.php?p=23290249
Sent using Tapatalk
Click to expand...
Click to collapse
Thank you. I've never worked with Android Debug Bridge but it looks drop dead simple from Androidsamurai's guide, so I'll give it a go along with Zaclimon's work. Much appreciated.
have you flashed the stock recovery for the 4.0? or did you already fix it?
minimeofctown said:
have you flashed the stock recovery for the 4.0? or did you already fix it?
Click to expand...
Click to collapse
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.
SGP4isokay said:
I haven't flashed anything yet. I just downloaded the guide, the All In One tool, and the Google USB drivers. I'm trying to load the drivers now.
Click to expand...
Click to collapse
For ADB you need samsung drivers not google's
Link to samsung drivers: http://forum.xda-developers.com/showthread.php?t=961956
zaclimon said:
For ADB you need samsung drivers not google's
Link to samsung drivers: http://forum.xda-developers.com/showthread.php?t=961956
Click to expand...
Click to collapse
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
Click to expand...
Click to collapse
With nothing following.
SGP4isokay said:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
With nothing following.
Click to expand...
Click to collapse
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.
also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.
SGP4isokay said:
Thank you. Unfortunately my Windows XP machine is not recognizing my Galaxy Player as anything other than a two drive mass storage device(with the "Safely Remove Hardware" icon in the system tray). The command adb devices returns
With nothing following.
Click to expand...
Click to collapse
youll have to have usb debugging on. it might give you that at first. just input the command again.
zaclimon said:
Ensure that Usb debugging is enabled: settings-->applications-->developpment-->enable USB debugging.
also ensure that you don't turn on USB mass storage (which means the little android remains green.) Then try again. (Before trying again do this command: adb kill-server.
Click to expand...
Click to collapse
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.
SGP4isokay said:
Yeah, I saw that I needed debugging on when I started going through Androidsamurai's guide. I neglected to enable that before I tried making a backup and now there appears to be no way to enable it since I am stuck in "Android system recovery". A little Googling leads me to believe that any effort to recover at my device hinged on that being enabled.
Click to expand...
Click to collapse
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
minimeofctown said:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
Click to expand...
Click to collapse
Thanks! I'll wait for news from you. I'm in no rush and this experience has been a pretty decent learning opportunity.
SGP4isokay said:
After unboxing my SGP 4.0(USA) I applied Steve's kernel which I cannot recommend enough. Anyway, I was so happy with it that I decided to try Klin's Klassic ROM. In Klin's instructions he stresses to make a backup via CWM prior to flashing so I booted into CWM, had my device create a backup, then rebooted. I ended up in bootloops like others have experienced.
Before anyone flips out on me, yes I was fully aware that Steve said, "NOTE: Don't use ROM Manager". I did not use the Rom Manager app. I booted into CWM and felt I was safe in doing so. No experimentation took place. I made a backup to the internal storage and rebooted.
Anyway, I was getting bootloops so I tried the fix in Hyperrunner's thread. I followed the instructions. The first portion of his recommended fix did not work so I proceeded to step two where I included the pit file and followed the instructions verbatim. I was stoked when I saw that his steps meshed with what I was seeing on my screen to include the booting into Recovery Mode. I Wiped Data and Wipe Cache. The data wipe got rid of a bunch of errors. The cache wipe did not.
I am now stuck in Android system recovery <3e> with the following errors:
-- Copying media files...
E:failed to mount /dbdata (Invalid argument)
E:copy_dbdata_media:Can't mount /dbdata
your storage not prepared yet, please use UI menu for format and reboot actions
Meida files copy failed.
# MANUAL MODE #
-- Applying Multi-CSC...
Successfully applied multi-CSC.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
So I'm stuck in system recovery with the options to:
reboot system now(Done several times)
apply update from sdcard(Have not seen that discussed)
wipe data/factory reset(Did that. It cleared some errors.)
wipe cache partition(Cache errors persist)
I cannot get the device to Download Mode, into the mode with the PC and phone), or connect via Odin. I saw this thread about getting back to download mode but it is for the 5.0 and I'm looking for help as to what my next step should be.
Thanks for your time.
Click to expand...
Click to collapse
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.
Thank you for any help.
minimeofctown said:
might wanna invest in one of these(; http://www.ebay.com/itm/Micro-USB-J...ccessories&hash=item3372a56243#ht_1175wt_1141
mine came in. im getting it tomorrow hopefully. so if you wanna wait until i test if it works then ill let you know if its safe to buy
Click to expand...
Click to collapse
I purchased a Jig from here(USBJig). With it I was able to get back to the "Downloading..." screen(Android with shovel). I plugged the USB cable in and Windows XP recognized my device. So...hooray!
Vilai said:
so i have the exact same problem BUT i can access download mode and it is recognized by odin, the next post says to use the zaclimon's recovery rom but it is closed for US. also use ADB but idk if that would apply to my case and if so what do i do exactly because for someone like me its very confusing.
Thank you for any help.
Click to expand...
Click to collapse
Indeed, Zaclimon's rom is a No-Go. I have been following Kwipper's "[STOCK ROM]" but it says that, "Your phone should be rooted prior to doing this." I did root my device but I'm so hesitant to do anything at this point that I wanted to check with XDA before I do anything.
I'm going to drop a note in Kwipper's thread and ask for guidance. Vilai, I will update you as I progress. Any other input from XDA posters is obviously welcome.
i actually did that one too a no go for me just gonna wait out what i see here in the coming days.
Vilai said:
i actually did that one too a no go for me just gonna wait out what i see here in the coming days.
Click to expand...
Click to collapse
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.
Here is his last post on the thread I linked just above:
So this is solved!
If anyone gets this kind of error (I think it appears after flashing something with a pit file, even if it is the same you just used), I fixed it by flashing a rom with those inside:
SBL
BOOT (IBL + PBL)
CACHE
DBDATAFS
PARAM
I have the 4.0 US but I took those from a 4.0 international.
PLEASE BE CAREFUL NOT TO USE A ROM WITH zimage & factoryfs INSIDE if you own the us version... if you do a usb jig will still do the trick.
Good to know: the unbrickable resurector does work on the 4.0, check that out if you have a hard brick (no screen response).
Click to expand...
Click to collapse
He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.
[EDIT]
I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.
Meh, progress. =- D
SGP4isokay said:
I found someone who has recovered from these errors but I don't know how to replicate his fix being that this is my first experience with Android/Odin. I will try to contact him and see if I can get a step-by-step repair process.
Here is his last post on the thread I linked just above:
He mentions at the top of his post that he successfully applied Steve's Kernel to regain Clockwork Mod recovery access so I tried that and now I have CWM working.
[EDIT]
I tried to restore my device from the backup. It seemed to go through successfully(the restore process) but then it just keeps booting into CWM regardless of what I do.
Meh, progress. =- D
Click to expand...
Click to collapse
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.
zaclimon said:
I've decided to remake the rom for the US (I will not include bootloaders this time) just /cache /system /dbdata and zImage only. I will post it later today. (your error is the recovery can't mount /cache so reinstall it would work.) I will send you a PM for testing if you want before sending it to the recovery thread.
Click to expand...
Click to collapse
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.
SGP4isokay said:
For Vilai and anyone else wanting a progress report, I tried the ROM supplied by Zaclimon and it cleared all errors in Samsung Recovery but I am still stuck there. Apparently the next step was to try flashing the bootloader but that failed in Odin. I still have access to Samsung Recovery and "Downloading..." mode.
Click to expand...
Click to collapse
I am having the same problem. I get no errors but keep booting into recovery. Tried flashing Steves kernel and it loaded into CWM with no errors. Still no system though.
Hmm, sorry for being late into the game, but I had these exact same errors, back before we really knew what we were doing, lol! I couldn't ever get rid of the errors, but I think that was because I was flashing the wrong partitions, so glad you got rid of them! I'm not sure why it still boots to recovery, I'll stay tuned to see what happens! Let me know if you need anything...
Sent using the XDA app.
Hello,
My Tablet S is in deep need of expert help to see the light of day...:crying:
History:
I've rooted it about one day after the working exploit was found, ran Condi's AiO tool to update, and everything went fine.
At once, I used the "reinstall to factory settings" in the Settings app, which gave me a happy - if somewhat unstable at times - tablet.
It suddenly stopped working and remained stucked at the Sony logo.
Having no other option, I restarted in Recovery (Power-Volume+), and tried to update the system from SD card :
- with latest Condi's R5a zip : signature error
- with stock encrypted Sony zip : update blocked (yes, I left the tablet running about 8 hours without a move from the progress bar)
In the Android Recovery, I then selected "Reset to factory settings". Which seemed to do its thing, except that...the tablet still was stucked at the Sony logo at boot.
Going to Recovery again...
Code:
E:Fail to read boot logo flad
E:Can't open /dev/block/mmcblk0p5
(No such file or directory)
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E:failed to mount /cache (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache (No such file or directory)
E:failed to mount /sdcard (No such file or directory)
E:failed to mount /cache (No such file or directory)
I can see the following device with ADB :
Code:
./adb devices
List of devices attached
0123456789ABCDEF recovery
and that's about all I can do with the tablet now.
Code:
./adb shell "ls /"
- exec '/system/bin/sh' failed: No such file or directory (2) -
One word remains: PLEASE HELP !
Is there any way I can dump a working system on the tablet in this state?
Note: I'm not afraid of running anything arcane command/script/setup.
Strange because the shell binary cannot be found but it can be wiped.
It is possible that the System partition is gone.
Sent from my Sony Tablet S using xda premium
andyabc said:
It is possible that the System partition is gone.
Click to expand...
Click to collapse
Yes indeed, I'm pretty sure that the Recovery option "Restore to factory settings" did wipe partitions...and failed to write anything sensible to them afterwards, or to recreate them at all (if that makes sense : I am far from sure of what the whole process really does and whether this is an Android standard or Sony-proprietary).
So, I'm there with my half-baked tablet ... any kind soul with the know-how how to revive it?
sorry to be the bearer of bad news, but I have had the expect same thing happened to my tablet s, all of sudden it stopped working, stuck on sony logo during booting, can't mount sd card in recovery mode, etc etc. Chances are your mother board is damaged. Might be a good time to send it to sony for repair. Good luck
since you have root,look here
how to use adb shell in recovery mode
http://forum.xda-developers.com/showthread.php?t=2081196
once you get shell,check you mmc device,and it's partitions
http://forum.xda-developers.com/showthread.php?t=2102704
any way,send your tablet to sony is a good chiose.
Palijn said:
Yes indeed, I'm pretty sure that the Recovery option "Restore to factory settings" did wipe partitions...and failed to write anything sensible to them afterwards, or to recreate them at all (if that makes sense : I am far from sure of what the whole process really does and whether this is an Android standard or Sony-proprietary).
So, I'm there with my half-baked tablet ... any kind soul with the know-how how to revive it?
Click to expand...
Click to collapse
Data partition is still there though.
The recovery has its own shell for sure since you are rooted.
The recovery has its own binary and adb support.
Here is the boot order:
Bootloader>Kernel>Boot Animation>System
When the Sony logo flashes thats when it switches to the Kernel but since it did not do anything it is possible that there is missing files in the data partition.
Bootloader = On a component on the motherboard somewhere
Kernel = Data Partition
Boot Animation = System Partition
System = System Partition (Obviously)
Sent from my Sony Tablet S using xda premium
maybe kernel is not on data patition.
kermel is in rootfs.which is split with inner mmc dev(or in a hidden partition)
robin said:
maybe kernel is not on data patition.
kermel is in rootfs.which is split with inner mmc dev(or in a hidden partition)
Click to expand...
Click to collapse
Yeah true but the question is did the Sony logo flash for a moment, if it did then it switched to the kernel successfully.
I cannot view your username in the quote above due to it using part of the tags used in programming languages.
Sent from my Sony Tablet S using xda premium
andyabc said:
Yeah true but the question is did the Sony logo flash for a moment, if it did then it switched to the kernel successfully.
Click to expand...
Click to collapse
Yes indeed, the Sony logo flashes (and that's a fairly nice indication for the right time to press Power again and enter Recovery afterwards!).
Anyway, the tablet froze from time to time just entering Recovery (screen with the green/white dots), then I was able once or twice to start restoring a system image from the original Sony encrypted-signed ZIP so gracefully provided by condi in his Google Drive , but the process froze at different places!
I guess there is definitely a hardware issue (such as a faulty memory chip, if not a grilled processor), so right away it went to repair.
If it comes ever back as "repairable and repaired" I'll inform here!
Thanks to all for the attempts at helping!:highfive:
Palijn said:
Yes indeed, the Sony logo flashes (and that's a fairly nice indication for the right time to press Power again and enter Recovery afterwards!).
Anyway, the tablet froze from time to time just entering Recovery (screen with the green/white dots), then I was able once or twice to start restoring a system image from the original Sony encrypted-signed ZIP so gracefully provided by condi in his Google Drive , but the process froze at different places!
I guess there is definitely a hardware issue (such as a faulty memory chip, if not a grilled processor), so right away it went to repair.
If it comes ever back as "repairable and repaired" I'll inform here!
Thanks to all for the attempts at helping!:highfive:
Click to expand...
Click to collapse
Every chip and processor has its own firmware so maybe somehow it became corrupted.
Sent from my Sony Tablet S using xda premium
After using Odin to update firmware on my Galaxy Player 5.0 (model g70cwy/xaa), I can no longer get it to start. I get the Failed to mount /cache (no such file or directory) (see attached screenshot.
I tried the factory rest option, it does not seem like any of the options on this screen works.
Any help greatly appreciated!!
Florida01 said:
After using Odin to update firmware on my Galaxy Player 5.0 (model g70cwy/xaa), I can no longer get it to start. I get the Failed to mount /cache (no such file or directory) (see attached screenshot.
I tried the factory rest option, it does not seem like any of the options on this screen works.
Any help greatly appreciated!!
Click to expand...
Click to collapse
volume down on wipe data press home if its not work try power button again volume down on ok press home or power button then same for wipe cache reboot
Kenxda33,
I have already tried that several time. Home button does not work, all power button does is reboot. I does not allow me to select an option.
Basically I can't choose any of the options displayed in the menu.
Any help greatly appreciated!!
I bought an MXQ Pro 4K box from an Amazon seller to see if it would be ok as a Plex/KODI client. All seemed ok so I bought another from a different Amazon seller as the original one was out of stock.
The second one has a different rom on It and it is not quite as good plus it is not rooted, however AIDA64 and CPU-Z seem to confirm the hardware is identical.
What I would really like to do it take a backup of the 1st box and restore it on to the 2nd box.
Any ideas how I can do this?
Anyone know a way to do this?
Google search for a file name ( minix_u1_ez_root )
Unzip the file and put the 3 files on a USB.
ezroot.zip
recovery.img
factory_update_param.aml
Go to "My Apps" and run "Update & Backup".
Click on "Local Update" and click on "Select". It should find ezroot.zip on your USB.
Select that and proceed.
This work in my MXQ Pro 4K BOX.
Doing something wrong?
I also have the p201 MXQ PRO 4K android box that came with 5.1.1 installed not rooted. I tried using the steps listed.
When I click update it restarts my box in recovery mode, I can move the cursor up/down but selecting an option does nothing.
down in the text area it says:
Recovery is listening adb sideload...
Waiting adb sideload command...
E:failed to mount (No such file or directory)
E:Can't mount /cache/recovery/log
and the "failed and Can't" messages continue....
It remains in that state until I unplug the unit.
Am I doing something wrong? Missed a step maybe? Input appreciated.
BTW, I tried doing this both from USB & the card slot
I have another quick question about this box. My settings do not offer BT at all. Could this be a bad chip or something else wrong with the box or a firmware problem? The add definitely stated "Android 5.1 More convenient Wifi and BT settings" so it is suppose to be there.
I don't even have the update and backup option at all on my device, mine is the version with 4 GB of RAM and 32GB ROM and Android NOUGAT 7.1.2