This is compatible with a wide variety of Xperia Devices
A guide bought to you by matt4321 and DaRk-L0rD
Here I am going to show you how to get the boot.img (kernel) out of an FTF! This procedure is most useful for Locked Bootloaders as it means we can upgrade without the need for FlashTool!
This guide assumes that you have FlashTool installed on your PC
#############################
Step 1:
You need a file extractor such as WinRar or 7zip.
Once this is done you want to open the whole FTF in the extractor. You will see a lot of .sin files!
The one we want is 'kernel.sin', not 'fotakernel.sin'.
Extract that file to somewhere appropriate on your computer, like the desktop!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#############################
Step 2:
Now you need to open FlashTool,
At the top you will see a tab that says 'Tools', click on that and select 'SIN Editor'. You will see a button that has 3 dots in the top right. This is the browse button, click on it and locate where your SIN file is.
One that is done, you need to click on 'Dump Data'.
This will dump the 'kernel.elf' to the same location of where your 'kernel.sin' is.
#############################
Step 3:
The next part is simple,
All you need to do is rename your 'kernel.elf' to 'boot.img' and put it in a flashable zip, to make the flashable zip follow the instructions by @DaRk-L0rD in the 2nd post!
Keep in mind that the kernel should be 20mb.
#############################
Step 4:
Enjoy! The kernel can be flashed via PhilZ for Locked Bootloaders and will work on both Locked and Unlocked bootloaders, since it is an official kernel it is signed by the Sony key so will be fine for Locked Bootloaders.
If you want to make a kernel's flashable zip
What you need:
1. winrar
2. Notepad++
3. The attachment: View attachment META-INF.rar
4. boot.img or kernel.elf
Procedure:
1. Extract the META-INF folder from the rar archive previously downloaded.
2. Open it and go META-INF -> google -> android and using Notepad++ edit the updater-script (right click on it and choose open with Notepad++).
3. Now you can see that the updater-script looks like this:
4. The line package_extract_file("boot.img", "/dev/block/mmcblkXXX"); should be edited ONLY for 2 reasons.
In case you have a kernel.elf (custom kernels) instead of a boot.img
To edit the mmcblkXXX partition since it's different for each device
5. At the end of this post you will find a list of the /mmcblkXXX . For each device are different to choose wisely!!
In my case is the /mmcblk0p4, so will look like this:
6. ui_print(""); , inside the " " you can add the text what you want. Remember that all the users will use this zip will be able to see what you wrote, so please be polite
For example:
ui_print("Installing the kernel");
ui_print("matt4321");
ui_print("DaRk-L0rD");
ui_print("");
package_extract_file("boot.img", "/dev/block/mmcblk0p4");
ui_print("Enjoy");
ui_print("Hit the thanks button");
Click to expand...
Click to collapse
----------------In case the kernel's format is kernel.elf, you can change the line and make it look like this: ----------------
package_extract_file("kernel.elf", "/dev/block/mmcblk0p4"); (as i said you before, the partition is my case is mmcblk0p4)
Also, make sure that you leave an empty line at the end of the commands (as you can see the line number 8 is empty).
6. Now select the META-INF folder and the boot.img or the kernel.elf file, right click on them and select Add to archive.
7. Make sure that the Archive format is ZIP and the Compression method is Store
8. Now your flashable zip is ready!
9. Enjoy
List of /mmcblkXXX
Each device has different partition for the kernel. Here is a list of those we found so far:
Xperia SP ---- /dev/block/mmcblk0p4
Xperia T---- /dev/block/mmcblk0p4
Xperia V---- /dev/block/mmcblk0p4
Xperia TX---- /dev/block/mmcblk0p4
Xperia Z1---- /dev/block/mmcblk0p14
Xperia E---- /dev/block/mmcblk0p3
Xperia Tipo---- /dev/block/mmcblk0p3
Xperia S---- /dev/block/mmcblk0p3
Xperia Ion---- /dev/block/mmcblk0p3
Since we don't know all devices' partition, you should give us a hand.
Here is what you have to do:
Procedure:
via adb shell
ls -l /dev/block/platform/
Click to expand...
Click to collapse
then pick the top one (in my case is msm_sdcc.1), so
ls -l /dev/block/platform/msm_sdcc.1/by-name
Click to expand...
Click to collapse
Then which ever says 'kernel' is the one we want.
On portal
Congrats you 2
Took much of wrong/incorrect/partial info in this thread...
DooMLoRD said:
Took much of wrong/incorrect/partial info in this thread...
Click to expand...
Click to collapse
Could you give us a hand with the right/correct/total mate?
We tested all this in different Xperia devices and never had issues and that's why we made the tutorial.
DooMLoRD said:
Took much of wrong/incorrect/partial info in this thread...
Click to expand...
Click to collapse
Reiterating what DaRk-L0rD said, what can we change/how can we make it better?
Sent from my LT30p using Tapatalk
DaRk-L0rD said:
Could you give us a hand with the right/correct/total mate?
We tested all this in different Xperia devices and never had issues and that's why we made the tutorial.
Click to expand...
Click to collapse
matt4321 said:
Reiterating what DaRk-L0rD said, what can we change/how can we make it better?
Sent from my LT30p using Tapatalk
Click to expand...
Click to collapse
btw you can still use with this script :
Code:
package_extract_file("kernel.elf", "/dev/block/platform/msm_sdcc.1/by-name/Kernel");
Code:
package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/Kernel");
you don't need to change compressed zip to store, normal is work
For a long time since Xperia X10, I think we can't flash kernel using an update package to flash in CWM?
This guide is very simple and very interesting, especially for locked bootloader users, but with just "rename" it would not cause a very high risk? ...
sorry with my question (just want to make sure ), because I know about kernel on Xperia devices that are quite complicated (unlike the Galaxy device)
btw, thank for the very simple guide, this is very useful, especially for my rom
ibanez7 said:
This guide is very simple and very interesting, especially for locked bootloader users, but with just "rename" it would not cause a very high risk? ...
sorry with my question (just want to make sure ), because I know about kernel on Xperia devices that are quite complicated (unlike the Galaxy device)
btw, thank for the very simple guide, this is very useful, especially for my rom
Click to expand...
Click to collapse
It's the method I have used for countless firmwares on the T, have done it for the V and TX as well. renaming it isn't totally necessary afaik, people are just more comfortable with the thought of a boot.img rather than a kernel.elf
New possibilities
Will this open up the possibility of upgrading android beyond 4.1.2 on locked bootloader on Xperia S and Ion?
osamaanjum said:
Will this open up the possibility of upgrading android beyond 4.1.2 on locked bootloader on Xperia S and Ion?
Click to expand...
Click to collapse
I don't think so, as it's just a method of flashing a stock kernel via recovery instead of using Flashtool. It will not allow modified/custom kernels to run on a device with a locked bootloader.
Sent from my C6603 using Tapatalk
osamaanjum said:
Will this open up the possibility of upgrading android beyond 4.1.2 on locked bootloader on Xperia S and Ion?
Click to expand...
Click to collapse
It just allows locked bootloaders to flash a kernel via a locked bootloader recovery. It helps for people to update without the need for flashtool
Sent from my LT30p using Tapatalk
When you update kernel, I think you have to update rpm too.
rpm is proprietary firmware file to be added to the kernel.
Code:
package_extract_file("rpm.elf", "/dev/block/platform/msm_sdcc.1/by-name/rpm");
Can you tell me what is the partition layout of 2011 device such as xperia mini. /dev/block/mmcblk???
no /dev/block/platform folder (xperia z)
where gonna help a bit by finding info fo SGP321 (xperia tablet z) but as title says I could not find the listed folder
Edit:
I found it but this is what I get
[email protected]:/dev/block/platform/msm_sdcc.1 $ ls -l /dev/block/platform/msm_sdcc
.1/by-name
/platform/msm_sdcc.1/by-name <
lrwxrwxrwx root root 2014-06-08 20:48 B2B -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2014-06-08 20:48 FOTAKernel -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2014-06-08 20:48 LTALabel -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-06-08 20:48 TA -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-06-08 20:48 aboot -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-06-08 20:48 alt_aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-06-08 20:48 alt_rpm -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-06-08 20:48 alt_s1sbl2 -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-06-08 20:48 alt_sbl1 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-06-08 20:48 alt_sbl2 -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-06-08 20:48 alt_sbl3 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-06-08 20:48 alt_tz -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2014-06-08 20:48 apps_log -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2014-06-08 20:48 boot -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-06-08 20:48 cache -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2014-06-08 20:48 m9kefs1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2014-06-08 20:48 m9kefs2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-06-08 20:48 m9kefs3 -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-06-08 20:48 ramdump -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-06-08 20:48 rpm -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-06-08 20:48 s1sbl2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-06-08 20:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-06-08 20:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-06-08 20:48 sbl3 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-06-08 20:48 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2014-06-08 20:48 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-06-08 20:48 userdata -> /dev/block/mmcblk0p27
i extracted the kernel.sin from Sony xperia z 4.4.4 ftf and using flashtool to dum data and renamed .elf to Boot.img but its only 7.86 mb ??????? while trying to cook a rom with Android kitchen , Android kitchen gives me an error that android magic header not found at start of boot.img and then a warning Android header not found in boot.img ( Unsupported format ) any idea what is going on ?
---------- Post added at 06:38 AM ---------- Previous post was at 06:04 AM ----------
Fota kernel is the kernel that you mentioned in ?? if no than i do not see any kernel listed here in adb shell.
if yes then here you can it add in the op.
Sony Xperia Z (C6603)
FOTAKernel -> /dev/block/mmcb1k0p23
ls -l /dev/block/platform/
then pick the top one (in my case is msm_sdcc.1), so
Quote:
ls -l /dev/block/platform/msm_sdcc.1/by-name
Then which ever says 'kernel' is the one we want. ???
In recent Xperia devices, kernel partition is called boot.
For android 4.4+ boot.img should b below 9 mb and its the correct one..So if u don't get a 20 mb sized boot.img means don't afraid. Just go ahead.
Epic guide man! You just saved some time for me with this guide!
That's me when I was searching for elf2img software on google and then I found your thread. xD
Related
The partition layout of the SGS3 is the following:
/dev/block/mmcblk0p9 /system ext4
/dev/block/mmcblk0p12 /data ext4
/dev/block/mmcblk0p8 /cache ext4
/dev/block/mmcblk0p3 /efs ext4
So, backing up efs with adb is easy:
'adb shell'
'dd if=/dev/block/mmcblk0p3 of=/sdcard/efsbackup.img'
'exit'
'adb pull /sdcard/efsbackup.img'
And there you go.
Restoring it is nearly the same process, but *surprise* reversed.
Only restore your efs partition if it's absolutely necessary. Yes, there is only a 0.01% chance of corrupting your efs partition/backup while doing the backup or restore but I won't be able to help you if you corrupt your backup or partition. You've been warned.
The usual disclaimer applies here: I nor XDA-developers.com are responsible for any damage you do to your phone.
But if you must know:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
And if you want to be absolutely sure there's no garbage left on your efs partition prior to restoring it:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/dev/zero of=/dev/block/mmcblk0p3'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
But, and yes this is a major problem. Adb shell isn't functioning properly on our SGS3. As I mentioned in this thread, you can only use one adb shell command per cmd window. If you want to do two things in adb shell, you'll have to open a new command prompt and enter the second command which isn't a huge disaster but it's quite annoying, especially if you've got some heavy duty shell work.
you can also use this for EFS Folder Backup
http://forum.xda-developers.com/showthread.php?t=1308546
Test:
http://translate.google.com/transla...sa=X&tbo=1&tbas=0&biw=1680&bih=925&prmd=imvns
I wonder if there are any information about other partitions? There are suppose to be 12 partitions. I only know the purpose of a couple of them.
Below is what I can find so far.
/dev/block/mmcblk0p1 - unknown
/dev/block/mmcblk0p2 - unknown
/dev/block/mmcblk0p3 - /efs
/dev/block/mmcblk0p4 - unknown
/dev/block/mmcblk0p5 - kernel
/dev/block/mmcblk0p6 - recovery
/dev/block/mmcblk0p7 - unknown
/dev/block/mmcblk0p8 - /cache
/dev/block/mmcblk0p9 - /system
/dev/block/mmcblk0p10 - unknown
/dev/block/mmcblk0p11 - unknown
/dev/block/mmcblk0p12 - /data
Supposing some of the unknown ones are bootloader related.
what partition is for modem?
Thx.
thanks to both of you guys for posting this! i was wondering what the partition layout looked like. now i'm ready to start tweaking even if we don't get root for US versions day1. this is unlikely, though.
Samsung Galaxy S3 I9300 Full Partition Layout
This should fill in the "blanks". From my system dump yesterday when I was searching for the modem (radio) partition. Check my guide in the sig
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's great information! The only remaining question is the mapping of sboot.bin and tz.img. I often see these two partitions in many ROMs. It seems likely that these are the first 2 partitions.
Thijs96 said:
.............But if you must know:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
And if you want to be absolutely sure there's no garbage left on your efs partition prior to restoring it:
'adb push efsbackup.img /sdcard/efsbackup.img'
'adb shell'
'dd if=/dev/zero of=/dev/block/mmcblk0p3'
'dd if=/sdcard/efsbackup.img of=/dev/mmcblk0p3'
'exit'
.........
Click to expand...
Click to collapse
Hey, why are the /block/ parts missing in some lines of code? looks like an error, isn't it? It should always be /dev/block/mmcblk0p3 if I'm not wrong
Thanks.
WT Ho said:
That's great information! The only remaining question is the mapping of sboot.bin and tz.img. I often see these two partitions in many ROMs. It seems likely that these are the first 2 partitions.
Click to expand...
Click to collapse
The sboot.bin is stored in the mmcblk0p1 partition. No idea what the tz.img stands for though...
is this info still the exact same info for SPH-L710 (Sprint CDMA) S3 Device?
its running android 4.1.1 stock but im rooted and have CWM installed
en11gma said:
is this info still the exact same info for SPH-L710 (Sprint CDMA) S3 Device?
its running android 4.1.1 stock but im rooted and have CWM installed
Click to expand...
Click to collapse
Have a look here http://forum.xda-developers.com/showthread.php?t=1959445
Perka said:
Have a look here http://forum.xda-developers.com/showthread.php?t=1959445
Click to expand...
Click to collapse
i did a search there for sph-l710 (my model and nothing came up)
i dont think that thread was for this phone so i guess the question remains.
is the partition tables in the (1st page) not just the first post correct for SPH-L710?
WT Ho said:
I wonder if there are any information about other partitions? There are suppose to be 12 partitions. I only know the purpose of a couple of them.
Below is what I can find so far.
/dev/block/mmcblk0p1 - unknown
/dev/block/mmcblk0p2 - unknown
/dev/block/mmcblk0p3 - /efs
/dev/block/mmcblk0p4 - unknown
/dev/block/mmcblk0p5 - kernel
/dev/block/mmcblk0p6 - recovery
/dev/block/mmcblk0p7 - unknown
/dev/block/mmcblk0p8 - /cache
/dev/block/mmcblk0p9 - /system
/dev/block/mmcblk0p10 - unknown
/dev/block/mmcblk0p11 - unknown
/dev/block/mmcblk0p12 - /data
Supposing some of the unknown ones are bootloader related.
Click to expand...
Click to collapse
odia gives this to restore bootloaders
# dd if=/sdcard/sboot.bin of=/dev/block/mmcblk0p1
# dd if=/sdcard/tz.img of=/dev/block/mmcblk0p2
# dd if=/sdcard/param.bin of=/dev/block/mmcblk0p4
so 1 = bootloader
2= tz
3= param
en11gma said:
i did a search there for sph-l710 (my model and nothing came up)
i dont think that thread was for this phone so i guess the question remains.
is the partition tables in the (1st page) not just the first post correct for SPH-L710?
Click to expand...
Click to collapse
well maybe you can use the commands to find your table?
in adb type:
mount
Sorry for bumping this thread but nothing is working for me. I've tried the EFS pro backup tool and only get "connecting to device" for hours. So I saw this thread and thought manually doing it would work fine, and I get "permission denied".
I'm on a rooted, US variant, the SPH-L710. Even backing up the MSL has posed problems, so idk what is going on. Please help. I've been searching the site for 2 days and came up with tons of threads that just do not work.
Now if only we could resize these partitions!
Sent from my GT-I9300 using Tapatalk
AzzidReign said:
Sorry for bumping this thread but nothing is working for me. I've tried the EFS pro backup tool and only get "connecting to device" for hours. So I saw this thread and thought manually doing it would work fine, and I get "permission denied".
I'm on a rooted, US variant, the SPH-L710. Even backing up the MSL has posed problems, so idk what is going on. Please help. I've been searching the site for 2 days and came up with tons of threads that just do not work.
Click to expand...
Click to collapse
AS this is not your phones forum i suggest you ask in your phones forum as there are significant differences in the hardware .
The I9300 stickys have a network EFS IMEI thread if you want to read that but any I9300 firmware or fixes may brick a different phone .
OH1 partitions
Thought I should post the latest partition for OH1 firmware (Stagefright BUG FIX firmware)
[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name/
lrwxrwxrwx root root 2013-12-31 23:48 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2013-12-31 23:48 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2013-12-31 23:48 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2013-12-31 23:48 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2013-12-31 23:48 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2013-12-31 23:48 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2013-12-31 23:48 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2013-12-31 23:48 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2013-12-31 23:48 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2013-12-31 23:48 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2013-12-31 23:48 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2013-12-31 23:48 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2013-12-31 23:48 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2013-12-31 23:48 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2013-12-31 23:48 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2013-12-31 23:48 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2013-12-31 23:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2013-12-31 23:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2013-12-31 23:48 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2013-12-31 23:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2013-12-31 23:48 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2013-12-31 23:48 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2013-12-31 23:48 userdata -> /dev/block/mmcblk0p15
So here we are
Its officialy confirmed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cant wait to create a rom / kernel for This Beast
Who has received it
Itsnot reciveable , just spam them tell them that htc dev didnt publish it yet
Just copy and paste this to them ,, they should know their ota system sucks
We need a download link for HTC desire 820s Dual Sim Software Version 1.14.709.1 Sense 7 , Lolipop 5.0.2 Build as itsn't recievable as OTA " we didn't and will never recive it as kk users " it only come out of the box by luck.
Please publish it . we are stuck at kitkat
There's no way they can send lollipop and Sense 7 OTA. That's about 4 GBs!!!!
---------- Post added at 04:07 PM ---------- Previous post was at 04:04 PM ----------
I've been spamming them the entire week. They are too reluctant to give the source code or OTA
I think going to get refund and reppace this device
Mohamed Yaser said:
I think going to get refund and reppace this device
Click to expand...
Click to collapse
Let me be patient until December
What about battery ,charging 6% / Hour ??
Too slow?
Wait a minute. Isn't a50mldtul desire 820s?
where u got that from
http://www.droidviews.com/list-of-android-device-codenames/
Yeah it is
i think also we are getting a recovery soon
[email protected]_a50ml_dtul:/ $ su
/platform/mtk-msdc.0"This is our chip"/by-name <
lrwxrwxrwx root root 2015-07-08 00:46 boot -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-07-08 00:46 cache -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-07-08 00:46 cota -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-07-08 00:46 dkb -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-07-08 00:46 expdb -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-07-08 00:46 flashinfo -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2015-07-08 00:46 kb -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-07-08 00:46 lk -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-07-08 00:46 logo -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-07-08 00:46 metadata -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-07-08 00:46 nvram -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-07-08 00:46 para -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-07-08 00:46 proinfo -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-07-08 00:46 protect1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-07-08 00:46 protect2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-07-08 00:46 recovery -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-07-08 00:46 seccfg -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-07-08 00:46 secro -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-07-08 00:46 system -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-07-08 00:46 tee1 -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-07-08 00:46 tee2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-07-08 00:46 userdata -> /dev/block/mmcblk0p21
[email protected]_a50ml_dtul:/ #
http://forum.xda-developers.com/desire-820/orig-development/desire-820-models-msm-chipset-twrp-2-8-t3147260/page4
http://forum.xda-developers.com/des...20-models-msm-chipset-twrp-2-8-t3147260/page4
The kernel source code for a50mldtul is at htcdev
There's this one I flashed. Seems to be working fine. It can backup. Haven't tried restoring or installing zip though.
CWM
Isn't this the greatest breakthrough for our phone
Oh , May be i will start work on a rom
PS ,, Give me a link to our source code and How u did unlock the bl
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Gibz97 said:
I'm not sure how I unlocked it. I remember trying to unlock it at htcdev.com and using kingo htc bootloader unlock but I wasn't successfull. I don't know maybe it's still locked.
At htcdev there are kernel source codes with a50mldtul name under Desire 820 dual sim. But again I'm not if sure they are for Desire 820s.
You can get the CWM I flashed here
http://www.4shared.com/rar/SM6wcBzyce/CWM_820s.html
It's fully working for me
Click to expand...
Click to collapse
who made this cwm
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Mohamed Yaser said:
who made this cwm
Click to expand...
Click to collapse
Have you tried it?
Gibz97 said:
I found it here
http://forum.xda-developers.com/and...6732-64bit-t2998980/post61761125#post61761125
Pretty old thread
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Have you tried it?
Click to expand...
Click to collapse
i didn't find the kernel source ??
no not yet
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
noobpremium said:
I am currently running CM 12.1
(Used CM13 with RazorKernel For some days which had a bootlogo)
Here's the partition info of our device
Code:
lrwxrwxrwx root root 2016-01-11 17:56 DDR -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2016-01-11 17:56 aboot -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2016-01-11 17:56 abootbak -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2016-01-11 17:56 boot -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 2016-01-11 17:56 cache -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 2016-01-11 17:56 config -> /dev/block/mmcblk0p28
lrwxrwxrwx root root 2016-01-11 17:56 fsc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2016-01-11 17:56 fsg -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2016-01-11 17:56 hyp -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2016-01-11 17:56 hypbak -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2016-01-11 17:56 keystore -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 2016-01-11 17:56 misc -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2016-01-11 17:56 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2016-01-11 17:56 modemst1 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2016-01-11 17:56 modemst2 -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2016-01-11 17:56 oem -> /dev/block/mmcblk0p29
lrwxrwxrwx root root 2016-01-11 17:56 pad -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2016-01-11 17:56 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 2016-01-11 17:56 recovery -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 2016-01-11 17:56 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2016-01-11 17:56 rpmbak -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2016-01-11 17:56 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2016-01-11 17:56 sbl1bak -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2016-01-11 17:56 sec -> /dev/block/mmcblk0p21
[COLOR="Red"]lrwxrwxrwx root root 2016-01-11 17:56 splash -> /dev/block/mmcblk0p18[/COLOR]
lrwxrwxrwx root root 2016-01-11 17:56 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2016-01-11 17:56 system -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 2016-01-11 17:56 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2016-01-11 17:56 tzbak -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2016-01-11 17:56 userdata -> /dev/block/mmcblk0p30
As you can see "mmcblk0p18" belongs to splash partiton.
I was successful in dumping splash.img on sdcard with adb shell as:
Code:
dd if=/dev/block/mmcblkp018 of=/storage/sdcard1/splash.img
But now what?
How to edit it?
I've searched for many hours but came up with mediatek or HTC guides which is pretty annoying -_-
Tools I've tried so far--> Android Kitchen, Kernel Kitchen, Logo Builder, nbimg tool.
Please help me through this.. I desperately want to make a splash image for my device.
Click to expand...
Click to collapse
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
I want to modify bootsplash too but im soo noob to do that,
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
nick37332001 said:
Which splash? Mi Logo splash? Tux Logo splash? Razor kernel splash I assume? If its Tux Logo splash, it is needed for some LCD types to work. For Mi Logo / Razor kernel splash I think, you must edit in kernel level and compile the kernel yourself.
Click to expand...
Click to collapse
Damn I dont have time to download sources and compile the kernel myself
Any other method to edit?
And yes its razor kernel splash (which is that blue thing ) or The Mi logo splash which appears before bootanimation.
But the thing is razor kernel had its splash and Kuma's cm12.1 dont!
Just that default "Linux's Penguin" appears in corner :3
Hope you got what I wanted to say
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
ketut.kumajaya said:
Never tried by myself, as your reference, try it at your own risk: https://www.codeaurora.org/cgit/quic/la/device/qcom/common/tree/display/logo?h=LA.BR.1.2.7_rb1.1
Click to expand...
Click to collapse
Too bad but I romoved ubuntu from pc just 2 dyas ago.. one more reason to regret -_-
maybe nick can do it :3
BTW any other method to do it? Like using cygwin?
noobpremium said:
Okay Thanks for the reply. That's from kernel source I assume.
However I'll see to it
Click to expand...
Click to collapse
Have you tried the latest version? I think kiran removed the logo
nick37332001 said:
Have you tried the latest version? I think kiran removed the logo
Click to expand...
Click to collapse
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
noobpremium said:
I dont want to flash CM13 now. I'm on 12.1.
Leave razorkernel. I'm not talking about 'only' razorkernel. If he is able to do so others should be too and for defferent kernel.
I've seen threads for bootlogo for motoX etc running lollipop
Anyways, do you have ubuntu? so you can run the script Kuma gave us link of.
Click to expand...
Click to collapse
the script is python so you should be able to run it on windows.
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay I'm nooob man. I didn't know that i can run it on windows, but I'll see to it.
Sent from my 2014818 using Tapatalk
nick37332001 said:
the script is python so you should be able to run it on windows.
Click to expand...
Click to collapse
Okay now here I am, successfully running that script on windows.
It created splash.img successfully but it was too small in size, around 65 KB :|
The one that i dumped was exactly 10MB.
Then also I flashed it but what I got was dessorted Mi logo and the same Penguin.
Now what? I'll see if I can decompile splash.img that I dumped using PIL.
Any help will be appreciated
Sent from my 2014818 using Tapatalk
You can give a try with Android Image Kitchen.....
Lennoard said:
You can give a try with Android Image Kitchen.....
Click to expand...
Click to collapse
Okay I'll see
Sent from my Xiaomi Redmi 2
noobpremium said:
Okay I'll see
Sent from my Xiaomi Redmi 2
Click to expand...
Click to collapse
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
KonradIC13 said:
Sorry for digging up old thread but how did it go? Did you manage to change default splashscreen?
What ive done myself so far was use X-Plore app with SuperSU access to copy splash file from /root/dev/block/bootdevice/by-name to external SD. In X-Plore splash file was 0b but upon copy it was 10MB.
Then i tried to use tool from other topic nbimg to convert splashscreen from 'unknown' format to BMP but result was bad. The tool is supposed to identify image resolution but it didnt know how in Redmi case (tool was orignally designed for HTC device i think) so i tried using w1280 h720 argument but result was like below:
http://i.imgur.com/sxYl65J.png
Well then i timply took any 720x720 image and used that nbimg tool to convert it to splash and then tried to replace it in /root/dev/block/bootdevice/by-name but on reboot it was reverted back to original
Click to expand...
Click to collapse
No problem for digging old thread.
I did all the things exactly as what you did and had same results.
I still desperately want to make bootlogos for our belowed wt88047 but I just can't @ketut.kumajaya please just one hint for us and we will figure out rest.
I tried that python script on windows too but same broken splash.
Sent from my 2014818 using Tapatalk
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
GokulNC said:
@noobpremium @KonradIC13
[GUIDE] How to Create Custom Splash Screen (Boot Logo) for Redmi 2
No need to edit kernel.. The kernel has the logo that displays after Mi Boot Logo..
The boot logo (splash screen) is present in a separate partition..
Click to expand...
Click to collapse
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
TWRP for backing up splash
noobpremium said:
What did you do exactly?
I'll have a look at your stuff and try it right now.
Seems you posted the thread just a while ago.
Sent from my 2014818 using Tapatalk
Click to expand...
Click to collapse
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
shanx_verma said:
Can I try the batman logo.bin file inside the zip I pointed you to, through this method?
Also, will taking a Backup through recovery work for this, or do I have to flash the whole fastbot ROM if this fails?
.
P.S - Found this, but am reluctant to try, as I have office in an hour. [emoji14] [emoji14] (Will it work if I have MM 6.0.1 installed as Primary ROM? As is says for KK in that thread)
http://en.miui.com/thread-114090-1-1.html
EDIT - Or will this be more relevant -
http://en.miui.com/thread-249552-1-1.html
Click to expand...
Click to collapse
Just use his tool no need of any flashable zip or something.
Sorry I didn't get time for your batman logo. I'll try tonight.
Btw, you can make your logo easily with that tool.
After it's compiled, flash is with terminal emulator or just fastboot command
"fastboot flash splash splash.img" and done.
Sent from my 2014818 using Tapatalk
This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Do a nandroid backup from the recovery
Nortabun said:
This might seem like a newbie question but this isn't the case.
I already know Titanium backup exists and I have been using it for years. However a few months back I suffered from the ''infamous brick'' seen everywhere on this thread caused by the unofficial CM13 ROM.
This brick corrupted everything on my phone (EFS Partition, etc) and the ONLY thing i could ever boot into was the recovery.
2 months and $150 later in repairs (literally everyone failed to fix it software-side) I learned my lesson
I need to back up my entire phone incase something like this happens again. What app should I use, and what should I back up?
Thanks
Click to expand...
Click to collapse
Here is a snapshot of everything on the entire phone.
[email protected]:/dev/block/platform/15540000.dwmmc0/by-name # ls -la
ls -la
lrwxrwxrwx root root 2015-12-31 13:08 BOOT -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-12-31 13:08 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2015-12-31 13:08 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-12-31 13:08 CACHE -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2015-12-31 13:08 CARRIER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-12-31 13:08 CDMA-RADIO -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-12-31 13:08 DNT -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2015-12-31 13:08 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-12-31 13:08 HIDDEN -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2015-12-31 13:08 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-12-31 13:08 PARAM -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-12-31 13:08 PERSDATA -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2015-12-31 13:08 RADIO -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-12-31 13:08 RECOVERY -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-12-31 13:08 RESERVED2 -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2015-12-31 13:08 SYSTEM -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 2015-12-31 13:08 TOMBSTONES -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2015-12-31 13:08 USERDATA -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs1 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs2 -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-12-31 13:08 m9kefs3 -> /dev/block/mmcblk0p6
Option 1 Command line:
Quick and easy way to backup /system
dd if=/dev/block/mmcblk0p18 of=/sdcard/system.img bs=4096
Quick and easy way to backup the kernel
dd if=/dev/block/mmcblk0p9 of=/sdcard/boot.img bs=4096
Quick and easy way to back up EFS
dd if=/dev/block/mmcblk0p3 of=/sdcard/efs.img bs=4096
Quick and easy way to back up Radio
dd if=/dev/block/mmcblk0p13 of=/sdcard/radio.img bs=4096
Quick and easy way to back up Recovery
dd if=/dev/block/mmcblk0p10 of=/sdcard/recovery.img bs=4096
Create a directory on your machine. C:\Phonerecovery
Copy all those files from /sdcard to that directory.
With those images you can build a ODIN flash file
Using Cygwin or a Linux machine: tar -H ustar -c boot.img kernel.img recovery.img system.img > Unf*ckMyNote4.tar
Using ODIN to restore stock firmware usually will unf*ck a CM flashed phone. Keeping one handy from a provider of stock Samsung Note 4 firmware is also a good thing.
Option 2:
Custom recovery like CWM / TWRP installed on your phone
Since you were able to reboot into recovery having a TWRP backup probably would have saved you.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry to ask, im newbie but as far i understand.
Ascend xt got:
Unlockeable bootloader
TWRP
Root
So what is missing for our custom roms?
yunior597 said:
Sorry to ask, im newbie but as far i understand.
Ascend xt got:
Unlockeable bootloader
TWRP
Root
So what is missing for our custom roms?
Click to expand...
Click to collapse
maybe start with a system dump?
Sent from my LGLS676
Sands207 said:
maybe start with a system dump?
Sent from my LGLS676
Click to expand...
Click to collapse
cause its not easy for one or u would of released a rom already 2 we dont have original source code for device so that slows progress 3 if we go to build one we have to modify a source from another device. i tried porting it was fail everytime, but u can always try to make one. pick one you like and port it or build it. im working on lineage atm someone else resurrection remix. and thats all i think
madvane20 said:
cause its not easy for one or u would of released a rom already 2 we dont have original source code for device 3 if we go to build one we have to modify a source from another device i tried porting was fail everytime but u can always try to make one. pick one you like and port it or build it. im working on lineage atm someone else resurrection remix. and thats all i think
Click to expand...
Click to collapse
Start here, get your system dump and create a fresh device tree on github https://forum.xda-developers.com/showthread.php?t=2450045 then you will have a base for cm, rr whatever you choose to build. If you want to build aosp source would be needed I believe or backported but a system dump will literally give you the same files that you would gain from building from source, I just went through this myself. Just trying to help, follow the guide and if you need help with a device tree I could try and help. good luck ?
Sent from my LGLS676
Sands207 said:
Start here, get your system dump and create a fresh device tree on github https://forum.xda-developers.com/showthread.php?t=2450045 then you will have a base for cm, rr whatever you choose to build. If you want to build aosp source would be needed I believe or backported but a system dump will literally give you the same files that you would gain from building from source, I just went through this myself. Just trying to help, follow the guide and if you need help with a device tree I could try and help. good luck
Sent from my LGLS676
Click to expand...
Click to collapse
go for it as u will have noticed if u read the other thread we have dumped the system i have even dumped all partitions. just cause u have the files doesnt mean u can click here and magic full working os comes out. without original source code we have to make changes to the source from a device with similiar hardware. as well as make sure correct paths to files that the other source did not include. this is due to other phones sometimes have different file structures. i dunno bout anyone else but im doing my best and going as fast as i can without just 100% fail. uploading my source i made to build on my server if it boots after i build it good if everything works awesome if not if it boots then i can go through check whats missing
madvane20 said:
go for it as u will have noticed if u read the other thread we have dumped the system i have even dumped all partitions. just cause u have the files doesnt mean u can click here and magic full working os comes out
Click to expand...
Click to collapse
you wanna be rude then figure it out for yourself, was just trying to help you lol
Sent from my LGLS676
Sands207 said:
you wanna be rude then figure it out for yourself, was just trying to help you lol
Sent from my LGLS676
Click to expand...
Click to collapse
wasnt being rude i modified my last post being i was in a hurry and didnt type it out so well. i was just saying man if u know the easy way to make us a rom. go for it alot of people will thank you. if not give us time its not a easy process. also by the way my first time making a rom well building from source i tried to port for about week and a half on windows that didnt work. now im using linux so hope that gives more promising results. as well building it also takes some time why i switched to using my server to compile it uploading files still got 50 gig to go. after i get a wroking one im going to try and fix our twrp to allow for those who want stock to do ota updates from twrp and backup cust and other partitions if feel a need too. hope u dont take this as being rude as it providing info and and letting you know if u can build one then thats awesome. if not give people time heres a list of the partitions
lrwxrwxrwx root root 1969-12-31 21:59 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:59 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:59 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:59 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:59 config -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:59 cust -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:59 erecovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:59 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:59 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:59 hyp -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:59 log -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:59 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:59 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:59 modemst1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:59 modemst2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:59 oeminfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:59 pad -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:59 pad0 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:59 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:59 recovery -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:59 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:59 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:59 sec -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:59 sgb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:59 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:59 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:59 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:59 userdata -> /dev/block/mmcblk0p28
Well, i see, good luck with that. I hope to see a rom in future. Hate all this bloatware and etc.
yunior597 said:
Well, i see, good luck with that. I hope to see a rom in future. Hate all this bloatware and etc.
Click to expand...
Click to collapse
i have a debloated rom however i need to upload a flashable zip that also removes the garbage from cust partition make a guide on how to remove it. or i may just repack the system image i debloated as well make guide to on how to get rid of stuff off there. theres already a guide how to backup and restore the cust as well as posts bout it all i might just make a guide for alot of it and also make a video on step by step rooting etc
madvane20 said:
wasnt being rude i modified my last post being i was in a hurry and didnt type it out so well. i was just saying man if u know the easy way to make us a rom. go for it alot of people will thank you. if not give us time its not a easy process. also by the way my first time making a rom well building from source i tried to port for about week and a half on windows that didnt work. now im using linux so hope that gives more promising results. as well building it also takes some time why i switched to using my server to compile it uploading files still got 50 gig to go. after i get a wroking one im going to try and fix our twrp to allow for those who want stock to do ota updates from twrp and backup cust and other partitions if feel a need too. hope u dont take this as being rude as it providing info and and letting you know if u can build one then thats awesome. if not give people time heres a list of the partitions
lrwxrwxrwx root root 1969-12-31 21:59 DDR -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 21:59 aboot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 21:59 boot -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 21:59 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 21:59 config -> /dev/block/mmcblk0p25
lrwxrwxrwx root root 1969-12-31 21:59 cust -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 21:59 erecovery -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 21:59 fsc -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 21:59 fsg -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 21:59 hyp -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 21:59 log -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 21:59 misc -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 21:59 modem -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 21:59 modemst1 -> /dev/block/mmcblk0p26
lrwxrwxrwx root root 1969-12-31 21:59 modemst2 -> /dev/block/mmcblk0p27
lrwxrwxrwx root root 1969-12-31 21:59 oeminfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 1969-12-31 21:59 pad -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 21:59 pad0 -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 21:59 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 21:59 recovery -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 21:59 rpm -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 21:59 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 21:59 sec -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 21:59 sgb -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 21:59 ssd -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 21:59 system -> /dev/block/mmcblk0p24
lrwxrwxrwx root root 1969-12-31 21:59 tz -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 21:59 userdata -> /dev/block/mmcblk0p28
Click to expand...
Click to collapse
While i appreciate the info and don't worry about it try this at least to get started. Look up @superR's kitchen and take your files, throw down the 10 bucks and get the donate version with plugins, which i can say personally helps a ton or Android Studio maybe? and take what you have and make a ROM that way although the kitchen is like ly the easiest route. You are well on your way! Im passing through and trying to help, tonight ill download the files you have and see what i can piece together if you want but obviously i can't make any promises. Providing info like you did is the way to go ? link me to your files either in a pm or here and ill see what i can do.
Sent from my LGLS676
Sands207 said:
While i appreciate the info and don't worry about it try this at least to get started. Look up @superR's kitchen and take your files, throw down the 10 bucks and get the donate version with plugins, which i can say personally helps a ton or Android Studio maybe? and take what you have and make a ROM that way although the kitchen is like ly the easiest route. You are well on your way! Im passing through and trying to help, tonight ill download the files you have and see what i can piece together if you want but obviously i can't make any promises. Providing info like you did is the way to go link me to your files either in a pm or here and ill see what i can do.
Sent from my LGLS676
Click to expand...
Click to collapse
oh im doing fine free tools im uusing my 16 core 18gv burstable to 30 gb server to compile my builds as go throw to debug
---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------
oh im doing fine free tools im using my 16 core 18 gb burstable to 30 gb server to compile my builds as go throw to debug
madvane20 said:
oh im doing fine free tools im uusing my 16 core 18gv burstable to 30 gb server to compile my builds as go throw to debug
---------- Post added at 05:46 AM ---------- Previous post was at 05:45 AM ----------
oh im doing fine free tools im using my 16 core 18 gb burstable to 30 gb server to compile my builds as go throw to debug
Click to expand...
Click to collapse
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
[/COLOR]
pekcle said:
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
Click to expand...
Click to collapse
Awesome that you found this, Huawei has released the source code. Should be easier to compile a ROM and tweak TWRP now.
In the search box, indeed type Ascend and it comes up from the above link
Awesome! Here's the direct download link if anyone wants to skip the search:
http://download-c1.huawei.com/downl...oadId=90665&version=353730&siteCode=worldwide
pekcle said:
madvane20,
You mentioned earlier that we don't have source code. I checked the Huawei site and found the source code posted. Perhaps Huawei silently posted it without anyone noticing because people stop checking.
H1611 Huawei Ascend XT, Texas-A1(H1611), Android6.0, EMUI4.1
http://consumer.huawei.com/en/opens...Type=openSourceSoftware&pageSize=10&curPage=1
Search for "ascend" and it shows up as the only result. It contains kernel.tar.gz at 168 MB along with a readme.txt on how to build it. I extracted a *.c file to make sure it has real source code, and it sure does.
Perhaps this will help with development. Do you think this is the last piece we need to get it all going? If so, I am ready to go out and buy one!
Thanks for keeping it going.
pekcle
Click to expand...
Click to collapse
yea im extracting it now check some thinks then i will upload or download it with my server im sure i can compile on it alot faster im going to build a twrp on my vm though faster atm then the server cause i have to fix some configs on my server i think
I'll be posting my H1611.STOCK.ROOTED.NOVA.B150.ROM.zip and H1611.B150.Debloated.Rom.zip along with instructions soon
clsA said:
I'll be posting my H1611.STOCK.ROOTED.NOVA.B150.ROM.zip and H1611.B150.Debloated.Rom.zip along with instructions soon
Click to expand...
Click to collapse
i hope to be posting a cooked version of lineage for us now that i have the source it might help me fix bugs that arise
This phone is so sad without custom roms...
yunior597 said:
This phone is so sad without custom roms...
Click to expand...
Click to collapse
It's taking time but it will come. We have a couple devs that are not all that experienced and learning as they go. I'm sure it will be worth the wait.
One thing people forget it's time consuming (especially when you are just learning) and everyone expects it for nothing. The devs do it as a hobby in their free time. If we want an experienced dev and want results, the answer is simple. Get as many people as we can, pool some money together and pay someone with all that knowledge for their time.
Then we would have some custom Roms ASAP... Three XDA members that I know of are working on it and once we have something I hope many of us will donate to thank them for their efforts.
I thought about starting a bounty to collect funds and pay someone. If you really know what you are doing it does not take very long. Say 100 members at $5 a pop, that would get us some pretty good results and what you are asking for
What do you not currently have which you expect to gain from a custom ROM?
yunior597 said:
This phone is so sad without custom roms...
Click to expand...
Click to collapse