• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Trying to return to stock

I just tried to SCid with the new token and got the same results, even though I tried to change it to 22222222... I'm gonna wait a little bit in the hopes that a new CID method comes up or I get a spare phone so I can send my one S in for the JTag method!! If I find a new method I will be sure to post it here!! Thanks again for everything! :)
 
i dont know if youre still following this thread,but there have been a couple claiming to have superCIDed from 3.16 RUU and OTA. :confused: there are enuff folks haveing prollems i feel like we have to me missing something...

http://forum.xda-developers.com/showthread.php?p=39403780#post39403780

mithg not hurt to run the 3.16 ruu( Androidfiles RUU ) if its compatible with your CID,and you havent allready.

sometime this weekend ill go over all this again and see if anything else pops out.

it just does not make sense that some could do the process from 3.16 and some cannot :mad:
 
Thats strange! I'm gonna check out that thread, thanks for posting it!! I'm gonna be following this thread till I find a way to SCID and if I do I will post the method here! If you look at my first post, I wrote down a 3.16 RUU that I downloaded and it matches the OTA that I was running before except that OTA was WWE and RUU is Europe. I havent tried it cause I didnt know if it would work but I think I'm gonna have to give it a try. I also heard that most people who have succeeded at SCID were on HBoot 1.14. I wonder if running the RUU will downgrade me from 2.15.0000 to 1.14?
 
I tried running the 3.16 RUU but no luck, it started out good but about 2 mins into the installation process, it said it was incompatible with my phone.. I'm gonna keep looking for another RUU but that one was definitely the closest to mine that I've found, oh well! Thanks again though....
 
Cyber Droid said:
I tried running the 3.16 RUU but no luck, it started out good but about 2 mins into the installation process, it said it was incompatible with my phone.. I'm gonna keep looking for another RUU but that one was definitely the closest to mine that I've found, oh well! Thanks again though....
Click to expand...

sorry that didnt work. you could try extracting rom.zip and flashing it via fastboot,but i believe that your build number or CID is just not compatible. its a little strange,as your fastboot getvar all doesnt reflect a build number :confused: so it seems you should be able to falsh any ruu that contains the same hboot. so it could be that the ruu does not contain a compatible CID on the android info.txt document. unfortunately,theres no way to check with windows. starting with JB htc is encripting their RUUs so that 7-zip,etc. cannot extract them :mad:

i keep looking for RUUs as well. ill let you know if i find anything else out :)

there really has to be a reason this is not working.
 
It's really frustrating knowing there's a reason for what's going wrong but not being able to figured it out! I'm gonna get to the bottom of this if it's the last thing I do!! LOL!!
HTML:
I was able to get back to Stock JB from a Nandroid backup I had done prior to trying out some custom roms, the problem is that the nandroid backup is the version of when I was running JB with the OTA update! I also have the Original Stock Nandroid of Ice cream sandwich 4.0.4 prior to JB OTA but after Unlocking bootloader and rooting! ICS is the ROM that came with my phone from purchase (factory)! When I updated to JB, I think my HBoot changed so I dont know if I can go back to ICS.. I have a feeling that if I could go back to the beginning (ICS, and original HBoot) i would be able to SCid but in order to downgrade hboot you have to be S-off right? Plus I dont remember what Hboot I had when I had ICS 4.0.4.! Is there any way to go back to stock ICS with the Nandroid I have? Thanks again!!
 
Cyber Droid said:
When I updated to JB, I think my HBoot changed so I dont know if I can go back to ICS.. I have a feeling that if I could go back to the beginning (ICS, and original HBoot) i would be able to SCid but in order to downgrade hboot you have to be S-off right? Plus I dont remember what Hboot I had when I had ICS 4.0.4.! Is there any way to go back to stock ICS with the Nandroid I have? Thanks again!!
Click to expand...

i believe you are correct that if you could go back to the old hboot,youd be fine. unfortunately,it is not possible to downgrade firmware,other than the brick method mentioned above(scary :eek:)

