yotaphone_flasher won't install - YotaPhone

Hi, I posted this under thread "yotaflasher" but no response... Apologies for any apparent newbie ignorance of protocol:
Yotaphone_flasher won’t even install!
Hi, i’m having trouble even installing yotaphone_flasher.exe on my ancient windowsXP PC. I get an “unable to locate component” error when I run the installation: the file missing is MSVCR100.dll. I’ve tried re-downloading but the error always comes up... HELP this whole process is driving me insane!

Could someone please provide the file MSCVR100.dll from their yotaflasher installation? I'm hoping I can place this in the right place manually to get this working...

nutsoboy said:
Could someone please provide the file MSCVR100.dll from their yotaflasher installation? I'm hoping I can place this in the right place manually to get this working...
Click to expand...
Click to collapse
That file is part of the Visual C++ library so you can fix it by installing that.
64bit: https://www.microsoft.com/en-us/download/details.aspx?id=14632
32bit: https://www.microsoft.com/en-in/download/details.aspx?id=5555

Amplificator said:
That file is part of the Visual C++ library so you can fix it by installing that.
Click to expand...
Click to collapse
Thanks! I will give it a go.
Shamefully I confess my main desktop computer is a Mac so I'm trying to flash my yotaphone 206 using an ancient WindowsXP PC?. I don't think the USB ports are even 2.0
Do you think this is going to work?
Thanks again...

nutsoboy said:
Thanks! I will give it a go.
Shamefully I confess my main desktop computer is a Mac so I'm trying to flash my yotaphone 206 using an ancient WindowsXP PC?. I don't think the USB ports are even 2.0
Do you think this is going to work?
Thanks again...
Click to expand...
Click to collapse
Sure, I don't see why not. It will just be slower. USB is backwards compatible
But I'm an Arch Linux user where all these ADB drivers etc. are not an issue; plug in the phone and it just.. works, for all phones and tablets
Why not just use fastboot to flash the rom you want on your Mac?
Download the zip for the rom you want from Yota Devices, unpack the file and flash the files one by one
Edit:
Or even easier, just put the zip on the internal storage, reboot to recovery and flash it that way.
If you do go with the Windows route and your usb ports for some reason are not at least 2.0, the only thing to keep in mind is that it will just be a lot slower but should work just fine

Amplificator said:
Why not just use fastboot to flash the rom you want on your Mac?
Download the zip for the rom you want from Yota Devices, unpack the file and flash the files one by one
Edit:
Or even easier, just put the zip on the internal storage, reboot to recovery and flash it that way.
If you do go with the Windows route and your usb ports for some reason are not at least 2.0, the only thing to keep in mind is that it will just be a lot slower but should work just fine
Click to expand...
Click to collapse
I got overwhelmed reading all the threads here about problems flashing a CN206 to achieve 201/Lollypop. Your suggestions seem very sensible but at the same time fill me with trepidation.
Would you mind explaining step by step the process of using fastboot via Mac? Is fastboot an app or a connection procedure?
As you'll realise I'm a complete novice when it comes to technical stuff, I've been using computers to earn a living for 25 years but they've been macs!

nutsoboy said:
I got overwhelmed reading all the threads here about problems flashing a CN206 to achieve 201/Lollypop. Your suggestions seem very sensible but at the same time fill me with trepidation.
Would you mind explaining step by step the process of using fastboot via Mac? Is fastboot an app or a connection procedure?
As you'll realise I'm a complete novice when it comes to technical stuff, I've been using computers to earn a living for 25 years but they've been macs!
Click to expand...
Click to collapse
I've never used a Mac before so you are probably better off looking here: http://forum.xda-developers.com/showthread.php?t=1917237
..or doing a google search if that link is not enough for whatever version of OSX you are using.
CyanogenMod does a good job of giving a quick explanation of what fastboot is: https://wiki.cyanogenmod.org/w/Doc:_fastboot_intro
But basically no matter how much you bricked your device you can always just boot into this mode and re-flash a working rom, so take note in the Settings -> About Phone what region your rom is.
The rom I'm currently using has a build number of: LRX21M.5.0.0-RU1.1.134 <-- RU is the important part, because knowing this you can always revert back to that rom if you brick anything. Here's the link for the Yota Devices ftp server with roms for all regions: ftp://fw.ydevices.com/YotaPhone2/Firmwares/
You can access fastboot using either volume up + power button or volume down + power button, I've forgotten which
Fastboot is always used to flash new recoveries for example, just like TWRP for our YotaPhone 2:
http://forum.xda-developers.com/yotaphone-one/development/twrp-3-0-2-0-yotaphone-2-t3494023
http://forum.xda-developers.com/yot...wrp-twrp-2-8-5-0-recovery-yotaphone2-t3142024
When you download a rom from Yota Devices as a .zip file it contains a bunch of files that are more or less images of partitions.. So what you do when flashing is essentially just restoring the rom image to the System partition and all the others.
What I imagine people are having problems with when flashing cross-region roms is that they install the baseband from a region which their device doesn't fully support, which could indeed result in issues. Yota Flasher will very likely do this, as this is a simple tool that just downloads whatever rom is the latest for the region you pick and then it flashes it. It does not take cross-flashing of various basebands into account.
What you can do then is to just install the baseband that is actually meant for your device after using the Yota Flasher, or if you manually flash all .img files from a zip, just simply not flash the new baseband.
The latest RU rom for example, on the Yota Devices ftp server, is version 124, which will OTA update to 134 once installed.
Link for the RU rom is here: ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/5.0.0-RU1.1.124.zip
Inside this zip file are these files:
Code:
Archive: 5.0.0-RU1.1.124.zip
inflating: 5.0.0-RU1.1.124/emmc_appsboot.mbn
inflating: 5.0.0-RU1.1.124/userdata.img
inflating: 5.0.0-RU1.1.124/recovery.img
inflating: 5.0.0-RU1.1.124/boot.img
inflating: 5.0.0-RU1.1.124/system.map
inflating: 5.0.0-RU1.1.124/system.img
inflating: 5.0.0-RU1.1.124/cache.img
inflating: 5.0.0-RU1.1.124/radio/rpm.mbn
inflating: 5.0.0-RU1.1.124/radio/sbl1.mbn
inflating: 5.0.0-RU1.1.124/radio/tz.mbn
inflating: 5.0.0-RU1.1.124/radio/NON-HLOS.bin
So what you would do is essentially just flash the relevant parts and not flash the irrelevant parts, such as radio if you have a different devices with other bands.
VirtuaLeech gives an example in another thread on using fastboot: http://forum.xda-developers.com/showpost.php?p=69461892&postcount=76 with the -S flag which splits the transfer due to size limitations.
It can all probably sound really technical if you are new to this, so I strongly suggest you flash using Yota Flasher first, then read up on fastboot if you want
It does take a bit of reading, but using fastboot you can always restore your device to any rom you want, no matter if you brick it trying out new stuff.
The worst that could happen is that you will lose the data currently on the phone so you'll have to set it up from scratch, but at least fastboot will ensure that you can always reflash to a working rom.
This goes for more or less every device out there. Fastboot is a tool from Google, so it's pretty generic stuff

