I am trying to reinstall the RUU but I believe bc I have CWM installed, it won't work. I tried different things and I am stuck. I know my PC recognizes the device b/c adb devices find the device. Is there a way I can send an image thru fastboot or something to the phone that would install the RUU image and restore my phone to stock form factor? Or is there anything else that I can try?
Thank you.
crazycray said:
I am trying to reinstall the RUU but I believe bc I have CWM installed, it won't work. I tried different things and I am stuck. I know my PC recognizes the device b/c adb devices find the device. Is there a way I can send an image thru fastboot or something to the phone that would install the RUU image and restore my phone to stock form factor? Or is there anything else that I can try?
Thank you.
Click to expand...
Click to collapse
Why not search for a PG58IMG?
Sent from my Sensation using Tapatalk 2
matt95 said:
Why not search for a PG58IMG?
Sent from my Sensation using Tapatalk 2
Click to expand...
Click to collapse
Okay, how do I do that after I find it?
push adb PG58IMG? and where can I find the default one? Thank you
Also, I think when I do a hard factory reset w/ volume down+power, it just loads up an older ROM. Any idea why?
PG58IMG.zip
crazycray said:
Also, I think when I do a hard factory reset w/ volume down+power, it just loads up an older ROM. Any idea why?
Click to expand...
Click to collapse
Is your phone rooted ?
If you put a PG58IMG.zip (make sure it's the right one for your phone), in your SD card, it will automatically flash it in fastboot, before doing enything else.
Just make sure you rename it (or delete it) after the procedure is done, otherwise everytime you go to fastboot it will automatically flash it again, and again...
Yes, it used to be rooted. It might not be anymore..
I believe the PG85IMG.zip file that I have on my microSD is the file for CWM? I can't remember if I replaced it w/ the original after I completed the root.
I can't seem to find the original PG85IMG.zip file anywhere on xda...
Finding your PG85IMG.zip + RUU
Ok, based on your CID, find the right PG85IMG.zip for your phone here
http://forum.xda-developers.com/showthread.php?t=1459767
Then, *if* you have SuperCID, you can download the right RUU from here, and intall the .exe
http://www.filefactory.com/f/c87a2330449af512/
codebr4k3r said:
Ok, based on your CID, find the right PG85IMG.zip for your phone here
http://forum.xda-developers.com/showthread.php?t=1459767
Then, *if* you have SuperCID, you can download the right RUU from here, and intall the .exe
http://www.filefactory.com/f/c87a2330449af512/
Click to expand...
Click to collapse
Okay. I will see if this works. Last time I was trying some fastboot or adb commands, it said "waiting for device" and nothing happened. Any idea what might be causing that?
"waiting for device"
crazycray said:
Okay. I will see if this works. Last time I was trying some fastboot or adb commands, it said "waiting for device" and nothing happened. Any idea what might be causing that?
Click to expand...
Click to collapse
That usually has to do with outdated drivers. Make sure you have the latest HTC Sync installed on your computer. That will also provide the latest drivers for your device.
Then sync your phone with HTC Sync (so that HTC Sync detects it).
Open the terminal, and go to the directory where you use adb.
Then try the adb commands
SuperCID commands in case it's not SuperCID:
(You will need it in case you get a "InvalidID" error while installing a RUU.)
>> adb reboot-bootloader
>> fastboot oem writecid 11111111
>> fastboot reboot-bootloader (Wait for it to reboot)
>> fastboot getvar cid (it should confirm your CID is 11111111)
>> fastboot reboot"
codebr4k3r said:
That usually has to do with outdated drivers. Make sure you have the latest HTC Sync installed on your computer. That will also provide the latest drivers for your device.
Then sync your phone with HTC Sync (so that HTC Sync detects it).
Open the terminal, and go to the directory where you use adb.
Then try the adb commands
SuperCID commands in case it's not SuperCID:
(You will need it in case you get a "InvalidID" error while installing a RUU.)
>> adb reboot-bootloader
>> fastboot oem writecid 11111111
>> fastboot reboot-bootloader (Wait for it to reboot)
>> fastboot getvar cid (it should confirm your CID is 11111111)
>> fastboot reboot"
Click to expand...
Click to collapse
Dude, thanks so much for all the help. I am at work but will try all this stuff out when I get home from work. I hope this works.
Does SuperCID get removed after installing the RUU? I'm certain I did not do that step when I first followed the guide b/c it was kind of over my head at the time
crazycray said:
Dude, thanks so much for all the help. I am at work but will try all this stuff out when I get home from work. I hope this works.
Does SuperCID get removed after installing the RUU? I'm certain I did not do that step when I first followed the guide b/c it was kind of over my head at the time
Click to expand...
Click to collapse
No worries, anytime
No, you SuperCID once, then it stays... till you throw your phone off the window, or , i don't know But it stays
codebr4k3r said:
No worries, anytime
No, you SuperCID once, then it stays... till you throw your phone off the window, or , i don't know But it stays
Click to expand...
Click to collapse
Does that void warranty?
crazycray said:
Does that void warranty?
Click to expand...
Click to collapse
Hmm, i guess no, because you can restore your original CID with the command:
>> fastboot oem writecid xxxxxxxx
(where xxxxxxxx will be your original CID)
Just make sure you make a note of your original CID, before making the whole procedure. Get it again with:
>> fastboot getvar cid
codebr4k3r said:
That usually has to do with outdated drivers. Make sure you have the latest HTC Sync installed on your computer. That will also provide the latest drivers for your device.
Then sync your phone with HTC Sync (so that HTC Sync detects it).
Open the terminal, and go to the directory where you use adb.
Then try the adb commands
SuperCID commands in case it's not SuperCID:
(You will need it in case you get a "InvalidID" error while installing a RUU.)
>> adb reboot-bootloader
>> fastboot oem writecid 11111111
>> fastboot reboot-bootloader (Wait for it to reboot)
>> fastboot getvar cid (it should confirm your CID is 11111111)
>> fastboot reboot"
Click to expand...
Click to collapse
So, I still got the waiting for device message. I was able to writecid 11111111 and i believe it was successful, but when i type the command again, it doesn't work and i get the waiting for device message. I am not able to get HTC Sync b/c I have a non sense ROM installed. Furthermore, I cannot get the RUU to reset the phone. Just says "Rebooting to Bootloader" and then I get an Unknown Error and it says ROM Update Utility cannot update my phone.
crazycray said:
So, I still got the waiting for device message. I was able to writecid 11111111 and i believe it was successful, but when i type the command again, it doesn't work and i get the waiting for device message. I am not able to get HTC Sync b/c I have a non sense ROM installed. Furthermore, I cannot get the RUU to reset the phone. Just says "Rebooting to Bootloader" and then I get an Unknown Error and it says ROM Update Utility cannot update my phone.
Click to expand...
Click to collapse
Hmm, that's sounds confusing :$
Right, you said that command: fastboot oem writecid 11111111 , worked ?
Ok, could you tell me your HBOOT version ? (when you're in the bootloader)
Related
my phone info
hboot 1.18.0000
radio 10.14.9035.01_M
image 1.45.401.2
its not getting even stock rom with same image version
ruu says
trying to reboot in bootloader .............
but no luck
ever tried with htcdev bootunlock method to S-Off
gots this
fastboot oem get_identifier_token
C:\sdk>fastboot oem get_identifier_token
Program too big to fit in memory
Try to go fast-boot and run ruu should work.
If not take out the battery and hold volume down and swith on,run recovery or fast-boot and then run ruu.
yes i have done that too
in fastboot ruu runs and read info of my set (which show that its conected with pc)
but when ruu tried to reboot in bootloader
it takes almost 30 minutes then error comes of usb conectivity
problem is that bootloader are locked
it shows when pluged in fastboot mode
"Locked"
It will do, that's completely normal
i think still a driver problem with your laptop.
download the official one from HTC, just following the installation and STOP the installation when it wants you in install HTC SYNC!!
EddyOS said:
It will do, that's completely normal
Click to expand...
Click to collapse
what will do what ???
i could'nt get that
Rawahi said:
i think still a driver problem with your laptop.
download the official one from HTC, just following the installation and STOP the installation when it wants you in install HTC SYNC!!
Click to expand...
Click to collapse
tried on three different systems with three differernt os and checked all drivers
it does'nt make sense that its a conectivity problem
cuz ruu shows all info of my set. so its conected in fastboot with pc
Dear xda-community,
as said in the title i dont know if i bricked my device by trying to get s-on again.
At first i read some threads here about getting s-on again and revert to stock.
I was s-off by revelutionary and flashed the ENG-hboot a few days ago (0.98.2000). After that i flashed the stock 1.47 rom and was trying to get s-on and stock again with the 1.47 RUU. I read that if i have the ENG-hboot i can run the RUU and then i get back to stock and s-on. But after i was running the RUU, i get to the bootloader again (on the phone). In the header stands now "*** Security Warning ***" and i'm s-on again like i want it with hboot 0.98.0002.
But the problem is that i cant get out of the bootloader, i can only acsses fastboot and the bootloader. If i click 'recovery', 'reboot' or anything else it only restarts the bootloader. I cant even turn the phone off, only with pulling the battery :/
So i'm stucked in the hboot 0.98.0002 with s-on and i dont know what i can do now or if i bricked my desire s permanently
Can anyone help me please?
are you sure that you have used the right RUU?
amidabuddha said:
are you sure that you have used the right RUU?
Click to expand...
Click to collapse
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Jahai said:
yes, i used the htc_saga_europe... 1.47 and im on a unbranded phone, so this is the right, isnt it?
Click to expand...
Click to collapse
It should be if you bought it in Europe. What happens when you try the RUU again? You should do this when "FASTBOOT USB" is written on your phone screen.
amidabuddha said:
It should be if you bought it in Europe. What happens when you try the RUU again?
Click to expand...
Click to collapse
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Jahai said:
yes, i bought and use it in germany. if i try it again it get aborted after receiving the information from the phone and tells me something about a error 140: bootloader error and in the manuel isnt an entry for error 140 :S
Click to expand...
Click to collapse
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
amidabuddha said:
Ok there is what you can do:
run RUU without a connected phone. Let the screen open. Go to WIndows Explorer, C drive and type in the search box : rom.zip. When you find it copy it to another place and close the RUU window.
Then extract from the rom.zip these images: system.img, boot_signed.img, recovery_signed.img
If you do not have fastboot command use the Guide in my signature. Then in cmd on your PC with phone in "fastboot usb" mode type:
Code:
fastboot flash system {path to the file}\system.img
fastboot flash boot {path to the file}\boot_signed.img
fastboot flash recovery {path to the file}\recovery_signed.img
where {patho to the file}\ should be replaced with the the actual path to the file from your Windows Explorer (like C:\android\images)
then, if the flashing is successful try to reboot to OS (wait several minutes on the white screen it can take some time to load)
This solution is taken from here, credits to degit
Click to expand...
Click to collapse
thank you for your help!
i will try that and report back in a few minutes
hm
i cant get it to work in this way :/
if i write fastboot flash system C:\android-tools\system.img
it tells me:
"sending 'system' (571388 KB)...
OKAY [93.130s]
writing 'system'...
(bootloader) signature cheking...
FAILED (remote: signature verify fail)
finished. total time: 166.095s"
its the same with boot_signed.img and recovery_signed.img
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
So you problem maybe sounds the same, but it is not.
Try
Code:
fastboot oem rebootRUU
Your phone will reboot to a black screen with silver HTC logo. Then run the RUU.
Other options is to go to the repair centre and tell them that this happened during OTA update.
Sent from my HTC Desire S using Tapatalk
Jahai said:
if i try fastboot getvar version-main i get : 11.10.401.4
think there is a typo, shouldnt it be 2.10.401.4? could it be this and if yes how could i change it?
Click to expand...
Click to collapse
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
amidabuddha said:
Hmm that's new. Have you flashed a new radio recently? Anyway try the latest RUU 2.10.401.8.
Sent from my HTC Desire S using Tapatalk
Click to expand...
Click to collapse
will try it with that. since now i tried it until 2.10.401.4
Edit: it took me ages to download that ruu from filefacrtory :/
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Jahai said:
i got the same error 140 with the last 2.10.401.8 RUU
looks like it is stucked in that bootloader for ever
Click to expand...
Click to collapse
Go to repair center and say that the OTA update did this (it is the same as RUU) They should repair it for free
Sent from my HTC Desire S using Tapatalk
maybe there is any way to get s-off from fastboot or bootloader?
got to new hboot with this instruction: http://forum.xda-developers.com/showpost.php?p=20850548&postcount=22
managed to get the unlocktoken from htcdev but if i flash it everything themes fine, but i cant choose the option yes (unlock bootloader).
if i choose "no" and press the power button it reboots like it should but if i choose "yes" and press the power button nothing happens. i can still choose between the options but nothing happens :/
anyone know how i can get it working to unlock this bootloader and flash a custom recovery?
Hi,
I need to make an unROOT and I cannot find original stock ROM for my 9023i Nexus S. I went through a lot of threads but there is no original ROM. I need to send it to servis and use warranty - so I probably need 2.3.3. I tried look for in out of xda and downloaded something that has 4MB - it does not work.
Please, if you have it, send me a link. Thank you!
forum.xda-developers.com/showthread.php?t=1063664
for unrot use youtube and google..
once you flash stock rom for your device with link from post above this one it will unroot and give you stock recovery
sean1984 said:
once you flash stock rom for your device with link from post above this one it will unroot and give you stock recovery
Click to expand...
Click to collapse
I read this. But what happend was, that I flashed it and the lock was opened at start - and when I got into the system, there were a lot of canceled processes and I couldnt continue Now I probably need to root it again (I hope it will work) but I dont know what to flash
EDIT: Great. I cannot get into system so I cannot enable debugging, - so I cannot root it again and eve get into system AND there is no recovery Only thing I can do is to connect USB cable and open disk in PC
Is there any way to push from bootloader recovery through adb???
Why would you flash 2.3.3 ? leting your device "officially" update to 2.3.6 or even ICS (if you're I9020T) isn't a guilt lol ..... Anything official and a locked bootloader , unrooted would be fine for warranty purposes ...
mahanddeem said:
Why would you flash 2.3.3 ? leting your device "officially" update to 2.3.6 or even ICS (if you're I9020T) isn't a guilt lol ..... Anything official and a locked bootloader , unrooted would be fine for warranty purposes ...
Click to expand...
Click to collapse
Never mind. I managed to get there 2.3.4. When the device comes back I root it again so no need to update right now.... anyway, I cannot relock it it does not have to be locked?
EDIT: I'd rather had it locked, just in case.... but I cannot relock it. I tried to use sdk, write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English)
devcager said:
Never mind. I managed to get there 2.3.4. When the device comes back I root it again so no need to update right now.... anyway, I cannot relock it it does not have to be locked?
EDIT: I'd rather had it locked, just in case.... but I cannot relock it. I tried to use sdk, write "adb reboot bootloader" and then " fastboot oem lock" but both case the command line responded something like that it is not internal command etc. (I dont have it in English)
Click to expand...
Click to collapse
While you're in fastboot mode and connected to your PC , run "fastboot oem lock" .... This should lock it unless you're having another issue ...
mahanddeem said:
While you're in fastboot mode and connected to your PC , run "fastboot oem lock" .... This should lock it unless you're having another issue ...
Click to expand...
Click to collapse
"run fastboot oem lock" means to put it in a command line? Because it does not work. Or it is a program??
devcager said:
"run fastboot oem lock" means to put it in a command line? Because it does not work. Or it is a program??
Click to expand...
Click to collapse
it means you go into your command prompt , guide your way to where you put your sdk tools with the fastboot command, and then run the command from there.
so basicly start > run > cmd , and from there find go to your directory where you placed your android sdk tools.
kwaidan said:
it means you go into your command prompt , guide your way to where you put your sdk tools with the fastboot command, and then run the command from there.
so basicly start > run > cmd , and from there find go to your directory where you placed your android sdk tools.
Click to expand...
Click to collapse
I do exactly this... It does not work. when in command prompt I put "cd android-sdk-windows" and get there. then I put "fastboot oem lock" and it tells what I wrote in previous posts :/
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
lileddy305 said:
question.. i was told i need a late firmware version in order to use ics roms so i decided to do it but idk why my device cant be found via cmd
i have s off
and hboot 1.27.1100
eMMC boot
i think i bricked my phone cause w.e. rom i install it just keeps looping. idk what to do?
there is no way my phone is being recognized by windows the device is not found and i cant even find a way to put it back to stock someone please help :/
at least i need to put s-on and remove recovery so i can send it back to t-mo but i cant do anything via adb. please im really willing to donate the person that helps me please
Click to expand...
Click to collapse
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Have you tried starting your phone and trying to get into your bootloader so you can run fastboot? or even make it into recovery to restore a back up or different rom? Make sure you have the most updated driver for your phone. You can also put your SD card in another phone or in your computer and put the firmware version on the root of your card, put it in your phone, run your hboot and let it update by itself. Between these two options you should be able to resolve your problem.
Or because I posted like 5 seconds after the guy above... Do what he ^ said
ganeshp said:
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Click to expand...
Click to collapse
hi, i did as you said but when i type adb devices it just goes blank. i get no device recognized but yea i am able to get to the bootloader
lileddy305 said:
hi, i did as you said but when i type adb devices it just goes blank. i get no device recognized but yea i am able to get to the bootloader
Click to expand...
Click to collapse
read my post again ..did i said adb devices ??? NO i said fastboot devices ..that too this needs to be done with phone in bootloader connected to pc
ganeshp said:
read my post again ..did i said adb devices ??? NO i said fastboot devices ..that too this needs to be done with phone in bootloader connected to pc
Click to expand...
Click to collapse
oh ok sorry i read wrong, ima do that right now.
btw when this works you better have a donate button lol
thank you so much for your help
ganeshp said:
you can go to bootloader right ...then no worries ..you are NOT BRICKED ...
i presume you got GB rom running ..so thats why after flashing the latest firmware ..your device is bootlooping ...
no worries
if you can go to bootloader ...connect the device to pc from there (phone reads fastboot usb after this)
and in adb folder ...open command window there and ..type this "fastboot devices" without quotes.it should show your device
(remember adb wont work ..when in bootloader only fastboot does)
now type this "fastboot getvar all"
and post the complete output here ...except IMEI and SERIALNO
I'll guide you further
Click to expand...
Click to collapse
ok so here are the results that i got
ok i understand your situation completely
you need to flash the 3.32 unlocked firmware
then you need to flash 4EXT recovery
then you need to go to recovery and then flahs the ROM
in order to do that ...this is the perfect guide
FLASH 3.32 FW and ROM
follow the post#1 and post #2 to the letter
then at the end you will come out fine
if you got any problems ..you can post back here ..I'll help you (or simply click the IRC HELP CHANNEL present in my signature and join that ..I'll be online there )
Also donation is not really required a simple thanks to my posts are enough ..but if you do feel like donating ..its much appreciated
I am new to htc
i am flashing a custom rom for first time on htc
what do i have to know?
and what is needed?
and i am stuck on soft brick and cant mount internal storage
i am using
hboot 2.15
it shows tampered
and twrp 2.8
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Rapier said:
Tampered is shown because you probably unlocked your bootloader on the HTC dev site (which is the first thing you should do anyway)
Now, taking in consideration what you said in the Candy thread, can you enter in fastboot mode? You can do this by entering in bootloader (with phone off, keep pressed the vol down and press power). On the bootloader screen navigate with vol up/down and select with power button. Enter fasboot from there and while you connect the phone to pc via USB you should notice on uour screen a line saying "fastboot USB"
After this you shoul be able to flash the kernel in that mode. You should have ADB installed for this on your pc (it is done by installing the Android SDK) and the ADB/fastboot drivers working.
Let us know how it goes so far then we can go further
Sent from nowhere over the air...
Click to expand...
Click to collapse
Do i need to s off
and ive noticed that even after flashing rom system folder is empty except for bin and by the way my device is t mobile
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Rapier said:
S-off is not mandatory but is good to have as the whole flashing process will be much easier. Is it somewhere in the bootloader screen written UNLOCKED? Above or below the "tampered"...
Sent from nowhere over the air...
Click to expand...
Click to collapse
unlocked yes i did it but i cant flash the rom it wont be pushed into system at all
please my mind is not clear can you give me a link for kernal pleaseee
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
ive restored from ruu
Rapier said:
Kernel that you must flash in fastboot is the file boot.img located in the system folder in the ROM"s zip....that is, you'll have to open the zip you're flashing, go to system and extract that boot.img file. Save it on your pc in the same location where fastboot and adb are installed then open a command prompt there. You can flash it using the "fastboot flash boot boot.img" command
Edit: Here's an XDA tutorial how to do it in detail
http://forum.xda-developers.com/showthread.php?t=1752270
Sent from nowhere over the air...
Click to expand...
Click to collapse
Why my device wont s-off its always telling me to f***off
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
What RUU Worked?
eswarvf said:
Why my device wont s-off its always telling me to f***off
Click to expand...
Click to collapse
În order to properly s-off, you might need a certain ROM to be installed. Have you tried to get s-off having that stock ROM you got after RUU?
Sent from nowhere over the air...
Can s-off be achieved without an installed ROM?
bobby2x420 said:
Can s-off be achieved without an installed ROM?
Click to expand...
Click to collapse
Only by a j-tag device but I don't know how that works. The software methods presented here needs a ROM as far as I know
Sent from nowhere over the air...
bobby2x420 said:
What RUU Worked?
Click to expand...
Click to collapse
Ya it worked (not androidruu though) i had to search a lot i got tired of it