Related
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed (error: i have 3.0.1)
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Flash new radios now my phone is bricked and get teh DLOAD drivers on windows.
I'm gonna take a guess and say you flashed the latest firmware 3.16 without flashing the previous firmware update 3.15.
There is no radio only zip available from the latest OTA update for this very reason.
If this is the case your phone is unrecoverable . back to sprint
Sent from my EVO using xda premium
Shad Stang said:
First I must say that I have already fixed the problem. I flashed and RUU using step 8 and up on the DirtyRacun method and my phone us back to normal.
I'm S-off
HBOOT 1.15.2222
Originally had Venom 2.0.1 installed
Flashed Using TWRP 2.4.1.0
I did a full wipe before flashing. While I was flashing MeanBean 2.02 I think it just restarted without warning. When I tried going into TWRP again it wouldn't load, it would show the boot screen for a split second then reboot into bootloops. I tried fastboot flashing other version of TWRP but that didn't do anything.
From here I relocked and flashed my RUU accordingly with the DirtyRacun process. After unlocking my bootloader and flashing TWRP 2.3.1.0 I restored my old backup of Venom and I'm back to normal.
I checked the MD5 sums of the MeanBean ROM and they matched.
What the heck happen during the install?
Click to expand...
Click to collapse
u must have did something u wasnt suupposed to do cause meanbean would not hurt your phone in anyway bro
I second this, I am having issues as well.
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Cruise was right, i thought i had the radio that came with 3.15 but i really had the radio that came with 1.22 XD.
Need to Update...not sure how!
cruise350 said:
Let this be a warning for others that may follow in your footsteps. You need to make sure you know what you are doing before you start flashing firmware. Firmware is meant to be upgraded one step at a time, not jumping from an old firmware to the latest, this will brick you phone in most cases. Please make sure you have verified your current firmware that you are on and upgrade to the next highest in sequence until you finally reach the newest. Also, the radio is just a part of the firmware, so if you did not upgrade the full firmware in the past then you need to go back and install the full firmware that you were on and then upgrade to each subsequent one. If you are s-on the only way to do this is to relock and take the OTA. For those that are s-off visit Captain Throwbacks thread in the development section and start reading and learning. You may find a solution in it.
Click to expand...
Click to collapse
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
KEMODREAMS said:
(1) How do I know if I'm s-off or on?
(2) I keep getting an OTA update notification. Do I take this update? If so, once it downloads then what?
-Running MeanBean_1.7 (I know sooo...far behind. That's why I want to update)
-Android 4.1.1
-PRL 25012
-Kernel: [email protected] #1 SMP PREEMPT
BaseB - 1.12.11.1119
Build - 3.15.651.16 CL124461 release-keys
I just need a step by step process on how to update this thing. Video, tutorial. etc.
Thanks in advance!
Click to expand...
Click to collapse
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
cruise350 said:
Unless you bought your phone used, you should know whether you are s-on or s-off since it is an involved process to get your phone s-off. What ota notices are you getting? Are they from the ota updater built in to MeanBean, or is it the HTC update?
If its the MeanBean update you can let it update and it should work just fine. Your firmware will not be up to date, but MeanBean will still work. If its HTC then don't take the update.
If you are s-off you can update you firmware with the file provided in the first post of the MeanBean thread.
If you are s-on, the only way to update your firmware is returning to stock, locking your bootloader, and taking the HTC ota update.
Sent from my icrap 2 using Tapatalk HD
Click to expand...
Click to collapse
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Need to Update...not sure how!
ronniemayo said:
+1 if you boot into boot loader you will see whether you are s-off or not.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Ok so I did that and it says I'm s-on. Now what? Do I take the OTA update that says "This will update your ROM (MeanBean) to version MeanBean_3.06"? If so, once it's downloaded what do I do? Restart into bootloader? Also my Titanium backup is saying that it "could not acquire root privileges" What does that mean? Thanks for your help.
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Shad Stang said:
If you want to update meanbean then backup and flash the latest meanbean. If yours breaks like mine did, flash an ruu and dont be an idiot like me. im guessing it s a rare occurrence that mine broke the recovery
If your goal is to flash new radios then you have two options:
Two methods:
Get your adventure face on and follow the DirtyRacun S-Off process step by step (It worked for me on windows 7 x64 but its easy to use a ubuntu livecd)
Once you are s-off you can flash radios. DO NOT JUMP VERSIONS... EVER use the baseband version as reference in about phone and flash each version up until you are at the latest
OR
staying s-on and leaving yourself less prone to brick hell
recovery nandroid backup: system, data, boot
flash ruu
ota update
reroot
restore backup.
i dont know how to root from the latest version so idk if this is a good procedure. make sure you can root with the latest version
But really if you have a choice, ditch the evo and get the s3. you can firmware jump all you want, but the downside is that the s3 has sh*t roms. I miss venom and stock with goodies :crying:
Click to expand...
Click to collapse
You should read Captain _Throwback's firmware thread
You can root the latest OTA just click the link in my sig
Sent from my PoS MoPho
Hello!
My current phone setup is:
2.13.651.1 710RD stock ROM
1.12.11.0809 baseband
Hboot 1.19
S-ON
htcdev unlocked
TWRP 2.1.8
rooted (SuperSU)
The phone is bugging me to take the 3.16 upgrade. Stock ROMs are fine...I won't be playing around with custom ROMs (don't have time right now), and I don't need S-OFF.
After reading and researching, I'm still not sure how to go about upgrading, or if it is a good idea. There seem to be issues with the 3.16 stock ROM and TWRP, a number of users having trouble gettings ROMs flashed in, etc.
From where I'm at now, is the 3.16 upgrade worth it?
What would the procedure be?
1) Back up with Titanium
2) Relock
3) Take the OTA upgrade
4) htcdev unlock
5) Install recovery and root (install what version of TWRP?)
6) Restore Titanium backup
Seems like something is missing between (2) and (3).
Thanks for any suggestions and advice!
Not 100% sure but I believe you need to flash a stock recovery for the ota to work. So step 2.5 would be flash stock recovery.
{ParanoiA} said:
Not 100% sure but I believe you need to flash a stock recovery for the ota to work. So step 2.5 would be flash stock recovery.
Click to expand...
Click to collapse
Gotta do that BEFORE relocking.
Ahhh yes...flashing the stock recovery before relocking. Thanks for the tip!
I'm still a bit confused about the touch sceen problem, and exactly when that problem occurs. According to some posts, it seems to affect some versions of TWRP. If I flash TWRP after taking the 3.16 OTA upgrade, will the touch screen work in TWRP?
Thanks again!
jbhtexas said:
Ahhh yes...flashing the stock recovery before unlocking. Thanks for the tip!
I'm still a bit confused about the touch sceen problem, and exactly when that problem occurs. According to some posts, it seems to affect some versions of TWRP. If I flash TWRP after taking the 3.16 OTA upgrade, will the touch screen work in TWRP?
Thanks again!
Click to expand...
Click to collapse
As long as you flash TWRP 2.4.1.0, your touch screen will work fine.
Captain_Throwback said:
As long as you flash TWRP 2.4.1.0, your touch screen will work fine.
Click to expand...
Click to collapse
Captain. I am new to being S-OFF. Can I take the OTA and it not affect my S-OFF state. This is the first time an OTA has come out and
my phone being S-OFF.
Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
michaeldm said:
Captain. I am new to being S-OFF. Can I take the OTA and it not affect my S-OFF state. This is the first time an OTA has come out and
my phone being S-OFF.
Unlocked
S-OFF
Recovery: TWRP 2.3.3
Device: HTC Jewel/PJ75100 (EVO 4G LTE) | Hardware Version: 0003
Baseband: 1.12.11.1119 | PRI: 2.87_003 | PRL: 25012
HBOOT: 2.09.2222
Click to expand...
Click to collapse
If you're S-OFF, taking an OTA won't change that.
Captain_Throwback said:
If you're S-OFF, taking an OTA won't change that.
Click to expand...
Click to collapse
Thanks fort the help captain. been looking for that answer for the longest.
I ahve 2 more question.
1) When taking the OTA will it replace the recovery with a a stock recovery. I am running TWRP 2.4.1. Will I have to reflash it.
2) Will the OTA relock my bootloader. Do I have to unlock that as well? Is it necessary to be unlock if I am S-OFF?
Thanks for the help.
michaeldm said:
Thanks fort the help captain. been looking for that answer for the longest.
I ahve 2 more question.
1) When taking the OTA will it replace the recovery with a a stock recovery. I am running TWRP 2.4.1. Will I have to reflash it.
2) Will the OTA relock my bootloader. Do I have to unlock that as well? Is it necessary to be unlock if I am S-OFF?
Thanks for the help.
Click to expand...
Click to collapse
1) Yes, taking the OTA will replace your custom recovery with a stock one. You will need to reflash TWRP.
2) When you're S-OFF your bootloader is unlocked. You will just need to flash the latest DirtyRacun HBOOT so that fastboot commands will function, since it will be replaced by a stock HBOOT with the OTA.
You'll have to first flash the DR HBOOT via PJ75IMG.zip, then you'll be able to fastboot flash TWRP.
Captain_Throwback said:
1) Yes, taking the OTA will replace your custom recovery with a stock one. You will need to reflash TWRP.
2) When you're S-OFF your bootloader is unlocked. You will just need to flash the latest DirtyRacun HBOOT so that fastboot commands will function, since it will be replaced by a stock HBOOT with the OTA.
You'll have to first flash the DR HBOOT via PJ75IMG.zip, then you'll be able to fastboot flash TWRP.
Click to expand...
Click to collapse
Thanks you. don't want to seem dense. I am newbie. I understand what you are saying. Is there an order in which these things are done., Is there a link with the steps for dong the previous stated instructions. In which order do I need to do this.
Should I take the OTA first and then try to flash. or do all of the flashing first then take the OTA? I kinda of confused by the order. I already have the latest
HBOOT and RUU (RUU 3.15.651.16 - HBOOT 2.09) from DR. That's How I go S-OFF. If there a set of sequential instructions you can point me to I would be greatly appreciative.
Just an update on how the upgrade went...
The upgrading to 3.16 part went fine, and TWRP 2.4.0.1 is working fine. The restore from Titanium part didn't work great.
First, Titanium says that you can make an adb backup and restore from it after unlocking/rooting. So after the upgrade and before rooting, I made an adb backup since it appeared that all (or most anyway) my settings were retained over the upgrade. That didn't work, as Titanium said the adb backup was corrupted or unrecognized.
Next, when trying to restore my Titanium backup, there was some glitch where I could change to the folder where my Titanium backup was located on the backup folder selection screen (and a backup was recognized there), but this change wasn't internally accepted, and thus when going back to the main status screen, the default folder location was shown, and no backups were found to restore. After rebooting the phone a couple of times, this problem sovled itself, and I was able to restore. For the most part, everything was restored, other than a couple of widgets and settings. I sent a request to Titanium about the adb backup issue, but never got a response so I proceeded to restore the Titanium backup.
However, now I have another problem, but since it's a different topic, I'll start a new thread for that.
So i just got my One yesterday and it still has the .7 firmware / rom on it. I am going to root it and s-off right now, but just wondering a couple things.
1. Can or should i use an ruu to update the firmware to the more recent versions?
2. If yes, will this make me lose root or s-off? (i would imagine root would be easy enough to get back as long as i still have s-off)
thanks!!
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Sisyphus306 said:
At the moment, unless the situation has changed, there isn't an RUU for the TMo HTC One. One was released the other day, but it didn't work and HTC pulled the download. For now, I'd wait a couple of days to see if they release a fixed version. Your only other option would be to flash the .ZIP with the updated radio after going S-OFF.
Click to expand...
Click to collapse
Ah.. ok. That makes sense. I downloaded one that was labeled for TMO, but i will just wait until it all gets sorted out. I am not to concerned about the radio, those are always easy to flash. Was wondering if there was anything else in the firmware i needed (like when the one s got jellybean there was WIFI partitions that needed to get flashed for everything to work properly)
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
frettfreak said:
For anyone else that is searching for this answer, here is what i ended up doing and it worked well.
My phone came with the .7 build install (this was the very first build before any updates). I rooted, and went s-off BEFORE ANY OTA's we taken. At this point i still had the original stock rom, it was just rooted. Since I always like to at least try the newest firmware out (cause you never know what benefits it may have) I flashed the STOCK TMO recovery back onto the phone.
Now you can boot into your OS, and go through the normal OTA process that you would get in any unrooted rom. Once those updates are complete you will be on the latest firmware and ROM from TMO, but no root access. Since you still are S-OFF, you have no problems here, flash TWRP back on (or CWM, i prefer TWRP) and flash whatever you want.
Hope that helps someone else that may be looking for the same answers.
Click to expand...
Click to collapse
Would you mind linking the T-mobile stock recovery that you flashed? I'm in about the same situation you were in.
FYI, there is a working TMOUS RUU available now, you can download it through the following link. I downloaded it yesterday and used it last night, I can confirm it works.
http://forum.xda-developers.com/showpost.php?p=43963285&postcount=9
Hello all,
I usually don't like posting new threads as you can find all you need by searching, but I believe I have a particular situation.
I rooted my phone a while ago using the appropriate methods and then flashed this rom: http://forum.xda-developers.com/showthread.php?t=2440315
I didn't recognize until now, as I am trying to return to stock rom and stuff in order to clean install the new official AT&T update, that this rom somehow also updated my firmware to 3.10.502.2 but I am not S-Off. I didn't/don't know how it upgraded my firmware to this w/o being S-Off but it is. So I have read that if I try and install any other stock rom than my touch screen won't work. And in order for that to work, I think I'll have to gain S-Off and then flash an earlier firmware then flash a rom, but I don't really want to be S-Off for this phone.
Also another stupid mistake I did was not create a nandroid backup of my stock everything before flashing
So in order to accomplish my goal I believe my 2 options are to either gain S-Off, flash an ealier firmware (like 1.26.502.12) and then flash a stock rom or I saw a link that had a stock nandroid backup: http://forum.xda-developers.com/showthread.php?t=2272893
that I can maybe use to restore but will this restore my firmware too?
Any help would be appreciated
Download the 3.17.502.3 RUU and update that way. Backup your data, the RUU method wipes internal storage.
cschmitt said:
Download the 3.17.502.3 RUU and update that way. Backup your data, the RUU method wipes internal storage.
Click to expand...
Click to collapse
Sorry it took me so long to respond but thank you for the help. I appreciate it
Can I still update that way even though I'm still S-On?
spacely8 said:
Sorry it took me so long to respond but thank you for the help. I appreciate it
Can I still update that way even though I'm still S-On?
Click to expand...
Click to collapse
Yes, RUU updating is meant to be done with S-ON.
So I see a number of people reporting using Baseband: 1.13.11.1105, including Captain_Throwback. I'm on Baseband: 1.13.11.0830 and am having some trouble with the phone connection - dropped calls, static on the line, etc. but data is fine (in fact I can make voip calls through hangouts no problem, but incoming calls are normal phone).
I looked at C_T's firmware collection on themikmik but that only contains up to Baseband: 1.13.11.0830 with the 3.17 software version.
I'm S-OFF via rumrunner after having flashed the 2.10 hboot and 4.13 651.4 Sense 5 Android 4.3 - Deodex to update the partitions to the new format. I've since flashed CM11 snapshot M12. Same phone issues on the rooted Sense and CM11.
Thanks to Captain_Throwback for all the excellent guides and collections here. Any suggestions from you or anyone here on where to find the latest baseband, and if you think this or maybe a custom PRL may help. (Is it possible to flash a custom PRL in CM11 or do I have to flip back to my Sense nandroid first?)
Thanks!
The baseband you're looking for can be found with the 4.3 RUU. You can find said RUU in the first post of my Hboot thread (top link in my sig). Not sure how you updated your Hboot but not your firmware, but I suggest running the RUU. You'll remain S-off afterwards.
To answer your other question you have to be running a Sense ROM to install a custom PRL.
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
cmags said:
OK that's what i thought - that the baseband should come with the hboot. Can i try just the 2.10 hboot in captain_throwback's thread or does it need to be the full ruu? Otherwise the process would simply be to backup, ruu, flash recovery and restore, right?
Related question, is 2.8.0.3 the latest twrp that works with cm11 or is there a 2.8.1.0 that works as well?
Click to expand...
Click to collapse
I would run the RUU. Once done, you'll need to unlock and install TWRP again. Then you can restore your backup. As far as recovery goes I'm not sure which is most recent.
Well, that was only partially successful, and I could use some suggestions.
I did a nandroid of my CM11 M12 snapshot image, and ran the RUU in your post (RUU_JEWEL_CL_JB43_SENSE50_MR_Sprint_WWE_4.13.651.4_R…igned_one_step.exe).
Afterwards Hboot is 2.10, and Radio is 1.13.11.1105. Great. Bootloader remains S-OFF (expected), and unlocked (unexpected, but cool).
I run fastboot flash recovery TWRP-Recovery-2.8.0.3-jewel-CPTB.img. Boot into recovery, restore my CM11 image, and reboot. Phone just spins on the boot animation.
Rebooted into recovery, wiped cache/dalvik/system/data, install flash CM fresh, wipe again, then restore (without boot) - same issue. About to wipe again and try restoring Sense nandroid, or flashing roms (CM and Sense) anew to see if i get different results.
Any other thoughts? Any way to verify the partition layout? Any way to get a log of what its hung up on while spinning the boot animation?
Thanks!
The issue you're describing reminds me of the issue that comes about from being S-on and having to flash the kernel separately from the ROM. You say you're S-off so that's not the issue, obviously. If you ran the RUU then you are on the new partition layout. Not getting any errors in recovery when you flash the ROM, are you? You might want to 're-download the ROM, check the MD5, and flash again.
Got it sorted out. Something must have gotten corrupted in the nandroid. A stock nandroid worked fine. So i restored cm11 then flashed the rom over the top to fix the boot partition. Im all set now, though the updated baseband didnt fix the static and dropped calls. Must be a hardware issue.