Wow that’s very helpful thanks!!
Although I am intrigued by this:
Amplificator said:
Or even easier, just put the zip on the internal storage, reboot to recovery and flash it that way.
Click to expand...
Click to collapse
To try this do I copy the file I want eg. from ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/onto my yotaphone using Android File Transfer? Which directory should I put it in on the phone? Downloads?

nutsoboy said:
Wow that’s very helpful thanks!!
Although I am intrigued by this:
To try this do I copy the file I want eg. from ftp://fw.ydevices.com/YotaPhone2/Firmwares/RU/onto my yotaphone using Android File Transfer? Which directory should I put it in on the phone? Downloads?
Click to expand...
Click to collapse
The zip file should be in the root of your internal memory and be named "update.zip" - without the quotes, of course.
Then you reboot into recovery by using volume down + power or volume up + power, again, I gotgot which one boots into recovery and which one enters fastboot mode.
But in the recovery menu you get an option to do the usual stuff you see on all phones, such as factory reset, flash an update etc.
Just keep in mind what I wrote about the baseband which will be flashed by using this method. What you would do then is after flashing the zip you would reboot into fastboot mode and then flashing the baseband/radio that fits your phone model.
Obviously everything is at your own risk and I don't promise anything.. yada-yada disclaimer .. but you need adb and fastboot set up first before attempting anything.
When adb is set up you can even reboot your phone straight into recovery by using "adb reboot recovery" for ease of use.
Things like "adb reboot fastboot" etc. also works.. but by reading about fastboot you will learn that stuff
Also, running "fastboot --help" will show you more options, such as the -S flag, unlocking bootloader, flashing recovery and all that stuff.
You can also sideload using adb which a russian guy wrote on a russian forum: https://translate.google.com/transl...topic=550302&st=6820#entry47048257&edit-text=

Amplificator said:
That file is part of the Visual C++ library so you can fix it by installing that.
64bit: https://www.microsoft.com/en-us/download/details.aspx?id=14632
32bit: https://www.microsoft.com/en-in/download/details.aspx?id=5555
Click to expand...
Click to collapse
OK so I now have yotaflasher working but next up I'm just getting 'waiting for device' while phone is showing 'downloading'.
Does this mean there is a problem with my USB drivers?
When I plug the live phone into USB the PC offers 4 choices: synchronise files/open to view files/sync digital media/take no action
I take this to mean USB driver is working...

nutsoboy said:
OK so I now have yotaflasher working but next up I'm just getting 'waiting for device' while phone is showing 'downloading'.
Does this mean there is a problem with my USB drivers?
When I plug the live phone into USB the PC offers 4 choices: synchronise files/open to view files/sync digital media/take no action
I take this to mean USB driver is working...
Click to expand...
Click to collapse
You just need to fix the adb driver.. driver issues are faily common on Windows.
Check the other threads where this has been discussed already.. it's just one of the joys of using Windows

Related

[How To] Root

TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related

Help me please, how to restore original firmware?

