I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Thx Red_81, again. Glad to see u put this here for the i777. Appreciate u sharing this. It should provide some good help for many users. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium
So much easier than trying to explain how to install the sdk and then what commands to run. The only problem is you need to have working drivers.
Sent from my SGH-I777 using xda premium
Red_81 said:
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Click to expand...
Click to collapse
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
lambition said:
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
Click to expand...
Click to collapse
Never mind. I just got it working.
Had to just enter adb command directly. wait-for-device is not working for my phone for some reason.
If you get stuck there again, unplug and plug in the device again.
Sent from my SGH-I777 using xda premium
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Phalanx7621 said:
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Script already does that
Sent from my SGH-I777 using xda premium
Thanks
Thanks i was tinkering with a noria 7" tablet, which hasn't worked right since i got it but for 65 bucks its to be expected, but i used sdk manager to get it to register on my computer as an android adb device and for some reason i tried to turn the wifi on and it crashed and got stuck in a boot loop idk why. like i said hasn't worked right since i bought it. But i did use adb portable like you said to get into recovery mode and it worked great thanks! For other noria users when i figure out how to flash a rom to it i'll start a section here on xda as soon as i figure it out. Thanks again
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
BrockSamsonFW said:
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
Click to expand...
Click to collapse
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
creepyncrawly said:
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
Click to expand...
Click to collapse
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
BrockSamsonFW said:
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
Click to expand...
Click to collapse
It's pretty difficult to recover information from the data partition when the phone is in a state such as you describe. Maybe the developers and technogeeks can do it. I can't. However, depending on where the game saves it's game data, you may be fine. If the game data is saved to the USB memory (internal sd card) then it will still be there once you flash new firmware. Your pictures should also be fine, since they are on the sdcard.
Related
Well, im having some problems going into Download Mode...i have tried lots of different combinations, tryed using virtual terminal, toying with the USB Cable and the battery, any suggestions? Is there some kind of bug that affects phones making them unable to go into Download Mode?
I can get to Recovery just fine, the problem is Download Mode.
What are you running?
Can you describe what you are doing (rather than me list it out if you are already doing it right)
be detailed.
s15274n said:
What are you running?
Can you describe what you are doing (rather than me list it out if you are already doing it right)
be detailed.
Click to expand...
Click to collapse
Well, im running latest CM7 Stock.
I have tried pressing both Vol. Up and Down and connecting the USB. Also tried taking the battery out, pressing both buttoms, connecting USB and then insert battery back. Also tried with the Pwr buttom pressed too, but it just goes into a bootloop in the Vibrant screen, and after i release the Pwr buttom, it goes to recovery.
I also tried using Virtual Terminal, and using "reboot download", but it just does a normal reboot, and goes back to the ROM. Am i missing something?
Have you installed the Nexus S drivers?
Here you go, if not.. from the FAQ:
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you isntalled the SDK
s15274n said:
Have you installed the Nexus S drivers?
Here you go, if not.. from the FAQ:
Q: Where can I get the Nexus S drivers?
A: Download and install the Android SDK here then download "Google USB Driver package, revision 4"
Once downloaded, right click on "Computer", "Manage", "Device Manager", "Nexus S", "Update Driver Software", and point it to wherever you isntalled the SDK
Click to expand...
Click to collapse
Thanks for that, but even after installing that driver and being able to use ADB (thanks to the driver, now i can use adb), the phone still can't go into Download Mode.
Anymore suggestions? Im not using the stock cable that came with my phone because i bought it from a friend, and he was using a BB charger and usb cable, and he gave me those to me.
Bump! Bump! Need some help here!
Now that you have ADB and the drivers... can you now use "adb reboot download" with success?
Do you have odin up and loaded, usb into pc, battery out, plug into phone, holding both volumes insert battery... still nothing?
s15274n said:
Now that you have ADB and the drivers... can you now use "adb reboot download" with success?
Do you have odin up and loaded, usb into pc, battery out, plug into phone, holding both volumes insert battery... still nothing?
Click to expand...
Click to collapse
I have Odin open...but how do i know if its "up and loaded"?
"adb reboot download" doesn't work, neither "usb into pc, battery out, plug into phone, holding both volumes insert battery"...altough, with the phone not connected to the USB, i pressed Vol UP, the Home Buttom and Power, and i was able to enter into "Unknown Upload Mode"...just to mention it.
Anymore suggestions?
EDIT: When i try to into download mode, when the phone turns on, instead of showing the "Vibrant Samsung" screen, it shows a loading circle, and the goes to directly to the "Galaxy S CyanogenMod" screen...that only happens when i try to go into Download Mode.
I just noticed that i didn't state the purpose of going into Download Mode...i want to flash my phone back to stock to flash some ROMs, im kinda stuck in CM7 now...SOOO, if there are others way to flash others ROMs other than flashing stock....
EDIT2: I have a question: I do have a Nandroid Backup of Bionix V1.3.3, should i use that back up? Or would it mess up the phone because of the file system CM7 uses?
Buump!!!!
Sent from my SGH-T959 using XDA App
djluis48 said:
Buump!!!!
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
With all the trouble you seem to be having just buy a jigg. You may need it if you plan on flashing and have such a difficult time getting into download mode.
Sent from my SGH-T959 using XDA Premium App
Here, try this.
1. Take out EVERYTHING from your phone (SIM card, MicroSD card, Battery(make sure USB isn't plugged into your phone when you do this))
2. Plug in the USB cable
3. Hold VOL up and VOL down
4. Put the battery in.
This is the ONLY way I can get into download mode from CM7, so it may work for you (sorry if you tried this method already, I skimmed through the thread, but didn't see this posted).
what happens when you run adb with your phone connected.
do you get #
when you are in shell type "adb devices" or devices can't remeber
you should get the name and serial number of your phone
If you do your sdk is installed properly and recognizes your phone.
then try "reboot recovery"
If you have a voodoo lagfix and
if you are in red recovery on the phone
go to voodoo in recovery and the lagfix menu should come up and you will see a selection for reboot download. Select that and you should see download.
But, if your phone is recognized by adb (see above) and you cannot use the reboot download command in the shell then ... I don't know.
I would check your sdk setup and make sure the phone is recognized.
I just want to point out that I've seen this problem twice and I was able to correct using a full JTAG write to the on board NAND. I'm not saying that's the only way to fix it but in my cases it solved it both times. I spent a few hours before asking the owner if he was ok with giving it a shot and I just made a backup to revert to in case it didn't work, but it worked great. PM me if you are interested in letting me correct yours with JTAG using the same methods...
Otherwise, good luck and please post what solved the problem if you fix it!
Longcat14 said:
Here, try this.
1. Take out EVERYTHING from your phone (SIM card, MicroSD card, Battery(make sure USB isn't plugged into your phone when you do this))
2. Plug in the USB cable
3. Hold VOL up and VOL down
4. Put the battery in.
This is the ONLY way I can get into download mode from CM7, so it may work for you (sorry if you tried this method already, I skimmed through the thread, but didn't see this posted).
Click to expand...
Click to collapse
Thanks for posting this method, but i had no luck with this one...
gongshow said:
what happens when you run adb with your phone connected.
do you get #
when you are in shell type "adb devices" or devices can't remeber
you should get the name and serial number of your phone
If you do your sdk is installed properly and recognizes your phone.
then try "reboot recovery"
If you have a voodoo lagfix and
if you are in red recovery on the phone
go to voodoo in recovery and the lagfix menu should come up and you will see a selection for reboot download. Select that and you should see download.
But, if your phone is recognized by adb (see above) and you cannot use the reboot download command in the shell then ... I don't know.
I would check your sdk setup and make sure the phone is recognized.
Click to expand...
Click to collapse
I don't the red recovery, i have the orange one, so no voodoo options for me there.
And ADB its working fine, if i type "adb shell" i get the "#", if i type "reboot recovery", the phone reboots and go to recovery, but if i try "reboot download", the phone just reboots like i just said "reboot".
I guess i will have to build a jigg...i was trying to avoid that trip to the electronics store since its really far away from where i live, and i don't have a car right now. If this doesn't work, then i MIGHT give connexion2005 a shot, but i really don't like the idea of JTAGing, but i have seen some cases of JTAGing in wich the phone was succesfully brought back to life.
Ask for a replacement from t-mobile and they will give you a new one free, just mess it up or something and theyll give you a replacement.
Just download the app easy reboot on the market. Plug in usb and click download mode.
Sent from my SGH-T959 using XDA App
Im having the same problem.. I cant get into Download mode.. But I can enter recovery mode... How can I go to another rom? or stock?
Im really scared right now
Can I go to another rom just by flashing it with the recovery?
ivan0550 said:
Im having the same problem.. I cant get into Download mode.. But I can enter recovery mode... How can I go to another rom? or stock?
Im really scared right now
Can I go to another rom just by flashing it with the recovery?
Click to expand...
Click to collapse
Which ROM are you using?
all of u guys having the problem getting into download mode, are ur phones hardware locked as in meaning they cant get into dl mode by the 3 button combo?
Another option, put a 2.2 rom on your sdcard.
2. Flash a 2.2 kernel in sgs kernel flasher
3. It will reboot and then pull battery
4. Go into recovery with three button method
5. Flash a 2.2 rom
6. It probably will not boot because of the filesystem but from there you can go into download mode without jig. A lot of people have trouble getting into download mode from CM7, but once you are on a normal samsung rom it is easy.
If this does not work do the following:
Download the attached file at the end
Put it on the root of your sd card
Go into CWM and click apply sd card:update.zip
You should be in CWM 2.5.1.2
Now you need to flash a 2.2 rom
Finally, you should be able to get into download mode
Another method if all else fails
Download this 2.2 rom http://www.mediafire.com/?whl91yw8s3bf1jf This is m11, Jellette's rom, I just modded it so you can flash it from CWM 3, CM7's recovery.
Now, reboot it might or might not work, if it does not pull the battery and go to download mode with normal three button method.
IF I helped you click thanks
Im trying to unlock Sony xperia sola rite now.... it wont stay on fastboot mode ( volume up + plug usb) when i press volume up, the light strip turns blue for a second or two, but then goes into charging while shutdown mode... I chek *#*#7378423#*#* -- Service info > Configuration > Rooting Status it says - YES// I try USB debugging ON and OFF... I try to stay on fastboot with my home pc windows 7 and my notebook windows vista..Battery 95-100% charged... What i do wrong?
Do you have installed drivers properly?
Try reinstall drivers and try different USB port.
xbeda said:
Do you have installed drivers properly?
Try reinstall drivers and try different USB port.
Click to expand...
Click to collapse
how can i install drivers without connecting device?
I solved the problem)
1) Open device manager in windows
2) Connect usb cable to your phone pushing vol up button
3) Device manager will show you fastboot device for 2-3 sec (before the phone go to charge mode) Right click on fastboot device and install drivers from C:\Android\sdk\extras\google\usb_driver
4) Reconnect usb cable pushing volup button
I have the same problem but I dont know if cuz my PC is way too slow. I dont even have a chance for it to show up But I know it connected cuz of the alert sound.
---------- Post added at 08:50 AM ---------- Previous post was at 08:27 AM ----------
Haha I solved my problem by installing the driver in safe mode. Things went much quicker here )
The solution that worked for me was:
Keep the Device Manager open
Connect the phone and quickly choose to change driver
Disconnect the phone again (because it goes into normal mode)
Choose to install a driver from the computer, choose "All devices" and "have disk".
Browse to the folder with the .inf
Now, before clicking Next, connect the phone again and quickly hit Next.
I think it took me two hours of googling and trial before I could finally get a custom ROM installed...
Nerre said:
The solution that worked for me was:
Keep the Device Manager open
Connect the phone and quickly choose to change driver
Disconnect the phone again (because it goes into normal mode)
Choose to install a driver from the computer, choose "All devices" and "have disk".
Browse to the folder with the .inf
Now, before clicking Next, connect the phone again and quickly hit Next.
I think it took me two hours of googling and trial before I could finally get a custom ROM installed...
Click to expand...
Click to collapse
Do you know u are GENIUS !!!
i have been trying to get my phone in fast boot mode for the last 3 weeks then then i changed the "System Varibales" in my Windows & ( 64Bit) and then tried your above method AND ... volaaaa it works ... in a flash it works then the pone is in Fastboot mode .
( Device : Sony Xperia Sola 2012 without upgrade to .654)
Don't call me the genius, I found the solution using google
I just wrote a quick summary of it.
Nerre said:
I just wrote a quick summary of it.
Click to expand...
Click to collapse
...which was enormously helpful. Thanks!! (Can't push the thanks button as I don't have enough posts yet.
BTW, I used the method with the Xperia Go, so obviously the method is not limited to a particular model.
It works
Really helpful!
Hey
I can't even know where will the fastboot device appear to change driver. What can I do? My sola goes in charge mode very quickly I plugged my usb cable in almost 100 times and tried everything.
Okay, I'm totally lost. When I hold volume down button "s1boot download" appers in device manager, but it can't install a proper driver. I know I need s1boot fastboot and hold volume up button but it doesn't appears. Only the portable device with an H:/ partition
Make sure phone is OFF
While plugging in the USB cable, hold and keep holding the UP VOLUME key
You will hear a system sound played
Do all these while you have Device Manager on screen
Exclamation mark appears on the ADB driver icon
Chose the option to look for the driver in your hard disk - point to where the drivers are.
If using Win8 then you need to disable signing of drivers first (search on net how to)
So far you managed to do this or not?
ricstc said:
Make sure phone is OFF
While plugging in the USB cable, hold and keep holding the UP VOLUME key
You will hear a system sound played
Do all these while you have Device Manager on screen
Exclamation mark appears on the ADB driver icon
Chose the option to look for the driver in your hard disk - point to where the drivers are.
If using Win8 then you need to disable signing of drivers first (search on net how to)
So far you managed to do this or not?
Click to expand...
Click to collapse
Hey, nothing is working for me. I did the steps above, but with no chance to install any driver. At the driver manager, the s1boot fastboot-thing is showing up for some seconds and then disappear. i can't change the driver or install the new one.
Any suggestions? I want to change to cm9 so much, because the stock rom really sucks...it is slow and buggy
Edit: I found this post http://forum.xda-developers.com/showthread.php?t=1554632 and it works for me!!!
Edit 2: It seems, that you have to do this steps everytime you flash the boot.img to the phone.
I did everything. I installed the driver but when I hold volume up while plug in usb, the led does not turn to BLUE. It turns pink or purple, some kind of colour. What should I do guys? I've gone mad.
Thanks
Nerre said:
The solution that worked for me was:
Keep the Device Manager open
Connect the phone and quickly choose to change driver
Disconnect the phone again (because it goes into normal mode)
Choose to install a driver from the computer, choose "All devices" and "have disk".
Browse to the folder with the .inf
Now, before clicking Next, connect the phone again and quickly hit Next.
I think it took me two hours of googling and trial before I could finally get a custom ROM installed...
Click to expand...
Click to collapse
Thanks a ton!!!
i wasted my whole day trying it!
just hit this thread!!
will reply if it works!
---------- Post added at 06:32 PM ---------- Previous post was at 06:10 PM ----------
srivmanu said:
Thanks a ton!!!
i wasted my whole day trying it!
just hit this thread!!
will reply if it works!
Click to expand...
Click to collapse
Does't work!!
help someone??:crying::crying:
Doesnt work for me either. I tried everything for hours, but i only see a purple LED for a few seconds and then the phone mode changes into charging.
All drivers are installed.
Flashtool doesnt recognize the Sola either.
Is there a way to flash a recovery without having the Sola bootloader unlocked?
Greetings
still no fastboot
device manager opened
phone off, holding vol. up plugging in usb
NOTHING happens on computer no sound, device manager doesn't refreshes, no purple led on the phone, just enters charging quickly
tried another usb port
tried to enter fastboot from flashtool,
tried to enter with command adb reboot bootloader / adb reboot fastboot
NOTHING happens just reboots normally
So I don't have a clue what's going on there, may the fastboot disappeard or broken?
BUT I used the fastboot for a couple weeks ago in this computer in this usb port, since that I tried some rom does it matter?
BL Locked
Win7 x64
pl explain in detail
Nerre said:
The solution that worked for me was:
Keep the Device Manager open
Connect the phone and quickly choose to change driver
Disconnect the phone again (because it goes into normal mode)
Choose to install a driver from the computer, choose "All devices" and "have disk".
Browse to the folder with the .inf
Now, before clicking Next, connect the phone again and quickly hit Next.
I think it took me two hours of googling and trial before I could finally get a custom ROM installed...
Click to expand...
Click to collapse
pl explain in detail.im a novice and i want to update to ICS in ma Sola....but fastboot driver installtion failed in my W 7 (64 bit):crying::crying::crying:
Solution
For those who still dont get it to work by "Nerre's" method.
The procedure will be same. You have to download latest android_winusb.inf file. I couldnt get it to work bcz of this. I was using the file from sony site. It was giving me some certificate error. Then I used the lates file downloaded from sdk kit. Then this procedure worked.
Make sure to choose "Android Boot loader Interface" after you select ...winusb.inf file. Then before clicking next, reconnect your device in fastboot mode.
Hope this helps someone.
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
JNiels1980 said:
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
Click to expand...
Click to collapse
When you press up on the USB icon and it freezes that it normal.. This is fastboot mode.
You now must access it over a PC after installing the naked drivers.. If it is not showing on your PC then either try a different PC or your cable is faulty.
Thanks for the quick reply.
I tried once more to enter fastboot. Same result.
But when I disconnected my usb cable to connect it to an other computer, suddenly I got this message on my tablet:
"Starting Fastboot USB download protocol"
This message didn't show up before.
I plugged the tablet back to my pc, but still no device detection in device manager, even when refreshing (So I can't install naked drivers, as it is not recognized).
My computer is a Windows 8.1 system.
I restarted my tablet again, (after disconnecting it from my pc) and followed the procedure to enter Fastboot again.
I waited for the message "Starting Fastboot ..." and then I connected the cable to my other pc (Windows 7 system)
Same result as on the Windows 8.1 machine, not recognized
You say it could be that my cable is broken. Maybe, but it's a strange coincidence that this happened when switching from ICS to JB.
I know JB for the tf201 is been out a long time, and I updated since I could. So over time, maybe my cable could be broken now. But I'm sure I had this problem (not recognizing) since then, because right after updating I wanted to do some things with ADB and so I found out I had this problem.
Hi there,
yesterday I tried to root my new Tablet Z (16GB, LTE, Model: SGP321, Firmware: 10.4.B.0.569) and it doesn't start since then.
I used an ubuntu live CD for all these tasks because fastboot doesn't work on my win 8.1 and my debian wheezy didn't have the libc-dev needed in its repositories (didn't want to mess with packets that weren't yet integrated into my OS).
What I did:
unlock the bootloader according to http://unlockbootloader.sonymobile.com/instructions
I followed the instructions here: http://forum.xda-developers.com/xperia-z/general/how-to-root-10-4-b-0-569-t2590781
a few annotations to this:
the firmware rar didn't include a "Recover.zip", so I used the boot.img directly inside the firmware rar
although sony and this CM tutorial use the "-i" parameter of fastboot, I didn't use it because it wasn't used by the tutorial
after I did the "fastboot reboot" step, the device wasn't listed anymore when typing "fastboot devices", which, I think, is okay since the device should restart then.
I think it didn't really restart, because the LED on the side glew red.
I tried to turn on the tablet but it didn't do anything (the LED kept glowing red).
I tried holding vol up and power for a few seconds (until the LED blinked first once and then three times) but the tablet wouldn't do anything except for the LED glowing red. at somepoint, the LED would turn off (I think that happened when I hold vol up and power for more than 10 sec).
I was able to let it glow red again by pressing vol up and power again and release the vol up button before the power button.
I also tried to use the PC companion on my windows machine to repair the tablet but the tablet wasn't even recognized (either using the fastboot-procedure by holding vol up while connecting the tablet nor normal plugging in...)
any ideas what I could do next?
Same Problem!
Hey wullxz!
I have the same problem. Red LED most of the time, and I cannot make ANY USB connection to the PC. The tablet won't show up in the device manager. So obviously cant use flashtool, nor PC companion. Ive tried all this volume up and down button stuff, but simply cannot get it to show up on the computer.. Tried a different USB cable as well.. Same issue. The USB port is definitely not broken. Its brand new..
Have you found any solution ? Or anyone else? Mine just got back from Sony Repair.. they wont fix it cuz they detected that Ive tampered with the original software.... meaning Warranty Lost!
Great!
hi,
i also sent mine to sony for a repair. i wrote that i did a firmware update and the tablet wouldn't boot afterwards.
i didn't try the bootloader-unlock again afterwards.
Help Needed!
Tablet Z with unlocked bootloader and rooted 10.1.C.0.370
My issues occured after a downgrade to 4.1.2.
I CAN:
1) Start my tablet, everything normal...
2) Charge my tablet
3) Go into safe mode
4) Go into fastboot mode (solid BLUE LED)
5) Use the memory card and use root apps (maybe this could help restore?)
I CAN NOT:
1) Get my PC to recognize that a USB device is connected. Neither in Mass Storage mode, Media mode, nor fastboot mode.
- Tried with several cables and computers (this is not a driver issue, since it won't show up at all in device manager)
- Flashtool obvious;y says, no device connected
2) Get in to flashmode: device blinks red for about half a second, then green for half a second, and then LED is off. Nothing recognized via USB on PC
3) Get into recovery mode
4) Update over WIFI (fails because unlocled bootloader I suppose)
Any help would be greatly appreciated!
i think you should open a new thread for your problem because it seems like it's not really similar to my issue.
you should get more/better replies in an own thread.
Oki
wullxz said:
i think you should open a new thread for your problem because it seems like it's not really similar to my issue.
you should get more/better replies in an own thread.
Click to expand...
Click to collapse
Oki thnx, will try that!
centinel_x said:
Tablet Z with unlocked bootloader and rooted 10.1.C.0.370
My issues occured after a downgrade to 4.1.2.
I CAN:
1) Start my tablet, everything normal...
2) Charge my tablet
3) Go into safe mode
4) Go into fastboot mode (solid BLUE LED)
5) Use the memory card and use root apps (maybe this could help restore?)
I CAN NOT:
1) Get my PC to recognize that a USB device is connected. Neither in Mass Storage mode, Media mode, nor fastboot mode.
- Tried with several cables and computers (this is not a driver issue, since it won't show up at all in device manager)
- Flashtool obvious;y says, no device connected
2) Get in to flashmode: device blinks red for about half a second, then green for half a second, and then LED is off. Nothing recognized via USB on PC
3) Get into recovery mode
4) Update over WIFI (fails because unlocled bootloader I suppose)
Any help would be greatly appreciated!
Click to expand...
Click to collapse
let it charge to 100%, check for flashmode drivers installed and then try attaching it to pc only when flashtool asks you to do it.
Rootk1t said:
let it charge to 100%, check for flashmode drivers installed and then try attaching it to pc only when flashtool asks you to do it.
Click to expand...
Click to collapse
Hey thanks for your reply... It wont go into flashmode... Theres something fundamentally wrong.. I cant figure out what... I leave it plugged in for 48 hours..but it doesnt really get full.. the most Ill get the orange LED.. like 50%... now its on since about 12 hours.. no LED on at all... strange..
But yea.. no flashmode... Nothing showing up when connecting the USB cable... nothing in device manager..and therefore flashtool sees nothing!
SOLVED
Problem solved! I can't believe it. Two bad(?) USB cables. Bought a new one, charges fine, flashmode fine. Flashed stock ROM.
However the Camera still doesn't work. Maybe the problem of the cable inside which may have come loose!
I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.