Database Develop

Flashing RUU error. Help.

Hello. After tons of tries, I finally achieved S-OFF so I was going to try to turn my phone into a GPe by using RUU. Everything was going fine, the install failed once like it should, but then, my phone just couldn't get found by my computer, I unplugged it, plugged it back, and when on fastboot, the pc won't recognize the device. Also, now I'm getting this when I boot into fastboot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
, BTW, I've been reinstalling drivers like crazy for like an hour now, nothing seems to work, when I boot the phone normally, it does find it though, any help? Thanks.

For starters you still need the correct cid or supercid to flash RUUs...

xcesivemastub8ah said:
For starters you still need the correct cid or supercid to flash RUUs...
Click to expand...
Click to collapse
I followed this tutorial http://forum.xda-developers.com/showthread.php?t=2358781 I had the correct CID and MID.

haZethew0rld said:
I followed this tutorial http://forum.xda-developers.com/showthread.php?t=2358781 I had the correct CID and MID.
Click to expand...
Click to collapse
Yea. That tutorial is very clear about hand holding for a reason... It's very vague That's why there are tons of other guides.
Your bootloader needs to be locked to flash ruu.zips unless it's the specific one that matches your cid and you're s-off. From the pic it says you're unlocked and your cid is tmobiles cid not the Google plays cid. Also you said you can reboot fine. That means you never flashed anything. Consider yourself lucky. Unplugging and rebooting on certain errors while in ruu mode can easily lead to a bricked phone. Don't do that unless you know exactly what your error is.

xcesivemastub8ah said:
Yea. That tutorial is very clear about hand holding for a reason... It's very vague That's why there are tons of other guides.
Your bootloader needs to be locked to flash ruu.zips unless it's the specific one that matches your cid and you're s-off. From the pic it says you're unlocked and your cid is tmobiles cid not the Google plays cid. Also you said you can reboot fine. That means you never flashed anything. Consider yourself lucky. Unplugging and rebooting on certain errors while in ruu mode can easily lead to a bricked phone. Don't do that unless you know exactly what your error is.
Click to expand...
Click to collapse
Thanks for the info, so pretty much all I need to do is lock the bootloader and change the cid? also, by locking the bootloader, does that fix the connection issue? cause I can't get fastboot usb to get detected by my pc, every time it says the device malfunctioned or something.
EDIT: Just locked the bootloader, I still can't get fastboot to work.
EDIT 2: I tried fastbook on a Mac and it worked right away, was able to change CID. Now I'll attempt to flash the RUU.
EDIT 3: SUCCESS! A mod can please close this thread now.

haZethew0rld said:
Thanks for the info, so pretty much all I need to do is lock the bootloader and change the cid? also, by locking the bootloader, does that fix the connection issue? cause I can't get fastboot usb to get detected by my pc, every time it says the device malfunctioned or something.
EDIT: Just locked the bootloader, I still can't get fastboot to work.
EDIT 2: I tried fastbook on a Mac and it worked right away, was able to change CID. Now I'll attempt to flash the RUU.
EDIT 3: SUCCESS! A mod can please close this thread now.
Click to expand...
Click to collapse
simply change the title to [SOLVED]blabla

[Q] Another Soft-Bricked GPE One, HELP!

What I have:
M7_UL
Hboot 1.54
Radio-4A.18.3263.15
OpenDsp-v31
OS-
CID -- GOOGL001
As you can see no OS. I had regular 4.3 on the phone, not rooted only unlocked bootloader. No root stuff at all. I applied the little 4.3 update last week(literally). Thursday(Nov28) I woke up and saw the update notification, so I proceeded to install. Been on bootloop since.
What Ive tried:
So when I try to install the OTA from CWM I get:
no file_contextsfile_getprop: failed to stat "/system/build.prop": No such File or directory
Status 7
When I tried to load the 4.4 Nandroid from inside this thread:
Installing update....
Installation aborted. <--------------------(no error, no eplanation)
When I try the M7_UL_JB43_STOCK_UI.....: E:can't open /sdcard/0/M7.....(bad)
Ive read that the (status 7) error comes from a assert flag preventing the script to run on the wrong phone. I unzipped two OTA files and they both only reference to m7 device not the m7_ul
I thought the update only came out for the GPE One and that all GPE's arre m7_ul. Anyways, would love some help folx. I have OTG to load anything onto the phone from TWRP. Just need to know how to get out of this mess. Been without a phone since yesterday morning....

