Database Users

[Tutorial] Kernel building instructions for Xperia SP

kernel sources for Xperia SP (C5302, C5303, C5306, M35h) {FW: 12.0.A.1.257} are available...
link to download sources:
http://dl-developer.sonymobile.com/code/copylefts/12.0.A.1.257.tar.bz2
i will keep pushing stock kernel sources to my git tree at the following branch:
https://github.com/DooMLoRD/android_kernel_sony_msm8960t/tree/sony_sources
following are the build instructions for developers who plan to work on this device....
toolchain recommended: Google GCC 4.7
Building kernel (zImage):
for Xperia SP:
import defconfig
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make viskan_huashan_defconfig
build zImage
Code:
ARCH=arm CROSS_COMPILE=~/arm-linux-androideabi-4.7/bin/arm-linux-androideabi- make -j8
incase u get errors like:
Code:
error : /scripts/gcc-wrapper.py
just correct the permissions of that file
Code:
chmod 755 ./scripts/gcc-wrapper.py
here is patch for compatibility with GCC 4.7 compilation
regards,
DooMLoRD

Instructions for building kernel.elf
first get the kernel built... once kernel is built u will get zImage and copy that zImage to the folder containing the build tools...
i have posted the build tools i use here:
https://github.com/DooMLoRD/build_tools/tree/master/msm8960t_viskan
Sony using the ELF format (similar to the 2012 devices)...
build kernel.elf
u can directly use the files posted at my git repo for build tools
or
use the following command:
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
the correct RPM.bin & bootcmd are posted at my git tree for build tools...
regards,
DooMLoRD

@DooMLoRD
I have to answer a lot of questions when compiling like board selection etc (have been clicking y and and enter for about 30 minutes now) is this normal?
View attachment 2411564

Hi Doomlord.
Being a fresh Xperia User, never heard about u on HTC forums. But glad to know you are helping a lot of people around here. I was wondering whether you could help me in understanding a bit about xperia phones before i dive into kernel kanging n stuff.
What i know from HTC devices
Partitions are like this:
Boot (separate partition on NAND)
Recovery (separate partition on NAND)
System like above
Data, same
Cache, same
etc
There, we used to flash boot.img to boot. boot.img contained kernel zImage+ramdisk
For recovery, we have recovery.img which contained zImage+recoveryramdisk
Then system and data etc as every other phone.
Here in Xperia, i cant understand where the recovery is. Is it inside kernel.elf?
Is it placed on a dedicated partition?
I want to know what i am messing with, before continuing.
What i plan to do is.
Build a clean TWRP from source (for myself, usage and learning.)
Build a stock based kernel from source. Add few govs/scheds and maybe Doubletap2wake etc. (but thats a little way ahead.)
Can you help me with this?

neXus PRIME said:
Hi Doomlord.
Being a fresh Xperia User, never heard about u on HTC forums. But glad to know you are helping a lot of people around here. I was wondering whether you could help me in understanding a bit about xperia phones before i dive into kernel kanging n stuff.
What i know from HTC devices
Partitions are like this:
Boot (separate partition on NAND)
Recovery (separate partition on NAND)
System like above
Data, same
Cache, same
etc
There, we used to flash boot.img to boot. boot.img contained kernel zImage+ramdisk
For recovery, we have recovery.img which contained zImage+recoveryramdisk
Then system and data etc as every other phone.
Here in Xperia, i cant understand where the recovery is. Is it inside kernel.elf?
Is it placed on a dedicated partition?
I want to know what i am messing with, before continuing.
What i plan to do is.
Build a clean TWRP from source (for myself, usage and learning.)
Build a stock based kernel from source. Add few govs/scheds and maybe Doubletap2wake etc. (but thats a little way ahead.)
Can you help me with this?
Click to expand...
Click to collapse
The recovery is inside the kernel but that's all I know
Sent from my C5303 using xda app-developers app

Yep. I found all I needed to know.... Fotakernel partition, elf ramdisk kernel and other stuff.
Sent from my C5303 using Tapatalk

No NAND is used
EMMC is there in all new xperia devices
Sent from my C6902 using xda app-developers app

DooMLoRD said:
No NAND is used
EMMC is there in all new xperia devices
Sent from my C6902 using xda app-developers app
Click to expand...
Click to collapse
ok thanks...
one more thing, if i build a custom kernel (lets say, stock-based), without any major changes..... can i flash that kernel file without unlocking bootloader???
as i understand, only kernel ftf files can be flashed via flashtool in locked bootlaoder.... correct me if im wrong.

