Current FW Version : 3.28.401.7
Current ROM: Carbon (latest nightly)
Rooted, S-off
No access to computer
superCID 1111111
I want to get ready for the release of 5.0, and also use SkyDragon ROM. Right now I'm downloading RUU 2.12.1700.1, and after download I'm renaming to 0P6BIMG. I can not change my CID because I don't have a computer. Is there anyway I can change CID w/o access to a computer, so updates don't fail ? I've never messed around with RUUs before, so my assumption is that the RUU will flash stock recovery ? Any help would be greatly appreciated
This will NOT work on a CDMA HTC One GSM ONLY!
PSA After converting you will not be able to flash Sense based roms due to the different size of the system partitions between the sense version and the GPe. To get back to sense please follow the steps in post #2
This thread is NOT to support changing your MID, Changing your CID, Rooting or Flashing a custom recovery. If you need to learn how to do any of those do NOT use this thread to post in. Post in the respective dedicated threads to complete these processes. This thread is ONLY to support flashing the RUU. Nothing more, nothing less.
This is NOT a general 4.4.4 discussion thread.
Furthermore, if you need any more detailed instructions than what's stated in this post then you really shouldn't be doing this to your device. If you need a "video" or ask for "step by step" instructions you will NOT get anything more than what's in this post (at least from me). There is no easier way to do this process, there is no easier way to explain it. If you read the post and still don't understand what to do then I advise you to leave your phone alone... Read and then read some more until you understand everything.. WE WILL NOT SPOON FEED YOU IN THIS THREAD!
This procedure is not easy and is not really noob friendly, well flashing the RUU is not really difficult but it's the prerequisites that are more complex/risky. If the instructions aren't clear enough for you or you require further hand holding then I'm sure most of us would advise you stay away from the process.
Also, please do not PM me for support. PM's will not be answered. Post it in the thread. It helps other's having the same issue find a solution. If it's over PM it only benefits you and not everyone else
Prerequisites
S-Off,
ADB knowledge
Fastboot knowledge
Instructions:
First you are going to have to have s-off on your device. Thread for S-off (and support for S-off) http://forum.xda-developers.com/showthread.php?t=2708464
Full Conversion 4.4.4 RUU ZIP 2.12.1700.1
This will wipe EVERYTHING INCLUDING YOUR INTERNAL SD CARD!!!! PLEASE REMOVE YOUR EXTERNAL CARD IF YOU HAVE ONE so make sure you back up the contents before running this, but you'll end up with a factory-fresh GE. Of course, there's still no support, warranty or responsibility implied or otherwise.
The 4.4.4 RUU Zip supports the following MIDs and CIDs if your MID or CID is not in this list you will have to modify the android-info.txt file in the zip to match your MID/CID
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B*****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
TO GET OTA UPDATES AND NOT HAVE THEM FAIL YOU WILL HAVE TO CHANGE YOUR CID TO MATCH THE GPE CID(it has yet to be determined if the mid must match the GPE as well)
In fastboot mode type fastboot oem writecid GOOGL001. If you take the OTA without having your Cid set to GOOGL001 the firmware in the ota does not get flashed and anything controlled by the kernel won't work (camera, wifi etc) you must set your Cid BEFORE taking the update.
(please note.. If your model id or cid is not supported you can open up the android-info.txt file that's in the zip and replace one of the model ids or cids listed to match yours.)
Method 1
No computer required. Everything else still required. s-off, super CID/gpe CID etc..
1. Rename the RUU zip file 0p6bimg.zip (if your hboot is looking for a different name then rename it to whatever it's looking for)
2. Place the zip on your external SD card
3. Power off your phone
4. Boot into Hboot (hold down vol down as you power on the device)
5. it will load the zip and ask you if you want to proceed
6. Say yes
7. Wait
8. Profit
Method 2
ADB/FastBoot Method
you will the following message:
Just run the same command again:
Download Links Can be Found on my Website: http://www.graffixnyc.com/m8.php
DO NOT MIRROR
If you want to flash a custom recovery you will have to flash back to stock recovery to get the OTA's
You can get the GPE Stock recovery here
Special thanks to @pasker17 for allowing me to walk him through pulling all the partitions!! @beaups and crew for S-off
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, implodes, or flames start shooting from it or it kills your neighbor's dog. Flash at your own risk. This process is not for the faint of heart so I am not responsible.... It was the other guy... I swear....
I'm trying to change my sense partition to GPE partition. I know I can rename the RUU to 0P6BIMG and go thru that method, but what confuses me is the stock recovery ordeal. Do I really need to change my CID or flash stock recovery ?
Why did you cut/paste the RUU thread into your post, instead of just linking it? Its confusing, as you don't even state you are/aren't quoting another thread. In addition to making your post unnecessarily long.
Also, just another constructive criticism: please title your thread in a way that relates to the topic of your question. This is a Q&A and support forum section, and literally everyone who starts a thread here wants "HELP". So you thread title is not particularly useful. Having a specific and descriptive thread title may help attract users that are familiar with your particular issue; as well as helps to keep the forum organized.
Yes, the RUU does a complete conversion, so therefore includes stock recovery. Additionally, if you want to install official OTAs, stock recovery is required. On the other hand, if you want to use custom recovery in the interim, I don't see why stock recovery is such an ordeal. With bootloader unlocked and S-off, installing custom recovery after the RUU is easy even without a computer.
If you want OTA, you need to change the CID. I would think there is some way to do it without a computer using terminal emulator or some other method. But I don't know of a specific guide or method for this.
After googling "can I change CID w/o access to a computer" all I read is it must be in
bootloader/hboot mode .
Can't run a terminal wile in hboot without a computer. Maybe the right person can make a 0P6BIMP. type of flashable method but I'm not sure what it would take
AT&T HTC ONE M8
I couldn't link with just the app..well I probably could if I had copied the link from xda app to clipboard then inserted in browser or chrome. I'm not sure why I did it that way.
Yeah jball I got the same search results. I went through 10 pages, but typically after the 4th pages the search results typically become less on point and start matching the search query on other sites that have 1 word, so I gave up. I think at one point you could run terminal emulation through recovery, but I dont think that's an option on any recovery even if it were I wouldn't have the slightest idea how to work the commands...
With a computer..its easy just navigate to cmd..fastboot OEM writecid (whatever name of CID is)
HolyAngel explained it to me last night. I'm on a GPE partition now. CID hasn't changed, but I'm happy with the results of finally having what I needed. I'm on 2.12.1700.1 as of right now. What I'm not sure about is if firmwares are partition specific like, are there 2 versions of say 3.28.401.7 for sense partition and gpe or will that firmware work on both types of partitions
I didn't need to know how,I was replying to your question. I've been S-off and supercid sense days after owning my device
AT&T HTC ONE M8
I gave up on the idea of changing CID without a computer. Once I have the time to fix mine, I will..just wanted to know of possibilities of doing so w/o the access
jxcorex28 said:
I'm on 2.12.1700.1 as of right now. What I'm not sure about is if firmwares are partition specific like, are there 2 versions of say 3.28.401.7 for sense partition and gpe or will that firmware work on both types of partitions
Click to expand...
Click to collapse
GPE and Sense don't share the same software numbers. So no, there is no 3.28.401 GPE.
Firmware includes hboot, so I'd stick with the hboot for your version (GPE vs. Sense) and not mix the 2.
I don't see myself changing it anymore. The signal strength right now is about what it was on 3.28.401.7...don't fix it if it isn't broken...but thank you for the comments
Related
Sorry for long post but I've tried to provide a sufficient level of detail. If the answer is in another thread let me know. I've read quite a few of them now!
I've had my flyer for a short time and was loving it until I tried to mod it.
I installed CWM and Superuser root and had it "S-Off". I tried to flash the Leedroid HC rom. It seemed to be dead on re-boot just the HTC screen. I did a restore from CWM and got Gingerbread back. Some apps like default browser did not work though.
Now I had a mostly working system I followed the O'brian (think' that correct name) including using official HTC unlocker as was in instructions. Tried to use another HC rom and the ARU wizard. I got an error 155 and an RUU failure msg on device. Not sure what to do know. I have download this file "Best RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204108_signed". Nothing much happens when I run it other than seeing the install screen, then it exits. I really need some help to get back to some kind of working system.
Been through thread "[GUIDE][Flyer+View]Gingerbread S-
OFF/Recovery/Permaroot"
Can't follow post 17 to get S-Off as device will not boot into android!
From CWM Backup, the external SD card I used seem to have got corrupted. This could have been root of problems
data.img - file error
cache.img - file error
nandroid.md5 - file error
Boot.img, recovery.img and system.img files seem ok...
Got this msg from "revolutionary.exe" when tried to get -"S-Off" again.
Found your device: /sbin/sh: getprop: not found (/sbin/sh: getprop: not-/sbin/sh
: getprop: not, Android: /sbin/sh: getprop: not, ROM version: /sbin/sh
Your device: /sbin/sh: getprop: not, with HBOOT /sbin/sh: getprop: not is
not supported at this time.
Here are my device details:
INFOversion: 0.5
INFOversion-bootloader: 1.11.0011
INFOversion-baseband: 3822.10.08.07_M
INFOversion-cpld: None
INFOversion-microp: 0950
INFOversion-main: 2.23.405.4
INFOserialno: HT15WT403213
INFOimei: xxxxxxxxxxxxxxxx
INFOproduct: flyer
INFOplatform: HBOOT-7230
INFOmodelid: PG4110000
INFOcidnum: HTC__054
INFObattery-status: good
INFObattery-voltage: 4143mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: f0e1145e
INFOhbootpreupdate: 12
INFOgencheckpt: 0
I have hboot 1.11.0011 with CWM and access via ADB
Your help appreciated, at end of my tether!
allot to take in but best I could tell you were on gingerbread and maybe tried to flash Lee Droid HC version so that would not work. So then you followed an old thread to update to HC using Paul Obrien's method whcih requires HTC Dev unlock of the boot loader. At this point in time you can not flash any roms via recovery and your system will not boot into android.
Please confirm if I am following what happened to you and if while in your hboot screen it says Unlock up top.
Thanks for replying.
In summary that's correct.
If I hold down the vol-down button I get the screen that says:
"*** UNLOCKED ***"
"flyer PVT SHIP S-ON RL
HBOOT-1.11.0011
Micro P-0950
Radio 3822.10.08.07_M
eMMc-Boot
I still have USB access to it via fastboot I think
ok so here we go
no hc rom will just directly flash and boot because you can not overwrite the boot.img via recovery with HTC dev unlock. If you wanted to flash say Leedroid you would have to pull the boot.img from the rom package then fastboot flash it first then back to recovery and flash the rom. This is a hacky way to do it and to be honest every time you flashed a rom you would have to do the same. Here is what I suggest:
follow this thread here to downgrade
http://forum.xda-developers.com/showthread.php?t=1307759
you may likely be able to skip the misc version part. Hopefully you are aware of what your stock ruu is. If you tried running it before and it failed it was because you did not relock the boot loader prior to trying as is described in the thread I linked
Once, hopefully, you are back on GB, I would run this method to get to HC
http://forum.xda-developers.com/showthread.php?t=1358758
now, if you flashed a hc rom on your device and it will not boot, just as mentioned flash the boot.img via fastboot from the rom and it should boot. This is if you are looking for the easy fix, and assuming I understand everythign you have done to this point
I have downloaded this file to use as my stock RUU
"RUU_Flyer_HTC_WWE_2.23.405.3_R_Radio_20.3504.30.089BU_3809.07.04.06_M_relea
se_204108_signed.exe".
I will go through steps 1 to 8 of the thread and the rest if I can. I am not sure about step 8, it says boot to android. Are you saving if I managed to get that far I will have some kind of working system back before I proceed further?
I will have a go now and let you know how I get get long.
Cheers!
as I stated you may not need to do the misc version part. and you do not need to flash recovery and su if you already have both
I followed the steps and apllied the HTC unlocker again, then flashed the recover.img with no error messages and put the Super User zip on my external SD card. I used the CWM install from zip option, seemed to proceed, no errors reported. When I re-booted the tablet I just have an empty black screen and nothing else. Should I proceed with the RUU or stop and try something else?? If I turn it off it immediately comes back on again to blank screen. The only way to keep it turned off is to use the power down option on hboot menu.
you were unlocked
you already had recovery
you already had super user
you did not have to repeat any of these steps
if you can get into hboot then follow the instructions to revert assuming you have the three things mentioned above. You can likely skip the misc-version step. If you get a message while flashing the ruu that states older version you will have to do the misc-version step which since you can not boot into android can be done in recovery as adb will see your device in recovery
I do not really think you are in too bad of a way right now, but without meaning to offend you, you scare me with not paying attention to what is being said. One concern I have is to make sure you have enough battery life left. If you hit less than 30% you will not be able to run the RUU. If you are confident that you have that much continue. If not power down through fastboot and charge for a couple of hours.
Please read, read, read, and do nothing unless you are atleast 50% confident that you understand
Hi
I really appreciate the help you are giving me. The only did all the steps just in case as I am paranoid about missing something important. I do think I have enough battery so I will see if I can use the RUU I downloaded
Thanks
I am now running the RUU, it says "updating rom image". It is showing a black screen with the letters HTC in white in the middle. I hope this works.
Thanks for your help.
Comment has been edited, sorry for silly question, answered in thread you mentioned
that is normal
My god, I am so relieved. To tired to be estatic. It's taken me 24 hours and only two hours sleeps to get back to Stock! You save my bacon Mcord! The battery after flashing was nearly 100%. Thankfully I kept it charging even though it was bricked in an attempt to increase the rescue time I had. The only downside is I missed a ski class I'd paid for and having to pay the "Filefactory" company for a subscription so I could reliably download the RUU.
I've learnt the hard way for sure. Anybody else reading this don't assume that just reading the instructions is enough. My SD Card had corrupt backup recovery files on it. How often do we double-check the integrity of our backups? the SD card may have also mean that the rom loaded onto it was corrupt as well. I should have checked the MD5 of all the files.
Thanks again!! I think I'll pause a bit before Honeycomb and def backup!
happy your back up and running. your problem was just not fully understanding the differences between GB and HC and S off and HTC Dev unlock. the thread I linked you is the one to use going forward if moving to HC and looking to run custom roms. As I mentioned before read, read, read.
What if in addition adb don't work ?
Hello,
I tried to downgrade, but the adb command don't work : device not found response...
So I connot follow the process explained http://forum.xda-developers.com/showthread.php?t=1307759
Second the CWN is broken too... Is that a problem ?
Thanks
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
xionchen4628 said:
Hi, everyone. I hope someone can answer my questions or point me to the thread with the answer to it. Below is the information for my Spint Evo 3D running stock ROM:
Shooter XC Ship S-off RL
HBoot 1.40.1100
Android 2.3.4
HTC Sense 3.0
Software: Shooter_S_Sprint_WWE_2.17.651.5_odex
The last time I did an update of my phone after rooting was early this year. Basically I installed a zipfile provided by a user on this forum (apologize to that user for not being able to credit him) that allows me to get the OTA update on my rooted phone. Now that Sprint released the Ice Cream Sandwich update for EVO 3D, I am looking to upgrade the software again. The main question is...was there a thread for this topic where someone has provided a zipfile to allow updates to ICS for a rooted phone (stock rom)? Would someone please point me to it if they found it (sorry, did not see it)? Second, is the update process the same as before? Do I wipe cache and/or dalvik cache and then just install from zipfile? Any help is appreciated. Just didn't want to brick my phone. Normally I let my sister test things out on her device before I do the same thing but last year she decided to go with Motorola Photon while I sticked with HTC. Help? Thanks.
Tommy
Click to expand...
Click to collapse
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
gav-collins1983 said:
That's simple mate, but you will lose, recovery and root, I can help get them back, but first you will need to flash this http://cmw.22aaf3.com/shooter/radio/1.09.00.0706/PG86IMG.zip by placing on your sd card root directory and booting into bootloader and then following on screen instructions
Click to expand...
Click to collapse
Hi. Thanks for replying. Please bear with me as I am more of a casual user who barely have any inkling of why he is doing something, only how to get to S-Off, rooted through developers who provided step-by-step guide for "Dummies who want to Root their Phone". I have been in contact with Ramjet73 who is really kind to answer my questions but I am trying not to bother him too much hence I am trying to pass on any further questions that I have to other users such as yourself. So...thank you in advance.
From what Ramjet73 told me, I can just run the RUU.exe for 2.89.651.2 (Sprint ICS build) since I am S-Off. However he then inform me that I need to download a custom bootloader and custom recovery. This supports your comments that I will lose recovery and root after update? Ramjet 73 suggested a custom bootloader from ENG or JBear. How is that different from the bootloader that you suggested in your reply?
I assume that after I update both the ICS RUU and the custom bootloader, I will remain S-Off and rooted with superuser status and apps such as titanium backup and wifi tethering operational?
As for custom recovery, Ramjet 73 suggested 4Ext Recovery which I assume is 4Ext Recovery Updater (if I want a free version) or 4Ext Recovery Control if I am willing to pay for more options. Now in the past, I haven't really install any custom recovery other than what was installed when I used Revolutionary's tool to turn my phone to S-Off. I believe that installed Clockworkmod which I access when I boot to it using Power+Vol Down. Is Rom Manager the newest equivalent to that? What is your opinion on 4Ext Recovery vs Rom Manager.
So to summarize, I run the RUU.exe for ICS upgrade. Then I flash a bootloader like you recommended in your reply or one of the custom bootloaders from ENG or JBear. Then flash a custom recovery and I am all set? Sorry for all these questions and I hope you can help. Thanks.
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Sent from my EVO using xda premium
sullivan7221 said:
I'm looking for a cut and dry answer to this as well. I'll be monitoring this and if I see or figure out anything first ill post here.
Click to expand...
Click to collapse
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
ramjet73 said:
I thought I made it as "cut and dry" as possible:
1. Flash the 2.89.651.2 RUU (.exe from Windows or .zip from the bootloader if you prefer that)
2. Flash the JBear Sprint ICS (1.58.5858) bootloader so you can use fastboot commands
3. Flash 4EXT recovery using the "fastboot flash recovery recovery.img" command
4. Flash the superuser.zip of your choice or a custom rooted rom from 4EXT
I have more detailed instructions in my guide and a single download with the software you need for each of these steps.
Is there something that you don't understand about these steps, or are you just waiting for someone else to confirm that they work?
Edit: If you are looking for another way to do it you can follow the steps in this post, but you will wind up with the stock 1.58 bootloader and won't be able to run most fastboot commands unless you flash a custom bootloader. It takes about as long to flash the firmware, superwipe and ROM in that post and still flash a custom bootloader as it does to perform the above 4 steps, which I believe give you a cleaner ICS base, but it's up to you. That option will save you from having to reflash recovery.
ramjet73
Click to expand...
Click to collapse
xionchen4628 said:
Hi, sorry if I sound like I am doubting you. Your method are pretty simple. Being a relative newbie who rarely tinker with his phone, I am being extra careful to make sure I understand everything before doing something. In any case, I am going to just do it following your procedure. Just downloaded the QADERSO.zip from your guide. I will follow the 4 steps below. If I encounter any problems, then I hope you or other knowledgeable members of the forum can help out. If everything works out great, I will also post to this thread. Thanks.
Click to expand...
Click to collapse
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
ramjet73 said:
No problem.
I was actually responding to sullivan7221 because I thought all his questions were answered in my guide thread and then I saw his post in this thread that seems to be asking the same things. It's no problem if he wants consensus from more people, but I did take exception to his reference to a "cut and dry answer". I know that Samsung and other brands have simpler "one click" processes for rooting because I've used them myself, but I've tried to refine and simplify the root and S-OFF process for the Evo 3D as much as possible, and I tested a "one click" root utility that popped up in this forum a few weeks ago and it didn't work.
I understand that you and sullivan7221 aren't looking for root and S-OFF since you both have that already, but it's still important to use a reliable and consistent method for upgrading to the offical Sprint ICS build, which may not be the easiest.
Good luck with your upgrade!
ramjet73
Click to expand...
Click to collapse
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
xionchen4628 said:
Well...HELP! I successfully update my phone to ICS (not so hard). Then I hit the wall called "Step 2" and promptly bounced right off on my ass. The first thing I try to do was flash the jb_boot.img through fastboot cmd. I put my phone (which is still S-Off like you said, H-Boot 1.58 with "Locked" all the way up top) into Fastboot then connected my phone to usb, resulting in Fastboot USB. Then I use the command "Fastboot flash boot jb_boot.img". Then the problem happened. It said:
writing 'boot'
failed (remote: not allowed)
From discussions online, I also checked to see if it sees my device using 'fastboot devices" and it seems to recognize it: "HT179..."
How do I unlock my bootloader? What did I do wrong? I have the jb_boot.img and jb_boot.zip from your file and the pg86img.zip that was recommended by the poster above containing a radio.img. Any other way to flash it?
Help?
Click to expand...
Click to collapse
Okay, final update for those looking at this thread. I now have stock ICS, remained S-OFF and have superuser access. Basically I followed ramjet who was helping me out. The first thing that someone in my same position who wants to do the same thing, should navigate to ramjet's guide: (http://forum.xda-developers.com/showthread.php?t=1889438). Download his file (QADERSO.zip) and unzip it.
1) I turned on USB debugging on my phone and connected to my pc using "charge only" option.
2) I clicked on RUU.exe file in ramjet's QADERSO\RUU folder which then update my phone to ICS. When I access the bootloader, it now said "Locked", then "shooter xc ship s-off RL" and finally "Hboot1-58.5858". So now i have ICS, still S-off but with an upgraded locked bootloader.
3) Then I copied the custom bootloader "PG86IMG_jb_hboot_Sprint_ICS.zip into the root directory of my sd card (the zip file can be found in another of ramjet's post (http://forum.xda-developers.com/showpost.php?p=30014044&postcount=7) and renamed it PG86IMG.zip. Once you go into the bootloader, the zip file will automatically update. Now instead of "Locked" on the top, you should have "JuopunutBear".
4) First remove the previous zip file from the directory. I put the "SuperSU-v0.96.zip" from the QADERSO\Root folder in the root director of my sd card again. then i access my bootloader once again.
5) I went into fastboot and then connect to my Pc with usb. It should now say "Fastboot USB".
6) you can now flash any recovery img that you want. This is where I differ from ramjet's suggestion of 4ext as I did a backup of my system before all of this with clockworkmod recovery.
7) once the recovery of your choice is installed, then just install the supersu.zip file from your sd card and you should have a rooted phone.
Thanks to ramjet for his guide and his help. Now onto my next problem. going back to the state I was before updating to ics. Posting another thread about it. Anyone who can help out, please do. Thanks.
xionchen4628 said:
Well...color me stupid (and an ass) for not reading in depth ramjet's guide. From ramjet's guide, I went to mpgrimm2's "Evo3d(CDMA)HBoot/S-off Differences & Rooting Background Info 9-25-12" thread which eventually lead to ramjet's post with all the different bootloaders available. As suggested, I used JB's ICS bootloader and now in the bootloader page, it no longer say "locked" but "JuopunutBear" now. Onto flashing recovery.
Click to expand...
Click to collapse
General Information
This Has Been Made To Help Those How Have No Clue What There Doing When Upgrading There Firmware Note And Want A One Click That Mimiks HTC RUU
New From Prism Pirate Chest of goodies here it is FUU For The HTC Evo 3D
FUU Definition
Firmware Update Utility
There are a few Firmware flashing threads and lots of zips and good and bad instructions. However, i noticed that many users asked about what they get when they flash what they download and also about how to flash it with S-OFF on various threads. This confusion has occasionally lead to people losing their custom kernels and custom recoveries and/or their SDcard partitions being unintentionally wiped.
I am writing this because i believe in "responsible" sharing. Since the full RUU's aren’t shared but only components (modified as well as unmodified) with often insufficient documentation, which in turn leads to a lot of confusion among the lesser informed users, i will try to catch some of that. I believe that sharing full RUU's would be a lot safer, as only those who actually know enough about it can disassemble them. RUU’s do always reassure users that there is a guaranteed and safe way to go back.
FUU How To
[*]Download the firmware you want
[*]then run the installer
[*]install it to folder you want to any folder will do
[*]then run the tool and upgrade or downgrade your firmware
Prerequisites:All you need is a Windows System with current drivers and maybe HTC Sync Manager installed, it is better to have HTC Sync uninstalled and only the drivers left. Just try if the FUU runs without HTC Sync. On my system, i am always greeted with an “Error 170" if i try to run the FUU on a booted Android - it doesn’t recognize the phone with ADB. This is a typical driver and/or ADB error. Solution here: make sure you have the latest driver suite. FailSafe way to get them is to install HTC Sync Manager (remove it if you don’t like it afterwards but leave the drivers in the sytem!).
ZIP Flash HowTo
Step-By-Step:1. If device is booted into Android, reboot into bootloader by running:
Code:
adb reboot bootloader
1.a Or else, if your device is in a different state or you just prefer the button method:
Press Power for 15 seconds and hold Vol Down at the same time, when the screen and charging LED go dark immediately release Power but keep holding Vol Down until you see the bootloader screen. Notice: If the device refuses to reboot, you might need to hold it to a bright light with its light sensor. This is a very specific bug in the HTC ONE. The light trick always works.
2. Now place the Firmware_named_something.zip into your adb/fastboot folder
3. Now run:
Code:
fastboot oem rebootRUU
4. Followed by:
Code:
fastboot flash zip Firmware_named_something.zip
(replace "Firmware_named_something.zip" with the name of your zip)
5. Now check the console output. It should approximately look like this:
“flush" certainly means “Flash" so press the arrow up key on your keyboard and enter to run the flash command again without reboot...
Important: the flash process halts at around 75% to 90% on phone screen! This is normal and a safety precaution! The last few percent is the reboot, which is NOT happening automatically, so you get a chance to check the console output before reboot to make sure it is safe to reboot! The bar will only fill up to 100% once you type the following command:
6.
Code:
fastboot reboot-bootloader
Error handling strategies:IF IT SAYS "FAILED" do not immediately reboot the device If you reboot with a FAIL it could not boot up anymore! It could brick! If no flash is being accepted you have to find out what is causing the malfunction before rebooting your phone. Keep it alive while trying to figure out the error. It might be your cable, your USB ports (dont use hubs! Always straight-to-mainboard connections), it might be USB 3.0 which is not good yet, it might be bad configuration of your ADB and Fastboot... there are many possible sources for flash fails.
The least dangerous FAILED messages are listed below and are safe to reboot:
Safe to reboot / Flash didn't happen Errors (if you encounter one of them, you can just reboot. Nothing changed):
- 12 signature fail (unknown yet but safe to reboot)
- 23 parsing image fail (means something wrong with the image in the zip)
- 32 header error (means the zip couldn’t be read and unzipped properly)
- 41 Wrong Model ID (means its not the right device)
- 42 Wrong Customer ID (wrong CID means you gotta swap cid first as explained below)
- 90 hboot pre-update (means it only flashed hboot and you have to run the process again immediately to flash all other partitions WITHOUT a reboot inbetween).
- 99 UNKOWN (is not yet clear but safe to reboot, might indicate a defunct S-OFF or S-ON)
- 155 you did not lock your bootloader (Needs a relock for S-ON phones that want to update the firmware.)
In fact, if it aborts before the "(bootloader) start image[hboot] unzipping & flushing..." line it actually didn't write anything and you can probably just reboot. If you see it flashing stuff though (the stages after that line) and then it stops with a FAILED, chances are a little higher that something is now broken. In that case do NOT reboot but do as i said above.
For Error 12 “signature fail" do:
- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
For Error 23 "parsing image fail" do:
- change image names in the zip to stock image names like “hboot.img" or “radio.img" or whatever failed there....
For Error 32 "header error" do:
- Sorry i haven’t found the exact cause yet and don’t know a definite solution.
- Make sure there is only one . (dot) in the filename, before the extension. fastboot reads anything after the first dot it sees as the extension. If that is not zip, it fails.
- If that doesn’t help, you can also try: make the zip new with recommended settings, re-run the command, check your connections...
For Error 42 "Wrong Customer ID" and: 41 "Wrong Model ID" do:
Code:
fastboot getvar all
Read that output, take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly (For Wrong MID change the MID in the text, for wrong CID add your CID to the text).
For “Error 90 hboot pre-update..." do:
- Run the same flash command again which you just ran (press arrow up on your keyboard to get to the previous command in console)
- Don’t reboot in-between! (It wouldn’t brick you but it would just make you run the flash command twice again)
- This might be caused by the newer encrypted RUU's, they need their hboot to be flashed first so it can then decrypt the rest of the ROM.zip. Look at an encrypted ROM.zip from a RUU, you will notice that you can mostly extract the hboot without decrypting the ROM.zip, but you can't extract much else.)
For “Error 99 UNKNOWN" do:
- Check with other zip’s if they work!
- Check if your S-OFF is correct
- Tell me if you find out what’s causing an unknown error here!
For “Error 155 relock bootloader" do:
- run the fastboot command “fastboot oem lock" - only applies to S-ON phones that want to update the firmware. There a relocked bootloader is required. This error won’t show on S-OFF phones.
- Error 155 can also mean that you need SuperCID. On a few occasions this was shown when the RUU/FUU refused to run because of wrong region lock.
For “Error 170 Check USB" do:
- Sometimes shown when running a RUU or FUU. Indicates issues with drivers or ADB/Fastboot binaries. One way to solve is to run the exe with the phone already in Fastboot mode. Else you will have to dig into your windows driver system and try to fix there. Best option: re-install HTC Sync manager. Also, avoid USB 3 ports (the blue ones) - they have a complete new driver stack and that doesn’t work with ADB and Fastboot.
I always test all of these zips on my own device. But as always, flash at own risk. You're writing to critical parts of your phone. If anything goes wrong along the way, you might be bricked.
FUU Downloads (Windows only)
Update: added Hboot 1.58 FUU
Download
MD5: 995a8b883a5e39af471a93a84b4ff52d
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.57
Download
MD5: 87acbac59f169b32900e58f34e3390e1
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.50
Download
MD5: 233943ae4117d2fe64726afed8231b18
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.40
Download
MD5: 054e40f479b2075a20f12d5426d44bc3
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.30
Download
MD5: 04b13923379267a82d93cf913de62040
This FUU is A Stock Hboot. Contents: Firmware from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
Update: added Hboot 1.04 ENG
Download
MD5: 476a819ce37ff8fae2960de9dc2969a2
This FUU is A Stock Hboot. Contents: Hboot from ramjet73 So You should be good to Go. This package does wipes SDcard So Remove It Be For you Run it.
CreditsThank You Sneakyghost For The Tool And The Op
ramjet73 My mentor for HBOOT Modding
ramjet73 For The Hboots Witch I Modify Of off
DisclaimerYou are aware that writing to the security protected partitions increases your risk to lose the device exponentially. You understand and agree that i cannot be held responsible for such or any other damages. The flash process is theoretically safe and tested on various phones at time of posting, however you are the brains behind the wheel and you are solely responsible for the execution of the process. I will not accept any responsibility. The method itself is developed by Google and HTC, i only provide access and information to it and you execute it.
You understand that you should not do it if you are not willing to accept this risk.
Five star guide flashalot much appreciated
Sent from my PG86100 using XDA Premium 4 mobile app
Nice job!! Thank you!
busventinc said:
Five star guide flashalot much appreciated
Sent from my PG86100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cant take credit for the guide thank @Sneakyghost
I just made the proper edits for the evo and my one s
newdad23 said:
Nice job!! Thank you!
Click to expand...
Click to collapse
No problem
Thanks so much for this Flashalot!
Question on these, apologize in advance if its off base or nonsense.
Currently have a friend who is running 1.58 hboot S-ON, unlocked bootloader (htcdev) with MIUI 3.2.22 ROM. Would it be possible to use these to downgrade his hboot version and run revolutionary S-OFF and/or install JB ROM? Or would it be best to relock, revert fully to stock and use JuopunutBear method?
Thanks in advance
snackle said:
Thanks so much for this Flashalot!
Question on these, apologize in advance if its off base or nonsense.
Currently have a friend who is running 1.58 hboot S-ON, unlocked bootloader (htcdev) with MIUI 3.2.22 ROM. Would it be possible to use these to downgrade his hboot version and run revolutionary S-OFF and/or install JB ROM? Or would it be best to relock, revert fully to stock and use JuopunutBear method?
Thanks in advance
Click to expand...
Click to collapse
This is for s-off only sorry this is what you need
http://forum.xda-developers.com/showthread.php?p=31617712 it has it instructions on how to s-off
Sent from my PC36100 using Tapatalk 2
Flashalot said:
This is for s-off only sorry this is what you need
http://forum.xda-developers.com/showthread.php?p=31617712 it has it instructions on how to s-off
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply Flashalot
Exactly what I was expecting but figured I should ask just in case. Thanks again for your time.
snackle said:
Thanks for the quick reply Flashalot
Exactly what I was expecting but figured I should ask just in case. Thanks again for your time.
Click to expand...
Click to collapse
FYI, depending on the current firmware level of the phone you may not be able to run an ruu after the 2.89 base (they don't exist) without being s-off. If jbear doesn't work for you see..
See my reference post in Unknownforce's Ultimate Unbricking and hboot Downgrade Tool thread. It is known to work by bricking it twice.
Sent from my TouchPad using Tapatalk
mpgrimm2 said:
FYI, depending on the current firmware level of the phone you may not be able to run an ruu after the 2.89 base (they don't exist) without being s-off. If jbear doesn't work for you see..
See my reference post in Unknownforce's Ultimate Unbricking and hboot Downgrade Tool thread. It is known to work by bricking it twice.
Sent from my TouchPad using Tapatalk
Click to expand...
Click to collapse
Thanks for the heads up mpgrimm2. I believe he has a nandroid backup from just after he completed the htc unlock, still running stock rom. If it does turn out to be 2.95.651.6, would he able to restore this nandroid and continue with jbear method?
I know jbear will need to be mostly stock if not full stock. That nand backup may work depending on if jbear requires a relock and stock recovery or not but I don't recall. Things got a little vague when they moved support off of xda to their own site and stopped supporting windows based installers.
I'm sure Ramjet73 had some FAQ's in his thread for the old windows version that would answer it though.
Either way I know Unknownforce's Tool will work for s-off.
Sent from my "Up All Night Sleep All Day" Nexus 5!
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
chilort said:
I was trying to root my HTC One Mini and I bricked it.
I was following the tutorial on AndroidRootCentral and things were going well until I needed to install the SuperSU zip file. I couldn't find the file. My file structure as shown through TWRP was nothing like the file structure as seen though HTC Sync Manager. I tried rebooting the phone and placing the SuperSU zip in many locations. I'm not exactly sure what when wrong.
I probably screwed myself even further when I tried various things to get the phone to reset. Nothing I've read seems to work and I've been reading things and trying to get it to work since Friday. I've tried relocking the phone and then using an AT&T (my carrier) RUU. None of the RUUs I've found for AT&T work. All come back with a message about something being too long (I could look this up if you really need to know).
So ... help!
Is there a way to basically format and start over?
Click to expand...
Click to collapse
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
es0tericcha0s said:
More specifics please. What version of the firmware were you on? What RUUs have you found / tried to run? Please provide the exact error to further expedite the process. Also, if you have fastboot set up, boot to the bootloader and run:
fastboot getvar all
and post the results.
Click to expand...
Click to collapse
I'm going to bring some of this to you in pieces so I may edit this post for more info to answer your questions (I have a toddler running around and it is dinner time).
I do not know my firmware version. Under relocked my phone says:
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.29.40g.00.19
OpenDSP-v19.2.0268.0927
OS-4.13.502.3
eMMC-boot 1024MB
Jul 11 2014,20:49:19.0
I cannot hotlink but the one in this thread (http://forum.xda-developers.com/showthread.php?t=2777778) is one of the RUUs I tried. I tried others but in my haste to try to get this thing running again I didn't exactly take good records.
After running getvar all
version: 0.5
version-bootloader: 2.22.0000
version-baseband: 1.29.40g.00.19
version-cpld: None
version-microp: None
version-main: 4.13.502.3
version-misc: PVT SHIP S-ON
serialno: HT385WA00294
imei: 356482050078674
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: CWS__001
battery-status: good
battery-voltage: 4314mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-0e1af350
hbootpreupdate: 11
gencheckpt: 0
Edit:
Okay, when trying the RUUs I get Error 155: Unknown error.
My PC is a an old Core 2 Duo and crashed a few times just trying to load the RUU. The RUU then asks to go through a recovery mode. It shows a picture with four exclamation points in the corners of the screen on the phone. My phone does not have the exclamation points. I've tried the recovery process a few times and it doesn't do anything.
The error about something being too long was when I was trying to load a .zip using fastboot from my Mac.
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
es0tericcha0s said:
Seems like you're in a bit of a pickle then... There aren't any current RUUs for your phone. The one that you linked to would not be able to work unless you are S-Off because S-On will not let you downgrade. That version is 4.2.2 and it appears that you have accepted the OTA which means you will not be able to just run that RUU and get back to normal. Now, that doesn't mean there aren't any options, but probably at this point, it might be easiest just to install a custom rom since you still have TWRP. Just have to remember to pull the boot.img out of the rom zip and use fast boot to install or you will bootloop. If you really want to be back on bone stock, you would need to jump through some hoops. Basic outline is as follows:
Put rom on phone.
Boot to TWRP
Wipe and install rom
Boot to bootloader and flash boot.img
Once back up and running you'd need to S-Off (I believe Rumrunner for 4.2.2, but you'll need to double check that)
Once S-Off is achieved, then you would need to relock the bootloader and then you should be able to run the RUU and accepts the OTA(s) to get up to date and stock / non rooted
Unless this is for warranty issues, I'd just use a custom rom. I'm certain there is one that is completely stock or just stock + root if that is all you want / need.
Click to expand...
Click to collapse
Thank you for the help! I am not at all opposed to a custom rom (I thought going backward might be easier than forward). But that goes beyond what I've read so far. I know I could Google it, but would appreciate any links, pointers, or other primers.
Stock + root is what I was trying to achieve.
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
es0tericcha0s said:
Here's a version of stock rooted rom from the international version (no AT&T bloatware - yay!):
http://forum.xda-developers.com/showpost.php?p=51779967&postcount=294
You need either the odexed or deodexed version from this post since you are on hboot 2.22. Odexed is fine if you aren't planning on trying to theme anything though there really isn't that much difference between them. Odexed used to be preferred for smoothness but with phones as powerful as they are now, you would be very hard pressed to tell them apart. Basically you just need to make sure you are on the right recovery, flash the rom, then use the boot.img to flash via the bootloader and you should be good to go.
Because you do not have an SD card slot, you will need to use adb while in recovery to push the rom zip from the computer to the phone. Like so:
adb push rom.zip /sdcard/ (replace rom.zip with the name of the rom you downloaded - Hint: you can name it whateveryouwant.zip to make it easier).
If you need adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Just make sure you have the right drivers and ^ and the rom zip in that folder ^ and use the Command Prompt (make sure you change directories to the adb/fastboot folder) to enter the commands.
Click to expand...
Click to collapse
The version of TWRP on my phone is 2.6.0.0. This is not version listed in the link you posted. They list 2.7.0.5. Will this be problematic?
I went ahead and gave it a try. I loaded TWRP and went into the adb sideload feature. The screen for sideload listed the following:
Updating partition details...
E: Unable to mount '/cache'
E: Unable to mount '/cache'
Running boot script ...
Finished running boot script.
E: TWFunc::Copy_Log -- Can't open destination log
E: Unable to mount '/cache'
Starting ADB sideload feature ...
I saved the rom as rom.zip to make things easier as suggested. In my terminal window I typed the command as listed (ADP and the rom are in the same folder). In the terminal window I received:
error: closed
error: closed
You will definitely need the newer TWRP before it will work. But you don't use adb sideload. As long as the PC recognizes the phone correctly, then you just need to open the Command Prompt, change directories to the folder where adb and rom.zip are store and then copy and paste the command into it and hit enter. It should start to send. It will take awhile and there is no timer so just go grab a sandwich or drink or something and be patient.
You can use this video for reference:
https://www.youtube.com/watch?v=Hn4E3fKX7WM
It's a different device, but the same exact steps. He does state that he puts the name of the rom after /sdcard/ in the command, but it's not necessary. Won't make a difference for this.
Okay. That was somewhat helpful. I couldn't find TWRP 2.7.0.5, but I did get 2.7.1.1 and I got it loaded.
I've tried the adb command. It sits there for a long time, then the phone reboots into TWRP. I get no messages back in the terminal window and nothing is loaded into the /sdcard directory (or anywhere else as far as I can tell).
Edit: wait. Formatted it and am going to try again.
Edit 2: loading rom!!!
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
es0tericcha0s said:
Don't forget to fastboot the boot.img or it won't boot. If it is still stuck in a bootloop after the rom and boot.img are installed, then reboot to recovery and perform another factory reset. Should work. If not, then you might need the other TWRP. The link for it is right on the same post as the rom. Not sure how you missed it...
Click to expand...
Click to collapse
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
chilort said:
I missed it because I didn't read carefully and am doing this in bits and spurts.
The good news is that I have a running phone again. Thank you so much for the help!:good:
Click to expand...
Click to collapse
:good::highfive::victory:
es0tericcha0s said:
:good::highfive::victory:
Click to expand...
Click to collapse
Thank you again for walking me through this. It is nice to have my HTC back. My slow, piece of junk work phone can now go back to running BOINC.
No problem. It's how I give back to the community.
I have an AT&T HTC One M8 running KitKat, but I want to convert to stock Dev Edition and run Marshmallow, ridding of AT&T's bloatware.
I have S-Off and have unlocked my bootloader. I am trying to root at this point but am coming across technical difficulties (mentioned in post 2).
I know that I'll have to change the Developer's Edition carrier ID. My current CID is AT&T's CWS__001
Lastly, I'll have to run the Dev Edition RUU, which I don't know where to get.
As I am quite new to all of this, there are terminologies that I have an idea as to what they mean, but may not fully understand.
So as you can see, I have this general outline of what I think I may need to do. But since I actually do not know how to do them, I basically am in need of a guide. Hopefully someone can inform me if I'm missing any crucial step(s)!
I'm not sure what to do at this point, but I'm going to try to root my phone. I'll update my status on how it goes.
I cannot flash a twrp. Yes, I am on FASTBOOT USB on my M8's bootloader.
When I type in "fastboot flash recover m8recovery.img" on my Command Prompt, it says... error: cannot load 'm8recovery.img'
m8recovery.img is what I have named my...
Wait a sec... brb
Okay, so I had to type in m8recovery.img.img because I had it named with the .img
My mistake, I didn't know. However, I still have the problem of being stuck on the "Entering Recovery..." screen.
I'm gonna have to try different versions of twrp.
Edit: twrp version 3.0 and 2.8 was not working. I had to try 2.7 before it would work.
After flashing SuperSU, I've finally managed to root my device.
lxiong1 said:
When I type in "fastboot flash recover m8recovery.img" on my Command Prompt, it says... error: cannot load 'm8recovery.img'
m8recovery.img is what I have named my...
Wait a sec... brb
Okay, so I had to type in m8recovery.img.img because I had it named with the .img
My mistake, I didn't know.
Click to expand...
Click to collapse
Do yourself a huge favor , and go into Windows folder options, and disable the option to hide known file extensions (which is enabled by default).
lxiong1 said:
However, I still have the problem of being stuck on the "Entering Recovery..." screen.
I'm gonna have to try different versions of twrp.
Edit: twrp version 3.0 and 2.8 was not working. I had to try 2.7 before it would work.
After flashing SuperSU, I've finally managed to root my device.
Click to expand...
Click to collapse
The proper version TWRP depends on OS version on the phone. Since you were still back on Kitkat, it would require an older TWRP (2.7).
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
lxiong1 said:
Lastly, I'll have to run the Dev Edition RUU, which I don't know where to get.
I basically am in need of a guide.
Click to expand...
Click to collapse
Guide to convert to Dev Edition is here: http://forum.xda-developers.com/htc-one-m8/general/guide-update-to-official-developer-t3002003
Although you don't need to change the MID (as the AT&T and Dev Ed versions already have the same MID), you just need to change CID. Then run the desired Dev Ed RUU.
MM Dev Edition RUU: http://dl3.htc.com/application/RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4.exe
But it should also be noted that for the MM in particular, you will need to flash the firmware, then RUU (otherwise RUU will fail with Error 155: unknown error): http://forum.xda-developers.com/showpost.php?p=66886759&postcount=23
It should also be noted, that all the above info (guide, RUUs, etc.) can be found my Index Thread: http://forum.xda-developers.com/showthread.php?t=2751432
So in short, the next steps to convert to Dev Editions (since you already have s-off and root):
1) Change to Dev Ed CID with guide linked above
2) Flash 6.12.1540.4 firmware with fastboot
3) Run 6.12.1540.4 RUU
I managed to change my CID to BS_US002
But when I download and try to flash firmware.zip, I get: FAILED <remote: 42 custom id check fail>
Any idea what gives? I tried brushing it off and going for the RUU. But obviously after failing to flash firmware.zip, I got Error 155.
It sucks to get this far and not get Dev edition Marshmallow. Uhghh... what a drag
If I knew that I'd have to go through this ridiculousness, I wouldn't have purchased this phone.
lxiong1 said:
It sucks to get this far and not get Dev edition Marshmallow. Uhghh... what a drag
If I knew that I'd have to go through this ridiculousness, I wouldn't have purchased this phone.
Click to expand...
Click to collapse
You have to repeat the same command when you get failed. That's how you flash a firmware .
Sent from my HTC One_M8 using Tapatalk
Deleted message.
Okay, it seems that the reason why I get the "42 custom id check fail" error is because my CID is at BS_US002
The firmware.zip file that I have is for CID's that are on CWS__001 (yes, two underscores)
So a tip for those wanting to convert to (Android 6.0) Dev Edition: Flash firmware.zip first before changing your CID.
I will test this out and see if my conversion is successful. If I fail, then I'd assume it's because I need a firmware.zip... specifically for BS_US002
Hell... Flashing the firmware was a success now; but running the RUU (Dev Edition)... was not successful.
On the other hand, running the RUU (AT&T) will successfully update you to Android 6.0 Marshmallow.
So in conclusion, someone should show us where we can get a firmware.zip file that is for the Developer Edition. Because the firmware.zip from this link: http://forum.xda-developers.com/show...9&postcount=23
... is only an update for specifically the AT&T firmware, not for Developer Edition.
Right now, I am reading: http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
And it says: take note of your CID and MID and then edit the "android-info.txt" in your firmware.zip accordingly. That is helpful information and important for those who need it.
But for now, personally... the task of altering/modifying a file within a zip file and then redoing this whole process for developer edition doesn't seem worth it to me. And the reason why I say this is because AT&T's skin is not so bad on Marshmallow... Whereas on KitKat and Lollipop, it was intrusive. This is something I can live with. AT&T's skin is actually nearly non-existent if I root and remove bloatware.
lxiong1 said:
Hell... Flashing the firmware was a success now; but running the RUU (Dev Edition)... was not successful.
On the other hand, running the RUU (AT&T) will successfully update you to Android 6.0 Marshmallow.
So in conclusion, someone should show us where we can get a firmware.zip file that is for the Developer Edition. Because the firmware.zip from this link: http://forum.xda-developers.com/show...9&postcount=23
... is only an update for specifically the AT&T firmware, not for Developer Edition.
Click to expand...
Click to collapse
My apologies, you are right I linked the wrong firmware.zip (502 for AT&T, not 1540 for Dev Ed). You can find the 6.12.1540 firmware here:
http://forum.xda-developers.com/htc-one-m8/development/progress-fuu-m8-t2813792
In short, the requirement to run the firmware.zip is the same as an RUU, that it needs to match your CID and MID.