i have a AT&T Samsung Galaxy SII SGH-I777 and it got stuck in a bootloop when i tried to unroot back to ICS, also i dropped the phone in water a week ago and the volume up button does not work so i cant get past the warning menu to get to the download screen! please help thanks in advance
Sloth Nuggets said:
i have a AT&T Samsung Galaxy SII SGH-I777 and it got stuck in a bootloop when i tried to unroot back to ICS, also i dropped the phone in water a week ago and the volume up button does not work so i cant get past the warning menu to get to the download screen! please help thanks in advance
Click to expand...
Click to collapse
1 word my friend,"FUBAR"!!You need insurance for things like that.Next time something like that happens,remove the battery and shake the excess water from the phone,then immediately blow dry it for about 1 minute,then drop it in a bag of rice for a day,it will soak up all the moisture in the phone.
Sloth Nuggets said:
i have a AT&T Samsung Galaxy SII SGH-I777 and it got stuck in a bootloop when i tried to unroot back to ICS, also i dropped the phone in water a week ago and the volume up button does not work so i cant get past the warning menu to get to the download screen! please help thanks in advance
Click to expand...
Click to collapse
can you use adb to boot into recovery and flash something from there?
Or are you on stock recovery?
orangekid said:
can you use adb to boot into recovery and flash something from there?
Or are you on stock recovery?
Click to expand...
Click to collapse
what is "adb" sorry im a newbie lol
Sloth Nuggets said:
what is "adb" sorry im a newbie lol
Click to expand...
Click to collapse
Adb stands for Android debug bridge. It comes with SDK Manager. Download SDK Manager and type in adb reboot recovery in cmd. That will get you to recovery mode on your phone. You might have to go to the sd card folder on the computer and right click while holding shift and click "open command window here".
Here's a good overview on adb and how to set it up.
It REALLY helps during boot loops because you can replace system files or get into recovery or do other things if you are rooted with just a few commands.
http://forum.xda-developers.com/showthread.php?t=2141817
azeem40 said:
Adb stands for Android debug bridge. It comes with SDK Manager. Download SDK Manager and type in adb reboot recovery in cmd. That will get you to recovery mode on your phone. You might have to go to the sd card folder on the computer and right click while holding shift and click "open command window here".
Click to expand...
Click to collapse
thanks for the reply, i download the sdk manager and i tried looking for the SD card on my computer but i cant find it also i typed the "adb reboot recovery" in cmd and it said that there are no devices connected! i have my phone connected but my computer wont recognize it and i downloaded the drivers for it and everything...
Sloth Nuggets said:
thanks for the reply, i download the sdk manager and i tried looking for the SD card on my computer but i cant find it also i typed the "adb reboot recovery" in cmd and it said that there are no devices connected! i have my phone connected but my computer wont recognize it and i downloaded the drivers for it and everything...
Click to expand...
Click to collapse
Did you have android debugging enabled before this happened? If your computer can't install the drivers and you can't see it in the list of devices after adb then you may have not had android usb debugging enabled under development options.
Related
I'm having trouble getting this POS rooted. Got it unlocked with little problem, but now that it comes to rooting, it's extremely confusing to follow the tutorials. Is there any working one-click methods? I'm no stranger to Android OS, I had my Dinc2 rooted in about 5 minutes after unboxing. But this abomination is really working my nerves. Help please?
There is no "One-Click Root"
But rooting using the given instructions is not difficult at all.
Its as simple as downloading a few files, and typing a few codes.
what have you tried so far? and what firmware are you running?
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Cat_On_Droid said:
Since you unlocked your bootloader,here is how you get Root
http://forum.xda-developers.com/sho...m.xda-developers.com/showthread.php?t=1130639
download the .img ,put it in your fastboot folder
download the rootxperia.zip to your SD card
Turn phone off,plug into your PC/Laptop and hold search button ( might take some tries) ,you should get BLUE LED
SHIFT+RIGHTCLICK on fastboot folder and open in command window (assuming your usiing vista/win7) and type
fastboot boot recoveryPLAY.img
wait 2 minutes,it takes time.
Apply zip from SDcard and you are rooted
Click to expand...
Click to collapse
the wait for recovery to load is HORRIBLE!! lol. push the menu button once in a while if you are unsure. i did. it makes the wait (for me) less painful but installing the .zip and rebooting successfully with a rooted phone is AWESOME!!
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
chattguy said:
Thanks for simplifying it for me Cat. I'm sitting here with my blue LED, my blank screen and my command window that now says "waiting for device" so that's what I'm doing. Waiting. Smoke break time.
Click to expand...
Click to collapse
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
mehdi.moha said:
are you sure that you installed the "S1Boot Fastboot" driver completely ?
cause i had some problem like yours ... just go to my computer=> right clik => manage=> devicce manager
and check if it's already install or not (( other devices ))
Click to expand...
Click to collapse
Sony Ericsson sa0102 is installed, but I'm not seeing anything in my device manager about S1 Fastboot. Hmm...how would one go about installing it? I have the fastboot folder on my desktop. It has two subfolders, Fastboot and USB_drivers .
chattguy said:
God this is painful. It's doing nothing. Should I unplug and try it again? it's been over 10 minutes.
Click to expand...
Click to collapse
In this case if it's either still 'waiting for device' or trying to boot recoveryPLAY.img, then you're safe to try again since nothing is being flashed
When connected next time, in fastboot mode, before booting the .img, type this:
fastboot devices 'enter'
It will show a list of devices attached.
It might be that your missing some drivers so fastboot is not working correctly and won't detect your device. Have you pc companion installed? I don't remember if there came any drivers with the fastboot download but check that, there might be some drivers you didn't install.
Regards Dousan...
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
chattguy said:
This is what happens. I just get another prompt. Here's a screenshot of that, along with the drivers folder.
Click to expand...
Click to collapse
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
AndroHero said:
That means no device is connected. Unlike ADB, fastboot does not return the usuall "list of attached devices" line. Have you installed fastboot drivers?
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
chattguy said:
I don't know, I just installed what the guy told me to when he did the remote bootloader unlock. Fastboot IS in my device manager, however, it says there are no drivers installed. I've got the blasted things on my desktop with some DPInst.exe installer, but it says I need the 64-bit version, which I can't find. Microsoft tried to have me download some silly .ISO file but I really think there must be an easier way than to burn some DVD installation disk.
Click to expand...
Click to collapse
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
AndroHero said:
Ok these are the x32/x64 fastboot drivers.
http://www.multiupload.com/0XZV1LXRVA
Download them and unpack them. Connect your device in fastboot mode. Then navigate to device manager on windows, Find the S1 Fastboot thats not installed correctly. go to update driver and navigate to the driver package you just unpacked. Done
Click to expand...
Click to collapse
Mother. Of. God.
I did it. No, f**k that, you did it. All of you, thank you so much. You guys really helped me out bigtime, without berating me and calling me a noob lol. I sincerely appreciate it.
Also a special thanks to Alejandrissimo for unlocking the bootloader. Without you, this wouldn't have even been possible. Yay this blasted phone is finally rooted...
...and nobody had to die in the process.
That's what we are all here for. Learning about things through each other. We were all without knowledge at one point
Sent from my R800i using XDA App
Flashed the Broccoli nightly rom I can no longer boot or get back into CWM. Computer cannot start the device. Can someone please help me? Tried all the tools and methods. It won't work unless I can get the device to start when connected to my computer.
RIght now when I press Vol Up and power, it brings me to cold boot linux. Cannot select anything or do anything. When connected to comp, it says device cannot start Code 10. Don't know what else to do. Help please
Looks like you're having an issue similar to mine. You'll need to setup ADB and push another rom to your Prime.
Can you get into recovery?
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
This thing is completely frozen no matter what. I can power off and on but that's about it. The device won't start according to windows. I'm praying I won't have to RMA or something.
You shouldn't be getting that screen pressing vol up and power.....that should be vol down and power, then doing nothing.
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Thats pretty strange. You kinda screwed unless you can get into recovery or fastboot
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Thanks let me try now. I hope it works. How did you get the computer to recognize the prime? Do I need to enable asus sync?
Tritium3.016 said:
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Click to expand...
Click to collapse
It's alive!!! Thanks for the help. :good:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
So when your device turns on its in a recovery loop right? You try to reboot and it goes right back to recovery?
It's ok don't worry, we will get it fixed. If that's what your problem is its referred to brick 1a in the unbrick your prime sticky thread.
We just need to setup ADB if you haven't already, and run one command. PM me if you need some help and ill try my best to get you through it or remotely connect to your computer to help you.
I highly suggest TWRP recovery after you get rebooted.
Sent from my ADR6425LVW using xda premium
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
This is what I did while in CWM. Below is a copy of an insert from this thread.
http://forum.xda-developers.com/showthread.php?p=24923189#post24923189
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
the thing is the computer is not picking it up i tried diffrent drivers and still nothing i try doing ADB Shell device not found in order to do some commands i have to have it mount and thats the problem what ever i do wont move nothing so basicly is still on CWM only reboot and back again to CWM
Hold power and vol down to boot into CWM. Then you can do the blobfile push. It worked for me
I can't boot my phone, stays black, cant be rcognized by windows.
I was just trying to flash a battery mod in recovery and when i hit reboot it never did. Now it seems screwed. Not sure what to do. any help appreciated
Out of curiosity which battery mod was it?
Sent from my EVO using XDA
Does it charge? Can you get to recovery?
{ParanoiA} said:
Does it charge? Can you get to recovery?
Click to expand...
Click to collapse
no not at all. cant get to recovery. and usb to computer says in device manager qusb_dload. I have no idea what that means
Can you get to bootloader by pressing power vol down?
If you can. hook your cable to phone and get it to fastboot usb mode then run the RUU file on your computor. This will unroot your phone. this is how i fixed my phone. I hope you get it fixed.
Ladicx said:
no not at all. cant get to recovery. and usb to computer says in device manager qusb_dload. I have no idea what that means
Click to expand...
Click to collapse
you can start by telling us exactly what you tried to flash..link?
what your seeing with the qusb is usually a indication is bricked.
Try
Try hooking the phone to the computer, after you do that open a command prompt and type. "adb reboot recovery" I hope you backed up, run the back up you should have, then you should be fine, i doubt your bricked.
musicman625 said:
Try hooking the phone to the computer, after you do that open a command prompt and type. "adb reboot recovery" I hope you backed up, run the back up you should have, then you should be fine, i doubt your bricked.
Click to expand...
Click to collapse
thanks for the responses but i panicked and took my phone in for repair and sprint gave me a new one.
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
cybrkada said:
Hi,
I'm on the process of installing ClockWorkMod Recovery, stupid of me i forgot to enable USB Debugging option on my phone. Now I'm stuck on Command Prompt saying...
C:\Fastboot>fastboot flash boot recovery-nozomi.img
< waiting for device >
It has been sitting for more than 5 minutes as I am typing now. Should I disconnect the USB cord? Would this action brick my phone?
Sorry for my stupidity!
Click to expand...
Click to collapse
How are you installing it ???
Via flash tool??
And nope your phone won't brick
I disconnected the cord. Turned on the phone and noticed that USB Debugging is ticked/checked. So I repeated the process but I am still getting..
< waiting for device >
What should I do?
soulhackereborn said:
How are you installing it ???
Via flash tool??
And nope your phone won't brick
Click to expand...
Click to collapse
Yes, via Flastool. Yeah my phone did not get bricked! :good:
cybrkada said:
Yes, via Flastool. Yeah my phone did not get bricked! :good:
Click to expand...
Click to collapse
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
soulhackereborn said:
can u give the link for this recovery you triein to push through flashtool and the turorial if possible...
Click to expand...
Click to collapse
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
cybrkada said:
Hi soulhackereborn!
Sorry for the late reply! Sorry the forum prevented me from posting the URL as I am just a new user here.
"To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!"
Anyway the tutorial says (copy&paste):
Use the computer for downloading the CWM file from here.
Then, on the same computer download fastboot from here.
Extract fastboot on C:\ drive.
Then, copy the downloaded “ecovery-nozomi.img” file to the Fastboot folder from your computer.
Now you must connect the phone in fastboot mode with the computer.
In order to do so you must plug the USB cord to the PC, then on your phone press and hold the Volume Up button and while doing this connect the USB cable to your Xperia S.
Up next, on the PC click on “Start -> Accessories -> on Command prompt right click -> Run as administrator”.
The command prompt window will now be displayed.
Now, enter the following commands (press enter after each one): “cd c:\Fastboot” and “fastboot flash boot recovery-nozomi.img”.
CWM will now be flashed.
In the end the “finished / OKAY” message should be displayed.
In command prompt enter “fastboot reboot”.
Your handset should now reboot into ClockworkMod recovery.
Remove the USB cord and disconnect the Xperia S from the computer.
Click to expand...
Click to collapse
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
soulhackereborn said:
everything seems to be good in the tutorial though..
But what is it a kernel, rom or an CWM image file ???
if still it says waiting for device then here's a couple things you should check :-
1) Fastboot ie; S1 Boot driver installed or no
2) Switch off phone and connect it to the PC via usb holding Volume + button (this is fastboot mode)
3) Check does your device remain in fastboot mode or no i mean purple led light glows stays on continuously or no until u execute the command, if not reinstall the driver and try again
4) If everything well till now try flashing with the given commands without the quotes ie; fastboot flash boot recovery-nozomi.img
Click to expand...
Click to collapse
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
cybrkada said:
1. I dont know how to check, it should be installed as i unlock the bootloader yesterday. I actually manually updated it on Device Manager.
2. I understand this.
3. On my case, it's a blue LED lit steadily after doing step 2. I am using Sony Xperia S.
4. Yes, i flashed them without the quotes.
Click to expand...
Click to collapse
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
soulhackereborn said:
Try rebooting both your PC and phone... This is a small thing but always helps and one more thing after switching off the phone n before connecting it in fastboot mode let der be a gap of alteat a min or two
Is this tutorial on xda or some other forum if on xda then try messaging me the link or tel me forum sub forum topic and title
Click to expand...
Click to collapse
I dont see PM here, i think I am still restricted.
see if the link helps, i removed w w w
android.gs/install-clockworkmod-recovery-sony-xperia-s
i'm rebooting them after this.. thanks
LiveSquare said:
Usually <waiting for device> can show up when you don't have proper drivers installed. Double check them if you haven't done so.
Click to expand...
Click to collapse
Which drivers? I have already downloaded SDK and I believe the S1 driver is installed yesterday when i unlock the bootloader.
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
cybrkada said:
i rebooted both the PC and the CP, but i am still getting < waiting for device >...
by the way is the ADB from tutorial the SDK one?
Click to expand...
Click to collapse
Dude as far as I know there is no need to check/ tick USB debugging for fastboot... It's just for flashtool..
Try re -installing the drivers again manually or let windows search over internet...
Finally, i made it! thanks to both of you!
fastboot.exe seems to be corrupted!
Problem solved!
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
cybrkada said:
Just last one question, now that i have CWM recovery on my phone, is it already rooted? sorry i am beginner...
Click to expand...
Click to collapse
Yes ur rooted!!
Thanks!
I'm currently downloading Cyanogenmod ver 9.1. Hopefully it works! Thank you so much buddy! You have been very helpful! If I get problems on flashing CM9.1, i'll contact you , hehe
One of the reminders on isntalling CM9 is:
Make sure that your Xperia S is already running a rooted firmware, and that it has the ClockworkMod Recovery properly installed.
How do I know I have a rooted firmware? Do I still need to flash FTF file?
By the way, I am getting a boot loop from CWM recovery, I cant go to the homescreen, no option to turn off! It only reboots the CWM.
(Still downloading CM9 as of the moment)
Hi guys,
I flashed a wrong ROM, and then the screen doesn't turn on any more, plug in computer, computer can't recognize the device, it gives me plug-in then unplug and then plug-in sound while it is plug in all the time. tried mini USB jig, no response. is it completely dead? anyway to save it?
Thanks guys
thunderzhao said:
Hi guys,
I flashed a wrong ROM, and then the screen doesn't turn on any more, plug in computer, computer can't recognize the device, it gives me plug-in then unplug and then plug-in sound while it is plug in all the time. tried mini USB jig, no response. is it completely dead? anyway to save it?
Thanks guys
Click to expand...
Click to collapse
If you want unbrick hardbrick solution please PM me.
Thanks.
hard brick = replace parts
soft brick = fixable
if your computer is outputting sound when you connect your phone to it, then there is life in the phone its not hard bricked. *ive softbricked many phones, and ive hard bricked 1, so i know the difference*
can you get to recovery?
can you get to download mode?
can you adb devices via pc?
JamieD81 said:
hard brick = replace parts
soft brick = fixable
if your computer is outputting sound when you connect your phone to it, then there is life in the phone its not hard bricked. *ive softbricked many phones, and ive hard bricked 1, so i know the difference*
can you get to recovery?
can you get to download mode?
can you adb devices via pc?
Click to expand...
Click to collapse
Thanks for your reply, I can't get into recovery or download. but never tried adb device via PC, is that the same as odin?. I will try that, and is there a guide on how to do that?
Well... if you freshly flashed a Rom let's hope that dev had usb debugging on. If not this is all am exercise in setting up adb...cause even if the device isn't bricked without that setting on, adb will not communicate with the device.
Install java runtime environment and add to variable path.
Then you can install the android sdk.
Once installed open a command prompt.
Cd (change directories) to the "platform-tools" folder of the sdk install.
Once the prompt is there type:
Adb devices (enter)
If you get a device and then an alpanumeric id, your device is alive
From there type:
Adb reboot recovery (enter)
To boot into recovery and flash a working Rom.
Or adb reboot download (enter)
To boot download mode and use Odin.
If adb says device offline, usb debughing is off but your device is still alive, try the button combos for recovery, or invest in a jig to force download mode.
And finally if that gets nothing.... you're bricked.
Mobile tech videos . Com is a very reputable site that offers jtag debricking repair.
Wow cris, I am amazed at your thorough responses.
rangercaptain said:
Wow cris, I am amazed at your thorough responses.
Click to expand...
Click to collapse
Sometimes even zombies can provide a benefit to society.
Studa ... Nice going sir.
Sent from my Big Ass Outlaw Phone
studacris said:
Well... if you freshly flashed a Rom let's hope that dev had usb debugging on. If not this is all am exercise in setting up adb...cause even if the device isn't bricked without that setting on, adb will not communicate with the device.
Install java runtime environment and add to variable path.
Then you can install the android sdk.
Once installed open a command prompt.
Cd (change directories) to the "platform-tools" folder of the sdk install.
Once the prompt is there type:
Adb devices (enter)
If you get a device and then an alpanumeric id, your device is alive
From there type:
Adb reboot recovery (enter)
To boot into recovery and flash a working Rom.
Or adb reboot download (enter)
To boot download mode and use Odin.
If adb says device offline, usb debughing is off but your device is still alive, try the button combos for recovery, or invest in a jig to force download mode.
And finally if that gets nothing.... you're bricked.
Mobile tech videos . Com is a very reputable site that offers jtag debricking repair.
Click to expand...
Click to collapse
thanks a lot for your detailed instruction!!!
unfortunately, computer cannot recognize the device, it just goes on and off endlessly, and asking to format the drive, Adb devices doesn't show anything either. probably have to send to repair
The usual cure for flashing a ROM for another device is a JTAG service. cris mentioned it -- www.mobiletechvideos.com. It takes a week for the repair and costs you about $50.
The phone is returned with your carrier's stock ROM ICS 4.0.4.
rangercaptain said:
The usual cure for flashing a ROM for another device is a JTAG service. cris mentioned it -- www.mobiletechvideos.com. It takes a week for the repair and costs you about $50.
The phone is returned with your carrier's stock ROM ICS 4.0.4.
Click to expand...
Click to collapse
Sounds like a plan, Thanks
thunderzhao said:
Sounds like a plan, Thanks
Click to expand...
Click to collapse
I only do for $ 25 and ship it back right away . More detail PM me.