neXus PRIME said:
ok thanks...
one more thing, if i build a custom kernel (lets say, stock-based), without any major changes..... can i flash that kernel file without unlocking bootloader???
as i understand, only kernel ftf files can be flashed via flashtool in locked bootlaoder.... correct me if im wrong.
Click to expand...
Click to collapse
No u can't
Sent from my C5302 using Tapatalk

Siddhesh said:
No u can't
Sent from my C5302 using Tapatalk
Click to expand...
Click to collapse
I compiled my kernel with a different splash screen and it flashed but I got a flashing black screen and it doesn't boot (i have UBL)

hi @DooMLoRD,
when i am making the elf of the zImage i am getting this error
[email protected]:~/android/huashan files/build tools/jk_output$ sudo bash '/home/jk-cha0s/android/huashan files/build tools/jk_output/build_it.sh'
[sudo] password for jk-cha0s:
Traceback (most recent call last):
File "mkelf.py", line 182, in <module>
main(sys.argv[1:])
File "mkelf.py", line 159, in main
size = os.path.getsize(seg.file)
File "/usr/lib/python2.7/genericpath.py", line 49, in getsize
return os.stat(filename).st_size
OSError: [Errno 2] No such file or directory: 'ramdisk.cpio.gz'
where to get the ramdisk.cpio.gz ?
edit:its inside a working kernel extract from there

neXus PRIME said:
Yep. I found all I needed to know.... Fotakernel partition, elf ramdisk kernel and other stuff.
Sent from my C5303 using Tapatalk
Click to expand...
Click to collapse
hey hi,
i need to know how to integrate recovery into a kernel i made. please help me to do it. :silly:

About Xperia SP(m35t)
Hello DooMLoRD
I want to ask you about how to build a kernel of m35t. I had tried to use the build_tools-master to unzip the kernel of m35t, and then repacked it without any modification. I flash the new kernel.elf but the phone doesn't work, how should I do ?
I want let the m35t run on Android 4.3 cause Sony hasn't update it, hope you can help me. Thanks a lot!

NewBay_STanLey said:
Hello DooMLoRD
I want to ask you about how to build a kernel of m35t. I had tried to use the build_tools-master to unzip the kernel of m35t, and then repacked it without any modification. I flash the new kernel.elf but the phone doesn't work, how should I do ?
I want let the m35t run on Android 4.3 cause Sony hasn't update it, hope you can help me. Thanks a lot!
Click to expand...
Click to collapse
Hi,
For android 4.3 the command to pack has changed from
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
To
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline

pec0ra said:
Hi,
For android 4.3 the command to pack has changed from
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
To
Code:
python mkelf.py -o kernel.elf [email protected] [email protected],ramdisk [email protected],rpm [email protected],cmdline
Click to expand...
Click to collapse
Thanks, Pec0ra.
Yes, I know the command is changed, I repacked original kernel with build_it_JB-4.1.sh, the system is 12.0.C.2.58, everything is original, but the phone doesn't work.
I guess there is a little difference between c5303 and m35t, that I need to make a little modification to this tool.

I found the difference between m35t and other SPs
Finally, I found a difference between m35t and other SPs. The build_tools-master shouldn't be wrong, there is only one explanation is the RPM.bin not working for m35t. So,the rebuilt kernel can't boot up the m35t. @DooMLoRD, could you give me the right RPM.bin for m35t? Thanks a lot!

NewBay_STanLey said:
Finally, I found a difference between m35t and other SPs. The build_tools-master shouldn't be wrong, there is only one explanation is the RPM.bin not working for m35t. So,the rebuilt kernel can't boot up the m35t. @DooMLoRD, could you give me the right RPM.bin for m35t? Thanks a lot!
Click to expand...
Click to collapse
I think you can simply unpack it from stock kernel with the build tools. You will just have to find out which one of the extracted file it is since it might have another name.

Good news!
Good news! I found the way to extract rpm.bin witch use the flashtool. I use the version 207 C5303's zimage and ramdisk.cpio.gz and m35t's rpm.bin to repack the kernel. When I flash the kernel and version 207's rom in my m35t, it works! But only press the power button can let the back light gets on and off, the screen still can't display anything, and it can't play any sound, but it still take a big step!

TWRP v2.8.6.0 with f2fs support

