I'm hate saying I'm a noob, I'm not but honestly with android I am. So here's my issue:
I have all my adb drivers and all the files I need. I stuck all of them on my C drive root and set up command prompt to CD to the 'tools' folder. When I first tried to root my MT3GS I (not sure why) didn't know to press 'vol. up + power' and after much frustration, just gave up Now that I've spent all my spare time reading up on everything android related and studied some more adb commands I've tried to root again. Once I start the loop and boot to recovery, adb sees my phone for a second (one loop) then - nothing. For the past 3 days I've tried and that's all I get, I've re-installed the drivers so that's not the issue.
Anyone know what's going on? I really don't want to do a factory reset but if that's what I have to do then I'll suck it up and pray my backups are good. Thanks in advance.
**EDIT**
mod please delete post
Related
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
hi im pretty new here a friend of mine gave me her lg c800 mytouch to try and fix it for her.. not sure what she did she said she rooted the phone and the root was successful but i have a good idea that she doesnt know what she was doing..i will post a pic of the error screen im getting. but it says
E:Cant find misc
E:cant find misc
Finding update package...
E:unknown volume for path [sd:/download/adb_fastboot_and_other_tools.Zip]
E:Cant mount SDCARD:/download/adb_fastboot_and_other_tools.zip
Installation aborted
facory reset failed
restart factory reset..
now im far from a pro at this i know a lil more about computers and Ios devices..but ive rooted a few phones and to me it looks like she unzipped adb fastboot on her phone from her sd card??
ive tried holding F..A..vol down..and power..Nothing..
ive tried volume up .volume down and power still nothing..
BUT if i hold E..vol UP and power it brings me to a white screen that says S/W update
the big problem is the phone wont stay on long enough to do anything on the computer it stays on 3 sec. then reboots to same screen (computer says phone is unplugged) then phone just keeps restarting.
but the phone WILL stay on when i put it on the S/W update screen..but computer wont recognize the phone at all on that screen
ive tried the adb and fastboot commands but the phone wont stay recognized..it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
well thanks ahead of time if anyone has any input or solution
and hopefully all this will make sense to someone lol
i think this pic will work.. if not ill try again
any ideas please?? or am i completely out of luck?
When you say:
delilah25 said:
it will recognize the phone and say thats its in recovery mode but when phone restarts it dont see phone no more..
Click to expand...
Click to collapse
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
post-mortem said:
When you say:
...do you mean that you can successfully communicate with the phone over USB, but you only have 3 seconds? What way is the phone recognized? Is it visible to adb/fastboot?
Click to expand...
Click to collapse
Yes In Adb device list it shows the phone and then says recovery..but after that I don't have enough time to type any other commands ..the phone is also recognized in "my computer" as removable device then when the phone restarts seconds later it says device unplugged ..and just keeps restarting on its own till I remove the battery...I just read on the forum in a post that Adb will recognize the phone if it's off but I remove the battery and put it back in and plug in USB and phone turns on and keeps restarting won't even let me turn it off!! I'm losing patience with this thing lol
But I don't get why the error mentions fastboot? Not my phone so if it's not fixable I don't really care but I'm just the stuborn type when it comes to fixing electronics ..again thanks ahead of time to anyone that helps cuz I'm completely lost on this one
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
i have the same problem
post-mortem said:
Have you tried timing it to send a quick "adb reboot recovery"? If you can use fastboot, you can tell it to boot off a new, custom recovery img, without actually flashing it.
Click to expand...
Click to collapse
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
diabolus ae said:
i used an app on the market to remove bloatware. i removed slacker and the app stated that after two reboots that everything would be fine and the app would be gone. after one reboot the phone has the same screen this gentlemans lady friend has. it looks like the app its looking for is no longer zip aligned properly. someone told me to rename a recovery image the error message to trick the bootloader into thinking the missing app is there. hes an app dev so i figured he knows whats what. ive tried everything the gentleman in this post said and more. hell i have two of these phones and rooted the other and made a backup of that phone and dragged the backup to an sd card and rebooted to see if any of the backed up system apks would trigger a successful reboot but to no avail. i have all the drivers i need and adb commands but nothing works because the phone doesnt stay connected to my pc long enough for anything. please reply with some knowledge. ive been scouring the web for at least a month. i was so happy when i came across this. i actually became a member just to post about this erroer (look up diabolus ae in the forum search field. my post is about 3 days old with a better pic of the screen message. i bought a galaxy s II but i want to give the lg to my son. please help or respond:cyclops:
Click to expand...
Click to collapse
Normally, if you want to flash a custom recovery through fastboot, people will tell you to run 2 commands:
fastboot flash recovery nameofimagefile.img
fastboot reboot recovery
Since you don't have time to execute those 2 commands, you can tell it to just boot from the .img file, without flashing over your current recovery. (This is actually proper form, as you can test if the .img file works properly without damaging your existing recovery.) The way you do that is to 1st copy a recovery .img file to the root of your SD card, then execute the following 1 command:
fastboot boot nameofimagefile.img
Since you only have ~3 seconds, type the command in, and wait for the right instant to hit enter on the keyboard. If the command is successfully sent to the phone, it will reboot into that .img.
See if that works for you. Good luck.
First of all, thanks for reading my post. I'll try to make this as concise as possible.
My Sprint Galaxy S3, which is rooted with CWM v6.0.1.2 and running official Jelly Bean was doing great.
I was trying to lower the screen density as much as possible and accidentally set it too low, so now it wont load past the last Samsung logo screen.
Ive tried pulling the build.prop, and i edited it with no issues. but i had issues pushing it back in (apparently i cant give the adb proper root access.)
Ive tried reinstalling cwm.
Ive tried pushing the build.prop with the phone in recovery mode (in which case my pc cant find the drivers), download mode, on the samsung logo, and on a frozen "updating apps" screen that appears whenever i reinstall cwm, and each time i get no response when i attempt to give root access to the adb. (tried using command "adb command su" and just "su" and the cmd never responds)
I even tried a factory reset.
And nothing has worked so far.
Ive been at it for hours, searching these forums trying to learn everything i possibly can.
but now im at a loss, and i've come here for help.
I sincerely appreciate any reply. My last option on my list is to install a custom rom to see if it will overwrite the build.prop.
Please please please help me find a solution. Thanks in advance,
-Clay
---
EDIT:
ended up unrooting and installing stock rom and it fixed it.
So i guess my new question is, what are the proper methods to make sure i can push files through the adb?
thanks!
-clay
Hello Xda community, I open this thread after two days of reading and trying different ways to solve my problem.
My Nexus 5 runs Android 5.1.1 which I got OTA, I've never Rooted, installed any ROMS or done anything that might violate the system or the warranty.:angel:
Few days ago I downloaded some crappy program to my PC called Wondershare Dr.Fone (BURN IN HELL !!!) that was suppose to recover my deleted photoes from the Nexus, during the process of syncing etc.. it asked me to open developer settings and turn ON debugging mode.. which I did... and after about 30-40 minutes of "working" I realized it FROZE
The program didn't have any "Abort" button, and it was already late, so I just disconnected my Nexus, and after a moment it restarted and went into Bootloop
First I waited about an hour to realize it was infinite, then I tried going into Recovery Mode and deleting Cache Partition then restarting... it also didn't help, whenever I tried to turn it off, it was just turning on again, showing the Google Logo and then bashing those infinite Spinning Google Ballz in my face (I can turn off the phone using the Bootloader which works just fine, but it doesn't helps with the bootloop)...
The next whole day I was trying to at least recover my photos and videos, hoping that I can use the ADB to Pull the Camera folder out... I tried to install maaaany Google USB drivers following the steps of dozen tutorials, downloaded the SDK Manager and tried to install them thru Google server, and even Installed Naked Drivers with Windows 8.1 Signature Check Disabled... and tried it on 3 different PCs (win 8.1 and 7) the result was the same: Nexus 5 remained invisible until I Clicked in recovery mode "ADB Sideload.." in which case my Nexus 5 appeared in Device manager under Other Devices section (which let me install the drivers) otherwise it was invisible for my PCs...
The problem: whenever I was lunching the ADB from it's folder and typing "adb devices" I saw some sort of serial number, and "Sideload" next to it (while in other tutorials people have the word "Device" instead) and every command such as "adb usb" or "adb pull /sdcard/" or "adb pull /Camera/" result in "Error: closed" :crying:
In despair I tried to Factory reset my Nexus, and after about an hour of wiping, it allowed me to reboot which ended up in another infinite Bootloop....
I don't know what to do now, I don't live in the States and don't have warranty, I feel it's really unfair how after preserving my Nexus and it's Stock OS for so long... some Dr.fone bull**** broke it...
Please help me save my Nexus
Yea well... I knew nobody would give a crap in here... >.>
iJutsu said:
Yea well... I knew nobody would give a crap in here... >.>
Click to expand...
Click to collapse
[sarcasm]Way to stay positive.[/sarcasm]
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
davehasninjas said:
You said you've tried doing a factory reset and that your system detects your device while in sideload mode on the stock recovery, correct? If so, have you at least tried sideloading the stock system update? Could be worth a shot at least.
Or with the driver issues, have you looked into opening device manager and see if it reads any kind of connection when hooked up not under sideload?
Click to expand...
Click to collapse
Factory reset didn't give any results, just destroyed any hope of recovering the photos I had onboard...
The system did detect my device for some time only when I activated the "ADB Sideload.." in the Recovery mode, but it wasn't same as in most guides and tutorials I've seen... When I typed the command "adb devices" it showed "4bd...serial.. Sideload", while according to tutorials it should be detected as "4bd.... Device"... Also I think the phone should get detected even without pushing the "Adb Sideload"... but the main problem is that every command results in "Error: Closed" so I can Pull or Push or Sideload anything since it's always same error"... which made me think perhaps the drivers aren't Okey, but I tried every Nexus 5/Google driver I could find, and I really doubt it's the drivers fault.
As I said the device remains invisible both in Device Manager and in Devices and Printers, until I click the Adb Sideload on the Nexus...
Factory Reset didn't work even tho I've never did any root or install Stock ROM or Kernel or anything of that sort, makes me wonder if that Dr.Fone crap app actually bricked my phone...
Thanks for trying to help
beekay201 said:
When adb is in sideload mode, you cant use any of the normal adb operations, like pull or push.
Click to expand...
Click to collapse
Aw... that's what I suspected... But activating the ADB sideload is the only way to make my Nexus 5 visible when I type "adb devices".... Does the fact that my PC can see it during ADB Sideload means that the Drivers are installed correctly? what may be the problem then? uff..
Have u tried this
Since you dont mind losing your data, I guess u already did a factory reset, I seriously suggest trying this guide. Read carefully. It worked perfectly for me which was in bootloop after 5.1.1 update.
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-stuck-boot-loop-lollipop-t3098632
I am trying to resurrect my tf101. This is my starting point. Some time ago I installed cm10-20130929-NIGHTLY-tf101 into my tf101 using twrp. That installed fine but in the process something happened and I cannot boot into twrp I can now only boot into CM by holding the power button and volume up. I was not able to install gapps . Also I think my bootloader is corrupted because if I try to boot into it I just get a blank screen. I was able to install the Official TWRP App and can run it but it crashes every time "Unfortunately the app has stopped".
I am about ready to throw this laptop out because I have tried many options on this board and nothing worked. I can connect the tf101 to my computer and I can see it in device manager and I can open the laptop in file manager. I would even be willing to wipe the entire laptop and start from scratch but I don't know enough how to do this.
Any help or suggestions would be welcome.
Hi. First, I'll explain to you that for 10 years I had no contact with flashing phones. I didn't have any problems with the previous models. So I stopped somewhere at the level of the Samsung Galaxy S3-S4. Some time ago I decided that I would bring two Asus tf101s back to life and install a new KitKiss ROM on them. I set to work confidently. Turns out it's not that simple. I can do nothing. Some of the links have expired and the tips seem outdated. I can not upload a new recovery or even root the device. Strange things are happening. First of all, after turning on the device in recovery mode, after some time it goes into system boot and exits recovery. I've tried many ways and I don't understand any of it anymore. In the command line (CMD) it seems to see the device but does not want to respond to any commands, even to "adb reboot fastboot". I can do like this :
1. Ask for simple instructions for a "boy" and current links to the necessary files.
2. Look for someone who will perform a miracle and install the required Android for me.
Will someone help me?