Related
hi i have just installed the ROM manager software from the market and after deleting this my hero flashing option screen not coming its shows like that i have attached the pictures please help me i have hard reset the phone its start working but the flashing options still gone & i m unable to install any other ROM ,suggestions from the Experts are needed thanks
sunshine4u said:
hi i have just installed the ROM manager software from the market and after deleting this my hero flashing option screen not coming its shows like that i have attached the pictures please help me i have hard reset the phone its start working but the flashing options still gone & i m unable to install any other ROM ,suggestions from the Experts are needed thanks
Click to expand...
Click to collapse
Just try pushing recovery via adb .. if you know how to use it
Do you mean fastboot isnt working? (3 skating andoids) it wont boot? or recovery doesnt work?
in the clockwork rom manager it has an option for broken recovery...
other than that put the recovery.img on the sdcard (the root of it) then connect the phone and type adb shell flash_image /sdcard/recovery.img
i have tried it with ADB its gives message
usage : Flash_image partition file.img
but it doesn't boot in recovery mod what to do now ?
sunshine4u said:
i have tried it with ADB its gives message
usage : Flash_image partition file.img
but it doesn't boot in recovery mod what to do now ?
Click to expand...
Click to collapse
I know this mite seem a dumb question but you are holding " home " & " Power " right ?
Have to tested using flashrac and amon ra ?
Steven_belfast said:
I know this mite seem a dumb question but you are holding " home " & " Power " right ?
Have to tested using flashrac and amon ra ?
Click to expand...
Click to collapse
whats these thing i dnt knw about them please provide the link for that
Greetings sunshine4u,
There use to be a how to on the unlockr but its no longer there,
How ever here you go man,
Flashrac
http://zenthought.org/content/project/flashrec
Amon_ra
http://forum.xda-developers.com/showthread.php?t=561124
Code:
1. On your phone, goto Settings, Applications, and make sure Unknown source is checked ON.
2. On your phone, goto Settings, SD card and phone storage, and click Unmount SD card.
3. Then click Format SD card (it should automatically remount after this).
4. Plug the phone into the compuer via USB, then pull down the notification bar and click on the SD card notification. Then click mount.
5. Download this APK and recovery image and save it to your computer:
6. Save both the recovery-RA-heroc-v1.5.2 and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
7. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-hero-v1.7.0.1.img
Then click on the Flash Custom Recovery Image button (this button might say something else in different versions of Flashrec, but similar to this) and wait for it to finish.
12. Turn off the phone and turn it on into Recovery mode by holding down Home and Power to turn it on (keep holding until the recovery screen comes up has a bunch of text on a black background). So long as that screen comes up, you have done it correctly
Now this mite not work with your rom but it will not damage it in any way,
If point 10 fails then you will not be able to do it this way.
I know my self i had to downgrade my orange rom before doing it,
But before that point 10 just kept saying failed,
Downgrade and it worked a treat.
Hope that helps.
how to downgrade ???
Greetings,
I guess it did not work then,
As for the downgrade this depends on your provider,
I was able to get the orange rru thats a .exe and just run this,
But if you give have a look on the internet for your provider i am sure you will be able to find some thing,
If not get back to me with the name of your provider and the software you are on at this point and i will have a look for you.
my hero has no logo on it and its unlocked to all networks and i m using it in pakistan i m using warid as service provider and they dnt know anything about this issuee
i have Flashed the RA-hero-v1.7.01. now can any body tell me which backup is required to take nand or nand+ext what both of these doo and which 1 i should take before changing roms??
sunshine4u said:
i have Flashed the RA-hero-v1.7.01. now can any body tell me which backup is required to take nand or nand+ext what both of these doo and which 1 i should take before changing roms??
Click to expand...
Click to collapse
Just nand,
Any time i do a nand+ext it all ways fails when i restore.
Hey as least you are getting there now.
Steven_belfast said:
Just nand,
Any time i do a nand+ext it all ways fails when i restore.
Hey as least you are getting there now.
Click to expand...
Click to collapse
i never had problems while doing Nandroid + Ext Back up/restore ..
i have taken it with +EXT after partiton the SD card no error will come on Nandroid + Ext Back up
Steven_belfast said:
Greetings,
I guess it did not work then,
As for the downgrade this depends on your provider,
I was able to get the orange rru thats a .exe and just run this,
But if you give have a look on the internet for your provider i am sure you will be able to find some thing,
If not get back to me with the name of your provider and the software you are on at this point and i will have a look for you.
Click to expand...
Click to collapse
Hi i have the same problem as threadstarter. It did not work for me. May i know how do i downgrade my version?
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.
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
WARNING!
If you dont know the slightest bit of Windows or Linux shell and never did more than USE the device, be warned... If you kill it, its dead!
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Click to expand...
Click to collapse
I confirm it works perfectly. ICS TPT _A400_03_0070_0132_US :good:
God, this is so wonderful. CWM works, Koshu's CM10 JB Firmware, too. I LOVE THE DEVICE AGAIN!
Great news! Who might have thought that a working exploit is already out there?
This is wonderful news, a friend of mine recently lost root after he had to send his TPT in for repair and got a new board already updated to ICS.
FANTASTIC - worked on UK running OTA 3.5
Booyah! Thanks Emuandco for your diligence!
Thank you. Had lost hope of root for ICS. My TPT may finally be the tablet I paid for.
22 hours and 5 badly needed factory resets were worth it ^^
Thanks a lot :good: :good: :good:
I just rooted my ThinkPad (WE version). Works like a charm.
emuandco said:
Hey guys, I have good news for you all. I sat down these days and tried all kinds of exploits and one, normally for the Asus Transformer Prime really works!
Debugfs automated root from sparkym3 provided me full root access to my device. Its simple to use and does all stuff automatic
So it enables Users of the Lenovo ThinkPad Tablet to finally root their device, even if you had it updated to ICS. As you all know, this was not possible before, but after I ran through almost all exploits running anywhere for ICS, I found this one working like a charm.
Have fun!
Click to expand...
Click to collapse
wonderful!!!
Thanks a lot!!!
Just tried and it worked!!!
after some trouble installing the adb drivers it worked fine on my WE tablet..finally, awesome, thanks
Amazing how much of a difference having root on this tablet makes.:good:
Stylus and Pressure Sensitivity
Been waiting a long time for this. I had one question that I can't seem to find the answer to. I use my TPT for sketching, allot, it's why I bought the tablet. I was wondering, if I root and then upgrade to Jelly Bean, will I lose stylus and pressure sensitivity?
Can someone post the steps to get this working starting from a clean OTA 4.0.3 rom? I just started messing with the TPT. What boot options are there? I see the hold-down-rotate-and-power boot which looks like what is needed for nvflash, but I can't seem to get any other bootloaders booting here. The debugfs script seems to want to talk to a recovery boot, yes? How do I boot into recovery mode?
Sorry for the TPT newbie questions. Is there a wiki someplace with all the boot modes and other info?
First, load this one: LINK
Its the Driver needed for the TPT to communicate with the PC over ADB protocol.
Go to your TPT Settings below inside Developer Options and check USB Debugging. Attach to your PC and hand the new unknown Device in Device manager the loaded ADB Driver. Then download and unzip everything from the Exploit into a directory; then run RootDebugfs.bat from that directory. This should do it for the rooting of the Stock Firmware. You can verify it by getting "Root Checker" from Play Store. If its green, next load this one: LINK and this one LINK. Its the ClockWorkMod aka modded Recovery Mode making it possible to flash unsigned Updates and making nice Full Backups and the JB Firmware itself.
Install this way from a windows console bein inside the folder where the adb.exe from the exploit is, Step one is making a backup of your previous Recovery Mode for future reverting if you want to do so. Step two is the actual install. You need to copy the loaded recovery.img from the CWM thread to the SD in your TPT, same goes for the JB ZIP File and maybe the 3G Patch for the 3G Card you might have.
BE SURE ALL FILES ARE COPIED ON THE SD AND ITS INSIDE THE TPT AGAIN!
Code:
adb shell
su
dd if=/dev/block/mmcblk0p1 of=/mnt/external_sd/orig_recovery.img
mount -o rw,remount /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
dd if=/mnt/external_sd/recovery.img of=/dev/block/mmcblk0p1
exit
exit
This should be enough. Now reboot and while the Lenovo mini Logo shows up, push Vol UP rapidly. This should boot up CWM6, our modded recover Mode. Here Vol UP is upwards, Vol DOWN is downwards and ON/OFF is Enter. First thing, DO A FULL BACKUP TO EXTERNAL SD in "backup and restore", "backup" !!! Then let it do a "wipe data/factory reset", then select "install zip from sdcard" and in there "choose zip from external sdcard". Choose the CM10 JB ZIP first, then the 3G Patch for your Card.
Reboot and youre done.
i have updated to the latest ota and i am not rooted.. A400_03_0070_0132_US
when i run it and choose option 1 the window automatically closes after like 2 seconds
am i supposed to use the asus drivers or what? if anyone can please help...
Somebody buy that man a beer.!!!!!!
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
pwstein said:
Yankies77 - right click on RootDebugfs.bat and choose 'Run as Administrator'
You may get a different result.
Click to expand...
Click to collapse
I have already tried that doesn't work. when in cmd i write adb devices it shows the device is connected
i have put it to transfer files and MTP settings with unknown sources and debugging on ..when i run the .bat file
after the *demon started successfully* it suddenly closes after which nothing happens..what do you think is wrong?
Open a CMD prompt and run the bat file from there. then show us the output of the script please.
AAND be sure that theres not any adb.exe coming from the system path variable, like in system32 or syswow64. kill these
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!
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
For this problem i downloaded UL-K013-WW-12.10.1.36-user.zip file from asus site and i installed. But i get an error like "This package is for K013 devices..... bla bla" and i googled and i deleted 2 rows from updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
and new rom installed without any problem. But result was same, Asus logo and gray-or-black screen.
Anyway, i downloaded the older version UL-K013-WW-12.10.1.36_KK-user.zip and i installed
now i just see this message.
AFU: test IFWI BIOS update.
FV File Size is 0x00300260
I cant open recovery menu, I mean
VOLUME+ and Power => NotWorking
VOLUME- and POWER => Not Working
Just Volume(+) plus Volume(-) plus POWER is working, i mean fastboot menu.
Can i install my tablet from this menu? Or what can i do for my tablet? What is your advice guys?
Sorry for my english.
Thanks.
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
it's not related with this thread
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lambdadroid said:
I assume you were already on Lollipop before you started installing all these packages? Installing the _KK package was definitely a bad idea because it's only supposed to be used for upgrading from KitKat to Lollipop.
Luckily (at least as far as I know) the screen you are able to enter with Power + Volume Up + Volume Down ("DNX mode") can be used to recover most software problems. I haven't done this before, so hopefully someone else can share the necessary steps to restore your tablet.
Click to expand...
Click to collapse
Hi
thanks for your replay, i tried somethink with fastboot but i didnt success.
I hope somebody can help me.
Thanks again.
pojeck said:
it's not related with this thread but i just want to share this picture
My son is open this menu, how? i dont know
Click to expand...
Click to collapse
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
lambdadroid said:
Well, this menu will open if there is no bootloader on your tablet. The tablet has a UEFI implementation similar to regular PCs, and it's even possible to navigate and change options in this menu with a powered USB OTG adapter and an USB keyboard. Nevertheless, this wouldn't help in this case.
Just did a search in the forums and found a potential solution. You need fastboot installed on your PC (Google for instructions depending on your OS).
Extract esp.zip and droidboot.img from UL-K013-WW-12.10.1.36-user.zip
Extract efilinux.zip from esp.zip (in EFI/Intel/efilinux.zip)
Start DNX mode on your tablet (Power + Volume Up + Volume Down), you should see 3 "Fastboot starting" messages
Connect the tablet to your PC
Run these commands:
Code:
fastboot flash osloader efilinux.efi
fastboot boot droidboot.img
If it works you're in Droidboot again and can flash the original UL-K013-WW-12.10.1.36-user.zip from there.
Source: https://forum.xda-developers.com/showpost.php?p=64213291&postcount=163
Click to expand...
Click to collapse
hi again
as you told me i did and recovery menu is working now.
C:\Temp>cd asus
C:\Temp\asus>
C:\Temp\asus>fastboot flash osloader efilinux.efi
sending 'osloader' (2009 KB)
fname=efilinux.efi...
2009 KB / 2009 KB
OKAY [ 0.085s]
writing 'osloader'...
OKAY [ 0.006s]
finished. total time: 0.094s
C:\Temp\asus>fastboot boot droidboot.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
OKAY [ 0.001s]
finished. total time: 0.434s
C:\Temp\asus>
Click to expand...
Click to collapse
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
pojeck said:
hi again
as you told me i did and recovery menu is working now.
now what is the best way flash the original file UL-K013-WW-12.10.1.36-user.zip to the tablet?
because i tried with ASUS Flash Tool and it didnt success.
Thanks again.
Click to expand...
Click to collapse
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
lambdadroid said:
You can use the temporary TWRP recovery session from https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096 (select twrp_hdpi_portrait.zip and use trigger T4). First make sure you have UL-K013-WW-12.10.1.36-user.zip on the external SD card so you can install it from there.
Click to expand...
Click to collapse
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Hi All
i have a me176cx asus tablet and i rooted my tablet. After root process my tablet is worked for a while i mean 3-4 months and halted,
i saw the asus logo and gray-or-black screen.
Click to expand...
Click to collapse
Any idea?
pojeck said:
Thanks for your replay
i did it and i copied zip file to sd card.
I get same error, this package is for "K013" devices; This is a "K013_1" (you can find in attachment)
and i delete 2 rows in UL-K013-WW-12.10.1.36-user-orjinal.zip\META-INF\com\google\android\updater-script
getprop("ro.product.device") == "K013" || abort("This package is for "K013" devices; this is a "" + getprop("ro.product.device") + "".");
show_progress(0.750000, 0);
1- i get message INSTALL from SD card complete
2- i have lot of text on screen and rebooted.
3- I just have gray/black screen.
I turn around
Any idea?
Click to expand...
Click to collapse
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
I'm not sure why your device isn't booting anymore. Have you tried a factory reset (you can also do that from TWRP).
Hi
Alright, but are you able to get it the Droidboot (with the Normal Boot, Recovery mode etc options) screen again now with Volume Down + Power? That means you've at least fixed your bootloader.
Click to expand...
Click to collapse
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
pojeck said:
Hi
Yes, droidboot is working without any problem. But serial number is strange i think... You can find in attachment
Also recoverymenu is working. I'm getting error screen, after volumeup + Power i have no problem.
I selected
wipe data/factory reset
wipe cache partition
Result is same. After asus logo i have blank screen. This is my real problem.
Thank you so much.
Click to expand...
Click to collapse
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
lambdadroid said:
The serial number on Fastboot is normal, it never displays the right one.
I don't know why your device doesn't boot anymore (and it's hard to figure out). My only other suggestion is that you give my Nougat ROM a try (see https://forum.xda-developers.com/me...-unofficial-lineageos-14-1-asus-memo-t3633341). It's very different from the original ASUS system so there is a certain chance that it'll work. Note that battery life is a lot worse on it though.
You can unlock your bootloader from Droidboot (since you can't boot normally currently). Download https://www.androidfilehost.com/?fid=312978532265362065, and take the ESP.img from there, then download https://github.com/me176c-dev/devic...recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Boot into Droidboot and run the following commands:
Code:
fastboot flash ESP ESP.img
fastboot flash recovery twrp-recovery-3.1.1-20170810-UNOFFICIAL-me176c.img
Power off your device, then press Volume Down + Power. Intel logo should show up, and ask if you want to go into recovery or fastboot. Go into recovery using Volume Down. Do a Factory reset again (it's under Wipe), then flash https://github.com/me176c-dev/devic...ge-14.1-20170815-UNOFFICIAL-me176c-signed.zip (e.g. put it on your external SD). Test if it boots successfully.
Click to expand...
Click to collapse
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
pojeck said:
Hi Again
I did all steps. But i get an error, failed to mount "oemcfg" invalid argument (you can find in attachment)
Last 10 minutes i'm waiting in BlueLine
Is this normal?
EDIT : I'm still waiting here last 1 hour.
Am i need the shutdown?
Thanks for all
Click to expand...
Click to collapse
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
lambdadroid said:
Yes, I hope you've already turned it off. The first boot normally doesn't take longer than ~30 seconds. You will drain your battery if you keep it running for so long You can turn it off by pressing the power button for at least ~10 seconds.
The /oemcfg error could be a possible pointer what's wrong with your device. Try the following: Boot into TWRP again. First check if you have enough battery left. If not, you can try to charge it in TWRP. When you're done go to Advanced -> Terminal and first check if your serial number is okay:
Code:
getprop ro.serialno
... should display something like E5OKCY... (or maybe different, dunno what ASUS uses for each device).
Next we need to try to find out what's wrong with /oemcfg. Go to Mount and click "Config" a few times. I assume nothing happens (it doesn't get ticked). Go back to the Terminal and type:
Code:
dmesg > /external_sd/dmesg.txt
And upload dmesg.txt from your external SD here so I can check what's wrong.
Note: If you are experienced with ADB you can also use it to run commands instead of the builtin Terminal, but I guess the builtin Terminal might be easier to use.
Click to expand...
Click to collapse
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
pojeck said:
Hi
firstly Thank you very very very much for your interest
I did all, you can find thepictures and log file in attachment.
as you said me i click the config and nothing happened.
I found lots of "Can't find ext4 filesystem" error message. I think it's related with my problem
Click to expand...
Click to collapse
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
lambdadroid said:
Alright, indeed. The good news is that your serial number is fine and everything else in the log looks fine too. The bad news is that your /oemcfg partition was somehow destroyed, and it holds important data such as WiFi and Bluetooth mac addresses. The second good news is that most of the information is also stored in /factory additionally.
To save some time, it would be easiest if you send me a copy of your oemcfg and factory partition, then I'll try to restore the oemcfg partition based on the factory partition.
To get a copy of oemcfg and factory, type the following in the TWRP Terminal:
Code:
dd if=/dev/block/by-name/config of=/external_sd/oemcfg.img
dd if=/dev/block/by-name/factory of=/external_sd/factory.img
And upload oemcfg.img and factory.img (you may need to put them in a .zip first if XDA doesn't accept the upload).
Click to expand...
Click to collapse
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
pojeck said:
I get a copy of oemcfg and factory img files and zipped.
But size is 333KB
is this normal?
You can find the zipped file in attachment.
If you want to get original files i can send another link.
Thanks
Click to expand...
Click to collapse
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
lambdadroid said:
The size is fine (just compression, and it works well for this because there is not much data in the partition), but there is something else wrong with the files. I think you've send the same partition (the broken one) twice.
In your screen shot you have dd if=/dev/block/by-name/config twice, but for the second command you need dd if=/dev/block/by-name/factory. Please run the second command from my post above again, and then post the ZIP again
Click to expand...
Click to collapse
I'm so sorry about that
you can find the correct files in attachment
Thanks...
pojeck said:
I'm so sorry about that
you can find the correct files in attachment
Thanks...
Click to expand...
Click to collapse
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
lambdadroid said:
Alright, the new files look fine. I need a while to fix the configs, and I'll be away for an hour or so I'll send you a potentially fixed partition in a few hours.
You may want to edit your two previous posts and remove the attachments because the partition can potentially contain sensible data (the serial number of the device, mac addresses etc) that may be abused. I've downloaded them so you can safely remove them now.
Click to expand...
Click to collapse
Hi
Thank you very much for your kindly notice
I deleted last img files and some pictures.
I'll wait for fixed files, Thanks again.