i would recommend adb for everyone is a simple step. for the reason i have the Samsung galaxy s, and for some reason i couldn't boot into recovery it would just boot up all the way in to a black screen. because i tried applying the lag fix twice but i dont believe it works doing it twice you need to remove it if you want to apply a different method. but yea i was stock when ahead settled up adb boom adb reboot recovery even though my screen was black, but still had usb debugging mode on went right ahead into recovery and then i could do a wipe to pas that black screen. i do use clockworks recovery but i use the app so i was stock on the stock recovery so couldn't do a Nan recovery.
this is were i found the adb settup http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ found it posted by wbexpress
Check out AdbWireless from the market
Very Cool.
http://www.androidzoom.com/android_applications/communication/adbwireless-10_jvai.html
cool adb wireless i should try that.
rhonal89 said:
i would recommend adb for everyone is a simple step. for the reason i have the Samsung galaxy s, and for some reason i couldn't boot into recovery it would just boot up all the way in to a black screen. because i tried applying the lag fix twice but i dont believe it works doing it twice you need to remove it if you want to apply a different method. but yea i was stock when ahead settled up adb boom adb reboot recovery even though my screen was black, but still had usb debugging mode on went right ahead into recovery and then i could do a wipe to pas that black screen. i do use clockworks recovery but i use the app so i was stock on the stock recovery so couldn't do a Nan recovery.
this is were i found the adb settup http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/ found it posted by wbexpress
Click to expand...
Click to collapse
I had the same problem yesterday, would not boot past the Galaxy S logo. I pulled the battery, placed back in, pressed the volume up and down while pressing the power button, got into recovery and wiped/reset.
Fixed!
I would be thrilled if there would be a way to flash new firmware on the android devices via adb without the need of ODIN then I will not need to use Windows PC at all
I guess I'm just bad. I've had the G1 since it came out and well I've done everything via console and I've yet to even learn how to use ADB.
I've always used Terminal Client and just typed reboot recovery opposed to vol+/- and power.
I do highly encourage everybody to learn ADB, but I'm guessing I'm just to lazy to install drivers and the SDK.
@OP Nice find on those instructions too.
Related
In an effort to get back to stock I took things a step too far and now have a phone that won't power on. I had successfully rooted the phone and installed Rom Manager and flashed the clockwork recovery and immediately created a nandroid backup. Sometime later my phone started acting funny... usb connected/disconnected events when it was not plugged in, crashes, etc. I felt confident that this was a hardware issue (started after my daughter chewed on it when I wasn't looking). Anyway, I followed the instructions here in the dev forum (True Stock 2.1 firmware for vibrant) for the vibrant to get back to stock ( I apparently can't post the link because I'm new...) . So that I'd be able to try and get it replaced. I kept noticing that no matter how hard I tried clockwork was still installed... then I did the bad thing. I should have known better, but I made the rookie mistake and deleted the clockwork folder from the internal flash. I don't know what possessed me to do it, but I did. Since then the phone doesn't seem to boot. I can get it into download mode to flash images from odin (battery out, battery in, volume up + volume down, connect usb and download comes on). And after a successful download it seems to restart ok. But if it crashes (which it is now prone to do) or is powered off it won't boot after that. Worse I can't get to the stock recovery either.
I'm hoping that someone who has a nice rooted stock phone with clockwork installed can just help me get a copy of that folder back and everything will be fine... if not I may just have to see if playing dumb with tmobile will get the phone replaced as is...
Thanks in advance for any help.
Are you talking about stuff in /sdcard? If so, that won't effect the boot. You could delete everything in there and not change anything. Some apps might not work as you will have deleted their data, but if you're flashing a stock ROM with Odin, that's fine.
Enable debug mode in the settings and use "adb reboot recovery" at a command prompt. That should get you to the stock recovery. Try a factory reset from there, that might help. If not, delete anything in /sdcard that's not supposed to be there and swap with TMobile as it sounds a hardware issue at that point. Don't forget to keep your external SD card if you've replaced it.
Is USB debugging on?
When you get the phone up, can you connect to it via ADB and then adb reboot recovery or adb reboot download?
Thanks for the suggestions. I did get the sdk installed and used adb to reboot into normal recovery, so it's not completely boned. Since I could use adb for resets I went ahead and followed the rooting process again and reflashed clockwork. The phone still won't boot on it's own. I'm starting to think whatever was going south with the hardware has continued to get worse. I'm going to use odin to get back to "true stock" again and try to use adb to reboot into recovery and do a factory reset suggested above and see if that helps.
Thanks again.
I went back to stock with odin, ran the factory reset, and still can't power up normally or into recovery. I can get into download though, load with odin, come up normally after the reset. I'm going to try giving it back to Tmobile in it's refusing to power up state and see if I can get them to swap it. It's as stock as I can make it so the problem should not be mine.
Thanks again for the help.
FWIW - i just installed Rom manager this morning, the premium version, and today experienced 5 force closures, one on google maps
before this i've had maybe one FC some 2-3 weeks ago - and like you i did a clockworkrecovery backup or nandroid backup
I rooted the tablet and it updated fine. I then reboot it and it is now stuck in boot loop. It says bootloader version unknown when I press power and volume button. What do I do?
Update. I have been able to successfully make my tab bootloop three times and three times have brought it back to life. All three times it has been because of an app that I guess is not compatible with 3.1. Because of my low thread post count I can't provide links or post into the development forum but my method has worked all 3 times.
A little background. First time I hadn't changed recovery and it was a bit easier. Second and third times I had cwm recovery and it was harder because adb wasn't recognizing my tablet.
First you need to have adb installed into your computer. I installed the sdk and then added the adb option. I then went into this post in the development forum: Re: [Solution] HC 3.1 OTA Difficulties 13% + Stock ODIN. In that post you'll find the Odin application for your computer and the appropriate PDA file for your tab. The PDA file contains the stock recovery, bootloader, and rom.
Whether you have stock recovery or cwm the next instructions are the same.
1. Connect the tab to computer.
2. Holding power button and volume down button, get into screen where you can choose fastboot or download mode. Choose download mode.
3. Once in download mode, on your computer open the Odin application.
4. Where it says PDA file, click the browse option to look for the PDA file you downloaded. Open it and it will be listed in the PDA section. Also the box next to PDA will be checked. Don't change any other settings.
5. Now you can press the button to run Odin. Don't touch tablet until it's done.
6. Now you can try rebooting it but it will still bootloop. Difference now is that you can adb into it.
7. With tab connected, go into cmd mode on your computer and type: adb reboot recovery
8. The tablet should reboot into stock recovery. From there wipe data and cache.
9. Reboot tablet and it should work! The tablet will be reverted back to 3.0.1. Just run the update again and enjoy.
Couple of notes. I tried the fastboot method mentioned in some posts but it never worked for me. This method that I've done has been flawless for me. I do have I/O version so I'm not sure if it is different from retail version. I think bootloops occur because some apps are not ready, stable, or compatible with 3.1. Something in the bootloader and recovery has changed in 3.1, whether it is changed via the apps or the update itself I'm not sure. I do know that the problem apps work great in 3.0.1, never causing bootloops, thus my conclusions.
Same thing happened to me. Fastboot -w did the trick. It wipes the tablet though.
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Help needed Samsung galaxy tab 10.1 stuck in boot loop
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
saviressej said:
Thanks. It's weird. My tablet was rooted but I hadn't changed anything. I ended up connecting it to my pc, adb'd into recovery. I wiped cache and data and it eventually worked. Only thing was that it went back to 3.0.1. I then did the update again and now it's working flawlessly with 3.1
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
How did you ADB it while it was in a bootloop?..
I'm stuck with this same issue! Everything was fine, I was on version 3.1 and I had rebooted it several times. Then one time it just got stuck on a bootloop and I can't figure out how to fix it. This is the google i/o version and I haven't done anything to it other than update to version 3.1.
I've been googling for an hour or so, but I have no idea what i'm suppose to be looking for. =\
you can recover.
i have posted detailed instructions in the OTA thread on xda.
sramasub said:
Hi,
I faced a similar situation, I upgraded by Samsung Galaxy Tab 10.1 to HC 3.1 and it had been working fine .
Unfortunately I did not use it for the past 2 days, the battery drained out and after that I tried to recharge and start itup.
It goes in a boot loop .
And also display's Entering upload mode, cause undefined .
Is fastboot the only way to recover the system now .
Click to expand...
Click to collapse
+1, i have the same problem. drained battery, recharged, stuck in boot loop. also got the "entering upload mode; cause undefined" message too.
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
_avatar said:
I experienced the "upload mode / boot loop" problem a couple days ago and wrestled with it for hours. I finally found a combination of things to do that would allow me to enter fastboot to fix the issue, see the following post:
http://forum.xda-developers.com/showpost.php?p=14832831&postcount=122
Some of the steps may not be required, but what I listed should get you into the bootloader without issue. Once inside, simply do a "fastboot -w" to fix the bootloop. Interestingly, after doing a fastboot wipe I am now able to enter the bootloader without all of the complicated gymnastics listed in my post above. It doesn't quite make sense to me, but it's certainly the case.
Click to expand...
Click to collapse
Yeah, I found your post a couple days ago, but couldn't get it to work. Once plugged into the wall charger, I couldn't get the charging icon to show up. I've tapped the power button, held it down for half a second, a full second, several seconds... it either does nothing, or tries to boot up.
I was able to get into Odin3 download mode and flash a ROM (see this thread: http://forum.xda-developers.com/showthread.php?t=1130216#2), but now my USB doesn't work and adb won't recognize it, so as a development device it's not very useful to me. I can't seem to get into the bootloader so I can't flash with adb or fastboot (when I boot into USB mode, adb doesn't recognize the device). I need to figure out how to flash an original I/O image, but can't seem to figure it out...
I've also had some difficulty getting to the "charging" screen, the trick is to be patient. Make sure the device is really off, plug it in, and walk away for a good while -- like 5 minutes.
When you say you're able to get it into USB mode what does that mean? Sounds like you are actually able to get it into fastboot mode. What operating system are you running? On my Mac the fastboot binaries I found floating around the net didn't work, I had to compile one from source. If you're able to get into fastboot mode but it's not detecting your device, and you have a Mac, I can send you the version I compiled from AOSP and you can try that. Let me know...
Try this...
http://forum.xda-developers.com/showthread.php?p=14791689#post14791689
Works for this guys.
I have a solution for the bootloop in my first post.
Sent from my GT-P7510 using XDA Premium App
I had a similar problem. Looks like Clockwork recovery can sometimes trash your /data partition and its format/wipe option won't fix it. I recovered by booting into stock recovery and formatting /data from there. Be forewarned that you'll lose your "sdcard," which really lives on /data.
Nice guide, thanks!
I have installed custom recovery using GooManager but i'm unable to really get in it, yes it was installed but I don't get in.
I have tried with connecting the usb cable to computer and entering fastboot commando's but everything just gets me at a black screen.
I read there are more problems with the recovery on Nexus 7, but I have followed many instructions here but still i'm not able getting in.
I used the Nexus 7 toolkit to.
DexterMorganNL said:
I have installed custom recovery using GooManager but i'm unable to really get in it, yes it was installed but I don't get in.
I have tried with connecting the usb cable to computer and entering fastboot commando's but everything just gets me at a black screen.
I read there are more problems with the recovery on Nexus 7, but I have followed many instructions here but still i'm not able getting in.
I used the Nexus 7 toolkit to.
Click to expand...
Click to collapse
You can get in to recovery using a terminal, if you are rooted.
Su
Reboot recovery
If you not rooted, boot into bootloader and then choose recovery
Excuse the capitalization
angellsl said:
You can get in to recovery using a terminal, if you are rooted.
Su
Reboot recovery
If you not rooted, boot into bootloader and then choose recovery
Excuse the capitalization
Click to expand...
Click to collapse
This also not worked, it resulted into an black screen after the Google boot logo. And when I boot into the boatloader I get the same.
Can you describe exactly what you do?
Also, what happens when you reboot while holding both top and bottom button (have it plugged into computer the whole time to avoid potential bugs). Are you able to get into fastboot then select recovery?
I have used GooManager to put recovery on it and I rooted with Nexus toolkit. I tried rebooting into recovery using GooManager and I tried with commando that was said here.
I do get into fastboot when pressing powerbutton and both vol up and down together, but when I wanna enter recovery this way it won't work and will end up a black screen.
Are you by chance connected to USB when you try to enter the recovery. Hook up and give it a try and let me know
** I reread and saw you already tried it. Was worth a shot
Yes I connected the tablet with usb but it resulted in the same and GooManager said it installed the recovery, I also got a folder off it on tablet but its empty. I also tried rebooting into recovery with Nexus 7 root toolkit v1.5.3 but after the Google logo dissapears de screen stays black and I don't see any recovery.
Are you sure you flashed the recovery? It seems it's not in there.
You can try flash it again, but don't use the toolkit. Use the command line instead.
Just make sure the recovery is made permanent.
Before you flash again, you can also check if there is a recovery img under /.
angellsl said:
Are you sure you flashed the recovery? It seems it's not in there.
You can try flash it again, but don't use the toolkit. Use the command line instead.
Just make sure the recovery is made permanent.
Before you flash again, you can also check if there is a recovery img under /.
Click to expand...
Click to collapse
Okay I will tired this tonight when i get back home. Which recovery can I best flash?
DexterMorganNL said:
Okay I will tired this tonight when i get back home. Which recovery can I best flash?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=28061076
Above is a good one
angellsl said:
Before you flash again, you can also check if there is a recovery img under /.
Click to expand...
Click to collapse
I just checked, I don't see any img there.
I did what was said but again got an black screen and there didnt show any recovery up.
http://forum.xda-developers.com/showthread.php?t=1766475
I was able to flash an other kernel using this root toolkit.
DexterMorganNL said:
I just checked, I don't see any img there.
I did what was said but again got an black screen and there didnt show any recovery up.
http://forum.xda-developers.com/showthread.php?t=1766475
I was able to flash an other kernel using this root toolkit.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=31508537
There is some big in the boot loader, try to reboot your boot loader using the link above
angellsl said:
http://forum.xda-developers.com/showthread.php?p=31508537
There is some big in the boot loader, try to reboot your boot loader using the link above
Click to expand...
Click to collapse
Black screen again, I see no recovery, but it goes past the the Google logo but then stays black.
It seems recovery is on it because I have flashed a kernel and made an backup but that I did using Nexus Root Toolkit. Do you think my Nexus 7 might have the backlight off when its booting in recovery? As I got the backlight bug in Android to and that is why I turned off auto brightness.
DexterMorganNL said:
Black screen again, I see no recovery, but it goes past the the Google logo but then stays black.
It seems recovery is on it because I have flashed a kernel and made an backup but that I did using Nexus Root Toolkit. Do you think my Nexus 7 might have the backlight off when its booting in recovery? As I got the backlight bug in Android to and that is why I turned off auto brightness.
Click to expand...
Click to collapse
Can you see a Google in the middle and a lock icon at the bottom? Before it turn back.
angellsl said:
Can you see a Google in the middle and a lock icon at the bottom? Before it turn back.
Click to expand...
Click to collapse
Yes i can see that Google in midle and unlocked icon and after that it turns black.
There is a stock recovery under systems on the bottom I had to rename that to .bak before I could get my recovery to work.
I think I already figured it out, recovery is installed but my Nexus 7 got the auto brightness issue to, so that is what must be happen the backlight is turned off and that must be why I can't see the recovery.
Because it works accualty. Now I don't know is it a software bug or do I got a faulty Nexus 7, i'm going contact Asus about.
EDIT
I got an replacement and now everything works fine, i also get into recovery so I guess my guess was right, the screen just went black.
Hey all, I figured it was time to make a post and see if anyone could help figure out what I'm missing.
So I recently got my G2 and rooted it, then I installed Team Win Recovery Mod (on accident, actually. Was intending to install Clockwork, but figured it wouldn't hurt anything and it was working fine). Anyway, moved on to install Cyanogen Mod and gapps following the usual factory reset -> flash from /sdcard/ approach. Unfortunately on reboot, it went into fastboot mode.
Since then I've read a ton of stuff about fastboot, and I've reflashed recovery, boot, and system a dozen times, but I'm still stuck in fastboot mode. I've grabbed the CWM for LG G2 (AT&T) from http://www.clockworkmod.com/rommanager and the latest stable Cyanogen Mod from http://wiki.cyanogenmod.org/w/D802_Info. Sadly everything I've seen just tells me to do what I did - reflash recovery and tell it to reboot. I've also tried the "volume down + power until logo, then release and re-hit" method of getting into recovery mode, but the logo is present for literally less than a second, so I just end up back in fastboot.
Perhaps I need to find an flash a stock OS first? The thread on returning to stock firmware scares me :/ http://forum.xda-developers.com/showthread.php?t=2432476 Edit: I gave in and tried playing with this anyway. No good, I can't get the phone to enter "download mode", no matter what I do, it reboots into fastboot.
Any ideas?
Edit: The flash method I used for TWRM: http://forum.xda-developers.com/showthread.php?t=2449670
Edit2: This seems possibly relevant. When I do "fastboot devices", I get "? fastboot". So something is wonky in terms of its detection. But all the commands seem to be getting executed fine...
Edit3: Finally a potentially useful piece of info: If I flash the boot image extracted from the Cyanogen mod zip, then run "fastboot continue" I get "ERROR: Getting device tree address failed". Which is the same message I get when trying to remotely run a boot image without flashing it. Possibly related to the "?" in the "fastboot devices" listing above? I switched to Koush's Universal Adb Drivers, but no change.
Pretty please?
I find it hard to believe I could manage to brick a 2 week old phone just by following the guides posted here
Well, I still have no clue what went wrong, but I was finally able to make use of the reset to stock thread. It was strange and scary and at no point did I really have any idea I was hitting the right buttons, and at the end it said it failed... BUT it rebooted me into a fresh install, apparently even unrooted! My problems along the way appear to have entirely been related to actually getting the phone *into* download mode since I couldn't get it to actually turn off. Once it ran itself out of battery and turned off, I was able to enter download mode while reconnecting it to power.
No to decide if I want to try installing a custom ROM again, or take this as a sign...
Who am I kidding. *re-roots phone and pulls up the mod threads*
Hey all, I recently flashed a new rom on my phone, which required me to factory reset my ticwatch I'm order to reconnect.
Upon doing to the first time, everything seems to have gone well, but had trouble connecting to the device. So I ran another factory reset. Since that one, I've been stuck in a boot loop.
I see the "device software can't be checked for corruption" screen for about 20 seconds, and then it vibrates, screen turns off, then I see the same screen again. And so on.
I tried letting the battery go to nothing and trying again, seems to be the same issue. I'm letting it charge and bootloop for now in case maybe I just don't have enough juice to make it through boot.
It is rooted, with custom ROM (followed a guide on this forum somewhere about half a year ago, was running great) and TWRP installed (at least it was, I've been unable to get to the recovery screen since the boot loop started). Cannot see it in adb ever in this process.
Anyone have any other suggestions? I remember the Samsung notes had a special USB tool that would bridge a couple pins to immediately go to recovery, is there a similar option here?
Can you get in usb mode,or fastboot or recovery maybe?There is solution..dont worry.I ghuess adb dont work,but you cant go to fastboot mode and boot twrp image and get in twrp recovery..in twrp recovery you need backup file..If you cant do that,we are going to another solution..
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
nieminen432 said:
Yeah, I can't - via any combination of button holding - get into any booted mode. No recovery, no fastboot, nothing. If anything, some buttons seem to make it circle boot faster .
Click to expand...
Click to collapse
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
KristijanKG3 said:
,Yeah tough situation,and when you connect it to pc in that "broken mode" -boot loop and open adb shell on pc ,comand adb devices or fastboot devices,does it show device?When you screwed boot and you have twrp there must be option to get in twrp.One trick more go to manage devices in pc find your device if unknown you right klick on it,update drivers,manually,and then choose android,then android adb install device.
Click to expand...
Click to collapse
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
nieminen432 said:
I tried adb devices, but not fastboot devices, thanks for the idea, I'll give it a go.
Click to expand...
Click to collapse
Maybe it wont work,but if doesnt,we figure out something..Bootlop is not the end of your device..
No go on either command. Nothing shows up.
I'm half wondering if it's my battery at this point. I think I'm getting a new watch for Christmas anyway, so not a huge loss. But happy to keep trying if anyone else has any ideas.