OK, I've posted some bootanimations and those don't look so great when the splash screen is the white one...
So I've pieced together a bunch of tutorials and findings and came up with way of changing it in the Desire S:
What you need:
1.) mspaint (or other bmp editor)
2.) NBIMG tool by pof (big thanks)
3.) cmd line
4.) zipping program (WinRAR etc...)
To start with, pick an image you want as a splashscreen, resize it to 480 x 800 pix. and save it as a 24bpp BMP file.
Now you need to convert it to the format HTC understands. To do that use NBIMG tool:
Code:
nbimg -F splash1.bmp -w 480 -h 800
This command is to be written in windows cmd line where splash1.bmp is the file you have created/resized in mspaint
The output file has to be renamed to splash1.nb0
Now normally you could have flashed the file as an .img file via fastboot tool, but I wasn't able to do that for some reason although my fastboot drivers are OK (the phone has rejected the flashing procedure...)
So I came up with a way that might be used even by S-ON users although I'm S-OFF so I can't try it.
OK, so to actually get the splash to the phone, you need to mask it as a critical update and flash it via recovery:
Create a android-info.txt file and put following code in it (for EU phones):
Code:
modelid: PG8810000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__J15
cidnum: HTC__016
cidnum: HTC__032
mainver: 1.28.401.1
hbootpreupdate:13
DelCache:1
DelDevlog:1
Or take the file from your corresponding RUU file from THIS COLLECTION !
This file will tell your phone that it is a critical update
Now take these two files and zip them in one PG88IMG.zip file.
Now go to recovery where you will be prompted to install the update.
You can download my SplashScreen corresponding with my QuietlyRooted bootanimation HERE
Big thanks also goes to TheGrammarFreak whom I partially ripped off
If you like it, click the THANKS button!
awesome dude works like a charm thanks
Are you S-OFF or S-ON?
He is obviously S-Off, S-On is nit rooted yet. I am S-On.
Sent from my HTC Desire S using XDA App
Obviously you don't know what you're talking about Installing the PG88IMG.zip does not require you to be S-OFF, that's how software updates are installed....I think
Ya, i feel stupid! I.read your post after writing the comment. Sorry. Well, thanks for the guide. And also, Do you think Desire S (S-On) will ever be rooted? If not then i am planning to sell my 2 Days used DS
Sent from my HTC Desire S using XDA App
khnfrhn said:
Ya, i feel stupid! I.read your post after writing the comment. Sorry. Well, thanks for the guide. And also, Do you think Desire S (S-On) will ever be rooted? If not then i am planning to sell my 2 Days used DS
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
It can already be rooted but only using XTC Clip...
Great! How much is XTC Clip in the market? On the website it shows quite expensive! :O
Sent from my HTC Desire S using XDA App
I'm not sure if you understand It's a piece of hardware, not an app and it's around £100...
Lol. I completly understand it, by Market i meant your local market
Sent from my HTC Desire S using XDA App
thanks you very much !
I was just curious, do you think this tool might work?
http://forum.xda-developers.com/showthread.php?t=794638
This ones pretty cool:
http://postimage.org/image/cofmd37o/
or this:
http://imageshack.us/f/821/splash1w.png/
Those are great! Just a quick note - that utility will work with the ENG S-OFF and if you have fastboot drivers... In the time I posted this, there was no ENG S-OFF, so I've devised a method to change it without that
Cheers!
Cool
Thanx
MarylandCookie said:
I was just curious, do you think this tool might work?
http://forum.xda-developers.com/showthread.php?t=794638
Click to expand...
Click to collapse
Yes, I can confirm this one does work with Android Flasher 1.8.0. Upgraded from the Desire to Desire S a week ago and thought I'd give it a shot.
Had to boot into bootloader (not fastboot) and accept the update manually on the handset after user using Android Flasher to choose the splash screen.
I know its easy enough to change boot animations but can we change the downanimations I really want to remove the operator boot and shutdown screens with oem HTC
Sent from my HTC Desire S using XDA App
craig1965 said:
I know its easy enough to change boot animations but can we change the downanimations I really want to remove the operator boot and shutdown screens with oem HTC
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
You can change the downanimation as easy as the bootanimation. For example in Virtuous Unity rom you can find it in /system/customize/resources called downanimation.zip(in this rom the bootanimation.zip is here also). Just replace it with an other animation and you're done. You have to have root to do this........
ffodi said:
You can change the downanimation as easy as the bootanimation. For example in Virtuous Unity rom you can find it in /system/customize/resources called downanimation.zip(in this rom the bootanimation.zip is here also). Just replace it with an other animation and you're done. You have to have root to do this........
Click to expand...
Click to collapse
Thank you I'm rooted and s off I did try this earlier I read you have to change permission to r-r-rw I did this removed the originals but all I got was a blank screen on shutdown and operator followed by android on boot
Sent from my HTC Desire S using XDA App
craig1965 said:
Thank you I'm rooted and s off I did try this earlier I read you have to change permission to r-r-rw I did this removed the originals but all I got was a blank screen on shutdown and operator followed by android on boot
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
I simply replaced downanimation.zip with ES explorer(with allowed root options). First time I had black screen too, but I've found out that the files must have the same name in the zip file as the originals. For example in unity rom with orkorolevs blue theme the file names must be like this: power_down_60_XX.png (XX are numbers from 01 to '"how many files you have").
Related
I'm wondering if this may work...
Please don't follow anything that I posted here, I'm just asking and would like to know if this is possible.
Read on and tell me what you think
Isn't the problem of installing OTA updates is the Recovery used by ClockWork mod? Why not just flash in the stock recovery instead of ClockWork mod?
I don't know if that is possible, but I'll just say what I see and tell me if I'm wrong
The PG58IMG.zip used for flashing ClockWork mod, contained an image called "recovery.img" which is basically available for those CIDs
Code:
HTC__001
HTC__E11
HTC__032
HTC__102
HTC__Y13
HTC__203
HTC__405
HTC__N34
HTC__304
HTC__A07
HTC__016
HTC__J15
So, my CID is HTC__J15, can't I use the "recovery_signed.img" in the "rom.zip" of the RUU to flash my old recovery? I can't see why it may not be possilble of creating a "PG58IMG.zip" and write in an andoid-info.txt with this:
Code:
modelid: PG5813000
cidnum: HTC__J15
mainver: 1.34.415.1
hbootpreupdate:0
DelCache:1
or just flashing using ADB the recovery_signed.img and we're done?
What you think?
Please gently tell me if I'm wrong, I'm just willing to learn and know more about this
Thank you
You can flash any recovery through ADB using
fastboot flash recovery recovery.img
where the file 'recovery.img' is the recovery file of your choice, which can be stock recovery, too.
You can get the update.zip from the OTA and use the option 'install update.zip' from custom recovery, I've never used this on the Sensation, but thats what we used to do back on the Desire HD forums.
prank1 said:
You can flash any recovery through ADB using
fastboot flash recovery recovery.img
where the file 'recovery.img' is the recovery file of your choice, which can be stock recovery, too.
You can get the update.zip from the OTA and use the option 'install update.zip' from custom recovery, I've never used this on the Sensation, but thats what we used to do back on the Desire HD forums.
Click to expand...
Click to collapse
Hmm....do you know if anybody has tried that yet. I'm trying to install the update and would have to flash a stock RUU to update. If this works, it would be so much easier.
claudenegm said:
I'm wondering if this may work...
Please don't follow anything that I posted here, I'm just asking and would like to know if this is possible.
Read on and tell me what you think
Isn't the problem of installing OTA updates is the Recovery used by Clockworld mod? Why not just flash in the stock recovery instead of clockword mod?
I don't know if that is possible, but I'll just say what I see and tell me if I'm wrong
The PG58IMG.zip used for flashing Clockworld mod, contained an image called "recovery.img" which is basically available for those CIDs
Code:
HTC__001
HTC__E11
HTC__032
HTC__102
HTC__Y13
HTC__203
HTC__405
HTC__N34
HTC__304
HTC__A07
HTC__016
HTC__J15
So, my CID is HTC__J15, can't I use the "recovery_signed.img" in the "rom.zip" of the RUU to flash my old recovery? I can't see why it may not be possilble of creating a "PG58IMG.zip" and write in an andoid-info.txt with this:
Code:
modelid: PG5813000
cidnum: HTC__J15
mainver: 1.34.415.1
hbootpreupdate:0
DelCache:1
or just flashing using ADB the recovery_signed.img and we're done?
What you think?
Please gently tell me if I'm wrong, I'm just willing to learn and know more about this
Thank you
Click to expand...
Click to collapse
Yes you can, absolutely. This is exactly what I did to get the OTA to work. I had CWM flashed so I created a PG58IMG.zip with the stock recovery image which i got from rom.zip. I then placed it on my SD card and booted in to the bootloader. Once stock recovery was back, the OTA update to 2.3.4 worked.
f3nd3r said:
Yes you can, absolutely. This is exactly what I did to get the OTA to work. I had CWM flashed so I created a PG58IMG.zip with the stock recovery image which i got from rom.zip. I then placed it on my SD card and booted in to the bootloader. Once stock recovery was back, the OTA update to 2.3.4 worked.
Click to expand...
Click to collapse
I flashed Stock Recovery and Clockworld Mod using ADB.
Everything worked like a charm!
Thank You!!
claudenegm said:
I flashed Stock Recovery and Clockworld Mod using ADB.
Everything worked like a charm!
Thank You!!
Click to expand...
Click to collapse
No problem!
shorty87 said:
Hmm....do you know if anybody has tried that yet. I'm trying to install the update and would have to flash a stock RUU to update. If this works, it would be so much easier.
Click to expand...
Click to collapse
I wrote this easy step-by-step tutorial, hope it helps
http://forum.xda-developers.com/showthread.php?t=1228648
Added prank1 and f3nd3r in the credits on my post, thanks guys
Sent from my HTC Sensation Z710e using XDA App
##NOTICE - Please Make sure you are downloading correct one for your ROM and Read this post!##
Thanks goes to Mike for his firmware files, Revolutionary for patching the file, and all devs who keep giving us a reason to flash.
Also Thanks goes to hoosbude who hosted my firmware files when I needed a place to keep them up for everyone
PLEASE realize that this has the same warnings as all firmware. It can brick your device so please know how to flash it before you do so. I am not responsible if you misflash and brick your device.
This thread is beginner friendly so by all means ask and I will respond when I can or I am sure others are willing to help as well.
Firmwares that I have posted:
3.33 Universal is the latest/stable release ICS 4.0.3 FW for Sensation (sense 3.6 Version and works for Sense 4 also)
3.32 Universal is ICS 4.0.3 FW for Sensation (sense 3.6 Version) that has the Unlocked bootloader (posted by Mike1986)
3.30 Universal is ICS 4.0.3 FW for Sensation (sense 3.6 Version) that has the Unlocked bootloader (posted by Mike1986)
3.24 Universal is ICS 4.0.3 FW for Sensation (sense 3.6 Version) that has the Unlocked bootloader (posted by Mike1986)
3.12 Universal is ICS 4.0.3 FW before that (Sense 3.5 Version)
1.17 Universal This is the original Revolutionary 1.17.1111 Firmware with a completed Gingerbread Firmware v 1.45 package (Radio 10.14.9035.01_M)
######################################################
What is all this?
What I have here is a series of flashable updates of a complete GingerBread package and the latest ICS Firmware [Firmware from 1.17 - 3.33]
This is for those who don't know or have bad luck editing the android-info.txt file. Some people don't want to superCID or don't know how to use fastboot or adb. This makes you able to update without having to superCID or have to go to a PC.
So what is universal about it?
I have added a method found by mf2112 that allows the android-info file to have a wildcard tag. So instead of having a T-Mobile file where the android-info file has every cidnum the identifier is one entry into the android-info file and it covers every possible CID that T-Mobile has.
######################################################
"I really want to use the latest ICS! How do I go about doing this?
I get this PM'd to me a lot. The best way I have seen to do it is as shown
0. Make sure you are S-OFF (These won't work if you aren't)
1. Download PG58IMG.zip for the version you want
2. Copy/paste PG58IMG.zip to the root of your microSD
3. Make sure MD5 match!!!
4. Reboot into bootloader (While phone it completely off hold down Vol - and Power. Keep pressing until in bootloader. In Ext4, if in android, choose Power Menu - Bootloader)
5. Once in the Bootloader choose Bootloader and then microSD will be scanned and will ask you if you want to update, press +vol for YES
6. Follow onscreen instructions.
7. Now just pull sd card out (when process is finished) if you don't have microSD reader or delete PG58xxxx if you do. PG58 will prevent you from going into recovery if phone sees it.
7.5 If you don't have a SDCard Reader - Pop the SDCard out. Boot into the bootloader, go down to recovery, pop the SD-Card in then choose recovery.
8. If you do have a SDCard Reader -> Reboot into bootloader and go to recovery after deleting PG58IMG.zip file and putting the SDCard back in the phone
9. Reboot or flash new rom
10. You are done. Enjoy the ROM
My ROM doesn't boot. HELP!
Boot into recovery and clear dalvik and cache. 99% of the time this will fix that issue.
######################################################
How can I tell if the firmware flashed successfully???
In the bootloader up at the very top it will say the firmware version you just installed.
Ex: -Firmware-3.33- or -Firmware-1.17-
How to check your current Firmware Version for those who flashed before the most recent update:
fastboot getvar version-main
How to check your CID & MID:
You can do this one of the following ways.
1. fastboot load into the bootloader and do:
fastboot getvar cid
fastboot getvar mid
If you don't have fastboot I have provided a download of it at the bottom of this post. Read the Read-Me file inside of it.
2. For those without fastboot you can use an app called CID Getter. CID is displayed at the top. MID is at the line ro.mid
This will not tell if you are SuperCID or not it just tells your original CID.
3. If you want to do it by terminal, open a terminal on the phone and do:
su
getprop ro.cid
getprop ro.mid
If it gives you the result of CID: 11111111 and MID PG58******
You are superCID. Use any file you like it doesn't matter they all work for you.
######################################################
What is in the Universal Firmware File android-info.txt?
modelid: PG5813000
modelid: PG5813001
modelid: PG5810000
modelid: PG5811000
cidnum: H3G__***
cidnum: HTCCN***
cidnum: HTC__***
cidnum: HTC*****
cidnum: VODAP***
cidnum: T-MOB***
cidnum: ORANG***
cidnum: O2___***
cidnum: ********
######################################################
Can I edit the firmware files and change them to my liking?
Ofcourse! And let me teach you how below ^_^
How to edit the android-info.txt File via Windows (Will add Linux later. Sorry I don't own a MAC so I can't tell how to use that)
1. Go download Notepad++ and install it [It is free and is a great editer and makes it easier]
2. Download your PG58IMG.zip file you want to edit or one from a post by a DEV.
3. Double click file and open using Windows Archive Manager (Windows built in ZIP program)
4. Right click android-info.txt and copy it. Paste outside of the zip file
5. Right click android-info.txt you just pasted and open in notepad++
6. Add your cidnum that you want to the file or modelid. Use the ones already in there as an example.
7. Make sure there are no spaces after your cidnum or modelid (So it shouldn't be "cidnum: T-MOB010_" _ = space)
8. Save it
9. Double click the PG58IMG.zip again. Click android-info.txt and delete it in the archive (Don't extract the archive)
10. Drag and drop the new android-info.txt over PG58IMG.zip
11. Flash your newly packaged edited Firmware
12. Grab a drink and celebrate. You just created a custom firmware package.
[Here is a video tutorial how! http://youtu.be/fW5jSiqDRLg (Thanks to Iocn)]
Beginner Friendly Firmware Downloads:
Firmware 3.33 Universal:
DOWNLOAD:http://d-h.st/SuC
MD5: 07cc2a2ea4473e8fe8d6fe844c4020a1
Firmware 3.32 Universal (Non-TMOUS):
DOWNLOAD: http://d-h.st/OCH
MD5: 861dd138f68523a6cc56db7a0320ee0f
Firmware 3.30 Universal:
DOWNLOAD: http://d-h.st/jqh
MD5: f818413b0a4284c41308dd52b82efe33
Firmware 3.24 Universal:
DOWNLOAD: http://d-h.st/F2k
MD5: be7c5075f966d386c87f7ea8103f7445
Firmware 3.12 Universal:
DOWNLOAD: http://d-h.st/iMn
MD5: 4bf63f041560702828dede9fa1d6c328
Firmware 1.17 Universal
DOWNLOAD: http://d-h.st/Kbp
MD5: 84c684219911858e4480856be5a2be0f
====================================================================================
HBoot 1.29.0000 Patch (Go from Hboot 1.27.1100 to 1.29.0000)
Download: http://d-h.st/ETo
MD5: f47d270e24cdca66a14278ed6d3e0a38
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
Download: http://d-h.st/gz1
MD5: 83606014bde64fd5b3076bd1aa1cf3fc
====================================================================================
Backup Links (Thanks to Emanon!!!!)
Firmware 3.12 unlocked hboot http://www.mediafire.com/?2ztahkck2lr74h0
Firmware 3.24 unlocked hboot http://www.mediafire.com/download.php?889vi1ej4op00vw
Firmware 3.30 unlocked hboot http://www.mediafire.com/download.php?np485s36z2s7akn
Firmware 3.32 unlocked hboot http://www.mediafire.com/download.php?mrynwif8cznhhvx
Firmware 3.32 TMOUS unlocked hboot http://www.mediafire.com/download.php?wbq2cg6ce2v2r8y
Firmware 3.33 Universal unlocked hboot http://www.mediafire.com/download.php?jxmi7jpiqbshgj1
Link for DropBox folder
https://www.dropbox.com/sh/rgtw3gumdbmvlol/7wugYfXmjF
Update Log:
[1/17/13] Changed HBoot via Hex Editor to report what Firmware Version you installed in the bootloader (ex -Firmware-3.33-)
[7/23/12] Added Full upgrade 3.33 Package.
[7/10/12] Fixed 3.33 to no longer have a HBOOT File and also combined "Others 1 & 2" into firmware package to make a full Universal package
[7/6/12] Added 3.33 Universal
[6/15/12] Updated 90% of packages to Universal Firmware. Switched hosting to Dev-Host.
[5/31/12] Added Universal FW link for v3.32 here for testing http://forum.xda-developers.com/showpost.php?p=26815412&postcount=1194
[5/17/12] Added TMO 3.32.531.14 710RD to post 2, Updated post 1 instructions (more specific)
[3/30/12] Built a complete GingerBread package after pulling revolutionary HBOOT. Uploaded files for users
**Removed older update info**
Kohr-Ah, it's about time you post this...good work.
Thank you
Ok I used cid finder says cid 111111 that's what I set it too when I rooted what file do I need
Sent from my HTC Sensation 4G using xda premium
Does this have new Ril in it and radio
Sent from my HTC Sensation 4G using xda premium
craven667 said:
Ok I used cid finder says cid 111111 that's what I set it too when I rooted what file do I need
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
That means you are superCID. Any file will work for you
craven667 said:
Oh this has new Ril in it and radio
Sent from my HTC Sensation 4G using xda premium
Click to expand...
Click to collapse
Correct.
This is this firmware
http://forum.xda-developers.com/showthread.php?t=1412618
made friendlier to beginners who don't know how to or don't want to superCID.
Thank you for creating this thread! While I already have the latest firmware loaded, the amount of time I spent reading through page after page of comments just to make sure I was doing it correctly was a bit much.
Again, thanks for contributing.
Sent from my HTC Sensation Z710e using Tapatalk
no image...
I have cidnum: VODAP110 but with the file for VODAPHONE I get the message: no image or wrong image...
Thanks dude. Is 3.24 firmwares are unlocked or locked?
Sorry for bad english
gokberks said:
Thanks dude. Is 3.24 firmwares are unlocked or locked?
Sorry for bad english
Click to expand...
Click to collapse
They are all locked
Same as Mike's firmware. As the only commands you lose are fastboot flash.
Sent from my Sensation in Ur-Quan subspace
hungi said:
I have cidnum: VODAP110 but with the file for VODAPHONE I get the message: no image or wrong image...
Click to expand...
Click to collapse
For all images when it scans them in the vodaphobe file or just one? (Also 3.12 or 3.24?)
Sent from my Sensation in Ur-Quan subspace
1 question
if i update the firmware...i'll be able to turn back to the original rom???? if yest what the steps? sorry for my english
I have a newzeland telecom sensation and it is not listed and I have been very un lucky editing the info, I can't save the changes to the file...
My Cid: TELNZ001
MODID: PG5811000
can you please add this to the file for me !
Thanks for this file they are making life easear for everyone!
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Panchulo77 said:
I have a newzeland telecom sensation and it is not listed and I have been very un lucky editing the info, I can't save the changes to the file...
My Cid: TELNZ001
MODID: PG5811000
can you please add this to the file for me !
Thanks for this file they are making life easear for everyone!
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
Will add and upload when i get to a PC figure about two hours from this post.
I will add it to the OTHERS firmware
Sent from my Sensation in Ur-Quan subspace
After reading the PG58IMG.zip, there's no yes / no question for installing, only the normal hboot menu...
Current version: 1.23 S-ON // CID: HTC__102
What's wrong?
ToM
Nightwing0815 said:
After reading the PG58IMG.zip, there's no yes / no question for installing, only the normal hboot menu...
Current version: 1.23 S-ON // CID: HTC__102
What's wrong?
ToM
Click to expand...
Click to collapse
When you flashed firmware it asked you to push vol up for yes and volume down for no didn't it before it began?
Sent from my Sensation in Ur-Quan subspace
Kohr-Ah said:
When you flashed firmware it asked you to push vol up for yes and volume down for no didn't it before it began?
Click to expand...
Click to collapse
It don't ask... It reads the content of the package and then it will switch without asking to a normal hboot menu. After that, i'm hboot 1.23, like before...
ToM
Can the firmware be edited to leave out certain elements?
It seems that the 3.24 firmware includes a screen update that makes AOU screens have a much colder/blue tint look.
Could that element of the firmware be hacked out?
I wouldn't even personally think to try such a thing. But if someone who knows how to code could yank that part of the update out it would be awesome.
hi all....i recently bought a t mobile htc one s and i am planning on debranding it....i dont live in the US and i dont need any of t mobiles services....my plan is to debrand it and get stock htc rom on it...i dont plan on using the phone rooted, so i want to be able to get OTA updates and everything, basically i want it to be like stock european htc one s....i google and found this link http://forum.xda-developers.com/showthread.php?t=1674202
after i rooted my phone i followed the steps in the link and was able to change my cid to HTC__001 from T-MOB010. i downloaded the european 2.31 RUU from http://www.filecrop.com/Ruu-HTC-One-S.html and when i ran it i got error code 130....my model id (PJ4011000) is different from the one the RUU is meant for (PJ4010000). so i was unable to debrand. i googled on how to change the modelid and read somehwere that i had to modify my build.prop file....followed the steps in this link http://forum.xda-developers.com/showthread.php?t=1236732 and changed the model id to PJ4010000 from PJ4011000 wherever it appeared in the build.prop file and pushed it back onto the phone, but still the ruu is giving the same error code 130.
i couldnt find any more links to help so i am posting it here. anyone have any ideas ? thanks
p.s i installed the stock recovery and the stock boot using fastboot and relocked the boot loader before trying to install using ruu. and the 2.31 ruu is compatible with HTC__001
anand_s said:
hi all....i recently bought a t mobile htc one s and i am planning on debranding it....i dont live in the US and i dont need any of t mobiles services....my plan is to debrand it and get stock htc rom on it...i dont plan on using the phone rooted, so i want to be able to get OTA updates and everything, basically i want it to be like stock european htc one s....i google and found this link http://forum.xda-developers.com/showthread.php?t=1674202
after i rooted my phone i followed the steps in the link and was able to change my cid to HTC__001 from T-MOB010. i downloaded the european 2.31 RUU from http://www.filecrop.com/Ruu-HTC-One-S.html and when i ran it i got error code 130....my model id (PJ4011000) is different from the one the RUU is meant for (PJ4010000). so i was unable to debrand. i googled on how to change the modelid and read somehwere that i had to modify my build.prop file....followed the steps in this link http://forum.xda-developers.com/showthread.php?t=1236732 and changed the model id to PJ4010000 from PJ4011000 wherever it appeared in the build.prop file and pushed it back onto the phone, but still the ruu is giving the same error code 130.
i couldnt find any more links to help so i am posting it here. anyone have any ideas ? thanks
p.s i installed the stock recovery and the stock boot using fastboot and relocked the boot loader before trying to install using ruu. and the 2.31 ruu is compatible with HTC__001
Click to expand...
Click to collapse
Try it without installing the recovery and boot before the RUU. There is no need to do that. Just relock and run the RUU, it will restore the boot and recovery for you.
Sent from my HTC One S using xda app-developers app
Lemme know how it goes. Might do this as well
Sent from my HTC VLE_U using xda app-developers app
Same here. I am trying to debrand the T-Mobile US as well. Thanks.
Sent from my HTC VLE_U using xda app-developers app
troby86 said:
Try it without installing the recovery and boot before the RUU. There is no need to do that. Just relock and run the RUU, it will restore the boot and recovery for you.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
hmmm......i thought the model id is stored in the build.prop file, dont know how this can fix that....i heard the ruu checks for cid and the modelid...i am passing the cid check, its the model id where i get stuck....anyways will try it out and let you guys know....its my only phone currently so might be a few days
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Is debranding needed in order to flash custom ROM ?
No. You just need to root the phone to install custom rom.
Sent from my HTC VLE_U using xda app-developers app
Confused
roadhero said:
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Click to expand...
Click to collapse
I am a bit confused with the above update and the thread here . The OP in the thread claims that he was able to de-brand his TMOUS HOS without SuperCID of 11111111.
Can somebody please clear the confusion?
Also, after de-branding, does the WiFi work on HOS which was previously TMOUS branded?
roadhero said:
Guys, I have debranded my T-Mobile One S just a couple weeks ago. Unless you have a Super-CID and locked (relocked) bootloader, you won't be able to install a European RUU on T-Mobile One S. On the other hand, MID is stored not only in build.prop file but in areas inaccessible unless you are S-OFF, so you can flash European RUU but you still won't be able to OTA and will have to wait for the new update RUU when (if ever, you know what I'm talking about) it comes out.
You can find how to Super-CID in this post.
Click to expand...
Click to collapse
hmmm....i wasnt able to flash the european RUU...as mentioned it gave me an error (code 130, model id not matching or something)....so forget OTA updates, even flashing the RUU was impossible with my current model id....i did consider going the super cid route but i heard that the jelly bean OTA update bricks phones with super cid...thats why i wanna get a more 'legitimate' cid like HTC__001....
chota_shivaji said:
I am a bit confused with the above update and the thread here . The OP in the thread claims that he was able to de-brand his TMOUS HOS without SuperCID of 11111111.
Can somebody please clear the confusion?
Also, after de-branding, does the WiFi work on HOS which was previously TMOUS branded?
Click to expand...
Click to collapse
yeah the OP in that thread was able to debrand....and i think he used the HTC__001 cid ...dont know what the model number of his phone is....i think it might be matching with the one in the european RUU (PJ4010000)....does anyone know of any unbranded RUU that supports the model id PJ4011000 ??
I was able to flash my htc one s T-Mobile us with RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655 using superCID 11111111 it work perfectly however it is impossible to install the OTA update JB_45_S_HTC_Europe_3.16.401.8.
yw2012 said:
No. You just need to root the phone to install custom rom.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
yw2012 thanks for your answer.
I suppose that no problem exists with this phone, a custom ROM could be flashed :
HTC One S
T-MOB101
HBOOT-1.14.0002
RADIO-1.09es.50.02.07_2
Android version : 4.0.4
HTC Sense version : 4.1
Software number : 2.38.111.10
Baseband version : 1.09es.50.02.07_2_10.09d.50.04L
Build number : 2.38.111.10 CL97613 release-keys
Bootloader unlocked
Rooted with SuperSU
ROM Stock
Well, I'd like to confirm that there's no way to flash a European RUU on USA T-Mobile device unless you Super-CID. There are also European T-Mobile branded phones, e.g. T-Mobile Germany. Those ones can be debranded using generic HTC__001 CID.
Small statistic report from fellow community (Not my own work):
1. HTC One S (Z520e) 1&1 Germany : CID: HTC__102 GER -> CID changed to 11111111 Super CID -> OTA --> OK!
2. HTC One S (Z520e) T-Mobile Germany : CID: T-MOB101 - TMD -> CID changed to HTC__102 GER -> OTA --> OK!
Few things you need to obey strictly when OTA to be safe, based on current brick reports:
1. Locked/relocked bootloader
2. Everything stock, no root, no custom recovery:
Code:
Radio: 1.06es.50.02.31_10.09a.50.04L
HBOOT: 1.14.0002
Recovery: Stock
ROM: Stock 2.31.401.5
3. CIDs:
Code:
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
4. FULLY CHARGED, CHARGING/SYNC CABLE DETACHED, leave the phone alone and let it apply the OTA update
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
roadhero said:
Well, I'd like to confirm that there's no way to flash a European RUU on USA T-Mobile device unless you Super-CID. There are also European T-Mobile branded phones, e.g. T-Mobile Germany. Those ones can be debranded using generic HTC__001 CID.
Small statistic report from fellow community (Not my own work):
1. HTC One S (Z520e) 1&1 Germany : CID: HTC__102 GER -> CID changed to 11111111 Super CID -> OTA --> OK!
2. HTC One S (Z520e) T-Mobile Germany : CID: T-MOB101 - TMD -> CID changed to HTC__102 GER -> OTA --> OK!
Few things you need to obey strictly when OTA to be safe, based on current brick reports:
1. Locked/relocked bootloader
2. Everything stock, no root, no custom recovery:
Code:
Radio: 1.06es.50.02.31_10.09a.50.04L
HBOOT: 1.14.0002
Recovery: Stock
ROM: Stock 2.31.401.5
3. CIDs:
Code:
cidnum: 11111111
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__304
cidnum: HTC__A07
4. FULLY CHARGED, CHARGING/SYNC CABLE DETACHED, leave the phone alone and let it apply the OTA update
Click to expand...
Click to collapse
Thanks a lot for the vital info. i never tried flashing the RUU using super cid. i will try.
some more things of concern. lets say i change my cid to super cid (11111111) and am able to flash the 2.31 european RUU
1) does wifi/cellular radio of the t mobile US one s work with the european RUU?
2) and lets say i follow all the steps you recommended before an OTA update, the jelly bean OTA update wont brick my phone? is this right ? is there anyone who has successfully updated to jelly bean while on super cid ?
yw2012 said:
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
sorry, i dont seem to get what you said. changing the cid will let you flash a different RUU but as people mentioned in this thread, you cant install an european RUU with generic cid like HTC__001 on a Tmobile US phone (cause of differing model id i presume). you can however install using super cid (i havent verified this myself and ofcourse i claim no responsibility ). but i dont know whether you can successfully update using OTA while on supercid
anand_s said:
Thanks a lot for the vital info. i never tried flashing the RUU using super cid. i will try.
some more things of concern. lets say i change my cid to super cid (11111111) and am able to flash the 2.31 european RUU
1) does wifi/cellular radio of the t mobile US one s work with the european RUU?
2) and lets say i follow all the steps you recommended before an OTA update, the jelly bean OTA update wont brick my phone? is this right ? is there anyone who has successfully updated to jelly bean while on super cid ?
sorry, i dont seem to get what you said. changing the cid will let you flash a different RUU but as people mentioned in this thread, you cant install an european RUU with generic cid like HTC__001 on a Tmobile US phone (cause of differing model id i presume). you can however install using super cid (i havent verified this myself and ofcourse i claim no responsibility ). but i dont know whether you can successfully update using OTA while on supercid
Click to expand...
Click to collapse
- I got the rom.zip from the RUU.exe.
- This .zip has a file called android-info.txt which mentions the "modelid: PJ4011000".
- I wonder if somehow you are able to edit this .zip and change modelid to match the current in phone, you might be able to do OTA update on HTC__001 unbranded phone from TMOUS.
As usual this is just a speculation with no real data to back it up. So use it on your own risk. I am not responsible to any damage this does to your phone :fingers-crossed:
yw2012 said:
So if I get it correctly, I can change my T-Mobile US HTC one s to cid HTC__001 and I can debrand it and still have OTA?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
No, you won't even be able to run a European RUU in this case.
anand_s,
to answer your questions,
1) wifi/cellular radio works like a charm with the european RUU.
2) you will receive a request to receive a European JB OTA, it will even download but it will give you a message that you have different software on the phone and it won't install, so everything's fine with that, you'll just have to run a European JB RUU if it becomes available.
And yes, you are right regarding everything else. There's OTA on SuperCID, but MIDs mismatch and it does not install, it does not break your phone either.
I personally have US T-mobile One S S4, have unlocked bootloader, SuperCID and running a european RUU 2.31.
starting Jan26 unlocking phones will be ilegal in US
for all you people from US, if you want to unlock and debrand your phone I strongly suggest doing it today; tomorrow it will be a crime
http://www.techspot.com/news/51439-...ne-will-become-a-crime-starting-saturday.html
wtf is that? you really have lots of control freak people walking freely on the streets, and even worse, they're writing laws . . .
chota_shivaji said:
- I got the rom.zip from the RUU.exe.
- This .zip has a file called android-info.txt which mentions the "modelid: PJ4011000".
- I wonder if somehow you are able to edit this .zip and change modelid to match the current in phone, you might be able to do OTA update on HTC__001 unbranded phone from TMOUS.
As usual this is just a speculation with no real data to back it up. So use it on your own risk. I am not responsible to any damage this does to your phone :fingers-crossed:
Click to expand...
Click to collapse
This does not work, unfortunately. I tried it (the RUU extracts everything well before actually flashing, so at the last 'Next' dialog, I unzipped rom.zip in the temp folder, changed the MID in android_info.txt from PJ4010000 to PJ4011000, saved, and zipped it again), but no luck. This time, the RUU process fails with Error 132 (Signature error) rather than Error 130 (model ID error).
This is with changing CID from T-MOB010 to HTC__001. I'm now trying 11111111.
Edit: Changing the CID to 11111111 works, so you can flash the European 2.31 RUU for model ID PJ4010000 to the T-Mobile (US) One S with model ID PJ4011000. I didn't dare update to the Jelly Bean OTA (it showed up as available) thanks to this thread.
jenesuispasbavard said:
This does not work, unfortunately. I tried it (the RUU extracts everything well before actually flashing, so at the last 'Next' dialog, I unzipped rom.zip in the temp folder, changed the MID in android_info.txt from PJ4010000 to PJ4011000, saved, and zipped it again), but no luck. This time, the RUU process fails with Error 132 (Signature error) rather than Error 130 (model ID error).
This is with changing CID from T-MOB010 to HTC__001. I'm now trying 11111111.
Edit: Changing the CID to 11111111 works, so you can flash the European 2.31 RUU for model ID PJ4010000 to the T-Mobile (US) One S with model ID PJ4011000. I didn't dare update to the Jelly Bean OTA (it showed up as available) thanks to this thread.
Click to expand...
Click to collapse
- First of all thanks for all the updates. Moreover thanks for the brick-after-jb-update-on-super-cid thread.
- I wonder does it makes sense to de-brand TMOUS to European version at this point of time, if we are not able to do JB update.
- I think this should be attempted when the RUU for European JB is available. Not sure thought if that will help.
This mod removes the red text that shows up in HBoot (while booting).
Code:
[B][COLOR="Red"][CENTER]This build is for
development purposes only
Do not distribute outside of HTC
without HTC's written permission
Failure to comply may
lead to legal action.[/CENTER][/COLOR][/B]
Credits:
- to rollon76 for building it
- to k1n9n0th1n9 for the Otus Australia file
- to jmztaylor and Facepalm crew for getting S-Off and for his tips
- bkcokota (for his cwm recovery, a start for development)
- MikG for TWRP 2.5 recovery
- the community where it did a lot of research
Notice:
I tested this myself on a european non-lte phone and it works. But as always bricks can happen and i am not responsible if your phone is dead afterwards.
Don't do this, if you are not experienced enough! Flash it on your own risk!
This works only if you are S-OFF!
How to install:
1.) Download
- PL80IMG(remove red text)k2u.zip for device without LTE
MD5 Sum: 91DF703FFA7FC875F72C4313F8B6D301
- PL80IMG(remove red text)k2ul.zip for device with LTE (only european LTE models!!!!)
MD5 Sum: 5D38B660F9326666989F0455DCD82B43
- PL80IMG(remove_red_text)k2ul_Optus_Au.zip (only Optus_Australia LTE models!!!!)
MD5 Sum: 1D71636F9CD628E424DF1D65BE17E3C5
2.) Rename the file to PL80IMG.zip
3.) Copy it to your sdcard (external not internal)
4.) Reboot into bootloader and hit volume up when prompted
Have fun!
I'd love to do this but still confused
risk is really high or just a regular reminder ?
and with splashscreen
I found a few very nice splash screen for other htc devices (eg DHD), Does it work on One SV ?
can i use the commands to complete it ?
Code:
fastboot flash splash1 splashname.img
fastboot reboot
In this thread its not about splash screen, this is only to remove red text.
And yes, this is risky, cause you are flashing hboot.
But k2u worked for me, k2ul worked for the one who made them.
So, if you don't have a bad download (check md5) or another weird crazy thing done wrong this should be go well.
Splash screen from DHD should usually work, cause its the same screen resolution.
I put it in sdcard, reboot to bootloader and push power button but failed. Need help
External SD? Is it recognized? Phone still alive?
More information please!
Yes...
my phone's alive.
I put it in sdcard and reboot to bootloader, push power button then :
Model ID incorrect
Update fail
Power to reboot
---------- Post added at 05:31 PM ---------- Previous post was at 04:50 PM ----------
old.splatterhand said:
External SD? Is it recognized? Phone still alive?
More information please!
Click to expand...
Click to collapse
Help me, plz
I hate red text
"Model ID incorrect" means that the android-info.txt doesn't fit to yours.
Code:
modelid: [B][COLOR="Red"]PL8010000[/COLOR][/B]
cidnum: HTC__001
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__016
cidnum: HTC__032
cidnum: HTC__A07
mainver: 2.14.401.2
btype:1
aareport:1
hbootpreupdate:11
You can change the red part to yours, but to be honest, i don't know, if the hboot fits to your device.
Be aware, that this can brick your device.
old.splatterhand said:
"Model ID incorrect" means that the android-info.txt doesn't fit to yours.
Code:
modelid: [B][COLOR="Red"]PL8010000[/COLOR][/B]
cidnum: HTC__001
cidnum: HTC__203
cidnum: HTC__Y13
cidnum: HTC__016
cidnum: HTC__032
cidnum: HTC__A07
mainver: 2.14.401.2
btype:1
aareport:1
hbootpreupdate:11
You can change the red part to yours, but to be honest, i don't know, if the hboot fits to your device.
Be aware, that this can brick your device.
Click to expand...
Click to collapse
how to know what is my model id ?
Did you get an OTA.zip from jelly bean?
The correct one for you is inside.
Or tell us, on which carrier you are/were. Australia, right?
old.splatterhand said:
Did you get an OTA.zip from jelly bean?
The correct one for you is inside.
Or tell us, on which carrier you are/were. Australia, right?
Click to expand...
Click to collapse
Yeah, Australia
My phone's K2_UL Optus AU
My OTA : http://www.androidruu.com/getdownlo...4.980.1_R2_release_308911r3s1xp7z9ibk1t4u.zip
Open it and unzip the firmware.zip. Inside the firmware.zip should be your android-info.txt.
old.splatterhand said:
Open it and unzip the firmware.zip. Inside the firmware.zip should be your android-info.txt.
Click to expand...
Click to collapse
ok, when I know my model id, I have to edit the android-info.txt and then replace it into PL80IMG.zip by drag and drop, right?
or need more complex change? (ed sign PL80IMG.zip)
Nothing to sign. You can replace the android-info.txt inside the PL80IMG.zip with yours.
old.splatterhand said:
Nothing to sign. You can replace the android-info.txt inside the PL80IMG.zip with yours.
Click to expand...
Click to collapse
Done!
Thanks
So you can confirm its working for Australia k2_ul?
Do you still have the file, i would add it to the first post.
old.splatterhand said:
So you can confirm its working for Australia k2_ul?
Do you still have the file, i would add it to the first post.
Click to expand...
Click to collapse
my file
Fine, thanks. I link it to first post.
will this work for the HTC one M7?
intramorph said:
will this work for the HTC one M7?
Click to expand...
Click to collapse
Absolutely NO!
This will kill your device, if you flash it.
O okay thanks for the warn. Lol
Sent from my HTC One using Tapatalk
Go thank @homeslice976 For helping me do the system pull for the 5.0.1 RUU. Since I don't have the device anymore it was a great help!
This will NOT work on a CDMA HTC One GSM ONLY!
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 5.0.1 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=2314582
Full Conversion 5.0.1 RUU ZIP containing System, Boot and all Firmware 5.11.1700.3 Available as pre-rooted and stock non-rooted
This will wipe EVERYTHING INCLUDING YOUR SD CARD 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 5.0.1 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: PN0710000
modelid: PN0711000
modelid: PN0712000
modelid: PN0713000
modelid: PN0714000
modelid: PN071****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: GOOGL001
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_GE-5.0.1-5.11.1700.3.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_GE-5.0.1-5.11.1700.3.zip
Code:
fastboot reboot
Download Links Can be Found on my Website: http://www.graffixnyc.com/m7.php
DO NOT MIRROR
You can also find the 5.0.1 OTA zip, firmware.zip, stock recovery and bootloader on my site as well from the same link above
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....
Graffixnyc had to run off to class, but he and I both wanted to make sure Argenist and the other guys in IRC got thanked properly.
Argenist, man this wouldn't have happened without your help. You're a hero around here to lots of people.
Thanks for trusting us not to brick your brand new phone.
To Daereys, and Originator, and everyone else involved in getting the partitions dumped
Thank you very much!
I haven't had that much fun in IRC in forever.
VERY important don't do the procedure in the OP unless you have backed up your STOCK BOOTLOADER
Here are instructions for reversing all of this
Prerequsites:
S-off
1.44 HBoot
RUU for your device
Ok I thought reversing since I had S-off would be a simple affair and maybe I took a misstep along the way but I got it done.
Here's what worked FOR ME.
1) set CID to superCID
2) install the 1.44 Hboot in RUU mode (thanks SneakyGhost) http://d-h.st/qfc
3) install the RUU for your phone/carrier
4) if RUU is unavailable for your carrier, install the 1.44 hboot, one of the stock 1.29 roms, and change CID back to your device's CID
If you changed your MID you'll need to change that back as well.
5) change CID back to your device.
This will take you back to a factory fresh install with 1.44 bootloader
RevOne still works and I retained S-off.
If someone else has an easier way that works, please let me know.
Please NOTE:
Restoring the RUU took a long time and looked like it hung up a couple of times when I ran it. Just let it run.
The following thread from Sneakyghost has everything you ever wanted to know about Hboots and then some. Please read it.
http://forum.xda-developers.com/showthread.php?t=2316726
Wow...this is awesome. So technically we can turn our phones into a full GE phone?
Sent from my HTC One using xda premium
so thats it these 2 commands and the rom will make the phone full GE edition?!?!?
Thank you to Graffixnyc, Argenist, and Gunnyman
verboten said:
Thank you to Graffixnyc, Argenist, and Gunnyman
Click to expand...
Click to collapse
Argenist and guys paypal details people will donate!! you guys are awesome
we have the dump of the entire phone.
A fully stock ROM will be here before you know it.
---------- Post added at 04:22 PM ---------- Previous post was at 04:20 PM ----------
syphern said:
so thats it these 2 commands and the rom will make the phone full GE edition?!?!?
Click to expand...
Click to collapse
well that and the fully stock unmodified dump posted elsewhere
gunnyman said:
we have the dump of the entire phone.
A fully stock ROM will be here before you know it.
Click to expand...
Click to collapse
Is radio the same as 2 24?
Sent from my HTC One using xda premium
kozmikkick said:
Is radio the same as 2 24?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I haven't looked at it, tbh
Wont we also need the untouched odexed system dump, radio and any other random partition on the phone.
nintendolinky said:
Wont we also need the untouched odexed system dump, radio and any other random partition on the phone.
Click to expand...
Click to collapse
We HAVE the whole dump
just posting the bootloader and recovery for now
kozmikkick said:
Is radio the same as 2 24?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Baseband is 4A.17.3250.14
Fully stock GE, very nice
nintendolinky said:
Wont we also need the untouched odexed system dump, radio and any other random partition on the phone.
Click to expand...
Click to collapse
It's been dumped. Several of people have it so I expect a stock convert ROM tonight.
Now if we all were to jump on the bandwagon and flashed this GE bootloader...is sense ROMs still working or will sense ROMs need to be modified?
Sent from my HTC One using xda premium
mrjaydee82 said:
Now if we all were to jump on the bandwagon and flashed this GE bootloader...is sense ROMs still working or will sense ROMs need to be modified?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
there's no reason to flash this stuff unless you want a full conversion.
I imagine with S-off you can put back your old HBOOT and be fine
So does recovery still not work.
No more red text, just the padlock like the nexus
Sent from my HTC One using Tapatalk 2
gunnyman said:
there's no reason to flash this stuff unless you want a full conversion.
I imagine with S-off you can put back your old HBOOT and be fine
Click to expand...
Click to collapse
I understand that...I was just curious if it would work or it hasn't been tested
Sent from my HTC One using xda premium
I read earlier, it was just booting from recovery back into the OS. Is this still happening as the recovery wont work.