Related
A few month ago, I updated my wife's DesireS with a custom rom so she could have the Sense 3 before the official update.
I installed the clockwork recovery, but now I cannot install the official rom, because after the install's reboot, I'm in recovery and it doesn't flash the update.
Altought I have a EVO3D with KingCobra's 1.9 Rom, I'm not too familiar with HBOOT and RECOVERY, and I couldn't find an original Desire S recovery to allow the offical update.
Of course, I made some google searches, but I couldn't find how to solve this problem. Most replies tell to flash another rom, not the official. But my wife is my wife, and each time she has a problem, she tells me that it is because it is not an official (bug free?) ROM.
I tried to run a shipped rom from this thead : http://forum.xda-developers.com/showthread.php?t=1002506 , but I fall in a boot loop, not able to enter recovery, no USB connection to flash with recoverymanager, and at a moment, I even thinked I bricked the phone.
Fortunately, I found the VolUP+Power several times, and I was able the re-flash the previous rom.
Can someone help me please.
Thank you.
@kitarolivier
Little unsure on what you are needing.
Do you 1) want to revert the phone to stock, i.e. as you first got it (s-on again/no custom recovery/not rooted) or 2) flash a stock ROM but the latest (still s-off/able to root/custom recovery installed).
Also you need to provide more info, like the current hboot, and what method you used to s-off, what was the software version when you s-offed, which RUU you tried. More info easier and more direct solution.
The thread you linked are RUU's to get the phone to point 1.
foX2delta : Thank you for reading and replying.
You are right : I want to revert it as i received it. My goal is to install last offical rom with the htc update in the settings.
I will post hboot version when I'll get hands on my wife's phone. I didn't expected a reply so soon
I installed a rooted rom (can remember which one) with rom manager.
Full information this evening (GMT+1).
@kitarolivier
How did you s-off the phone? Also do you know if the phone is a Europe unbranded device?
@foX2delta :
The phone is S-OFF
HBOOT 6.98.1002
It's an unbranded european phone.
Is this enough as information ?
You should be able to flash this eng hboot http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 via fastboot, then you should be able to flash the stock rom that you tried to flash previously
Sent from my HTC Desire S using XDA App
Thank you for the answer. I'll check that tomorrow, because I'm not home today.
Regards,
Olivier.
@kitarolivier
Pretty easy fix.
Have a look at this guide I wrote here, follow section 2.
If you want to get the latest (2.3.5/sense 3.0) then use the 2.10.401.8 RUU.
Hello,
I find lots of helpfull contents here, especially in your guide @foX2delta.
I'm a bit interessted by the second method to get stock ROM "2) flash a stock ROM but the latest (still s-off/able to root/custom recovery installed)."
Is it possible to get the stock ROM and keep s-off and custom recovery ? Have you a guide about this ?
I know it's possible to get the ROM from RUU but how to install this rom.zip ?
thank you in advance, bye
ps: sry for my poor english
@LitonX
If your phone is s-off and you have a custom recovery then it is as easy and flashing a rom, see this thread for prerooted stock roms.
thx,
i get HTC_Europe_2.10.401.9_Prerooted_Deodexed (http://forum.xda-developers.com/showthread.php?t=1480576). it's works fine.
I have a last one question. it is complicated to make my own flashable .zip from the "rom.zip" wich is obtained by RUU (start RUU and get rom.zip in %tmp%) ?
foX2delta said:
@kitarolivier
Pretty easy fix.
Have a look at this guide I wrote here, follow section 2.
If you want to get the latest (2.3.5/sense 3.0) then use the 2.10.401.8 RUU.
Click to expand...
Click to collapse
I followed with success the section 2 of your tutorial. I also donwloaded in installed the ROM you suggested, and it was OK. After that, the device updated a few apps (FB, locations, etc...).
Many thanx for your help, and I will press the thanki button right now, so you are now at 33 I think.
Olivier.
@kitarolivier
Good stuff, glad it all worked out for you!!
hello.. i have same case to.. i want to get back to s-on..
i`ve tried all tips and trick, but it still didnt work...
could you give me some solution?..
sendietera said:
hello.. i have same case to.. i want to get back to s-on..
i`ve tried all tips and trick, but it still didnt work...
could you give me some solution?..
Click to expand...
Click to collapse
Follow section 2 of post: http://androidforums.com/3405058-post1.html
Basically, you have to go through flashing the bootloader twice.
Hi,
I have a question.
I already flash 4.1.1 via OTA and use some bloody init.d script for R/W system, that doesnt work and gives me reboot after I enter into supersu app.
My question is... how can i flash 4.1.1 again (i wanna clean system, just for better feeling.) If Im using TWRP recovery? Because, ota file doesnt contain stock recovery as RUU does and I didnt find any ruu for 4.1.1 CID_032 | villec2.
Or, can I flash OTA update as update.zip in TWRP recovery?
sorry, for my bad english.
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
JohnKoeMan said:
Step 1: relock the bootloader (check out some xda forums). This is a pretty easy process.
Step 2: find your desired stock jb online.
Step 3: connect your phone to the pc (make sure you have the htc drivers installed).
Step 4: run the RUU or stock file as an exe. An installation guide will follow, just follow it through.
It should work after this!
If you have questions or run into problems, let me know!
Sent from my One S
Click to expand...
Click to collapse
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
Haha no problems friend!
I've found a link to a custom ROM using JB 4.1.1, you can look into that?
http://forum.xda-developers.com/showthread.php?t=1871866
Also you can instead remove TWRP (if you know how) and instead install CWM (clockworkmod).
I found CWM to work better than TWRP.
I myself am using CyanogenMod 10.1, very nice and clean, works perfectly ad has Android 4.2.1
That might also be an option if you want a clean ROM. ^^
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
orenfl said:
I think you're missing something here.
The fact is that there is no original JB RUU that can be pushed to phones already after JB OTA, which updated their phone to custom ROM and want's to go back to stock now.
Running an ICS RUU will do no good since it will fail based on lower Hboot version.
My recommendation, therefore, is to use as close to stock JB ROM like http://forum.xda-developers.com/showthread.php?t=2076855.
I will choose to go back to TrickDroid 9.1 if I had to.
Another option if no RUU is available is to get a nandroid done on the JB OTA just after flashing and rooting. And restore it.
Click to expand...
Click to collapse
Since I'm facing the same problem, and there is no RUU for now, how and where to get a JB OTA nandroid... Haven't seen any around.
Impo5sible said:
Thanks, but I think there's misunderstanding. I know how to use adb - relock, etc.
My point is, that I have android 4.1.1 (updated via OTA) and I wanna re-flash this with same android - 4.1.1 (due to I've installed a script that doesnt work - Easy_InitD_1.1.zip... and makes me couple of reboots. And I would prefer to have a clean rom, without any "possible future" problems.
Damn, I think Im getting worse, isn't this true? =D
edit: bloody RUU for JB would solve my problem, but it doesnt exist, yet.
Click to expand...
Click to collapse
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
tominozh said:
I had the same problem and no stock jb nandroid to go back to. Luckily I kept ics nandroid in my laptop, restore that and run OTA jb update again.
There is another option. Get Zenrom ICS, check for updates, download jb, install and then do factory reset. Then root it ( superuser, busybox, modified boot.img), make system back up and keep it in pc. Then you have it safe and you can go back to it if you need full stock jb.
I hope this will help.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
bo6o said:
So I'll be able to install Zenrom ICS on JB stock with hboot 2.15?
Click to expand...
Click to collapse
Yes, you should be. Download zenrom, reboot recovery, wipe everything a few times, flash zenrom, set it up, then recovery, flash STOCK RECOVERY ( very important), prompt for update, download, install, set up, ( you may get a few errors here and there so just do factory reset in setting-->factory reset). Then flash twrp, flash superuser, backup.
Sent from my HTC One S using xda app-developers app
After two weeks of forum crawling and surviving 2 soft-bricking incidents, I've finally decided to reach out for help from the experts :crying:
Currently I have an ATT HOX, unlocked/rooted/SuperCID - running stock ICS (4.0.4).
My goal is to get JB on it and then flash to Blade ROM (I tried flashing to Blade with ICS - OOPS!)
Even though the info is on the forums - it's not all together in a streamlined format for me to follow - I feel I could get lost and screw it up (again)
From what I gathered from reading - here is what I "think" I need to do from my current phone state:
1. Facepalm S-Off
2. Install OTA Rootkeeper then backup root
3. Flash stock recovery
4. Re-Lock Bootloader
5. Flash OTA ATT JB.zip using stock recovery
6. Unlock Bootloader
7. Flash TWRP
8. Restore backup root with OTA RK
9. Flash Blade ROM
Can someone please check my thinking and make sure I'm not missing something?
Or any recommendation of an easier process? I feel I'm going to get lost somewhere in those steps and end up in Oz.
Or maybe a recommendation on an awesome ICS Rom? (so I can avoid confusing myself)
I'm terrified of another 3AM morning and a bricked-out HOX.
Thanks in advance!
Do you mean this rom: http://forum.xda-developers.com/showthread.php?t=2134328?
Because that's a rom for the quad-core Tegra One X. If you've been doing that, it's no wonder you got bricked.
You don't need OTA Rootkeeper. You can just flash a rooted rom.
2 major points:
1) As already mentioned, Blade is not for our phone, its for the quad core One X. Stay within this forum section. If you are looking at any XDA thread that just says "HTC One X" (no mention of "AT&T, Rogers" etc.) near the top of the screen, you are in the wrong section. Stick to the forum section that mentions AT&T. Flashing a ROM for the quad core version won't work, and might also hard brick your phone.
2) Aside from S-Off which is a good idea) you don't need to mess with any of the stuff you mentioned (Rootkeeper, stock recovery, OTA zip) in order to flash a JB based custom ROM if you are already bootloader unlocked and have TWRP. With S-off, just flash the ROM. If S-on, just flash the ROM, then flash the boot.img with fastboot (if hboot 1.14 or higher).
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
redpoint73 said:
I'm not sure how you got the notion that you need to do all these other steps (maybe some process for the quad core forum?).
Click to expand...
Click to collapse
<---- desperate noob
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
I can't believe I lost sleep over the simplicity of it all.
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Thanks a ton guys!
razorc03 said:
But.... just to make sure I understand this correctly - Even if I have ICS currently installed, I can flash a JB based ROM without issues?
Click to expand...
Click to collapse
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
iElvis said:
Correct you can flash it.
But some people have been having issues on JB coming from older firmware. If you have problems later, then ruu'ing and updating is warranted. Right now it's overkill.
Click to expand...
Click to collapse
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
razorc03 said:
Would I be able to RUU to a stock JB? Or would I have to start from stock ICS again?
Click to expand...
Click to collapse
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
iElvis said:
There are no JB ruu's as far as I know. But you can run the 2.20 ruu and then flash the 3.18 ota, then unlock again and reflash everything. That's what I did. Whole process took about half an hour and wasn't complicated. Just be sure you're s-off.
Click to expand...
Click to collapse
Thanks for the info. But I need to bug you again.:angel:
A few questions about the ruu method. After you ruu, does that remove root, lock bootloader, and goes back to s-on?
And since I love numbered steps, here is how I am viewing it with my inexperienced understanding with question marks:
1. Check for S-off
2. Lock bootloader? (I guess not with S-off)
3. Run ruu 2.20 exe
4. Flash 3.18 ota
5. Rerun superCID (X-Factor xploit)?
6. Unlock bootloader
7. Flash TWRP
8. Flash ROM (Assuming S-off wasn't changed during the ruu)
I would love to be at your confidence level to run it it 30 minutes. One day I guess....
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
iElvis said:
Before you run a ruu, you have to relock. When you run it, it wipes your entire phone and returns it to stock-out-of-the-box (except for s-off). So you need to back up anything you want to keep.
Here's a corrected list:
1. S-off
2. Relock in fastboot
3. Run ruu
4. Copy OTA update.zip to internal storage
5. Flash in stock recovery
6. Unlock
7. Flash custom recovery
8. Flash rooted rom
None of this affects s-off. AFAIK, the only way to be s-on again is manually change it in fastboot.
I wouldn't do all this unless you have a reason to, as there are spots in here where you can get tripped up if you're a complete noob.
Click to expand...
Click to collapse
Thanks for the checklist! It makes me feel safer to know an exit strategy so I don't panic if/when stuff goes bad.
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
razorc03 said:
...and I also came from the original Samsung Vibrant. With that phone, I also had the idea that I could only use a ROM based of the current android version. Hence the carry over of thought from that side.
Click to expand...
Click to collapse
This varies completely by device, and firmware versions. Never assume that something you learned on another Android device applies to a different device.
razorc03 said:
I noticed you didn't list a step to re-root through custom recovery after step 7. Is the previous root still in place?
Click to expand...
Click to collapse
No, it's that once you're unlocked, you can re-root just by flashing a rooted rom.
Trying to solve a lag/crash issue with any ROM I install on my or my wifes phone. Reading the forums I've seen references to needing to install the official Jelly Bean RUU before flashing a Jelly Bean ROM like Viper XL, etc.
To do this, do I need to be S-OFF first?
Both our phones are already rooted (never took the 2.20? update, so never any issues with root).
Would it be something like this?
S-OFF the phone.
Install Jelly Bean RUU
Re-root
Install Jelly Bean ROM
Thanks!
that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?
Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X
ECEXCURSION said:
Instead of "re-root", just push twrp 3.xxx to the phone. Then you can flash whatever rooted Rom you want. Has to be v3 or higher since the touchscreen drivers were updated. Personally I downgraded my touchscreen drivers to use 2.2.2.0 instead cause I'm partial to that version.
Sent from my HTC One X
Click to expand...
Click to collapse
cwm ftw!!!
do the touchscreen driver downgrade like ECEXCURSION said though.
DvineLord said:
that would work fine, you would need to s-off to run the jb update. as far as lag from jb sense roms, are you doing a full wipe before flashing?
Click to expand...
Click to collapse
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.
jburkco said:
Yeah I completely wipe everything including storage. Still get lag after a while, still get freezes and reboots.
Just trying to figure out the best way to do this, step by step.
Click to expand...
Click to collapse
You'll want to:
s-off
run ruu
update if your ruu doesnt include the latest update.
ruu will not relock your bootloader nor do you need to relock so no need to unlock or reroot.
fastboot flash recovery. i suggest twrp 2.3.x
then you can downgrade your touchscreen if you intend to use an older recovery or an aosp rom but i like to think the updates made improve things so i wouldnt downgrade unless you need to for an aosp rom or older twrp version.
flash whatever rom you like! if you just want stock rooted boot to recovery after flashing and it will prompt to root your rom when you go to reboot from within recovery.
good luck and have fun!
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
-JB touchscreen firmware does not work with AOSP roms. Your touchscreen won't function.
-TWRP 2.4.x seems to cause problems with flashing for a lot of people.
jburkco said:
Okay, whats the reason behind downgrading the touchscreen drivers and using TWRP 2.3 vs 3.0
Click to expand...
Click to collapse
you need to downgrade touchscreen driver so you can use non-jb sense roms such as aosp roms and ics sense roms. he meant to say twrp 2.3 vs 2.4, twrp 2.4 can give many users random issues. i personally haven't had a single issue with official cwm.
Okay but since I'll be using ViperXL, the touchscreen wont be an issue. Thanks for all the help everyone.
2.4 doesnt properly wipe partitions and remnants are left behind causing issues.
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.