Develop Bugs

[Dev] *obsolete* Xperia S Boot Manager v0.1 (devs only for now)

Hello Guys,
Here is my last toy, it's a dual boot system for the xperia S:
It lets you start two different kernels with their associated cpio with a third kernel that handles the boot menu and embeds cwm. It works with any kernel, this is not kexec based. As a demo in the video, I have stock firmware on regular partitions on one and cm9 on the other one with loopbacks on internal storage. I'll experiment later on with partitioning to see if we could have two sets of native partitions to make it more comfortable.
As it it's, it's quite rough, but if anyone has interest in it I will release it as it is and try to improve usability.
This is for devs and advanced users only, you would have to fiddle a lot to get the second build to run, you need an arm toolchain to embed both kernels and you have to modify its cpio.
I'm working on tools to flash kernels directly on device, but they're not ready yet. And ideally, CWM would need to be extended to support two environments. Don't expect quick progress, I don't have much free time to work on this.
Here are some details on how it works:
I trimmed down a stock kernel to remove some fat and add a driver to set a specific memory location.
I embed a small assembly loader with this kernel and its cpio plus the other 2.
The tiny kernel is loaded first, it displays the menu and eventually starts cwm. The menu will set the memory location with the kernel choice, then reboot.
At next reboot, the assembly loader will detect the kernel choice and start the appropriate kernel.
So, in fact, you're booting two times, first the small loader, then the real boot.
It adds some boot time, but it's not dramatic. The advantage is that it's easy to build the loader, it's a simple init. Second advantage, the second kernel is running on a "fresh" start, no left-over in memory, no kexec patch to apply, it works with any kernel. Last, cwm can be embedded with the tiny kernel, so it's finally independent from the build kernel.
First a disclaimer: I'm not responsible if you fry your phone using this, it's very experimental and I'm not 100% sure running a build on loopback won't reduce internal flash lifetime. I don't expect problem, but proceed with caution!
* Updates *
2012-09-07: Trimmed kernel uploaded to gitorious here , branch bootloader_kernel, boot menu (FBMenu, thanks to openAOS for initial release!) source added here.
2012-09-06, more details here :
1) on-device kernel flasher attached (kf_v0.1.zip). It let you flash kernel 1 or kernel 2 directly from device (adb from recovery for instance). You must have previously flashed dual.elf in fastboot!
And again, all of this is highly experimental! Be careful.
syntax:
kf [1|2] kernel_zimage_file cpio_file
Source code at: https://gitorious.org/sony-tools/dual_loader_kf
2) Loader source code uploaded to: https://gitorious.org/sony-tools/sony-tools, in dual directory.
2012-09-04:
If you have a 6.1.A.2.45 stock firmware, you can try the setup displayed in the video:
Download package here (mirror) and extract it on your PC.
Copy the 3 ext4 files at the root of the phone internal storage.
Reboot in fastboot mode
Flash dual.elf in fastboot mode with "fastboot flash boot dual.elf".
Reboot with "fastboot reboot"
You should now have the boot menu at each phone start. If you want to get rid of it, just reflash your original firmware kernel.
Note:
- I'm not sure cwm is working completely properly, I barely tested it.
- it may work with another stock firmware version, but the embedded stock kernel is 6.1.A.2.45 one, I'm not sure how it behaves on other builds.
Don't hesitate to give feedback here!
LeTama

wow, this is very very nice, now we can have the best of stock and cm9, thanks for all your hard work, im sure this is going to go far in the xperia s development community

Thats Realschule great when You allow i will try to implement twrp 2 at an later Version just as an Experiment
Sent from my LT26i using xda premium

This is awesome
Great job
Take as much as u want , this is so promicing

ok so my two cents : -
1. we should NOT flash kernel every time we need to boot into other OS (too much flashing = bad blocks)
2. thus I suggest we need to maintain the same kernel tree for both stock and cm/aosp/aokp kernel. the zImage will be same, but ramdisk will be different ....
3. how will that help ? we will keep a minimalistic ramdisk (containing only bootmanager) on the original kernel.elf. the stock and aosp ramdisk can reside as stock_ramdisk.gz and aosp_ramdisk.gz either inside the ramdisk (if it has space) or inside /system/dual_boot/ and the required ramdisk will be inflated/deflated on the fly as per usage requires something like
Code:
rm -f -r /sys
rm -f -r tmp
rm -f -r etc
tar -xf ./stock_ramdisk.gz
for referrence see how CWM runs using chargemon script on locked bootloader
4. we will need our own custom CWM/whatever-recovery-we-want-to-use that shall allow us to flash system1 and system2, data1 and data2, like that....
5. for optimum results i want to suggest to use current system partition as system1 and current data partition as system2, both data partition can be kept as loop devices on the internal sdcard. that will be best for space as well as speed. using any other combination we will have to sacrifice either on speed or on space.
now these are my opinions, and I'll sit down an speak with OP after my exams are over on 17th Sept. I am very much interested on this idea, because it's a win-win situation. People get to use custom firmware alongside stock and devs get more users for their ROMs because there is no risk of non-working hardware as we always have stock on the other partition

Thanks for your reply championswimmer.
I wasn't clear enough in my message I guess, so to clarify: I'm not flashing kernel each time I boot, the three kernels are flashed once and everything happens in memory. I'm using the whole 20 MB space to fit the three kernels, and my assembly loader jumps in memory to the desired kernel.
Your idea of having a single kernel for all is nice, but afaik, cm differs in kernel from stock, this is not a problem of ramdisk only.
Regarding partition scheme, well, I have no opinion yet, I'd prefer avoid loopbacks if I can repartition, but I'm not sure bootloader will let me do it. If repartition is possible, cwmod handling should be easy and only a matter of launching it while swapping on two recovery.fstab.

Noob question , so it's a kernel that hot boot another ?

Forzaferrarileo said:
Noob question , so it's a kernel that hot boot another ?
Click to expand...
Click to collapse
Not really, the first kernel+cpio is here mostly to handle the boot menu. After selection is made, the phone reboots and a small assembly loader starts the final kernel.

I added my current setup if anyone want to test it, see bottom of first post.

letama said:
Thanks for your reply championswimmer.
I wasn't clear enough in my message I guess, so to clarify: I'm not flashing kernel each time I boot, the three kernels are flashed once and everything happens in memory. I'm using the whole 20 MB space to fit the three kernels, and my assembly loader jumps in memory to the desired kernel.
Your idea of having a single kernel for all is nice, but afaik, cm differs in kernel from stock, this is not a problem of ramdisk only.
Regarding partition scheme, well, I have no opinion yet, I'd prefer avoid loopbacks if I can repartition, but I'm not sure bootloader will let me do it. If repartition is possible, cwmod handling should be easy and only a matter of launching it while swapping on two recovery.fstab.
Click to expand...
Click to collapse
Got it
Makes more sense
Great job
About repartition... We do have a lot of space in system to partiton into system1 and system2 say....
But splitting data is not good idea
Some people keep.big.games on data which need lot of space
Lets see what happens
Will check your current scheme tomorrow
Really like your memory base shifting concept... Pretty neat
Instead of 3 we can still make do with 2 kernels and 3 ramdisk.
We can keep the first kernel for both stock rom as well as the for.bootmanager
Sent from my LT26i using xda app-developers app

Regarding repartition, my idea was to take space from internal storage, no from data and/or system. We'll see... I hope I won't fry my brand new toy
Regarding having two kernels, well, yes, it's possible, but it would mean that one of them is modified to support the driver I use. It would defeats the benefit of running any untouched kernels as it is now. My modified kernel is only 2MB, it's not such a big toll on the whole 20 MB.

You could get in touch with FXP, doomlord, and binary... They are brains of xperia.
together you can make it more stable, improve it and make it amAzing
Glad to hear this news, i would never sell my phone (AOSP, sony stock rom, cyanogenmod 10)
Sent from my LT26i

All works fine , but a little question , can you share source to allow everyone to integrate the kernel that anyone want ( until dualboot compatible recovery will finished)
P.S. +1 for stylish purple led color

WooooooooW amazing :laugh:
waiting for noobs version

What a great job!
wowwwww!!!!!! just brilliant!!!!!!!!!!!!!
it looks like the magldr for hd2, which enables a multi-boot!~:good::good::good::good:

Forzaferrarileo said:
All works fine , but a little question , can you share source to allow everyone to integrate the kernel that anyone want ( until dualboot compatible recovery will finished)
P.S. +1 for stylish purple led color
Click to expand...
Click to collapse
Sure, will do. I need to cleanup the mess a bit before, but it will come soon.
The purple led is from cm9 recovery, can't take credit for that

