Related
Download removed, go ahead and thank user nimdae for pointing out the wrongness of my work. I am done with Eris dev work because of people like him.
nimdae <-- that user right there.
THIS IS NOT FOR LEAK USERS SO DON'T ASK
*start rant* THIS MEANS DON'T MESSAGE ME ASKING HOW TO USE IT ON 2.1LEAK, ITS NOT CURRENTLY POSSIBLE TO DOWNGRADE FROM LEAK. PLEASE STOP SENDING ME MESSAGES ASKING HOW.*end rant*
If it bricks your phone, not my fault (it shouldn't and I hope it doesn't).
Please read and follow the directions included in this thread.
unzipme.zip md5sum: 0ed3c91d7574367d65428b3bc230f217
This is fully working, I just did a full reflash to 1.5, including the kernel, the system software, the radio firmware, recovery image and the bootloader.
This must be done from a PC with Fastboot, which comes with windows. Linux/Mac users will have to find it and compile it. You will need to have Amon's recovery image installed to use this downgrade, at the end we will overwrite his image with the stock one.
Inside unzipme.zip are three files
downgrade.zip md5sum: c440c87f1e67f4b62e05da0d255e80e9
-Do not unzip/open/alter this file
--Contains your kernel, radio firmware, and system.
recovery.img md5sum: 71a4b633bdb32de9dcdd8953fef43cdc
--stock recovery image
hboot.nb0 md5sum: 38899da4e5e002e3be22900f5f4eb6f7
--Original bootloader
Step one:
Put hboot.nb0 and recovery.img in the tools dir of your sdk.
Put downgrade.zip on the sdcard of your phone
Step two:
Turn your phone off, then turn it back on holding the power button (red) and send button (green). Once in the boot loader press volume down, then volume up to get to Amon's recovery image. Go to wipe, wipe dalvik cache, and do a factory reset (aka wipe data). Then choose flash zip from sdcard, and flash downgrade.zip. The phone will flash the kernel, and system softare, then ask you to reboot. Let it reboot so it can flash the radio, it will restart back in the recovery image. You can power down your phone now.
Once the phone says "Formatting CACHE:" wait 30seconds and your done. This is an minor error in the update-config on my part, but it is not harmful and I won't be fixing it.
At this point if your just wanted 1.5 back, you are done.
If you want the original bootloader and recovery image, (ie 100% stock) continue on.
Step three:
Plug your phone into your PC. Power your phone on using the power button (red) and send button (green). Your phone should now be sitting back at the bootloader screen and say FASTBOOT USB. Now on your PC, go to the sdk tools dir in command line. Issue this command.
Code:
fastboot flash recovery recovery.img
Let it flash, when done wait a minute (just to make sure).
Then issue this command
Code:
fastboot flash hboot hboot.nb0
Once this is done, wait a minute then pull your battery and restart your phone.
You are now back at factory stock.
Thank you ivanmmj for showing me how to do this crud, and zifnab06 for telling me the right way to flash hboot.
...
..
.
jcase
Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.
This is not the droid your looking for......
move along move along.
What are the risks / requirements?
Darn, if this was a 2.1leak to 1.5 test, I would so be your guinea pig, since I'm getting a new phone tomorrow anyway. lol
Ruh17 said:
Risk of losing root permanently? I could be up to test, but I won't be home til after 5 pst. I'll hit you up on irc later to check if you're still looking for someone.
Click to expand...
Click to collapse
no you could just root again by loading the rooted 2.1 rom
Thanks jamezelle. Good job devs. Don't know how you find the time to work your magic every day.
I have 2 eris's here. Ones an extra. Let me know..
This kind of gets me excited being on 2.1 leak atm but I guess I should not bother to get hopes up doing things while rooted is a lot easier than when not so Im guessing I am going to be stuck.
OH DANG!!!!!
i am so excited!!! if you're like 90% seure it will work i volunteer!!!
i love 2.1 but i WANT to root SO BAD
Too bad its not for 2.1 leakers huh?
Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)
morbidpete said:
Has anyone tried this? I have an extra eris sitting around running the 2.1 root. If it has not been tried i will test it on the extra one (warranty have to send it back in a few days)
Click to expand...
Click to collapse
Please try it! I want to have a sure downgrade after root.
no links :-/
Apparently I need to fix it, and i dont have time right now.
jcase said:
Apparently I need to fix it, and i dont have time right now.
Click to expand...
Click to collapse
ohh ok. NP
where is the link to download
?
bah never mind shouldhave read the last post.... =X
Now, if I root and go stock, the engineering bootloader stays correct? Would they notice that the engineering bootloader was there if I turned it in for warranty? What's the difference in appearance on the engineering bootloader?
Ok so this is whats been happening. I have an eris im trying to load a custom rom on after I did the 2.1OTA
When I came out to XDA to use the root I was at first confused since it was all going from 1.5 to 2.1. After reading further I read reports that 2.1OTA is rootable just like 1.5 as long as I follow the proper steps.
I: Gaining root
An unlocked hboot will allows us to flash in a modified IMG ROM signed with test keys as supposed to requiring an official ROM from HTC. This will open us to be able to flash a modified recovery.
1. Download this file: PB00IMG.zip (md5: 63eacc5ede3b179f95dc22d8ef585f94)
2. Place PB00IMG.zip onto the root directory of your sdcard.
3. Power down your phone.
4. Hold Volume Down while you Power On. This should bring you to a screen saying "HBOOT" and some other stuff. Wait for it to load the image, and it will say Push Activate. Push the trackball button to continue. The process will take around 5-10 minutes. The first time your phone boots up it will take a lot longer than normal.
Click to expand...
Click to collapse
I think this is where things go wrong. When this was attempted it I saw that my bootloader was now reading 1.49 (phone never been rooted before) instead of the one people report you need to root which is 1.47
It loaded up under 2.1 still and I believe its still the 2.1OTA so I head on to next step for recovery img. something seems to have gone wrong with it too (possibly me messing up the sdk) as now when I try to load any recovery images via fastboot "FAILED <remote: not allow>
Now the more trouble part is now that its ready I follow the instructions on how to actually load the rom through the recovery and SD card method. I believe my recovery is not what its supposed to be either as when it loads I see an android next to a caution symbol with a yellow ! and when the recovery screen is brought up I only have 4 options. Ill type abit what I see
"
Android system recovery <2e>
Use volume key to highlight:
click power key to select.
Reboot system now
Apply sdcard:update.zip
Wipe data/factory reset
Wipe cache partition
E:Can't open /cache/recovery/command"
Now I have tried the instruction of wiping first with a data and cache wipe but it does not give me any options after that on to flash from sdcard
IV: Flashing a custom ROM
1. Download the Rooted 2.1 v0.8T2 zip file.
2. Copy the WHOLE zip file to the root directory of your SD card. (You can enable USB-MS enable from your shiny new recovery to mount your phone as a USB Mass Storage device.)
3. Choose Wipe. Choose data/factory Reset (In the stock ROM, the dalvik is stored in the data and you don't have an EXT partition... yet.)
4. Choose Flash zip from sdcard. Find the eris_0_3.zip file.
5. Wait until it shows as complete and choose reboot system now.
Click to expand...
Click to collapse
I have tried putting different ROM's on my sdcard. I attempted to downgrade using the tutorial provided and using the official RUU from PCD's website. (which both didnt work as downgrade would stop at recovery or RUU states wrong bootloader version towards the middle of the load) and I tried even renaming the ROM's to update.zip the message I get everytime is the same with 2 results one for the rom without the update.zip and one with it.
(with update.zip)
-- Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
(without update.zip)
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Also for those wondering I followed the method of installing drivers and using debugging mode ....all drivers seem to be working fine.
Also just for further info when I run the RUU to try and downgrade my bootloader goes back to showing 1.47 but the radio is still 2.40 if this gives and help
If some could first tell me where I went wrong and then where to go from here I will be most appreciative and im even willing on putting out a reward if someone can do this for me quickly (I am poor some it wont be a big reward but it will be something)
Thanks for any help.
This means you are on the leaked version now and there is nothing that can be done as of right now.
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
ca2l3vin said:
K well thanks for the short and sweet answer. Can anyone tell me how I went from stock 2.1OTA to getting the leaked verision? was it step number one that did it? something didnt load correctly after that?
Click to expand...
Click to collapse
So you saying you had 1.5, then got the OTA update from Verizon?
If that is true, are you sure you downloaded the correct root image? Cuz if I remember correctly, the non root one is named the samething. But I could be wrong as I never tried leak.
sounds like you got a bad pb001.img file.
ca2l3vin, it sounds like you may have downloaded and flashed the wrong PB00IMG.zip file. Where did you get it from?
nevermind addressed my issue
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
ca2l3vin said:
As far as I understood I got it from the tutorial was the first place I got it. After I started to have issues I downloaded it from another site thinking I could just update with correct one. Same name same file size and unfortunately same results.
also I did forget to put in my build number like the above post so ill drop that in now.
Firmware Version
2.1
Baseband Version
2.40.00.01.22
Kernel Version
2.6.29-5898f66b
[email protected] #1
Build Number
2.19.605.1 CL123435 test-keys
Software Number
2.19.605.1
Browser version
webKit 3.1
PRI Version
2.11_002
PRL Version
51866 (I know this is just area based)
ERI Version
5
Click to expand...
Click to collapse
I hate linking back to another forum, but I used this guide and it worked flawlessly for me.
http://androidforums.com/all-things-root-eris/53963-guide-stock-1-5-latest-root-2-1-a.html
Did not check your link to see if its teh same but I can vouch that this one is 100% working.
af man...seriously!
out of curiously i reboot my phone via power + volume up and saw my hboot version 1.49.... it's werid because I had my phone rooted long ago when I was running on 1.50. Anyway, I'm still able to boot into Amon_RA's recovery and using Tainted Vanilla ROM as of now. I'm thinking it might be because of *228 actually reprogrammed SPL somehow, because i saw glimpse of message during programming phase, it said "SPL unlocked" and "OTA update completed"
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
ca2l3vin said:
HAAZAAAA!!!! Thanks to droidkevlar
So what happened was the wording on the original tutorial confused me quite abit. basically on the recovery step I skipped over it completely due to the fact that it was worded as an optional step for just creating your own recovery point. Once I read the guide linked by droidkevlar I see that THAT is the actually Amon's Recovery image needed to load the custom ROMS in the first place.
ITS A NEEDED STEP not really an optional one (unless your a dev I guess)
I just did my first flash to the EvilEris Rom and now will be trying others out.
I think the tut should be possibly re-worded as I have seen others that seem to be in the same boat I was in. or atleast put in that all steps are needed.
Anyways all the steps and files are the same on both so just follow them both out all the way and it works with 2.1OTA
Click to expand...
Click to collapse
Glad I could help. Aloysius is also a very good one to check out. Heard there are issues with v12 but v11 maps is solid!
I'M BEING VERY CLEAR HERE-THIS IS FOR CDMA DESIRE ONLY, NOT GSM!!!
You have to be S-OFF to do this.
Because the CDMA desire does not have extended fastboot yet, this is the only way to change the ( white with green HTC ) screen to a custom splash1 ( anything you want ) screen.
Giving credit where its due, I'd like to thank:
Team unrevoked for S_OFF
MRE-net for his guide with the .img converter tool and half of his how to that I was able to use, I will put his link in here.
ipfreelytech for his encouragement and unknowingly pointing me in a direction that made sense.
The only part I played in this is bringing these together and finding the right way to create the .txt file.
If I missed anyone, feel free to point it out.
I'm going to make this quick and simple but explain in detail so no one should have a problem but not to where you have zero legwork yourself; it took me 3 weeks to figure this out.
Requirements: my android-info.txt file
MRE-net's nbimg coverter tool
And whatever flavor archiver tool to make the .zip
Download this-[URL=http://www.4shared.com/document/ymcXsiz-/android-info.html]android-info.txt[/URL]
Go to this link http://forum.xda-developers.com/showthread.php?t=795132,
download NBIMG command-line splash<-->image converter tool for your platform, read how to use the nbimg tool in command prompt ( extremely easy ). Read his how to thoroughly but PAY NO ATTENTION TO THE FASTBOOT PORTION!!!!!!!!!! Basically don't bother past #8.
Now, after you have converted it with nbimg tool, you want to zip up the android-info.txt and the splash1.img you created together and name it PB99IMG.zip ( exactly how I have it underlined ) and place it on the root of your sdcard. Reboot into booloader ( which on my phone the screen goes straight to fastboot ) the fastboot screen has the word FASTBOOT highlighted in RED, and below it a little, BOOTLOADER is highlighted in BLUE. If thats what you see then hit the power button once and you should see HBOOT highlighted in BLUE under the phone info. Give it a few seconds ( 10-15 ) and you should see this:
Parsing...(SD ZIP)
(1) SPLASH1
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
You want to hit vol up obviously and when you do it happens very quick, almost instant and then hit vol up again to reboot and BAM, you should see your new SPLASH!!!!!!
Now for those who this didn't work for, its NOT the .txt file. More than likely its a bad archive or you didn't do the image right, so I don't want a lot of negative feedback because people can't figure it out. I have changed mine a couple times before I wrote this up, WORKS GREAT!!!!!!!!!
Note: If your baseband differs from the mainver: in the .txt file then edit it to what yours is before you make the .zip or it wont work.
ENJOY GUYS!!!!!!!!!!!
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Rastaman-FB said:
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Click to expand...
Click to collapse
So far nothing else worked on cdma. The tool or manual commands. I'm going to try this out after work. Thanks for finding this!
Definatly going to give this a shot after work as well. Thanks for figuring this out.
Rastaman-FB said:
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Click to expand...
Click to collapse
Currently the CDMA Desire does not have extended fastboot commands, despite having s-off. The Alpharev team is working on getting it working so this is our only method available for now
It totally works! Thanks lohp75 for doubting me when I said it couldn't be done lol
Like I said bud, doubt creates possibilities .
Sent from my HTC Desire CDMA using XDA App
heavymetalmage said:
Currently the CDMA Desire does not have extended fastboot commands, despite having s-off. The Alpharev team is working on getting it working so this is our only method available for now
Click to expand...
Click to collapse
my bad mate, as you had s-off i assumed they would have included extended fastboot commands
AWESOME!!!! very easy to do just sounds difficult. thanks for getting it working and posting for us all!
You guys are very welcome :+). Its good that I am able to contribute back to the community instead of being a full time mooch . And like I said in the post, I detailed it so everyone should understand how to do it, but it will be so much easier when extended fastboot comes available to us!
Sent from my HTC Desire CDMA using XDA App
Ok I have followed this guide exactly.. I have done and re done the picture in Photoshop, tried converting it with several file converters, and they all get the same result...
That is the file I made.. I changed the baseband to coinside with my device (US Cellular HTC Desire)..
And it completely refuses to flash the zip. There are some error messages that pop up VERY quick, what I can see, says no image in zip.. but its there... converted with the tool...
Any ideas???
Well bud, the only problem I saw with it is you must not be s-off. If that's the case then go to unrevoked.com and get what you need for your phone. I looked in your zip and for ****s and giggles flashed it to my phone and it worked as smoothly as mine does. Of course I had to flash back to mine. So your zip is good.
Cythrawl said:
Ok I have followed this guide exactly.. I have done and re done the picture in Photoshop, tried converting it with several file converters, and they all get the same result...
That is the file I made.. I changed the baseband to coinside with my device (US Cellular HTC Desire)..
And it completely refuses to flash the zip. There are some error messages that pop up VERY quick, what I can see, says no image in zip.. but its there... converted with the tool...
Any ideas???
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App
good job! I knew this would work, glad you figured it out. Rocking a custom splash on my phone now
lohp75 said:
Well bud, the only problem I saw with it is you must not be s-off. If that's the case then go to unrevoked.com and get what you need for your phone. I looked in your zip and for ****s and giggles flashed it to my phone and it worked as smoothly as mine does. Of course I had to flash back to mine. So your zip is good.
Sent from my HTC Desire CDMA using XDA App
Click to expand...
Click to collapse
Yes its S-Off.... I have Cyanogen Mod on it... I can do everything else except change the boot splash...... I am at a loss why it's not working for me.... Followed the guide exactly...
EDIT::: Just tried the Unrevoked FOrever patch too.. still the same issue....
This is what the Bootloader says:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.0000
MICROP-051e
TOUCH PANEL-SYNW0101
RADIO-2.05.10.06.29
Jul 5 2010, 19:14:11
Everything seems right and correct... Oh well... I give up...
Does it give you the option to update, or does it flash a bunch of crap real quick then back to hboot? Maybe try and redownload my original. txt file and don't modify it at all, zip it up and try again. I was able to flash yours without changing the mainver: surprisingly.
And the unrevoked that you did was through recovery right?
Cythrawl said:
Yes its S-Off.... I have Cyanogen Mod on it... I can do everything else except change the boot splash...... I am at a loss why it's not working for me.... Followed the guide exactly...
EDIT::: Just tried the Unrevoked FOrever patch too.. still the same issue....
This is what the Bootloader says:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.0000
MICROP-051e
TOUCH PANEL-SYNW0101
RADIO-2.05.10.06.29
Jul 5 2010, 19:14:11
Everything seems right and correct... Oh well... I give up...
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App
lohp75 said:
Does it give you the option to update, or does it flash a bunch of crap real quick then back to hboot? Maybe try and redownload my original. txt file and don't modify it at all, zip it up and try again. I was able to flash yours without changing the mainver: surprisingly.
And the unrevoked that you did was through recovery right?
Click to expand...
Click to collapse
yes it does exactly that.. flashes up a bunch of crap real quick then back to HBoot.. And yes I applied the Unrevoked forever with recovery too (which told me I already had S-OFF). I have also tried it with your original text file (which is why I edited the baseband as I thought that was the issue)..
Its pretty odd that it doesnt work at all.... its got me totally scratching my head atm.... Im gonna try a couple of other things, but I think I wont be able to do it until the next release of Unrevoked that allows the Fastboot stuff like the GSM Desire...
EDIT:: Just tried removing all zips from the root of the SDCard and only have the PM99IMG.zip there.. Still the same result...
Ok, when I first started to play with this I got the same thing. I uploaded the zip to ipfreely who then told me it was corrupt, if he couldn't open it then phone can't right. So the next night I stopped using my windows environment and went back to using the mac osx archiver and tried it again. This time it showed flash errors, that told me the zip was good but info bad. So now I strictly use my mac and that's also where my cs5 is at.
Point being don't give up. Two more suggestions, try a different archiver, and as stupid as it sounds download your zip attachment from your post straight to your phone, again sounds stupid but exhaust all possibilities!
Cythrawl said:
yes it does exactly that.. flashes up a bunch of crap real quick then back to HBoot.. And yes I applied the Unrevoked forever with recovery too (which told me I already had S-OFF). I have also tried it with your original text file (which is why I edited the baseband as I thought that was the issue)..
Its pretty odd that it doesnt work at all.... its got me totally scratching my head atm.... Im gonna try a couple of other things, but I think I wont be able to do it until the next release of Unrevoked that allows the Fastboot stuff like the GSM Desire...
EDIT:: Just tried removing all zips from the root of the SDCard and only have the PM99IMG.zip there.. Still the same result...
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App
lohp75 said:
Ok, when I first started to play with this I got the same thing. I uploaded the zip to ipfreely who then told me it was corrupt, if he couldn't open it then phone can't right. So the next night I stopped using my windows environment and went back to using the mac osx archiver and tried it again. This time it showed flash errors, that told me the zip was good but info bad. So now I strictly use my mac and that's also where my cs5 is at.
Point being don't give up. Two more suggestions, try a different archiver, and as stupid as it sounds download your zip attachment from your post straight to your phone, again sounds stupid but exhaust all possibilities!
Click to expand...
Click to collapse
Tried 2 different archivers now.... WinRAR and 7zip... both same result.. I will get round to putting a Virtual Linux box with Virtualbox and try it with that... I all also try winzip just to be sure...... Not giving up just yet...
To be honest, thinking about it, if it was the archiver I was using then it should not have worked (my archive) on your phone either. The fact that it did, says its nothing to do with the Archiver otherwise you would have had the same result as me....
Cythrawl said:
To be honest, thinking about it, if it was the archiver I was using then it should not have worked (my archive) on your phone either. The fact that it did, says its nothing to do with the Archiver otherwise you would have had the same result as me....
Click to expand...
Click to collapse
I know I had an issue the first time around because I named the file PB99IMG.zip which really made it PB99IMG.zip.zip and it didn't show up. Probably not your issue but just a thought. Maybe you'd like to post the image, your baseband version, and we can make a file, test flash it and repost it for you to verify it works. Then, if it still doesn't work, we know it is your phone and possibly an issue with s-off that you may have to alert the unrevoked folks to. Try mounting /system to rw while booted and see if that works. That would be an indicator whether s-off is truly working.
sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.
sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!
evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.
I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium
Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!
now i'm off to screw something else up!
*** I HAVE SOLD MY M8 BUT I WILL TRY AND KEEP THIS UP-TO-DATE WHEN NEW RUUs COME OUT ***
*** NEW GUIDE AS WE NOW HAVE AN RUU!!! ***
This guide is for Windows-only. The reason for this is because the htc_fastboot file used is a Windows binary and there doesn't appear to be a version for Mac/Linux
This guide will allow you to return your EU, unbranded M8_UL device to 100% stock (inc. locking the bootloader and removing the tampered flag) for resale purposes or to return to HTC. It does not cover carrier-branded handsets and does require you to be S-OFF but Step 3 can be done on an S-ON EU M8 so long as your bootloader is relocked and you match one of the CIDs listed below. A lot of this can be used to restore a US carrier M8 as the RUUs are available, though, but you'd have to get the relevant RUU.zip from the EXE (which is very easy)
This process applies to the following CIDs:
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
You need the following files stored in your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (renamed to ruu.zip - not ruu.zip.zip!)
md5:4e03845aeab375746b4553e610047680
htc_fastboot.exe - *** REMOVED DUE TO HUGE AMMOUNTS OF SPAM REQUESTS ***
md5: 7343C5BCEC64373F83D69BD074954759
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (renamed to recovery.img) md5:
e51c6ce8db0b7318ef31e1e7bd03c96e
And you'll also need HTC Sync Manager - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it for the drivers and then uninstall it but leave the drivers on your PC)
All commands in bold are to be done in a command prompt window in your fastboot folder
1. 'Lock' the bootloader and reset the tamper flag
We know we can relock the bootloader by using the command 'fastboot oem lock', but it will show 'RELOCKED' on the bootloader and still show the phone has been unlocked in the past. With S-OFF we can set it back to 'LOCKED' . To do this, we need to use TWRP and adb shell
Flash TWRP in the usual manner by connecting the phone to the PC whilst in the bootloader and flash by using the command fastboot flash recovery recovery.img. Once flashed, boot the phone into TWRP and connect to your PC and make sure the drivers are successfully installed. To confirm it's working type adb devices and it should be listed with your devices serial number. Assuming you can see the device, we can now use adb shell to change the flag from 'UNLOCKED' to 'LOCKED' by using the following commands:
adb shell
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
Once the command has finished, we can continue using adb shell to reset the tamper flag by using the following command:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
Once this has finished, we can exit out of adb shell by simply typing exit. Then reboot the phone into the bootloader through the menu in TWRP so we can confirm the flags are set back to stock.
2. Change the CID (if required)
Now we're in the bootloader and are 'LOCKED' and not listed as modified (but still S-OFF) it's best we reset the CID so moving forward things are easy. To do this, you just need to use fastboot oem writecid HTC__001, or whichever CID your device originally came with from the list at the beginning of this guide. Once you've reset the CID, reboot the bootloader to confirm the changes using fastboot reboot-bootloader
3. Flash the RUU
We are now at the point where we can flash the RUU and restore the phone to 100% stock. To do this, we first need to boot the phone into RUU mode using the command fastboot oem rebootRUU. Once in RUU mode, you'll see a silver HTC logo on the phone and that's it. At this point, we now use the HTC fastboot package to flash their RUU.zip file using the command htc_fastboot flash zip ruu.zip. This process will take a few minutes, and the phone will reboot a few times but once done it'll say complete. At this point, reboot the phone back to the bootloader using fastboot reboot-bootloader
4. Factory reset the device *** OPTIONAL ***
Having flashed the RUU, I always prefer to do a factory reset to make sure everything is in order. To do this, boot into the stock recovery and once at the black screen hold volume up and press power to get into the menu and then select 'wipe data/factory reset' using the volume buttons and use power to select the option.
5. Reboot the phone
Pretty obvious this - just select 'reboot system now' and you should be good to go!
Reserved in case I need it
To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app
exad said:
To adapt this for every single m8 would be incredibly simple, I'm not sure why you would target such a small group? Nice guide never the less.
Also you always need to flash firmware files twice.
Sent from my HTC One_M8 using xda app-developers app
Click to expand...
Click to collapse
Because there aren't any pre-packaged ZIPs for any other build - only Nandroids. Now, I'm sure someone could make a flashable ZIP out of a Nandroid but I don't have the time for that! Plus, you've then got to make sure the right FW package is available as well as the stock recovery. I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
As I have an unbranded EU handset I did this guide - if anyone wants to use it as a template then please feel free to do so!
EddyOS said:
I also DIDN'T have to flash the FW package twice, it worked doing it once only but it does mention to do it again as a precaution
Click to expand...
Click to collapse
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.
EtherealRemnant said:
Any time hboot is flashed, you have to flash it twice for it to actually complete the full flash. There are no exceptions to the rule so if you did it once, you effectively didn't finish your firmware flash and run the risk of bricking your device instantly if you go S-ON to return it if the firmware was modified in any way over how it was stock. Please fix your guide before someone has modified their hboot to remove the red text and bricks their phone when they find the separate guide to go S-ON.
Click to expand...
Click to collapse
It says it already!! I didn't flash it twice as I was already on the correct FW. I've made it bold so people will notice it
EddyOS said:
e. Type: fastboot flash zip firmware.zip and wait for process to complete. Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Click to expand...
Click to collapse
EddyOS said:
It says it already!! I didn't flash it twice as I was already on the correct FW
Click to expand...
Click to collapse
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.
EtherealRemnant said:
You're on the correct firmware but not everyone will be. Currently your guide sets people up for a brick should they follow it and then follow the procedure to go S-ON afterwards as many actually get rid of the red text. Its not optional to flash it twice like you make it sound, its mandatory. If you won't change the text, I'll report the thread because this will result in bricks, end of story.
Click to expand...
Click to collapse
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock
Text changed to make it a bit more obvious to do it twice, although this is different to flashing an RUU ZIP (where you HAVE to flash it twice as that's how the RUU ZIP works). Surely if it needed flashing twice it'd tell you to do it (as an RUU ZIP does)?
EddyOS said:
In which case blame @mike1986. as it was taken from his firmware thread. I'll 'correct' it to please you but I don't agree with it as EU users will already be on the right FW. Nowhere does this mention that you have to go back to S-ON as that's nothing to do with this guide. All this is for is going back to stock
Click to expand...
Click to collapse
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
EddyOS said:
Text changed to make it a bit more obvious to do it twice
Click to expand...
Click to collapse
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.
EtherealRemnant said:
I can't believe mike doesn't have it right either but I checked his thread and sure enough, there it is. Hopefully he'll change it since you tagged him here.
Even if you are on EU firmware, if you modify hboot to get rid of the red text and you have an incomplete firmware flash, you will brick if you turn the secure flag back on to return the device for warranty/exchange. Most people who return to stock are doing so in order to return the device so it is just smart to assume that they may have changed their hboot at some point.
Thank you.
EDIT: Noticed your edit to your post. It doesn't say something like this:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
After you do the first command? I suppose its possible HTC changed it. I don't have a firmware zip for me to go back to my T-Mobile firmware or I would try it myself to see but every HTC I've ever had before, if you are flashing an image with the hboot in it you had to do it twice. I wonder if the hboot is actually removed from mike's image.
Click to expand...
Click to collapse
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up
EddyOS said:
That's correct, it's not there any more. And the HBOOT is in the FW ZIP (see attached). That's why I didn't make it 'mandatory' as I assumed it wasn't needed as that warning didn't come up
Click to expand...
Click to collapse
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works. I don't have the time to mess with it right now so I'd still suggest the old way. You know what they say about things that aren't broke...
EtherealRemnant said:
I still don't trust it and would continue to flash it twice to make sure. I don't remember the exact reason why the hboot caused it to fail all the time, something to do with the signature checking I believe.
The only way to really verify if it is actually flashing or not is to flash a different hboot this way and see if it actually works.
Click to expand...
Click to collapse
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)
EddyOS said:
You're probably right, I just did what I did but then again I never flashed a custom HBOOT so it wasn't gonna be an issue (and I'd never go back to S-ON anyway)
Click to expand...
Click to collapse
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:
EtherealRemnant said:
The only time I ever bother returning to stock is if I have to return the phone under warranty, sorry I was so mean about it, its just a serious issue when you have the potential to brick someone's device. I've never been unfortunate enough to brick but I've seen it posted before and what it came down to was something that wasn't explained clearly and could have been totally avoided. Thanks for the guide, I'm sure it will help many people. :good:
Click to expand...
Click to collapse
It's all good! I've made one last change to that point to highlight that although it's not strictly required it's strongly recommended to do it twice as a precaution
Not sure what else you can out as no doubt someone will get it wrong at some point...
EddyOS said:
Not sure what else you can out as no doubt someone will get it wrong at some point...
Click to expand...
Click to collapse
It wouldn't be XDA if they didn't! :highfive:
Is it possible on my phone with CID HTC__J15 and S-on??
sari94 said:
Is it possible on my phone with CID HTC__J15 and S-on??
Click to expand...
Click to collapse
You can use parts of the guide but not the parts with (REQUIRES S-OFF) next to it (basically 1 and 5 are what you need, so long as you have an unbranded handset)
Added CIDs that will work with this guide to help users - if it's not listed then it won't work
Im guessing that once your back at stock you'll get OTA updates?