Hello,
Is there now a way how to fix the Rumrunners Exploit 7x Vibrate bug? Someone have examined this phenomenon and knows how it is done?
It seems so, it is not in Systems u can modify Hboot, Radio, boot, data, system or something.
I already have flashed a new Ruu on ICS with new Radio and hboot from that ota updated ruu!
I have heard something about an ebr... That Exploit must be in in any higher systems where u cant get any acess or modify...
Maybe there is an extra MBR Master Boot Record u cant acess?
Anyone any presumptions? how this could have happened?
Sorry for my bad english and greetings from Germany
Related
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
I've posted in 2 Dev threads, and its like everyone passed right over them w/o any kind of answer of any sorts. What I've included below is a copy of my build.prop I've pulled. If you notice I am on 2.12.1700.1...I ran a ruu to GPE convert, but now that 5.0 is dropping like wildfire. I believe I've come across an issue. You see, I do not have access to a computer so everything I do must be done through my phone or my galaxy tab 4 tablet. I've superCID my device;however, the build.prop line ro.aa.cidlist gibes multiple cid's. These "other" cids don't show in bootloader.
In order to receive OTA..you must be
1. GPE cid (mid-im not sure)
2. On the appropriate firmware
3. Stock recovery
Right now, as it sits I'm on 2.12.1700.1 with philz recovery. I'll make the change to stock when the 5.0 OTA drops...
All I'm trying to figure out is:
Does anyone think I'll have problems based off what my build.prop is displaying ?
I can not change my CID (Unless you/someone knows of a way without a computer can do so)
ro.aa.romver=2.12.1700.1
ro.aa.maincid=GOOGL001
ro.aa.modelid=0P6B10000,0P6B50000,0P6B60000,0P6B12000,0P6B13000,0P6B11000,0P6B15000,0P6B16000,0P6B17000
ro.aa.cidlist=GOOGL001,11111111,T-MOB010,CWS__001,HTC__001,HTC__102,HTC__203,HTC__E11,HTC__405,HTC__Y13,HTC__304,HTC__A07,HTC__032,HTC__J15,HTC__016,HTC__M27,HTC__K18,HTC__A48,HTC__002,BS_US001,BS_US002,ROGER001
Some lines I've copied from my build.prop...my bootloader says superCID (1111111);however, this build prop seems to tell me that it looks like I'd be ready for the 5.0 OTA (When I flash stock recovery,which I'm still using philz)...I've asked entirely too much, even helped a few users with the things I understand, but I haven't received a complete answer...I'm s-off, GPE converted, 2.12.1700.1, rooted, superCID..I can not change my cid (no computer-no access to fastboot commands)...
Bump
Well now I can add some insight.
If in fact your completely converted than you must have the matching "CID"/" MID" as the out of box GPE HTC one m8 .no solid facts as far as the MID but I changed mine to match as I'm ready for the official GPE update. I'll just have to flash the stock recovery back when it's time.also I wouldn't use Xposed framework or anything like it just in case 5.0 rejects it.
I will add that the MID didn't matter for past OTA .I uses the 4.4.3 ruu so I could take the official 4.4.4 update
(easy as pie)
Well I believe I have completely converted to GPE...I followed graffixnyc thread for doing so, and got insight from HolyAngel. I'm still not even a 100% sure if I'm all good to go. I understand that I need to flash stock recovery, but I wasn't planning on doing so til the 5.0 OTA drops. I have searched everywhere for info about changing CIDs w/o the use of a computer,but to no avail...
Currently as it sits..I'm still on 2.12.1700.1, still superCID with philz recovery and bliss ROM...I'm switching back to skydragon 3.0.1 because the battery life is much better
Ultimately your going to need a computer at some point or wait till the ruu is released .
There needs to be more organization in this thread though. I'm not entirely stupid nor am I new to android. The reason I wanted GPE...I never used Sense based ROMs anyways. Partition is smaller with GPE too...
GOOGL001 is the CID, 0P6B17000 is MID for outta box GPE M8...I'm superCID, but never have done anything with MIDs as I let the RUU 2.12.1700.1 flash the MIDs included with the android info text of the RUU zip
I agree to e certain degree but with people making new threads about things that have already been covered definitely don't help.I'm in and out of all kinds of device forums to help because I like the challenges thrown out by all kinds of users.I realize you know what needs to be done and also realize your without a computer to get were you need to be.I hope I've not come off offensive in any way cause I am trying to help.
You didn't come off as offensive...I've gone against the grain of how things are done because after a few days of researching thread after thread after thread. I never found what I was looking for, and I still haven't...I guess I'll just wait til I get a computer to rewrite the CID. I'll just wait til 5.0 ota drops, flash the 3.09.1700.2 fw and see what happens..if anything I'll just reRUU to 2.12.1700.1...it seems to me that my phones ready for the ota anyways considering my build.prop suggests I have 1111111 and GOOGL001..
Am sure I'll see you around.good luck
I'm not going anywhere...nychitman quit supporting DU, so I'm looking into taking over in the near future...my computers still screwed til I get another hard drive put in it
@jxcorex28
Here you go man,I only hope GPE is a choice in aroma.
This is what found
http://www.droidviews.com/change-cid-mid-htc-one-devices/
MID tool zip below
http://d-h.st/w9V
I wonder if cid matters than ? I appreciate it, as it sits my mid is 0PB6B12000..Ill switch to whatever GPE MID is needed
jxcorex28 said:
I wonder if cid matters than ? I appreciate it, as it sits my mid is 0PB6B12000..Ill switch to whatever GPE MID is needed
Click to expand...
Click to collapse
Yes cid matters
So do you think superCID matters. From what I understand it doesn't because of being able to flash any ROM neantvfor any HTC m8 (as long as its GSM)
jxcorex28 said:
So do you think superCID matters. From what I understand it doesn't because of being able to flash any ROM neantvfor any HTC m8 (as long as its GSM)
Click to expand...
Click to collapse
Yes but what I've read 5.0 will check for everything. It's not worth the risk if you ask me.
To make 100% sure everything goes right just change everything to match.
Like I said all I have to do is flash stock recovery and except the OTA
After two days of searching I'm sucking it up and just asking you guys...
I have s-off but my bootloader is locked. I tried the one click superCID method and it outputs 111111 but its still locked when I try to flash a recovery.
I tried to use rumrunner even though its 2.xx because it worked for someone else and it said I needed root first...
My phone won't bug me to update OTA to get to 2.xx but think that might be a good thing... please help. My ultimate goal is to flash NuSenseSix
Day 3 still no luck...
I've tried the SuperCID method found on this thread
http://forum.xda-developers.com/showthread.php?p=36976137#post36976137
- problem is the file that is linked is CID 1 and not CID-2.apk So I am outputting 11111 instead of 222222 which doesn't work on HTC Dev. Anyone have the updated supercid file? *this thread is locked so you can't ask for help there*
I've also tried this method http://forum.xda-developers.com/showthread.php?t=2011611
Except for all of the mirrors are either missing or from corrupted websites
You do not state your software version, I suggest you try Sunshine. It may or may not work.
princessjae said:
Day 3 still no luck...
I've tried the SuperCID method found on this thread
http://forum.xda-developers.com/showthread.php?p=36976137#post36976137
- problem is the file that is linked is CID 1 and not CID-2.apk So I am outputting 11111 instead of 222222 which doesn't work on HTC Dev. Anyone have the updated supercid file? *this thread is locked so you can't ask for help there*
I've also tried this method http://forum.xda-developers.com/showthread.php?t=2011611
Except for all of the mirrors are either missing or from corrupted websites
Click to expand...
Click to collapse
If you are s off you can unlock using an adb command. Also, you need an ruu mode twrp.
I can help you flash a custom recovery and update your firmware using team viewer
Hi all,
I try to fix my stuck in airplaine mode and no IMEI issue by repairing efs folder.
Up to now I haven´t found an HTC RUU that could be installed.
Is there any other method to repair EFS? I heard of 3-parts ROM setups. Is something like that avialable for the ONEX plus?
I even can not find the location on my storage, where the efs folder should have been at times when the phone was OK.
Hints and Tips would be great
ICE
Hey guys,
it would help me a lot, if I only knew where I have to search for the damaged relicts of the efs on my One X+.
I can´t find it. Is it a separate partition?
Best Regards,
Wolfgang
Hello,
after endless nights I am faced with the following situation:
- Still stuck in airplane mode
- some write in forums, that a RUU could be the only solution to get the efs partition repaired
- RUU needs Stock Rom as a prerequisite
- Newest available RUU for unbranded HTC One X+ Europe seems to be: RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1 204.168.32_release_299688_signed.exe are
- That would need stock ROM 1.17.401.1
- Stock Rom 1.17.401.1 and hboot 1.72 don´t work together
- is this all correct?
- am I trapped?
Are there any ideas for me?
Best Regards,
ICE
ICEMAN_77 said:
Hello,
after endless nights I am faced with the following situation:
- Still stuck in airplane mode
- some write in forums, that a RUU could be the only solution to get the efs partition repaired
- RUU needs Stock Rom as a prerequisite
- Newest available RUU for unbranded HTC One X+ Europe seems to be: RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1 204.168.32_release_299688_signed.exe are
- That would need stock ROM 1.17.401.1
- Stock Rom 1.17.401.1 and hboot 1.72 don´t work together
- is this all correct?
- am I trapped?
Are there any ideas for me?
Best Regards,
ICE
Click to expand...
Click to collapse
if your device is s-off, then i think it should work.Did u try?
ps: dont forget to relock the bootloader first!
I received an OTA update on my AT&T M9 and proceeded to unlock the bootloader and flash a custom recovery, and forgot to make a backup of my system before flashing a new rom. Now I can't get any rom to load properly, and can't run the RUU program from HTC on any of my computers. Does anyone have a way of retrieving an official AT&T firmware zip or any solution? I'm at my wit's end, and HTC was no help at all. The phone is S-On, to make matters worse. And any rom I flash that manages to get to the welcome screen hangs at "Connecting to Wi-fi" forever.
Managed to fix it, had to S-Off to reset my firmware version, but to anyone who screwed up like I did, this is the AT&T Marshmallow update to the HTC One. Fixed my problem, and allowed me to restart from the beginning. To anyone that reads this, $25 is a small price to pay for an S-Off.
https://www.htc.com/us/support/htc-one-m9-att/news/