Nice work. Maybe we should use LVM for partitions? It doesn't seem like the bootloader will let us write a new partition table.

Awesome work dude !! +1 for the effort :victory:
You guys make our phone more and more lovely !!
Keep up the great work !!
I hadn't but now unlocking my bootloader for this !!
As I am on stock .45 i will try experimenting this and give you the feedback :fingers-crossed:

isn't it a bad idea to keep the data partition the same for both say cm and stock, i had conflicts with cm without wiping data?
Sent with my Sony Xperia S using a little bit of KA magic.

K900 said:
Nice work. Maybe we should use LVM for partitions? It doesn't seem like the bootloader will let us write a new partition table.
Click to expand...
Click to collapse
Well, I just tested repartitionning, it's possible:
Code:
~ # cat /proc/partitions
major minor #blocks name
179 0 31162368 mmcblk0
179 1 2048 mmcblk0p1
179 2 512 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 1 mmcblk0p4
179 5 512 mmcblk0p5
179 6 3072 mmcblk0p6
179 7 3072 mmcblk0p7
179 8 3072 mmcblk0p8
179 9 5120 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 1048576 mmcblk0p12
179 13 256000 mmcblk0p13
179 14 2097152 mmcblk0p14
179 15 25272312 mmcblk0p15
179 16 512024 mmcblk0p16
179 17 256024 mmcblk0p17
179 18 1023928 mmcblk0p18
Now, is it reasonable to release how, that's another debate I'm not sure yet... There is definitely a risk of permanent brick with this.

AT&T Fusion 2 U8665 Root - General/Q&A

I will be editing this post, and organizing everything, so stay put.
EDIT: I am no longer using my Fusion 2 as my primary phone, but I will still be able to update this thread. If you need any help, just post here, or shoot me a PM.
Links and Guides
Root your Fusion 2
Installing CWM 6
How to install CM7.2
Q&A
Q1.How do I root my phone?
A1.There are several ways to root your phone.
Shagerty's Guide
RoboticBuddy's Guide
Q2.How do I install a Custom Recovery?
A2. User Oct3178 has discovered that the Y201 CWM works with our U8665. Check out his post here, and follow "Installing CWM Recovery":
User Shagerty has made a step-by-step guide for installing CWM.
Oct3178's Post
Shagerty's guide
Q3. Are there any ROMs for my phone?
A3. The post in A2 gives you that answer. You can use Huawei Y200 ROMs for the U8665.
RFE has also dumped a pre-rooted stock ROM.
NEW:Shagerty has developed CM7.2 for this device. Please refer to the links above the Q&A.
Oct3178's Post
RFE's Post
Thanks to RFE, who made rooting the Fusion 2 possible!

RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE

RFE said:
Thank you for creating such a nice organized thread in a good place. I've bricked a few phones now and just successfully flashed the FIRST FUSION2 ROM EVER. All that is required to apply the new ROM is fastboot & fastboot tools working.
Thanks,
RFE
Click to expand...
Click to collapse
If you could, please PM me the Rom, so I can add it to the OP.
Thank you,
-RoboticBuddy

Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.

statussticks said:
Hello, super fresh noob here. I bought the "AT&T Fusion 2 GoPhone" three days ago, and successfully used this method of gaining root access on my device. I am an experienced linux user/developer who just bought his first Android phone.. :laugh: Instead of trying to remove the factory installed components, would it be possible to build a custom version of basic/minimal Android for this device? If this is what RFE is currently doing, I would be willing to help test/bug report any such images and/or help with development. You guys are awesome by the way.. really didn't expect this phone to turn out to be such a good deal.
Click to expand...
Click to collapse
I do believe that RFE is working on a custom ROM that removes all the CrapWare that was pre-installed on the phone. Hopefully after that, he will be able to start to build CM for it.
If I could, I would attempt to start building CM for the Fusion 2, but I do not know how to setup a build environment.

Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?

Thanks
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys

still bricked
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!

BOOOYA, well done! Rooted WiFi homephone.. thank you!

Lmao, so rad

