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
Related
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... :-/
ok so i made a custom splash screen and all I need to do is compress my .IMG splash screen image with the android-info.txt file for the evo shift into a .zip...
all i need is the android-info.txt file, this is specific for each phone and i was wondering if anyone has it... it is in this format-
here is a example
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.26.651.6
hbootpreupdate:3
DelCache: 0
DelUserData:0
im.nick.hello said:
ok so i made a custom splash screen and all I need to do is compress my .IMG splash screen image with the android-info.txt file for the evo shift into a .zip...
all i need is the android-info.txt file, this is specific for each phone and i was wondering if anyone has it... it is in this format-
here is a example
Code:
modelid: PC3610000
cidnum: SPCS_001
mainver: 3.26.651.6
hbootpreupdate:3
DelCache: 0
DelUserData:0
Click to expand...
Click to collapse
Here ya go hope it's the right one.
FdxRider said:
Here ya go hope it's the right one.
Click to expand...
Click to collapse
thank you so much!
WARNING: You REALLY need to UNDERSTAND and read EVERYTHING or you MAY brick your phone!
Purpose of this thread:
To get you, the Verizon Moto X 2014 owner, from any version to 5.0 ( LXE22.46-11).
Things you will need:
FXZ LXE22.46-11
Thanks @stras1234
Instructions:
Use the RSD Flasher with KEEP DATA to flash this on your phone with RSD.
OR
Use the House of Moto with KEEP DATA to flash this to your phone with fastboot.
OR
RSD Lite 6.2.4
Has anyone done this? Mighty tempting... Didnt even know this was possible!
I'm not sure what you mean by "done this", exactly, but, if you mean flashing this FXZ to upgrade, then yes. It's the same update as the OTA that's pushing out now...this is just the full version rather than the update zip. Is that what you were asking?
Do you mind reuploading both of those tools to a new file hosting service? Because I can't see either of them because I'm not a member of DroidRZR.com and I don't intend to be.
Or just providing the direct link to a upload or mirror would be great.
Just use RSD 6.2.4 in that case. I keep the tools I wrote in one place only because there's a lot of instructions that go with it and it's easier to support if it's in one place. But the link to RSD is to a mediafire download so you should be able to grab that no problem.
Don't bother, just updated ota. Rocking lollipop now
I followed your root and boot loader unlock on the xt926 I had. You being on the moto x makes me very happy. I bow down to you
SamuriHL said:
Just use RSD 6.2.4 in that case. I keep the tools I wrote in one place only because there's a lot of instructions that go with it and it's easier to support if it's in one place. But the link to RSD is to a mediafire download so you should be able to grab that no problem.
Click to expand...
Click to collapse
Can you provide the direct links to both then? I'd like to be able to clean flash this at some point.
bmwh0r3 said:
I followed your root and boot loader unlock on the xt926 I had. You being on the moto x makes me very happy. I bow down to you
Click to expand...
Click to collapse
I don't own any of these devices. LOL
The fact you are so good with them is even more amazing.
SamuriHL said:
I don't own any of these devices. LOL
Click to expand...
Click to collapse
You're probably still rocking the Bionic
texassax said:
You're probably still rocking the Bionic
Click to expand...
Click to collapse
It's around. I'm rocking an NX6 right now. Love it.
SamuriHL said:
It's around. I'm rocking an NX6 right now. Love it.
Click to expand...
Click to collapse
Trying to extract the system.img - is there a catch with Moto devices? I can't seem to get anywhere with mounting it on Windows or OS X.
I have consulted the great and powerful(tm) search engine thingie and determined your fate on this endeavor as documented with the following scroll...
http://forum.xda-developers.com/showthread.php?t=2294909
Sent from my SM-P600 using Tapatalk
SamuriHL said:
I have consulted the great and powerful(tm) search engine thingie and determined your fate on this endeavor as documented with the following scroll...
http://forum.xda-developers.com/showthread.php?t=2294909
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
LOL - If only it were that easy. Anyone else?
SamuriHL said:
I don't own any of these devices. LOL
Click to expand...
Click to collapse
me neither
joderme said:
Trying to extract the system.img - is there a catch with Moto devices? I can't seem to get anywhere with mounting it on Windows or OS X.
Click to expand...
Click to collapse
Extracting system.img on Windows is simple Just do the following:
1. You need two utilities: sparse2img.exe and ImgExtractor.exe
2. Download and extract both in one folder
3. Put system.img in the same folder
4. Run CMD from that folder
5. Run: sparse2img system.img system_new.img
File system_new.img will be created
6. Run: ImgExtractor system_new.img
Folder system_new_ will be created. You will find all extracted files and folders here
Al936 said:
Extracting system.img on Windows is simple Just do the following:
1. You need two utilities: sparse2img.exe and ImgExtractor.exe
2. Download and extract both in one folder
3. Put system.img in the same folder
4. Run CMD from that folder
5. Run: sparse2img system.img system_new.img
File system_new.img will be created
6. Run: ImgExtractor system_new.img
Folder system_new_ will be created. You will find all extracted files and folders here
Click to expand...
Click to collapse
Welp - I feel like an idiot. I saw this method elsewhere, however, it seemed like it would only work with system1.sparse files as other updates have had multiple files for system.img.
This worked - thanks!!!
Now to find the APKs for moto assist.
This is quite interesting as none of the APKs will work on a Nexus 6.
APKs from the pure edition seem to have little problem.
I would think that the Nexus 6 wouldn't have a problem running these.
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!
Does anyone have a copy of or know where I can download a copy of the XT1060 4.4.4 system files broken down into sparse chunks?
I am trying to make a pre-rooted ext4 image for the XT1060 to use MoFo and need the sparse chunks. Thanks!
I do at home on my build box, never mind, not broken down into chunks, sorry
JulesJam said:
Does anyone have a copy of or know where I can download a copy of the XT1060 4.4.4 system files broken down into sparse chunks?
I am trying to make a pre-rooted ext4 image for the XT1060 and need the sparse chunks. Thanks!
Click to expand...
Click to collapse
Are you talking like the messaging, camera, calendar, etc.? I'm trying to figure out what exactly you're trying to do here. I've heard of pre-rooted roms (when I had my Samsung phone) but the ext4 is throwing me off a bit here.
cindylike24 said:
Are you talking like the messaging, camera, calendar, etc.? I'm trying to figure out what exactly you're trying to do here. I've heard of pre-rooted roms (when I had my Samsung phone) but the ext4 is throwing me off a bit here.
Click to expand...
Click to collapse
No, I am talking about the system image in sparsechunks. It is for MoFo - search xda paid software mofo for more info. It is a root method.
JulesJam said:
No, I am talking about the system image in sparsechunks. It is for MoFo - search xda paid software mofo for more info. It is a root method.
Click to expand...
Click to collapse
OK. Thanks for clearing that up for me.