Related
Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???
Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.
matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!
Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
when you say perm root you mean s-off right?
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
sinistersai4d4d said:
Yes, perm root using the root tool. I believe that's S-off... but I'm not certain.
Click to expand...
Click to collapse
its not s-off, go here to get s-off
http://forum.xda-developers.com/showthread.php?t=1576672
my HTC MyTouch 4G Slide using Tapatalk 2
gtmaster303 said:
Over 500 posts and people still don't know what threads to post questions in...
Thread reported
Click to expand...
Click to collapse
Badass
Sent from my myTouch_4G_Slide using xda premium
Let me take advantage of this newb. I got my new device, S-On Unlocked. I restored my modded version of stock and using blues UV 5% kernel. Wifi wont work, and my camera has weird lines on it. But the pics are still good. I just needa fastboot the boot.img righ'?
sinistersai4d4d said:
Apologies in advance if this is the wrong forum.
Today I successfully perm rooted my Doubleshot...
Then I tried to flash CM9 Alpha 5 using CW recovery.. downloaded the .zip...
Flashed it.. hit reboot... and it wont get past the mytouch splash screen.
I've tried flashing other roms, and other alphas.. but they all don't reboot into the rom.
I can still boot into recovery and get into ClockWork..
Any ideas on what I can flash or do to at least get any rom running on here... I'm not even picky at this point... I just wanted something like CM7 or some AOSP.
Thanks in advance.
Click to expand...
Click to collapse
1) This goes in General. I don't know why the mods can't just add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
blackknightavalon said:
1) This goes in General. I don't know why the mods just don't add a Q&A board to remove the n00b confusion.
2) Fastboot the ROM's boot.img before booting up.
Click to expand...
Click to collapse
Ok, I'm def S-ON but unlocked and nperm rooted.
Can someone walk me through what to do? How can I fastboot the rom's boot.img?
I'm sorry I'm new to this, that's why I'm using my secondary device to learn. I've been googling anything I can find and it got me to through the root process but now I'm stuck.
xmc wildchild22 said:
im assuming he's s on....remember to take the boot.img out of the cm9 zip and flash it using fastboot. You can find out more info on how to do it here. Also apology accepted (this should be in general)
Click to expand...
Click to collapse
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
sinistersai4d4d said:
This something I have to do with a PC (as opposed to Mac)? No way to unbrick this thing without methods like this? Just asking, before I try and commandeer a pc.
Click to expand...
Click to collapse
Did you not read the stickies?
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Sent from my SGH-T959V using Tapatalk 2
wesomatic said:
You have to take the bootimage from the rom that you are using and put in a folder and name it so you can reconize it. You follow the command prompt instructions they give in this thread. You have to have some knowlege of a PC in order to be successful. I had the same problems as you did. You can get it to work... Do you know how to use the command prompt for your PC?
Click to expand...
Click to collapse
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
sinistersai4d4d said:
Not really. But I guess I'll start there...
And thanks for everyone's help. Here goes nothing.
Click to expand...
Click to collapse
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
AgentCherryColla said:
You can just flash back to stock to fix it. Learn to fastboot, then run CM9.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
*UPDATE*
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
sinistersai4d4d said:
Thanks again for all your help...
Last question before I fastboot, is it necessary to have the SDK or ADB to fastboot? Can I fastboot/flash the kernel using Hasoon's all-in-one-kit (the app I used to attain root)? Or is it too late since now the device wont boot and Hasoon "can't find the device"?
I have the boot.img I want in a place where I can locate it. Can I use the command prompt without the SDK/ADB?
Click to expand...
Click to collapse
Of course not. 'Fastboot' is an 'ADB' command. BUT if Hasoon's tool 'can't find device'....that's an ADB error message and you probably don't have all the drivers installed that you need but he has the necessary files included for what you need for 'Unlocked" & recovering from a mess-up. You may as well go ahead & install ADB tho....you'll eventually need it.
---------- Post added at 10:12 AM ---------- Previous post was at 09:59 AM ----------
sinistersai4d4d said:
Interestingly enough I was able to mount using recovery, and boot a new kernal... phone won't boot but at least it's stuck at a different splash screen lol "mikroms"..
I'm calling this progress.
Ok, got it!
I mounted the phone to my computer using recovery and used the Hasoon kit to flash the CM boot image.. then I rebooted and got the mikroms splash screen. That was because the last zip i flashed wasn't CM.. it was the MikRom..
so I went back into recovery, flashed CM.. now I'm good!
Click to expand...
Click to collapse
I believe what you did is 'Flash' a ROM from MikROMs but the kernel didn't go because you have S-On. Take that same '.zip' you just flashed, look inside it and put the file named 'boot.img' where you can find it in the windows 'path' and THEN
'fastboot flash boot boot.img' http://forum.xda-developers.com/showthread.php?t=1508556
You should boot up fine then.
hey need some help have succesfully rooted my phone but after flashing trickdroid rom my phone got stuck on the white htc screen.. i believe i have since wiped everything.. i now get unable to mount sd card messages and waiting for device messages when ever i now try do anything including flashing a stock rom. i have tried using the all in one tool and i re locked my bootloader through it but now cant re unlock it.. i can use the tool to reboot my phone into bootloader and recovery modes.. but not to do any sort of flashing, have read numerous posts and threads but no luck. Please help
nj_mills said:
hey need some help have succesfully rooted my phone but after flashing trickdroid rom my phone got stuck on the white htc screen.. i believe i have since wiped everything.. i now get unable to mount sd card messages and waiting for device messages when ever i now try do anything including flashing a stock rom. i have tried using the all in one tool and i re locked my bootloader through it but now cant re unlock it.. i can use the tool to reboot my phone into bootloader and recovery modes.. but not to do any sort of flashing, have read numerous posts and threads but no luck. Please help
Click to expand...
Click to collapse
Are you using TWRP or CWM as your recovery?
twrp
You will not be able to flash any custom roms as long as your bootloader is locked. The most you can do with the locked bootloader is use an RUU to get back to stock. Which bootloader are you on now? 1.14?
my bootloader is unlocked at this moment. um would my bootloader be where it says.. hboot? if so its 2.13.0000?
Correct, the bootloader is an all white screen, with the radio, hboot and other such info at the top of it. Well you are good then. Just so we are clear you have a HTC One S S4 right, you dont have a HTC One S C2? Thats very important that we get that info correct, we don't want to brick your device.
im almost certain its a s4.. i got it from t mobile here in the uk any check i can do from the bootloader to confirm?
If you're not S-off, did you make sure to fastboot flash the kernel after flashing rom in recovery?
From my Evo LTE, yup.
im s-on, and no i dont believe i did no
how would i go about fixing that?
nj_mills said:
im s-on, and no i dont believe i did no
Click to expand...
Click to collapse
You should have read and followed the instructions in the OP of the rom you downloaded so.
Try flashing boot.img in fastboot mode with typing 'fastboot flash boot boot.img' in terminal window. Hope you're familiar with the platform-tools in android development kit...
Else download here and
follow the step by step instructions.
reboot into bootloader with your phone connected to you pc. make sure you are in Fasboot USB mode, it should say that in the bootloader screen. Move the boot.img from whatever rom you flashed and put it in the same directory as ADB and Fastboot. make sure its named boot.img. open a command prompt that points at that same directory as ADB and Fastboot, type
fasboot flash boot boot.img
Click to expand...
Click to collapse
and after its done type
fasboot erase cache
Click to expand...
Click to collapse
have tried that and still get stuck on the white htc screen saying this build is for development purposes....
thanks for trying so far
Is it still locked? And you're on custom recovery (twrp)?
You need to reflash the ROM you want. Then reboot into the boot loader from TWRP. Once there, follow my previous instructions.
Sent from my One S using xda app-developers app
it says unlocked at the top of the bootloader screen... and i have twrp installed yes
nj_mills said:
it says unlocked at the top of the bootloader screen... and i have twrp installed yes
Click to expand...
Click to collapse
Thats's already half the way. Please do what impostle says (reflash, reboot, etc.)
how can i get the rom onto my phone now that i cant access the phones internal folders?
Is the ROM not on your phone anymore? If not, just mount from TWRP and copy over.
Sent from my One S using xda app-developers app
---------- Post added at 01:45 PM ---------- Previous post was at 01:42 PM ----------
You guys need to start reading the whole guide before rooting and flashing.
Sent from my One S using xda app-developers app
twrp - mount - mount usb storage
Then copy that file to root or wherever you want.
Which TD version do you have?
Okay, so I decided to do something stupid and forget to backup my HTC One S while rooting. I installed CM10, and it got stuck in a bootloop, so stupid me decided to also do a factory reset and basically delete everything I needed to get out of it. I've tried numerous things, including ADB sideloading a ROM, but whenever I do that, it also gets stuck in a boot loop. I have no idea how to use RUU's, and if anybody could help me to fix my phone, that'd be really really helpful. I'm also kindof a n00b towards this stuff, so step-by-step instructions would be much appriciated Thanks.
~MuZiiX
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
CuzCrostyPwns said:
Is your device S-off and do you have supercid?
Then I believe you can just use any RUU file for your phone to get it back to stock.
A Ruu is basically a file that installs the stock ROM onto your device.
Find the Ruu you need here: http://forum.xda-developers.com/showthread.php?t=2094414
Just download it, connect your phone with a USB and run the Ruu file ( it's an .exe ) on your PC.
I hope this helps. Don't just listen to my advice. I'd wait till someone confirms my advice to be safe/correct. I'm still a bit of a noob after all who's trying to help and learn.
Click to expand...
Click to collapse
I think my device is s-off...i used the HTC One S all in one toolkit, and I have no idea what supercid is :s I've tried a couple RUU's before (don't know if i used them correctly, but i did relock the bootloader when i did it) but none of them helped. It just stayed at a black screen with "htc" in the middle. No error triangles or anything.
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
CuzCrostyPwns said:
Did you run the RUU files like you would run an .exe file on your pc with your phone connected by USB?
I'm not sure how your PC will recognize your phone when you're not in fastboot (bootloader).. Or am I misunderstanding something.
Wait. Can you get into your recovery? Do you still have that installed?
Click to expand...
Click to collapse
Yeah, the RUU's were .exe's with my phone connected through USB. I can get into recovery, I have CWM installed.
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
CuzCrostyPwns said:
I'm not sure if CWM has this option, but maybe you can mount your phone through recovery.
Then just place a new ROM on your SD card and flash it.
Click to expand...
Click to collapse
Well thats what I've been trying to do with the ADB sideloading, because it wont let me mount my sd card. It just says 'ERROR MOUNTING SD CARD" and when I've tryed flashing a new ROM from ADB sideloading, it just gets stuck in a bootloop again.
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
CuzCrostyPwns said:
My best bet is to run the RUU file.
To know which one is the correct one is to see which RUU title fits your phone's Stock 'settings' the best (ie: provider, country, android version)
---------- Post added at 08:42 PM ---------- Previous post was at 08:20 PM ----------
Oh and this thread should be moved to the Q&A forum I just realized
Click to expand...
Click to collapse
I've tried running multiple RUU files, and I have no idea what one to use. The phone when I got it was unlocked, and the android version was ICS I'm pretty sure.
I dunno how to find my stock settings because I cant get past the loading screen.
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
did you flash boot.img? most of roms will bootloop without it
Roundtableprez said:
Did you try flashing the boot.IMG from adb. It sounds to me, that since every ROM you try results in a bootloop that you did not flash the boot.IMG
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
the boot.img is located in the zip you downloaded from get.cm
NQNH said:
the boot.img is located in the zip you downloaded from get.cm
Click to expand...
Click to collapse
So what command would I use while flashing the boot.IMG file? (again sorry for not getting this, I just wanna get my phone working again)
MuZiiX said:
Pardon my stupidity, but what boot.IMG would I flash? As I stated before, I'm not that good at this kind of stuff :s
Click to expand...
Click to collapse
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Download or build from source
Download gapps
wipe unless you're upgrading from an earlier CM10 ROM
flash rom in recovery
flash gapps in recovery
unless you have s-off fastboot flash boot boot.img
Click to expand...
Click to collapse
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
dc211 said:
You failed to follow the instructions to install the rom. That is why you phone wouldn't boot.
Take your CM10 Rom and open it up. Inside you'll find a file called boot.img. Copy that file to the location where you installed the toolkit. Place it in the data folder there. Then open the toolkit and press the "flash a kernel" button. Just follow the instructions to flash the file.
You phone should now be fixed just reboot it.
Next time, make sure you read the instructions and if you aren't sure what's going don't move forward. Or use the search button. Finally, questions like this one go in the Q&A forum. :good:
Click to expand...
Click to collapse
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
MuZiiX said:
Thanks, I'll try that and see how it goes. I totally forgot to do a backup, and I now know that I should do one...and sorry, I'm kinda new to the forum and went here as a last resort.
Click to expand...
Click to collapse
It not really a big deal. Your problem is the most common one we see in Q&A. Also, once you finish flashing the boot.img keep in mind that CM10 can take a few minutes to boot the first time.
Also, just a heads up while the toolkits are helpful learning the command yourself actually lets do you a lot more things a lot faster.
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
CuzCrostyPwns said:
heres how to do it using fastboot:
Http://forum.xda-developers.com/showthread.php?t=1752270
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
MuZiiX said:
Thanks for the quick responses guys, I'm going to try that once I get home. Do I absolutely need USB debugging enabled? Because mine Isn't :s
Click to expand...
Click to collapse
Nope, just gotta do it one of the three ways mentioned. If debugging isn't enabled use option 1.
This can either be done via
1 powering off and keeping volume up & the power-button pressed
2 the extended power-menu (If your ROM has it, just select "reboot" & then "bootloader")
3 via adb, connect your phone with the pc, make sure it says "USB debugging connected", go to Android/platform-tools/ & then press shift while you perform a right click with the mouse, then choose "open prompt here", type
Click to expand...
Click to collapse
Hi everyone. I'm having some problems getting S-Off on my phone. I'm running CM10 and I'm trying to follow Facepalm's method. I've got the phone to the black htc screen from the bootloader by typing in "fastboot oem rebootRUU" but when I type in "fastboot flash zip PJ8312000-OneX.zip" I get a message that says "error: cannot load 'PJ8312000-OneX.zip': Unknown error". I've tried downloading and redownloading the file a bunch, but the error is still the same.
Now just to give you more info: I don't know too much about using adb or fastboot. I downloaded them as a package with SDK and just extracted it to my desktop. That's where I saved the PJ8312000-OneX file and the soffbin3 file too. Got the error. I tried moving the files to the "platform tools" folder in the SDK folder. Still got the error. I don't know if the SDK folder itself needs to go somewhere else or not.
Any help would be appreciated.
The files just need to be in the same directory as adb and fastboot.
Are you SuperCID?
iElvis said:
The files just need to be in the same directory as adb and fastboot.
Are you SuperCID?
Click to expand...
Click to collapse
Yes, I'm SuperCID. The files are in the same directory as adb and fastboot, but I'm still getting the same error. Checking them with md5 shows that the files are good too.
I don't know if this is relevant or not, but adb won't recognize my device either. I have to get to fastboot either using Quick Boot or holding volume down. Fastboot recognizes my phone in the cmd prompt, but adb won't. Like I said, that might be irrelevant though.
Try this: Reboot your phone and start from the beginning. Create a folder on your desktop and put the adb and fastboot files in there, with the soffbin and PJ file. Then try again. This worked for some people, though I'm not sure why.
Someone else reported success by unzipping the PJ file then rezipping it.
---------- Post added at 02:27 PM ---------- Previous post was at 02:23 PM ----------
PatC87 said:
I don't know if this is relevant or not, but adb won't recognize my device either. I have to get to fastboot either using Quick Boot or holding volume down. Fastboot recognizes my phone in the cmd prompt, but adb won't. Like I said, that might be irrelevant though.
Click to expand...
Click to collapse
I was having the same issue--adb devices returned nothing--but it made no difference. The commands still worked.
Sorry for dipping out earlier. Had to run out for a bit. Thanks for your help by the way.
Anyway, I've tried making the separate folder for adb and fastboot and that didn't work. I tried unzipping and rezipping the PJ file and its the same error.
Use a stockish sense Rom. Clean Rom or viperxl. That is what our phone is supposed to be running. Should help you out.
Sent from my HTC One X using XDA Premium HD app
Also for adb commands run it with phn booted into Rom when you get to reboot cmd it will take you into fastboot then when executed
Sent from my HTC One X using xda premium
As suggested, I would try flashing one of the stock rooted roms and see if that helps.
HTC ONE X s off error
PatC87 said:
Hi everyone. I'm having some problems getting S-Off on my phone. I'm running CM10 and I'm trying to follow Facepalm's method. I've got the phone to the black htc screen from the bootloader by typing in "fastboot oem rebootRUU" but when I type in "fastboot flash zip PJ8312000-OneX.zip" I get a message that says "error: cannot load 'PJ8312000-OneX.zip': Unknown error". I've tried downloading and redownloading the file a bunch, but the error is still the same.
Now just to give you more info: I don't know too much about using adb or fastboot. I downloaded them as a package with SDK and just extracted it to my desktop. That's where I saved the PJ8312000-OneX file and the soffbin3 file too. Got the error. I tried moving the files to the "platform tools" folder in the SDK folder. Still got the error. I don't know if the SDK folder itself needs to go somewhere else or not.
Any help would be appreciated.
Click to expand...
Click to collapse
Did you ever figure it out? im stuck at the same part
spinks420 said:
Did you ever figure it out? im stuck at the same part
Click to expand...
Click to collapse
On cm10 don't you have to give adb root access? I haven't run a cm Rom in ages but I think I've seen it discussed about allowing access in one of the setting screens.
Sent from my HTC One XL using xda premium
31ken31 said:
On cm10 don't you have to give adb root access? I haven't run a cm Rom in ages but I think I've seen it discussed about allowing access in one of the setting screens.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah that's right. In developer settings you must turn on usb debugging, and there is another option which is called root access I think. This option has apps only checked by default, you need to change it to apps and adb.
Sent from my Evita
also, if you're on 4.2 jellybean based rom, you will need to make sure that you have a newer version of adb, and that even after you have the debugging settings checked, that you check the checkbox on the phone when it tries to connect the first time. It was an added security "feature" (just double checked, has to be 1.0.31 of adb in this case)
http://android-developers.blogspot.com/2013/02/security-enhancements-in-jelly-bean.html has some more technical information about it....
HELPP
iElvis said:
The files just need to be in the same directory as adb and fastboot.
Are you SuperCID?
Click to expand...
Click to collapse
yes ive tried everything. idk if this is relevant but it says the zip file PJ8312000 is invalid. what can i do?
---------- Post added at 02:50 PM ---------- Previous post was at 02:44 PM ----------
31ken31 said:
On cm10 don't you have to give adb root access? I haven't run a cm Rom in ages but I think I've seen it discussed about allowing access in one of the setting screens.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
yeah but im curently on the viperxl rom im trying to get cyanogenmod 10 but i have to s off first then downgrade the touch panel cause i took the ota and my hboot is 2.14. and i keep getting stuck at the step of s-off where you have to upload the zip file PJ8312000-OneX.zip
spinks420 said:
yes ive tried everything. idk if this is relevant but it says the zip file PJ8312000 is invalid. what can i do?
---------- Post added at 02:50 PM ---------- Previous post was at 02:44 PM ----------
yeah but im curently on the viperxl rom im trying to get cyanogenmod 10 but i have to s off first then downgrade the touch panel cause i took the ota and my hboot is 2.14. and i keep getting stuck at the step of s-off where you have to upload the zip file PJ8312000-OneX.zip
Click to expand...
Click to collapse
Press and hold power on your phone until it shuts off, then after it reboots, try again.
exad said:
Press and hold power on your phone until it shuts off, then after it reboots, try again.
Click to expand...
Click to collapse
still the same problem is says no such directory exists for the s-off bin files and for the zip it just says cannot load and an error has occurred. but thank you. can you think of anything else i might try?
spinks420 said:
still the same problem is says no such directory exists for the s-off bin files and for the zip it just says cannot load and an error has occurred. but thank you. can you think of anything else i might try?
Click to expand...
Click to collapse
Yeah they're not in the directory with ADB and fastboot.
exad said:
Yeah they're not in the directory with ADB and fastboot.
Click to expand...
Click to collapse
they are in the same folder as adb and fastboot which ive named Android-adb and placed in the root of my C:\drive and i then went into my computer settings and added the folder path to the paths. so my adb and fastboot are working fine they issue commans correctly and everything but it wont flash those files.
spinks420 said:
says no such directory exists for the s-off bin files
Click to expand...
Click to collapse
That means they are not in your dirctory with ADB and fastboot. If you did not unzip them into that folder, that constitutes as not being in that folder.
exad said:
That means they are not in your dirctory with ADB and fastboot. If you did not unzip them into that folder, that constitutes as not being in that folder.
Click to expand...
Click to collapse
i tried unzipping soffbin into the directory and it still didnt work and it wont open the pj8312000.zip it says the file is invalid. and ive downloaded it from multiple sites and it says the same thing for every one.