statussticks said:
Thanks for your response robo buddy. I have done some poking around myself over ssh and a sshfs mount. After researching a bit about 'standard/common' Android filesystem layouts, I'm starting to think the stock ROM on this phone is pretty screwy. There is only one flash memory block device (/dev/block/mmcblk0), and it is partitioned into nearly 20 different slices:
Code:
Device Boot Start End Blocks Id System Analysis
/dev/block/mmcblk0p1 * 1 40 20 4d Unknown ?
/dev/block/mmcblk0p2 41 640 300 45 Unknown ?
/dev/block/mmcblk0p3 641 266880 133120 c Win95 FAT32 (LBA) contains fat16 volume with arm9 radio software
/dev/block/mmcblk0p4 266881 7634943 3684031+ 5 Extended extended partition
/dev/block/mmcblk0p5 270336 294911 12288 6a Unknown ?
/dev/block/mmcblk0p6 294912 688127 196608 83 Linux /cache
/dev/block/mmcblk0p7 688128 696319 4096 63 GNU HURD or SysV ?
/dev/block/mmcblk0p8 696320 702463 3072 58 Unknown ?
/dev/block/mmcblk0p9 704512 712703 4096 46 Unknown ?
/dev/block/mmcblk0p10 712704 718847 3072 4a Unknown ?
/dev/block/mmcblk0p11 720896 727039 3072 4b Unknown ?
/dev/block/mmcblk0p12 729088 1515519 393216 83 Linux /system
/dev/block/mmcblk0p13 1515520 3088383 786432 83 Linux /data
/dev/block/mmcblk0p14 3088384 3096575 4096 47 Unknown ?
/dev/block/mmcblk0p15 3096576 3112959 8192 48 Unknown ?
/dev/block/mmcblk0p16 3112960 3153919 20480 60 Unknown ?
/dev/block/mmcblk0p17 3153920 3162111 4096 6c Unknown ?
/dev/block/mmcblk0p18 3162112 3325951 81920 83 Linux /cust
/dev/block/mmcblk0p19 3325952 7634943 2154496 6b Unknown /HWUserData (vold? mounted to /mnt/sdcard)
Partitions 1-4 do not end on cylinder boundary
This is a dump using fdisk with some minor comments at the end of each line. So my question is... where the heck are the 'boot', 'system', and 'recovery' partitions? This layout doesn't make any sense. Where does the bootloader find 'boot.img' at startup?
On top of that, I'm trying to make sense of all this Android jargon. I'm on 64 bit Arch linux with a dev setup and ADB communication with my U8665 working. Found a file "open source-kernel-2.6.38.6-U8815- Gingerbread.tar.gz" on the Huawei website. Contains what appears to be the source for the kernel version running on my U8665 right now. Many comments by authors who appear to be employed by Huawei. Grepping the source tree for 'U8665' nets results in a file 'fs/proc/app_info.c':
Code:
{ /* machine_arch_type s_board_id hw_version_id */
...
{MACH_TYPE_MSM7X27A_U8655_EMMC, "MSM7225A_U8665", "HD2U8655M"},
Searching google for the string "HD2U8655M" nets the device's PTCRB certification of some kind ..?
Ahem. I'm not exactly sure where to go from here. I am wondering if I can somehow compile this kernel along with CM 7 and build an image that way. From what I can understand from what I've read, this phone supports the ARM7 instruction set and has an Adreno GPU, so it's possible to eventually support ICS/JB..
P.S. I have some references to research I've been doing, but alas the forum wont let me insert hyperlinks until I make 10 posts
Edit: Alright, so I went further. mmcblk0p15 and mmcblk0p16 contain android images..
Code:
[[email protected] U8665]$ split_bootimg.pl mmcblk0p15
Page size: 2048 (0x00000800)
Kernel size: 3521448 (0x0035bba8)
Ramdisk size: 701945 (0x000ab5f9)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyDCC0 androidboot.hardware=huawei
Writing mmcblk0p15-kernel ... complete.
Writing mmcblk0p15-ramdisk.gz ... complete.
[[email protected] U8665]$ split_bootimg.pl mmcblk0p16
Page size: 2048 (0x00000800)
Kernel size: 3501096 (0x00356c28)
Ramdisk size: 1690977 (0x0019cd61)
Second size: 0 (0x00000000)
Board name:
Command line: console=ttyMSM0,115200,n8 androidboot.hardware=qcom
Writing mmcblk0p16-kernel ... complete.
Writing mmcblk0p16-ramdisk.gz ... complete.
So p15 is 'boot' and p16 is 'recovery', right? I should be able to build a ClockworkMod image with one of these kernels and then either fastboot flash it to recovery or just dd it into the proper device, correct?
Click to expand...
Click to collapse
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
ericrazy2000 said:
I just made an account to thank you guys for helping me root my fusion2. I am just a complete freeloader who has helped nothing whatsoever, but if i could i would! thanks guys i just hope you know you are appreciated for your hard work, and i hope a custom rom is made because i dont know how to get rid of some bloatware apps that have nand security and i have no idea how to turn that off O.O
best 100 bucks ive spent in a while for the fusion 2, i use the app pinger and i pay $0 dollars a year for texting and calling as long as i use wifi!!
well i hope u guys proceed more with this phone, if not, either way thanks guys
Click to expand...
Click to collapse
sinco54 said:
BOOOYA, well done! Rooted WiFi homephone.. thank you!
Click to expand...
Click to collapse
gigilie said:
sounds like theres some more interest in the phone now thx RFE. I'm still bricked with this one tried every way I could think of to flash those rooted stock system files they took every time via fastboot flash system but I havent been able to get the phone to load past white at&t. I'm assuming my boot.img / recovery.img / system.img either not existing or not correct for phone so unable to load. Could someone give me simple instructions to flash that or possibly rip those img files and or create an update.zip containing everything and signed properly so fastboot can flash as simply as fastboot update that'd be awesome and a quick and easy fix for anyone that bricks in the future experimenting with customs or whatever... wish I could help but new to most of this thx guys keep up the good work!
Click to expand...
Click to collapse
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:

RoboticBuddy said:
I do believe so, but I'm not too sure. Maybe you can help out RFE, since I'm no developer.
Thanks for all your support! Looks like we have potential developer (statussticks) for this phone. :good:
Click to expand...
Click to collapse
I hope so, i bought this phone at frys for 59.99 on a crazy 1 day sale for no good reason. lol... Its actually a pretty little impressive piece for the price and a custom bare bones aosp/aokp/cm would be the meow meow!!! cool little phone for sure!!

I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..

statussticks said:
I have to be honest, I know nothing about Android development. I just jumped into this because I was forced to replace my flip phone GoPhone (submerged) and ended up with a smartphone. I am going to PM RFE once more, see if I get a response.
See the thing is.. at this point I'm supposed to be able to issue the command
Code:
fastboot boot out/target/product/u8665/recovery.img
to load a test image over USB into the phone's memory and boot it (?), essentially to test a build before you flash it. I've tried this with both the 'boot' and 'recovery' kernels (p15 and p16), building a CyanogenMod-gingerbread Recovery image (apparently) successfully. When I issue the above mentioned fastboot command it reports success, but nothing happens. Phone just sits at the ATT logo, and is no longer accessible by any fastboot commands. Requires me to unplug the phone, remove the battery. Hard freeze.
So it's like.. do I really wanna run the risk of trying to flash this to recovery and bricking my phone? I'm still not sure if I can just reflash the superrecovery backup if things don't go well. I have heard incidents of people saying 'fastboot won't respond anymore, screen always stuck at the logo.'
I may just go for it a little later. Hell, I'll buy another $99 phone if I have to. I wish RFE would chime in and drop the knowledge carpet bomb or something..
Click to expand...
Click to collapse
A working twrp would be straight drug deala pimp style.. I'm gonna reach out to a couple of devs that may be willing to help out but I don't know, I may have to get him loaded and bribe him with cheap hookers. Also, if you go for it and your phone explodes into puppies then is be willing to help on a 2 device for development.. ill run by frys and see if they are on sale or if I can weasel the sales guy into hookin a sale price up today after I close the store.. stand by sweetie pie.
Sent from my HTC One XL using xda premium

Got Root/Trying to build CWM
sinco54 said:
Lmao, so rad
Click to expand...
Click to collapse
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
RoboticBuddy said:
I have made this thread to compile all the posts on rooting/custom ROMs for the Fusion 2.
Q1. How do I root my device?
A. I have put all the necessary files together in one package for rooting. https://www.dropbox.com/s/lm11rrn3z5c2j6v/Huawei-Fusion-2-Recovery-Root.zip
Q2. Is there any Custom Recovery?
A. There is no CWM or TWRP as of now, but you can boot into CWM via fastboot. http://forum.xda-developers.com/showpost.php?p=36534284&postcount=4
Q3. Is there any Customs ROMs for this phone?
A. As of now, there are NO developed custom ROMs for this phone, yet. There is a pre-rooted stock ROM, for anybody who has a bricked phone. http://forum.xda-developers.com/showpost.php?p=36533895&postcount=46
Will add more later, when I have the time.
Thanks to RFE, who made rooting the Fusion 2 possible!
Click to expand...
Click to collapse
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)

Shagerty said:
Got root no problem, but dumping the files necessary to build CWM is puzzling me.. help?
---------- Post added at 08:45 AM ---------- Previous post was at 07:48 AM ----------
After using this http://www.mediafire.com/?irr4cc14xy9ygs9 which is a method to get cwm on the first fusion. I lost the recovery.img including the stock one.. However when I replaced the CWM build for the fusion 1 found in the "INSTALLADOR" CWM thing with a build intended for the fusion 2 I am back on stock recovery! (found in a random forum don't feel like finding now will post if anyone wants PM ME)
Click to expand...
Click to collapse
I'm trying /a friend of mine/ is to get a twrp to function..
Also, these phones were on sale at Fry's again but were 79.99.. I picked 1 more up solely for development.
Sent from my One X using xda premium

Thank you! Rooted my phone without any problems following your instructions!
Probably it is a wrong place to ask such questions, but could you point me to any information how to unlock network on this phone (currently it is locked for AT&T, and can be used with their SIM cards only)?
Thank you!

I'm still looking for that info too...
Sent from my HTC One XL using xda premium

Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup and Root Uninstaller to remove AT&T apps.

Aknodx said:
Got unlocking code from one unlocking services for $15 in 24hours.
And then used Titanium Backup to remove AT&T apps.
Click to expand...
Click to collapse
Where did you buy the unlocking code?

BigPart Repartition Upgrade and Resource Center

