Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!
+1 i have same questions
You might get more responses if this was in the question thread. Mod please move this to the correct area.
Sent from my HTC One XL using xda premium
watswidme said:
Since I can't post on the original android development thread. I'll ask here.
I'm a noob on all of these rooting and custom roming however I did manage to unlock my bootloader, flash TWRP 2.6.0.0, have root access via Superuser, S-OFF and finally flash Android 4.2.2 Sense 5-5.08.111.2 stock ROM by Turge on my ATT device running JB 3.18 (HBOOT 2.14).
I love the stock rom however I'm having problems such as signal drops throughout the day, random reboots and no signal when I wake up everyday for the past 3 days.
I know the solution is to flash Kernel and update firmware - which is explicitly stated on Turge's thread, which leads me to my questions:
1) What does firmware updating do to my device? I'm pretty clear on what happens when you flash Kernel.
2) Assuming I was able to update firmware (including HBOOT to 2.15?) and Kernel, Would I still be able to revert back before messing with them? Would creating a nandroid backup before updating and restoring that nandroid backup be able to revert them back pre update w/o issues (or bricking)?
3) Lastly, I made an original nandroid backup while still Android 3.18 w/ Sense 4 (my very first nandroid backup) before flashing Sense 5. Assuming I updated firmware and Kernel while on Sense 5, Would restoring the original nandroid backup allow me to restore back to Sense 4 w/o issues (or bricking)?
Hope someone would take time to respond! Thanks!
Click to expand...
Click to collapse
1. The firmware update will update the hboot, radio, and some WiFi and media modules.
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
2b. A nandroid backup doesn't backup the partition that is updated by a firmware package. It only backs up the OS/data/boot partitions, so restoring a backup won't change your firmware, use the RUU as suggested above if you need to revert.
3. Restoring your backup will return you to the Sense 4 ROM. Like I mentioned above though it will not change your firmware.
You are s-off so the chance of bricking while running an RUU is minimal. There is always a small chance of bricking no matter what you're doing, whether it be flashing a ROM/kernel, changing hboot (higher risk), flashing a radio, running an RUU. With your current setup, you have no greater risk than anyone else though.
PS. Questions go in the q&a section (for future reference).
Sent from my Evita
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
timmaaa said:
2. You can revert using the 3.18 RUU, this will return you to the 2.14 hboot, stock recovery, and stock Sense 4 ROM.
Click to expand...
Click to collapse
This^ I was gonna ask about it in Q&A thank goodness I read this thread first. Thank you!
Sent from my HTC One X using Tapatalk 4
Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.
watswidme said:
Timmaa - Great stuff buddy! One additional question, It sounds like I can restore my backup (made on 2.14) while my firmware is 2.15? Wouldn't this cause any trouble?
rwalterk - I will err on the side of safety and flash my Kernel first, like how you did it. My phones getting more reboots and dead signals after a week of use. If problems still continue I will update my firmware.
pjacanales - noted, questions on the questions thread.
Click to expand...
Click to collapse
I can't see any reason why reverting to Sense 4 wouldn't be ok on the newer firmware.
Sent from my Evita
Newbie Question.
rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
Hey bro
I'm from Venezuela and I'm having the exact same problem as you guys have.
I readed your post and downloaded Beastmode 3.5 and flash it, but i got caught in a bootloop.
I'm using the VIPER 4.2.2 Rom.
Since this is not a solution for me, i was wondering which Rom are you using exactly?
Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita
rwalterk said:
I had the same exact issue. I did the easiest thing first - flashed the Beastmode 3.5 kernel, and thankfully that has completely fixed the issues for me. Been running with it for 4 days now and the signal has not dropped once nor have I had random reboots. I did not have to upgrade firmware.
Just a personal note... the stock settings flash did not work for me; I had to choose the custom flash and enter the stock settings. He mentions this in the install notes.
Here's the Beastmode 3.5 thread:
http://forum.xda-developers.com/showthread.php?t=2165880
Here's his post with what the stock settings should be if you need to choose the custom flash:
http://forum.xda-developers.com/showpost.php?p=45195808&postcount=251
Click to expand...
Click to collapse
timmaaa said:
Did you select custom from the Beastmode installer? He's using Turge's stock Sense 5 ROM which can be found in the development section.
Sent from my Evita
Click to expand...
Click to collapse
Thank you my friend!
I downloaded Turge's ROM and install it, and actually didnt have to flash the New kernel; i used the one in the Package and it Worked! i almost sold my phone because i couldnt find a ROm taht works but, so far, its been passed one day only and i havent had any signal drop, nor battery fast draining!
Sorry for my english BTW.
Thank you once again!
PS: If u find a way to fix VIPER ROM let me know, cause i've read a lot and cant find a way to fix it, but im to shy to ask in a new post hahahahahhahahahahahahaha.
Let me know if you need my phone specs. (as bootloader version, software version etc.)
The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita
timmaaa said:
The best way to overcome the problems is to get s-off, then you're able to upgrade to the 2.15 firmware which is the best solution to signal loss and reboots on Sense 5 ROMs. In order to get s-off you'd most likely need to flash a different ROM though, I don't think a single person has had the process succeed while running a 4.2.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Yeah, i'm already S-OFF.
Actually, all this problems came out when i was 1.14 FW, but when i checked for the first time this post, i decided to change the FW and now i'm @ 2.15 FW, S-OFF and CID-11111111.
I haven't checked what is gonna happen if i install VIPER ROM, but in the meanwhile, i'm gonna try this ROM which runs smooth.
Related
hello and sorry for the same questions asked over the same issue...
its my first time and im afraid to brick my phone
anyway now im with custom rom and want to go back to stock to receive ota updates.
my phone is rooted and s-off i want to stay s-off with stock rom.
1. is it possible ?
2. will i need to wipe data before the flash?
3. backup needed ?
4. will i get ota updates with stock rom s-off?
5. the ruu is europe 1.47 do i need it to match to my software/radio/hboot?
my phone:
SAGA PVT SHIP S-off RL
HBOOT -0.98.0002
RADIO-3805.06.02.03_M
EMMC-boot
@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.
foX2delta said:
@yonigo870
Since you want to stay s-off and a stock rom then....
1) Yes if you don't want need OTA. No if you want ota
2) Yes
3) If you want to restore your apps/data yes, google SHOULD be okay with contacts/calendar
4) Dont be silly, really, DONT TRY STOCK THINGS ON ALTERED PHONES, thats common sense (at least it should be)
5) You will not use a RUU, you wil use a pre rooted stock rom from the development forum
However, if you want to get ota updates you will need to go s-on and use a RUU, I suggest just getting the latest RUU
My suggesttion, rather leave your phone as is and install a stock pre rooted rom, you can always install the latest stock rom when the OTA is released and its made into a prerooted rom.
Click to expand...
Click to collapse
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped
thanks
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!
yonigo870 said:
thanks for the help !
how do i flash pre rooted roms?
and witch one i need???
and the other thing is, if i want to flash one of the custom roms via rom manager how do i flash the updates ? will it be the same way? do i need to change anything else or i can just backup and flash rom?!
Click to expand...
Click to collapse
here is a few guides to help with that question i don't know anything about rom manager sorry i use 4ext touch recovery
Custom ROMS:
Custom roms can be found in this thread: http://forum.xda-developers.com/show....php?t=1146601 or head to the development section.
(Most of these ROMs are pre-rooted, which means that you don't need to root your phone after flashing one of the custom ROM.)
How To: Flash Custom ROMs using Recovery (Method 1)
(You can use your default recovery from Revolutionary tool but I recommend using 4EXTRecovery)
1. Copy your custom ROM "zip" file to your SD card (Root directory).
2. Turn off your phone.
3. Turn on your phone by holding the power button and the volume down button together.
4. Once you see the white screen, choose "Recovery"
5. Make a full wipe/format and clear all cache.
6. Choose "install from sdcard/zip file" and then choose your Custom ROM zip file from your SD card to flash your Custom ROM.
Optional: If you want to use 4EXTRecovery, just flash it like you are flashing your custom ROM(Step 6). Just do it before you flash your new ROM.
How To: Flash Custom ROMs using ROM Manager (Method 2)
(This method might be easier for flashing ROM updates or add-ons)
1. Go to ROM Manager (You can install this software from the Android Market.)
2. If you want to use 4EXTRecovery, please follow steps below, and if you're not using 4EXTRecovery, please skip to step 6)
3. Press your phone's option's button and choose Manual Flash Override.
4. Press OK and choose your phone model.
5. Choose ClockworkMod 3.x (After these steps, your ROM Manager won't ask you to flash new recovery again when flashing new a ROM)
6. Reboot into Recovery and make a full wipe/format and clear all cache then reboot.
7. Now, from your ROM Manager, choose Install ROM from SD Card.
Note: Flashing ROMs can be vary, some custom ROMs may require you to flash some of their own file first. Eg, The LBC Mod ROM requires you to flash "WIPE zip file" before flashing the ROM. Read their instructions carefully to know more.
NOTE: I am not responsible for any faulty or bricked devices after S-OFF or flashing new ROMs. Do it at your own risk.
How To: Flash a ROM in a "Perfect" Way (Method 3 - Recommended)
A great guide from vampire36 for people who encounter the following problems:
1. The ROM you flashed gets stuck on HTC screen (bootloop) while the same ROM works right for others
2. You get the same kernel and radio yet you find your cell to have more battery drain than others
3. Finally some strange force closes and restarts but works perfect for others
So this is basically one of the most perfect way to flash a custom ROM and is a way to help people who face such issues.
Please head to : http://forum.xda-developers.com/show....php?t=1257731 to see full instructions and discussions.
Blush91 said:
@foX2delta i agree with you
@yonigo870 flashing a ruu can actually force you into a bootloop if you flash the wrong RUU the best wasy to get to stock is to flash a pre-rooted stock ROM
heres both links to the RUU and pre-rooted stock ROMs
RUU http://forum.xda-developers.com/showthread.php?t=1002506
pre-rooted http://forum.xda-developers.com/showthread.php?t=1183684
i hope i have helped
Click to expand...
Click to collapse
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root afterwards and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!
Saipro said:
You can enter a boot-loop but I've flashed ROMs too many times to remember (stock & MOD) and never truly boot-looped. You may soft-brick your phone however, but with remedy. Rooting phones & flashing ROMs isn't for the faint-hearted. My phone was dead for almost 48 hours (within 24 hours of purchase). That's how I joined XDA.
Scary. Turned out it wasn't hopeless. Within an hour of Temp Root, I had self-styled flashed CWM Recovery (haven't run into the gung-ho method I crafted yet, at least on these forums), proceeded to acquire Permanent Root and within the week had flashed 4 ROMs. Invented a few tricks myself .
Point is you have to get your hands dirty. That's why you bought the darn phone in the first place! Pull your gloves & get those hands dirty!
Click to expand...
Click to collapse
yes i've flashed many roms also and have never encountered a boot-loop the only time i got a boot-loop was when i flashed the wrong RUU in the past 48 hours i've changed roms about 20 times
flashing pre rooted stock rom
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager
yonigo870 said:
in progress...
hope i wont fu*k my phone at the very first time im doing this
btw im doing that with rom manager
Click to expand...
Click to collapse
Loooool don't worry that's what's xda is for were all here to help
Sent from my HTC Desire S using XDA
no wifi
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
the phone updates himself ??? i see it updates programs from the market without me doing anything
* do i need to reboot the phone after flashing rom ??? and how ?
yonigo870 said:
flashed Saga_Europe_2.10.401.8_heb made by dmatik
and no wifi !!! how to fix it ?
the other thing is that i cant connect to market ...
and how do i restore titanium backup if i cant find the program on my apps ?
Click to expand...
Click to collapse
I don't know much about titanium I use app extractor try this ROM http://db.tt/Wnl7ZrKa
App extractor restores your apps contacts wifi settings SMS from your nandroid(backup)
Sent from my HTC Desire S using XDA
many thanks for the help !!!!
do i need to reboot after flashing ?
Yeah reboot I hope you made a full wipe before flashing sorry should have told you earlier
Sent from my HTC Desire S using XDA
yeah i did full wipe
after flashing rom the phone made updates from the market by himself, and now im restoring via titanium and seems like everything is ok...
after that titanium asked me to reboot, and so i did.
again thanks a lot for the support and for the help !!!!!!!!
problem !!! the rosie utility stopped unexpectedly...
htc widgets (like clock and weather) not working after restoring with titanium!
maybe its since the backup was on sense 2.1 and now its 3.0
how can make the htc widgets work ???
reboot back into recovery and fix permissions i dont know if you can do that in titanium
solved !!!
all was needed is to clear data from the htc sense
Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
I no longer need to downgrade to get the WiFi thanks to this great post here: WiFi Fix
I hope this helps people in the future.
All roms wifi works fine for me on hboot 1.14...
Vuciz said:
Hello, my HTC One S was fine on the stock things, but I decided to root it and add a custom ROM.
Bad idea.
I can't install Linux, so I can't downgrade the bootloader, and I can't find any ROMs where wifi will work without doing so. How can I revert to full stock, or is there a ROM where wifi works on hboot version 1.14?
Click to expand...
Click to collapse
i regret rooting my phone.. i cant sell it because they dont want a rooted phone
Re: Need To Fuly Revert To Stock
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app
zaak00 said:
There's a guide somewhere in here how to revert to stock. I used it and worked perfectly. You should be able to find it using the search .
Basically the procedure goes like this:
1. Install zenROM (it's in the dev section).
2. Install stock recovery (also posted here in several threads)
3. Boot the phone into zenROM and look for OTA updates. ZenROM can find and install official updates.
4. Once updates are ready, you should be running stock JB rom.
5. Relock bootloader, or root or whatever. Now you are on the stock rom.
Of course this requires that there is a JB update available for your CID.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
so let me post it the fourth time ..
http://forum.xda-developers.com/showpost.php?p=37942416&postcount=2
Usually you'll find answers to your problems in the according rom section as you're not the only one with it.
But as you are pretty new here:
1. You can use Linux livecd for downgrading. More here. The process isn't that easy so and you'll need to be patient and careful. (I did that couple of times on my device. The first time it was really worse also I was/am not new to Linux).
2. 1.14 means you have been on ICS only so far. So any ICS rom should work for you. If there is still trouble with wifi, search for answers in that rom section. I remember some guys editing a file for enabling/boosting wifi. As I'm not concerned by this, I have no links.
3. If you'd like to move to JB roms search for 'flashing wifi partitions' as long as you want to keep 1.14. If flashing the OTA update for JB your bootloader version will be 2.15 and the according wifi partitions will be working as well. For both, ICS and JB.
Substantially there will be no real differences for you between 1.14 and 2.15 as only with 1.06 and 1.09 you don't need to flash kernels via fastboot mode.
Hope you got the point as my answer is very short.
My HOX was running stock rooted ICS and I did a TWRP backup and flashed [ROM ][22 MAR][UrDroid][HTC One X AT&T][Stock][JB][OTA][Odexed] EVITA 3.18.502.6 using the AROMA installer which had a kernel included. Now I am trying to restore the backup, while the process shows as successful, the phone does not pass the HTC screen, it goes black where the AT&T logo is supposed to come in.
I have to reflash the JB rom to get the phone working again. However, this rom is not stable, I keep getting random crashes or reboots, so I wish to revert to stock
Any idea why this is happening and how I can fix it?
Thanks in advance.
rohangiase said:
My HOX was running stock rooted ICS and I did a TWRP backup and flashed [ROM ][22 MAR][UrDroid][HTC One X AT&T][Stock][JB][OTA][Odexed] EVITA 3.18.502.6 using the AROMA installer which had a kernel included. Now I am trying to restore the backup, while the process shows as successful, the phone does not pass the HTC screen, it goes black where the AT&T logo is supposed to come in.
I have to reflash the JB rom to get the phone working again. However, this rom is not stable, I keep getting random crashes or reboots, so I wish to revert to stock
Any idea why this is happening and how I can fix it?
Thanks in advance.
Click to expand...
Click to collapse
What hboot do you have? If you have hboot 1.14 or newer and are not s-off, you'll need to pull the kernel from the ICS rom and flash it via fastboot.
Great! I just need to track down the stock ICS kernel because I think my phone came with version 2.20.
Any idea where I can locate it?
Thanks.
rohangiase said:
Great! I just need to track down the stock ICS kernel because I think my phone came with version 2.20.
Any idea where I can locate it?
Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1671237
Custom ROMs -> Stock Rooted (Odexed/De-Odexed)
Grab any of the ICS ones and it should do the trick. If your TWRP backup backed up boot, you should also be able to pull it from the backup (\sdcard\TWRP\backups\etc.), but I've never done this before and don't have a backup handy on my phone, so I wouldn't be able to tell you exactly where you'd need to look to find it. Shouldn't be too complicated though if you poke around?
Hi,
I have unlocked bootloader using htc dev. and flashed recovery with Clockwork recovery 6.0.0.3.
whenever i i tried to update with custom roms like cynogen mod 10.1.3 and viperXL, Urdroid jb 4.2.2
its loosing the network signal frequently and restating automatically...
Please help me to get rid of this problem....
harithota20 said:
Hi,
I have unlocked bootloader using htc dev. and flashed recovery with Clockwork recovery 6.0.0.3.
whenever i i tried to update with custom roms like cynogen mod 10.1.3 and viperXL, Urdroid jb 4.2.2
its loosing the network signal frequently and restating automatically...
Please help me to get rid of this problem....
Click to expand...
Click to collapse
This has already been discussed in countless places, including the fix in the first post of the UrDroid thread, under the big red boldface letters "RECOMMENDED".
Always take a few minutes to search and browse for the answer, and read the ROM thread before posting a question; since its almost certainly already been asked and answered by others.
no need to worry
harithota20 said:
Hi,
I have unlocked bootloader using htc dev. and flashed recovery with Clockwork recovery 6.0.0.3.
whenever i i tried to update with custom roms like cynogen mod 10.1.3 and viperXL, Urdroid jb 4.2.2
its loosing the network signal frequently and restating automatically...
Please help me to get rid of this problem....
Click to expand...
Click to collapse
install this kernel
http://forum.xda-developers.com/show....php?t=2061577 and if u still have issue then install it again with higher voltage i had same issue and now m happy with my phone .... install this kernel in clean rom
redpoint73 said:
This has already been discussed in countless places, including the fix in the first post of the UrDroid thread, under the big red boldface letters "RECOMMENDED".
Always take a few minutes to search and browse for the answer, and read the ROM thread before posting a question; since its almost certainly already been asked and answered by others.
Click to expand...
Click to collapse
Thank you for your valuable suggestion.
I have seen that while i was downloading ROM! but i don't know the importance of that.
and i know only how to flash custom ROM. but really don't know how to flash a firmware?
could you tell me how to flash that firmware?
i must need TWRP recovery?
whether i need flash this firmware before flashing ROM? or after?
harithota20 said:
but really don't know how to flash a firmware?
could you tell me how to flash that firmware?
i must need TWRP recovery?
whether i need flash this firmware before flashing ROM? or after?
Click to expand...
Click to collapse
If using carl1961's file from the UrDroid thread (as I suggested) just flash in recovery. Not sure, but CWM should work. You must be SuperCID and S-off to flash the firmware.
Can be flashed anytime, doesn't effect the ROM itself. But with flashing anything, I always do a nandroid first.
:good:
redpoint73 said:
If using carl1961's file from the UrDroid thread (as I suggested) just flash in recovery. Not sure, but CWM should work. You must be SuperCID and S-off to flash the firmware.
Can be flashed anytime, doesn't effect the ROM itself. But with flashing anything, I always do a nandroid first.
Click to expand...
Click to collapse
i flashed turge. i hope it will work!
thanks.:laugh:
So as a n00b, I posted in the wrong forum earlier, lol
Anyways , long story short, htc one x evita, unlocked bootloader, tampered, rooted, will not flash past htc splash screen, when I try to restore, it does nothing, when going into folders there is NOTHING there, so random, I did clear my caches as instructed, maybe I am n00bish and deleted the wrong things, I can read the phone in adb, will go into teamwin screen,
REgardless, If I can get this fixed, I will not be messing with it again, lol(as all noobs say)
IS there anything I can do at this point before I throw my hands in the air and throw my phone at a wall?
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
timmaaa said:
Far from unique. It's possible that you've accidentally wiped the sd at some point, or did you possibly do a factory reset from the bootloader? Why haven't you just copied a ROM to the device to flash?
Sent from my Evita
Click to expand...
Click to collapse
HI, I may have wiped the sd, let's say sure to this..lol..
I have tried to copy a rom, I had Viper somewhat load, then it flashes back to htc splash, then to twrp,
Any insite to one that may possibly work?(the others will not load at all, they all fail install)
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
timmaaa said:
I need a bit more background on the device, please post your bootloader details (the first five lines). What TWRP version are you using? What had you done to the device directly before encountering this problem?
When you say you had Viper somewhat load what do you mean? Did it boot into the ROM at all? Or did it only boot as far as the Viper boot animation? Or did it only make it as far as the HTC splash screen?
I can't really say what's going to work until we figure out exactly what's wrong. Make sure you answer all the above questions with as much relevant detail as possible and we'll see if we can sort it out.
Sent from my Evita
Click to expand...
Click to collapse
First off, thank you for your prompt replies
Venom loaded splash screen, then reboot to htc splash with the red developer on the bottom
twrp is the newest one
first 5 lines are you meaning?
*** TAMPERED ****
*** UNLOCKED ****
Evita put ship s-on rl
hboot-2.14.0000
radio-0.23a.32.09.29
??
Well I tried to load the stock RUU from rogers, (ota one)
then after rooting,unlocking bootloader, I tried to load a custom rom(slimkat IIRC)
then IT shut down, I left it for the night, and then nothing, so I tried to install slimkat again, nothing, so I tried venom, and I had the splash screen for the rom, now I am basically back at square one, nothing lol
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
timmaaa said:
Yes those are the bootloader details I needed. When you say the latest TWRP I'm assuming you mean 2.6.3.0? There are two versions of 2.6.3.0, the official version and the modified version.
Official version
Can flash any ROM except 4.4 ROMs. If you're using this one it is why SlimKat (plus any other 4.4 ROM) is failing to install.
Modified version
This is required to flash 4.4 ROMs. It does work on some pre 4.4 ROMs but it doesn't on others.
The most common cause for your current situation to happen is that you've forgotten to flash the boot.img with fastboot. Your phone is s-on, this means that the boot.img is unable to be flashed during the recovery install due to security restrictions on hboots equal to or greater than 1.14. So, make sure you're using the correct recovery for the ROM you want to flash (official 2.6.3.0 for Viper, modified 2.6.3.0 for 4.4 ROMs), and make sure you flash the boot.img with fastboot. I have detailed instructions on how to flash a boot.img in my How-To Guide For Beginners thread, link in my signature.
Do that and report back with how you go.
Sent from my Evita
Click to expand...
Click to collapse
Thank you so very much, once again with the quick replies and the "dumming" it down for me,
I will try in a little bit, to be honest, im not sure what twrp it is, I know its 2.3.6.0, it was the newest one,
in your instructions is there a way to boot just back to stock rom as well?(my pc is horrible, if I load more then one page it dies off lol) I will try this when I get home in a little bit herre.
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
timmaaa said:
I can almost positively say you're on the official version of TWRP, you'd need to go out of your way to find the modified one usually. With your phone in its current state you can't use an RUU to go back to stock. The latest Rogers RUU is older than your current firmware and you can't run an older RUU while s-on. If you made a TWRP backup of your stock ROM before wiping you could restore that backup though.
Your best and easiest option right now is to just flash a ROM. Once you've gotten a custom ROM booted up my guess is you won't want to go back to stock
Once you've gotten a ROM booted you can get s-off on your device which will make life a lot easier for you. It means no more flashing a boot.img, you'll be able to flash radios, you can run any Evita RUU (forwards or backwards, and from any carrier), and more benefits. But for now just concentrate on getting the ROM booting.
I'm assuming you have adb/fastboot installed on your PC already? If not you'll need to do that first, Google search "minimal adb and fastboot", the first result should take you to a thread that can get it done with very little effort.
Sent from my Evita
Click to expand...
Click to collapse
Yes I have a basic Adb/fastboot setup already, is there a particular rom you recommend?(I will trust your best judgement here) I am home now, I will try and let you know
Thank you again
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
timmaaa said:
Asking for a ROM recommendation isn't allowed on XDA so I can't answer that question, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge.
Each user has different tastes anyway. Some people like Sense ROMs, some like aosp ROMs. Personally I'm an aosp guy, aosp ROMs are generally a bit snappier, plus you can run the latest version of Android (Sense ROMs are limited to 4.2.2 for our device). I'd suggest having a look at the ROMs on offer, check out their features and pick one to flash. If you don't end up liking it you can always just flash another, and that's half the fun.
As a side note, getting s-off via Rumrunner s-off seems to work better on Sense ROMs. I know someone very recently got s-off while on the Kickdroid ROM so if you do want to get s-off I'd suggest flashing that ROM purely for the s-off process. You might like it and want to stay on it, if not just flash away.
Sent from my Evita
Click to expand...
Click to collapse
I understand and apologize, Never thought of it that way,
Anyways an update, I followed your tutorial, and I am not having much luck here, It still maintains to say NO OS installed (through twrp when rebooting after I do adb and such)
maybe I am missing something ?
Adb or fastboot?
Sent from my Evita
timmaaa said:
Adb or fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Fastboot,
Small update I did manage to get a rootbox rom to load, but its not stable by anymeans...Ugh super frustrated with it
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
timmaaa said:
Are you wiping in TWRP before flashing? It's very important to wipe system/factory reset/cache/dalvik cache before installing a ROM. Just never do a factory reset in the bootloader, that'll corrupt your sd card.
Sent from my Evita
Click to expand...
Click to collapse
Yes to wiping before flashing in TWRP just those ones mentioned, (if you do sd you loose your flash right?), anyways the rom I flashed yesterday was super unstable, just trying a few diff. ones out and trying to find one that will continue to stay working lol!! Your tutorial in your signature is very helpful
thank you so much for all your help,and patience
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
timmaaa said:
Yeah you don't want to wipe sd card/internal storage or you'll lose all of your personal data like images, music, ROM zips, backups.
Sent from my Evita
Click to expand...
Click to collapse
Oh this is a clean phone, I already backed up on pc Before lol
Question though, I installed Viper again(just to try it) and it loads a menu showing ram, one of the memory sections shows -1? is this correct?
On a side note, I got Venom up and running and WOW!!!
once again, a super thank you for your patience and help all along Timmaaa,
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
timmaaa said:
I'm not sure what you're talking about, is that after booting into the ROM? Can you show me a screenshot?
Sent from my Evita
Click to expand...
Click to collapse
it was while I was installing, everything seems fine, still no wifi(original issue)
im thinking the logic board may be buggered...sad day...lol
But, it is fast as heck now, running venom rom, I will try to get S-off and then maybe try to get it so I can load up the 4.4X roms
Thanks for all the help