TWRP for Z1c amami & Z1 Honami
Thanks to @funiewski who inspired me/ teached me how to repack Z2 twrp to work with z1 and z1c.
This ain't my work! I've just been cooking with projects made by others. Thank TeamWin, [NUT], creator of Android Image Kitchen, and others
Use at your own risk!​
Download:
TWRP_v2.8.6.0_amami-f2fs_from_cm12.1_150423.img 11.6 MB - https://mega.co.nz/#!3gRwGZiK!sXMsMx1GGwUVkTCCsr8ntZekCE-o-hB4DDp6wlhVQqA
TWRP_v2.8.6.0_honami-f2fs_from_cm12.1_150423.img 11.6 MB - https://mega.co.nz/#!qkp0jDRR!cqRQ-8CkfFmR6SJyGMCtWr2Rn89FTRl3dUNxluUWDxs
What is this?
This is a repacked TWRP from Z2 sirius, where I have:
- Replaced "default.prop" and "res"-folder to one from [NUT] dual recovery for Z1/Z1C
- Added f2fs support by adding mkfs.f2fs from CM nightly dated the day I cooked the recovery.
- Shrinked images in twres/images folder. It wouldn't boot otherwise.
More info? See recepy down below
Works for?
ONLY: Unlocked bootloader, AOSP based ROMs with support for booting a recovery from the FOTA partition.
Stock ROM, locked or unlocked bootloader: See [NUT]s project: http://nut.xperia-files.com/
How to install?
There are many ways in doing so. Fastboot: "fastboot flash recovery nameofrecovery.img" is the easiest IMO
Bugs?
Me and others have tested it, only bug atm seems to be:
- Can't adjust screen brightness in TWRP
Report if you find anything
Can you fix bugs?
Most probably not. If you find bugs regarding layout, images and stuff like that: Maybe.
This is not compiled for Z1, this is just repacked using Android Image Kitchen.
Bugs in this recovery will most probably be bugs that all TWRP builds share.
Recepy
Just repacking the Z2 recovery won't make it boot on Z1/Z1c. I believe this is due to some limitations regarding size or something.
In order to get the file size down I made a new, simple "curtain.jpg". Plain black with the text "TWRP". Kind of clean and simplistic when I think about it And I found out that these PNGs can be compressed without getting grapchical glitches:
Code:
- file.png
- folder.png
- keyboard (all)
- medium-button.png
- menu-button.png
- slideout.png
- slider-touch.png
- slider.png
- unlock.png
How I did it:
- DL TWRP for Z2 (sirius), [NUT]s lates flashable build for Z1c, Z1, and Android Image Kitchen
- Unpack TWRP for Z2 with Android Image Kitchen
- Take default.prop and "res"-folder from [NUT]s latest build, for your respective phone (z1/z1c), and copy this to the place you unpacked the Z2 recovery (inside ramdisk folder)
- Change images in "twres/images" with these (they are compressed. Unless you use them the img won't boot: https://mega.co.nz/#!e9g1TRCI!vmGsPqVdqSnpcW6G8PC_saLLyyfqTL-1FhjQmggVvxA)
- Repack with "Android Image Kitchen".
Add F2FS support:
- DL lates CM nightly
- Unpack boot.img from it, using Android Image Kitchen.
- Use 7zip to open sbin\ramdisk-recovery.cpio. Get the "mkfs.f2fs" from sbin folder.
- Add this to your project: Copy mkfs.f2fs to ramdisk\sbin
- Repack your recovery with "Android Image Kitchen".
If you want to manually edit default.prop:
Z1 Info: http://www.gsmarena.com/sony_xperia_z1-5596.php - Honami, C6902, DPI: 480
Z1c Info: http://www.gsmarena.com/sony_xperia_z1_compact-5753.php - Amami, D5503, DPI: 342
Z2 Info: http://www.gsmarena.com/sony_xperia_z2-6144.php - Sirius, D6503, DPI: 424
Guides:
Migrate to f2fs: http://forum.xda-developers.com/showthread.php?t=3004755
How to use f2fs on Sony Devices: http://forum.xda-developers.com/showthread.php?t=3056740
It's said that CM12 supports f2fs now. I haven't tested myself yet, so can't confirm.

it works great for me.nice work

Perfect exacly what i am looking for...
Flashed it and works nice, hope to see also updates in future.
Thank you :good:

How to enter in recovery?

nArdow said:
How to enter in recovery?
Click to expand...
Click to collapse
On sony logo at boot, press volume up. Led will turn from indigo/violet to orange.

TWRP v2.8.7.0 (fota) with F2FS for: Z1, Z1c, Z2, Z3, Z3c, TabZ3c(LTE&WIFI)

TWRP v2.8.6.0 (fota) with F2FS for: Z1, Z1c, Z2, Z3, Z3c, TabZ3c(LTE&WIFI)
Thanks to funiewski who inspired me/ teached me how to repack Z2 twrp to work with z1 and z1c.
This ain't my work! I've just been cooking with projects made by others. Thank TeamWin, [NUT], creator of Android Image Kitchen, and others
Use at your own risk!​
Seems like fota TWRP for sirius (Z2) will boot on all these phones: Z1, Z1c, Z2 (offcourse), Z3, Z3c and TabletZ3c (both LTE and WIFI version)!
When repacked with res/ and default.prop from NUTs dual recovery, we got TWRP for each specific device.
Download folder:
Edit 25. september 2021: Please consider using newer recoveries than these old ones.
Officially supported Sony devices: https://twrp.me/Devices/Sony/
Includes Z1 (honami), Z2 (sirius), Z3 Compact (z3c), Z3 Tablet Compact Wi-Fi (scorpion_windy)
Unofficial
Z1 Compact (amami), by 115ek: https://forum.xda-developers.com/t/3960699/
Z1 (honami), by daviid99: https://forum.xda-developers.com/t/4316409/
If you are still interested in my old frankenstein builds:
MEGA.co.nz
https://mega.co.nz/#F!fh5hhL5L!xso7GESQ9AR556_nswFfTw
Google Drive
https://drive.google.com/drive/fold...ourcekey=0-0_o2xNplFlKcnt4IaxrUdg&usp=sharing
What is this?
This is a repacked TWRP from Z2 sirius, where I have:
- Added f2fs support by adding mkfs.f2fs and fsck.f2fs from blastagators TWRP.
- Shrinked images in twres/images folder. It wouldn't boot on my Z1c otherwise.
- Switched res folder and default.prop from respective ones from [NUT]s XZDualRecovery
More info? See recepy down below
Works for?
ONLY: Unlocked bootloader, AOSP based ROMs with support for booting a recovery from the FOTA partition.
Stock ROM, locked or unlocked bootloader: See [NUT]s project: http://nut.xperia-files.com/
How to install?
There are many ways in doing so. Fastboot: "fastboot flash recovery nameofrecovery.img" is the easiest IMO
Bugs?
Me and others have tested it, only bug atm seems to be:
- Can't adjust screen brightness in TWRP
Report if you find anything
Can you fix bugs?
Most probably not. If you find bugs regarding layout, images and stuff like that: Maybe.
This is not compiled, this is just repacked using Android Image Kitchen.
Bugs in this recovery will most probably be bugs that all TWRP builds share.
f2fs does not work!!
Yes it does. The recovery will format any partition to f2fs for you. But you need a compitable kernel to use it. Don't ask me for compitable kernels, google it.
Migrate to f2fs: http://forum.xda-developers.com/showthread.php?t=3004755
How to use f2fs on Sony Devices: http://forum.xda-developers.com/showthread.php?t=3056740
Recepy
Just repacking the Z2 recovery with f2fs-files will make a un-bootable IMG. I believe this is due to some limitations regarding size or something.
In order to get the file size down I made a new, simple "curtain.jpg". Plain black with the text "TWRP". Kind of clean and simplistic when I think about it And I found out that these PNGs can be compressed without getting grapchical glitches:
Code:
- file.png
- folder.png
- keyboard (all)
- medium-button.png
- menu-button.png
- slideout.png
- slider-touch.png
- slider.png
- unlock.png
How I did it:
- DL TWRP for Z2 (sirius), Android Image Kitchen, [NUT]s XZDualRecovery flashable for your device, and blastagators TWRP for LG G2
- Unpack blastergator TWRP with Android Image Kitchen. (drag'n'drop .IMG on to the "unpack.bat")
- In ramdisk/sbin "steal" these two files: mkfs.f2fs and fsck.f2fs. Store them some place safe.
- Cleanup Android Image Kitchen folder. (cleanup.bat)
- Open XZDualRecovery with 7zip. Go to system/bin. Open the twrp file. "Steal" the res/ folder and the default.prop file. Store it somewhere safe.
- Unpack TWRP for Z2 with Android Image Kitchen
- Change images in ramdisk/twres/images with these (they are compressed. Unless you use them the img won't boot: https://mega.co.nz/#!e9g1TRCI!vmGsPqVdqSnpcW6G8PC_saLLyyfqTL-1FhjQmggVvxA)
- Add mkfs.f2fs and fsck.f2fs to ramdisk/sbin.
- Replace res folder and default.prop with the ones from XZDualRecovery
- Repack with "Android Image Kitchen". (Double click on "repack.bat")
Links:
Z1 (Honami): Official TWRP - http://forum.xda-developers.com/showthread.php?t=3234877 | http://teamw.in/devices/sonyxperiaz1.html
Z1 (Amami) : Compiled TWRP with f2fs by hawkeyexp - http://forum.xda-developers.com/showthread.php?t=3173411
Z2 (Sirius): Official TWRP - http://forum.xda-developers.com/showthread.php?t=2772879 | http://teamw.in/devices/sonyxperiaz2.html
Z3c: Official TWRP - http://teamw.in/devices/sonyxperiaz3compact.html
Z3 Tablet (Scorpion_Windy): Official TWRP: http://teamw.in/devices/sonyxperiaz3tabetcompact.html

Do it Compiling by yourself and all will works like a charm.
You guys so funy use only ONE repacked images for all other devices which have different resolutions and different kernel base

UPDATE: Packed a individual recovery for each device, with /res folder and default.prop taken from [NUT]s XZDualRecovery. Installing amami CM with sirius recovery gets aborted..

Does this work with the Z3 tablet (scorpion-windy)?
Thanks

belrik said:
Does this work with the Z3 tablet (scorpion-windy)?
Thanks
Click to expand...
Click to collapse
It would probably boot, but installs of ROMs and similar would be aborted because device id on flashable zips would not match device id of recovery.
If you modify build.prop to fit your device, I bet it would work
EDIT: Made a img for tablet z3c. I believe both 4g and WIFI-version can use the same recovery (CM uses same device ID in their build.prop)
EDIT: Separate recovery.img is up for scorpion and scorpion_windy.

o-l-a-v said:
It would probably boot, but installs of ROMs and similar would be aborted because device id on flashable zips would not match device id of recovery.
If you modify build.prop to fit your device, I bet it would work
EDIT: Made a img for tablet z3c. I believe both 4g and WIFI-version can use the same recovery (CM uses same device ID in their build.prop)
EDIT: Separate recovery.img is up for scorpion and scorpion_windy.
Click to expand...
Click to collapse
could you build a second one for tabz3c with "scorpion_windy" device ID? the scorpion one does not flash cm12.1 on my SGP611.

2 Bugs I found:
-Inability to shut off the screen. Even happens when device displays the power (full screen picture of battery). This bug doesn't affect [NUT]'s recovery.
-TWRP crashes whenever you try booting to recovery via charging cable without the system attempting to boot to Android (in other words, turning on the phone with the power cable rather than the power button). The only way out is to hard reset.
Using Xperia Z1 (honami)

kentexcitebot said:
2 Bugs I found:
-Inability to shut off the screen. Even happens when device displays the power (full screen picture of battery). This bug doesn't affect [NUT]'s recovery.
-TWRP crashes whenever you try booting to recovery via charging cable without the system attempting to boot to Android (in other words, turning on the phone with the power cable rather than the power button). The only way out is to hard reset.
Using Xperia Z1 (honami)
Click to expand...
Click to collapse
Yep. Asked in the Z2 TWRP thread, Z2 owners don't have these bugs. Might be because we use z2 related stuff (kernel base) for other phones. If I learn to compile in future this should be fixed afaik. But as far as i know, there is nothing I can do (in regards of repack with other stuff) to fix these bugs.

o-l-a-v said:
Yep. Asked in the Z2 TWRP thread, Z2 owners don't have these bugs. Might be because we use z2 related stuff (kernel base) for other phones. If I learn to compile in future this should be fixed afaik. But as far as i know, there is nothing I can do (in regards of repack with other stuff) to fix these bugs.
Click to expand...
Click to collapse
I lack knowledge with TWRP+Recoveries+Pretty much a lot of things, but couldn't you repack NUT's recovery and try porting it to Lollipop? Maybe exclude Philz's version if it conflicts...?

Hi,
is it possible, to make also a Version for the Xperia ZL?

thanks for the scorpion_windy build! :good:
unlock with material theme has some troubles. i need to get the right line on the screen for wipe to work and also then it takes several tries.

TWRP 2.8.6.1 supposedly brings support for encryption (on bacon at least) [1]. Has anyone played with that on a sony device yet? Maybe created a first package to test?
[1] https://github.com/TeamWin/Team-Win-Recovery-Project/issues/333#issuecomment-105152622

can make a version for zr/zl/z? thx!

hi anyone : )

nostupidthing said:
can make a version for zr/zl/z? thx!
Click to expand...
Click to collapse
http://forum.xda-developers.com/xperia-z/orig-development/recovery-teamwin-recovery-project-t2982889
Z already has TWRP with f2fs and stuff.
If you need it for zr or zl simply repack it with res/ and default.prop from the correct phone. Guide in 1st post.

Hi, does it work for scorpion_windy with lollipop? Thx.

v2.8.7.0 is up! I'm on stock ROM now, so please check if it works
http://forum.xda-developers.com/showthread.php?t=3098573

2.8.7.0 on sony z1 (honami) with cm-12.1 is botting, gui is ok, but internal storage and sdcard not present.

hawkeyexp said:
2.8.7.0 on sony z1 (honami) with cm-12.1 is botting, gui is ok, but internal storage and sdcard not present.
Click to expand...
Click to collapse
same on amami.
EDIT: fixed in yesterday build with z1c res and default prop! :good:

rzlatic said:
same on amami.
EDIT: fixed in yesterday build with z1c res and default prop! :good:
Click to expand...
Click to collapse
still not working on honami...

issues with otg flash drives

Videos in Otg flash drive are not showing in media player apps. However USB storage is showing file explorer apps. Is there any way to give permissions to other apps to access otg flash drive directories

dineshp953 said:
Videos in Otg flash drive are not showing in media player apps. However USB storage is showing file explorer apps. Is there any way to give permissions to other apps to access otg flash drive directories
Click to expand...
Click to collapse
It's not connected with permissions
Video app need to have implemented otg
Or create symlink, it could help a lot
Wysłane z mojego Mi A1 przy użyciu Tapatalka

What is symlink

dineshp953 said:
What is symlink
Click to expand...
Click to collapse
Type in google
Linux symlink
It's a link to directory which redirect you to the real one
Wysłane z mojego Mi A1 przy użyciu Tapatalka

How to change CID with S-ON, without SunShine

How to change CID with S-ON, without SunShine
Not so long ago, I got my U11 back under warranty - kindly replaced with a new phone (it has nothing to do with marriage). Naturally, the S-OFF license from SunShine is gone, as it is tied to the motherboard. I know before they could transfer the license to another phone, asked @beaups about it .. received the answer that no, only within a month after the purchase you can transfer the license SunShine. I understand why the month is like for the USA and it’s not that I’m offended .. and for the sake of diversity I didn’t buy S-OFF more on this device and the result is here .. and I’ll put it on xda .. This technique applies exactly to U11, U11 +, HTC 10, HTC One M9 where checked, I think today and to the U12 + too.
How to change CID with S-ON, without SunShine
(to a friend: How to save $ 25 or how much he pays for the mean )
ATTENTION!!! There is a danger that the instructions will not be properly followed, which will cause the phone to scrape and go to the SC. Therefore, if you do not have a full understanding of what it is about or you do not know how to do it, then it is better not to start! Here the author of the post or anyone else on this forum is not responsible for what was done, all responsibility lies only with you.
Baseline:
OCEAN DUGL (Dual SIM), Product ID: htc_ocndugl, MID: 2PZC30000, unlocked bootloader Unlocked, the last permanent TWRP configured by the PC to run adb utilities.
By compulsory preliminary reading: Which version you can remake your U11
For example, EMEA with SKU 2.33.401.19 and the task to remake in Taiwan, CID HTC__621 Taiwan needs
RUU for flashing the phone after changing the CID, available for this phone from the cap 2.31.709.1
#
Initial data
Reduced by 88%
Attached Image
2240 x 4000 (2.47 MB)
Reduced by 81%
Attached Image
1440 x 2560 (86.28 KB)
0. Connect the phone to the PC and load it into TWRP and move it aside:
adb reboot recovery
1. In order to be able to flash the desired RUU, we clear the software number in the phone:
1a. Execute the command from the terminal:
adb shell "dd if = / dev / zero of = / dev / block / bootdevice / by-name / misc bs = 1 seek = 2208 count = 16"
Should get an approximate result:
16 + 0 records in
16 + 0 records out
16 bytes (16B) copied, 0.007466 seconds, 2.1KB / s
1b. Check done:
adb shell "dd if = / dev / block / bootdevice / by-name / misc bs = 1 skip = 2208 count = 16"
We see instead of the software number an empty space:
16 + 0 records in
16 + 0 records out
16 bytes (16B) copied, 0.006654 seconds, 2.3KB / s
If everything is so, we move on ..
2a. Copy to the internal SD the desired section for further editing:
adb shell "dd if = / dev / block / bootdevice / by-name / board_info of = / sdcard / board_info.img"
2b. The resulting file can be edited by third-party * programs on Android on SD or copied to your PC (as I did) to the subdirectory where adb utilities, in any way or:
adb pull /sdcard/board_info.img
Attention! Save a copy of this to your original file.
3. On a PC, you can edit this file with a regular editor, such as Notepad, but better, more professionally, Hex Editor
Attention !!! There is a danger of the human factor, automatic whistles, typos. HTC's CID consists of 8 characters ... for example, Taiwan should be right: HTC__621, Europe: HTC__001, Russsia: HTC__A07. Before saving, check that you have not touched IMEI, which is written together for CID. It is necessary to edit only within 8 characters of CID, otherwise problems cannot be avoided !!!
We are looking for the current CID and fix it to the desired one:
#
save.
4a. We return the edited file to the phone in SD:
adb push ./board_info.img /sdcard/board_info.img
4b. We sew in its place edited board_info.img:
adb shell "dd if = / sdcard / board_info.img of = / dev / block / bootdevice / by-name / board_info"
The result can be seen in the download mode with the command fastboot getvar all or fastboot getvar cid
#
5. Reboot into download mode:
adb shell reboot download
from where we sew a pre-prepared RUU with extSD according to the instructions from the header, confirming it with the Volume + button, or using the RUU firmware method from a PC.
We end up with a phone on another full stock firmware:
#
5a. If someone wants to stay on the stock, then you can close the bootloader for Google Pay and similar applications according to the instructions: HTC U11 - Firmware (Post ziand # 64292895)
PS It is especially useful for those who want to change Hong Kong to another to display Russian letters in the dialer stock dialers .. etc.
PSS Of course, there is a technique and MID changes, but I do not post it for reasons of general bricks, especially on U11 ... there you also need to change something else too mfg
enjoy HTC : derisive:

The CID number is also in the files, sdf1, sde1, and it must be changed there.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

kajfux said:
The CID number is also in the files, sdf1, sde1, and it must be changed there.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
Click to expand...
Click to collapse
Hello. Please teach us if you know this tutorial.

AHMADHAFEZY said:
Hello. Please teach us if you know this tutorial.
Click to expand...
Click to collapse
You have to copy the / dev / block / sdf1 and / dev / block / sde1 files as described above, and edit them using the hex editor. Remember to edit so that you do not delete anything because it will change the structure of the file, just set the cursor in front of the CID number and overwrite it.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

kajfux said:
You have to copy the / dev / block / sdf1 and / dev / block / sde1 files as described above, and edit them using the hex editor. Remember to edit so that you do not delete anything because it will change the structure of the file, just set the cursor in front of the CID number and overwrite it.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
Click to expand...
Click to collapse
Please complete the tutorial from the beginning.

AHMADHAFEZY said:
Please complete the tutorial from the beginning.
Click to expand...
Click to collapse
You can find everything on the U11 and U11 + forums, but you must know that playing with files is a big risk, I did so but there were always problems, during the attempts to update the phone hung on the bootloader. In the end, I used the SunShine application, and now everything works fine. It is not known how much and what files, apart from those given by you and me, must be changed to make everything work well.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

kajfux said:
You can find everything on the U11 and U11 + forums, but you must know that playing with files is a big risk, I did so but there were always problems, during the attempts to update the phone hung on the bootloader. In the end, I used the SunShine application, and now everything works fine. It is not known how much and what files, apart from those given by you and me, must be changed to make everything work well.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
Click to expand...
Click to collapse
Unfortunately, it's not possible to buy and use Sanshin for my country.

AHMADHAFEZY said:
Unfortunately, it's not possible to buy and use Sanshin for my country.
Click to expand...
Click to collapse
I used this tutorial, but remember that this data may still be in other files.
You must look for any information in which files the CID is still stored.
https://www.google.com/url?sa=t&sou...Vaw2AbzuA2qFdPOxKDJqUrppd&cshid=1547131288110
Wysłane z mojego HTC U11 przy użyciu Tapatalka

kajfux said:
I used this tutorial, but remember that this data may still be in other files.
You must look for any information in which files the CID is still stored.
https://www.google.com/url?sa=t&sou...Vaw2AbzuA2qFdPOxKDJqUrppd&cshid=1547131288110
Wysłane z mojego HTC U11 przy użyciu Tapatalka
Click to expand...
Click to collapse
This worked for your u11 or do you have u11+? And which model did you change to and from ?

DaveedDB said:
This worked for your u11 or do you have u11+? And which model did you change to and from ?
Click to expand...
Click to collapse
The method is the same for both models.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

kajfux said:
The method is the same for both models.
Wysłane z mojego HTC U11 przy użyciu Tapatalka
Click to expand...
Click to collapse
Are you sure ? The commands are different the other thread points the sdf2 img ,while this one points to board img or something like that I'm a noob here ,I want to change my sprint version but idk which method is best

DaveedDB said:
Are you sure ? The commands are different the other thread points the sdf2 img ,while this one points to board img or something like that I'm a noob here ,I want to change my sprint version but idk which method is best
Click to expand...
Click to collapse
For sure, the CID number is in the files sdf1, sde1, board_info. In what other, I do not know, these are certainly needed to be edited.
Wysłane z mojego HTC U11 przy użyciu Tapatalka

Okay so I was successful in changing my sprint to us unlocked version and got the update to the June 2018 which is old but still better than 2017 Nov ,and I think US unlocked will get Pie I'm not sure about Sprint hence why I changed thanks to @ziand for tutorial and op for pointing me to it and saving me from needing to s-off

Is absolutely necessary an unlocked bootloader? Can those adb commands be executed within stock recovery?
I mean, we are flashing official firmware so the ideal scenario would be not touching the bootloader status.

DaveedDB said:
Okay so I was successful in changing my sprint to us unlocked version and got the update to the June 2018 which is old but still better than 2017 Nov ,and I think US unlocked will get Pie I'm not sure about Sprint hence why I changed that's to @ziand for tutorial and op for pointing me to it and saving me from needing to s-off
Click to expand...
Click to collapse
Pls help us a tutorial to change from Sprint to US unlocked. Tks in advance .

phuonglev said:
Pls help us a tutorial to change from Sprint to US unlocked. Tks in advance .
Click to expand...
Click to collapse
just follow the link in op he copy and pasted the translated version ,but what i did was firstly backup your internal such as pics and vids then
open both the original and translated in 2 tabs because the translated version puts spaces in the commands like:
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16"
became
adb shell "dd if = / dev / block / bootdevice / by-name / misc bs = 1 skip = 2208 count = 16"
also just remove the " so
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16
then I copied the file from my internal edited and make sure to back up this file pushed it back to my u11 i used hex editor we change our cid from SPCS_001 to BS_US001 (in the pic from other link the guy changed to TW variant i think HTC__621 only some variants can be changed which share the same mid)
dont try to boot into system like a normal reboot
the boot into download mode with cmd:
adb shell reboot download
and i used external xd card RUU method to flash the us unlocked ruu
from
https://androidfilehost.com/?fid=962157660013070749
then it will boot and you should be on us unlocked the go to settings and search for updates and they should be 2 updates there for you

AHMADHAFEZY said:
Unfortunately, it's not possible to buy and use Sanshin for my country.
Click to expand...
Click to collapse
I was bought and get s-off for my M8 (summer 2014 as I remember) if you asked how? I tell you: I buy some Prepaid Credit Card from an webstore (be carefull from cheaters!) then I got connected with an vpn apps(at that time I used psiphon) and in 5 -15 second I was paid and that's it!
however,I believe that was risky!

DaveedDB said:
just follow the link in op he copy and pasted the translated version ,but what i did was firstly backup your internal such as pics and vids then
open both the original and translated in 2 tabs because the translated version puts spaces in the commands like:
adb shell "dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16"
became
adb shell "dd if = / dev / block / bootdevice / by-name / misc bs = 1 skip = 2208 count = 16"
also just remove the " so
adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16
then I copied the file from my internal edited and make sure to back up this file pushed it back to my u11 i used hex editor we change our cid from SPCS_001 to BS_US001 (in the pic from other link the guy changed to TW variant i think HTC__621 only some variants can be changed which share the same mid)
dont try to boot into system like a normal reboot
the boot into download mode with cmd:
adb shell reboot download
and i used external xd card RUU method to flash the us unlocked ruu
from
https://androidfilehost.com/?fid=962157660013070749
then it will boot and you should be on us unlocked the go to settings and search for updates and they should be 2 updates there for you
Click to expand...
Click to collapse
im trying to connect the dots here, but having problems with this tutorial.
I have adb on my comp set up, I can enter bootloader on the phone, and thats where I get lost....
device I have is U11 2PZC500 (model name)
in htc download mode this is the info:
***locked***
htc_ocnwhl PVT S-ON
LK-1.0.0.000
radio blabla
opendsp...
etc etc
what do I do to get this junk from that 2pzc500 version, as it has some Claro bloatware on it, and it wont update to android 8.0... stuck at 7.1.1.

Gabre said:
im trying to connect the dots here, but having problems with this tutorial.
I have adb on my comp set up, I can enter bootloader on the phone, and thats where I get lost....
what do I do to get this junk from that 2pzc500 version, as it has some Claro bloatware on it, and it wont update to android 8.0... stuck at 7.1.1.
Click to expand...
Click to collapse
You enter recovery mode then enter the commands,not bootloader
But if you just want to get rid of bloat a clean flash and custom rom is better method

DaveedDB said:
You enter recovery mode then enter the commands,not bootloader
But if you just want to get rid of bloat a clean flash and custom rom is better method
Click to expand...
Click to collapse
ok, im close to figure this out.
figured out how to find out my CID, it is actually BS_US001
so I downlaoded latest RUU from HTC and need to flash it on the phone... but this is where Im stuck...
whats the simplest way?