Hello everyone.
You should know that time ago Motorola decided to stop updating our Xoom, but we showed (and we are still showing) them that our tablet is still alive and kicking.
Let me update this with the last news (a big win, indeed) from @bigrushdog:
IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, your cow starts to give bitter milk or if it unchains a thermonuclear war.
bigrushdog said:
BigPart Repartition Upgrade and Resource Center
Credits
Much love, credit, and respect go out to @Schischu and @rchtk! Your insight on the kernel patch paved the way! The Motorola Xoom cheats death once again!
Repartition Guide
1) Your data will be totally wiped! If you have Nandroids, TitaniumBackups, or anything of any value on your internal storage, copy them to your microsd or computer! They will be gone forever! Your microsd card is the only safe haven on your Xoom during this process.
2) Put all needed resources on your microsd card! You will need the original TWRP 2.6.3.0 touch recovery from @runandhide05, TWRP 2.6.3.0 BigPart version, your desired rom, and the BigPart boot image that goes with your desired rom. The BigPart boot images can be found in the next section.
3) Reboot into recovery. Flash TWRP BigPart. Don't reboot just yet.
4) Go back into wipe menu and wipe everything but /sdcard.
5) Go to reboot menu and reboot into recovery. Disregard the "No OS" warning and don't install SuperSU when asked.
6) When you come back into recovery, it will think your data is encrypted but it's not. Go into wipe menu and "format data". Type "yes" when prompted. When done, go back into wipe menu. Select "Advanced Wipe". Check "system" and "cache" and wipe them.
7) Hit Home then go to reboot menu and reboot recovery. Once again, disregard "No OS" warning and don't install SuperSU when asked
8) When you come back into recovery, go into mount menu. You should see "cache" and "data" checked. "System" will be unchecked. Check it to confirm it mounts, then uncheck it. Congratulations! You are now repartitioned!
9) Go into install. Recovery should show your microsd storage by default. If not, using the navigation panel, navigate to root then go into "sdcard". Flash your rom, BigPart boot image package, and any other resources as you normally would.
10) Reboot into system. You are done!
Later.... How to restore to stock partitions.
TWRP 2.6.3.0 R.A.H BigPart Edition Recovery
TWRP 2.6.3.0 BigPart
BigPart Eos 4 boot images with the usual modules
WARNING: You must have already executed the repartition before using these boot images. If not, follow the guide above! These will soft brick your device otherwise!
Eos 4 BigPart Wingray Boot Image
Eos 4 BigPart Stingray / Stingray_CDMA Boot Image
Eos 4 BigPart Everest Boot Image
CM10.1 BigPart Kernel by @matt4321
http://d-h.st/IzQ
For CM10.1, follow instructions in the OP but when getting to the flashing of ROMs, flash CM10.1, then flash thi
BigPart @dreamcwli MyWingray 4.3 (or in theory any 4.3) boot image with the usual modules
Note: This is a new kernel rebased on @dreamcwli 's tree. No overclock or gpu overclock yet, but soon ;D
WARNING: You must have already executed the repartition before using these boot images. If not, follow the guide above! These will soft brick your device otherwise!
MyWingray 4.3 BigPart wingray Boot Image
Click to expand...
Click to collapse
Q&A
Q: OK to understand this right, now we have a new recovery and boot. Which ROM do we use? The same as before? And BigPart @dreamcwli MyWingray 4.3 is only for wingray?
A: Yes, we have new recovery and boot. For this recovery and boot you need to use the new BigPart roms. If you are not using BigPart roms, you will need to install old recovery and boot and format everything again. And yes, it seems like @dreamcwli MyWingray 4.3 is only for wingray at the moment, but brd published a version of the last EOS4 stable with the new kernel working for BigPart.
Q: Does this new space mean we can start using full blown GApps Instead of the scaled down versions we had been previously?
(I understand there may be NEON ramifications causing a NO Answer here)
A: You can use the GApps that you prefer. Now we have space enough, but scaled down versions might be slightly faster as it uses less resources (I guess).
Q: Seems like a good time to ask and reveal my limited understanding of why user space is formatted vfat. I'm a linux fan who dislikes being limited to 4096 Mb when creating a linux.img. A yes or no answer will suffice. As long as the devs are pushing the limits, can the user space (sdcard) be formatted ext2, 3 or 4?
A: I think that that is something to implement in the kernel. I think that it is easy to do and our bakers eventually will implement it.
Q: Can cm10.2 be flashed instead of an eos4 rom after the repartition?
A: You need to replace BOOT.img in the CM zip with the BigPart compatible with your Xoom, and if the kernel is compatible with CM it will work.
Q: I'm on stingray_cdma.....unless i can flash a wingray rom and boot.img after the repart?
A: No idea, but it's safer to use roms build for your device. Take a look to the previous question.
Q: im on stingray and i tried using cm10.1 as my rom and it didnt get to the bootanimation so i tried eos 3 and it works well. couldnt get eos 4 to download from goo.im
A: brd published some EOS4 working with BigPart (see http://forum.xda-developers.com/showpost.php?p=47005701&postcount=1 )
Q: I am asking again to understand this right, now we have a new recovery and boot.
Which ROM do we use? The same as before? Do we have to change the boot IMG in the ROM with the big part one?
And BigPart @dreamcwli MyWingray 4.3 is only for wingray or it can be used with everest as well? And what is its difference with the other big part in the kernel?
A: Use only BigPart roms. You will need to change the boot.img from the rom if the rom is not compatible with BigParts, but if the rom is not compatible with the new kernel, it is useless... MyWingray is compatible with Everest but you will not have 3G, I guess... But I'm not sure.
Q: That's great. @bigrushdog @realjumy Is there a way to get the radios for everest and stingray on a separate zip?
A: The rom must be cooked with the radios...
Q: I wanna ask you because i have my xoom forma two years, and laste time i format it and give me error with dev block mmblck or something else and i think that i could have my internal storage corrupt.. If i install your 4.3 image modded, and then the repartition, Will it works fine?? Thanks and sorry me
A: No idea.
Q: Followed the instructions for the re-partitioning. Everything worked except the Xoom cannot see the external sd card in recovery. I have re-formated it as fat32 and tried another card. When I view the files in the PC they are there. Any ideas?
A: Something something went wrong... Copy the data from the SD to your PC, format SD and put back data. Let's see if that works...
Q: How can we identify which ROMs are for the new partition layout? Just assume everything 4.3 and later? It would be nice if we added [BigPart] to the thread title to make them more easily identifiable.
A: Only roms with BigPart in their name can be used with the new layout.
Q: I was under the impression that we could use old roms provided we replaced the boot.img in the zip with the NEW BIGPART boot.img for our unit? (Only after repartitioning has been completed) Is that wrong and we need to wait for a particular build?
A: Not all the roms are compatibles with the boot.img method (kernel method). You will need to try to be sure. EOS4 and Dream's have proper versions. If you want to use, for example, CM you will need to:
option 1.- Build it yourself patching the kernel
option 2.- Use CM and try to use a different kernel
option 3.- Ask to the CM maintainer to release BigPartition versions.
There is a lot of 4.2.2 projects running, some 4.3 and if we are successful, MAYBE we will be able to port 4.4 to our devices. One of the main problems (but not the only one) is the internal storage structure of the tablet. It seems that is not too hard to solve, as in other devices (mainly Samsung) is common to change it.
The aim of this project is to compare how the internal partitions are setted up in order to change them and have more room for system and apps. This will improve all the ROMS (4.1, 4.2.*, 4.4). @bigrushdog is doing a big effort to change it but we need more data from all models to compare and be sure that we don't break anything.
It will take up to 3 hours (depends on the model) but is something that can work while you are sleeping or not using the tablet. With the data provided by you, we can compare and choose the best changes.
IMPORTANT: It should be harmless for your Xoom, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your Xoom bricks, dies, loses the data, gets cursed, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.
IMPORTANT: It should be harmless for your PC, but you need to do it at your own risk. Nobody will give you any kind of warranty and we will be not guilty if your PC bricks, dies, gets cursed, loses the data, makes your cow begin to give bitter milk or if it unchains a thermonuclear war.
What are you going to do:
You are going to do a 1:1 copy of your internal storage into your PC. Then, we will detect the partitions and where begins and ends each one. Nothing else. We will compare the different versions and in the future a tool will be released to make the changes.
What you will need:
Linux (maybe you can use a Live DVD / USB?). It should be a way to do this process under Windows. If you know how to do it, please, share the info.
33GB of disk space in your computer, anywhere.
Android SDK working (that means that if you plug your tablet turned on and run
Code:
./adb devices
in the folder "platform-tools" of your SDK will provide a serial number): http://developer.android.com/sdk/index.html
3 hours (can be done while sleeping, not using the tablet, etc) if you have a 32GB Xoom.
Rooted Xoom.
Before you begin:
DO A NANDROID BACKUP!!!!!
READ EVERYTHING AND ASK IF YOU DON'T UNDERSTAND SOMETHING
Step by step:
Full charge your tablet (or keep it connected to AC?) and turn it on WITHOUT SDCARD.
If your Android SDK is not installed or working properly, fix it now: http://developer.android.com/sdk/index.html
Install the dependencies. For Ubuntu / LinuxMint / Debian:
Code:
apt-get install testdisk netcat pv extundelete testdisk
Activate USB Debug on your device (in order to connect with adb). You can find it under Settings > Developer options.
Note: On Android 4.2 and newer, Developer options is hidden by default. To make it available, go to Settings > About phone and tap Build number seven times. Return to the previous screen to find Developer options.
Click to expand...
Click to collapse
Plug your tablet (it must be on) and run
Code:
./adb devices
in the folder "platform-tools" of your SDK. If you don't get as a result a serial number, STOP. Something is wrong with your SDK. Please, fix it to continue.
Open a terminal on your computer, go to the Android SDK directory's subdirectory sdk/platform-tools (where adb is located).
We will setup a forward port to be able to download the data to our PC:
Code:
./adb forward tcp:5555 tcp:5555
Now we will connect to the tablet
Code:
./adb shell
Maybe you need to grant permission to do it. Take a look to your tablet's screen.
We become superuser:
Code:
su
Grant permanent permissions when asked. You can revoke the permissions later if you want.
With this we will transfer the data to the port that we set previously:
Code:
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
DON'T CLOSE THAT TERMINAL. An now OPEN A NEW ONE IN THE PC.
Go again to the folder "platform-tools" of your SDK and let's collect the data:
Code:
./adb forward tcp:5555 tcp:5555
Code:
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw
If you want to save the file in a different place/partition, change what is after ">". For example, if I want to save the file in my home folder, I will write /home/jumy/mmcblk0.raw. If you are not sure or don't know how to do it, don't change it.
You will to wait up to 3 hours until it finish.
When the transfer is finished, run this in the folder where the dump is located (if you changed nothing, it is located in the older "platform-tools" of your SDK):
Code:
testdisk mmcblk0.raw
First restore the GPT partition table. Select mmcblk0.raw in the TestDisk interface and choose Proceed.
Choose EFI GPT.
Then select Analyse.
Choose Quick Search.
The search will return a table that you should copy and paste in this thread.
Now you can exit and remove the dumped file (mmcblk0.raw).
Please, when you provide the data, tell us which model, storage size, ROM name and version and indicate if it is the Hong Kong model.
Info collected from http://www.df.lth.se/~jokke/androidfilerecovery/ --> Visit it if you want some screenshots.

Everest, 32GB, using EOS4 V170, NOT Hong Kong model.
Code:
Partition Start End Size in sectors
>P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 993280 62319583 61326304

Ill Help!
Testing in progress... =]
Device: XOOM 32GB Wingray MZ604
Android: 4.2.2
ROM: EOS4 Nightly 203
EDIT: i did my bloody SD card... did it again and now heres the internal 32GB
Code:
Disk mmcblk0_1.raw - 31 GB / 29 GiB - CHS 3880 255 63
Partition Start End Size in sectors
P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 993280 62319583 61326304

