Related
Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man
So, my phone is stuck in a boot loop. I can restore factory setting but first i want to back up my data .. specifically my text messages and pictures. They are very important. Is there a way i can do that ?
the bad news is Im not rooted. now im trying to find ways to save data from my the phone before i do a factory reset. i hope i can sort it out.
Thanks,
runingwild said:
So, my phone is stuck in a boot loop. I can restore factory setting but first i want to back up my data .. specifically my text messages and pictures. They are very important. Is there a way i can do that ?
the bad news is Im not rooted. now im trying to find ways to save data from my the phone before i do a factory reset. i hope i can sort it out.
Thanks,
Click to expand...
Click to collapse
Your pictures should be on your SD and unaffected, but without root I'd say goodbye to your messages.
XperienceD said:
Your pictures should be on your SD and unaffected, but without root I'd say goodbye to your messages.
Click to expand...
Click to collapse
so is there no hope even by using ADB commands for example, or some other way? :crying:
up
runingwild said:
so is there no hope even by using ADB commands for example, or some other way? :crying:
Click to expand...
Click to collapse
I think, without root, you can't view /data, but you can try.
If you can, the sms should be located in this .xml: er /data/data/com.android.providers.telephony/databases/mmssms.db
Then backup it via adb, reflash your rom and replace the file with the backuped one.
If you can't access /data, maybe you can root/flash cwm to your phone too, if it's bootloped? (Phone specific, so I don't know.)
Good luck.
Sent from my GT-I9100 using xda app-developers app
cakebomb said:
I think, without root, you can't view /data, but you can try.
If you can, the sms should be located in this .xml: er /data/data/com.android.providers.telephony/databases/mmssms.db
Then backup it via adb, reflash your rom and replace the file with the backuped one.
If you can't access /data, maybe you can root/flash cwm to your phone too, if it's bootloped? (Phone specific, so I don't know.)
Good luck.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
thanks for the advice,
and how can i view the .xml file? (im not experienced with android..)
btw, its an Htc Desire S. yes its stuck in bootloop now
runingwild said:
thanks for the advice,
and how can i view the .xml file? (im not experienced with android..)
btw, its an Htc Desire S. yes its stuck in bootloop now
Click to expand...
Click to collapse
Connect your phone to your computer, start adb shell and type in su and then cd data
If you can view the directory by typing in ls you should be able, to copy the .xml to your computer.
Sorry for the late reply.^^
cakebomb said:
Connect your phone to your computer, start adb shell and type in su and then cd data
If you can view the directory by typing in ls you should be able, to copy the .xml to your computer.
Sorry for the late reply.^^
Click to expand...
Click to collapse
ok thanks. i downloaded SDK, then installed ADB package. But now i click on Adb icon and it wont open. what am i doing bad??
runingwild said:
ok thanks. i downloaded SDK, then installed ADB package. But now i click on Adb icon and it wont open. what am i doing bad??
Click to expand...
Click to collapse
You have to open cmd.exe and navigate to the location, where the adb file is located.
Then type in ‘adb shell’.
Sent from my Nexus 7 using xda app-developers app
cakebomb said:
You have to open cmd.exe and navigate to the location, where the adb file is located.
Then type in ‘adb shell’.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
when i type in adb shell, it says Error: device not found, while the phone was in the boot menu.
Is it maybe because im missing drivers? I googled a bit and now i have the driver i need, its .exe file , what should i do with this file? if i double click on it, i get an error message.
thanks
runingwild said:
when i type in adb shell, it says Error: device not found, while the phone was in the boot menu.
Is it maybe because im missing drivers? I googled a bit and now i have the driver i need, its .exe file , what should i do with this file? if i double click on it, i get an error message.
thanks
Click to expand...
Click to collapse
Yes, the drivers could be the problem or maybe (but I don't hope so) the phone isn't recognizable in this mode via adb.
If you're using Windows, go to the device manager and check, if there's a android thing with a exclamation, then refresh the driver of this, if it's possible. Simply via right click etc. (Of course, if the device is connected.)
And have you tried this here? http://forum.xda-developers.com/showpost.php?p=15585507&postcount=2
btw: Your phone seems to don't boot up since a few days, do you don't need it? Another idea is, maybe you can backup all your files via fastboot/download mode or something else, but you'll have to post this question in the device specifically forum, because it's different on phones.
Okay, one more time good luck.
hello
cakebomb said:
Yes, the drivers could be the problem or maybe (but I don't hope so) the phone isn't recognizable in this mode via adb.
If you're using Windows, go to the device manager and check, if there's a android thing with a exclamation, then refresh the driver of this, if it's possible. Simply via right click etc. (Of course, if the device is connected.)
And have you tried this here? http://forum.xda-developers.com/showpost.php?p=15585507&postcount=2
btw: Your phone seems to don't boot up since a few days, do you don't need it? Another idea is, maybe you can backup all your files via fastboot/download mode or something else, but you'll have to post this question in the device specifically forum, because it's different on phones.
Okay, one more time good luck.
Click to expand...
Click to collapse
yes, in the device manager there is an android thing with a yellow exclamation. i clicked on refresh the driver and i get the window asking me where i want to get the driver from. since i have the driver in an Sd card, i´ll try that tomorrow.
well, i do need the phone, but now im using my old one. until i can finally fix this issue.
What did you mean with the Fastboot mode? when im in the boot menu, i can select Fastboot, but it wont help much, because it will just start the booting again (bootloop). but i dont know if this is what you meant with fastboot.
thanks
runingwild said:
yes, in the device manager there is an android thing with a yellow exclamation. i clicked on refresh the driver and i get the window asking me where i want to get the driver from. since i have the driver in an Sd card, i´ll try that tomorrow.
well, i do need the phone, but now im using my old one. until i can finally fix this issue.
What did you mean with the Fastboot mode? when im in the boot menu, i can select Fastboot, but it wont help much, because it will just start the booting again (bootloop). but i dont know if this is what you meant with fastboot.
thanks
Click to expand...
Click to collapse
Okay, but you can also let Windows automaticly search the internet for the drivers.
About fastboot, I don't know if you can backup files with this. (Normally you can use this to flash boot.img etc.) And I don't know, how it works on your device, so ask in your device forum.
Sent from my GT-I9100 using xda app-developers app
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
runingwild said:
adb is not recognizing the device, so im giving up on recoverying the phone data. I tried a factory reset to fix the bootloop but it aint working either. So now i can only think of sending it to the Htc technical center, the phone is under warranty.
Click to expand...
Click to collapse
Okay.
Are you talking about flashing stock rom, when you said factory reset?
If not, maybe this helps. (There's a link to flash stock rom in this thread.)
http://forum.xda-developers.com/showthread.php?t=1186401
Sent from my GT-I9100 using xda app-developers app
I was trying to disable FSYNC using the method described by poofyhairguy. I did it via terminal, in su. I mounted /system in rw mode, I copied libsqlite.so and libsqlite_jni.so into backup copies, and overwritten them with copied provided by poofyhairguy. Alas, I forgot to chmod, so they were left with whatever permission they came from. I rebooted the tablet and now it is permanently in the starting screen with big ASUS letters across. I cannot even turn it off!
Help, please, what do I do? I don't really know much about Android, so please use simple explanation.
Just to add some details. My Prime is stock, rooted but not unlocked.
I also don't seem to be able to reach it from ADB. I did install ADB and drivers on my PC a while ago, when I rooted it. I'm trying this now:
- connect Prime to PC
- reboot with volume down, select a USB symbol
- PC says "installing drivers" and "ready"
- in adb shell, when I try "adb devices" it shows an empty list
Any help?
OK, here is more information and more questions. I can start the tablet in fastboot mode (USB symbol on screen). After reinstalling ASUS suite and Google SDK I connected the tablet to my Windows 7 laptop. It searched for drivers for a while, installed and said "ready".
"adb devices" returns and empty list. "fastboot devices" returns one entry, a long hexadecimal number and the word "fastboot". Does it mean that I can see my tablet via fastboot but not adb? Does adb work when tablet is in fastboot mode at all?
Does it mean that the only option is to reflash ASUS firmware?
@Felisek Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Sorry, I'm not much expert in android underhood that I can help you more but looking at your problem doesn't look like you have bricked your device so keep hopes. Someone having more knownledge might come and help you.
btw; AFAIK, adb and fastboot are different kinds. You see fastboot.exe in the sdk package? yes that links with fastboot option on the devices. But I might be wrong as well.
May be you try entering into fastboot and use fastboot.exe, then go to the path where you modified the files. Either replace them to original ones or chmod. But I don't know whether this gonna work.
CRACING said:
Did you tried to wipe aka hard reset the device via bootloader? or you have important files which you don't want to reset? or you don't see wipe option in bootloader?
Click to expand...
Click to collapse
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Felisek said:
There is a wipe option, but I don't think it is going to work. As far as a know (correct me if I'm wrong), factory wipe does not change /system folder. In particular, there are two "wrong" files in /system/lib that cause the problem, so wiping everything else is not going to help. I need to change/restore these files.
Click to expand...
Click to collapse
Hmm may be you are right so reflashing whole ROM is required.
Felisek said:
I think I can reflash the stock ROM using recovery, but I'd like to try and fix it without wiping everything first. I don't have anything unmissable on the tablet, but reinstalling everything and rooting is a bit of a hassle.
Click to expand...
Click to collapse
Recovery? but you said you haven't unlocked or you mean stock recovery?
Yeah, upon reflashing, you will lose root but hey, you can root again using the new method (motorola's) and its not at all risky as unlocking. :good:
May be you can wait for sometime, I hope someone comes up guiding you how to replace/modify the system files using adb or fastboot.
CRACING said:
Recovery? but you said you haven't unlocked or you mean stock recovery?
Click to expand...
Click to collapse
There is a "RCK" option on startup, I thought that was recovery. But, yes, I mean stock recovery, if this is how it is called. Download stock firmware, put it on a microSD, rename it to EP201_SDUPDATE.ZIP, reboot and apparently it installs automatically.
When I was making my guide I tried using the old ICS libsqlite.so and libsqlite_jni.so files and softbricked in the same mannor. The only way I found to fix it was to flash the stock ROM as it says to do in my guide.
Note that unless you purposefully wipe your data in the recovery your data should remain intact from my experiance with it. The way the stock Asus recovery seems to do it is to blow /system away (so yes you must re-root, etc).
Good news. I unbricked my Prime by reflashing the stock ROM, using the method described by poofyhairguy. All my apps and settings survived. I only lost root, so even rootkeeper cannot recover it. Not too bad, after all.
Sent from my Transformer Prime TF201 using Tapatalk HD
So I should not be doing this on so little sleep, obviously. I have a Verizon HTC Droid DNA, Moonshine S-off, TWRP, and I had CarbonROM on it, but I was having issues so after some fumbling around and trying different things, I was at a loss. So I wiped all data and formatted. Well, before this, for some damn reason, I think I turned USB Debug off. Now I can't get into Fastboot USB. Am I totally screwed? My PC won't communicate with the phone.
HELP!
Actually its difficult to be "totally screwed" you can always hold the power + volume down until the phone boots into HBoot. Once your in HBoot again fastboot should work if it doesn't then that generally a driver issue. Once your back in HBoot you can select fastboot and that will give you the option to boot back into recovery. Once you get into recovery again I would select sideload and flash the ROM using "adb sideload <rom name>" making sure your in the adb directory and so is the ROM. Hope this helps.
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Kevin5377 said:
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Click to expand...
Click to collapse
PC driver issue, go into device manager and load new driver
I'll take a look
Sent from my Nexus 7 - Carbon Rom
Yeah, I'm not even getting the Windows sound like I connected anything. Usually it'll tell you no drivers or unsuccessful installation or something!
Holy crap... well you were right... it was a driver issue. I reinstalled the HTC drivers and I got FASTBOOT USB now... thank goodness!
I feel like my brain isn't working. How do I now get my .zip on my device using fastboot so I can then get into recovery and flash it?
Nevermind... booted to recovery, used adb to push my .zip to device
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
trickster2369 said:
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
Click to expand...
Click to collapse
Even more fun when they answer themselves
hawkstwelve said:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
Click to expand...
Click to collapse
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Enjoy
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Thanks that worked! Back to loving viper.
I Have a similar problem
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Hey i'm new to this and i also formated my phone when installing a new rom i can still get into twrp and when i plug in the phone to the computer fastboot usb shows up and it makes the sound on the computer however when i type adb devices in the cmd its blank could someone please walk me through the adb stuff sorry for being a noob
I also have a OTG cable but i tried to plug in a 16GB FAT32 flash drive but twrp didnt recognize it. it says unable to mount
Thanks a bunch
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Kevin5377 said:
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Click to expand...
Click to collapse
Thanks a bunch but i plugged in a bunch of flash drives until one was recognized and then was able to restore my old ROM... WHEW
solved mods delete this as idk how
why don't you share with the rest of us what you on how you did it, instead of deleting your thread.
flashhsalf said:
why don't you share with the rest of us what you on how you did it, instead of deleting your thread.
Click to expand...
Click to collapse
Follow this guide > http://forum.xda-developers.com/showpost.php?p=52170480&postcount=2
before the mods del,ete this, i wanna ask a relative question. I've gotten adb to recognise my dna on my computer, and i can use adb commands, but when I get to fastboot to flash the new firmware, i get a (waiting for device) message where nothing happens. where did i go wrong?
champdr0id said:
before the mods del,ete this, i wanna ask a relative question. I've gotten adb to recognise my dna on my computer, and i can use adb commands, but when I get to fastboot to flash the new firmware, i get a (waiting for device) message where nothing happens. where did i go wrong?
Click to expand...
Click to collapse
In your adb folder press shift + right click and open the command prompt window from there and try that. Try a different USB port?
HTC DNA
Saw and tried both with no better results. I ended up using the recovery flashable zip in santod's closed thread without any problems. I know it's not the full RUU, but whatevs for now. Thanks though!
Beanstalk holds a special place in my heart.