Anyone know where to get a stock Rogers RUU. I need the .exe file to get myself up and running again.
http://http://forum.xda-developers.com/showthread.php?p=27882810#post27882810
Finally got it working...the above linkis what worked. Here is the summary...
I was having this same problem and it took a while before I could get it to work. Try opening a command window in the same location of your adb tools.
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
Hopefully this helps you out!
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Berserk87 said:
I'm stock right now (rooted) , but the updates keep failing, so i want to reflash stock rom.
I'm lost as to how to do this.
I downloaded ARUwizard and the stock rogers rom (PJ83IMG) but its still failing. I dont get all this adb tools stuff.
Click to expand...
Click to collapse
do this:
1.Put Rogers stock zip (keep it in zip form) in your platform-tools folder (you need to download Android SDK). This is the rogers file I downloaded...http://rapidlibrary.com/files/pj83i...elease-254934-signed-zip_ulc8eyefx8i89on.html
2. Boot phone into fastboot (hold power button and volume down key)
3. Used command window to relock bootloader by doing the following:
use command window to get to location on your computer where you have saved SDK stuff, continue with command window to the platform-tools folder then enter the following commands:
fastboot devices <enter>
fastboot oem lock <enter>
Phone will restart and reboot into fastboot again
4. type 'fastboot oem rebootRUU'.
5. Next, make sure you have the .zip RUU file in the same folder (see step 1) and type 'fastboot flash zip XXX.zip' (replace XXX with whatever the rogers stock zip is called, I changed it to "rogersstock.zip")
Phone will reboot to a HTC screen. If you see "re-flush image immediately", repeat fastboot flash zip XXX.zip command. You may have to do this 2 or 3 times.
After doing this, I was able to download and install the Rogers firmware update
BTW...I didn't discover any of this stuff on my own...I researched a bunch of different posts and put it together. Hopefully, someone else finds have all this in one post useful.
I do all the above steps but then i get this message:
FAILED (remote: 44 hboot version check fail)
I try to update the RUU in windows but I get Error 154 Image Updating error.
Any ideas?
Related
last night i flashed an update of clockwork mod through rom manager. i then went to do a back-up of my current rom. the phone re-booted to the fastboot mode and now says no boot or recovery img. when i scroll to recovery and click it, the phone reboots right back into the bootloader. i am trying to flash a new recovery through adb but i cant get anything to connect. when i do "adb devices" in the command prompt i get the daemon started and list of devices but there are no devices listed. "fastboot devices" does nothing either. i have the android sdk loaded onto c:\ and the drivers seem to be installed correctly. when i rooted the phone i used a different pc that i dont have access to now. i also used pdanet for the drivers so i have never had the google drivers set up correctly. i type fastboot flash recovery recovery.img and it says "cannot load recovery.img" i have downloaded the recovery-clockwork3.0.0.5-crespo.img to the "tools" folder and renamed it "recovery.img"
i have tried to explain everything i have done so far but i am sure there are some steps i have missed. i read some on odin and downloaded it but i am even more lost trying to figure that out. i really need some help here and i would appreciate anything i can get
when you're in bootloader, you're supposed to use "fastboot"
you cant flash a recovery using adb.
go into bootloader mode
fastboot devices
... if your device doesn't show up, then your drivers are not properly set up.. uninstall them and look for the sticky and reinstall your drivers using those set of instructions; assure your SDK is updated to support 2.3.X
when you get your device to appear in fastboot devices.
download clockwork recovery 3.0.2.5 (3.0.2.4 is buggy) or 3.0.0.5; 3.0.2.5 is found in dev forums; rename it to recovery.img
put it in /sdk/tools/
fastboot flash recovery recovery.img
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
tohg2 said:
i guess i need help getting the device connected through fastboot. i have tried 5 times now to install the drivers verbatim to what the sticky says (using W0lv3r1n3's Great Windows Rooting Guide). adb command works and pulls up the adb help text. fastboot is still unrecognized by the command prompt. adb devices nor fastboot devices works. i have no idea what else to do. most of the stickies just graze over this part and have no trouble shooting guides.
Click to expand...
Click to collapse
if your device is unable to GET into bootloader mode... that wont get you anywhere.
when you plug your phone into the computer with the USB.. does that USB sound pop up? if it doesnt.. then its bricked.
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
when i plug the usb in i dont hear a sound. the phone will only boot into "fastboot mode".
when i do fast boot devices i see "38328e03afbf00ec fastboot"
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
bootloader mode is for fastboot. you wont be using ADB to recover your device.
you unzip the file. it should be like: clockwork-recovery-version..blah blah blah.img
rename it to "recovery.img" assure that your "fastboot" appears as "fastboot.exe" and not just "fastboot." if it is "fastboot" you need to go into folder options and show extensions otherwise you'll be trying to flash "recovery.img.img" and SDK wont recognize it
tohg2 said:
ok i have fastboot devices seeing the device. but adb devices still wont see it. when i do fastboot flash recovery recovery.img it says cannot load recovery.img. i put the clockwork file in the tools folder renamed at recovery.img. do i leave it as a zip file though?
Click to expand...
Click to collapse
Make sure you are typing the full file path, for example on my setup its "fastboot flash recovery c:\android\tools\recovery.img"
Sent from my Nexus S using XDA App
file extensions are being shown and it is named recovery.img. still saying cannot load "recovery.img" i have tried several recovery downloads from different sources. as for file size of the img its 3,988kb sound right? i tried fastboot oem lock and unlock and everything worked fine. is there another recovery img i can try. maybe a stock recovery or somehting?
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
tohg2 said:
ok so i tried "fastboot flash recovery c:\program files (x86)\android\android-sdk\tools\recovery.img" exactly and still nothing i have the path modified in the system so i was under the assumption that i didnt have to write out the whole path in the command prompt.
Click to expand...
Click to collapse
cd C:\program files (x86)\android-sdk\tools\
fastboot flash recovery recovery.img
is what you want to do.
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
tohg2 said:
tried that path and still got nothing. i re-booted my pc thinking that would help and now i cant find my device with fastboot devices. adb isnt recognized either now. i just cant catch a break. although i suppose its my fault. i really appreciate you going back and forth with me like this. with all the trouble i am having does trying odin make any sense? i searched a bit but there dosent seem to be alot of info on that either
Click to expand...
Click to collapse
Odin is last resort. If fastboot devices shows your phone you will be able to flash recovery. Reinstall phone drivers and get fastboot to work. Then get back to trying to flash recovery. I really think it is some small mistake. Did you exctract the zip of recovery and copy the .img file?
The error you were getting means the appropriate file was not found in the file path you specified, so its not a phone error.
Sent from my Nexus S using XDA App
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
tohg2 said:
got it. the first line in my command promt kept saying c:\users\dana>. i couldn't delete it so i ignored it and kept typing in the path after that but i guess it was always looking in users/dana and that wasn't where the img file was. i put the img file alone in the users/dana folder and it worked. i guess i am a bit slow to understanding the command prompt. thanks again for everyone's help and patience
Click to expand...
Click to collapse
Cool! Glad you got it, good job!
Sent from my Nexus S using XDA App
Please help, I'm having the exact the same problem
I know, I shouldn't have play around with my phone since I don't know much about rooting the device.
My phone booted into Andriod logo with an unlocked, I have successful downloaded
clockwork recovery 3.0.2.5 and rename it to recover.img
I ran following command
fastboot flash recovery recovery.img and it was successful..
I tired to reboot my phone after that as normal but I'm still getting the same screen which only showing the Android Logo with an unlocked lock.
I'm not sure what I am suppose to do after need to get my phone to work again, any help would be appreciated.
Thank you,
So I know I'm a dumb ass but here's what happened:
HTC Rezound S-off
Amon Ra 3.15
Hboot 2.27
ViperRez 1.0.3
My phone was acting a little buggy and my friend kept telling me I should flash a firmware update so I flashed
this " PH98IMG-firmware.zip - 33.02 MB " from here: http://forum.xda-developers.com/showthread.php?t=1835811&highlight=ruu&nocache=1
I checked the MD5 when I dl'd to PC BUT not when I copied to sd card. When flashing, all steps were successful except for 2: MDM9K - FAIL-UZ & RADIO_V2 - FAIL-UZ
I rebooted and got stuck at the white HTC screen. Battery pop and I tried to flash again. This time almost everything returned -- FAIL-PU except for the two above which still said FAIL-UZ.
Adding insult to injury I tried flashing two more RUU's from android police, I have a screenshot attached of one of my failed attempts.
ADB Devices doesn't recognize my phone but FASTBOOT devices returns a serial number. Boot loader also changes from " fastboot" to "fastboot-usb" when I plug into a PC but my PC doesn't see my phone.
I think it was a corrupted RUU because I decided to check the MD5 of a RUU on my sd card after the damage was done and it was bad. I then copied the same file over to my sd card a bunch of times, checking each MD5 and more than half the time they were bad.
I appreciate any suggestions anyone might have.
Suggestion. I've ran into this before awhile back with my HTC EVO 4G. Which I still own .
Using phone in fastboot USB mode. Trying running this command " fastboot -w update update.zip" this is assuming u may have the zip file and also assuming "update.zip" is the file name.
Or, if all you have is the ruu.exe file the while in the bootloader.. perform a full wipe.. then go back into fastboot USB and type this in cmd. " fastboot reboot oem-78" or "fastboot oem rebootRUU" can't remember which and it will go straight into ruu mode then run the ruu.exe and see if this helps. Might also want to see if you can find a full ruu instead of just an update.
If you wish to try the first method, either obtain a zip format of the rom which you should be able to grab from the exe itself "Google this".
Hope this helps or makes any sense.. its 6:30am and typing on my phone lol. Now I'm gonna feed my 5month old n check back later today on your results or questions. happy flashing .... hopefully
Thanks for the reply. I tried running in fastboot...heres what I got:
c:\mini-adb_vigor>fastboot devices
HT19RS207848 fastboot
c:\mini-adb_vigor> fastboot -w update rezound_AndroidPolice_4.03.605.2_PH98IMG.z
ip
Whoops: didn't find expected signature
read_central_directory_entry failed
²ετ╪»╛g[ÑÖ╥yïS¬☼û÷A☼├║f:e{ûhh%►ÉÉW└|'╢σG╣S╙τφN}┐{S
c:\mini-adb_vigor>
Yikes!!
I have to go do some stuff but I will check back this afternoon. Thanks again.
iAMsalm said:
Suggestion. I've ran into this before awhile back with my HTC EVO 4G. Which I still own .
Using phone in fastboot USB mode. Trying running this command " fastboot -w update update.zip" this is assuming u may have the zip file and also assuming "update.zip" is the file name.
Or, if all you have is the ruu.exe file the while in the bootloader.. perform a full wipe.. then go back into fastboot USB and type this in cmd. " fastboot reboot oem-78" or "fastboot oem rebootRUU" can't remember which and it will go straight into ruu mode then run the ruu.exe and see if this helps. Might also want to see if you can find a full ruu instead of just an update.
If you wish to try the first method, either obtain a zip format of the rom which you should be able to grab from the exe itself "Google this".
Hope this helps or makes any sense.. its 6:30am and typing on my phone lol. Now I'm gonna feed my 5month old n check back later today on your results or questions. happy flashing .... hopefully
Click to expand...
Click to collapse
What about running this zip?
http://forum.xda-developers.com/showthread.php?t=1833530
You can give it a try, but not sure if I read too quickly and seems that solution is only if you were trying to go from S-OFF to S-ON. If you want to try other zips or "ruu.exe" files you can try some from here. http://shipped-roms.com/index.php?category=android&model=Vigor .
See if they can give you a better outcome while trying to flash with fastboot.
This guide is made for those people who want to unroot and revert there HTC butterfly to stock firmware by flashing Stock RUU using ADB commands. this is tested personally by me. a compete detail explanation can be found in this link.
1. download the stock RUU in this link. This is a working Stock RUU image and can be flash only using ADB command. the zip file will prompt you that it is corrupted when you try to open manually. rename the file to PL99IMG.zip to flash it faster.
PL99IMG_DLXB1_U_JB_45_hTC_Asia_WWE_1.12.707.1_R_Ra dio_3A.22.306.10_10.07.1060.04D_release_signed.zip
http://www.androidfilehost.com/?fid=9390288116658475218
Click to expand...
Click to collapse
2. You will need sdk & and drivers, please take a look here. if you already have it, continue. extract the folder and copy the PL99IMG.zip to that directory.
3. Reboot to bootloader by Holding Vol down + Power button
4. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using.
5. open a command prompt and browse to the folder containing the ADB files.
6. enter the following commands
fastboot erase cache
Click to expand...
Click to collapse
7. You may not see any output, then enter the command
fastboot oem rebootRUU
Click to expand...
Click to collapse
8. You phone will now go into the RUU mode.
9. Wait for around 30 seconds, then enter the command
fastboot flash zip PL99IMG.zip
Click to expand...
Click to collapse
if this error will prompt you. enter the command again in step 9.
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Normal after Hboot version changes. You need to run only the flash command again (not the whole set of commands, just the fastboot flash command.)
Click to expand...
Click to collapse
10. The installation will begin and you will be able to see the progress at every step.
Once done, enter the command
fastboot reboot
Click to expand...
Click to collapse
i hope this guide will be a great help.
Hit Thanks if you like it.
Or you could rename this thread to 'How to flash RUU zip for X920D'
Does this include stock recovery?
So why do we have 2 threads .. ?? Just confused
Also when I tried fixing the zip, I didnt see any boot image in it.. can someone who has restored confirm that their kernel also actually reverted ?
v-b-n said:
So why do we have 2 threads .. ?? Just confused
Also when I tried fixing the zip, I didnt see any boot image in it.. can someone who has restored confirm that their kernel also actually reverted ?
Click to expand...
Click to collapse
you dont have to fix the zip file. let the internal RUU flash everything for you including the boot image. as i said never try to fix the zip file even though it saying its corrupted. only RUU will can open the zip file properly. this guide is a step by step procedure. alright? i confirm that this is working. this where the steps i used to revert my butterfly back to stock.
lombers said:
Does this include stock recovery?
Click to expand...
Click to collapse
yes this contains the stock recovery and even the boot image.
acid28 said:
you dont have to fix the zip file. let the internal RUU flash everything for you including the boot image. as i said never try to fix the zip file even though it saying its corrupted. only RUU will can open the zip file properly. this guide is a step by step procedure. alright? i confirm that this is working. this where the steps i used to revert my butterfly back to stock.
Click to expand...
Click to collapse
Agreed on that , whats baffling me is that boot image doesnt come up in the zip listing at all ... anyways, I am not in need of this , was just clarifying for others
acid28 said:
This guide is made for those people who want to unroot and revert there HTC butterfly to stock firmware by flashing Stock RUU using ADB commands. this is tested personally by me. a compete detail explanation can be found in this link.
1. download the stock RUU in this link. This is a working Stock RUU image and can be flash only using ADB command. the zip file will prompt you that it is corrupted when you try to open manually. rename the file to PL99IMG.zip to flash it faster.
2. You will need sdk & and drivers, please take a look here. if you already have it, continue. extract the folder and copy the PL99IMG.zip to that directory.
3. Reboot to bootloader by Holding Vol down + Power button
4. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using.
5. open a command prompt and browse to the folder containing the ADB files.
6. enter the following commands
7. You may not see any output, then enter the command
8. You phone will now go into the RUU mode.
9. Wait for around 30 seconds, then enter the command
if this error will prompt you. enter the command again in step 9.
10. The installation will begin and you will be able to see the progress at every step.
Once done, enter the command
i hope this guide will be a great help.
Hit Thanks if you like it.
Click to expand...
Click to collapse
This will put my Butterfly to stock everything right? Locked bootloader, stock recovery and all?
Sent from my HTC Butterfly using Tapatalk 2
enyaj said:
This will put my Butterfly to stock everything right? Locked bootloader, stock recovery and all?
Sent from my HTC Butterfly using Tapatalk 2
Click to expand...
Click to collapse
Yes this will revert your butterfly back to stock. and relock your bootloader
I guess this is a sort of side question, but is this the latest current software available for the X920D or is there an OTA available?
EDIT: Also what languages are available in this RUU?
acid28 said:
This guide is made for those people who want to unroot and revert there HTC butterfly to stock firmware by flashing Stock RUU using ADB commands. this is tested personally by me. a compete detail explanation can be found in this link.
1. download the stock RUU in this link. This is a working Stock RUU image and can be flash only using ADB command. the zip file will prompt you that it is corrupted when you try to open manually. rename the file to PL99IMG.zip to flash it faster.
2. You will need sdk & and drivers, please take a look here. if you already have it, continue. extract the folder and copy the PL99IMG.zip to that directory.
3. Reboot to bootloader by Holding Vol down + Power button
4. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using.
5. open a command prompt and browse to the folder containing the ADB files.
6. enter the following commands
7. You may not see any output, then enter the command
8. You phone will now go into the RUU mode.
9. Wait for around 30 seconds, then enter the command
if this error will prompt you. enter the command again in step 9.
10. The installation will begin and you will be able to see the progress at every step.
Once done, enter the command
i hope this guide will be a great help.
Hit Thanks if you like it.
Click to expand...
Click to collapse
getting error FAILED (remote :99 unknown fail)
i hv tried 4-5 times as instructed but same error
getting error FAILED (remote :99 unknown fail)
guyluvsgals said:
getting error FAILED (remote :99 unknown fail)
i hv tried 4-5 times as instructed but same error
Click to expand...
Click to collapse
Found solution for this......
Need to relock back the bootloader
1.) On bootloader, type "fastboot oem lock" (I got the message mentioned locked successful or something but end of the process FAILED)
2.) Just don't bother bout the message, ur phone may restarted now.
3.) Boot back to Bootloader (Hold Power + Vol Down)
4.) Follow back all the steps as mentioned on the thread.
Hope this help
guyluvsgals said:
getting error FAILED (remote :99 unknown fail)
i hv tried 4-5 times as instructed but same error
Click to expand...
Click to collapse
Your bootloader is still unlocked. You didn't relock your bootloader. Relock your bootloader using this command:
Code:
fastboot oem lock
acid28 said:
This guide is made for those people who want to unroot and revert there HTC butterfly to stock firmware by flashing Stock RUU using ADB commands. this is tested personally by me. a compete detail explanation can be found in this link.
1. download the stock RUU in this link. This is a working Stock RUU image and can be flash only using ADB command. the zip file will prompt you that it is corrupted when you try to open manually. rename the file to PL99IMG.zip to flash it faster.
2. You will need sdk & and drivers, please take a look here. if you already have it, continue. extract the folder and copy the PL99IMG.zip to that directory.
3. Reboot to bootloader by Holding Vol down + Power button
4. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using.
5. open a command prompt and browse to the folder containing the ADB files.
6. enter the following commands
7. You may not see any output, then enter the command
8. You phone will now go into the RUU mode.
9. Wait for around 30 seconds, then enter the command
if this error will prompt you. enter the command again in step 9.
10. The installation will begin and you will be able to see the progress at every step.
Once done, enter the command
i hope this guide will be a great help.
Hit Thanks if you like it.
Click to expand...
Click to collapse
hello I got an error here :
FAILED (remote: 43 main version check fail)
Your device is S-ON & you are trying to use an RUU that has software number less than your current software number.
what should I do now
acid28 said:
This guide is made for those people who want to unroot and revert there HTC butterfly to stock firmware by flashing Stock RUU using ADB commands. this is tested personally by me. a compete detail explanation can be found in this link.
1. download the stock RUU in this link. This is a working Stock RUU image and can be flash only using ADB command. the zip file will prompt you that it is corrupted when you try to open manually. rename the file to PL99IMG.zip to flash it faster.
2. You will need sdk & and drivers, please take a look here. if you already have it, continue. extract the folder and copy the PL99IMG.zip to that directory.
3. Reboot to bootloader by Holding Vol down + Power button
4. Connect your phone to the PC while in the bootloader. The phone should say fastboot USB, if not, select fastboot on the phone & check if it says fastboot USB, if not, change the USB port you are using.
5. open a command prompt and browse to the folder containing the ADB files.
6. enter the following commands
7. You may not see any output, then enter the command
8. You phone will now go into the RUU mode.
9. Wait for around 30 seconds, then enter the command
if this error will prompt you. enter the command again in step 9.
10. The installation will begin and you will be able to see the progress at every step.
Once done, enter the command
i hope this guide will be a great help.
Hit Thanks if you like it.
Click to expand...
Click to collapse
Success!
the ruu has corrupted?
Can someone post the stock recovery img please
v-b-n said:
Can someone post the stock recovery img please
Click to expand...
Click to collapse
here it is, recovery.img from : OTA_DLXB1_U_JB_45_hTC_Asia_WWE_1.12.707.1_R
How do unlock the bootloader again so that I can flash the stock recovery img? when i relock i used the fastboot oem lock command..then flashed RUU..all ok..just that the stock recovery doesnt show..just an image of a phone with a red exclamation mark.Thanks.
edit..ok..managed to unlock again..but after I flash the stock recovery..still get the red triangle...
Do i have to unroot a rooted x920d to receive OTA update?
Hi all,
its been a long time since I last on xda. I was using HTC P3600i back then. Now I just bought a butterfly & its rooted. I am unable to update via air since then. My question is do I hve to do this to update my system
software? We all know new OTA update is available. I can't update cos everytime got error while flashing. The error is zip file not found. When I use it with tarp the error is cannot flash zip file, the signature verification failed. Any help here dud be great. Thx
A week ago I faced this error for the first time but didn't have the time to take a look at it so I just downloaded Air Droid as a temporary solution. But then more problem appeared. The battery indicator wasn't working so I decided to fix it somehow. To dig on Google. I tried flashing different ROMs and recoveries and on and on. the problem is that I'm now stuck on bootloader. I have no system installed and that crappy TWP won't start. The splash screen just flashes and that's all. So my phone is now a brick and I just don't have any more ideas. I need to lock my bootloader somehow so I can take it back to Samsung establish some kind of USB connection so I can install a new atleast,
Any help would be very much appreciated.
Zunex
anyone?
Zunex95 said:
anyone?
Click to expand...
Click to collapse
Hello,
I assume you are using a windows pc (correct me if i'm wrong)
Use this forum > http://forum.xda-developers.com/showthread.php?t=1901617 to install drivers for your nexus s.
Afterwards, reboot your PC
Do you have adb installed? If so skip this part:
Install minimal adb and fastboot using this forum > http://forum.xda-developers.com/showthread.php?p=42407269
Try inputting fastboot devices into the terminal window and see if your device shows up
Then you can flash everything back to stock. You can do this by following the following steps:
Go to this link and download the appropriate files for your nexus s >https://developers.google.com/android/nexus/images
Use a program such as 7-Zip to open and uncompress the package to a folder of your choosing
Navigate to that folder and try clicking flash-all.bat
Hopefully that will flash your whole phone back to stock. If not you will have to manually flash each part. Do this by typing the following into the terminal, one by one, replacing the file names with the appropriate ones for your nexus s.
fastboot flash bootloader bootloader-crespo-i9020xxlc2.img
fastboot reboot-bootloader
fastboot flash radio radio-crespo-i9020xxki1.img
fastboot reboot-bootloader
fastboot -w update image-soju-jzo54k.zip
For example, for the first line of code, I would go into the uncompressed folder and hold down shift while right clicking the bootloader file. I would then select “copy as path”. Then I would go back to the terminal and type “fastboot flash bootloader ” then paste the path I just copied. I would then repeat for the rest of the items.
Feel free to ask questions if it does not work. Ill try to reply as soon as possible. Cheers.
Thanks I solved it. The problem was with my phone's USB port. Atleast the usb module/part of the port. I put a little metal in it then moved it around a couple times.. tried to save it. Somehow I got it working again, so I instantly flash a working recovery then went back stock. I returned my device to Samsung (It was under warranty) and they fixed it.
Cheers
hey guys i have a question.. i made a total n00b mistake and now i am not sure what to do..
I have a htc one s
-i rooted the phone and put twrp 2.8 the newest one then i tried to load a custom rom.. i read somewhere on line that you did not need s off to do this so i tried and now everytime the phone boots it loads the htc screen but goes to a black screen which is kind of dim .. anyway my bootloader is unlocked its version 2.15 and i can get back in to my recovery and mount it i tried several roms but none work.. i was wondering if someone here has a stock rom or something that can get my phone to boot in to a os.. i have tried using fastboot to try and s off but everywhere i read it says u need debugging on my drivers are installed correctly but when u do adb devices it shows empty space.. ive tried many drivers even the google generic i cannot get it to work for the life of me... any help will be appriciated
cheers
Sam
Well let's take it easy. There were some things you've missed when reading so that's why you run into problems.
First thing you missed is that YOU MUST FLASH THE KERNEL IN FASTBOOT if you're S-On. That is EVERYTIME you flash a ROM.
Second, when you're in fastboot, you won't have "ADB devices" command working, you'll have to use "fastboot devices" command instead, ADB does not work while in fastboot.
What you'll have to do is like this:
1. Take any ROM you'd like to flash, place it on your sdcard (while you're in recovery you can mount sdcard to be accessible from pc)
2. Extract from the rom and save it on your pc (in the same folder where adb/fastboot commands are, usually /android-sdk/platform-tools) the "boot.img" file that's in the root of the ROM zip. That'll be called generic "the kernel".
3. Flash the ROM in recovery
4. Reboot to bootloader then while still connected to pc via USB, select fastboot mode. On your screen the "fastboot USB" will be shown.
5. Check if fastboot drivers are installed and fastboot commands are working by issuing "fastboot devices" command. If it'll not return your device then check if drivers are installed properly and you are not using an USB 3.0 port on windows 8.1 (were reported some issues with this configuration).
6. Having fastboot working, open command prompt in the location where fastboot is (and where you have saved the boot.img file) and issue the command: "fastboot flash boot boot.img"
7. Reboot
Now your new ROM should boot and work. Pay attention to choose the right ROM for your hboot and don't forget to do these steps EVERYTIME you're flashing a ROM.
If you're still looking for a stock ROM to flash, there's a thread with all RUUs linked, choose the one for your carrier or model type and run that one but I guess you won't need that
Good luck
Sent from nowhere over the air...