4.4
No problem for test

Would love to test
I would really love to test Android 4.4 on my Xoom... The new platform seems to be much faster and my Xoom feels very slow and clumpy on Android 4.2 and even 4.1

djripster said:
I would really love to test Android 4.4 on my Xoom... The new platform seems to be much faster and my Xoom feels very slow and clumpy on Android 4.2 and even 4.1
Click to expand...
Click to collapse
4.4 will have the same problem that 4.2.* and 4.3 as it is a problem with the storage. That is the reason why we need so badly to change the partitions, and that is why we are asking for help to collect this data.

I'm running it now!
Sent from my Xoom

notbrodie said:
I'm running it now!
Sent from my Xoom
Click to expand...
Click to collapse
That's great!!!!

i got no Linux box. will see if i can do some research over the weekend on Windoze tools.

I derped my development laptop so I was down a few days. I think we have what we need for a repartition script. As some of you know kitkat source dropped. Under the hood, not much changed. At least from what I hear. So I'll slap together a theoretical repartition script. Any volunteers?

realjumy said:
That's great!!!!
Click to expand...
Click to collapse
Disk mmcblk0.raw - 1967 MB / 1875 MiB - CHS 240 255 63
Partition Start End Size in sectors
>P MS Data 47104 51199 4096
P MS Data 61440 65535 4096
P MS Data 122880 647159 524280
P MS Data 647168 993279 346112
P MS Data 1860958 1862168 1211 [\^I]
Xoom WiFi 32GB EOS-203, Not Hong Kong.
also: 3 hours... lol. it took 18 minutes
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
bigrushdog said:
I derped my development laptop so I was down a few days. I think we have what we need for a repartition script. As some of you know kitkat source dropped. Under the hood, not much changed. At least from what I hear. So I'll slap together a theoretical repartition script. Any volunteers?
Click to expand...
Click to collapse
Count me in! i've got a nandroid on my external sdcard, though I'm not sure what good that'll do if the repartitioning fails...
---------- Post added at 08:18 PM ---------- Previous post was at 08:09 PM ----------
about to load 4.4 on my N4... let's see if this super-hyped new android is really that much different/better than 4.3!

Model: MZ604 (wifi-only)
Storage size: 32GB
ROM: EOS Stable release 3.0
NOT Hong Kong model
testdisk output:
Code:
Disk mmcblk0.raw - 32 GB / 29 GiB - CHS 3892 255 63
Partition Start End Size in sectors
>P MS Data 43008 47103 4096
P MS Data 57344 61439 4096
P MS Data 118784 643063 524280
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
Took a bit more than 3 hours...
notbrodie, there may be something wrong in your experiment as the dump file is only around 2GB. Or maybe you just have non-standard partitioning, I am not sure...
PS: Small correction to the instructions (just to make it perfect):
- closing code tag seems to be lost in ./adb shell command
- A typo in "If you want to save the fine"

Thank you guys!
Sent from my Nexus 4 using Tapatalk

DaniLoveSky said:
Model: MZ604 (wifi-only)
Storage size: 32GB
ROM: EOS Stable release 3.0
NOT Hong Kong model
testdisk output:
Code:
Disk mmcblk0.raw - 32 GB / 29 GiB - CHS 3892 255 63
Partition Start End Size in sectors
>P MS Data 43008 47103 4096
P MS Data 57344 61439 4096
P MS Data 118784 643063 524280
P MS Data 643072 989183 346112
P MS Data 989184 62512095 61522912
Took a bit more than 3 hours...
notbrodie, there may be something wrong in your experiment as the dump file is only around 2GB. Or maybe you just have non-standard partitioning, I am not sure...
PS: Small correction to the instructions (just to make it perfect):
- closing code tag seems to be lost in ./adb shell command
- A typo in "If you want to save the fine"
Click to expand...
Click to collapse
Thanks mate. I will correct the post later from the PC.
Sent from my Nexus 4 using Tapatalk

I'm dumping stingray right now. From what i can see, it already looks like the offsets are different for different models. That's very good to know. So calculations will need to be made for each version. After talking with @Roach2010 he says there may be partition table info that needs updating somewhere in the NAND dump. However, it doesn't appear that is the case for all devices. Once i get this dump we can play some more.
EDIT: found some interesting information http://forum.xda-developers.com/showthread.php?t=1388996

You guys... are brilliant... I'm in. My Xoom is just collecting dust since Eos shutdown.

also guys im getting my nexus 5 by the end of the week, let me know if you want any information extracted from that ! will be rooting that m*****f***er soon as! which leaves me with 2 dev devices XOOM and S2

I have a mz605 umt_everest model, at monday in my lab I will do this and post here.

bigrushdog said:
I'm dumping stingray right now. From what i can see, it already looks like the offsets are different for different models. That's very good to know. So calculations will need to be made for each version. After talking with @Roach2010 he says there may be partition table info that needs updating somewhere in the NAND dump. However, it doesn't appear that is the case for all devices. Once i get this dump we can play some more.
EDIT: found some interesting information http://forum.xda-developers.com/showthread.php?t=1388996
Click to expand...
Click to collapse
Nice find, so by doing this research and analysis it will be possible to create a universal partition structure (in terms of the XOOM versions). am i right in thinking this?

LOGMD said:
Nice find, so by doing this research and analysis it will be possible to create a universal partition structure (in terms of the XOOM versions). am i right in thinking this?
Click to expand...
Click to collapse
No... Whit this we will be able to:
1.- Check if every Xoom version have the same or different partition structure (done, each model has a different structure).
2.- See how every model need to be restructured (pending, that will be next step).
3.- Provide a script to make it easy to do (we need to do the 2nd step first).
Sent from my Nexus 4 using Tapatalk

[Q] a little help here

I have a sm-t210r tab and ever since I've updated it to 4.4.2 it gives me so many bugs after I've install a new ROM for example nolekat and i know for a fact that it's not the ROM because I've install the same ROM on my little sister's tab and she has no bugs her tab is not updated. So my question is if there is any way to remove the new bootloader or to downgrade?

Please anyone? Its driving me crazy to see my little sister's tab running so nice and mine keeps unfortunately stopping apps at random and even random reboots it sucks.

kgalv419 said:
Please anyone? Its driving me crazy to see my little sister's tab running so nice and mine keeps unfortunately stopping apps at random and even random reboots it sucks.
Click to expand...
Click to collapse
You need to update your recovery to its latest version. I recomend philz touch!

That's what I'm using bro

i have installed philz touch, so how do we downgrade bootloader?

That's all i want to know too? I know someone can figure it out

from my post in note 10 forum
kgalv419 said:
I have a sm-t210r tab and ever since I've updated it to 4.4.2 it gives me so many bugs after I've install a new ROM for example nolekat and i know for a fact that it's not the ROM because I've install the same ROM on my little sister's tab and she has no bugs her tab is not updated. So my question is if there is any way to remove the new bootloader or to downgrade?
Click to expand...
Click to collapse
stewart30 said:
i have installed philz touch, so how do we downgrade bootloader?
Click to expand...
Click to collapse
this has worked on gt-p5210, gt-n8013 so it stands to reason it should work on the t210
keep in mind these instructions are in the specifics for the gt-n8013, adjust accordingly.
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb in recovery mode
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
edit-or pack it for recovery flashable
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
Click to expand...
Click to collapse
m
kgalv419; you can pull the original from your sister's tab if it's t210r , just don't screw it up.

