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.
Related
Here is an interesting article that will help you if you want CRT screen Off animation like in Nexus S:
http://www.freeyourandroid.com/guide/enable-crt-animation
Worked with no problems on my SGC with Rogers ROM.
I actually used NinjaMorph to package the modified resources.arsc into framework-res.apk, but I assume the original method will work too.
Safe to flash
this?
Aquethys said:
Safe to flash
this?
Click to expand...
Click to collapse
Probably no. Most likely you will end up with phone freezing on the Samsung logo at boot. framework-res.apk files are not interchangeable between models, maybe not even between firmware versions for the same phone.
Can you post a step by step guide then? I can't really understand anything here
The step-by-step instructions from the link in the first post are pretty much what i did. Read the comment by ravenstark - if you mount the filesystem with root explorer there will be no need to execute the commands in red in section 8.
The instructions from the link in your post cover steps 3-7. You still have to download the file to your PC (1), decompile it (2) and upload it back to the phone once you are done with it (8).
For the first step which terminal do you use??
(Free Your Android guide)
adb. If you don't have you can download it from here. It is part of the SDK and probably the most essential tool.
The command is exactly as written there
Aquethys said:
For the first step which terminal do you use??
(Free Your Android guide)
Click to expand...
Click to collapse
What do you mean? If you're using a Windows PC, then just open up a cmd prompt. You should read the guides at the beginning of that page so you know how to setup adb and the apk tool.
The big picture is this. Connect your pc to computer, pull file from phone to PC using adb, modify file on PC, push file back to phone using adb.
For what it's worth, here's a thread I wrote quite a long time ago, some is not applicable for the Glide, but most of it still applies. If you're going to be mucking around in your phone it's best to know how to do a few things first. Read Before Flashing.
When I try and open SDK or AVD (what's the difference :| ) then I just get a quick terminal screen that closes.
It would be appreciated if someone could just create a flashable CWM version >_<
I hate my inexperience @ this. It keeps saying this isn't "adb" isn't recognized, but I've downloaded it! How can I check?!
Aquethys said:
I hate my inexperience @ this. It keeps saying this isn't "adb" isn't recognized, but I've downloaded it! How can I check?!
Click to expand...
Click to collapse
Ok, so what have you done so far?
What should be done. Assuming you're using Windows, install the Android SDK. Once installed, launch the SDK Manager. Then from the list of installable options, choose the Platform Tools and I always like to get the drivers. Once done, you will have this path, CrogramFiles(x86)\Android\android-sdk\platform-tools, now you could add this path to your variables in Windows, which would be easiest, or copy the Platform-tools folder to C:. Then plug in your phone via USB to your computer.
Now, if you added the Path to your variables, just go Start>Run>cmd, and at the cmd prompt type adb devices. If you see a device you're good.
If you copied the Platform-tools folder over, then Start>Run>cmd, and in the cmd prompt type,
C:
then
cd platform-tools
then
adb devices
Beyond that, can't really help, never use apk tool. Good luck.
Aquethys said:
It would be appreciated if someone could just create a flashable CWM version >_<
Click to expand...
Click to collapse
Attached to this post is a CWM update with CRT Screen OFF and battery icon with percent for ROGERS ROM. I'm not sure this will work on AT&T ROM.
Make a backup before applying this update so you can restore if you end up stuck on SAMSUNG logo on boot.
Apologies to the author of the battery mod - I couldn't find his post to link to here...
Aquethys said:
I hate my inexperience @ this. It keeps saying this isn't "adb" isn't recognized, but I've downloaded it! How can I check?!
Click to expand...
Click to collapse
Hopefully the file tcfx44 posted works for you. Either way, I highly suggest you learn how to use adb and some other tools if you plan on flashing your phone in the future. It could prove useful some day.
Will this apply over OsiMood? I really am not sure if I am using the Rogers, but apparently I am because in XDA App it says I927-R and same with a benchmark.
Doesn't work for OsI mood 2.1.30 or whatever version was released today. I don't want to give up the amazing UI and stuff of OSi. I'm working fine though, so doesn't look like the install failed or bricked. Any revisions?
Aquethys said:
Doesn't work for OsI mood 2.1.30 or whatever version was released today. I don't want to give up the amazing UI and stuff of OSi. I'm working fine though, so doesn't look like the install failed or bricked. Any revisions?
Click to expand...
Click to collapse
I changed a bit the CWM mod. Hopefully this one will work. Make a backup of your current ROM - I'm not sure if this mod is compatible with OsiMood.
tcfx44 said:
I changed a bit the CWM mod. Hopefully this one will work. Make a backup of your current ROM - I'm not sure if this mod is compatible with OsiMood.
Click to expand...
Click to collapse
CRT Screen Mod -- Works with Rom manager..
Addition
Default Battery Indicator Changed.. Shows Percentage in steps of 5%..
Anyone having problems powering off and crashing GO Launcher? (then run through media scanner, etc..)
Could you remove the battery mod? I don't like it compared to OSiMood battery >_>
Finally, sorry for demanding so much, could you also put CRT on and ICS animations here?
Sorry!!!!!
Having serious problems turning off. This then affects my underclock.
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
wipe everythin and reflash another rom/same rom...............
2012katas said:
wipe everythin and reflash another rom/same rom...............
Click to expand...
Click to collapse
i guess that'll work, but could anyone recommend another, more time-saving possibility?
greets to india!
Tourist06 said:
Hey guys,
I was using Sandvolds ICS for some weeks, but since yesterday my phone won't work anymore. I was starting a bike tour, but GPS on Endomondo didn't really work. So I restarted my phone. When I boot it'll show the white screen with green HTC logo, then it'll show the Evervolv animation and this animation will be displayed until I remove the battery, one time I had it running for half an hour.
I tried to boot the phone without sd card and could boot, but after "optimising" apps it kept on crashing because, as it appears, the system data is partly on the sd card.
Now I don't know what to do, what would you recommend? I'd probably just wipe everything and reinstall a backup, but - I don't have a backup
Click to expand...
Click to collapse
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
UserMatty said:
I got the same situation with you dude!!
I'm now using beta 0.17.1, but after this afternoon everything was wrong.
Then I did a full wipe and installed the latest version of Sandvolds ICS,
It's good and normal before I activate a2sd, but after that
everything went wrong again.
And finally I tried HTC DESIRE-AOKP-milestone6 v2,
It is working normally with INT2EXT, but not very smooth and stable.
actually i don't know what's going on right now :crying:
Click to expand...
Click to collapse
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Cesk87 said:
hi everybody..i've got the same problem..everything was ok until yesterday with the latest release of the sandvold ics rom..when my phone shutted down for low battery,i put it on charge..after that,i booted it up,and it still remain on the evervolv logo...so i tried to wipe cache,wipe partition,factory reset and format and repartition the sd card..reinstall the rom..and eveything was ok the first time..after that,i enabled the a2sd,and it strucked another time..so i did everything again from the beginning,but this time i enabled the a2sd without any problem..so i started to download from the market all the stuff that i needed,and everything was fine..so i rebooted the phone..and here we go again..strucked!but the worst thing is that without the sd,the phone boot without any problem!now..i bought the sd a week ago..it's a new one..i don't think that it's an sd problem..or also the first times it won't be able to boot up and everything..also i would't be able to install the rom!..so..any suggestion?
Click to expand...
Click to collapse
maybe you can temporarily try DESIRE-AOKP-milestone6 v2
it's also a good choice! and a good rom also.
Hey,
I have the same problem! I also have Sandvolds ICS rom and it gets stuck on the Evervolv loading screen.
It loads up flawlessly without my SD card but then all my stuff is gone.
Any way to backup my data? (EDIT: Nevermind that question, I used backup from recovery)
BTW, SD card works, I can mount it from recovery mode.
Guys, what you say doesn't make me happy!
Maybe it's worth mentioning that I was NOT using the latest version of ICS, but I had no problems for weeks. I'm already waiting for the new Nexus phones, one of them will save me a lot of time and trouble updating to the newest OS and software
Good luck everyone, and please tell us if you manage making your phone working again
tried updating to latest ics via 4ext - fail! i could watch the evervolv animation for hours
Possible Solution
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
The solution is here: http://forum.xda-developers.com/showthread.php?t=1944766
For me didn't work, but I want to try again and apply the solution directly on the first boot.
AceShinobi said:
Looking in the Sandvold's thread a lot of people have been claiming that the bootloops is caused by the most recent version of Google Play 3.9.16. Apparently just deleting that will let you boot fine.
Click to expand...
Click to collapse
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Tourist06 said:
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Probably because there is no folder /data/data? Have you followed the instructions in this thread? That should work.
Tourist06 said:
Thanks for your hint, but after a few steps, I was stuck. After downloading the SDK (not mentioned in the tutorial) I experienced problems in the following steps, here is where I had problems
- cd Program Files(x86)/Android/android-sdk/platform-tools/ - I had to enter cd AppData\Local\Android/android-sdk/platform-tools/
- adb shell - command didn't work - I entered adb resulting in lots of text on my screen
- cd /data/data/ - the shell didn't accept this
Click to expand...
Click to collapse
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
freakymonkey said:
Seems like an adb fault.
If you type: adb get-state and adb get-serialno you have in output the infos of your Desire?
Click to expand...
Click to collapse
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Tourist06 said:
[...] I mounted system and sd-card [...]
Click to expand...
Click to collapse
You need to mount "system" and "USB storage". You have to be connected to your computer.
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
Exactly, you have to mount more or less everything, depends on what kind of a2sd you have.
In my case, I had to mount everything because of "standard app2sd"; my "vending" are in /system, /data and /sdext.
Just to be sure, you have to undestand if the phone is connected to the computer. To check this try to write:
...../platform-tools/adb kill-server (press enter)
...../platform-tools/adb start-server (press enter)
NOW plugin your HTC Desire (in Recovery mode) to the computer and digit:
...../platform-tools/adb devices
Should appear at least your Deside (on the right side of the phone code will appear the word"recovery")
If this appear, you can prooced with "adb shell" or all other commands required for the procedure.
I had the same bootloop problem, it was easy to remove all the Play Store files.
Hope helping you.
Mat
Tourist06 said:
adb shell will return device not found, adb get-serialno and adb-get-state return unknown
Using 4ext, I mounted system and sd-card
I also tried dietwice's tip (http://forum.xda-developers.com/showpost.php?p=33073702&postcount=8), but at step 3, cd /system/app , it says path not found. I'm no guru, so I don't really know what to do now.
Sorry about the fonts, it's a mess^^
Click to expand...
Click to collapse
gartenriese said:
You need to mount "system" and "USB storage". You have to be connected to your computer.
Click to expand...
Click to collapse
I think that Tourist06 can't resolve with mounting /system or something else, because he has a problem with adb (adb don't talks with his device).
Have you followed this guide for installing adb?
@freakymonkey: I followed the guide, seemed to work! If I enter the shell I no more need to enter the whole path, entering "adb" will produce text. Please have a look at the following screenshot, hope you can confirm this.
@matteo.rex, no success, here's a screenshot
A pop-up appeared saying there were unidentified devices.
Thanks for your help, guys! My phone isn't working for the sixth day now
Tourist06 said:
A pop-up appeared saying there were unidentified devices.
Click to expand...
Click to collapse
Uhm, this is the problem maybe.
First question: is the phone charging when you plugin it to the pc? (I had a problem with the cable...solved changing it)
Second: could be not an ADB installation problem, but a Driver Installation problem. Check this thread to download it: http://forum.xda-developers.com/showthread.php?t=654047
If typing "ADB" a list of command appear, this mean that it work.
Windows, after the driver installation, have to recognize you Desire also during Recovery, not only during common use.
I hope it could help you!
Let us know!
p.s. I use ADB over Ubuntu, but the work is the same.
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.
So i wiped internal storage and now i have no rom on my phone. I can still get to recovery but adb does not see my phone. i was hoping i could push it using ADB but like i said it does not see my device!!! need help cause my wife will not approve a new purchase!!!
Do you know how to get to fastboot? You can use fastboot to push the files you need to load the OS.
elinca247 said:
So i wiped internal storage and now i have no rom on my phone. I can still get to recovery but adb does not see my phone. i was hoping i could push it using ADB but like i said it does not see my device!!! need help cause my wife will not approve a new purchase!!!
Click to expand...
Click to collapse
This should have everything you need:
http://forum.xda-developers.com/showthread.php?t=1989675
Basically the issue is that there is no Hardware ID assigned in Windows to your Nexus 7 when in recovery mode. You'll notice that the only difference is two lines in the .inf file added to fix this. If you're using Windows 8, then you may have issues with unsigned drivers after modifying them. Just follow the instructions linked in the OP to boot into Windows 8 with driver signing disabled.
The link below is to my modified drivers, using the instructions linked above..
https://www.dropbox.com/s/g59tpy70dlwdmfz/Nexus%207%20Driver.zip
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
CrankyPants said:
first of all i want to say that I almost know nothing about rooting and stuff.
I rooted my phone with the all-in-one toolkit and actually didn't know what I was doing. I was just clicking next and did what the screen told me to do. Everything went great and i had no problems until know. I downloaded and flashed the venom dotview tweak but it didn't work and the normal dot view which I reinstalled also didnt work so I decided to do a recovery from the settings app. it was really stupid to do that beacause my softkeys and statusbar are gone know and the flashed apps are still there. Is there a way to have my phone like it was when I bought it? I don't need a root anymore, I just want my phone getting to work normal.
Thanks
Click to expand...
Click to collapse
Restore you stock ROM nandroid. Look for it in here COLLECTION of Stock backup's seeing as you really didn't bother to provide us with the relevant and more important information such as the CID and Main software version you were on before you decided to mess your phone up and I doubt you made a backup of your device before doing it.
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
I guess I will be the "bad guy" but why are you messing with your phone when you have no clue what you are doing?
Everyone starts somewhere. Im sure we all learned a lot of what we know now by making lots of stupid mistakes. This logic rings true for life... not just phones.
lucas.scott said:
Is your phone still recognized by a pc?
If so, just load another ROM on your sd card.. Wipe everything and flash through recovery. You'll lose all your data, but your phone will be back.
Since you are new to this - CONGRATS! You just learned the most important rule of flashing. Always make a backup first!
Good luck man. It's an easy fix.
Click to expand...
Click to collapse
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
CrankyPants said:
yes and no, my pc sees him but the phone folder is empty en htc manager gives an error. any idee how to put a rom on the phone?
Click to expand...
Click to collapse
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Jyotirdeb said:
Unlock bootloader,install a custom recovery via adb then download a custom rom of your choice then move it to ext/internal sd.you may use otg.Then go to the custom recovery(TWRP/Cwm/philz) wipe then install zip through the location.
Click to expand...
Click to collapse
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
CrankyPants said:
How to install a custom recovery via adb and what is adb?
sorry I don't know anything
Click to expand...
Click to collapse
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
leongwengheng said:
I'm a beginner too, but I learnt loads from watching videos from a channel called Sakitech on YouTube. I watched them over a few times to understand the process before doing anything.
Unlook bootloader:
https://www.youtube.com/watch?v=rEVSfwXsx-c&index=3&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA
Turn S-Off:
https://www.youtube.com/watch?v=--Hlms1BuPg&list=PLRt6ru-Tz2f4tMLvv9wm9yyiW9mTeVIGA&index=4
Install a custom recovery and root your phone
https://www.youtube.com/watch?v=WuHFcGvUjwA&feature=youtu.be
Install a custom rom:
https://www.youtube.com/watch?v=t4KeVs5axtM
Remember to backup before you put your phone under serious surgery!
https://www.youtube.com/watch?v=eda67mn-oXc
Hope this helps.
Click to expand...
Click to collapse
Good choice on the videos, these days reading is a bit to tedious for most people. Heck, they don't even read "STOP" on the STOP signs anymore, just drive straight past
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
leongwengheng said:
I have a super short attention span so I need YouTube to learn anything in life lol.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Good luck at school then and later on in your job
Lucky boy having such a commited community here. You could've quite easily ended up with a £600 paper weight. Might want to show some appreciation to everyone holding your hand through a process that you should've read about before doing anything. Must admit, I did like the 'I just kept hitting next without knowing what I was doing', that's probably the best thing I've read lol lol.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
BerndM14 said:
This is why you shouldn't use all in one toolkits, you don't learn anything like that and if you're not willing to learn then you probably shouldn't mess around with these things in the first place, expect others to then fix the problems for you. I'm not trying to be mean here, just stating fact.
Download the Android SDK
After downloading, extract the .zip file. Then go into folder inside the sdk folder you'll find a folder named "platform-tools" right click that folder and copy it on your desktop(Ease of access). Inside that platform-tools folder you'll find the applications adb and fastboot.
Download HTC Sync Manager in order to install the drivers(If you haven't done so already and just to be sure).
Download custom recovery, either Philz CWM Recovery or TWRP Recovery . Place the downloaded .img recovery file inside the platform-tools folder.
Make sure your phone has USB-Debugging enabled, if you don't have developer mode on phone. Go to Settings > About > Software Information > More > Tap 7times on Build Number. This will enable developer options. Go back to Settings and scroll down to Developer Options, open it and enable USB Debugging.
Connect your phone to the PC, make sure to accept any prompts that might appear on the phone then inside the platform-tools folder, hold shift then right click, then select "Open Command prompt here". Type adb devices if adb picks up your device it'll show you your devices serial number. Next type adb reboot bootloader to boot into bootloader mode then type fastboot devices again just to make sure the device is connected and being picked up by the prompt. Type fastboot flash recovery name_of_recovery_you_downloaded.img MAKE SURE you type in the correct name for the recovery, exactly the same!!!
When it's done, flash ROM of your choice.
Click to expand...
Click to collapse
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
CrankyPants said:
I have one problem. Since I don't have the notification bar anymore, the phone doesn't notificate me. How will I get the USB notification to work?
Click to expand...
Click to collapse
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
BerndM14 said:
If there's a pop up it'll show on screen, have you tried the adb devices command to see if your phone gets picked up?
Out of curiousity though, when you used the toolkit didn't you have to enable USB Debugging anyway? I'm not familiar with the toolkit, don't use it myself...? If you already enabled it then it's fine, as long as adb devices picks up your device then you're good to go.
Click to expand...
Click to collapse
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
CrankyPants said:
My device is already wiped so I have no configurations anymore.
I have no softkeys and no statusbar anymore since I recovered my phone with the settings app. So no statusbar means no pop-ups.
The adb devices command sees my device in the list of devices but next to it, it says 'offline'. when normaly it has to say 'device'.
Click to expand...
Click to collapse
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
BerndM14 said:
You see it's supposed to throw a small pop up on the screen of the phone where it wants you to accept the RSA key to connect it to PC. It doesn't have anything to do with the softkeys or the notification bar on the top, it's supposed to be on the screen. I take it you probably can't even get into app drawer anymore in order to go to settings. Doesn't give any pop up on the screen... I think you really did f*** up your device
Did you use Hasoon2000's all in one toolkit? If so you probably had to have flashed a custom recovery, it's like the very next thing to do after you unlock bootloader?
Click to expand...
Click to collapse
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Jyotirdeb said:
les us assume he is in stock.So he should have a stock recovery.now Boot into fastboot get the details fastboot getvar all.you will find the mid of your choice.download international fw's ruu open the zip there will be an android-info.txt file.edit the file with your mid(change 0P6B10000 to 0P6BXXXXX) where XXXXX represents your mid.then flash the ruu via recovery.Since he connects his device adb will at least detect it (i hope).
Also open toolkit on the right side it is written "next flash a recovery". Connect your phone and simply select twrp and press flash recovery.this should do it.For more details ask hasoon.
Click to expand...
Click to collapse
To get getvar all you'll need fastboot commands, will fastboot commands even work if he MIGHT not have enabled USB Debugging or for that matter haven't accepted the RSA key?
That's why I asked about the recovery as well though. I saw that on hasoon's toolkit the flashing of a custom recovery was like the next step on the process which means that this guy should at least have a custom recovery already installed.