i need help i cant get the wifi to work on the viper rom 1.2.0 i wiped everything and once i flashed i wiped again and still nothing
Anyone?
Sent from my HTC One S using xda app-developers app
If your on the latest tmob ota you're out of luck
Sent from my HTC VLE_U using xda app-developers app
Can't he just change his cid to 001 and flash 2.31 ruu?
Sent from a man, using a mobile phone
Have you tried flashing the boot.img (the correct one, extracted from the ROM zip) with fastboot? Well, try it again! "adb fastboot flash boot boot.img" and make sure that you have the boot.img in the folder where you run the command. This way you will reflash the kernel and at least the WiFi problem should go away.
VERY IMPORTANT after you run the flash boot command in fastboot, it is recommended to do a "fastboot erase cache" before booting.
Cheers!
Related
i was craving some aosp so I wiped then flashed aokp. Want to switch back now, so I rebooted to recovery but twrp splashscreen shows for 2 seconds, then screen goes black. then the phone reboots into normal os. i tried reinstalling twrp via goomanager to no avail. will flashing the img make any difference? any one else have this issue?
ok i tried flashing the twrp img and still no go. gonna try ruu'ing now unless someone jumps in with a solution.
Are you rooted and bootloader unlocked?
Sent from my HTC One X using xda premium
yes... i've been around here for ages. just this problem is very weird. tried erasing recovery via fastboot and says fastboot remote not allowed FAILED. gonna ruu now.
if ruu dosent work try relocking bootloader by using the "fastboot oem lock" command i believe and then ruu
Sent from my HTC One X using xda premium
DJ-midnite said:
if ruu dosent work try relocking bootloader by using the "fastboot oem lock" command i believe and then ruu
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
lol thats what I just said but thanks anyway
k ruu'ed and all is back to normal. interestingly, no data was wiped when i relocked bootloader and flashed ruu.
and remember try wiping/factory reset when flashing aokp on twrp, and youre welcome
Sent from my HTC One X using xda premium
Okay - I did a really dumb thing - I flashed CM7 with S-on
I tried RUUing it - but my battery is below 30%
It all started when I was on 2.3.4 and my battery wouldn't charge past 15%. So I rooted it, ignored the s-on, and flashed cm7 thinking a different rom might fix the battery issue. I fixed it alright - it stays stuck on the white screen with the HTC Logo. Can anyone direct me to an unbrick without using RUU because it will not charge past 15%
Arrrrrrggggggg- I'm a newb
Any suggestions...
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Ok - got it to charge tried ruu again - 2.3.4 ruu fails & 2.2 ruu gets stuck at 13% reading header. Any thoughts?
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Try THIS take it back to Stock 2.3.4 . Then start the whole rottoing process over.
Ok i'll try running ruu 2.3.4 again tonight. Im skeptical though because as i posted earlier ruu 2.3.4 kept failing.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
prboy1969 said:
Try THIS take it back to Stock 2.3.4 . Then start the whole rottoing process over.
Click to expand...
Click to collapse
I really appreciate your input prboy1969
When I run ruu 2.3.4 I get this errror:
ERROR [155]: UNKNOWN ERROR
Please get the correct ROM Update Utility and try again.
Kind of a crazy error because before the update process starts it compares roms and they match.
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT-0.99.0001
RADIO-1.08.01.0111
eMMC-boot
Dec 29 2011, 10:29:48
Try this. Get adb/fastboot and take the boot.img from the cm7 ROM and move it to where adb/fastboot are. Once there power down and reboot to bootloader and select fastboot USB.
Plug the phone in and open terminal and navigate to where your adb/fastboot are. For me its home/strapped365/android/android/platform-tools
Then use this command
fastboot flash boot boot.img
S-ON Unlocked users can't flash to the boot partition.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
strapped365 said:
Try this. Get adb/fastboot and take the boot.img from the cm7 ROM and move it to where adb/fastboot are. Once there power down and reboot to bootloader and select fastboot USB.
Plug the phone in and open terminal and navigate to where your adb/fastboot are. For me its home/strapped365/android/android/platform-tools
Then use this command
fastboot flash boot boot.img
S-ON Unlocked users can't flash to the boot partition.
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
so your saying change directory to my adb folder (c:\program files\android\andrroid-sdk\platform-tools)/extract contents of cm7 to platform-tools folder/fastboot flash boot boot.img
ok I'll try - although I've flashed it so many times with ruu 2.3.4 that I'll have to first re-flash cwm/su/& cm7 - I'll give it a try tonight. thx
mook_ said:
so your saying change directory to my adb folder (c:\program files\android\andrroid-sdk\platform-tools)/extract contents of cm7 to platform-tools folder/fastboot flash boot boot.img
ok I'll try - although I've flashed it so many times with ruu 2.3.4 that I'll have to first re-flash cwm/su/& cm7 - I'll give it a try tonight. thx
Click to expand...
Click to collapse
Not the whole ROM. Just open it with 7zip or similiar and move its boot.IMG to where fastboot is then run the fastboot command I gave. I was under the impression none of the RUUs worked for you so I thought you were s-on unlocked with cwm
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
strapped365 said:
Not the whole ROM. Just open it with 7zip or similiar and move its boot.IMG to where fastboot is then run the fastboot command I gave. I was under the impression none of the RUUs worked for you so I thought you were s-on unlocked with cwm
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
That's right - S-on. I'm going to have to reload cwm because RUU deletes but then fails during update
So this is what I'm going to try:
- reflash cwm from fastboot
- flash boot.img only from CM7 from fastboot
Then what after that?
mook_ said:
That's right - S-on. I'm going to have to reload cwm because RUU deletes but then fails during update
So this is what I'm going to try:
- reflash cwm from fastboot
- flash boot.img only from CM7 from fastboot
Then what after that?
Click to expand...
Click to collapse
Well like after cm7 is flashed and you fastboot its boot.img it should boot
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
strapped365 said:
Well like after cm7 is flashed and you fastboot its boot.img it should boot
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Click to expand...
Click to collapse
Dude - that freaking worked!!!
I noticed when I go to settings/about phone it crashes "Sorry! The application Settings (process.com.android.settings) has stopped unexpectedly. Please try again.
what next? ruu back to 2.3.4...do the s-off?
mook_ said:
Dude - that freaking worked!!!
I noticed when I go to settings/about phone it crashes "Sorry! The application Settings (process.com.android.settings) has stopped unexpectedly. Please try again.
what next? ruu back to 2.3.4...do the s-off?
Click to expand...
Click to collapse
Well since your booted in, atleast your phone is up and working, even though the settings are crashing. I wouldn't ruu from aosp or anything but that's just me. Being s-on unlocked won't keep you from anything, but you have to fastboot flash boot boot.img of every ROM that has a custom kernel, so its a pain for flashaholics. The choice is yours though, you could just need to do a full wipe a fresh flash and a fresh flash of the boot.img
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Hi I have an HTC one X at&t with aokp installed now im triying to install the stock rom with ruu I try 3 of them and is not working, The RUU is not recognizing my current image. I do factory reset, I try installing in Boot mode but not luck, please help.
First, make sure you have the correct ruu or it won't run.
Second, you have to relock your bootloader before you run an ruu. Go into fastboot on your phone, then open the fastboot cmd prompt, type 'fastboot oem lock' and your bootloader will be locked.
Sent from my One X using xda app-developers app
You also have to have HTC sync manager working correctly
Sent from my One X using Tapatalk 2
InflatedTitan said:
You also have to have HTC sync manager working correctly
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Its not working I think the problems is when the RUU go to the step
From Image Version:
To Image version 2.20.502.7
This is the RUU that I tried
htc_one_x_RUU_2.20.502.7_att_us_08022012
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17.32.09.12_10.86.32.08L_release_262092_signed
RUU_Evita_UL_Cingular_US-1.73.502.2_2FE6772699D8596307CC997452BB8D25
If you simply want to get back to the stock ROM, just flash a stock rooted ROM:
http://forum.xda-developers.com/showthread.php?t=1671237
So I recently unlocked ky bootloader and rioted and flash cwm,and flash a cm10 Rom and it boots up but just stays at the bootlogo AMD doesn't do anything else anyone know what's wrong?
Sent from my HTC VLE_U using xda premium
brandontamas said:
So I recently unlocked ky bootloader and rioted and flash cwm,and flash a cm10 Rom and it boots up but just stays at the bootlogo AMD doesn't do anything else anyone know what's wrong?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
You need to fastboot boot.img.
u did not flash the kernel that is the boot.img. from fastboot flash the boot.img by using this command---
fastboot flash boot boot.img
Sent from my One V
Hi All,
I am fairly new to all this, I have read countless posts and done everything I can but I am stuck.
I have a HBOOT 2.14 currently with S-ON.
I have installed TWRP in recovery but no custom mods work due to the HBOOT version.
SuperCID is 111111111 and is already set.
I want to be able to S-OFF my device so i can downgrade the HBOOT and use the custom roms.
I ran through the facepalm S-OFF procedure, it all runs correctly, although upon reboot it still says S-ON.
Does anyone know why this would be? Is there something I am missing?
I am doing this some the TWRP recovery mode as that is the only place I can access adb commands currently.
There is no working ROM currently installed, CM 10.1 is installed although it can't be used because the touchscreen doesn't work.
Any information people can provide me to get all this working would be of great help.
Happy to donate/pay someone to help me via teamviewer or whatever.
Thanks,
Tabmowtez
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Venomtester said:
What version of twrp are you using? 2.3.3.1 ?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
v2.4.4.0
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Venomtester said:
I have heard that 2.3.3.1 works better for your hboot and you can also downgrade your touch panel firmware and get cm to work.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Really? I haven't seen this said anywhere? Do you have any references to the procedures or the TP firmware?
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Venomtester said:
There is a thread down the page hboot question that addresses this.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes that's the one I posted, it still requires S-OFF.
It seems all the fixes need S-OFF and that is the one thing I can't seem to get working as there is no ROM installed so I can't use supersu?
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Venomtester said:
Have you tried flashing a sense based Rom like viper using adb to flash boot image? Just to see if you can get phone working?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I will download ViperX3.4.0.zip and use the boot.img to flash it from adb and see how it goes.
I have tried AOSP and CM Roms and all have had the same issue of the TP not working though.
I'll see how this goes.
Just to confirm, it seems all ROMS based off of the 3.17 kernel and higher work with S-ON.
I have the HatkaXL-evita-v4.2.5_Sense5Elements ROM working after I did the following steps:
Place boot.img in sdk platform tools folder
Boot phone into fastboot usb
open your command prompt from the sdk files folder. (shift+right click-select open command window)
type: fastboot erase cache
type: fastboot flash boot boot.img
type: fastboot erase cache (just to be safe)
On phone select bootloader, then recovery.
Once TWRP loads (I'm using 2.4.4.0) go to wipe and select factory reset then wipe system and both caches
Then install the rom and go through setup
once setup is complete, UNCHECK restart now so it leaves the rom and goes back to TWRP.
Click on clear cache/davlik and then click reboot
Settings application keeps on crashing so I am going to try the aokp_evita_jb-mr1_build-4 ROM now after a backup.
I still have issues getting adb to recognise the device once the ROM is booted but that's a separate issue for now...
Are you sure your getting error 92 and not 99 when you flash the zip for s-off cause if your getting 99 you need to fastboot write your cid then reboot and try again
Sent from my One X using Xparent Green Tapatalk 2
I'm definitely getting the error 92. My CID is already a SuperCID so would I have to do that again?
I have the ViperX ROM running now so I am happy, would still like to S-OFF though so I can try CM etc. after a hboot downgrade.
Sent from my HTC One X using xda app-developers app
When I did the s-off to my One XL, the error 92 is normal and I just followed the steps in this thread and it worked fine
http://forum.xda-developers.com/showthread.php?t=2155071
That is the same thread I follow, I will try again now that I have a working ROM and see how it goes.
Sent from my HTC One X using xda app-developers app
All good, I successfully S-OFF'd my device and downgraded my hboot to 1.09. Hopefully this means I can put any mod on now without flashing from fastboot first and having the touchscreen work!
Sent from my HTC One X using xda app-developers app