Hi everybody,
I'm a Toshiba Folio user and I've a great problem (I think!).
After the last ROM update I made, my tablet does not start Android system. Plus, when I try to install the Rom (or any other) again trought the ClockworkMod Recovery, the installation fails because the system gives this messages:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I try, also, to connect my tablet to pc, but I see only the sd-card, if inserted.
How can I solve the problem?Thank you.
I highly encourage you to perform all the ROM installation or update through fastboot. It's a great little utility that you can never wrong. There's already someone else making a very in-depth tutorial on Fastboot in General section, you can try these steps and let everyone know if have any further problem.
I've tryed your solution but I have the same problem expalined in this thread:
http://forum.xda-developers.com/showthread.php?t=1183293
Can you help me solve this problem?
xitrumch said:
I highly encourage you to perform all the ROM installation or update through fastboot. It's a great little utility that you can never wrong. There's already someone else making a very in-depth tutorial on Fastboot in General section, you can try these steps and let everyone know if have any further problem.
Click to expand...
Click to collapse
Thank you very much...I solve the problem using fastboot as you say to me. My tablet is come back!Thank you again!
You're welcome. Sorry I didn't answer your previous message as I seldom check this forum now (this Folio section used to be so active...sighh)
But well, anyway, with Fastboot + adb utility, I can safely say that we are not afraid of messing up our tablet, since it's always possible to revert back to original state with a few command line.
Folio100 Update
Hey Guys.
I've been using this 1.4 mod for some times but wanted to try the new - so I followed this guide http://forum.xda-developers.com/showthread.php?t=1470823
But after using the flash - I'm stuck with a blanc screen!
The start Toshibo logo is shown but thats it.
I've tryed reset it with fastboot back top original image and everything - but the screen still goes blank.
I can easilly goes into recoivery mode - where it says it cyagen mod 5.5.0.4 - but then again goes into blanc screen and after 1 hour nothing happends !
So I'm not quite sure If I busted this device now - or how can I get it back online and usefull!
Tia
Per
Related
This is made for any HTC Android 2.1 device based from the HTC Legend OTA exploit
Originally created by @Eugene_373, scripted/modified by @WesGarner
Download and extract these according to your platform:
http://bit.ly/wesaspin#285
Report Issues: http://code.google.com/p/wgbuild/issues/list
In a command shell, run rootme. The stuff below is a copy of what is prompted to you in the shell
At this point, your phone should be booted as normal
Make sure these three things:
USB Debugging Enabled - Settings/Applications/Development
USB Connection Type - Charge Only (select on your notifications bar)
ADB Server needs to be pre-started (can do this via sudo adb start-server)
[Asks you to press the enter key]
This will reboot your phone into recovery, hopefully with adb working via the loop exploit
To access the controls in recovery, press Volume Up+Power
From here, use the Volume buttons to go up and down and the Power button to select
[Asks you to press the enter key to begin the loop exploit]
Once the phone is rebooted into recovery, you will see one of the following outputs:
Successful: - exec '/system/bin/sh' failed: No such file or directory (2) -
Unsuccessful: error: device not found
If successful, then run rootme2
If unsuccessful, reboot your phone then rerun this script
To access the controls in recovery, press Volume Up+Power
From here, use the Volume buttons to go up and down and the Power button to select
Press CTRL+C to end the loop script
Your phone will now reboot into recovery, press enter
[Run rootme2 if successful]
OK! Congratulations, your phone is almost ready to be rooted
Here is the tricky part...
To access the controls in recovery, press Volume Up+Power
From here, use the Volume buttons to go up and down and the Power button to select
IMPORTANT:
You will select apply update.zip, but within 1/2 sec of doing this you must press enter to continue this script
Also, it helps to stare at the screen until you see a progress bar under the text
If it is not done in the timely manner, you can try again by rerunning this script
From here, you should see ClockWork Recovery by Koush, and can install any ROM you would like!
Wes Garner
Twitter: http://twitter.com/wesgarner
Donation: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=10254127
Eugene_373
Twitter: http://twitter.com/Eugene_373
Donation: https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8574353
Hey wes, use the New Root.zip I posted regarding the Update.zip
Once the Update is ran, everything is Golden.. Su / Superuser.apk & everything is Fixed & installed at once..
Kudos for a legible guide, and an effective root method.
As someone who spent an entire afternoon trying to root my slide, I know how grateful people will be with this method available.
Good work sir.
slobatch said:
Kudos for a legible guide, and an effective root method.
As someone who spent an entire afternoon trying to root my slide, I know how grateful people will be with this method available.
Good work sir.
Click to expand...
Click to collapse
Yes legible, It just automates everything for you
I understand people are having trouble with it, but I honestly thought mine was easy to understand..
Major Kudos Wes, for making this Noob Friendly
~Eugene
eugene373 said:
Yes legible, It just automates everything for you
I understand people are having trouble with it, but I honestly thought mine was easy to understand..
Major Kudos Wes, for making this Noob Friendly
~Eugene
Click to expand...
Click to collapse
I understood yours perfectly.
I know this will be totally noobish but I don't care at this point (4 hours in to attempting root). What is sudo adb start-server? I tried typing it in but I got "'sudo' is not recognized as an internal or external command, operable program or batch file. I tried finding it on google but no real luck. I don't mean to clog up the forums but I am getting desperate.
Edit: I now have root but used the original way. Had some major problems. Please place on the disclaimer that this works best with a class 2 card. I couldn't get it to work with a Class 6 and only found that was an issue after snooping through hundreds of posts. Thanks Wes, Eugene, and all involved!!!!!
eugene373 said:
Yes legible, It just automates everything for you
I understand people are having trouble with it, but I honestly thought mine was easy to understand..
~Eugene
Click to expand...
Click to collapse
You bet it was! I was understandably cautious in rooting my first android. I read your guide 3 times and went for it. Took 10 minutes with lots of tripple checks. Soooooo easy. I thank you greatly for your work and I am a rom switching junkie thanks to it!!
simplyTravis said:
I know this will be totally noobish but I don't care at this point (4 hours in to attempting root). What is sudo adb start-server? I tried typing it in but I got "'sudo' is not recognized as an internal or external command, operable program or batch file. I tried finding it on google but no real luck. I don't mean to clog up the forums but I am getting desperate.
Edit: I now have root but used the original way. Had some major problems. Please place on the disclaimer that this works best with a class 2 card. I couldn't get it to work with a Class 6 and only found that was an issue after snooping through hundreds of posts. Thanks Wes, Eugene, and all involved!!!!!
Click to expand...
Click to collapse
"Sudo" is a linux command to run as root and as such is only needed if your running linux. If your using Windows you would just type "adb start-server" (I think, it's been a while since I've used Windows). But glad you got root with original method.
heybobitsme said:
"Sudo" is a linux command to run as root and as such is only needed if your running linux. If your using Windows you would just type "adb start-server" (I think, it's been a while since I've used Windows). But glad you got root with original method.
Click to expand...
Click to collapse
You are correct, Good advice
eugene373 said:
You are correct, Good advice
Click to expand...
Click to collapse
Thank you, sir!
Now, about Froyo... Just kidding!
Anyone know if this root method gets Root Explorer and Metamorph working?
So I ran into a problem using the SimpleRoot v1.3 Linux. I tried to follow the instructions, and was able to do the rootme. When I try to execute the rootme2 script I run into a problem. When trying to "select apply update.zip, but within 1/2 sec of doing this you must press enter to continue this script" I get one of two errors. This is what comes up on my phones screen. Any idea what it is? Or why this is happening?
Code:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
or
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
slughappy1 said:
So I ran into a problem using the SimpleRoot v1.3 Linux. I tried to follow the instructions, and was able to do the rootme. When I try to execute the rootme2 script I run into a problem. When trying to "select apply update.zip, but within 1/2 sec of doing this you must press enter to continue this script" I get one of two errors. This is what comes up on my phones screen. Any idea what it is? Or why this is happening?
Code:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
or
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Click to expand...
Click to collapse
Looks like you pressed the enter key too fast - look for the bar behind the text and give it a go
Need help
Could someone please help me with pre starting the ADB server. I dont know if this is the reason but my mt3gs wont boot to recovery mode automatically. My phone is in debugging mode and charge only. When i ran rootme from command prompt my device was not detected. I hope thats enough info to figure out my problem. Thanks in advance.
Ratard
So I had absolutely no issues rooting my G1 or my original MyTouch, but I can not make it work on the slide. It never sees my phone except for a split second after it reboots. After that it just cant see the phone at all. I've retried it multiple times to no avail. Any suggestions?
I knew this would happen. It took me a week to root my slide the hard way, now this is out
Let's hear some noise for the impatient!
Great job on another release Wes!
Thanks for your hard work
wesgarner said:
Successful: - exec '/system/bin/sh' failed: No such file or directory (2) -Unsuccessful: error: device not found
If successful, then run rootme2
If unsuccessful, reboot your phone then rerun this script
/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=8574353[/url]
Click to expand...
Click to collapse
I just got my slide today and followed your instructions to the letter about 5 times and each time I get the same unsuccessful result. I get into the recovery menu using vol+up and power but the loop script never finds the device at this point.
When the device is fully booted and powered on, I'm able to adb shell into it just fine, but after it reboots and goes into recovery, I looked in device manager and there are no adb drivers present and no hardware missing drivers. Any suggestions?
not to say that i am not grateful(i deffinately am) but why do we make it easier and easier to root our phones? isn't rooting supposed to be for the advanced users that know what can be done after root? shouldn't we just discover one method and leave it at that? i wrote a script as well that does this on the windows box, but i didn't see a point in fixing it as you have honestly just made it too easy to root(and therefore screw) your phone. i like the old way of doing things where we had to work it out on our own and if we wanted scripts and such we needed to write them ourselves. just throwing these thoughts out there
P.S. eugene your way took 10 minutes and my script took 8 minutes, your way worked fine except my power flickered while rooting so i had to wait for comp to reboot so i could continue.
P.P.S. thank you wes for this
tubaking182 said:
not to say that i am not grateful(i deffinately am) but why do we make it easier and easier to root our phones? isn't rooting supposed to be for the advanced users that know what can be done after root? shouldn't we just discover one method and leave it at that? i wrote a script as well that does this on the windows box, but i didn't see a point in fixing it as you have honestly just made it too easy to root(and therefore screw) your phone. i like the old way of doing things where we had to work it out on our own and if we wanted scripts and such we needed to write them ourselves. just throwing these thoughts out there
P.S. eugene your way took 10 minutes and my script took 8 minutes, your way worked fine except my power flickered while rooting so i had to wait for comp to reboot so i could continue.
P.P.S. thank you wes for this
Click to expand...
Click to collapse
back in my day we had to walk 15 miles up hill and we liked it...in the snow...naked
the other methods weren't exactly full proof, getting the loop to catch and stay in offline mode was a huge pain in the ass and the only known working method was to buy an a 16GB microSD. So yes, easier is better.
It's not like this is an exclusive club or anything...android is supposed to be open.
Not saying this should be exclusive, just saying that there are some people out there that are just too dumb to figure out how to do it and by making it easier we are just making more threads on main page telling us that WE broke their phone and that its <enter dev name here>'s fault that it didn't work. Not trying to fight just figured that we should stick to the stuff that means people have to know how to use a computer
Hi there! I need someone help because, i'm really lost. :X
I have one primux bora 7 with ICS 4.0.3 and i want to install the CM9 ROM.
I see in this forum and i download this files that see in this picture:
img231.imageshack.us/img231/1876/pict3012.jpg
After this i install the CM9 nightly and appears in me screen this:
img37.imageshack.us/img37/7249/pict3013.jpg
Until this it's ok.
Then, when i install compatibility mode and/or gapps, appears on my screen this: (and even with only .zip files in the external sd card appears that)
img22.imageshack.us/img22/7228/pict3015i.jpg
Then i reboot the device, and it enter on a boot loop mode, that i can't do anything. Even the tablet it's not recognizes in windows mode (usb drivers didn't work). Touchscreen didn't work to. I'm desperate to fix this. My question is:
Can anyone give me some help, that can permit me to install CM9 in this tablet. I need noob tutorials. I don't understanding nothing of this, and i appreciate some patient from user here. please!
Can anyone help me with this?
Best regards in advance!
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
This may help. http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
At least there is more going on for Firefox Open over there.
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Defier525 said:
Thanks but as you might have noticed I posted several comments there already, but I thought XDA would be the right place for unbricking devices.
Click to expand...
Click to collapse
Sorry! Eyes tight shut!
Are there any updates on this one?
I have bricked Open too, I'm attaching the PCB picture, if it is any help to maybe find UART or JTAG pins?
Can someone be really nice and please dump the bootloader from working ZTE Open in send it to me?
I've found some guy, who maybe can help me write bootloder with JTAG.
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
psywolf said:
I think this should work, but no promises: https://sites.google.com/site/zteopenfirmware/download-mode
Click to expand...
Click to collapse
Thanks for your time to help, but this does not work for me. I get an error, when I press flash button (printscreen under attachments).
I've tried to probe the pins with the multi-meter and found GND and V+ (picture under attachment)
Now it would be nice to have something like this -> http://www.grandideastudio.com/portfolio/jtagulator/
Defier525 said:
Hi folks,
unfortunately I somehow bricked my ZTE Open. I flashed cwm (worked fine) but after flashing both system AND userdata via flash_image, the phone won't boot and what is much worse it won't boot into cwm anymore as it hangs there with just showing the logo and the cwm version. The menus are missing, it does not react buttons and does not show up in adb. FTM mode is also non-functional, holding volup gets you also into broken recovery.
For earlier ZTE devices like the ZTE Blade it seems to be possible to low level flash them in diagnostics mode. Diagnostics mode is working fine on the ZTE Open (it shows up with the diagnostics port on USB. Luckily I also have all the 20 partitions backed up, but I don't know how to flash them in this diagnostics mode. I tried putting the files into the root of the SD card and including sha1/256/512 plus md5sum files, but it was not impressed by that. Not sure if this only works in FTM mode, though.
Any help would be highly appreciated! I highly assume that the procedure is the same as for the ZTE Blade.
Click to expand...
Click to collapse
tpt files for the zte open
https://www.dropbox.com/sh/rnj3rja7gd54s98/_twgXEkMFH/P752D04_DEV_EU_20131212_v1.2.7z
Thank you for the link. But what tool is supposed to be used to flash the files? And is there a way I can use my backup as well? In this case: how can I transform it to TPT files?
Update: I tried flashing it by following the instructions of the link posted by psywolf, but unfortunately I am getting the same error as aversario. I tried also flashing just recovery, but it seems like no single partition is flashed successfully.
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
aversario said:
So, I've ordered jtagulator and it showed the pins. Now I need jtag programmer, which one do you guys recommend?
And I am still looking for some great guy to share with me his bootloader of a functional zte open.
Click to expand...
Click to collapse
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
linr76 said:
on what partition is the bootloader? i have a UK revision 02 one, i would help you out if you tell me how to get the bootloader?
Click to expand...
Click to collapse
Well, I don't know the partition names by heart, but as I remember the bootloader is one of the small partitions (so definitely not system or boot or userdata or recovery).
The way to get that small partitions would be installing CWM recovery first -> http://pof.eslack.org/2013/07/05/zte-open-firefoxos-phone-root-and-first-impressions/
then enter adb shell on computer
su # to get root privileges
then it should be something like explained here -> https://www.youtube.com/watch?v=j3GOzUURSgM&feature=player_detailpage#t=153
And thank you very much for your time
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Sent from my V3 using Tapatalk
linr76 said:
If i figure out how to do that without CWM i'll upload it for you. Cannot install CWM because i need to be on stock recovery for development of update packages, sorry
Click to expand...
Click to collapse
OK, I get that. I'm sure there exists a way to do it without changing recovery also. I just can't figure it out because that's the only Firefox OS phone I've had.
try to reinstall
Hi, I bricked my ZTE Open (EU version) too. Had bought it from a German Ebay seller and tried to flash FirefoxOS 2.0 on my device. I don't have the CWM recovery installed, only the "Firefox OS System Recovery" Big mistake, I know . When I switch on the device, the Firefox OS logo appears, then disappeas after a few seconds, and so on, the perfect bootloop
I can't access the device via ADB or fastboot.
When I ty to install any downloaded zip (even from ZTE's homepage) from the SD card, I get following messages:
Code:
--Install /sdcard ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: signature verification failed
Installation aborted.
So there is no valid signature.
Can you help me please? Thank you!
Heinz
Found a solution by myself!:victory:
I downloaded the update.zip file from firefox.ztems.com (Update package of Android GB for OPEN device) and installed it.
After that I could flash the CWM recovery. It seems to work...
THL W5000 problems getting stuck on Boot, adb unauthorized/offline
Hello there Guys,
I already postet this in the XDA Assist Forum and I got redirected to here. So here´s my problem listed below. Hope for help from the Pros.
After I flashed a few tons of phones, this one gets me really p*ssed of. I can´t acces the THL W5000 with ADB, I can´t mount the SD-Card because in Recovery there is no Option for this to do so.
I cant push/pull files to/from the Phone. Got no luck with fastboot and it gets stuck on Boot screen, so I can´t accept my PC for adb to work.
And what I recently found out, the Bootloader is locked, so I can´t even Install from SD-Card. I got a new SD-Card with ROMs and TWRP, the Recovery is able to read the SD, but when I launch a .zip, it
suddenly appears the Message (in Dropbox the last Image):
Code:
-- Install /sdcard ...
Installation aborted.
I need help asap
When you need more Info please ask I will reply asap.
Folder with Pics from problem: dropbox.com/sh/hpiiqb72ngyl1fn/AACFDDrhpxA33xRDUEl7CksDa?dl=0 (I will provide more pics when needed.)
Thanks in Advance,
skorpion1298
Related to: forum.xda-developers.com/general/xda-assist/thl-w5000-problems-getting-stuck-boot-t3185514
push.
Phone works again, just got the right ROM, pulled it onto SD, plugged into the SD Slot, installed ROM from there and suddenly it worked all.
What a wonder!
Thanks to me
Hello, excuse my English but I'm Spanish and I used the translator, I hope someone can help me, it is that I have a fova orange and tinkering delete accidentally the launcher or something, the issue is that the battery alone carrying 50% and I made a reset from recovery and the result was catastrophic lol, to turn all black was seen and only the time and the battery appears, unfold the notification menu and just have no access to anything, I say I was root with kingroot but not There is no backup.
I tried everything:
1- from the factory recovery can not install an update that I found in the forum because I E: error in /tmp/sideload/package.zip (status 7), as original rom also gives me another error and this in CPB format.
2- from adb I can not because I have usb debugging enabled in fastboot mode and I did not recognize the PC and can not find anywhere drivers (ignition normal if recognized) plus I guess you also need the usb debugging.
3- I tried from the same phone but heard nothing but notifications can not be accessed.
Well that's all lol friends if anyone has any formulation would appreciate.
Cheers
sebas1979 said:
Hello, excuse my English but I'm Spanish and I used the translator, I hope someone can help me, it is that I have a fova orange and tinkering delete accidentally the launcher or something, the issue is that the battery alone carrying 50% and I made a reset from recovery and the result was catastrophic lol, to turn all black was seen and only the time and the battery appears, unfold the notification menu and just have no access to anything, I say I was root with kingroot but not There is no backup.
I tried everything:
1- from the factory recovery can not install an update that I found in the forum because I E: error in /tmp/sideload/package.zip (status 7), as original rom also gives me another error and this in CPB format.
2- from adb I can not because I have usb debugging enabled in fastboot mode and I did not recognize the PC and can not find anywhere drivers (ignition normal if recognized) plus I guess you also need the usb debugging.
3- I tried from the same phone but heard nothing but notifications can not be accessed.
Well that's all lol friends if anyone has any formulation would appreciate.
Cheers
Click to expand...
Click to collapse
Do you have a custom recovery ? If yes then making a flashable zip of a launcher and flashing it will solve your problem
sdeepb said:
Do you have a custom recovery ? If yes then making a flashable zip of a launcher and flashing it will solve your problem
Click to expand...
Click to collapse
The recovery is the original.
Thanks for your answer.
sebas1979 said:
The recovery is the original.
Thanks for your answer.
Click to expand...
Click to collapse
Is your stock recovery capable of flashing non OEM zips ?
I tried to install zip original and non-original and always gives me errors and similar errors signature except an update that gives the following error :
"/system/app/logkit.apk" has unexpected contents.
E:Error in /tmp/sideload/package.zip (status 7)
sdeepb said:
Is your stock recovery capable of flashing non OEM zips ?
Click to expand...
Click to collapse
I tried to install zip original and non-original and always gives me errors and similar errors signature except an update that gives the following error :
"/system/app/logkit.apk" has unexpected contents.
E:Error in /tmp/sideload/package.zip (status 7)