Related
Hey All,
Long time reader, first time Soft Bricker. I was flashing the Z Kernel 2.0 over Viper, and am now in a bootloop that doesn't let me get into my Recovery (TWRP). I can get into bootloader, though, and run fastboot. I've read the instructions on how to fix this error by flashing the RUU, but I can't find a link to an RUU where there isn't a $12 fee.
Is there another way to do it? I backed up my stock One S from after I rooted.
Help?
Thanks!
MrPickleFicker said:
Hey All,
Long time reader, first time Soft Bricker. I was flashing the Z Kernel 2.0 over Viper, and am now in a bootloop that doesn't let me get into my Recovery (TWRP). I can get into bootloader, though, and run fastboot. I've read the instructions on how to fix this error by flashing the RUU, but I can't find a link to an RUU where there isn't a $12 fee.
Is there another way to do it? I backed up my stock One S from after I rooted.
Help?
Thanks!
Click to expand...
Click to collapse
Open the zip file for viper rom and extract the boot.img file and move it to the folder on your computer where adb.exe is. Then get into the phone into fastboot connect it to your computer and run this command. "fastboot flash boot boot.img"
That should get you back into viper.
dc211 said:
Open the zip file for viper rom and extract the boot.img file and move it to the folder on your computer where adb.exe is. Then get into the phone into fastboot connect it to your computer and run this command. "fastboot flash boot boot.img"
That should get you back into viper.
Click to expand...
Click to collapse
Thanks, going to take approximately 24 minutes while I wait for the Zip to download then I'll post results. Is Viper different in some way? I've flashed probably 50 roms (including an earlier version of Viper) and haven't run into boot.img issues as long as I've flashed a kernel with it. On H-Boot 1.08.
MrPickleFicker said:
Thanks, going to take approximately 24 minutes while I wait for the Zip to download then I'll post results. Is Viper different in some way? I've flashed probably 50 roms (including an earlier version of Viper) and haven't run into boot.img issues as long as I've flashed a kernel with it. On H-Boot 1.08.
Click to expand...
Click to collapse
You can just pull boot.img from your original download of Viper Rom if it's still on your computer. The reason i suggested that you flash the boot.img is because you said you only have access to fastboot and your problems started with you flashed a new kernel. Since the boot.img from the rom will contain the original viper kernel it should reverse your problem.
dc211 said:
You can just pull boot.img from your original download of Viper Rom if it's still on your computer. The reason i suggested that you flash the boot.img is because you said you only have access to fastboot and your problems started with you flashed a new kernel. Since the boot.img from the rom will contain the original viper kernel it should reverse your problem.
Click to expand...
Click to collapse
I didn't download the rom on my computer the first time around, just had it on my phone's "SD Card". So with our snail mail up here have about 10 minutes left on my computer download. Hoping this works!
You da man! Thanks a ton! Hopefully I'll be able to return this favor to someone else in the future.
MrPickleFicker said:
You da man! Thanks a ton! Hopefully I'll be able to return this favor to someone else in the future.
Click to expand...
Click to collapse
Glad it worked out for you. :good:
Hey guys!! I was thinking about flashing the Blackout Beast Mode 3 to my phone thats runnig viper xl. I just wanted to make sure there're compatible and I also want to know if I have any problems how I would go about getting the stock kernel back. Thanks for your answers as always.
Nevermind I found the answer. No it will not work. Moderaters feel free to delete thread.
ImagioX1 said:
Nevermind I found the answer. No it will not work. Moderaters feel free to delete thread.
Click to expand...
Click to collapse
Yea it will. Flash the camera fix and it should work fine
Of course it wil bro. Flash that shiz and be amazed. I'm running viper 2.1, beastmode at a consistent 1.89 GHz, and this thing is on fire. You won't be disappointed
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Just a note I have had some overheating at times and a lot of slowdown without ocing...Although the slowing down I have a feeling is because of my execcive undervolting which did make my battery awesome though
I run performance. And overvolted :sly:
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Where would I find the camera fix cause I can't do without a camera? I have read several post in the beastmode thread but haven't seen a camera fix.
ImagioX1 said:
Where would I find the camera fix cause I can't do without a camera? I have read several post in the beastmode thread but haven't seen a camera fix.
Click to expand...
Click to collapse
cam fix
absolutelygrim said:
cam fix
Click to expand...
Click to collapse
I found it just before you posted, but thanks anyway. I think i'm going to give up on flashing the kernel though. I thought it could be done through recovery but with 2.20 you must flash through fastboot. I don't even know the commands for flashing or all the steps involved-i'm new at this stuff. Don't want to brick my five hundred dollar phone thats only a month old and don't even have a warranty.
ImagioX1 said:
I found it just before you posted, but thanks anyway. I think i'm going to give up on flashing the kernel though. I thought it could be done through recovery but with 2.20 you must flash through fastboot. I don't even know the commands for flashing or all the steps involved-i'm new at this stuff. Don't want to brick my five hundred dollar phone thats only a month old and don't even have a warranty.
Click to expand...
Click to collapse
You can't brick your phone by flashing a kernel.
If you really want to flash the kernel, do this:
1. Install the SDK (fastboot and adb) and drivers as per the root threads that currently exist
2. Flash BeastMode Kernel
3. While still in Recovery, open a Command Prompt (in Administrator mode) on your laptop
4. Switch to the folder where "adb.exe" and "fastboot.exe" are located
5. type "adb pull /tmp/boot.img"
6. If it fails, the drivers aren't installed properly or you're not in the right folder
7. Reboot your phone to Bootloader by typing "adb reboot bootloader"
8. Run "fastboot flash boot boot.img"
9. Reboot your phone
Make sure you also flash the cam fix.
Phone bootloops.
Will not work on my phone. Successfully pulled the boot.img after flashing in recovery. Then I flashed the boot.img that I pulled in fastboot. Then I reboot the phone and wind up in a bootloop. I then have to reflash the boot.img from viper to get the phone to start.
ImagioX1 said:
Wound up with a boot loop flashing the boot.img on page 166. I'm running Mac to do the fastboot commands and for some reason I cannot pull the boot.img after flashing the kernel.
Click to expand...
Click to collapse
Just drag and drop the boot.IMG out of the zip and put it in the same.directory as fasboot
Sent from my HTC One XL using xda-developers app
absolutelygrim said:
Just drag and drop the boot.IMG out of the zip and put it in the same.directory as fasboot
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
I edited my post after you posted that. I have sucessfully pulled the boot.img after installing beastmode. It is in the same directory as fastboot and it sucessfully flashes. It just bootloops after that.
Anyone have any ideas what the problem might be?
ImagioX1 said:
Anyone have any ideas what the problem might be?
Click to expand...
Click to collapse
Let's try this again
1.) Wipe System
2.) Factory Reset
3.) Flash boot.img from ViperXL (from fastboot)
4.) Flash ViperXL (from recovery)
5.) Boot your phone
6.) reboot into fastboot
7.) flash kernel boot.img on page 166 (from fastboot)
8.) flash kernel zip (from recovery)
After flashing the kernel, your camera will NOT work. You will need to flash the camera fix. I don't know if you have to flash that from fastboot or recovery on 1.14.
cam fix
absolutelygrim said:
Let's try this again
1.) Wipe System
2.) Factory Reset
3.) Flash boot.img from ViperXL (from fastboot)
4.) Flash ViperXL (from recovery)
5.) Boot your phone
6.) reboot into fastboot
7.) flash kernel boot.img on page 166 (from fastboot)
8.) flash kernel zip (from recovery)
After flashing the kernel, your camera will NOT work. You will need to flash the camera fix. I don't know if you have to flash that from fastboot or recovery on 1.14.
cam fix
Click to expand...
Click to collapse
Ok. Will try.
I still get a boot loop. If my phone can't handle 2.1 ghz would that be the cause of the bootloop?
ImagioX1 said:
I still get a boot loop.
Click to expand...
Click to collapse
oh 2.20 firmware..
try the same thing but without the last step
I don't know what they did, if they flashed the boot.img and rebooted, or if they flashed the zip with it
absolutelygrim said:
oh 2.20 firmware..
try the same thing but without the last step
I don't know what they did, if they flashed the boot.img and rebooted, or if they flashed the zip with it
Click to expand...
Click to collapse
Ill try that, but TURGE on the previous page of this thread said flash both.
Hi i'm new to the att htc one x, just rooted, and installed twrp... then flash cleanrom5. I also noticed clean has a kernel, i did not see an install guide, but i've installed kernels before on my captivate. So what i'm wondering if it's as easy as....
1. place kernel on phone storage
2. reboot into recovery
3. install kernel from recovery
4. reboot
If there anything i am missing or if i am completely off could someone please help me out with this?
Thank you :good:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
redpoint73 said:
If you are on the 1.14 hboot (rooted on 2.20 firmware) you can't flash kernels from recovery. You have to do it using fastboot.
Click to expand...
Click to collapse
Would you mind walking me through that process?
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
cannon19932006 said:
Would you mind walking me through that process?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
absolutelygrim said:
http://forum.xda-developers.com/showthread.php?t=1957193
http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
Sent from my HTC One XL
Click to expand...
Click to collapse
I don't see anything about flashing kernels in that thread.
cannon19932006 said:
I don't see anything about flashing kernels in that thread.
Click to expand...
Click to collapse
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery. fastboot flash method http://forum.xda-developers.com/showpost.php?p=33493959&postcount=2
edit: btw, what exploit did you use to achieve root? Was it the x-factor exploit?
cannon19932006 said:
Unless this makes any difference "CleanROM V is based on the latest Asian 2.29 RUU which is Android 4.0.4, Sense 4.1 and is ODEXED!"
not sure if that means i am on 2.29 rooted.
Click to expand...
Click to collapse
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
redpoint73 said:
Not the firmware you are on now. The firmware you originally achieved root on. More importantly, what version is your hboot (go to hboot, and the version number is listed)?
If your phone was purchased with 2.20 firmware, and you rooted using the new X-factor exploit method, you have the 1.14 hboot.
Hboot 1.14 plugged the hole by which flashing kernels from recovery was possible. So it can only be done by fastboot.
Click to expand...
Click to collapse
i used x-factor yes, and yes it's 1.14, thank you both for the help.
cannon19932006 said:
i used x-factor yes, and yes it's 1.14, thank you both for the help.
Click to expand...
Click to collapse
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
absolutelygrim said:
Ok, since you used x-factor, make sure to flash your boot.img before flashing the ROM
Same with a kernel. Flash boot.img then the kernel zip
Click to expand...
Click to collapse
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
cannon19932006 said:
I already flashed the rom, just not the kernel, i don't remember flashing the boot.img, just following the instructions on the rom's page here
http://forum.xda-developers.com/showthread.php?t=1655011
"Must have twrp Recovery installed with unlocked bootloader! CWM Recovery will cause serious issues!!!
Copy ROM to storage
Reboot to Recovery
Wipe data / Factory Reset in Recovery!
Install ROM and Aroma installer will start.
Choose Options
Let install complete
Reboot to System"
That's how i flashed this rom anyway.
That's funny your in schertz, i live like 5 miles from there in Universal city lol.
Click to expand...
Click to collapse
Well, If cleanROM is using the same Kernel as stock, then you got lucky. If they use the same kernel, no need to flash boot.img.
If they are different kernels and you dont flash boot.img, you are now in a bootloop
lol Universal City
not bad
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
cannon19932006 said:
Sorry for so many questions lol, just making sure i do this right.
okay so basically i want to download the kernel and the fastboot drivers posted in your post.
Extract the fastboot drivers, and then unzip the kernel, taking the boot.img from it and placing it into the fastboot directory that i just unzipped.
I then want to boot my phone into hboot and select fastboot
open the command prompt and take it to where the fastboot.exe is.
then type fastboot flash boot boot.img into the command prompt
After all this is done i want to go into recovery and flash the zip of the kernel?
Is that all right?
Click to expand...
Click to collapse
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
absolutelygrim said:
Yeap. Don't "extract" the zip, just drag the boot.img out of the zip
Click to expand...
Click to collapse
Success, THANKS!
absolutelygrim said:
the boot.img has the kernel in it, it has to be flashed from fastboot.
heres the kernel. dl.dropbox.com/u/31360541/CleanKERNEL/CleanKERNEL 1.1 - HOX.zip
flash the boot.img from fastboot, then flash the zip from recovery.
Click to expand...
Click to collapse
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
cimenta said:
Why do you say to flash the boot.img and then zip if boot.img has the kernel in it?
Thank you. R
Click to expand...
Click to collapse
Because the new hboot makes it to where you cant flash kernels through recovery. only fasboot
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
cimenta said:
So why the second flash if the boot.img was flashed via fastboot?
I am just lost in these. Could you recommend any reading except this forum for me to get more understanding? So I don't do anything to my phone?
Click to expand...
Click to collapse
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
absolutelygrim said:
It wasn't.
boot.img can't be flashed from recovery, it skips it.
Thats why you flash boot.img from fastboot then the ROM from recovery
http://forum.xda-developers.com/showthread.php?t=1963896
Click to expand...
Click to collapse
So although ROM zip file contains boot.img when flashing boot.img won't be flashed? That's why we need to flash is separately? Is it important to flash it before flashing ROM?
Thank you.R
I'm also, learning as I go. From reading and multiple failed attempts at flashing ROMs and kernels, I have found the correct way with 1.14 Hboot.
-dl the rom/kernel
-extract only the boot.img file
- save both .zip and boot to your desired folder.
-go into recovery and mount sd card to pc
-transfer .zip file to your phones sd card
-get back into fastboot on your phone
-transfer boot.img to fastboot folder
-from fastboot cmd prompt(if you have win7, open your folder with fastboot in it hold shift+right click and open cmd)
-type "fastboot boot boot.img" without quotes
-go back into recovery and clean cache/delvik
-then install .zip that you copied to the sd card
You should be good to go from there.
If I have left anything out, please feel free to correct.
Sent from my HTC One X using xda app-developers app
Tried to boot in to recovery to flash a root zip..
When i volume up to enter recovery, screen goes black. I hit power button and TWRP opens but its unusable and dual screen..top and bottom. Slide to unlock is on the screen but nothing works. Only way out is to hold down power and reset.
Help!
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
DatacomGuy said:
Motochopper not working. I run SuperUS app and get "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"
I agree!
Click to expand...
Click to collapse
What bootloader are you on (its in settings app)
cmendonc2 said:
what bootloader are you on (its in settings app)
Click to expand...
Click to collapse
10.6.1.8-20130225
DatacomGuy said:
10.6.1.8-20130225
Click to expand...
Click to collapse
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
cmendonc2 said:
10.6.1.8 is compatible with very few recoveries. Upgrade it to 10.6.1.27 to flash recoveries for KitKat ROMs.
Click to expand...
Click to collapse
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
DatacomGuy said:
Asus has 10.6.1.27.5 posted. This one safe?
How do i manually update this?
Click to expand...
Click to collapse
I know you can use that firmware to install KitKat ROMs as shown here (http://forum.xda-developers.com/showthread.php?p=49028315).
Use the 10.6.1.27.5 firmware with this:
Tylorw1 said:
1. Download the latest version of Android for your tablet. Make sure you download the correct SKU version.
A. To find the SKU, go into settings, About tablet, and look for your Build Number, There are two letters (such as US,WW, TW, etc.) that is your SKU. When downloading the zip from ASUS', you must download the correct SKU zip.
2. Decompress downloaded .zip file (it will be another .zip)
3. Rename it to:
A. For the TF700 and TF300: EP201_768_SDUPDATE.zip
4. Make sure your MicroSD card is formatted Fat32. It must be Fat32 Format or it will not work.
5. Copy the file to (the root directory of) your MicroSD
6. Insert the MicroSD into the tablet
7. Shutdown (power off) the tablet
8. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
9. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button (on RCK, this is your recovery which should already be selected) until you see Android logo and process bar
10. Give the update process 5-10 minutes. It should not take longer than that. If it happens to run for more than 45 minutes to an hour, force shut down the tablet and see if it boots. If it does not, try rerunning steps 7-9.
Click to expand...
Click to collapse
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
DatacomGuy said:
Only issue is that it's flashed in recovery, which isn't functioning for me.. Or usable.
Can I flash cwm again, flash this firmware, then try twrp again?
Click to expand...
Click to collapse
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
cmendonc2 said:
You can also use fastboot to flash the ROM from your computer
Sent from my TF300T using xda app-developers app
Click to expand...
Click to collapse
Alright..
fastboot -i 0x0B05 flash recovery firmwarefile.zip
Click to expand...
Click to collapse
Is that the right syntax?
DatacomGuy said:
Alright..
Is that the right syntax?
Click to expand...
Click to collapse
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
cmendonc2 said:
Remove the "recovery", that means you are flashing to the recovery partition. So
Code:
fastboot -i 0x0B05 flash firmwarefile.zip
for the stock Rom.
Click to expand...
Click to collapse
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
fastboot -i 0x0b05 flash US_epad-user-10.6.1.27.5.zip"
Click to expand...
Click to collapse
and i get:
Unknown partition 'US_epad-user-10.6.1.27.5.zip'
error: cannot determine image filename for 'US_epad-user-10.6.1.27.5.zip'
Click to expand...
Click to collapse
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
DatacomGuy said:
I'm trying to flash "US_epad-user-10.6.1.27.5.zip" by doing:
and i get:
What might i be doing wrong? I tried with the zip and without.
I checked the contents of the zip, and i have folder named "META-INF" with a bunch of content, and also a blob file, about 820mb.
Grr.
Click to expand...
Click to collapse
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
Extract the blob from the stock zip file. It should be a large file. Put that blob in your fastboot folder.
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
EDIT2: Is this the right one?
openrecovery-twrp-2.6.3.0-tf300t-JB.blob
DatacomGuy said:
There we go.. Thank you very much for all your help.
Got it all flashed, all running well.
I tried to boot in to recovery, and got a "system error". I'm assuming i need to reflash the correct TWRP, and then try motochopper again? Or is there a better way to root..
EDIT: Currently running stock 4.2.1...
Click to expand...
Click to collapse
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
cmendonc2 said:
Flashing the stock wipes the recovery, so you will need to flash the correct version of TWRP this time . I dont think you need TWRP for motochopper. Since you are unlocked, you can just flash the SU binaries directly from TWRP.
Click to expand...
Click to collapse
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
DatacomGuy said:
Makes sense.. openrecovery-twrp-2.6.3.0-tf300t-JB.blob the right version?
You lost me on your last part.. where do i find the SU binaries?
Click to expand...
Click to collapse
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
cmendonc2 said:
Wait! Flashing that will brick it again!!! Dont flash that, use the -42 TWRP since you are on Android 4.2 now.
Click to expand...
Click to collapse
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
DatacomGuy said:
LOL!
openrecovery-twrp-2.6.3.0-tf300t-4.2.blob
Got it.
What about root? After i flash, where do i find the SU binaries?
Click to expand...
Click to collapse
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
cmendonc2 said:
TWRP should have the SU binaries built into it. If TWRP doesn't detect root when it is run from the bootloader, it asks you if you want to flash them. Are you trying to flash a KitKat ROM or a Jelly Bean ROM. KitKat needs TWRP -2.6.3.1
Click to expand...
Click to collapse
i dont want to flash any rom right now, i just want to stick with stock 4.2.1...
Last time i flashed TWRP.. albeit incorrectly.. it didnt ask anything when i rebooted into recovery. I'm assuming thats when it asks....
Hi there! i bought an htc one s and managed to flash cm 10.0.0. to it. my problem is that when i flash a newer cm version it bootloops everytime. i have installed twrp 2.6.3.0. .
baseband version:1.08ts.50.02.16
kernel version:3.0.51
s-off, rooted, hboot 2.15, CID 11111111
radio 0.16.31501s
Please any help would be appreciated.
Are you sure that you flashed the right version? Cyanogenmod official is only for ville (S4) version. Are you sure that you didnt flash ville version on villec2 or opposite?
Cvolton said:
Are you sure that you flashed the right version? Cyanogenmod official is only for ville (S4) version. Are you sure that you didnt flash ville version on villec2 or opposite?
Click to expand...
Click to collapse
i believe my htc is the s4 version. max freq 1512Mhz, and at bootloader screen writes vle.
Did you update the Kernel? Tryed to do the Wipes?
Cvolton said:
Did you update the Kernel? Tryed to do the Wipes?
Click to expand...
Click to collapse
no i didnt update the kernel. is it important to update the kernel? and if so how can i do this? i did the wipes
Of course you must update the kernel. Extract boot.img from the ZIP and put it in your folder with adb.exe fastboot.exe etc. (On the computer) then restart the phone into fastboot mode (volume down + power and choose fastboot), shift right click in the folder on PC and choose open command prompt here. Now type here "fastboot flash boot boot.img" and wait till the operation is done. Then reboot and enjoy
Odesláno z mého HTC One S pomocí Tapatalk
3555
Cvolton said:
Extract boot.img from the ZIP and put it in your folder with adb.exe fastboot.exe etc. (On the computer) then restart the phone into fastboot mode (volume down + power and choose fastboot), shift right click in the folder on PC and choose open command prompt here. Now type here "fastboot flash boot boot.img" and wait till the operation is done. Then reboot and enjoy
Odesláno z mého HTC One S pomocí Tapatalk
Click to expand...
Click to collapse
you mean to extract the zip file of the rom i flashed and flash the boot.img of that rom via fastboot?i thought that its not necessary if you have flashed twrp 2.6.3.0. recovery
Yes! Its necessary if you're S-ON
Sent from my VilleC2 using Czech localised Tapatalk
If you're S-ON:
On windows 7, 8 click on ROM.zip. You will see "boot.img". Drag it with mouse on ather folder.
After you wipe everything, except SD CARD, instal rom.
After instal, reboot bootloader. Plug the cable. On phone screen you will have "Fastboot USB"
Open comand promt: ""fastboot flash boot boot.img".
On S-ON phone never work without this.
null0seven said:
If you're S-ON:
On windows 7, 8 click on ROM.zip. You will see "boot.img". Drag it with mouse on ather folder.
After you wipe everything, except SD CARD, instal rom.
After instal, reboot bootloader. Plug the cable. On phone screen you will have "Fastboot USB"
Open comand promt: ""fastboot flash boot boot.img".
On S-ON phone never work without this.
Click to expand...
Click to collapse
Cvolton said:
Yes! Its necessary if you're S-ON
Sent from my VilleC2 using Czech localised Tapatalk
Click to expand...
Click to collapse
as you can see in my first post im S-OFF
tocamrd said:
as you can see in my first post im S-OFF
Click to expand...
Click to collapse
Sorry, blind in the last times :laugh:
However you could still try to do that... Or maybe the download is corrupted, did you check the MD5 checksum? That could be also the problem.
Cvolton said:
Sorry, blind in the last times :laugh:
However you could still try to do that... Or maybe the download is corrupted, did you check the MD5 checksum? That could be also the problem.
Click to expand...
Click to collapse
ok no prob. I tried that with no luck . im tring to flash a rom that i have already flashed to another htc one s so i dont think that this rom is corrupted. i can flash the rom through recovery and gapps and when the phone reboots nothing happen but keep looping... the only rom i can flash is cm 10. do i have to update radio or kernel or something other to my phone??
Sorry for my previous answer.
Flash a new recovery image. Latest is 2.7.0.8.
http://goo.im/devs/mdmower/htc-twrp
I finally gave the phone to a friend with cm 10.0 without trying something else. Thanks all for replies!!!