Root [AT&T] At&t [ruu] 1.26.502.12

[clsA]

Not my work
Thank @designgears over at XDA

http://www.androidfilehost.com/?fid=22964708692722204

 

[LoyalServant]

RUU.. YES.... love it!

 

[scotty85]

awsome sauce :smokingsomb:

now,if the t mobile and sprint versions would pop up!

 

[LoyalServant]

Just out of curiousity has anyone tried this RUU?
I definitely downloaded it and stuffed it away for a rainy day but I wonder if it works now that I have done that.
Don't want the rainy day to come and I pull out my shiny RUU and find out it's stuffed.

 

[scotty85]

I've got it downloaded and rom.zip extracted. I have every intention of flashing it,but haven't gotten to it yet. Since this phone wipes the internal sd every time I run an ruu,its a bit more of a pain. Ill prolly get to it in the next couple days.

 

[LoyalServant]

I've got it downloaded and rom.zip extracted. I have every intention of flashing it,but haven't gotten to it yet. Since this phone wipes the internal sd every time I run an ruu,its a bit more of a pain. Ill prolly get to it in the next couple days.

I thought you had the unlocked or international version?
Would this RUU work on those?
My understanding is that it's the same phone but I am no expert.

 

[scotty85]

I thought you had the unlocked or international version?
Would this RUU work on those?
My understanding is that it's the same phone but I am no expert.

Correct,I have an international version. The ruu should work on any m7_u or m7_ul that's s-off and supercid(or cid changed to CWS__001). I have m7_u,and i do know m7_ul RUUs work on it.. its currently running the developer edition software/firmware that's one cool thing about gsm international phones... Lots of RUUs! I almost get a bigger kick out of running other regional/carrier ruus than I do running custom roms,lol

This is a good reason to be s-off... No security checks on signiture,main version or hboot,and the ability to change cid give you lots of ruu options for soft brick recovery. Your att ruu is only good with an s on phone as long as you don't upgrade to newer firmware. At that point you need a New ruu

 

[clsA]

DesignGears tested it himself ..I'm sure it fine

 

[scotty85]

im currently on it. working fine

 

[LoyalServant]

DesignGears tested it himself ..I'm sure it fine

Forgive me if I don't take the word of a guy that's leaking a confidential and copyrighted file on a forum that has become less than reputable of late.. then says he tested it himself... it's okay.

Now that Scotty says it's okay... I know it is.

Harsh.. yes.. but I have fond memories of someone giving me a beta copy of Multimate (after Ashton-Tate bought it) and claiming that it was clean.
Similar remark: xyz at Ashton-Tate said it was okay.. till it had some virus that made letters fall off the screen like the matrix.. but this was long before the matrix and at the time it was a virus spreading around across various BBS systems. I can't remember the name of that thing.... some other old fart chime in....

That, and XDA had a bad track record of having kids with GPL violations playing "If I show the source someone will kang it and say it's theirs!"

 

[scotty85]

its actually working really well. some combination of the ATT rom and firmware,and some edits to build.prop i found to make att devices more consistent on t mobile have really stabilized my data.

the GF and i went to eat,then meijer and target,and ill be darned if it didnt read 4g the entire time. usually its spotty,and drops down to edge in certain places along the travled route.

my cellular network widget did show umts 3g occasionally,and the 4g icon didnt change,but it did show hspa+ mostly,and never dropped to edge. few speedtests got anywhere from 7 to 12 mbps down. :smokingsomb:

i hate to change it now its working so good,but im curious if all have the same results by modding build.prop on other ruus.

of course,i guess its also possible that t mobile flipped on the 1900 band on a few more towers making it a huge coincidence

 

[myvwrocks]

just curious. is s-off required for this to work?

 

[scotty85]

just curious. is s-off required for this to work?

not if you are running this att firmware.

if you have t mobile or an international phone,or are running newer att firmware,thens off will be required. if you have a t mobile or intenational variant,then superCID will be required as well.

 

[myvwrocks]

ran to program and bricked the phone. AWESOME.

 

[scotty85]

ran to program and bricked the phone. AWESOME.

More info?

 

[myvwrocks]

ran utility from link above. seemed odd as an exe. connected phone ran utility and got error could not connect to phone on pc and black htc screen on phone when i unplug usb it says
***tampered***
***unlocked***

and wont power off or reset

 

[scotty85]

