Related
Hello,
I have a zip file which contains boot.img, hboot.nb0, radio.img, recovery.img, splash1.nb0, system.img and userdata.img.
Also there is a text file called android-info with the following content:
modelid:CLIC10000
cidnum:HTC__001
cidnum:HTC__102
cidnum:HTC__203
cidnum:HTC__E11
cidnum:HTC__016
cidnum:HTC__032
cidnum:HTC__Y13
cidnum:HTC__506
cidnum:HTC__304
cidnum:HTC__405
cidnum:HTC__N34
cidnum:11111111
mainver:1.65.405.1
Click to expand...
Click to collapse
It is a tattoo rom.
My question is, if I flash hboot.nb0 to my phone and my phone's cid is not in the above list, will it kill my phone?
Also, how do I get the cid of my tattoo knowing that I dont have root access?
Thank you
http://androidspin.com/2010/10/18/rom-leaked-for-the-t-mobile-mytouch-htc-glacier/
think we can use this to extract the wifi-calling and other goodies to our G2s?
Not until write protection is disabled...
Sent from my T-Mobile G2 using XDA App
For anyone that would like to open it up and look at what is inside the ROM, it is a RAR file. Once you have it downloaded change ZIP to RAR and open it.
The contents:
Code:
android-info.txt 73
boot.img 2,994,176
hboot_0.86.0000.nb 1,048,576
radio.img 25,427,968
rcdata.img 114
recovery.img 4,042,752
splash1.nb0 786,432
system.img 585,101,312
72,945 tp_atmel224_20aa.img 72,945
72,289 tp_atmelc12_20aa.img 72,289
userdata.img 1,232,072,704
I do not know what the userdata.img is yet, but it is big. Maybe the Apps already installed to SD? Oh, maybe user data like videos, games, music. That makes sense.
android-info.txt contains:
Code:
modelid: PD1510000
cidnum: T-MOB010
hbootpreupdate:2
mainver: 1.14.531.1
-Unconnected
Edit: maybe I should find some other place to post this data (too?)
That wifi call stuff requires more than just an app. IIRC there's a kernel module and VPN connection to deal with. Extracting these from the MyTouch rom is dubious, but not impossible. The write protection is still the limiting factor at the moment.
userdata is just your user partition.
It's an (almost) empty preformatted ext3 to dd.
You can mount-loop it as ext3 and browse through the contents.
Can anybody post a mirror? I've tried a few times to get it with no luck... :-/
Help
Bit of a noob I'm afraid and I'm getting the message;
Error[131]: Customer ID Error
when trying to install RUU_Buzz_HTC_WWE_1.37.405.1_Radio_13.53.55.24H_3.3 5.19.25_release_151892_signed
It's a rooted T-Mobile Wildfire which has been successfully rooted and I have been using a WildPuzzle rom. A few days ago I was able to apply the shipped rom RUU_Buzz_TMO_UK_1.14.110.1_Radio_13.45.55.24_3.35. 15.19_release_130442_signed. I then did a software update to take me to the following settings;
Baseband Version: 13.51.55.24H_3.35.19.01
Build Number: 1.28.1107.2
I've researched this and variuos posts say it's probably the GoldCard but surely that must be working fine as I've managed to root it ok and indeed apply the RUU_Buzz_TMO rom.
I'd be very grateful if any of you guys could point me in the right direction as I need to get to a shipped rom rather that a custom rom.
Thanks in advance.
check the goldcards associated to the sd card CIDs when you created the gold card you should have supplied the sd cards cid to receive the relevant img for your card
Hi
Thanks for your reply.
I've just tried again, re-requested a goldcard img, using a different SD Card - FAT32 formatted. Proved it works by successfully rooting phone but still getting the Error[131] when trying to run the RUU_Buzz_HTC_WWE_1.37......
Can anyone think of anything I might be missing at all please?
If rooted try rom manager to install Danne jo's RUU_Buzz_HTC_WWE_1.37.405.1 Safe version rom. He pulled it from the shipped rom version and took out the uneeded bloat and will update your ver to most current.
Wow thanks for the prompt reply and advice.
When you say it's a non-bloated rom, how far off the shipped rom is it?
As if I was to change the phone in the near future I would be a little concerned to let it go with a custom rom!
Another reason for putting on a shipped rom was to unroot it to avoid the problem of not being able to switch it on during charging.
Hi Guys,
I am badly stuck. I have rooted my HTC Wildfire out of curiosity using unrevoced. Now after the official release froyo I tried to update my phone which is now giving me this error
getprop("ro.cid")="99999999" || getprop("ro.cid")="HTC_038" E:ERROR in /sdcard/download/OTA_Buzz_Froyo_hTC_Asia_India_2.25.720.1-1.25.720.1_reslease_161546bwou4mclajggz2mu-1.zip (Status 7)
And when I try to flash the phone with RUU its gives me an error "error 131 customer id error" . I believe both the message are same.
I have followed the steps to create the Goldcard. Now I dont know what I should do with the goldcard to update my phone with the official froyo release. I dont mind loosing the root access . please advice.
Thanks you,
Shankar
what version do you have installed? i got same error with wildpuzzle installed, so i nstalled ruu(original) and then i did full ota_update like first was 1.14 then updated to 1.25 when it ota 1.37 and after that it installs froyo ota. probally you need do the same way, good luck
rolks said:
what version do you have installed? i got same error with wildpuzzle installed, so i nstalled ruu(original) and then i did full ota_update like first was 1.14 then updated to 1.25 when it ota 1.37 and after that it installs froyo ota. probally you need do the same way, good luck
Click to expand...
Click to collapse
The verion I am on right now is
Phone model: HTC Wildfire
Firmware Version : 2.1 update 1
Build number: 1.25.720.1 CL227575 release-keys
Software number : 1.25.720.1
No custom rom installed on the phone but just been rooted with unrevoked and not with "unrevoked forever"
My questions are:
1. Does rooting the phone affect the ro.cid/CID information? Is this information a hardware/firmware related info? if it is a firmware information does rooting with unrevoced affect the firmware by anychance?
2. Now that I have Goldcard , are we expecting some prompt to import the CID info to phone when it is plugging in? Or do I have perform some steps to have to import the CID? or just by inserting the goldcard and performing update would just do it's magic .
3. Also my assumpstion is that the goldcard is related to the mini SD card while the CID means that it is realted to the region to which the phone belongs to hows does Goldcard affect the process of upgrade ? Correct me if I am wrong (just started learning about android excuse my innosense)
4. Is there a way I can modify the update to skip the update ignoring the Signature verification and CID verfication. I have tested the options in the Clockworkmod bootloader options i.e. disabled signature verification- this helped me get pass the signature verification error , disable assert verification did not make any changes, Still getting the ro.cid error
I request someone to redirect me to this info or clarify ..
Thank you,
Shankar
create fail get-cid.bat copy this to android sdk>tools catalog and run if you cid is in this cidlist you have europe model
@echo off
echo Android 2.2 to 2.1 Downgrade
echo ============================
echo.
echo This script is no longer necessary as from version 2.0.
echo This script determines your cid and your software, radio and bootloader.
echo The phone must now be rebooted to perform this step.
pause
echo.
echo Rebooting to fastboot
adb reboot bootloader
echo Press enter when bootloader screen appears
pause
echo Your phone's details are as follows:
fastboot getvar cid
fastboot getvar version-main
fastboot getvar version-baseband
fastboot getvar version-bootloader
echo.
echo Enter your CID into the website generator.
echo.
echo Finished. Rebooting phone.
pause
fastboot reboot
Click to expand...
Click to collapse
cid list
modelid: PC4910000
cidnum: HTC__032
cidnum: HTC__102
cidnum: HTC__203
cidnum: HTC__304
cidnum: HTC__A07
cidnum: HTC__E11
cidnum: HTC__K18
cidnum: HTC__N34
cidnum: HTC__Y13
cidnum: VIRGI001
cidnum: HTC__001
cidnum: HTC__405
cidnum: HTC__016
mainver: 1.21.405.2
hbootpreupdate:2
DelCache: 1
DelUserData: 0
Click to expand...
Click to collapse
rolks said:
create fail get-cid.bat copy this to android sdk>tools catalog and run if you cid is in this cidlist you have europe model
cid list
Click to expand...
Click to collapse
first I want thank for the reply. I am not sure whether I am doing this right. I have created the .bat file in the AndroidSDK\tools on my PC and executed. The output is as follows
FIRST TRY: C:\androidSDK\tools>get-cid.bat
offecho Android 2.2 to 2.1 Downgradeecho ============================echo.echo T
his script is no longer necessary as from version 2.0.echo This script determine
s your cid and your software, radio and bootloader.echo The phone must now be re
booted to perform this step.pauseecho.echo Rebooting to fastbootadb reboot bootl
oaderecho Press enter when bootloader screen appearspauseecho Your phone's detai
ls are as follows:fastboot getvar cidfastboot getvar version-mainfastboot getvar
version-basebandfastboot getvar version-bootloaderecho.echo Enter your CID into
the website generator.echo.echo Finished. Rebooting phone.pausefastboot reboot
Nothing happened on the phone though
SECOND TRY:
C:\androidSDK\tools>adb shell
$ get-cid.bat
get-cid.bat
get-cid.bat: permission denied
$ su
su
Permission denied
am I doing something wrong? If you want to know where I bought this phone then , I am in India and bought this in India.
emacine said:
first I want thank for the reply. I am not sure whether I am doing this right. I have created the .bat file in the AndroidSDK\tools on my PC and executed. The output is as follows
FIRST TRY: C:\androidSDK\tools>get-cid.bat
offecho Android 2.2 to 2.1 Downgradeecho ============================echo.echo T
his script is no longer necessary as from version 2.0.echo This script determine
s your cid and your software, radio and bootloader.echo The phone must now be re
booted to perform this step.pauseecho.echo Rebooting to fastbootadb reboot bootl
oaderecho Press enter when bootloader screen appearspauseecho Your phone's detai
ls are as follows:fastboot getvar cidfastboot getvar version-mainfastboot getvar
version-basebandfastboot getvar version-bootloaderecho.echo Enter your CID into
the website generator.echo.echo Finished. Rebooting phone.pausefastboot reboot
Nothing happened on the phone though
SECOND TRY:
C:\androidSDK\tools>adb shell
$ get-cid.bat
get-cid.bat
get-cid.bat: permission denied
$ su
su
Permission denied
am I doing something wrong? If you want to know where I bought this phone then , I am in India and bought this in India.
Click to expand...
Click to collapse
some more info from the logs for the update that is run
$ pwd
pwd
/sdcard/clockworkmod
$ cat report.log
cat report.log
Starting recovery on Thu Dec 23 20:09:58 2010
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (240 x 320)
ClockworkMod Recovery v2.5.0.1
Fixing execute permissions for /cache
I:Set boot command "boot-recovery"
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=ECLAIR
ro.build.display.id=koush_buzz-eng 2.1-update1 ECLAIR eng.koush.20100714.210216
test-keys
ro.build.version.incremental=eng.koush.20100714.210216
ro.build.version.sdk=7
ro.build.version.codename=REL
ro.build.version.release=2.1-update1
ro.build.date=Wed Jul 14 21:03:06 PDT 2010
ro.build.date.utc=1279166586
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-OSx86.local
ro.build.tags=test-keys
ro.product.model=HTC Buzz (EU)
ro.product.brand=generic
ro.product.name=koush_buzz
ro.product.device=buzz
ro.product.board=buzz
ro.product.cpu.abi=armeabi
ro.product.manufacturer=htc
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=buzz
ro.build.description=koush_buzz-eng 2.1-update1 ECLAIR eng.koush.20100714.210216
test-keys
ro.build.fingerprint=generic/koush_buzz/buzz/buzz:2.1-update1/ECLAIR/eng.koush.2
0100714.210216:eng/test-keys
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
ro.config.sync=yes
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=HT0A5PY00027
ro.bootmode=recovery
ro.baseband=3.35.15.31
ro.carrier=HTC-India
ro.bootloader=0.80.0007
ro.hardware=buzz
ro.revision=129
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Set boot command ""
$
forgot to say you must get phone to hboot mode.
I think your gold card is made with wrong number. Try Gold card tool. The correct CID is placed in the header of the application (00********************).
If anyone has a REAL GPE or a converted GPE you will notice you can't flash any ROMS without getting errors. I investigated into this and this is what I found. The system partition is only a little over 1 gig where the sense system partition is 2.8 gb. So if you try to flash a sense rom on a GPE or a converted HTC m8. It will fail (because the partition is too big for the gpe partition). The only way to correct this is to flash a sense RUU when it's available.
I'm working on a new GPE conversion RUU that will use a bigger system partition. If this works (which I'm not sure it will) then it will be easy for people who to convert to go back..
Just figured I'd let everyone know.. This was NOT tha case with the m7!
Here is a df from a real GPE (non converted)
/system 1006.7M 778.0M 228.6M 4096
Mine after conversion:
/system 1006.7M 779.1M 227.6M 4096
Can someone do a df on a sense version?
Using adb
Type adb shell
Then df
Thanks for that info, very good to know!
Sent from my LG-V510 using Tapatalk
Wow! Glad I didn't convert yet! Here's a pic of it
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I converted not worried about it at all tho. On a side note graffix do you have the GPE hboot pulled? If so can you upload it or add it to your recovery thread, want it to edit out the red dev text lol.
djkinetic said:
I converted not worried about it at all tho. On a side note graffix do you have the GPE hboot pulled? If so can you upload it or add it to your recovery thread, want it to edit out the red dev text lol.
Click to expand...
Click to collapse
It's already there I posted it last night in the stock recovery thread.
Sent from my HTC One_M8 using Tapatalk
subscribed. :fingers-crossed: will guinea pig if safe
Can't you just flash sense (htc) hboot.img? Won't that change the partitions.
Remember on my desire I used to modify the hboot to make a bigger system partition.
No one seems to have sent you this yet so... Here is a stock Sense
/system 2641M 2062M 579M 4096
backfromthestorm said:
Can't you just flash sense (htc) hboot.img? Won't that change the partitions.
Remember on my desire I used to modify the hboot to make a bigger system partition.
Click to expand...
Click to collapse
I tried that and it didn't work. Maybe a modified hboot but not the normal one.
Sent from my HTC One_M8 using Tapatalk
Do you need a signed ruu? Or can you just have someone dump from a sense rom the same partitions changed with the conversion?
Are the bootloaders different because of this?
Sent from my HTC PG09410 using xda app-developers app
scotty1223 said:
Do you need a signed ruu? Or can you just have someone dump from a sense rom the same partitions changed with the conversion?
Are the bootloaders different because of this?
Sent from my HTC PG09410 using xda app-developers app
Click to expand...
Click to collapse
You don't need a signed one I don't think. But the issue is with the system image. RUU mode complains the image is too big. Jmz Taylor was saying that there is a size limit on the system images that be flashed in fastboot/ruu mode. So they need to be split.. And each zip run after each other in ruu mode. Maybe a signed one does deal with the system image differently (not sure)
If you do a Google search on split system image ruu, you'll see a few examples. Jmz sent me a template to use and I was able to split the system image and I flashed the first one and it flashed correctly, the 2nd part failed.. I'm going to try again though.. One more time to see if I can get it to work.
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
You don't need a signed one I don't think. But the issue is with the system image. RUU mode complains the image is too big. Jmz Taylor was saying that there is a size limit on the system images that be flashed in fastboot/ruu mode. So they need to be split.. And each zip run after each other in ruu mode. Maybe a signed one does deal with the system image differently (not sure)
If you do a Google search on split system image ruu, you'll see a few examples. Jmz sent me a template to use and I was able to split the system image and I flashed the first one and it flashed correctly, the 2nd part failed.. I'm going to try again though.. One more time to see if I can get it to work.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I really hope it works. I'm really mad at myself for doing the conversion. Are you in Colorado now?
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
You don't need a signed one I don't think. But the issue is with the system image. RUU mode complains the image is too big. Jmz Taylor was saying that there is a size limit on the system images that be flashed in fastboot/ruu mode. So they need to be split.. And each zip run after each other in ruu mode. Maybe a signed one does deal with the system image differently (not sure)
If you do a Google search on split system image ruu, you'll see a few examples. Jmz sent me a template to use and I was able to split the system image and I flashed the first one and it flashed correctly, the 2nd part failed.. I'm going to try again though.. One more time to see if I can get it to work.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
hmm that makes sense,now,lol. a couple weeks ago a set up the ruuveal tool to decrypt ruus,and when i broke down m7 rom.zip from 4.19.401.9 it gave me 5 more zip files,instead of a bunch of images.
the first contains adsp thru tz. the next 3 each contain 2 android info documents and a system image,lables system_1,system_2,system_3 inside their respective zips. the last one contains different dz_data and tp.
at first glance,the zip files all appear the same:
Code:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 4.19.401.9
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
numofsystem: 3
indexofsystem: 1
sizeofsystem: 629145600
even tho the system zips,each have a second one named android-info-1,android-info-2,android-info-3,matching the the number of the system image inside that particular zip. if thats confusing,the sustem zips each contain: androit-info.text , android-info-x.txt , and system_x.img
sorry if youre allready aware of all this,the point is that you prolly just need to get the android info documents correctly worded/formatted,and the system images all named correctly. not sure if we can manually flash the zips one at a time,or need to zip them all up together somehow with yet another text document inside my ruuveal folder,all there was were the zips,i dont recall it showing anything else in there.
if you need a i can upload this decrypted ruu somewhere for you to look at,or copy/paste the rest of the android info documents. as soon as i get my m8 set up,ill try and flash them all and see what happens. that may be a couple days,tho.
**
the other thot that i had,is it possible to simply DD system back instead of using ruu/fastboot? what about DDing back the whole phone(mmcblk0) ?
housry23 said:
I really hope it works. I'm really mad at myself for doing the conversion. Are you in Colorado now?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, sir I am
scotty1223 said:
hmm that makes sense,now,lol. a couple weeks ago a set up the ruuveal tool to decrypt ruus,and when i broke down m7 rom.zip from 4.19.401.9 it gave me 5 more zip files,instead of a bunch of images.
the first contains adsp thru tz. the next 3 each contain 2 android info documents and a system image,lables system_1,system_2,system_3 inside their respective zips. the last one contains different dz_data and tp.
at first glance,the zip files all appear the same:
Code:
modelid: PN0710000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
mainver: 4.19.401.9
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
numofsystem: 3
indexofsystem: 1
sizeofsystem: 629145600
even tho the system zips,each have a second one named android-info-1,android-info-2,android-info-3,matching the the number of the system image inside that particular zip. if thats confusing,the sustem zips each contain: androit-info.text , android-info-x.txt , and system_x.img
sorry if youre allready aware of all this,the point is that you prolly just need to get the android info documents correctly worded/formatted,and the system images all named correctly. not sure if we can manually flash the zips one at a time,or need to zip them all up together somehow with yet another text document inside my ruuveal folder,all there was were the zips,i dont recall it showing anything else in there.
if you need a i can upload this decrypted ruu somewhere for you to look at,or copy/paste the rest of the android info documents. as soon as i get my m8 set up,ill try and flash them all and see what happens. that may be a couple days,tho.
**
the other thot that i had,is it possible to simply DD system back instead of using ruu/fastboot? what about DDing back the whole phone(mmcblk0) ?
Click to expand...
Click to collapse
Yeah, I'm aware of the different info files I used a template zip that JMZ sent me.. hmm dding the whole system image might work.. I didn't think of that before..It could fail, but it might work.
@housry23 I'm uploading a system.img now from my AT&T version as well as my boot.img from it. Once it's done uploading I'll post the link and directions what I want you to try to get back into sense. If you don't mind giving it a try that is.
graffixnyc said:
Yes, sir I am
Yeah, I'm aware of the different info files I used a template zip that JMZ sent me.. hmm dding the whole system image might work.. I didn't think of that before..It could fail, but it might work.
@housry23 I'm uploading a system.img now from my AT&T version as well as my boot.img from it. Once it's done uploading I'll post the link and directions what I want you to try to get back into sense. If you don't mind giving it a try that is.
Click to expand...
Click to collapse
Let me know how it goes.
if the boot/system fail,I think it's worth a shot to dd the whole phone and see what happens.
Sent from my HTC One using Tapatalk
I'll try too...Link me as well
graffixnyc said:
Yes, sir I am
Yeah, I'm aware of the different info files I used a template zip that JMZ sent me.. hmm dding the whole system image might work.. I didn't think of that before..It could fail, but it might work.
@housry23 I'm uploading a system.img now from my AT&T version as well as my boot.img from it. Once it's done uploading I'll post the link and directions what I want you to try to get back into sense. If you don't mind giving it a try that is.
Click to expand...
Click to collapse
I don't mind at all. Just let me know.
Sent from my HTC One_M8 using Tapatalk
Ok, well I'm out at the moment (on vacation in Colorado) I'm uploading a system IMG at the house (we are out to dinner)
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
Ok, well I'm out at the moment (on vacation in Colorado) I'm uploading a system IMG at the house (we are out to dinner)
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Take your time. Enjoy your vacation man. This can wait for sure!
Sent from my HTC One_M8 using Tapatalk
This brief guide will allow you to return your M9 WWE to Stock rom and:
Bootloader LOCKED
**Software Status: Official***
OPTIONAL - S-ON
REQUIRED:
- S-OFF
- Root
- ADB/fastboot
- install HTC drivers
- Battery at least 30% ( but recommended 50-70%)
- SDcard (max 32GB)
Link to Ruu.zip (1.32.401.8) : https://drive.google.com/file/d/0B17smFr95pleMjhDVXVlTjlmX0U/view?usp=sharing - thanks @djluisbento
list of supported CID/MID
modelid: 0PJA10000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__031
cidnum: HTC__102
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
cidnum: HTC__Y13
0. RUU.zip = Full Data Wipe from your phone
1. Change your CID ( reboot to DOWNLOAD MODE) for example:
HTML:
fastboot oem writecid HTC__032
fastboot reboot
1a OPTIONAL. Change your MID ( reboot to DOWNLOAD MODE) - thanks @scotty1223
HTML:
fastboot oem writemid 0PJA10000
fastboot reboot
2. LOCKED Bootloader ( to flag LOCKED not RELOCKED) - thanks @scotty1223
HTML:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
3. Download "RUU.zip" ( 1.32.401.8) , rename to 0PJAIMG and put in SDcard
4. Reboot to download mode:
5. Press VOL UP to start flash.
6. After the end of the process, select the "power" and run devices
7. Profit
OPTIONAL: If you want your device was S-ON ( reboot to Download MODE)
HTML:
fastboot oem writesecureflag 3
***I am not responsible for any problems during process to return stock romu ***
Thanks!
Enviado desde mi HTC One M9
More RUU's can be found here >> http://www.androidruu.com/?developer=M9
And I posted my collection of AT&T and Developer Edition RUU's here >> https://www.androidfilehost.com/?w=files&flid=28823
You would of coarse have to adjust the commands to match your CID and MID requirements
The rom in OP works but it doesn't let me change brightness, enable power save/extra power save or airplane mode.
Also this keeps popping up every 30-45 seconds
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it comes from an app called Demo which you can't delete. This rom is more than likely taken out from a display unit.
clsA said:
More RUU's can be found here >> http://www.androidruu.com/?developer=M9
And I posted my collection of AT&T and Developer Edition RUU's here >> https://www.androidfilehost.com/?w=files&flid=28823
You would of coarse have to adjust the commands to match your CID and MID requirements
Click to expand...
Click to collapse
I changed the CID & MID back to what it was originally (DEV edition) but it wouldn't find the flie for some reason while in download mode, had to change the CID & MID back to the ones on the list and it did pick it up but then it gives me an error while flashing (failed: -2, 7: fail to flash via downloadzip).
haZethew0rld said:
The rom in OP works but it doesn't let me change brightness, enable power save/extra power save or airplane mode.
Also this keeps popping up every 30-45 seconds and it comes from an app called Demo which you can't delete. This rom is more than likely taken out from a display unit.
I changed the CID & MID back to what it was originally (DEV edition) but it wouldn't find the flie for some reason while in download mode, had to change the CID & MID back to the ones on the list and it did pick it up but then it gives me an error while flashing (failed: -2, 7: fail to flash via downloadzip).
Click to expand...
Click to collapse
you have to use the included htc_fastboot or
You can also use the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree
If you have problems with the normal fastboot flashing any RUU you'll have to use the htc_fastboot pulled from the RUU.EXE
you can download it here >> https://www.androidfilehost.com/?fid=96039337900114016 >> Thanks go to @Sneakyghost for sharing
With the phone in download mode
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
Click to expand...
Click to collapse
clsA said:
you have to use the included htc_fastboot or
You can also use the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree
Click to expand...
Click to collapse
It fails doing the 0PJAIMG.zip method. I noticed htc_fastboot is an exe program, I will try it on my Windows side and will report back in a few.
EDIT: just changed the CID & MID back to their original developer edition status, and it seemed to have worked
haZethew0rld said:
It fails doing the 0PJAIMG.zip method. I noticed htc_fastboot is an exe program, I will try it on my Windows side and will report back in a few.
EDIT: just changed the CID & MID back to their original developer edition status, and it seemed to have worked
Click to expand...
Click to collapse
was your ext sdcard fat32 - 16 or 32 gig ?
clsA said:
was your ext sdcard fat32 - 16 or 32 gig ?
Click to expand...
Click to collapse
It's 32gb not sure if fat or ntfs, I've only formatted it through the phone, so I'm guessing fat. Thanks anyways.
haZethew0rld said:
It's 32gb not sure if fat or ntfs, I've only formatted it through the phone, so I'm guessing fat. Thanks anyways.
Click to expand...
Click to collapse
if you formatted it with the phone it is likely exfat and it won't work. It must be fat32
clsA said:
if you formatted it with the phone it is likely exfat and it won't work. It must be fat32
Click to expand...
Click to collapse
Hmm. Anyways I'm already back on the dev edition software, so I guess it wasn't as important anyways. Thanks
Whats the difference betwen WWE and stock?
Sent from my HTC One M9 using XDA Free mobile app
This works on T-Mobile variant too. I did this a few days ago thanks to Scotty1223 & Behold_This and others in that other forum thread.
magnum15 said:
Whats the difference betwen WWE and stock?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
WWE- World Wide English ( unbranded version X.XX.401.X)
STOCK- clean,unmodified rom from HTC
So- Stock rom WWE ( x.xx.401.x) - rom unbranded /variant europen form HTC
Nice guide,sir. Just wanted to throw out here folks need to make sure the phone is charged prior to flashing an ruu via any method.
scotty1223 said:
Nice guide,sir. Just wanted to throw out here folks need to make sure the phone is charged prior to flashing an ruu via any method.
Click to expand...
Click to collapse
Thx.
Good point I add information about this in #1 post
Is it necessary to lock bootloader while flashing RUU in S-OFF devices ? I've flashed RUU many times in UNLOCKED position with M7.
Can we flash 0PJAIMG.zip from fastboot:
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip 0PJAIMG.zip
and again:
Code:
fastboot flash zip 0PJAIMG.zip
Is this RUU suitable with HTC__M27 CID devices or can we modify android-info.txt in RUU.zip to flash RUU properly?
coolberry said:
Is it necessary to lock bootloader while flashing RUU in S-OFF devices ? I've flashed RUU many times in UNLOCKED position with M7.
Click to expand...
Click to collapse
No, lock it's not necessary to flash RUU (but if you want to have your phone out of the box it as )
coolberry said:
Can we flash 0PJAIMG.zip from fastboot:
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip 0PJAIMG.zip
and again:
Code:
fastboot flash zip 0PJAIMG.zip
.
Click to expand...
Click to collapse
Of course we can flash rom.zip via fastboot but this method will not restore ***status : official*** ( I checked it several times)
coolberry said:
Is this RUU suitable with HTC__M27 CID devices or can we modify android-info.txt in RUU.zip to flash RUU properly?
Click to expand...
Click to collapse
probably yes, but I can't confirm
And whats the benefit stock vs. Wwe?
Sent from my HTC One M9 using XDA Free mobile app
my device is now locked, official and s-on
big thanks to @Mutasek24 and @scotty1223 :good:
I'm guessing that flashing the official RUU (regardless of variant, as long as you flash the correct RUU for the given variant) removes the red "development' text from the HTC splash screen?
Thank you so much for this guide!