raphsabb said:
What I have:
M7_UL
Hboot 1.54
Click to expand...
Click to collapse
i have to sign off, but will get back to you tomorrow, in the meantime, stay away from any 4.4!!!
you're still on hboot 1.54, which would lead me to believe your firmware (even though it's not showing), is a 2.24.
If you need you're phone back up right now, just get a custom ROM (NOT 4.4), or even a Guru Reset from: http://www.htc1guru.com/downloads/stock-rom-downloads/
(unselect "stock recovery")
keep your phone unlocked, and we'll take a look at it tomorrow.

Current situation
For those wondering and scouring the forums as I did, heres my current situation,
I flashed the HTC_One_GE_2.14.1700.15 from here so I got the phone working again. The 4.3 update has already shown up, I dont want to load anything else yet. I want to know why I am on an old firmware as I did the updates provided all the way up to 4.3, and what should be done to get current and be able to run 4.4
So I got out of bootloop because I did not relock the bootloader, I hope this helps
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Help To Get OTA WITH S-off

hey guys
i have rooted device with ٍSuper CID + S-off + Flased stock recovery + Odexed Rom From revlation HD so i receive update and i download it then its show that msg any solo for that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

sadeg111 said:
hey guys
i have rooted device with ٍSuper CID + S-off + Flased stock recovery + Odexed Rom From revlation HD so i receive update and i download it then its show that msg any solo for that
Click to expand...
Click to collapse
i am back to stock CID now triying to make update

Post your fastboot getvar all please, make sure you remove your imei and serial number before posting.

sadeg111 said:
i am back to stock CID now triying to make update
Click to expand...
Click to collapse
variant system version error is caused by MID not matching the ota. So you will have to change your MID to match the version you are on.

OTA Sense6 not installing with SuperCID 11111111!
Hi Guys,
I think the CID-change will do you good. I tried for several hours to get the OTA-applied, however, only after I changed my CID from 11111111 to "HTC__001" the update finally applied. Before that I only got "assert failed". What's strange:
In the updater-script the CID "11111111" is "regarded" in theory, however, it did not work for me! Maybe there's a bug in the code like Apple's "Goto fail"-bug?
For everyone having issues with the Sense6-OTA: CHANGE YOUR CID TO "HTC__001" (thats two underscores __, CID is always 8-digit). Took me really several hours, I found it strange that I didn't see this anywhere mentioned.
Greetz,
Hallu

so i should change my MID OR NOT ?
???

It wouldn't hurt to change it, but must be the same as the one in the ota, you can find out what that is by finding the ota download on your phone, it's a zip file, open it and in there you will see another zip called firmware.zip open that and there should be android-info.txt open it, opens in notepad, it will say what cid and mid it supports.

Seanie280672 said:
It wouldn't hurt to change it, but must be the same as the one in the ota, you can find out what that is by finding the ota download on your phone, it's a zip file, open it and in there you will see another zip called firmware.zip open that and there should be android-info.txt open it, opens in notepad, it will say what cid and mid it supports.
Click to expand...
Click to collapse
is there any other way to know CID & MID for OTA except that why /? cuz when download done the file deleted and can't to extrart it to know -_-

sadeg111 said:
is there any other way to know CID & MID for OTA except that why /? cuz when download done the file deleted and can't to extrart it to know -_-
Click to expand...
Click to collapse
It shouldn't delete it unless it installs it, when its downloaded, select install later, it should just sit on your internal memory.

well see almost done with downloading

[Q] Help returning M7 to stock from Google Edition

Ok, I'm going to try to be as thorough as possible, so bear with me.
Last summer a friend of mine and I both bought ATT M7 64gb's. We pretty much immediately unlocked through HTC Dev and flashed the google edition rom. I decided to S-OFF and SuperCID, he did not.
I sold my M7 when the N5 came out, he was deployed. He just came back and his mic stopped working. He would like to return it to stock, tried, and had no luck, so I'm trying for him.
As mentioned, it's a bootloader unlocked ATT HTC One M7 64gb, now running 4.4.3 Google Edition rom. When I got it, it wouldn't boot, just went to a weird blue screen and did nothing else. Thankfully still had recovery and bootloader. I tried flashing a stock RUU from here:
http://www.htc1guru.com/downloads/ruu-file-downloads/
And got "Remote 99 unknown fail"
HMM
I tried flashing the newest CWM recovery and installing CyanogenMod, just for the hell of it, and got a "status 0" failure.
I tried the same rom with the newest TWRP and got "error executing updater binary"
I finally got the Bigxbie 4.4.3 GPE rom to flash in TWRP, boots fine, everything works (except the mic still of course).
Here's where we are right now:
Current ROM:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Bootloader info:
I read that flashing RUU files requires S-OFF, so I tried to do that.
Firewater yielded:
So I figured since it was an older hboot I would try RevOne, which I used a year ago.
That got this:
Here's the CID, I believe the correct one for ATT.
What are my options at this point? I have a booting 4.4.3 GPE rom with a hardware issue and he needs to send it back for repair. Just say screw it and send it in or is there a way to get back to stock from here?