Ahhh. You are not bricked.

Plug back in and enter:
Fastboot reboot-bootloader

If that doesn't get you to normal Fastboot,relock and run the ruu
Fastboot oem lock

Then run dui(phone in fastboot or ruu screen)

Sorry for the short answer,I'm at work

 

[myvwrocks]

ok plugged in and it said it cant find the device. i popped the sim card and held vol down and power and it did reboot back to before i started. i think i am confused about the ruu process. i am currently rooted not sure if that is an issue but do i need to relock the bootloader. and then run the ruu.exe from the fast boot screen? will i have to reroot and instll recovery again? sorry havent done a ruu install yet just rooted the $#!t out of my htc evo design.

 

[scotty85]

ok plugged in and it said it cant find the device. i popped the sim card and held vol down and power and it did reboot back to before i started. i think i am confused about the ruu process. i am currently rooted not sure if that is an issue but do i need to relock the bootloader. and then run the ruu.exe from the fast boot screen? will i have to reroot and instll recovery again? sorry havent done a ruu install yet just rooted the $#!t out of my htc evo design.

sorry for the short answers earlier,and the late reply. so is your phone booting and working?

to run the ruu,you must have a locked or relocked bootloader. the utility can be started with the phone in the booted OS,or in the case of a non-bootling phone,in fastboot or ruu mode(the black screen with silver htc)

the .exe utilities are notoriously fussy. they often fail for various reasons,so i dont run them very often. i personally like to extract "rom.zip" from the utility,and then flash it in fastboot.

at the risk of overloading you with info,here is how you extract rom.zip:

the .exe utilities can be finicky,so if you have trouble getting it to run, you can extract "rom.zip" in the following manner:
-start the utility
-check the "i understand" box to move on to the next screen
-hide the utility temporarily out of site
-search your C drive for "rom.zip". you will find it in a temporary location(it will be in a different spot each time you run the utility)
-open the folder location,and transfer rom.zip to a safe location on your PC.
-unhide and cancel the utility,youre done with it.
-rom.zip can be renamed to PxxxIMG and flashed in hboot,from a FAT32 sd card

you can ignore that last bit about a FAT32 sd card,its for older phones. if youve had htc's before,your prolly familiar with putting a file named similar to"PxxxIMG" on the sd card and letting it flash in hboot. the rom.zip extracted from the utility is this type of file. with newer phones,flashing these types of files is a lil different,they must be flashed from a cmd window,with the phone in fastboot.

here are some directions to flash "rom.zip":

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

to answer your other question,yes,you will need to re-unlock and re-install recovery after running the RUU. an ruu is designed as an "unroot" solution, or emergency fix,if other attempts have not made the phone operational.

so... if your phone is working again,just holler if you have further questions about RUUs.

if you still need help getting it booted and working,let us know exactly what state the phone is in... what you can boot to,what you cant... whats on the hboot screen,etc. we can get you sorted and running

 

[myvwrocks]

The phone is working with rom build 10. I am at work now so I will try again when I get home. I will try doing it thru adb as it does seem more reliable. Thanks much. I will follow up tomorrow with the results.

 

[myvwrocks]

I was unable to find rom.zip. i ran utility and it failed at the end and had cool little exclamation triangles on all four corners of the screen. Ran it again and it took. Rebooted the phone and checked it out. All the AT&T apps were still there I loaded scottsroms cleanRom2.5. That was nice because it lets you pick what apps you want or not. Rebooted did the CWM helium restore and it's all better. Thanks again for your help. BTW not sure if its related but the cleanRom is based on RUU build 12. Not sure if in phone info it says that because I flashed build 12 or if his rom is built on build 12?

 

[clsA]

CleanRom 2.5 is 1.26.510.12 base ...from the leaked RUU

 

[myvwrocks]

That's great news because I love it.

 

[clsA]

That's great news because I love it.

Yes Sir it's a nice everyday use rom. The developer has unfortunately abandon it again. Not a real problem it functions perfectly.

We will have to find something else when the 4.2.2 update drops ( I'm sure someone will figure out how to clean it up too

 

[clsA]

sorry for the short answers earlier,and the late reply. so is your phone booting and working?
...

if you still need help getting it booted and working,let us know exactly what state the phone is in... what you can boot to,what you cant... whats on the hboot screen,etc. we can get you sorted and running

Wow thanks for that .. ton of good info their