Thanks a lot bro will get to work on it now and let u know how it went thanks again

i have one last question bro, i successfully got the fix.img from my sister's tab and turn it into a flash-able zip. Should i use odin to flash the official 4.1.2 then flash the zip via recovery? or flash the zip first then use odin?

kgalv419 said:
i have one last question bro, i successfully got the fix.img from my sister's tab and turn it into a flash-able zip. Should i use odin to flash the official 4.1.2 then flash the zip via recovery? or flash the zip first then use odin?
Click to expand...
Click to collapse
for my note 10 and for the tab 3 10
flash the fix first - provided you're absolutely certain you got it right.
then flash the rom though, i don't think you should any of the above for a tab
that doesn't really need a rescue. Just triple check every step before you perform it
and be deliberate and not impulsive. Good luck.
m

Thanks a lot moon

What exactly does the fix.img do moon?

kgalv419 said:
What exactly does the fix.img do moon?
Click to expand...
Click to collapse
k,
hey,
sorry to take so long in getting back to you,
please re-read my post in this thread about the procedure carefully, just to get your head in the game.
now, the reason for this approach to restoring original bootloader is because if you try to write the bootloader
via the dd command directly in normal operation and recovery the tab kicks back and reboots and in that
scenario you stand a VERY good chance of hard-brick, dead, done.
pulling/dumping from /dev/mmcblk0 for X=amount in MB has the same effect as a cloning procedure and seems to work
well, i have done this on my gt-n8013 and coached another user through the process for the gt-p5210 using the data i pulled
from my own tab and packeged for recovery flash. I am saying you should consider not doing this for a tab that isn't
soft-bricked to a degree that would make this exercise necessary. You may just need to use a different rom instead.
m
keep in mind you will need to re-flash a rom afterward. NOT and odin firmware but an appropriate xda recovery flashable
rom for your device.

[GUIDE/TUTORIAL/HOWTO] Sony Xperia S stock to Android 8.1 Oreo

