Phone Was working fine on latest PA rom until battery died. Upon charging and rebooting up, the Rom some how got corrupted i guess, because it now just boots logo forever. I don't have any roms on the device itself so can't reinstall anything through recovery to try to fix whatever may have got corrupted. I know there is a way to Side Load with TWRP, but am running into difficulties. I do have the drivers for the nexus installed. I can't directly drop files through windows because it doesn't read in recovery and read up upon researching the Side load function. So I downloaded the ABT bundle zip folder and placed it in C folder, but that's where i'm stuck. I've tried looking a few things up but every time i try to run Adb command in the platforms folder it just opens and closes within a second. not sure what i'm missing. i've tried looking at other ways but most other phones have the capability of just throwing it on to the SD card which helps other people. thanks in advance.
Tl:dr Need to get a rom file onto the Nexus, to install and repair my corrupted rom.
you run adb from COMMANDLINE, it sounds like you are trying to double click the adb.exe....that will never work. adb is a commandline tool
ok, i'm pretty much a noob, don't know how to do that but i'll google it first before i bug any more. thanks again.
Since you are using windows, while looking at the explorer window that contains the adb/fastboot exes, hold down shift and right click somewhere in the blank space within the folder...OPEN COMMAND WINDOW HERE
once you have a DOS prompt open in that location, type 'adb devices' without any quotes to see if your device is being recognized.
there is an entire thread dedicated to walking you through this whole process.
start reading here:
http://forum.xda-developers.com/showthread.php?t=1812959
this site contains all the info you need.
I googled it and got it set up and working. it does recognize my device. now i'm reading up on the command to send the zip file. seriously, thanks for the feedback. been sitting here for like 2 hours trying to figure this out without pulling out my hair and tossing the phone lol.
You could have just read the stickies... Why people don't get curious about things like "RETURN TO STOCK ON ANY GALAXY NEXUS VARIANT" or "ANDROID 101", I'll never understand.
a manta wrote this.
Related
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
pbrady5 said:
Hello everyone!
I've been coming to this site for a few weeks now. What a ton of helpful information! I finally decided to create an account though, because I had a question I couldn't seem to get answered.
I'm fairly new to android, this a100 tablet is my first device I've "owned" but have worked with and have a little experience with other android devices. I'm pretty good with Linux, being an IT admin. I'm sure my issue is minute, I'm just stumped as to what is causing the problem.
I've upgraded my a100 to the latest ICS build. I've installed the drivers from acer (unfortunately after windows detected the device drivers first) and I am trying the quickroot method I found in the development forum. I can run the windows .bat file, and everything goes through CMD so quickly that I am not able to read whats happening, but it reboots my device and says root achieved. I've got super user installed, it won't find any updates for the SU in the settings menu, says failed every time it looks for them. I open terminal emulators, still getting $ instead of #. Tried a terminal command I read about for root, where I put the root and SU files at mnt/sdcard and use the command to install, no luck.
Am I truly rooted? I cant tell anymore. I just want to unlock the bootloader, install cwm, and flash an a500 custom rom to it.
Any help at all is greatly appreciated. I'm sure I'm overlooking something, but Im not sure. I can add a legacy device, add Acer's ADB driver, but the fastboot one gets a code 10 and cannot start.
Thanks!
Click to expand...
Click to collapse
You do have Superuser and it's su binary, so yes, you should be rooted. Try this app if you want to be sure: https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en.
Besides the root checker that theonew pointed you too I have always found downloading and installing Titanium Backup from the market as a surefire way of determining if root was successful.
Upon first run it will ask for SU permissions and should present you with a dialog box asking if that is ok with you. I always answer yes and make sure that the "remember this selection" box is checked.
That will be the first sign that you are rooted. Then, The program should provide you with a summary where you will see a bunch of green check marks. Most notably Busy Box should have a green checkmark and it will probably state Installed from program or something to that effect.
Wahla, you have confirmed you are rooted.
BTW, I recommend this program for it's ability to backup your apps which makes flashing new rom's easier as the apps can then be restored after performing a data wipe which is usually a requirement of flashing new Roms. Just be sure you understand that sometimes restoring app's AND their associated DATA can mess with a new ROM. In that case you can simply install the APP only. which still saves you the time and bandwidth of re-downlaoding it from the market.
Good luck and welcome to the playground.
I unlocked my bootloader and flashed a Bigxie Jellybean rom this morning for the first time.
Everything was going great until I tried to reboot for the 4th time and now there is no boot animation.
I tried doing a factory reset in CWM as well as wiping the cache but it didn't help.
I also don't have the Jellybean zip file any more.
What do I do now?
Is there a way to push the zip file to my phone and try again?
Use search, there's a lot of threads about this; next time read before you do stuff, hope this serves as a lesson.
Sent from my i9250
Read? All I've done for the last 2 days is read. And when I finally tried it everything worked well.
Anyway, I managed to fix it. Pushed over the update file with Wugfresh Toolkit and flashed it again.
Eliott said:
Read? All I've done for the last 2 days is read. And when I finally tried it everything worked well.
Anyway, I managed to fix it. Pushed over the update file with Wugfresh Toolkit and flashed it again.
Click to expand...
Click to collapse
Glad you solved it.
You asked a good question "Is there a way to push the zip file to my phone and try again?", awnsered and asked by people like probably dozens of times now. How can you miss it? Simple, you didn't search well.
This was the first result, on regional google, for the search tag "xdadev push zip". Sure, we could have used other tags like "android push zip", but it's for a subforum on Archos Gen8, Gen9; it tells you how to push a script, which is a file, then the command gotta be the same. Oh, what's this, ADB!?
Once again, regional google search first hit was this when searching for tag "adb". Reading the linked webpage, you see a bit down further
Copying Files to or from an Emulator/Device Instance
You can use the adb commands pull and push to copy files to and from an emulator/device instance's data file. Unlike the install command, which only copies an .apk file to a specific location, the pull and push commands let you copy arbitrary directories and files to any location in an emulator/device instance.
To copy a file or directory (recursively) from the emulator or device, use
adb pull <remote> <local>
To copy a file or directory (recursively) to the emulator or device, use
adb push <local> <remote>
Click to expand...
Click to collapse
Great. We know what is adb, and what can we use it for. So, this topic was about bootanimation disapearing. You solved it by pushing a rom zip and reflashing. You could have just searched for "xdadev android bootanimation galaxy nexus" and you would have found this, the third result on google.
This would tell you where bootanimation file is located at, so you'd have known how to push it, where to push it.
You see, you didn't search well. You spent 2 days searching, I spent 10 minutes, like I didn't know a thing about android.
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
EDIT: The guide that was followed to root: http://forum.xda-developers.com/showthread.php?t=1531646&highlight=root
phracture said:
So I've tried searching on here, I've tried googling to no success...So time for my first post on this site I guess.
I have an Acer Iconia Tab A100 running stock ICS (rooted) which now stops during its boot sequence.
I've read that when a device is bricked it stops at the Acer logo on boot, mine goes past this but stops before the Android logo appears.
Stuff I did before this happened:
- Friend rooted my device for me using a guide from these forums.
- I tried seeing what I can do with Superuser permissions and got used to the new features.
- Wanted an app that wasn't compatible with my device so I tried using a Device Spoofer to make my device appear as an HTC Thunderbolt.
- Realized it didn't work still so I used the device spoofer to restore back to my default device.
- Device rebooted and I am now stuck between the Acer logo and the Android logo on boot.
Am I bricked and screwed out of a device?
Is there a way to recover my device/restore to factory?
Any help is appreciated. You all most likely know more that I do.
Click to expand...
Click to collapse
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
justjackyl said:
Is cwm or twrp recovery installed?
Sent via G2x on temasek b135.2 w/ Trinity TD1.58 kernel (testing)
Click to expand...
Click to collapse
I don't believe either was installed. Is there anyway to fix this problem without those?
phracture said:
I don't believe either was installed. Is there anyway to fix this problem without those?
Click to expand...
Click to collapse
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Ahhh okay I think that makes sense to me, and yes I believe I had debugging turned on so I should be able to fix this I guess fairly simply.
Thanks so much will post to say if I've solved or ran into trouble once i get home.
pio_masaki said:
Well for starters what happened was that tool wrecked build.prop which sits in /system. Not a bug issue except it won't be fixed by resetting, you need to replace/repair build.prop or flash a whole new system to it. Did you enable debugging before doing this? If so adb might be used to repair the damage. If not you'll need to flash an official acer ICS ROM by placing it on the root of external SD named update.zip then power on holding the volume key closest to the lock switch.
Tapatalked from my Nexus 7 - Kuroikaze AOSP
Click to expand...
Click to collapse
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
phracture said:
Could someone be nice enough as to tell me how to access my device to put the build.prop on it?
I have installed adb and downloaded the files for 4.0.3 using android ADK. I see the build.prop file that I need. However when i try to run adb.exe to see how the program works, I just get a window which scrolls through a large amount of text before closing.
EDIT: I am running windows 7 x64. Would this be easier if I tried using adb on my laptop which runs Ubuntu?
Click to expand...
Click to collapse
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Excuse me for butting in but wouldnt it be easer for him to just do the SD card. A lot less confusing at least fo me..
pio_masaki said:
Open a terminal then cd to where you have adb.exe then run it that way, otherwise it just scrolls help and closes like you saw.
Power on and once it gets stuck booting try
adb devices
And see if it shows up, if it does do
adb pull /system/build.prop
This pulls it to where adb.exe is, from there you can check it for errors or even upload it and we can check it out.
Tapatalked from my Galaxy Nexus - CN(A)
Click to expand...
Click to collapse
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
Romman0 said:
First you need to have the acer drivers installed. Second the tab will need to be booted to the recovery to be seen.
Place the build.prop you need to push to the device in the platform tools folder (the one with adb.exe). Make sure the name is properly build.prop
**There are modded ones here in the dev section here that will work, speed up your tab and/or rename it to an A500 to get more apps.
Open a command propt in the platform-tools folder (shift-right click)
type
adb devices
There should be a device listed
type
adb push build.prop /system
Your done, type reboot
It should reboot with the new build.prop
Click to expand...
Click to collapse
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
phracture said:
I'd be fine with uploading it for you guys to check out, but first I need adb to find my device.
I made sure I have the Acer drivers installed, but when I plug it in and run "adb devices" I get no devices listed.
I tried both at the screen where it stops loading as you said and at the recovery screen as Romman0 said.
I tried that and no devices are listed as I said above.
Also, the shift+right click blew my mind. That could've been and will be very useful to save me time.
Click to expand...
Click to collapse
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
phracture said:
So I still haven't gotten my device to be recognized. Should I try to connect using Ubuntu or Mac OS?
As I was told before, there is something i can do where i put the android API in an update.zip and place it on an external SD. By external SD does this mean micro SD card? Could this solve my problem potentially?
Click to expand...
Click to collapse
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Romman0 said:
Yes the microsd. And yes, if you flash the ICS stock ROM http://forum.xda-developers.com/showthread.php?t=1611696
It will fix it to. Rename to update.zip then place it on your microsd card, power off and boot recovery by pressing both the power and volume rocker closest to the corner at the same time until it starts updating.
Click to expand...
Click to collapse
Thanks for confirming and giving me that link. Problem is solved. Thanks everyone for helping a noob out.
Hi XDA users,
I am in a strange position right now, it is already two years I browse the site, and root and install custom roms on my phones.
Right now, I have a problem with my galaxy nexus, the device is rooted, I can access CWM recovery, but I did accidentally wipe my internal SD , which means no backup to restore from. I know it s silly, but it had to happen. So I can enter fastboot mode, recovery mode, but as there is nothing to use on the recovery , I d rather go for the fastboot way.
But what I am asking help for is , how can I inject the stock image? I feel the phone is not dead, at all, but I don't know how to proceed, I would gladly try the toolkit, but I m on a mac, 10.8, hence I can't run the toolkit. Anyone to help me get out of trouble please?
I can of course reach a PC, if absolutely needed, but I can make proper procedure on my laptop, it would be better.
Thank you in advance for any direction , advice , one could provide me with.
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
3rdstring said:
[HOW-TO] [GSM & CDMA] Return to stock for ALL Galaxy Nexus phones (latest JOP40C)
Click to expand...
Click to collapse
Hi, many thanks for your reply, however, when I use terminal on my mac, the device is not recognised, there is no response . Still I m looking at my phone with the droid on his back, belly open. The main thing is I don't know how to get it recognised by my mac.... rrrrrr !!!! I m confident it will work out some time, but now, I m still stuck. And I m not really easy with adb, but willing to learn...
When in terminal and I type ./fastboot-mac devices it reads " no such file or directory, so what am I doing wrong? Maybe a question , in terminal, when I want to indicate in which folder is the platform-tools-v6 folder , ijust drop it in the terminal window... Am I right or completely wrong?
Usually I tend to read tens of pages in xda, and it is not like I want to be spoon fed, but since yesterday I m trying to go through all the troubles I have, but so far no luck!!!
Thanks anyways to whoever will help me out.
Aur3L said:
When in terminal and I type ./fastboot-mac devices it reads " no such file or directory, so what am I doing wrong? Maybe a question , in terminal, when I want to indicate in which folder is the platform-tools-v6 folder , ijust drop it in the terminal window... Am I right or completely wrong?
Usually I tend to read tens of pages in xda, and it is not like I want to be spoon fed, but since yesterday I m trying to go through all the troubles I have, but so far no luck!!!
Thanks anyways to whoever will help me out.
Click to expand...
Click to collapse
When your in a terminal window you want to change directories to where you have the platform tools & image files before typing in the commands. I'm not sure how you do that on a Mac. Inversely you could copy the platform-tools files & the image files to where ever the terminal window opens.
Well, yes, but it drives me crazy to not know where the terminal is looking at... However, I managed to connect to my phone in fastboot, there was a script I pasted in the terminal window, which I have executed several times, and which made the phone reboot in fastboot mode.
So there is some kind of progress... :fingers-crossed:
What mistake have I done yesterday.....
I also tried through heimdall 1.3.2, which detected the device, but could not load anything properly, so I gave up that option , back with the fastboot mode.
So I m not sure how I will manage it, but I m not done with it now.
Edit: Finally, I managed to get control of the the phone, thanks to the work of Techfanatic9 and his Gnex toolkit for mac. What a relief, but in the meantime it got me to deal with adb, and I guess I will certainly dig deeper in this way to interact with phones .
So, of course, many thanks to 3rdstring for being so helpful and so fast ! All is well that ends well.
this is the link that got me out of trouble , so if you happen to be a mac user and get a bit out of control with your phone , check it out.
http://forum.xda-developers.com/showthread.php?t=1790399
Hi Folks
Let me preface by saying I've flashed RUU before, and flashed many recoveries and ROMs over the years, not a total novice, but certainly no expert either. But I've never seen anything quite like this one, and not sure what to do at this point.
first, I downloaded the GPE non-rooted RUU and copied the zip into my ADB folder (Windows 10 PC)
then, I connected phone, shift+rclick open cmd window in ADB folder
renamed the file "ruu2.zip" (which was a mistake, it should have just been "ruu2")
adb devices - device recognized
adb reboot bootloader
fastboot oem readcid - it's GOOGL001, no problem
fastboot oem rebootRUU - no problem, HTC logo displayed on device
fastboot flash zip <drag and drop file into cmd window> - (note, I haven't actually done that before, I've always just typed it, and drag+drop showed whole file path - "C:\user\me\adb\ruu2.zip.zip" - but shouldnt make a difference, as far as I know, so I hit enter)
it ran through everything, checked zip, etc then failed. This is expected and normal, no problem.
so I hit up arrow, reloaded the command and hit enter...
and now my cmd window is stuck. It says "sending zip", displays file size, and the cursor is flashing...and nothing is happening. It's been an hr or more. Nothing is going to happen.
Now what?
If I pull the phone am I going to be bricked? I just alt-tabbed and googled for a solution, but didn't find anything. So I figured I better post here. This is not a good place to be stuck.
Thanks in advance.
(I have a screenshot of my cmd window but I don't have enough posts to link it.)
EDIT: Figured worst case = new phone. Pulled cord. CMD window reset itself, phone stayed in RUU mode. Would not power down or respond to any button combo. Reconnected cable, entered command again, and it went. Worked fine. No idea why that happened, but all is well.
Thanks anyway.
Mods, please close thread. Thanks.
Sir_Cusfreak said:
renamed the file "ruu2.zip" (which was a mistake, it should have just been "ruu2")
Click to expand...
Click to collapse
Highly recommend you disable the Windows option to hide file extensions, to avoid any future file name confusion.
Sir_Cusfreak said:
Mods, please close thread. Thanks.
Click to expand...
Click to collapse
Threads typically stay open, in case there are other members with a similar issue, subsequent comments, etc.
Mods usually only close threads, if you start a thread about something you shouldn't have!
Hi, just wanted to say that the same thing happened to me, i got stuck on sending zip .. and i did like the OP, disconnected the cable and reconnected again, the cmd reset just like the OP said and after i put the command again it worked for me too. Cheers.
i had to do the trick a few times before it worked. thanks