Revone needs to be ran from a sense rom. Try flashing an old version of ARHD 4.2.2. you might need to flash TWRP 2.6.x.x to do so.. Once you have an older sense rom booted, revone should work. At least, that's what worked for me.
Then you will have S-OFF and can flash the RUU.

synt3k said:
Revone needs to be ran from a sense rom. Try flashing an old version of ARHD 4.2.2. you might need to flash TWRP 2.6.x.x to do so.. Once you have an older sense rom booted, revone should work. At least, that's what worked for me.
Then you will have S-OFF and can flash the RUU.
Click to expand...
Click to collapse
Having a hard time finding a 4.2.2 Sense rom, but I'll give it a go, thanks.

MSigler said:
Having a hard time finding a 4.2.2 Sense rom, but I'll give it a go, thanks.
Click to expand...
Click to collapse
Install this ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone

nkk71 said:
Install this ROM: http://forum.xda-developers.com/showpost.php?p=48955645&postcount=251
and then use revone
Click to expand...
Click to collapse
If I could hug you over the internet I would. Obviously it worked, thank you very much.

MSigler said:
If I could hug you over the internet I would. Obviously it worked, thank you very much.
Click to expand...
Click to collapse
no problem
and remember, once S-Off do not go S-On again!
Sent from my HTC One using Tapatalk

nkk71 said:
no problem
and remember, once S-Off do not go S-On again!
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm not messing with it any more. This should be sufficient for what is very clearly a hardware issue.

[Q] HTC one stuck on bootloader - after trying to get S-On back

hi
needed to revert my m7 back to stock for repair.
went from S-On to off. locked the bootloader, removed the "tempered". everything went okay
and then i tried going back to S-ON using this command --> fastboot oem writesecureflag 3
and now this is my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
no matter what i click i cant leave bootloader, please please help me, WILL DONATE to whoever helps me out of this.
thanks
ps. found this thread, not very helpful though as it is for EVO 3D and with linux http://forum.xda-developers.com/showthread.php?t=1627897

SultanAlush said:
hi
needed to revert my m7 back to stock for repair.
went from S-On to off. locked the bootloader, removed the "tempered". everything went okay
and then i tried going back to S-ON using this command --> fastboot oem writesecureflag 3
and now this is my phone
https://fbcdn-sphotos-h-a.akamaihd...._=1414465116_f9731b2ccfdfdceab9769399b7cafa6b
no matter what i click i cant leave bootloader, please please help me, WILL DONATE to whoever helps me out of this.
thanks
ps. found this thread, not very helpful though as it is for EVO 3D and with linux http://forum.xda-developers.com/showthread.php?t=1627897
Click to expand...
Click to collapse
Did you do the final step and flash the RUU to the phone ?
this one should work >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe

clsA said:
Did you do the final step and flash the RUU to the phone ?
this one should work >>
Click to expand...
Click to collapse
i stupidly tried going back to s-on before flashing the ruu
will this work now that i am S-ON and Locked?? and cant get out of the bootloader

SultanAlush said:
i stupidly tried going back to s-on before flashing the ruu
will this work now that i am S-ON and Locked?? and cant get out of the bootloader
Click to expand...
Click to collapse
yes just flash it from the screen in the pictures
plug the phone into the pc first

clsA said:
yes just flash it from the screen in the pictures
plug the phone into the pc first
Click to expand...
Click to collapse
do you mind just quickly telling me how to exactly do that? my first time..
and of course everything will be deleted right?
and i noticed the ruu says sense 5.5, im on sense 6 if that matters.

SultanAlush said:
do you mind just quickly telling me how to exactly do that? my first time..
and of course everything will be deleted right?
and i noticed the ruu says sense 5.5, im on sense 6 if that matters.
Click to expand...
Click to collapse
According to the OS in your bootloader screen you are on JB 3.62.401.1 the RUU provided is a higher version than what is presently on your phone. Since, you are S-ON you can only run an RUU that is the same or higher than your OS. Yes, it may wipe your information.
Connect your PC to your phone via the USB cable
Double-click the RUU.exe file on your computer
Follow the on-screen instrutions