[GUIDE/TUTORIAL/HOWTO] Sony Xperia S stock to Android 8.1 Oreo
[GUIDE/TUTORIAL/HOWTO] Upgrade Sony Xperia S (Model LT26i codename nozomi) from Android 2.3.7 to Android 8.1 Oreo / nAOSP Rom
This detailed step-by-step guide helps you transform your Sony Xperia S to a much fresher one with Android 8.1 Oreo.
To make sure you are with a compatible Xperia S:
On the smartphone, go to Settings > About phone. Check that "Model number" is correct: LT26i.
### We need to make sure Bootloader can be unlocked before going further.
Open dialer, enter code
Code:
*#*#7378423#*#*
In the follow menu, go to Service info > Configuration > Rooting status.
Bootloader unlock allowed: Yes
If it is set on No, you cannot update your device. You can quit this tutorial and cry, you will never unlock it.
### You must be logged as a Microsoft Windows administrator to run console commands below.
CHANGELOG
v4. Moved to Bitgapps to solve infinite GApps "searching for updates", TWRP 3.5.2_9-0
v3. Android 7.1 if needed, hints to solve problems (error 7, fdisk -l)
v2. Slight tutorial improvements
v1. Initial release
1) DOWNLOAD FILES
- djibe Xperia S pack: https://bit.ly/djibe-xperias-pack
(contains FlashTool Xperia Driver Pack 1.8 for USB drivers + fastboot/adb + recovery TWRP 3.5.2_9-0)
+ ROM nearAOSP 8.1 build 11: https://forum.xda-developers.com/t/rom-8-1-naosprom-for-xperia-s-acro-s.3853082/
Download latest build (2020/03 or newer): https://androidfilehost.com/?w=files&flid=240525&sort_by=date&sort_dir=DESC
+ BitGApps Package ARM 8.1: https://github.com/BiTGApps/BiTGApps-Release/releases
+ You find Android 8.1 laggy ? Android 7.1.2/nAOSP is suitable https://androidfilehost.com/?fid=890129502657590583
Download according BitGApps.
+ Charge phone to 100%.
NB. Use a USB2 port to connect tablet to PC.
2) INSTALL USB DRIVERS
Commands below are for Windows 10 installation of unsigned drivers.
### For other Windows versions, Google "windows X install unsigned driver".
On the keyboard of PC, use "Windows key + R" combo.
In the command prompt that opens, type:
Code:
shutdown -r -t 0 -o
This opens a Windows menu:
Go to Troubleshooting > Advanced Options > Settings > Restart
Upon restart, press on keyboard : key 7 - Disables drivers signature verification
After boot,
Start Flashtool Xperia Driver Pack 1.8,
check the Flashmode Drivers, Fastboot drivers, Common drivers Fuji board (both lines) and Xperia S driver for ICS.
Start the installation and confirm the forcing the driver installation.
It ends by saying that everything was installed.
Restart Windows.
3) BACKUP ALL YOUR DATA
Backup every SMS, photo, app login or sync everything in the cloud.
You will lose everything, including what is contained in the microSD card during bootloader unlock.
So backup everything and transfer every file to your computer.
### Do it now or you will regret it.
4) IMEI NUMBER AND UPDATES
On phone, go to Settings > About phone > Status > IMEI
Note the IMEI (15 digits). Store it.
5) MAKE SURE PHONE IS NOT SIMLOCKED
We need to check phone is not SIMlocked.
Open dialer, enter code again
Code:
*#*#7378423#*#*
Go to Service info > SIM lock. If everything is blank/unchecked ( [] ), phone is Desimlocked.
If not, you must contact your network provider for an unlock code.
### Don't move further until phone is simlocked. You cannot debrand/desimlock it using a custom ROM.
6) GENERATE BOOTLOADER UNLOCK CODE
From your PC, go to https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
At the bottom of the page, in "Select your device:" menu: select Xperia S.
Enter your IMEI, check first 2 checkboxes "I acknowledge that", click Submit and complete the captcha to generate unlock key.
Note the unlock code (beginning and end of page paragraph C.)
7) CONNECT PHONE IN FASTBOOT MODE
Phone powered off, hold "Volume up" while you plug phone in USB.
The blue light appears at the front bottom edge, the drivers install in Windows.
8) UNLOCK BOOTLOADER
In Windows, copy the path to the "flash" folder you unziped earlier.
Open a Windows command prompt : Start menu > Command prompt > Start as administrator
Then type
Code:
cd /d thePathToFlashFolder
(ex: E:\root\djibe Sony Xperia S\djibe\flash)
Type:
Code:
fastboot devices
If "PSDN:..." is returned, drivers are correctly installed.
Create this text: fastboot -i 0x0fce oem unlock 0xAPPENDYOURUNLOCKCODEAFTER0x
Paste the previous line in windows command:
Code:
fastboot -i 0x0fce oem unlock 0xAPPENDYOURUNLOCKCODEAFTER0x
confirm with Enter.
After 5 seconds, it is displayed Finished. Total time: ...
Bootloader is unlocked !
9) FLASH TWRP RECOVERY 3.5
Still in fastboot, type in console :
Code:
fastboot flash boot twrp-3.5.2_9-0-nozomi.img
. Confirm with Enter.
Wait, then once the confirmed success,
type :
Code:
fastboot reboot
(confirm with Enter).
Be fast to disconnect phone AND while it restarts, repeatedly click Volume+ AND Volume- buttons to access the recovery (can take a while).
Reconnect phone to PC once recovery has started.
10) BACKUP ORIGINAL ROM AND USE TWRP RECOVERY
You are now in TWRP recovery,
check Never show this screen during boot again and Swipe to Allow modifications.
Go to Backup, select all partitions.
Confirm with OK.
Then swipe to start backup.
Click the TWRP icon to return to home.
Go to Mount. Select Data partition and make sure bottom right button is dsiplaying Disable MTP text.
Phone must be connected to computer.
In Windows Explorer, open Xperia S device > Internal Storage.
Copy whole TWRP folder and save it somewhere safe on your PC.
In the opposite way, copy twrp.img and paste it in the same phone's folder you grabbed TWRP folder (SDcard root folder).
11) FLASH A PERMANENT TWRP RECOVERY
The TWRP recovery you are using is temporary.
We need to flash it on a partition.
Back to TWRP Home screen > Install > Install Image button > twrp.img > Select boot partition > Swipe to flash.
12) REPARTITION INTERNAL MEMORY
Newer Android versions changed the partition layout. We have to do so.
Back to TWRP Home screen > Mount.
Deselect ALL partitions.
You can copy-paste commands with right click in the Windows command.
From Windows command, type following commands:
Code:
adb devices
Command returns: List of devices attached
CB511Z8FWJ recovery
Code:
adb shell
Code:
fdisk -l /dev/block/mmcblk0
### fdisk -l (this is letter L, not number 1)
Command returns
Code:
4 heads, 16 sectors/track, 973824 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 65 2048 f0 Linux/PA-RISC boot
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 65 81 512 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 129 768 20480 48 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 769 954240 30511104 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 785 800 512 46 Unknown
/dev/block/mmcblk0p6 833 928 3072 4a Unknown
/dev/block/mmcblk0p7 961 1056 3072 4b Unknown
/dev/block/mmcblk0p8 1089 1184 3072 58 Unknown
/dev/block/mmcblk0p9 1217 1376 5120 70 Unknown
/dev/block/mmcblk0p10 1409 1664 8192 83 Linux
/dev/block/mmcblk0p11 1665 2176 16384 f0 Linux/PA-RISC boot
/dev/block/mmcblk0p12 2177 34944 1048576 83 Linux
/dev/block/mmcblk0p13 34945 42944 256000 83 Linux
/dev/block/mmcblk0p14 42945 108480 2097152 83 Linux
/dev/block/mmcblk0p15 108481 954240 27064320 c Win95 FAT32 (LBA)
~ #
### Copy all the text of the partition layout to be able to reformat in case of a crash.
### Paste this text in a file somewhere safe on your PC.
We are interested by line /dev/block/mmcblk0p14, Start sector: 42945 in my case,
And /dev/block/mmcblk0p15 End sector: 954240 for me.
### These values may differ for you. USE YOUR OWN VALUES.
Now type
Code:
fdisk /dev/block/mmcblk0
Commands returns: Command (m for help):
Enter
Code:
p
Commands returns: Command (m for help):
Enter
Code:
d
Command returns: Partition number (1-15):
Enter
Code:
15
Commands returns Command (m for help):
Enter
Code:
d
Command returns: Partition number (1-15):
Enter
Code:
14
Commands returns: Command (m for help):
Enter
Code:
n
Command returns: First cylinder (769-954240, default 769):
Enter
Code:
42945
(Your /dev/block/mmcblk0p14 Start sector)
Command returns: Last cylinder or +size or +sizeM or +sizeK (42945-954240, default 954240):
If "default 954240" is the same as your /dev/block/mmcblk0p15 End sector, just press Enter.
Commands returns: Command (m for help):
Enter
Code:
t
Command returns: Partition number (1-14):
Enter
Code:
14
Command returns: Hex code (type L to list codes):
Enter
Code:
83
Commands returns: Command (m for help):
Enter
Code:
w
And let command return to its waiting state: ~ #
We must restart phone now, unplug USB and from TWRP go to Reboot > Recovery for a refresh of partition table.
### Your TWRP recovery is not compatible with new partition layout.
13) FORMAT PARTITIONS TO F2FS
nAOSP Rom doesn't support EXT4 filesystem. We need to repartition to F2FS, easily with TWRP.
### If you experience errors while flashing like "Unable to mount storage", use TWRP 3.2.3 instead: https://androidfilehost.com/?fid=1322778262904003720
Check Never show this screen during boot again and Swipe to Allow modifications.
Back to TWRP Home menu.
Go to Wipe > Wipe Advanced > Select Data > Repair or Change File System > Change File System > F2FS.
Repeat same procedure for Cache partition.
We must restart phone now, go to Reboot > Recovery for a refresh of partition table.
### If you don't, you won't be able to flash zipfiles.
After reboot, Swipe to Allow modifications.
### If you still see 0MB or a wrong size for data after the reboot, try to format data (Wipe/Format Data).
### In the worst case, convert data to ext4 and convert back to f2fs will do the job.
### You get ERROR 7, Failed to mount '/system' etc.), try this fix: https://bit.ly/3BvcYvM
### Failed to mount '/system' error: https://bit.ly/3yF2jwX
14) PUSH ROM AND GOOGLE APPS
Go to Mount > make sure nothing is mounted.
Connect phone to PC with USB.
Copy downloaded ROM and Google Apps to your /flash folder (along adb.exe and twrp.img).
Rename bitgapps*.zip to gapps.zip
Make sure adb is still running with 'adb devices' command.
Now push the ROM to the phone with
Code:
adb push nAOSProm-8.1.0-b11-nozomi.zip /sideload
Then
Code:
adb push gapps.zip /sideload
15) INSTALL ROM AND GOOGLE APPS
Go back to TWRP Home menu.
Go to Install > You are in /sdcard empty folder.
Tap on (Up a level) > sideload.
Select nAOSProm > Swipe to flash.
Wait during "Install Zip".
Then Reboot > Recovery
Go back to Install > select bitgapps*.zip > Swipe to flash.
## Problems flashing? Use TWRP 3.2.3-0: https://eu.dl.twrp.me/nozomi/twrp-3.2.3-0-nozomi.img.html
At the end, tap on Wipe Cache/Dalvik and Swipe to wipe.
Then tap on Reboot system.
Wait during long first boot.
Enjoy your new phone.
16) BETTER PERFORMANCES
Go to Settings > About phone.
Tap 7 times on Build number.
Go to Settings > System > Developer options.
Set Windows animation scale, Transition animation scale and Animator duration scale to 0.25x.
Right below, you may try to switch Force GPU rendering On (default is off but feels slower, isn't it ?)
17) ROOT
nAOSProm has a built-in root.
No extra Root manipulation needed.
### DO NOT TRY MAGISK, you will have problems.
### If you run in troubles with Magisk, see the end of this tutorial.
Configure Android as you like.
For faster GPS fix, use GPS Status and Toolbox and download A-GPS data.
You may try Greenify app to improve battery.
Your phone is up to date, enjoy ;-)
Thanks: @millosr, @mickybart, @AdrianDC, TWRP team, OpenGApps team, Flashtool Xperia Driver pack team
-----------------------------------------------------------------------
### Android doesn't see Wifi channel 14 (or 13),
Your phone doesn't see your local Wifi network?
You are probably european and your wifi is set to channel >= 11.
Reboot to TWRP recovery.
Go to Mount > check System partition.
Open a Windows command like before:
Code:
adb pull /system/build.prop
Edit file with Notepad++ freeware.
Locate line: ro.wifi.channels=
Change it to: ro.wifi.channels=14
Add this line just below: ro.boot.wificountrycode=EU
Save file.
Send modified file to phone:
Code:
adb push build.prop /system/
Disconnect phone, go to Reboot > System.
-------------------------------------------------------------------------
### Tried Magisk and it doesn't work ? (we know it doesn't)
You can't access recovery because phone restarts as soon as it reboots.
Let battery drain by bootloop.
When it is exhausted, hold Volume+ and connect phone tu USB, blue light will appear (fastboot mode).
Unzip boot.img from nAOSProm-8.1.0-b11-nozomi.zip to /flash folder (along fastboot.exe).
Make sure fastboot is OK with
Code:
fastboot devices
Then
Code:
fastboot flash boot boot.img
And restart with
Code:
fastboot reboot
Phone is op.
Enjoy

Thank you very much for this detailed guide. I have two questions:
1) Why do you recommend to flash version 2.3.7 of Android before beginning this procedure?
2) Everytime I have Flashed nAOSProm-8.1.0-b11-nozomi.zip on my phone (folllowing the original guide), I've had a very annoying bug, which is that it's really difficult to answer a phone call (I have to swipe the phone icon up several times until it finally rsponds). Of course I have always made a totally clean flash of the rom. Do you know what the reason for this can be?

TXUTXI72 said:
Thank you very much for this detailed guide. I have two questions:
1) Why do you recommend to flash version 2.3.7 of Android before beginning this procedure?
2) Everytime I have Flashed nAOSProm-8.1.0-b11-nozomi.zip on my phone (folllowing the original guide), I've had a very annoying bug, which is that it's really difficult to answer a phone call (I have to swipe the phone icon up several times until it finally rsponds). Of course I have always made a totally clean flash of the rom. Do you know what the reason for this can be?
Click to expand...
Click to collapse
Hi,
1) By precaution. For some phones you have to flash latest firmwares which upgrade bootloaders. We never know and there is no information about this. Just precaution.
2) I will test it.
Have you tried another call app ? That's the benefit of Android.