Dear developers,
I have deleted (by mistake) program Launcer from my Smartphone and now it is not going to load. When I turn on it, there is only symbol of IDEOS. After a minute symbol starting to twinkle, but system not loading.
Could you please tell me how can I return to original firmware?
I hope someone will be able to support me.
If the launcher is the problem, you can just install another, or push again the original from a rom via adb. I assume that the device is rooted(I think you cannot delete a system app if isn´t). If you can connect to pc, then possibly you can install a launcher from huawei' s suite(I´m not sure because I don' t use windows and I haven't try this app) or from a android file manager like QtADB, Android commander or Droid Explorer. You can also install it only with adb via windows command prompt:
http://www.brighthub.com/mobile/google-android/articles/37151.aspx
And maybe, if wifi is enabled and connected, you can just install a launcher from market via pc' s web browser:
https://market.android.com/
The Modaco wiki has a list of original firmwares, but no link to Huawei works anymore. However, it is possible to download the latest China Unicom firmware - which does contain english language support. That should at least get you started.
As a new user I can't post links yet, but it is easy to find if you look for u8800 software, and then switch to Chinese.
Put the extracted directory (dload) on an sd card, in the top/root, put it in the phone and then hold volume down and power on.
Note, this will blow everything away to start from scratch so make sure it is what you want. In addition everything will be in Chinese so you need to be able to navigate to the settings to set it to English.
Better ideas? I am a noob myself so no guarantees...
I have unrooted it before to delete some trial games. And deleted Launcher by mistake.
I can't connect via usb now.
I'm afraid if I upgrade firmware, I have less memory because old one will not be deleted. Or maybe I'm wrong?
No, you're not gonna have less memory.
Did you tried to wipe to factory defaults from recovery mode(power button and vol+)?
You will not have less space because an original firware will format everything from boot partition, system and data... Basically , it will give you original software and status like it came from factory ... Like the other user said, jut find it, extract it , put the dload directory to the root of you sd card and hold volume down and start up the phone ... You will see a progress bar and when it is finished , the phone will restart itself, you will have to wait longer due to the creation of new files and there you go
vladislavnm said:
I have unrooted it before to delete some trial games. And deleted Launcher by mistake.
I can't connect via usb now.
I'm afraid if I upgrade firmware, I have less memory because old one will not be deleted. Or maybe I'm wrong?
Click to expand...
Click to collapse
Install recovery first, then you can connect your device to PC using recovery. If you have friend that have X5, copy the launcher. Else, just install Custom ROM.
The old one will be removed if you install custom ROM. If I'm not wrong.
Recovery.
Unplug USB, turn off your phone, press and hold vol + and -, then press power. Hold those three buttons until it turned on and the screen is purple-pink.
Backup all image data(copy). The rest is in the link.
Sorry for my English. Hope you understand what I write..
dancer_69 said:
No, you're not gonna have less memory.
Did you tried to wipe to factory defaults from recovery mode(power button and vol+)?
Click to expand...
Click to collapse
You are magician. it works now.
hmmm... but there is no launcher application - no workspace available. it doesn't want to load as before. strange.
upgrade don't work too. It is cycle repeating of step1/2.
I just tested and found that you can copy the missing apk from bootloader mode. In this mode(power + vol- + vol+ buttons), when connected to pc via usb cable all partitions of device mounted(at least this happens on linux). So, you can navigate to system partition on /system/app folder and copy there the missing launcher' s apk file. You can find this file on a custom' s rom(or on an official' s rooted rom like modaco's roms) update.zip file. It's on system/app folder. I tested this on linux and I could(not as normal but as root user though) copy or delete files from there.
dancer_69, thank you for your support. At my side when I connect via bootmode, there is only flashdrive is visible.
It's really strange that it is not going to upgrade.
I'm able to apply sdcard:update.zip. So maybe if to put this application inside of the card, it could install. but I don't know how to do it.
I finded apk file and tried to install it but it don't receive file because it hasn't some certificate. ???
I think you have 3 options here.
1. flash an official rom(you put the dload folder of rom's zip file on root of sdcard and boot to bootloader mode. The update starts automatic)
2. Use a linux system(maybe a livecd) to access the other partitions.
3. Try to reroot the device from pc, via superoneclick app(you can find it here), so to have access to system again.
but I haven't access to installation program area. nothing!
I have only ability by pressing (vol + and on) to choose install update.zip from flash card.
so.
1. when I runned new firmware from dload it didn't install. it was cycling at first level (1/2)
2. linux is good idea. but I'm not sure that it's will be profitable. maybe I have turned off access to partitions inside of phone
3. I can't install superoneclick as I'm not able to install any application.
I hope we are closer to some geniously idea. I have bought phone yesterday and we haven't service center in our city. So, I need to buy the other one.
This is not so serious problem, it' s not hardware, it´ software related. And I think you cannot turn off access so easy.
The superoneclick is a pc application. You don't need to install something on device(if I remember well, because I use it once before a long time). You can try it.
And you can try linux too.
I don't think that this is a problem that only service can solve it.
What firmware you tried? Try another one. And better try to find the one that you device has(if you know it)
Thank you for positive opinion.
1. Will try to change firmware as you said. Try 2 more firmware from Huawei.
2. Superoneclick needs approval from phone, today night I wasn't able to run it.
3. I'll try Linux too.
dancer_69 said:
This is not so serious problem, it' s not hardware, it´ software related. And I think you cannot turn off access so easy.
The superoneclick is a pc application. You don't need to install something on device(if I remember well, because I use it once before a long time). You can try it.
And you can try linux too.
I don't think that this is a problem that only service can solve it.
What firmware you tried? Try another one. And better try to find the one that you device has(if you know it)
Click to expand...
Click to collapse
Thank you very much for your excellent support. It's work now after trying of other firmware. Everything is excellent now.
I only noticed that battery is no very capacitive.
Please, send me your paypal account, I want to donate you a little.

[Q] Using fastboot.

So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot (following instructions here on the forum) mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
a friendly warning
CyaN1de said:
So I am not quite sure what exactly fastboot is supposed to do. I know you can flash recoveries, bootloaders, etc with it but that is about it for my understanding.
I tried to get into fastboot mode earlier today and while the tablet gives me the fastboot message in the upper left, windows says that fastboot failed. Is there a folder I am supposed to be running cmd prompt from?
Sorry, still new to this stuff and my understanding of some of these tools is limited at best.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
dibb_nz said:
Give me 30 mins got all the reading u gonna need b4 u make an attempt
if u fk up in here there is definitely NO WAY BACK in meantime you'll
Want to set adb as environmental variable in windows gonna make it
Helluva lot easier . Android sdk will too. f u don't know what I'm on About..
.best do some reading up on these as well.
Fast boot ain't something someone else can talk u thru and I doubt the devs will
Have any sympathy for anyone asking ....i bricked my tab pls help....
Click to expand...
Click to collapse
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
CyaN1de said:
Running adb from its native folder is not an issue.....is fastboot the same way having to run cmd from folder that a file is located?
I prefer not to mess stuff that I do not fully comprehend (not that I fully comprehend ANY of this) but some of it makes more sense once you are into it rather than reading someone elses interpretation.
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
yeh just a group of extended adb commands that allow you to do some pretty awesome stuff - like really, really bricking your tab for instance, lol. I'm unsure as to whether all the fastboot commands are available to us - i havent had enough spare time to devote to heavy duty reading in the Dev Forums!!!! You can flash everything in here so its like a supercharger;;;;Sort of like going from timmydeans EUU root to Civ's nvflash unlocking bootloaders thing, if you know what i mean.......
But heres some reading, most of it tutorial step by step stuff, mostly for other devices which may not apply to our tab but definitely apply to fastboot. AS you know, there is alot of info in our own dev forum but its hard to find a flow as the devs actually speak a different language to us!!!! So the tutorials are quite good in that respect as they use noob-ite speak
the backup and restore tute is a goody, couldnt get it going on v3 so looking forward to giving it a go on v4 (when i can find a quiet 30 mins or so, that is)
anyways happy reading be interested in your thoughts and keep us posted about what you get around to trying
rgds
Full Phone Backup http://forum.xda-developers.com/showthread.php?t=1420351
setup adb http://forum.xda-developers.com/showthread.php?t=1249798
adb http://forum.xda-developers.com/showthread.php?t=879701
adb logcat http://droid-force.com/showthread.php?tid=150&pid=573#pid573
ics BL by Skrilax_CZ http://forum.xda-developers.com/showthread.php?t=1514951
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Set up adb/fastboot for noob-ites 101
CyaN1de said:
So I located Fastboot in D:\Android\android-sdk\platform-tools\Fastboot.exe
But putting tablet into fastboot mode yields the driver installer to report that "Device driver software was not succesfully installed".......Fastboot X Failed....is this normal? Will it run when I use cmd prompt from D:\Android\android-sdk\platform-tools?
I guess a little linux knowledge would go a long way.....too bad I can't get a grasp on that either.
Thanks for the links.....hopefully I can find time to give a read.
Click to expand...
Click to collapse
weird??? i kicked straight in to bl, fastboot drivers installed, never saw red x
u mean u arent cmd from platform tools???
in the cpuid guide I suggested extracting the just_adb.zip into C:\ so setting
up the env. var. would be easier I have been meaning to post the steps for
doing that, guess theres no time like the present
Set adb as Environment Variable or call adb direct from command prompt
............ first, copy the path to your install - in your case:
............ "Path to adb" = D:\Android\android-sdk\platform-tools
1. Click on the Start menu
2. Right click on Computer
3. Click on Advanced system settings
4. Click on the Environment Variables button
5. Look for Path in the System Variables section. Double click on it
6. Go to the end of the Variable value box and put in a semicolon ;
7. Now paste your "Path to adb" after the ;
8. it should look like this in your case ;D:\Android\android-sdk\platform-tools
9. Now test it out - start - run/search - cmd - in cmd window type: adb devices
10. If you've followed the steps you will see your device ID - voila!!!!
as you can see this makes trouble shooting so dam easy -
if you cant get a device id do not go any further in what u r doing
cos it aint gonna work....period!!!!! also since ICS has screwed
with getting our cpuid like this, for our purpose here, it is only important
that a device id is shown - not how right or wrong it is.....clear????
so getting back to it, check fastboot*.exe in same folder as adb.exe -
it came like this in my own setup not sure about the asdk setup -
remember too fastboot only has a few commands and i still havent
got round to trying them all out yet....
to anyone following this, I cannot say enough how dangerous this can be
please, please, please take a moment to read thru just one of the links i
posted earlier - they are tutorials and if you see the dev thread regarding
v4 unlock...you will not only learn something amazing but begin to
appreciate and respect the work done by these devs who laid the groundwork
that enabled civato and blakthund3r to produce what they have with the
unlocked bootloader - without this groundwork we would still be waiting
for a way to get full root access and cwm, custom roms, themes and mods......
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
CyaN1de said:
Thanks for that
Seems my Windows skillz need brushing up on again too....LOL
C:\Users\username>adb devices
List of devices attached
11717XXXXXX device
Click to expand...
Click to collapse
sweet m8 -
yeh whoever thought windoze would actually be useful!!!!
which i guess is freakn handy as having to go linux would spin me out....
what can i say??? I'm a child of windoze had no choice, forced-addiction
before i was born, lol - breaking the habit, but always go back, goddamit
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Trying just "fastboot reboot" (not wanting to go any farther until I get a grasp...HAHA) I get "waiting for device"
CyaN1de said:
OK....I get the adb ok.
But when I put tab into FB i get the driver error (see attachment). I suppose that I should not be getting this?
Click to expand...
Click to collapse
dont let windows install
choose let me choose where to install dunno exact wording
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
CyaN1de said:
Does not give me a choice.
Driver is located at D:\Android\android-sdk\extras\google\usb_driver ???
This is making my head hurt....LOL
Click to expand...
Click to collapse
Yr head hurts????
Ive updated the cpuid guide u my wanna take 5 min timeout to read it, the answers r all in there
I don't use full sdk there's a link to mini sdk zip in that post just has ad and fast boot
I've never had to use google drivers
Just plugged my tab in and its just 'worked'
DL Acer drivers if u haven't already . These are the most important ones to have installed right.
Disconnect and reboot everything
Run Acer setup.exe
Plug USB in
Go into fast boot, win doze will want to install f/b drivers let win doze do it, but if they fail, then run again and choose let me install, blah, blah, blah
What OS u got? Vista/win 7 don't normally have any probs
Acer drivers have been installed and all relevant sdk packages installed and up to date AFAIK. (USB_Acer_1.06.1500_A30HA31H_A.zip)
Had no issues installing ICS Bootloader V.3 manually through APX (no auto script) via instructions so I know I can at least do that well.....LOL
Might have to try reinstalling USB drivers and see if that helps.
Thanks
EDIT: Reinstalled USB Drivers now I can't get adb working....F#@K!!!!!!!!!
EDIT II: Re-Re-Installed Drviers and ADB working again...yay...LOL
EDIT III: Used A500_Manager.exe, clicked on "Enter Fastboot" and windows installed and recognized drivers......DBL YAY!!!!
C:\Users\username>fastboot reboot
rebooting...
finished. total time: 0.165s
Now.......to Brick this puppy.....
Thanx for your help dibb_nz....looks like all I needed in the first place was a driver reinstall...HAHA.
Hek m8 for a second or two there, I was feeling ya pain, lol
Oh but the elation when it finally happens!!!!!
I dunno why those drivers act out like that, but it always the same....
Fail, reinstall, fail, reinstall u can understand why peeps get frustrated
Glad u got it m8

Root and Install Custom Rom on Xoom WiFi (Wingray)

Hello, I have a stock XOOM WiFi (Wingray) and have been looking at installing a custom ROM. I am doing it for fun, knowledge, and to hopefully get a little better performance out of my XOOM.
I currently use my xoom for Web Browsing, XBMC, and Sling Player...
I have been searching the Web and this Forum for information on how i can do this, step by step but i am lost. I know that i have to do the following:
1.Unlock Boot loader (Lord AIO Tool, was unsuccessful which is why i started the thread to post useful links after i succeed.)
2.Modify the Recovery Partition.
3.BigPart
4.Install Custom ROM (Based on whatever Android Ver / Kernel)
I am running Mac OSX 10.8, have a windows VM, and access to a windows laptop if needed.
*EDIT*
Results: I used my Windows Laptop and started to have some success with the Lord AIO Tool. i dont see why the VM wouldn't work, but i had given up on the VM thinking it may have cause a problem.
Steps Needed:
1. Download Motorola Fastboot Drivers:
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
2. Download ADP Tool (or Install Android SDK and add appropriate locations to your System Path)
ADP Tool: (Awesome)
http://forum.xda-developers.com/showthread.php?t=2588979
Android SDK:
http://developer.android.com/sdk/index.html
3. Download Lord AIO Tools: (also, Awesome)
http://forum.xda-developers.com/showthread.php?t=1468298
4. Download the ROM you need. I used OMNI 4.4.2 (Also needed Big Part, and this too is Awesome)
http://forum.xda-developers.com/showthread.php?t=2593757
Big Part:
http://forum.xda-developers.com/showthread.php?t=2506997
5. Download Super User Root zip file.
6. Format an microSD Card FAT32 and copy over the following files:
TeamWin Recover Partition
TeamWin Recovery Partition Big Part (only needed for ROMs that need larger partition.
Super User
OMNI ROM (or whatever ROM you want)
GApps (one of the Google Apps. I used the gapps-wingray-kk-20131223.zip)
7. Follow Instructions for Lord AIO Tool installation and then do the following:
Run the tool and unlock the boot loader (enter option 03, not 3, but 03)
When done you need to install The recovery partition, i used TeamWin RP. (This is option 09 in the Lord AIO Tool)
Then i rebooted into recovery mode and was in the TeamWin RP menu. From there i Flashed the BigPart, then ROM, then Gapps, and then the Super User to Root.
I think there is an option to Root from the Lord AIO Tool, but i dont think i used it at all.
I was trying stuff all day and when it's all said and done I think that's basically what i did, things didnt always work on the first try and i had some trouble mounting the microSD in the Recovery Partition.
I put this here to hopefully give people new to the game a run down of what to do. i did a lot of searching yesterday and was spinning my wheels. and some of the old threads i found were quite technical and had dead links. (not necessarily from XDA) It's not a Step by Step for the XOOM but will hopefully get people who are late to the game a good start.
tonycajjo said:
Hello, I have a stock XOOM WiFi (Wingray) and have been looking at installing a custom ROM. I am doing it for fun, knowledge, and to hopefully get a little better performance out of my XOOM.
I currently use my xoom for Web Browsing, XBMC, and Sling Player...
I have been searching the Web and this Forum for information on how i can do this, step by step but i am lost. I know that i have to do the following:
1.Unlock Boot loader (Lord AIO Tool, was unsuccessful which is why i started the thread to post useful links after i succeed.)
2.Modify the Recovery Partition.
3.BigPart
4.Install Custom ROM (Based on whatever Android Ver / Kernel)
I am running Mac OSX 10.8, have a windows VM, and access to a windows laptop if needed.
*EDIT*
Results: I used my Windows Laptop and started to have some success with the Lord AIO Tool. i dont see why the VM wouldn't work, but i had given up on the VM thinking it may have cause a problem.
Click to expand...
Click to collapse
I use the Lord AIO Tool on desktop Windows 8.1 and when I ran the Set_Up.bat as Admin, it say file is missing. Not sure what i did wrong.
cat2115 said:
I use the Lord AIO Tool on desktop Windows 8.1 and when I ran the Set_Up.bat as Admin, it say file is missing. Not sure what i did wrong.
Click to expand...
Click to collapse
i did not need to run as Admin, possibly cause the user was already admin. i had issues when i ran as admin... that's one thing i forgot to add above. (I ran it on Win7 32-Bit)
2. Download ADP Tool (or Install Android SDK and add appropriate locations to your System Path)
ADP Tool: (Awesome)
http://forum.xda-developers.com/show....php?t=2588979
Android SDK:
http://developer.android.com/sdk/index.html
also, try moving LAIOT to C:\ if not already there.
after you install ADP tool you may have to reinstall LAIOT, delete the files and just start over using the setup.bat
Stuck on step seven
I will be very grateful of any help stuck on step seven it says too many parameters
floydme said:
I will be very grateful of any help stuck on step seven it says too many parameters
Click to expand...
Click to collapse
what part of step 7? my step 7 is pretty broad.
tonycajjo said:
what part of step 7? my step 7 is pretty broad.
Click to expand...
Click to collapse
After running setup bat on the second return key hit I I get too many parameters message
Perfect (step by step)
Followed this step by step, utilizing this process as well as the individual threads regarding each part (Big Part Partitioning, LORD AIO Tool-with file folder placed on "C" drive, etc.) and worked like a charm.
This thread should become sticky and placed at the very top for Xoom Rooting guide.
Stingray Xoom
kamikazebeats said:
Followed this step by step, utilizing this process as well as the individual threads regarding each part (Big Part Partitioning, LORD AIO Tool-with file folder placed on "C" drive, etc.) and worked like a charm.
This thread should become sticky and placed at the very top for Xoom Rooting guide.
Stingray Xoom
Click to expand...
Click to collapse
good stuff, glad it helped.
floydme said:
After running setup bat on the second return key hit I I get too many parameters message
Click to expand...
Click to collapse
can you write explicitly what the error says, and when you hit "enter" the second time what are you exactly hitting enter to?
also include a bit of info on what OS you are using, where you have stuff installed, and so on.

A500 ICS Full Update files Decrypted for bricked tablets- Links Valid

So for Stock A500 users stuck at the Acer Logo, or maybe some other strange issue with the tablet not booting, you may want to try this method first before rolling up your sleeves and moving on to getting your UID, which involves the use of Linux for the most part.
Download these full ICS Update files for the A500 (501 owners can try this also, but you'll have a 500, but that might can be changed later)
These files are already "decrypted" and are named differently as to keep them separate. Download them all to a folder.
Now, select one of them, rename it to "update" (end result is a file called update.zip) copy it to SD card, boot tab and see if it installs. If it hangs on the install, delete it from SD card, and do the same with the next. Hopefully one of them might take. You may have to try all 4 of them before one works. It's hit and miss.
http://d-h.st/Zf8
http://d-h.st/2cm
http://d-h.st/gw8
http://d-h.st/KXl
Mega Links:
https://mega.co.nz/#!lM5iQYLZ!TKx3ZIsN1-L4-Lk2LveHhEjb-PejZ1ZNZPwdsBsuNZM
https://mega.co.nz/#!8R5X3T6C!D-j_EcGhkWyhG8nyprhimcic_uf2chA-rXlnqaLIe7k
https://mega.co.nz/#!sBwwVDQB!cDmVCNH63i-eAMnvtrro7rMGjXDMJPqJbgbXjzX6jDQ
https://mega.co.nz/#!MQhB1L5R!Dj06bqJVgXZ1JAnLGvX1CuUqNs3lXtg8NkxkfbU4osY
Hope this gets you going.
MD
Bricked Iconia A500 working again
Hi, after nearly 3 years my Iconia A500 bricked when I tried to play a viseo file via the usb port.
After reading the forum I tried the first update zip file from this thrread and BINGO it worked
Thanks guys for the good job done:good::good:
studioph said:
Hi, after nearly 3 years my Iconia A500 bricked when I tried to play a viseo file via the usb port.
After reading the forum I tried the first update zip file from this thrread and BINGO it worked
Thanks guys for the good job done:good::good:
Click to expand...
Click to collapse
How long does it take to load, how long should I wait to try the next one?
gonka95 said:
How long does it take to load, how long should I wait to try the next one?
Click to expand...
Click to collapse
Because it is some weeks ago I can't remember how long it took to load but it was not extreme. I think all was done in 1 or 2 hours. But during the process you get already some info that the tablet is working "normally"
Good luck with trying, my tablet is still working fine
PH
I have try with all update.zip and my tab is always block on "Android" logo.. can u help me?
megoza said:
I have try with all update.zip and my tab is always block on "Android" logo.. can u help me?
Click to expand...
Click to collapse
First of course, is that the file must be renamed to just "update.zip" and if you are doing this from a Windows machine, you may not see the ".zip" part. Do not be worried about that and just rename to "update". I copied each file, in turn, to the MicroSD card BEFORE renaming the file. That way, you retain the original and don't end up with "update", "update(1)", update(2), etc.
Have your Iconia A500 fully charged and powered off. Disconnect the power cable. Install the MicroSD, loaded with the "update.zip" file (the gold contacts side of the card face the screen side on the A500) into the card slot in the top of the Iconia A500. Holding the left side of the Volume Switch down, press and hold the Power Button down. When the tablet powers up, release just the Power Button. When you see the writing appear in the top left corner of the screen showing that it is loading the update file, release the Volume Switch. You should shortly see an Android figure with a spinning ball of triangles (not sure of the correct geometric term) in its belly. If the Android changes to laying down, with a red triangular exclamation, that version did not work. You should see a light blue thin progress bar if it is loading.
---------- Post added at 03:14 PM ---------- Previous post was at 03:01 PM ----------
I tried the different files. The "41-124-01-update.zip" loaded, but the progress bar only got about 20% - 25% along the way before not progressing any further. I left it overnight, and in the morning, it was still the same. The ball of triangles is still spinning in the Android's belly, but no progress is happening. The first time this happened, after an hour, I manually powered down the tablet, and then powered it back up. I got the buzz and the ACER logo (constant brightness), but it went no further. It just hangs there. And yes, I tried the external Factory Data Reset, and no, it did not work either!
Any ideas on what might be stopping the progress bar, or how to get the update to completely load?
Has anyone had any luck installing an alternative bootloader and then installing a different image?
Is this a software or hardware issue?
NOTE: My A500 Iconia experienced the exact same issue regarding failure to boot that has been described by hundreds on various forums. I was hoping that I'd finally discovered a fix.
Hi do you mind upload these files again? They are no longer exist.....Thanks!
Aelliseu said:
Hi do you mind upload these files again? They are no longer exist.....Thanks!
Click to expand...
Click to collapse
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Moscow Desire said:
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Click to expand...
Click to collapse
Is this valid also for A501 and, if not, where can I find the update.zip for A501? Thanks!
lahor said:
Is this valid also for A501 and, if not, where can I find the update.zip for A501? Thanks!
Click to expand...
Click to collapse
Well, they will run on a 501, but you won't get 3g or GPS.
www.acer.ru has the 501 ICS update files. You will need to match the update to your current Operating System Build. The reason, is that they run "patch" updates. So if you've been running a custom ROM, you will need to roll back to a factory 3.x.x and use the matching update file.
Moscow Desire said:
Just checked and all links are valid.
I'll try loading them to Mega if I get time. Dev Host has become really slow lately.
MD
Click to expand...
Click to collapse
Thank you so much!!!! You save my tablet!!!!:good: :good:
Aelliseu said:
Thank you so much!!!! You save my tablet!!!!:good: :good:
Click to expand...
Click to collapse
I did?
I got no result with those 4 options. Tablet is stil dead. Do you have another option of file?
lahor said:
I got no result with those 4 options. Tablet is stil dead. Do you have another option of file?
Click to expand...
Click to collapse
Not really, you will have to use Timmy Dean's Rollback Tool.
Basically it's an EUUS 3.2.1 ROM that will reset your partitions. The only advantage to running TD's tool, compared to a regular EUUS, is that TD's tool installs it "pre-rooted with a CWM recovery".
Either way, you are going to have to go back to 3.2.1. No way around it.
And... you will need your CPUID number to do it. I hope you had a custom recovery installed, as it should have this number. If not, you will need linux to get it. Neither tool will run without it.
MD
Moscow Desire said:
So for Stock A500 users
MD
Click to expand...
Click to collapse
I used these update.zip's to upgrade my 4.0.2 to 4.0.3. Great, but I can't get adb to recognize the A500. Is there a trick to this?
My A 500 has not been modified, but I too had no result, or at least no positive result. Do I also need to use this Timmy Dean's Rollback Tool? I also don't have my CPUID number. I do have a laptop loaded with Ubuntu 14.04, so can I use that to get it?
rasmith3530 said:
My A 500 has not been modified, but I too had no result, or at least no positive result. Do I also need to use this Timmy Dean's Rollback Tool? I also don't have my CPUID number. I do have a laptop loaded with Ubuntu 14.04, so can I use that to get it?
Click to expand...
Click to collapse
Get your CPUID here, using Ubuntu.
http://forum.xda-developers.com/showthread.php?t=1751978
Download the following Timmy Deans 3.2.1 rollback tool and extract to your PC;
https://mega.co.nz/#!FFoxzRLY!fSmY49VDxCdr-hwv6Tw7GPLIzUQNOzSgDzmzAspwmNc
Run the PBxxx.exe and use administrators rights, Wait till it gives the pop up to put your tab in apx mode and do it and connect. Enter uid number.
Hope it works. Remember that acer no longer has ota servers, for a year now, so you will have to do a manual update.
Thanks for the information MD. I will try this and report back here my results.
Moscow Desire said:
Not really, you will have to use Timmy Dean's Rollback Tool.
Basically it's an EUUS 3.2.1 ROM that will reset your partitions. The only advantage to running TD's tool, compared to a regular EUUS, is that TD's tool installs it "pre-rooted with a CWM recovery".
Either way, you are going to have to go back to 3.2.1. No way around it.
And... you will need your CPUID number to do it. I hope you had a custom recovery installed, as it should have this number. If not, you will need linux to get it. Neither tool will run without it.
MD
Click to expand...
Click to collapse
I am back without results.
1. need linux- i have a linux (Ubuntu ) on my comp
2. I saw the instructions but:
He says: You need to install this: Install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev . where can I find those files and how can I install this?Do you have one package for all files or some links?
I tried to get some file and I begin with gcc apx.c -o apx -lusb-1.0 , then I get on my terminal
[email protected]:/home/deni/Bureaublad# gcc apx.c -o apx -lusb-1.0
apx.c:1:31: fatal error: libusb-1.0/libusb.h: Bestand of map bestaat niet(this is dutch)
#include <libusb-1.0/libusb.h>
What I need to do in this case?
3 Tablet in APX mode? How can I know when my tablet in APX mode is?
4.With all erorrs I tried to type ./apx (rename the apx.c) but I get the message: acces denied??
[email protected]:/home/deni/Bureaublad# ./apx
bash: ./apx: Toegang geweigerd
I need a Help
lahor said:
I am back without results.
1. need linux- i have a linux (Ubuntu ) on my comp
2. I saw the instructions but:
He says: You need to install this: Install GCC, lsusb, libusb-1.0.x, libusb-1.0-dev . where can I find those files and how can I install this?Do you have one package for all files or some links?
I tried to get some file and I begin with gcc apx.c -o apx -lusb-1.0 , then I get on my terminal
[email protected]:/home/deni/Bureaublad# gcc apx.c -o apx -lusb-1.0
apx.c:1:31: fatal error: libusb-1.0/libusb.h: Bestand of map bestaat niet(this is dutch)
#include <libusb-1.0/libusb.h>
What I need to do in this case?
3 Tablet in APX mode? How can I know when my tablet in APX mode is?
4.With all erorrs I tried to type ./apx (rename the apx.c) but I get the message: acces denied??
root[email protected]:/home/deni/Bureaublad# ./apx
bash: ./apx: Toegang geweigerd
I need a Help
Click to expand...
Click to collapse
Moscow Desire Thanks!
I have know Jellytime 4.3 on my tablet.Need a 10 days to make this. In the beginnig everything was difficult but now it seems so simple and easy.
My description for more clarity:
1. UBUNTU last version
2. In this version you have a GCC but not libusb-1.0-dev. The best option is synaptic package manager. Install this from UBUNTU software center.
Open the synaptic and search the all files with libusb -you will get the list with the required files . Just install the all!
3.Make or download apx.c. If you have 32 bit you can use code from this site (something about printif changing). Make the folder APX on Dekstop and put file apx.c there .
4. Open the terminal ( if you can not find the terminal(no experience with UBUNTU , just in search type terminal).
5. In the terminal type dir or ls,. You can see the all folders and then type
cd Desktop/APX. If you get something strange or you get no result try to type sudo su for "refresh"
6. type gcc apx.c -o apx -lusb-1.0
7. If you get message with errors this mean that your libusb 1.0 dev is not installed. If you see a new file apx near your old file apx.c then is OK
8.type ./apx .....(if you get the message acces denied or cannot open device just type sudo su for refresh)and your CPUID is there.
9. then you need SBK
10. Download V8-UNL-ICS-HC-bootloader-MULTI-cwm.zip and unzip this
11.Make APX mode on your tablet ( push reset button(with needle) then power(with finger ) ) everything is black(that's good) and you are ready.
12. open the V8-UNL-ICS-HC-bootloader-MULTI-cwm with V8.bat file, and follow instructions. Use your SBK, choose option 2 and go next(two times). When you get PASS on your tablet your tablet is ready.
13. Download the jellytime 4.3 with GAPPS to your microsd. from
http://forum.xda-developers.com/showthread.php?t=2376662 or HC 3.2 for ( in my case) A501 from this forum
no need to change name to update.zip .
14. The next step: Volume down +power (you are going to the recovery mode) and folow the instructions
Boot in recovery mode to flash theJellytime or HC3.2.
First, don't forget to execute a 'Wipe Data/Factory reset'
Flash the Jellytime
Flash the Gapps
Do a 'wipe cache partition'
Reboot
15. That's it!
16. Enjoy!

Categories

Resources