your JB firmware should run your ICS nandroid just fine,so you can certainly restore it and run it. youre welcome to try supercid from that,if you havent allready,but i dont believe the results will be any different :(
 
scotty85 said:
your JB firmware should run your ICS nandroid just fine,so you can certainly restore it and run it. youre welcome to try supercid from that,if you havent allready,but i dont believe the results will be any different :(
Click to expand...

My nandroid from 4.0.4 would not run last night after I flashed new boot .img for viper 2 - Havent tried since I got CM10 working though.
 
I dont mind trying the downgrade through the linux bricking method, I read it and it seems straight foward , but I dont have the right RUU ! Is it possible to do the bricking method with files from my Stock ICS Nandroid, something like a substitution for the RUU?
 
Cyber Droid said:
I dont mind trying the downgrade through the linux bricking method, I read it and it seems straight foward , but I dont have the right RUU ! Is it possible to do the bricking method with files from my Stock ICS Nandroid, something like a substitution for the RUU?
Click to expand...

no,cant use the nandroid,or even a pieced together ruu. youll definately need a full,signed by htc,official ruu for the firmware you want to downgrade to.

your previous hboot was prolly 1.14.0005. do you remember your previous build number? or what is your current build number? that may help us find an ruu you can use.
 
This is a screenshot of my current build #. I dont remember my previous build sorry!
 

Attachments

  • 2013-03-24_00-04-50_1.jpg
    2013-03-24_00-04-50_1.jpg
    25 KB · Views: 97
is that your stock rom? or just a rom based on that build that your running? the impiortant part is the "1500" in finding a matchng carrier RUU

the main version is edited prior to the downgrade,so that it wont hinder the older ruu from flashing. you wouldnt neccessarily have to use that an ruu with that same build number(1500),as long as its compatible with your CID.

we basically just need to start extracting them from the .exe,unzipping them,and looking at the android info text document. this one is from the europrean 2.31.401.5 ruu,so we know the 401's are out:
modelid: PJ4010000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__J15
cidnum: HTC__016
cidnum: HTC__A48
cidnum: HTC__M27
cidnum: HTC__032
mainver: 2.31.401.5
hbootpreupdate:13
DelCache:1
Click to expand...
 
That's my stock ROM, which is what I'm currently running. It came from a Nandroid that I made prior to messing around with Custom ROM's... So 401's wont work,and 1500 is what I should be looking for? My carrier is Wind Mobile which is (Globalive).
 

Attachments

  • 2013-03-26_07-36-02_1.jpg
    2013-03-26_07-36-02_1.jpg
    33.8 KB · Views: 98
We need to look for an ruu that either contains 1500 in the name, as the build number, or 1 that has your cid(GLOBA001) on the android info text document.
 
awsome! ok,im excited for you to try this,and trying not to get my hopes up myself that it works!

we are going to try the one vx/LTEvo method of supercid. heres what were going to do: one vx supercid

re-unlock,of youre not. install superuser if your not rooted.

enter the commands:

adb devices

adb shell

su (if needed to get #)

echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20

exit (exit again if you need to to get back to > )

adb reboot bootloader

fastboot devices

fastboot oem readcid (or fastboot getvar all if youd rather)

if you want you can check it out for your self first,the way i did:

-dump mmcblk0p5 just like you did when following the supercid guide
-open it up and check it out. youll see your cid at offset 00000010x04.
-run echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
-dump mmclk0p5 again,but call it something different(i called mine mmcblk0p5new).
-open it up and you should now see 22222222 at 00000010x04 instead of GLOBA001
-go ahead and reboot to bootloader and see if it sticks. :)

i tried it on mine,and it seems harmless. in a worse case,i believe it will just fail if write protection has got that block too :mad:

let us know how it goes! :D
 
Altaone said:
I am new but could this help?

http://forum.xda-developers.com/showthread.php?t=1633906

Third post in excerpt:
"if that fails run an RUU. If you need to change it to match your version, Extract the rom.zip and modify the android-info.txt to match your CID and MID."
Click to expand...

its not of much help to this thread. while s on,you can only flash files that are signed with HTCs special key. you cant edit the info on the androif info document because it will break the signiture.

so,in reference to finding an ruu to use for hboot downgrade,the ruu in question will need to pass the main version,signiture,CID,modelID,and a few other checks as well.

that info can be useful in other situations,tho :)
 
I tried it out, let me know if I messed up.. First attempt:I tried entering the commands as stated.. Second attempt I dumped the mmcblk0p5 like the supecid method, took a look at the file and saw my cid. Followed the rest of the procedure as stated and named it mmcblk0p5new but no changes... I'm entering the command "22222222", should I be entering it without the quotations (")(")??? Check out the screenshots.. Thanks.
 

Attachments

  • Onevx1.PNG
    Onevx1.PNG
    55.8 KB · Views: 96
  • Onevx2.PNG
    Onevx2.PNG
    61.7 KB · Views: 93
  • Onevxmmc.PNG
    Onevxmmc.PNG
    53.2 KB · Views: 92
you need to leave the quotes in place,you did everything just fine. looks like that block is being protected too :mad:

i wonder if one block is checking the other? my last suggestion before trying the hboot downgrade would be to try both processes at once...

-change the cid in mmcblk0p4 as you have been. before booting to bootloader,go ahead and change mmcblk0p5 as well like you just did.
-boot to bootloader and see if it sticks. if it does,reboot and see if it still sticks.

im pretty sure both blocks are write protected,so neither of them will change,but you never know ;)

after that,if you decide to try the downgrade,make sure the tools are using the same hboot that comes in your ruu. id hate to see you get stuck with an ruu you cant use becasue the hboot is older than what the tool used :eek:
 
Ok, I will try both process and cross my fingers, lol... If trying to change both doesnt work, I was going to try the RUU that I posted in post #41 with this method: http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html . Will that work or should I be trying that RUU after the Linux/brick method! I'm just not sure what you mean by the tools having the same HBoot as the RUU. I think the RUU that I posted has a 1.09 HBoot but I'm just baseing that on the title!
 
crap! :mad: so we know both blocks are protected and not performing checks on one another.


Cyber Droid said:
Ok, I will try both process and cross my fingers, lol... If trying to change both doesnt work, I was going to try the RUU that I posted in post #41 with this method: http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html . Will that work or should I be trying that RUU after the Linux/brick method! I'm just not sure what you mean by the tools having the same HBoot as the RUU. I think the RUU that I posted has a 1.06 HBoot but I'm just baseing that on the title!
Click to expand...

unfortunately,simply running the ruu as per that link will fail. even if we lower the main version of the phone,it will fail the hboot check,realizing that youre trying to install an older hboot than what the phone has on it.

other than jtag(wich is IMO safer) the only option to downgrade hboot is the brick method. in a nutshell:
-lower the main version
-brick the phone(read: un bootable,unusable,dead :eek:)
-use a process similar to jtag to write an older hboot(so the ruu wont fail the hboot check) and restore the other partitions so hboot will load
-run an older ruu

the method is here:
http://forum.xda-developers.com/showthread.php?t=1990043

but there is now a very large red disclaimer not to use it if youve taken the JB OTA. it may still work for you,but i would not recomend trying it.

looks like the download for the downgrade tool does take you to hboot 1.06,so if you did try it,youd need an ruu that contained hboot 1.06 or older

ill extract rom.zip and take a look to see what it has
 
You must log in or register to reply here.
Back
Top Bottom