djibe89 said:
Hi,
1) By precaution. For some phones you have to flash latest firmwares which upgrade bootloaders. We never know and there is no information about this. Just precaution.
2) I will test it.
Have you tried another call app ? That's the benefit of Android.
Click to expand...
Click to collapse
Hi again! Thanks for answering.
First of all, 2.3.7 was not the last firmware for Sony xperia s, but the first one. The last one was Jelly Bean (4.1.2, or something like that, as far as I remember). So I am confused by your answer.
Secondly, yesterday I flashed again nAOSProm-8.1.0-b11-nozomi.zip, and this time I didn't get that annoying bug related to the phone app. Why? Well, there are two possible reasons:
1) This time I Flashed TWRP the way you tell in your guide. I used to do it via Flashtool.
2) I have used Nano Gapps instead of Pico Gapps.
Another thing I would like to tell you, is that yesterday it was impossible for me to flash the rom with the official TWRP (the one you recommend). I had to use TWRP 3.2.3, the version the developer of this rom recommends. It is something I don't understand: Why does the official TWRP work for you, while it doesn't for me?
Thank you very much again for all your help. I am pretty much interested in bringing to life again this old phone. What I really like about Xperia S is its small size
Now I am going to try to flash the rom again, because, although it works correctly, I cannot reboot into recovery
Cheers!

TXUTXI72 said:
Hi again! Thanks for answering.
First of all, 2.3.7 was not the last firmware for Sony xperia s, but the first one. The last one was Jelly Bean (4.1.2, or something like that, as far as I remember). So I am confused by your answer.
Secondly, yesterday I flashed again nAOSProm-8.1.0-b11-nozomi.zip, and this time I didn't get that annoying bug related to the phone app. Why? Well, there are two possible reasons:
1) This time I Flashed TWRP the way you tell in your guide. I used to do it via Flashtool.
2) I have used Nano Gapps instead Pico Gapps.
Another thing I would like to tell you, is that yesterday it was impossible for me to flash the rom with the official TWRP (the one you recommend). I had to use TWRP 3.2.3, the version the developer of this rom recommends. It is something I don't understand: Why does the official TWRP work for you, while it doesn't for me?
Thank you very much again for all your help. I am pretty much interested in bringing to life again this old phone. What I really like about Xperia S is its small size
Now I am going to try to flash the rom again, because, although it works correctly, I cannot reboot into recovery
Cheers!
Click to expand...
Click to collapse
Hi,
Sorry for my late replay.
Sorry for the 2.3.7 version. When i tried to force updates nothing came out so I thought it was the last one. I will remove comments on version.
For the Recovery, everything went fin with latest version. However, with 3.4+ TWRP, every time you wipe a partition you must reboot recovery before flashing.
I'll put a comment for those who have problems flashing.
And now I must add the Magisk tuto.

djibe89 said:
Hi,
Sorry for my late replay.
Sorry for the 2.3.7 version. When i tried to force updates nothing came out so I thought it was the last one. I will remove comments on version.
For the Recovery, everything went fin with latest version. However, with 3.4+ TWRP, every time you wipe a partition you must reboot recovery before flashing.
I'll put a comment for those who have problems flashing.
And now I must add the Magisk tuto.
Click to expand...
Click to collapse
Flashing Rom and Gapps over adb gives an insufficient space error. I first install Rom and then install Gapps.

Hi @haktug,
did you repartition correctly ? The partition should be ultra wide after repart

after writing the partition layout and formating /data and /cash the only i get whatever i try to do is "Unable to mount storage". SDCard partition is marked as no present and on "Select Storage" button the only i get is "SDCard (0MB)". and that lets me do NOTHING at all. i tryied everithing i cant get over it, dispite my every step in this guide were presice... please somebody help...

djibe89 said:
Hi @haktug,
did you repartition correctly ? The partition should be ultra wide after repart
Click to expand...
Click to collapse
yes ı did

bkokkinos said:
after writing the partition layout and formating /data and /cash the only i get whatever i try to do is "Unable to mount storage". SDCard partition is marked as no present and on "Select Storage" button the only i get is "SDCard (0MB)". and that lets me do NOTHING at all. i tryied everithing i cant get over it, dispite my every step in this guide were presice... please somebody help...
Click to expand...
Click to collapse
which version of twrp are you using?

haktug said:
which version of twrp are you using?
Click to expand...
Click to collapse
the one you provide ... 3.5.0.9.0 i think it is
i made the procedure multiple times and i formated many times both /data and /cashe and i return to my previous layout installed a random rom and tryied this repartition again with the same results....
unable to mount storage
SDCard (0MB)
on advanced wipe >SDCard >change file system > Present:No

@bkokkinos Can you send the log form the command
Code:
fdisk -l /dev/block/mmcblk0

bkokkinos said:
the one you provide ... 3.5.0.9.0 i think it is
i made the procedure multiple times and i formated many times both /data and /cashe and i return to my previous layout installed a random rom and tryied this repartition again with the same results....
unable to mount storage
SDCard (0MB)
on advanced wipe >SDCard >change file system > Present:No
Click to expand...
Click to collapse
you should use twrp 3.2.3 on this link.
Downloads for : Sony Xperia S | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

haktug said:
you should use twrp 3.2.3 on this link.
Downloads for : Sony Xperia S | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Click to expand...
Click to collapse
WWWOOOOOOOOOOOOOOOOOWWWWWWWWWWW!!!!!!!!!!!!!
What did you do......????????!!!!
i just flashed twpr 3.2.3 and everything worked perfectly....!!!! How could just different version make such differance???? OOOUUUFFFFFF i can't believe it... my two days headache is gone... THANK YOU Very Much!!!

Hi, I updated tutorial thanks to both of you.

Thanks t
djibe89 said:
Hi, I updated tutorial thanks to both of you.
Click to expand...
Click to collapse
Thanks to you!

Hello,
Good day! I was stuck at step 13) INSTALL ROM AND GOOGLE APPS
It says,
"Updater process ended with ERROR: 7 error installing zip file 'sideload/nAOSProm-81.0-b11-nozomi.zip'
Failed to mount '/system' ".
I used TWRP 3.2.3-0.
Thank you...

l3mu3l said:
Hello,
Good day! I was stuck at step 13) INSTALL ROM AND GOOGLE APPS
It says,
"Updater process ended with ERROR: 7 error installing zip file 'sideload/nAOSProm-81.0-b11-nozomi.zip'
Failed to mount '/system' ".
I used TWRP 3.2.3-0.
Thank you...
Click to expand...
Click to collapse
I don't know if I can really help you, but I would recommend you to use the links provided by the author of the rom himself. For instance, the author of this rom says clearly to use the following link in order to get the proper TWRP version: https://androidfilehost.com/?fid=1322778262904003720
Another important thing is in my opinion that the permanent twrp must be flashed into the fota partition, not in the boot partition. In my case, everytime I flashed it into the boot partition, the device always rebooted into system and not into twrp.
And very important as well is to check if the repartition has been made correctly. Check out that the sd has about 28 gigabytes free after doing the repartition.

l3mu3l said:
Hello,
Good day! I was stuck at step 13) INSTALL ROM AND GOOGLE APPS
It says,
"Updater process ended with ERROR: 7 error installing zip file 'sideload/nAOSProm-81.0-b11-nozomi.zip'
Failed to mount '/system' ".
I used TWRP 3.2.3-0.
Thank you...
Click to expand...
Click to collapse
By the way, I have just read someone who was getting error 7 while trying to install the rom, and he warns: MAKE SURE YOU DON'T CHANGE SYSTEM PARTITION INTO F2FS. Only Data and cache partitions must be changed into f2fs. Just in case it may help you...

TXUTXI72 said:
I don't know if I can really help you, but I would recommend you to use the links provided by the author of the rom himself. For instance, the author of this rom says clearly to use the following link in order to get the proper TWRP version: https://androidfilehost.com/?fid=1322778262904003720
Another important thing is in my opinion that the permanent twrp must be flashed into the fota partition, not in the boot partition. In my case, everytime I flashed it into the boot partition, the device always rebooted into system and not into twrp.
And very important as well is to check if the repartition has been made correctly. Check out that the sd has about 28 gigabytes free after doing the repartition.
Click to expand...
Click to collapse
ı agree. if it doesn't work, you're doing it wrong somewhere. You should do it again