Sad noob here.
Current Status:
Once rooted device (now recovery mode goes to TWRP)
No longer have su privaleges
No wifi (bad wpa_supplicant file)
SuperSU in a messed up state (says it is installed but only the .apk is visible in /system/app - nothing from the apps view on the tablet (i.e. the "gui")
Device Details:
Samsung Galaxy Tab 4 7"
SM-T230NU
Marvell PXA1088
Android Version 4.4.2
Build date August 2014
What I was trying to do:
Enable ad hoc networking capability
What I did:
Rooted Tablet via http://forum.xda-developers.com/showpost.php?p=55581754&postcount=4
This worked GREAT btw, thanks for those who worked on that solution
Follow steps to enable ad hoc capability via: http://androidtablethacks.com/android-tablet-hacks/how-to-enable-adhoc-wifi-on-android-tablets/
This didn't appear to work so I successfully tried the recovery steps
THEN I MESSED UP: I must have stomped on my original wpa_supplicant file at some point because after the initial successful recovery I have been unable to turn wifi on (nevermind ad hoc)
The way I see it, without both su permissions and wifi I'm dead in the water. I can't download SuperSU without wifi, when I download the SuperSU.apk to my PC and try to use ADB to install it it does not work because I do not have su permissions.
PLEASE tell me I am wrong and you have a solution you can share.
Thanks in advance for any help offered.
drrunnel
You might try to download the super zip "update" file with PC put it on the micro SD card . with the card in tablet use "my files" or you chosen file explorer and move the zip to internal memory and then boot to recovery and flash it.
<Resolved> Thanks
mrmazak said:
You might try to download the super zip "update" file with PC put it on the micro SD card . with the card in tablet use "my files" or you chosen file explorer and move the zip to internal memory and then boot to recovery and flash it.
Click to expand...
Click to collapse
I ended up downloading firmware from Sammobile and flashed it using Odin. Device is not the way I got it from the factory, but wifi works now. Much better situation than I was in earlier.
Thanks for your response mrmazak!
Caio!
Related
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Ph0tin0 said:
HI Guys,
Maybe somewhat can help me out here, in my attempt to update my Acer A500, I may have in a kind of way bricked my phone. I attempted to replace wpa_supplicant file as per some of the instructions, needless to say the update failed and me in my pure genius figure I would simply factory reset and reboot. Which I ended up doing, the problem now is that the WIFI does not turn on and my tab has been unrooted, I no longer have any file explorer app on the phone and I can't download anything. Does anybody know how I can gain access to the root files so that I may revert back the old file, or somehow install an apk file from the mini sdcard or even get access to the internet via bluetooth or USB. Anything would be helpful.
FYI - I am trying to gain access to my root files using Android SDK, but I've always had problems getting any of my pc to find any of the android stuff when plugged in.
Click to expand...
Click to collapse
I was in this court just yesterday, swearing up and down for some reason.
You'll need the root explorer apk, gingerbreak apk and the original wpa_supplicant file posted all over XDA.
Download and install Android SDK. It will also make you download the Java SDK too before you install the Android one. Start installing the Android SDK. It will seem like it's going to take forever, but you really only need what's in the folders 2 minutes in.
Go into the program files folder where the SDK stuff is and rip the 3 ADB files out and place them in their own folder. Mine were in: c:\program files\android\android-sdk\platform-tools\
I took the 3 files out and placed them in c:\and\
Place the apks in the c:\and\ folder
Make sure the driver files are installed from the Acer website.
Make sure USB bugging and apps from outside sources are enabled in settings on the tab.
Plug the tab into the PC via USB.
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
rorytmeadows said:
Open up the command prompt and go to the c:\and\ folder
then type
adb install c:\and\rootexplorer.apk
ENTER
then
adb install c:\and\gingerbreak-v1.20.apk
ENTER
The apps should be now installed on the tab.
Then just transfer the wpa_supplicant file over and you're right where you need to be.
Make sure you change the permissions on the wpa_supplicant file like you did the first time (enable everything read/write/etc etc) by holding on the wpa_supplicant file that you paste.
Click to expand...
Click to collapse
You are my new hero, all this time I've been trying to get Android ADK to recognize my tablet, but to no success. All I had to do was run ADB, which Ironically I had done, but only to see if it recognizes my unit. I was not aware I can install apps with it.
I'm not worthy... I'm not worthy
A million thank you's, now to try and get 3.1 installed and hopefully Googel/android was smart enough to put in a stock file explorer.
Not working wifi hardware
Somewhat similar to what happened to this guy. But to be specific, I am using an acer a500 originally on a rooted ics 4.0.3, i remember using lucky patcher and using the custom patch on adobe flash player then i saw an update regarding busybox and superSU...i was able to install the busybox updater but not the superSU since i remembered i already had superuser. I opened superuser and then it updated...from then on...I lost my wifi...at start it was still there but it can't connect. also, i lost my root because i no longer am able to use titanium backup. double checking it, i downloaded a root checker and it displayed not properly rooted. seeing this, i thought it's been a long time since i've updated my rom so i might as well upgrade everything...my bootloader, kernel, rom. So i first degraded it by flashing to the full package stock HC 3.1 ROM (it had an old HC 3.1 bootloader). Then i noticed i can no longer turn on my wifi and use my old apps...I flashed it back to a NON-rooted stock ics 4.0.3 thinking it might fix it...but it did not. HELP please...
Hey everyone - I figured this might help some folks. It is a CWM installable zip that will restore your system to a completely stock UEKHA (the US retail build for P7310). This includes the stock kernel and recovery image as well.
Heres the instructions:
1) Download this file: http://www.multiupload.com/1KRF1M4CQZ
2) Put the file on your internal storage.
3) Reboot into recovery
4) Execute the Wipe Data/Factory Reset option
5) Choose Install Zip from SD Card
6) Choose Choose Zip from SD Card
7) Select the P7310UEKHA_Restock_v1.zip
8) Sit back, wait about 5 minutes
9) Once the script completes and says "Done", reboot.
10) Welcome to a completely stock US Retail tab
Enjoy.
I just want to ask: Can we flash this on other 8.9s from other regions (namely, an Asian model)?
I'm used to how it is in Maemo where the only differences between firmwares is localization and some preinstalled programs.
Yes you could flash it onto another 8.9 as well, although it should be a P7310 (Wifi only). Just like Maemo, the only differences between regions are localizations and pre-installed apps.
This stock image would not support 3G functionality however, so it would be a bad idea to install it on a P7300.
That's great. Going to flash Clockwork and this once I pick up my P7310 on Tuesday.
Which reminds me - how are Samsung kernels built? I heard that they need to use an initrd (or can the modules be compiled straight into the kernel? or is there a kernel size limitation, which is why an initrd is needed?)
I am truly grateful for this as I rooted and debloated my Tab the very first day lol. This is a great step!
Just flashed my tab with the ROM, works great! Originally had asian ROM on the tab.
Thank you very much! I needed some of the stock original loadable modules after some prior tweaks .
Thanks for the good work!
I was checking the system script used, and I was wondering if this CWM preserve the file/folder permissions as out of the box state or is just 7777 state?
mramirezusa said:
Thanks for the good work!
I was checking the system script used, and I was wondering if this CWM preserve the file/folder permissions as out of the box state or is just 7777 state?
Click to expand...
Click to collapse
Permissions should be out of the box state...the system image was taken from my stock tab directly, and the extract script should leave all permissions in tact.
Hey alterbridge86, it's great to hear you have a GT 8.9 now, that's good news for us
Quick question, how did you dump the ROM and the recovery? I have a GT 8.9 3G from Orange France and I'd like to dump everything before installing CWM to be able to restore to stock if needed.
Thanks! And again, great work!
masterludo said:
Hey alterbridge86, it's great to hear you have a GT 8.9 now, that's good news for us
Quick question, how did you dump the ROM and the recovery? I have a GT 8.9 3G from Orange France and I'd like to dump everything before installing CWM to be able to restore to stock if needed.
Thanks! And again, great work!
Click to expand...
Click to collapse
I ended up dumping it using the CWM I posted in the other thread. The new clockworkmod stores its backups in .tar format, so it makes it really easy to manipulate. Simply create a backup, then if you're feeling adventurous, you can take this flashable zip, replace system.tar and boot.img with the ones created by your backup. The stock recovery is same on all devices, so you can leave the one that is in this package and itwill work for you
Sounds good, thanks I'll give it a try when I have a little more time to play
Hey guys, i did something really stupid today to my 8.9 p7310...I installed that Asia update to it and it placed the tab into a loop and crashes in the settings app when it first starts up. Cant access SD card to install this firmware. I need the Odin firmware to put back to stock I think. Any ideas?
shatty said:
Hey guys, i did something really stupid today to my 8.9 p7310...I installed that Asia update to it and it placed the tab into a loop and crashes in the settings app when it first starts up. Cant access SD card to install this firmware. I need the Odin firmware to put back to stock I think. Any ideas?
Click to expand...
Click to collapse
When you installed the Asian firmware at ODIN, did you remember putting the CSC, PIT, BOOTLOADER to their corresponding places along with the biggest file being at PDA? If you just used the PDA file and not the other files...there's your issue. Once you successfully ODIN, flash this specific CWM Recovery and then you can either choose Stock (this thread) or the Overcome ROM.
Yea just did the pda. The instructions only said the pda. Doesnt matter anyway i am back to stock used adb to load the stock zip to sdcard and loaded
shatty said:
Yea just did the pda. The instructions only said the pda. Doesnt matter anyway i am back to stock used adb to load the stock zip to sdcard and loaded
Click to expand...
Click to collapse
Good to know you made it. The same happened to another user. Those instructions aren't correct.
Sent from my GT-P7310
Help getting China based GT-7310 to US stock
Hello,
I recently bought a GT-7310 in China, and want to get this to stock US using your method. I had a question on step #2.
2) Put the file on your internal storage.
How do I get the file to the internal storage and where is that location? I don't see an /SDCARD folder anywhere when browsing the tab in Windows 7. I have the latest USB drivers installed. I tried to push the file to /SDCARD using ADB but Android SDK tools doesn't recognize my tab. Are there any other ways to get the file to internal storage?
Thanks.
zinzino said:
Hello,
I recently bought a GT-7310 in China, and want to get this to stock US using your method. I had a question on step #2.
2) Put the file on your internal storage.
How do I get the file to the internal storage and where is that location? I don't see an /SDCARD folder anywhere when browsing the tab in Windows 7. I have the latest USB drivers installed. I tried to push the file to /SDCARD using ADB but Android SDK tools doesn't recognize my tab. Are there any other ways to get the file to internal storage?
Thanks.
Click to expand...
Click to collapse
When you plug in the tab, it connects via MTP to Windows. Then you can only get to the internal storage, just drop it in there. You'll see all the default folders (music, videos, etc.) so you'll know your in the right place.
Thank you. I got the file to SD Card, went into recovery, executed the wipe data/factory reset option. After the wipe data/factory reset is complete, I selected the option "apply update from /sdcard". I selected that and I get the following error:
E:error opening /data/media: No such file or directory
Any ideas?
Thanks.
You need to use CWM recovery, not the stock recovery.
Hello everyone here at xda-developers.
A few days ago I was watching streams on my Asus Transformer TF101(B70). Suddenly out of nowhere the tablet shuts off and starts an infinite loop which I simply cannot get it out of. I end up restoring the tablet to factory default and load a stock kernel onto my tablet using adb push. Since the tablet doesn't have any rom installed at this point I try to push CyanogenMod 9.0 onto my tablet in order to try and get my tablet to work and this is where the issues begin. First of all I try to push the rom onto /sdcard but that bugs my CWM 5.5.0.4 and will not allow me to access /sdcard and keeps telling me that there are "No files" when I'm trying to access /sdcard. If I restart into recovery it can access my files again but the pushed file is not there.
Afterwards I try again to push the file to /sdcard/download but then it tells me that this archive is Read-Only. I run a the "adb remount" command and it tells me it completed succesfully but when I push again it tells me that the archive is still Read-Only.
I've tried various commands but I can simply not change the archive into read/write. A few times I have succeeded in pushing the rom to /sdcard/download but when I try to locate the file it is simply not there and is not located anywhere on /sdcard despite the process being completed. I have simply no idea on how to get the rom file onto my tablet in order to restore it to normal and I was wondering if any of you have any ideas on how to get my tablet working again?
If you have any questions regarding information needed about just ask and I will provide the necessary information. I am really out of ideas on what to do.
Get a Micro SDCard and copy the ROM onto that from a PC, then put that in the TF and boot to recovery
*Detection* said:
Get a Micro SDCard and copy the ROM onto that from a PC, then put that in the TF and boot to recovery
Click to expand...
Click to collapse
I already have a MicroSD card in my tablet but I am not able to access it from CWM recovery
Try pushing the file to data/media.
Are you pushing the file while in cwm recovery?
baseballfanz said:
Try pushing the file to data/media.
Are you pushing the file while in cwm recovery?
Click to expand...
Click to collapse
I am pushing files while in recovery mode. I have already tried pushing to.other directories than /media/download but the same thing.happen. either it tells Me that the file system is read only or it says that the file transfer succeeded but the file cannot be located anywhere. I read up on the solution of trying to access a rom through microssd. Unfortunately my recovery doesn't support that unless I can change it to use external.memory instead of internal memory.
The only thing I succeeded in was getting a rom pushed to /system. Would I be able to access this directory from my recovery?
baseballfanz said:
Try pushing the file to data/media.
Are you pushing the file while in cwm recovery?
Click to expand...
Click to collapse
I am pushing files while in recovery mode. I have already tried pushing to other directories than /sdcard/download but the same thing happen. either it tells Me that the file system is read only or it says that the file transfer succeeded but the file cannot be located anywhere on /sdcard. I read up on the solution of trying to access a rom through microsd. Unfortunately my recovery doesn't support that unless I can change it to use external memory instead of internal memory but I do not know it that is possible.
The only thing I succeeded in was getting a rom pushed to /system. Would I be able to access this directory from my recovery?
WebberX said:
possible.
The only thing I succeeded in was getting a rom pushed to /system. Would I be able to access this directory from my recovery?
Click to expand...
Click to collapse
It would be better to try than to ask !
How did you get on, any luck yet ?
You could try flashing a new CWM that supports SDCards via NVFLASH
WebberX said:
If you have any questions regarding information needed about just ask and I will provide the necessary information. I am really out of ideas on what to do.
Click to expand...
Click to collapse
If you did a factory reset (and hence data loss is not a problem), your best option is using nvflash/wheelie to restore the device to a clean state with a stock firmware build and then reflash CWM to install whatever custom ROM you want.
Hi Guys
I'm so lost and I've been trying to figure this out for 2 days now on my own.
I've rooted my S4 i9505 and installed ClockWorkMod on it but I don't have an SD card and am trying to install a ROM from the internal memory. My question is now how do I put the ROM at "root access level" on my phone? I have a Mac and a PC so instructions for either would be appreciated. When I attach the device via USB, it connects as a media device in Windows but what folder do I put the rom into?
Any help hugely appreciated
I had this problem as well. I ended up just sending the via sideload. Download the Google SDK and install the software toolkit.Place your .zip file in the same place as the adb.exe. Navigate to that folder in command prompt and run these command after selecting sideload in CWM.
ADB USB
ADB SIDELOAD NAMEOFROM.ZIP
Sent from my GT-I9505G using Tapatalk 4 Beta
Thanks for the reply.
I managed to sort out the issues.
What I did was install this:
1) CWM Advanced PhilZ Touch - this gave more options and made everything easier
2) I then downloaded the ZIP Rom I wanted and created a new folder on the phone using "Android File Transfer"
3) I then booted the phone into recovery mode and installed the rom via the "internal SD card" option and selected the zip and it was done in about 2 minutes!
Easy peasy when you know how but took me ages to figure it out!
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Matra-PB said:
Hi,
have you read the tips? It says:
"- Google play will not work right if you do not format your data partition to f2fs. (You can do this in recovery)"
Have you tried it?
Click to expand...
Click to collapse
That may not be the problem I've hear a lot of people are having this problem. But it's a good place to start if he hasn't tried it yet.
Success story upgrading A500 in 2019 July
finneus_ said:
Hey together,
I really hope someone out there is still using a A500 Tablet and may be able to help me fix a weird issue i encounter on every ROM i tried so far.
I installed the ROMs mentioned in this Thread: https://forum.xda-developers.com/iconia-a500/general/2018-a500-upgrade-threaddownloads-to-t3832293
And all of them come with the Same Problem for me.
If i try to open the Google PlayStore or something else that wants me to login into a Google Account it just says: "There was a problem communicating with Google Servers" "Try again later"
anyone knows of this issue ? All the fixes several Google searches gave me did not help to fix that issue for me on any of the ROMs.
help would be highly appreciated
kind regards
Finn
Click to expand...
Click to collapse
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
Step1a: Install a File Manager app from the Google playstore. This will help you extract the CPU ID and convert it with the SBK tool to get the SBK number/string. important steps SBK tool was available in file - SBCalc_v1.1.ZIP available in this forum.
STEP 2b: SUPERUSER and SUPERSU installation
1. Install SuperUser.apk first.. (IMP - Its available in this forum. Its like a base version for superSU to install over. If you do not install SuperUser.apk, then each time you try installing SuperSU, you would get an error message about a SU file being incompatible.)
2. Then install an older version of SuperSU downloaded from the website - filename -> eu.chainfire.supersu_v2.65-265.ZIP . Newer versions will not work. U got to install an older version as new version seems to be a paid SW.
3. Next Open SuperSU app on your tablet and let it update itself a couple of times each time opening and closing the app after the upgrade.
4. Remove SuperUser.apk file as now its no longer needed.
5. Now that you have ROOT access and SuperUSer access
6. Install Titanium Backup. File name in this forum- update-recovery-TWRP-rev2.0-beta4.ZIP . This will help you to flash/upgrade ROM software on your tablet.
Twrp 2.8:
http://www.mediafire.com/file/e7wpny5f39vw3pc/update-recovery-TWRP-rev2.0-beta4.zip/file
Compressed Archive (.ZIP)
File size: 4.91MB
Uploaded: 2018-08-14 21:40:26
https://www.mediafire.com/download/e7wpny5f39vw3pc
STEP 3: Install an Unlocked Bootloader i.e. unlocked bootloader Skrillax v9 - file name in this forum BabSector.rar or A500-Bootloader-Nvflash.ZIP
Once you have reached this step, you now have the basic tools needed for the final ROM upgrade of the tablet.
I did get error message after the reboots that happened after Unlocking the Bootloader. Someting about a LNX partition not being okay or some such msg. Each time I just WIPED the Cache and selected similar options to wipe System, Data, User, Dhelvic cache (spelling incorrect) etc. Since you have not installed the final OS or ROM for your tablet yet, no harm in deleting these partition data. Actually its recommended to wipe, format in f2f formats etc. all of which is possible using the TWRP Recovery software you installed in step 2. Choose Recovery menu option each time the tablet boots or gives errors.... using the volume rocket and power buttons. More info -> Go through this thread and install unlocked bootloader.
https://forum.xda-developers.com/showthread.php?t=1622425
Flashing Bootloader Steps
-------------------------
1. generate your SBK from cpuid
2. put tab in APX by holding reset (small pinhole bottom right side)
and pushing power for 3-4 sec. - then release reset approx 1 sec. later
the screen should be blank and power button should be lit - plug in USB to PC.
2. Run A501 A.bat - when finished reboot tab to recovery (win 7 and under
right click on A501 A.bat and select Run as Administrator)
3. run Recovery(power and volume-) ->WIPE -> "Advanced wipe ->System (only)and swipe to wipe.
4. unplug USB and reboot tab to APX
5. plug in USB afer it is in APX mode -> Run A501 B.bat (win 7 and under
right click on A501 B.bat and select Run as Administrator)
Bootloader unlock tutorial
--------------------------
Step 1: Get your cpuid - https://forum.xda-developers.com/showthread.php?t=1624645
Step 2: Convert it into an SBK - https://forum.xda-developers.com/showthread.php?t=1810618
Step 3: Download the A500 drivers
- http://www.mediafire.com/file/pde8rojv1t8gnif/USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501.zip/file
Step 4: Download the files to install the bootloader
- http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
Step 5: Follow the instructions in "how to.txt"
Step 6: Download a rom and flash in twrp
This tutorial is based of
https://forum.xda-developers.com/showthread.php?t=2450119 thread so big thanks to KaijiKun .
Bootloader unlock files:
http://www.mediafire.com/file/o7m2ouwo6zuod4d/A500-Bootloader-Nvflash.zip/file
STEP 4. Downloaded file omni-4.4.4-20150210-a500-IconiaHD.ZIP as I was not sure version omni 5.1.1 was as stable as Omni4.4.4 reading all the threads in this forum.
First rename the downloaded OMNIROM file as update.zip .
OmniRom 4.4.4
http://www.mediafire.com/file/ghd72j3g618kk9g/OMNIROM-5.1.1-Tegraowners_ROM_v13t2.zip/file
File size: 244.66MB
Uploaded: 2015-04-05 17:40:14
STEP 5: Install another tool adb_fast.ZIP. This tool is also available in this forum.
Note:You need to copy the update.zip file to your computers folder where this tool adb_fast is installed. In mine it was C:\Program files (x86)\Minimal ADB and Fastboot folder. This adb_fast file creates an application shortcut on your computer desktop. Clicking on the short cut launches adb and fast boot programs I mentioned at the beginning.
STEP 6: Copy the file to the SD card (16GB) of your tablet.
Run the adb_fast tool from your desktop shortcut. This will open a Command Prompt type black screen window where you can enter the code as given below. Note you may need to see how your SD card is listed in a file manager in your computer
Code:
adb push update.zip /mnt/sdcard/update.zip --- NOTE: this creates mnt folder on internal storage and I had to then move the file using TWRP recovery tool installed in step 2, to the SD card.
adb push < ------- is the push command.
rom.zip < ------- is the name of the Rom zip file.
/sdcard < ------- is the location your pushing the Rom to.
E.) Reboot tablet with Power+Down Arrow i.e. This will start the Upgrade process for the tablet to OMNIROM 4.4.4
-- Power Button + UP VOLUME pressed... then release Power button after LED lights.
-- System will boot to commmand prompt
STEP 7: Install GAPPS using pico gapps short version and Wipe Data/Factory reset ----------------?>and wipe cache partition?
Reboot after 1st reboot
G.) https://opengapps.org/ to install a minimal version of Google Apps on the tablet.
File name -> pa_gapps-modular-mini-4.4.4-20150410-signed.ZIP
Root tablet again and install SuperSU if you need it
other info.
You can use TWRP to flash the OmniROM on the tablet or you can use the following in worst case senario to do the same.
Code:
fastboot devices
fastboot flash update.zip -- check if syntax is ok from threads in this forum
fastboot reboot-bootloader
copied below from other threads ---->
I find that a large amount of complaints in developer threads are due to people not properly wiping before a flash.
Of course there is times when a 'dirty' flash is fine, but if you're ever not sure, wipe as cleanly as possible.
fastboot allows for about the cleanest of wipes by the way. And each partition can be done separately too.
Code:
fastboot erase system
fastboot erase data
fastboot erase cache
can all be done individually, but to do these all in one command
Code:
fastboot erase system -w
If possible I recommend to do these steps before flashing a ROM, and now that you know you can do this all within fastboot mode i suggest to try it out, its quick and painless!
Don't forget to wipe your kernel too! (fastboot erase boot)
~Important~ If your device uses an emulated SD card (as in no removable micro SD but an SD partition on phone)
Then be careful wiping data/userdata as this will erase all contents of internal SD - you are forewarned!
ADB= Android Debugging Bridge (ADB)
[TOOL]Minimal ADB and Fastboot [2-9-18]
https://forum.xda-developers.com/showthread.php?t=2317790&page=12
First a short explanation:
Fastboot, like ADB, is a tool to communicate from PC to Android phone. There are times when it is a must to use, and times when it is just helpful.
ADB is used within your recovery or within your OS, but when you are in bootloader mode and need to communicate with your phone then you need fastboot.
And you may ask why would i ever need this?
Well many reasons. Main one is knowledge, learning the ins and outs of fastboot, like learning ADB, can get you out of many jams.
And if you want to unlock your bootloader this is done through fastboot. Granted HTC's unlock is... well crap, but for a Nexus this is how its done.
One other reason I have to stress is learning for safety reasons, This is about the safest way possible to flash firmware to your phone (ie Radio, Hboot, Recovery)
Lastly you may want to know the limitations,
There are many of course, this isnt JTAG, it will not resurrect a hard brick, but it often save peoples phones from 'soft bricks' and lots of time when know how and when to use it.
Think of fastboot as the program that takes over when ADB cant be used, it works with firmware more than software.
https://forum.xda-developers.com/showthread.php?t=1624645&page=3
GUIDES
---------------
Civs Guide to flashing the bootloader http://forum.xda-developers.com/showthread.php?t=1622425
Walkthrough using APXFLASH tool at Step 6 http://forum.xda-developers.com/showthread.php?t=1624645&page=2
From Civato's OP of The Guide: nvFlashToolPackages
Skrilax_CZ bootloader thread http://forum.xda-developers.com/showthread.php?t=1619913 and should be "required reading" for anyone mucking about in their tabs internals!!!!
Rollback to HC
jazzyjames guide http://forum.xda-developers.com/showthread.php?t=1516012
Iconia Root http://forum.xda-developers.com/showthread.php?t=1138228 /gingerbreak: For returning to Honeycomb
----------------
To get my CPUID, I have followed the steps below:
Open yr file explorer, esfile explorer is a great one....navigate to:
/sys/firmware/fuse/acer_cpuid - add a zero to the front!
To get CPUID get a Root browser of some sort and go to sys/firmware/fuse/acer_cpu_id
convert my CPUID into SBK?
--------------------------
https://forum.xda-developers.com/showthread.php?t=1055354&page=6
What Does Root Give Me?
1. Full control over your system
2. Ability to alter system files. You can replace many parts of the "Android Core" with this including:
o Themes
o Core apps (maps, calendar, clock etc)
o Recovery image
o Bootloader
o Toolbox (linux binary that lets you execute simple linux commands like "ls") can be replaced with Busybox (slightly better option)
o Boot images
o Add linux binaries
3. Run special apps that need more control over the system
o SuperUser (lets you approve or deny the use of root access to any program)
o Task Manager For Root (Lets you kill apps that you otherwise could not kill)
Tether apps (like the one found at [android-wifi-tether.googlecode.com])
4. Backup your system
o You can make a folder on your SDCARD and backup all of your .APK files to your SDCARD (helps if an author decides to "upgrade" you to a version that requires you to pay to use the version you just had)
5. Relocate your (browser/maps/market) cache to your /sdcard
6. Relocate your installed applications to your /sdcard
7. Reboot your phone from the terminal app easily (su <enter> reboot <enter>)
Turn the rotation lock off.
-------------------------------------------------------
SUMMARY - Regardless of version, rooting is the same... next
** Unlock the bootloader.
** Fastboot flash a Custom Recovery (TWRP).
** Download to the Tablet, Chainfire's SuperSU root updater .zip
** Boot into the previously fastboot flashed Custom Recovery, and flash the SuperSU updater .zip.
** Reboot - you're rooted.
-------------------------------------------------------
PS. I tried to maintain a log in Notepad during my upgrade. Unfortunately did not write detailed instructions and link to required files. Above is a summary of what worked for me.
Can not root
sukasis said:
First my thanks to the forum key members for providing answers to queries and to all the key contributors of SW/ROMS in this forum. I followed the procedures from this forum to Flash / upgrade my Acer Iconia A500 on 4.0.3 ICS that was sitting in a trunk for the last few years. Summary of steps I tried out.
STEP 1: Install the Acer device drivers listed in the links in this forum on your Laptop/Computer even if by default your Windows 10 OS (assuming you are on Win10 like me) is able to recognize the A500 connected to the USB port.
USB_Acer_1.00.0524_A30HA31HA32H_A.ZIP
STEP 2: ROOTING the Acer A500.
1. The tablet should be already upgraded to stock ICS for A50x (or stock ICS A10x/A510 for other tablets).
2. On a tablet: "Settings" -> "Applications" -> "Development" -> "USB debugging" switch ON. If you do not see this menu, then click 7 times of the Android Build No. listed under settings and come back to the menu above to enable USB Debugging.
3. Connect the tablet to the computer (Before connection it is recommended to update the driver for a tablet from here: A10x, A50x, A510).
4. Since most of the discussions regarding flashing A500 were from 2011, the earlier Gingerbreak method for rooting did not work.
I downloaded the following file from this forum to root my tablet.
ICS_rooting_A10x_A5xx.zip
5. Open the directory with the unpacked archive. Execute file: for windows - runit-win.bat; for Linux - runit-linux.sh.
The root is received!
Note: The McAfee Antivirus software started tagging a file 'mempodroid' within this ZIP file Tools folder as a virus or malicious file. This rooting method uses the 'mempodroid' exploit which is detected as a VIRUS by McAfee and Qurantined. So restore from Qurantine and check list of files are still present in the folder. If not verify 8+8 files in folders again.
As per inputs in this forum, I restored the files quarantined and then suppressed McAfee SW for the duration of my upgrade activities on my laptop and was able to successfully extract all the files in the ZIP file to a local folder on the laptop. This ZIP file has adb and fastboot - two key programs useful for rooting your A500 apart from SU or superuser base file used in step 2. The file to run is the BAT file runit-win.bat if you are on windows. At the end of this step your tablet should be rooted. You may check by installing the RootCheck app from Google Playstore.
......
Click to expand...
Click to collapse
Hi sukasis, i was unable to root the tablet. I download all and run the runit.win.bat (trying normal, as admin, and open a cmd as admin and then navigate to the bat to execute).
- It say device connected
- Then push 7 files correctly
- Executing of the main script. (it freeze here a lot of time)
Then error: protocol fault (no status)
The file "su" isn't created
Not getting root!
I try in USB 3.0 and 2.0 same error.
I have windows 10.
I uncheck the Debugging mode and it's bring another error, so i believe the connection is good because in debug mode can push files.
I don't know whate else i can do.