Apologies if this is in the wrong forum, I've been away from xda for close to a year...
I managed to get wallet to install and open, but it bails, and logcat indicates an error that there is no secure element.
Does anyone have the special sim with the secure element for ISIS and feel like giving this a try?
Steps:
1. Add com.android.nfc_extras.jar (attached) to /system/framework, chmod to 644
2. Add the signature from the attached nfcee_access.xml.txt to the /system/etc/nfcee_access.xml on your phone
3. Add com.android.nfc_extras.xml (attached as com.android.nfc_extras.xml.txt) to /system/etc/permissions, chmod to 644
4. Reboot the phone
5. Push the region/device free wallet apk to /system/app (can be found here: http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-15-r87-v15/ )
the bits in step 1 and 2 came from http://forum.xda-developers.com/showthread.php?p=32338688 post #9
My phone was able to run wallet, but it got an error:
java.io.IOException: NFC EE failed to open
some digging led me to find that this can happen if you don't have any secure elements.
Well, scrolling back in the logcat, I found this:
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a1c0 (0x51ca5a7c)
01-12 15:51:04.642 1045 1069 D NFCJNI : Open Secure Element
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_Mgt_IoCtl()
01-12 15:51:04.642 1045 1336 D NFCJNI : Callback: > IOCTL successful() - status=0x0000[NFCSTATUS_SUCCESS]
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_SE_GetSecureElementList()
01-12 15:51:04.642 1045 1069 D NFCJNI :
01-12 15:51:04.642 1045 1069 D NFCJNI : > Number of Secure Element(s) : 0
01-12 15:51:04.642 1045 1069 E NFCJNI : phLibNfc_SE_GetSecureElementList(): No SMX detected
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a1c0 (0x51ca5a7c)
So there appears to be no secure element, or the libs have it disabled (haven't found any libs that don't make nfc_service explode).
Does anyone have the isis app working and have the special sim card with a secure element? If so, can you do a logcat and see if Number of Secure Element(s) shows greater than zero?
Would love to get this working
Trying it now I have both sim cards. I may need to replace phone soon though ISIS corrupted my element I think
vilord said:
Apologies if this is in the wrong forum, I've been away from xda for close to a year...
I managed to get wallet to install and open, but it bails, and logcat indicates an error that there is no secure element.
Does anyone have the special sim with the secure element for ISIS and feel like giving this a try?
Steps:
1. Grab the region/device free version of wallet from modaco here: http://www.modaco.com/topic/354635-region-device-root-patched-google-wallet-apk-15-r87-v15/
2. Grab the galaxy s3 wallet rollback package from here: http://forum.xda-developers.com/showthread.php?p=32338688 post #9
3. From the S3 package, push com.android.nfc_extras.jar to /system/framework, chmod to 644
4. From the S3 package, add the signature in system/etc/nfcee_access.xml to the nfcee_access.xml on your phone
5. Push the wallet apk to /system/app
My phone was able to run wallet, but it got an error:
java.io.IOException: NFC EE failed to open
some digging led me to find that this can happen if you don't have any secure elements.
Well, scrolling back in the logcat, I found this:
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Allocated node: 0x5160a1c0 (0x51ca5a7c)
01-12 15:51:04.642 1045 1069 D NFCJNI : Open Secure Element
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_Mgt_IoCtl()
01-12 15:51:04.642 1045 1336 D NFCJNI : Callback: > IOCTL successful() - status=0x0000[NFCSTATUS_SUCCESS]
01-12 15:51:04.642 1045 1069 D NFCJNI : phLibNfc_SE_GetSecureElementList()
01-12 15:51:04.642 1045 1069 D NFCJNI :
01-12 15:51:04.642 1045 1069 D NFCJNI : > Number of Secure Element(s) : 0
01-12 15:51:04.642 1045 1069 E NFCJNI : phLibNfc_SE_GetSecureElementList(): No SMX detected
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a080 (0x51ca5a70)
01-12 15:51:04.642 1045 1069 D NFC_LIST: Deallocating node: 0x5160a1c0 (0x51ca5a7c)
So there appears to be no secure element. Does anyone have the isis app working and have the special sim card with a secure element? If so, can you do a logcat and see if Number of Secure Element(s) shows greater than zero?
Would love to get this working
Click to expand...
Click to collapse
---------- Post added at 09:44 PM ---------- Previous post was at 09:08 PM ----------
JTidler said:
Trying it now I have both sim cards. I may need to replace phone soon though ISIS corrupted my element I think
Click to expand...
Click to collapse
No Luck, I did all as stated no Google Wallet on the phone
Do you have time to look at the logcat?
On our phones, the internal secure element is disabled (and i haven't found any libraries that have it enabled that don't cause the nfc service to blow up)
Google wallet doesn't support sim-based secure elements yet (they're working to fix that now).
What I'm hoping is that it shows "Number of Secure Element(s) : 1" when the sim is in there...
then hopefully with an updated wallet that reads the sim, it will work.
I'd missed a couple of steps, please see the OP for updated steps and the missing preferences file
vilord said:
I'd missed a couple of steps, please see the OP for updated steps and the missing preferences file
Click to expand...
Click to collapse
No luck I tried. Used off market after changing build.prop crashes after "Adding your account"
No luck
How can I get logs?
when connected with usb, with drivers installed (or on a mac/linux box no drivers are needed), with usb debugging enabled, you can run "adb logcat" from your computer. You'll get hundreds of lines of stuff (connecting to network, changing status bar display, screen pressed, etc, etc, but if you page around enough, or if you output it to a file and search it, you should be able to find the section near where google wallet was trying to connect...
-jesse
how did/is this going
Let us rekindle this thread and see how we are doing with this. I also have a rooted ota 4.1.1 Razr M and would love wallet. I have been reading about it and how to get it done for the last few weeks. any progress?
vilord said:
when connected with usb, with drivers installed (or on a mac/linux box no drivers are needed), with usb debugging enabled, you can run "adb logcat" from your computer. You'll get hundreds of lines of stuff (connecting to network, changing status bar display, screen pressed, etc, etc, but if you page around enough, or if you output it to a file and search it, you should be able to find the section near where google wallet was trying to connect...
-jesse
Click to expand...
Click to collapse
If there's anything I can do to help, I'd need some guidance on how logcats and all that work, but I'm a fast learner and I'd be happy to offer my time and effort!
Heads up: once we get working 4.4, we should be able to use wallet assuming NFC doesn't get broken
Sent from my XT907 using Tapatalk
I would like to first start by sharing a bit of history behind this library. @Benjamin Dobell started the Heimdall project where he packet-sniffed the Odin(desktop client)/Loke(on-device server) protocol in order to create Heimdall, an open source flashing tool which I've personally used in my own projects Heimdall one-click and One-Click UnBrick as well as my current project, CASUAL. Heimdall was released with a very rough, but working, analysis of the PIT files and has been slowly increasing over time.
@Ralekdev , @Rebellos and myself began looking at the PIT files much later than Benjamin. Ralekdev and Rebellos were to reverse-engineer the bootloaders of several Samsung devices and was able to come up exploits while I somewhat brought the work together and assisted where I could. Ralekdev even identified proper sizes of data blocks and has created a few tools to assist.
Introduction
I'm happy to announce that we have 100% identification of all parts of the PIT files as they stand today. We are no longer working on identifying variables thanks to Ralekdev, Rebellos and Benjamin's work. We can read, and write and integrate PIT files into our Java Applications. As a demonstration of this library, i encourage you to
Analyze Your Pit File Online
If you don't have a PIT file, you can use this one. This will provide you with human-readable analysis of a PIT file.
This can also be accomplished locally on your computer with this file: http://goo.im/devs/AdamOutler/libpitX/libpit-X-R917.jar
Code:
[email protected]:~$libpit-X.jar GalaxyCamera.pit
PIT Name: Mx
Entry Count: 17
File Type: COM_TAR2
--- Entry #0 ---
ID: 80 Partition Name: BOOTLOADER
Filename: sboot.bin param: md5
Block Size: 1734 (887.8 kB)
Block range: 0 - 1733 (hex 0x0 - 0x6c5)
PartType: 2 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Bootloader partition resides on the AP EMMC.
--- Entry #1 ---
ID: 81 Partition Name: TZSW
Filename: tz.img param: md5
Block Size: 312 (159.7 kB)
Block range: 1734 - 2045 (hex 0x6c6 - 0x7fd)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #2 ---
ID: 70 Partition Name: PIT
Filename: camera.pit
Block Size: 16 (8.2 kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #3 ---
ID: 71 Partition Name: MD5HDR
Filename: md5.img param: in.md5
Block Size: 2048 (1.0 MB)
Block range: 50 - 2097 (hex 0x32 - 0x831)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #4 ---
ID: 1 Partition Name: BOTA0
Filename: -
Block Size: 8192 (4.2 MB)
Block range: 8192 - 16383 (hex 0x2000 - 0x3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #5 ---
ID: 2 Partition Name: BOTA1
Filename: -
Block Size: 8192 (4.2 MB)
Block range: 16384 - 24575 (hex 0x4000 - 0x5fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #6 ---
ID: 3 Partition Name: EFS
Filename: efs.img param: md5
Block Size: 40960 (21.0 MB)
Block range: 24576 - 65535 (hex 0x6000 - 0xffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #7 ---
ID: 4 Partition Name: PARAM
Filename: param.bin param: md5
Block Size: 16384 (8.4 MB)
Block range: 65536 - 81919 (hex 0x10000 - 0x13fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #8 ---
ID: 5 Partition Name: BOOT
Filename: boot.img param: md5
Block Size: 16384 (8.4 MB)
Block range: 81920 - 98303 (hex 0x14000 - 0x17fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #9 ---
ID: 6 Partition Name: RECOVERY
Filename: recovery.img param: md5
Block Size: 16384 (8.4 MB)
Block range: 98304 - 114687 (hex 0x18000 - 0x1bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #10 ---
ID: 7 Partition Name: RADIO
Filename: modem.bin param: md5
Block Size: 65536 (33.6 MB)
Block range: 114688 - 180223 (hex 0x1c000 - 0x2bfff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #11 ---
ID: 8 Partition Name: CACHE
Filename: cache.img param: md5
Block Size: 2097152 (1.1 GB)
Block range: 180224 - 2277375 (hex 0x2c000 - 0x22bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #12 ---
ID: 9 Partition Name: SYSTEM
Filename: system.img param: md5
Block Size: 3145728 (1.6 GB)
Block range: 2277376 - 5423103 (hex 0x22c000 - 0x52bfff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #13 ---
ID: 10 Partition Name: HIDDEN
Filename: hidden.img param: md5
Block Size: 737280 (377.5 MB)
Block range: 5423104 - 6160383 (hex 0x52c000 - 0x5dffff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #14 ---
ID: 11 Partition Name: OTA
Filename: -
Block Size: 16384 (8.4 MB)
Block range: 6160384 - 6176767 (hex 0x5e0000 - 0x5e3fff)
PartType: 5 FilesystemType: 1 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA:
This Basic format Data partition resides on the AP EMMC.
--- Entry #15 ---
ID: 12 Partition Name: TDATA param: TA
Filename: - param: erdata.img param: md5
Block Size: 409600 (209.7 MB)
Block range: 6176768 - 6586367 (hex 0x5e4000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: param: Dmained
This EXT4 format Data partition resides on the AP EMMC.
--- Entry #16 ---
ID: 13 Partition Name: USERDATA
Filename: userdata.img
Block Size: 0 (0 B)
Block range: 6586368 - 6586367 (hex 0x648000 - 0x647fff)
PartType: 5 FilesystemType: 5 BinType: 0 DevType: 2
Offset:0 Size: 0 FOTA: remained
This EXT4 format Data partition resides on the AP EMMC. The partition will expand to fill the remainder of the EMMC.
Development Library/Downloads/Documentation
The libpit-X library is an extremely heavy overhaul of the libpit--Java- library by Benjamin Dobell. It features 100% accurate read/write/modification ability. It is also very well documented. I've submitted an issue for Benjamin to pull my changes. Until then you can find the library here.
Online documentation can be found here: http://javadoc.casual-dev.com/namespacecom_1_1casual__dev_1_1libpit_x.html
When you load a Library into your development environment, you need three parts. The Package, the Javadoc and the Source. The latest version of these three parts can be found here:
Package: http://jenkins.casual-dev.com/view/All/job/Build libpitX/ws/trunk/X/libpitX/dist/libpit-X.jar
Javadoc: http://jenkins.casual-dev.com/view/...runk/X/libpitX/dist/javadoc/*zip*/javadoc.zip
Source: http://jenkins.casual-dev.com/view/All/job/Build libpitX/ws/trunk/X/libpitX/src/*zip*/src.zip
Library Archives can be found here: http://goo.im/devs/AdamOutler/libpitX
Here's a picture of the library in action: http://dl.xda-developers.com/attach...3/7/8/Screenshot_from_2013-11-23_21_16_36.png
Automated Testing
Testing is conducted on EVERY SINGLE REVISION and compiled code is not published to the archvies if testing fails.
Latest test results: http://jenkins.casual-dev.com/job/CASUALbuild Test/lastBuild/console
Test code for this $X project: https://code.google.com/p/android-c...trunk/CASUALcore/test/CASUAL/archiving/libpit
And of course you can always test version yourself with our Analyze Your Pit File Online utility.
About
This is a $X project. The $ represents CASUAL for two reasons; CASUAL commands start with $, and the way CASUAL is commonly pronounced is cash-ual. In $X projects, the $ is silent. $X projects are not CASUAL core projects but rather offshoots. Rather than create an entire new repository for $X projects, we will host them in the http://android-casual.googlecode.com repository. For example, the working source code for this project is located in the CASUAL-Core and during build, the $X project is automatically created in the X.casual_dev.libpitX pacakge.
If you wish to contribute to this project, or any other CASUAL project, check out the "Developers" section of this page: http://casual-dev.com/about/. There's a lot to do and we are wiling to help you learn.
Please tell how to redistribute space from cache and hidden partions to increase user space with your utility?
Adam, most PIT files I analyze have one or two strange partitions at the end..is this the fault of the analysis software or is just something else completely? Also, have you ever been able to extract the pit from a device that you was the same as ( md5 match) one you would get in a odin tar? The pit files I extract never end up being the exact same as the pit files that come in the odin tar for a particular device regardless of the method used; Heimdall and/or using dd if/of= w/ correct skip/count don't yield the right results. The PIT analysis tool you helped make lists everything correctly for the VZW GS4 but doesnt list the strange partition at the end thats found with other analysis tools like the one below, so I assume the last thing isn't a partition then?
TL;DR - What is the partition at the end with strange characters?
{
"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"
}
Surge1223 said:
TL;DR - What is the partition at the end with strange characters?
Click to expand...
Click to collapse
That would appear to be a signature.
Please tell me this is going to lead 16gig Samsung Sg4 users to get more than 9 gigs free space when using a non touch wiz ROM . Great project and congrats
igoa said:
Please tell how to redistribute space from cache and hidden partions to increase user space with your utility?
Click to expand...
Click to collapse
This isn't a utility, it's a library. You would include it in your Android Application or Java Desktop App.
Here's how you would use it for your project
Code:
Class BlockResizer{
public void remove100BlocksFromCACHE(){
//Open the PIT file
PitData pd=new PitData("mypit.pit");
//get the CACHE partition
PitEntry CACHE=pd.findEntry(String partitionName);
//Remove 100 blocks from CACHE
int blocksToRemove=100;
CACHE.block_count=CACHE.block_count-blocksToRemove;
//Loop through the rest of the partitions and bump them up 100 blocks.
for (int i=CACHE.part_id+1; i<pd.entryCount; i++){
pd.getEntry(i).BLOCK_START=pd.getEntry(i).BLOCK_START-blocksToRemove;
}
//write out the new PIT to "newPit.pit"
pd.pack(new DataOutputStream(new FileOutputStream("newPit.pit");
}
This would work just fine assuming that the rest of the partitions after the CACHE are in proper order.
igoa said:
Please tell how to redistribute space from cache and hidden partions to increase user space with your utility?
Click to expand...
Click to collapse
Hey, i just added the ability to do this easily after reviewing the code for a bit. The commit is still processing and the new library and documentation should be up shortly... Here goes a partition resize
Code:
public void resize(){
PitData instance = new PitData("MyPitFile.pit");
String partName="CACHE"; //partition name to change
int changeToSize=-2000; //size to change partition (-2000 blocks= 1 megabyte smaller)
try {
instance.resizePartition(partName, changeToSize); //actually resizes the partiton and all others are moved.
} catch (ClassNotFoundException ex) {
Logger.getLogger(PitDataTest.class.getName()).log(Level.SEVERE, null, ex); //this occurs if the partition specified is not found
}
instance.pack(new DataOutputStream(new FileOutputStream("newPit.pit"); //write out the new PIT to "newPit.pit"
}
This code has accompanying test code. So, if you'd like to resize a PIT, all you need to do is add the libpitX library into an existing project then run the code above.
AdamOutler said:
That would appear to be a signature.
Click to expand...
Click to collapse
This is very interesting. Is there anything we can do with it? Or is this read only/unknown flash protocol?
ryanbg said:
This is very interesting. Is there anything we can do with it? Or is this read only/unknown flash protocol?
Click to expand...
Click to collapse
You can append it to the end of the file.
AdamOutler said:
You can append it to the end of the file.
Click to expand...
Click to collapse
So it's not possible to write my own certificate to this 'partition' yet?
ryanbg said:
So it's not possible to write my own certificate to this 'partition' yet?
Click to expand...
Click to collapse
Yeah but it's worthless without Samsung's private key.
AdamOutler said:
Yeah but it's worthless without Samsung's private key.
Click to expand...
Click to collapse
Have you seen this post? here
and more specifically this:
ERROR: Image Invalid, X509_Certificate is NULL!
ERROR: Boot Invalid, RSA_KEY is NULL!
ERROR: Image Invalid! Decryption failed!
ERROR: Image Invalid! Please use another image!
Does this make a difference?
That's just strings and it says what error you'll get if you put in a null signature.
@AdamOutler for the VZW Galaxy S4 I analyzed the PIT file produced by Heimdall and it reports the last four partitions as "remained" so I decided to manually extract my PIT file using
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/sch1545.pit bs=8 count=580 skip=2176
which is specific to MSM8690 S4's and the PIT analysis now shows the "remained" partitions actual values and you can see the PIT I extracted is factory signed, because I compare the md5 to the PIT from a factory Odin tar here so is this problem unique to just the S4 or is it a Heimdall problem? I assumed Heimdall just extracted the padded PIT file but even so it should still show the information for the last 4 partitions.
Before
Code:
--- Entry #29 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #30 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #31 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #32 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
After
Code:
--- Entry #29 ---
ID: 70 Partition Name: PGPT
Filename: pgpt.img
Block Size: 34 (17.4kB)
Block range: 0 - 33 (hex 0x0 - 0x21)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PGPT partition, identified as partition number 70, is 17.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as pgpt.img.
--- Entry #30 ---
ID: 71 Partition Name: PIT
Filename: MSM8960.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 71, is 8.2kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as MSM8960.pit.
--- Entry #31 ---
ID: 72 Partition Name: MD5
Filename: md5.img
Block Size: 32 (16.4kB)
Block range: 50 - 81 (hex 0x32 - 0x51)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The MD5 partition, identified as partition number 72, is 16.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as md5.img.
--- Entry #32 ---
ID: 73 Partition Name: SGPT
Filename: sgpt.img
Block Size: 33 (16.9kB)
Block range: 30777311 - 30777343 (hex 0x1d59fdf - 0x1d59fff)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The SGPT partition, identified as partition number 73, is 16.9kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as sgpt.img.
bump
Surge1223 said:
@AdamOutler for the VZW Galaxy S4 I analyzed the PIT file produced by Heimdall and it reports the last four partitions as "remained" so I decided to manually extract my PIT file using
Code:
su
dd if=/dev/block/mmcblk0 of=/sdcard/sch1545.pit bs=8 count=580 skip=2176
which is specific to MSM8690 S4's and the PIT analysis now shows the "remained" partitions actual values and you can see the PIT I extracted is factory signed, because I compare the md5 to the PIT from a factory Odin tar here so is this problem unique to just the S4 or is it a Heimdall problem? I assumed Heimdall just extracted the padded PIT file but even so it should still show the information for the last 4 partitions.
Before
Code:
--- Entry #29 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #30 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #31 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
--- Entry #32 ---
ID: -1 Partition Name: remained
Filename: remained
Block Size: -1 (-512 B)
Block range: -1 - -3 (hex 0xffffffff - 0xfffffffd)
PartType: -1 FilesystemType: -1 BinType: -1 DevType: -1
Offset:-1 Size: -1 FOTA: remained
This unknown format unknown partition resides on the CP unknwon. The partition will expand to fill the remainder of the unknwon.
After
Code:
--- Entry #29 ---
ID: 70 Partition Name: PGPT
Filename: pgpt.img
Block Size: 34 (17.4kB)
Block range: 0 - 33 (hex 0x0 - 0x21)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PGPT partition, identified as partition number 70, is 17.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as pgpt.img.
--- Entry #30 ---
ID: 71 Partition Name: PIT
Filename: MSM8960.pit
Block Size: 16 (8.2kB)
Block range: 34 - 49 (hex 0x22 - 0x31)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The PIT partition, identified as partition number 71, is 8.2kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as MSM8960.pit.
--- Entry #31 ---
ID: 72 Partition Name: MD5
Filename: md5.img
Block Size: 32 (16.4kB)
Block range: 50 - 81 (hex 0x32 - 0x51)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The MD5 partition, identified as partition number 72, is 16.4kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as md5.img.
--- Entry #32 ---
ID: 73 Partition Name: SGPT
Filename: sgpt.img
Block Size: 33 (16.9kB)
Block range: 30777311 - 30777343 (hex 0x1d59fdf - 0x1d59fff)
FilesystemType: 1 PartType: 5 DevType: 2 BinType: 0
Offset:0 Size: 0 FOTA:
The SGPT partition, identified as partition number 73, is 16.9kB in size and carries a Basic format. This partition resides on the Data section of the AP EMMC. It identifies itself to Odin as sgpt.img.
Click to expand...
Click to collapse
@Benjamin Dobell may know something about this.
Can anyone share the file http://goo.im/devs/AdamOutler/libpitX/libpit-X-R917.jar? The link fails.
t2060079 said:
Can anyone share the file http://goo.im/devs/AdamOutler/libpitX/libpit-X-R917.jar? The link fails.
Click to expand...
Click to collapse
I'm looking for the same stuff. I think that the dev has relocated to here:
http://3of5.com/builds.casual-dev.com/files/libpit-X/
HTH, J
Hi All,
Any experts on the initial boot stages (radio, I think of android).
Quick back story:
1) Found that on 28 Dec 2015 Nexus 4 dead overnight. Turned on got stuck in a boot loop I (and it's stock 5.1.1. LMY48T) found that it was hanging on first boot coloured dots or 'starting apps' after optimising apps. Prior to this it had been turning off randomly, unresponive with flashing notification light, loosing network when low on battery, asking for SIM pin. It came back on once a few days later, then same issue.
2) After trying many things (and failing as it's locked, unrooted and doing anything would wipe user data) - I managed to get logcat going and see what was going on - it seemed to hang due to audio issues.
3) Recently opened it up, checked all connections and added a new battery (just in case) - no change
3) Recently I got into the shell and pulled and then delete the DCIM folder to free up some internal space (it was very full). Then re-sidedloaded the OTA LMY48M > LMY48T (clearing caches).
3) After a few restarts it came back, but then after restarting after a successful boot back to square one - so this ruled out full storage as being the culprit.
4)Tried deleting caches again and after a few restarts it has just come back (now doing a full adb backup).
Looking through adbcat I'm now more convinced it's a hardware and/or software issue over the radios - as on a successful boot some kickstart stuff works out well (essentially completing the Sahara protocol for some ESF / MDM9K). On an unsuccessful boot something fails and keeps trying, rearing it's head further up the tree as audio policy issues.
I know in 4.3.3 and in 5.x of Android Nexus4 were having radio issues - so undecided if this is a software or hardware issue (or both).
SUCESSFULL BOOT:
Code:
- waiting for device -
--------- beginning of main
E/rmt_storage( 0): Remote storage service is not supported on mdm target
W/auditd ( 165): type=2000 audit(0.0:1): initialized
I/auditd ( 165): type=1403 audit(0.0:2): policy loaded auid=4294967295 ses=4294967295
W/auditd ( 165): type=1404 audit(0.0:3): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295
I/kickstart-qcks( 172): PARAMETER VALUES
I/kickstart-qcks( 172): COMPORT_DLOAD=/dev/ttyHSL1
I/kickstart-qcks( 172): COMPORT_SAHARA=/dev/ks_hsic_bridge
I/kickstart-qcks( 172): PATHTOIMAGES=/firmware/image/
I/kickstart-qcks( 172): PATHFORRAMDUMP=/data/tombstones/mdm/
I/kickstart-qcks( 172): EFSRAW1=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1
I/kickstart-qcks( 172): EFSRAW2=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2
I/kickstart-qcks( 172): EFSRAW3=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3
I/kickstart-qcks( 172): Header1=efs1.mbn
I/kickstart-qcks( 172): Header2=efs2.mbn
I/kickstart-qcks( 172): Header3=efs3.mbn
I/kickstart-qcks( 172): Testing if port "/dev/mdm" exists
I/kickstart-qcks( 172): Trying to bring MDM9K out of reset
I/lowmemorykiller( 167): Using in-kernel low memory killer interface
D/QSEECOMD: ( 173): qseecom listener services process entry PPID = 1
D/QSEECOMD: ( 173): Parent qseecom daemon process paused!!
D/QSEECOMD: ( 187): QSEECOM DAEMON RUNNING
D/QSEECOMD: ( 187): qseecom listener service threads starting!!!
D/QSEECOMD: ( 187): Total listener services to start = 2
D/QSEECOMD: ( 187): Init dlopen(libdrmtime.so, RTLD_NOW) succeeds
D/QSEECOMD: ( 187): Init::Init dlsym(g_FSHandle atime_start) succeeds
D/QSEECOMAPI: ( 187): QSEECom_register_listener 11 sb_length = 0x5000
D/QSEECOMD: ( 187): Init atime_start ret = 0
D/QSEECOMD: ( 187): time services: Started
D/QSEECOMD: ( 187): Init dlopen(libdrmfs.so, RTLD_NOW) succeeds
D/QSEECOMD: ( 187): Init::Init dlsym(g_FSHandle fs_start) succeeds
D/QSEECOMAPI: ( 187): QSEECom_register_listener 10 sb_length = 0x5000
D/QSEECOMD: ( 187): Init fs_start ret = 0
D/QSEECOMD: ( 187): file system services: Started
--------- beginning of system
I/Vold ( 169): Vold 2.1 (the revenge) firing up
I/SurfaceFlinger( 170): SurfaceFlinger is starting
I/SurfaceFlinger( 170): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/libEGL ( 170): loaded /vendor/lib/egl/libEGL_adreno.so
D/libEGL ( 170): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D/libEGL ( 170): loaded /vendor/lib/egl/libGLESv2_adreno.so
I/Adreno-EGL( 170): <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/15/15, ab0075f, Id3510ff6dc
I/qdgralloc( 170): using (fd=13)
I/qdgralloc( 170): id = msmfb44_80601
I/qdgralloc( 170): xres = 768 px
I/qdgralloc( 170): yres = 1280 px
I/qdgralloc( 170): xres_virtual = 768 px
I/qdgralloc( 170): yres_virtual = 3840 px
I/qdgralloc( 170): bpp = 32
I/qdgralloc( 170): r = 24:8
I/qdgralloc( 170): g = 16:8
I/qdgralloc( 170): b = 8:8
I/qdgralloc( 170): width = 61 mm (319.790161 dpi)
I/qdgralloc( 170): height = 102 mm (318.745087 dpi)
I/qdgralloc( 170): refresh rate = 60.00 Hz
D/qdutils ( 170): DEBUG_CALC_FPS: 0
D/qdutils ( 170): period: 10
D/qdutils ( 170): ignorethresh_us: 500000
D/qdutils ( 170): DEBUG_CALC_FPS: 0
D/qdutils ( 170): period: 10
D/qdutils ( 170): ignorethresh_us: 500000
D/qdoverlay( 170): initoverlay:: opening the device:: /dev/graphics/fb0
D/qdoverlay( 170): initoverlay:: opening the device:: /dev/graphics/fb1
D/qdoverlay( 170): initoverlay:: opening the device:: /dev/graphics/fb2
D/qdoverlay( 170): initoverlay:: opening the device:: /dev/graphics/fb0
D/qdoverlay( 170): initoverlay:: opening the device:: /dev/graphics/fb1
D/qdoverlay( 170): initoverlay:: opening the device:: /dev/graphics/fb2
I/qdhwcomposer( 170): Initializing Qualcomm Hardware Composer
I/qdhwcomposer( 170): MDP version: 440
D/qdhwcomposer( 170): connectPPDaemon: CABL is disabled
I/SurfaceFlinger( 170): Using composer version 1.2
I/qdhwcomposer( 170): hwc_registerProcs
I/qdhwcomposer( 170): Initializing UEVENT Thread
I/qdhwcomposer( 170): Initializing VSYNC Thread
D/qdhwcomposer( 170): hwc_getDisplayAttributes disp = 0, width = 768
D/qdhwcomposer( 170): hwc_getDisplayAttributes disp = 0, height = 1280
I/SurfaceFlinger( 170): EGL information:
I/SurfaceFlinger( 170): vendor : Android
I/SurfaceFlinger( 170): version : 1.4 Android META-EGL
I/SurfaceFlinger( 170): extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_fence_sync EGL_KHR_create_context EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable
I/SurfaceFlinger( 170): Client API: OpenGL_ES
I/SurfaceFlinger( 170): EGLSurface: 8-8-8-8, config=0x5
I/SurfaceFlinger( 170): OpenGL ES informations:
I/SurfaceFlinger( 170): vendor : Qualcomm
I/SurfaceFlinger( 170): renderer : Adreno (TM) 320
I/SurfaceFlinger( 170): version : OpenGL ES 3.0 [email protected] [email protected] ([email protected])
I/SurfaceFlinger( 170): extensions: GL_AMD_compressed_ATC_texture GL_AMD_performance_monitor GL_AMD_program_binary_Z400 GL_EXT_debug_label GL_EXT_debug_marker GL_EXT_discard_framebuffer GL_EXT_robustness GL_EXT_texture_format_BGRA8888 GL_EXT_texture_type_2_10_10_10_REV GL_NV_fence GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth_texture GL_OES_depth24 GL_OES_EGL_image GL_OES_EGL_sync GL_OES_EGL_image_external GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_fragment_precision_high GL_OES_get_program_binary GL_OES_packed_depth_stencil GL_OES_depth_texture_cube_map GL_OES_rgb8_rgba8 GL_OES_standard_derivatives GL_OES_texture_3D GL_OES_texture_float GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_vertex_type_10_10_10_2 GL_OES_vertex_array_object GL_QCOM_alpha_test GL_QCOM_binning_control GL_QCOM_driver_control GL_QCOM_perfmon_global_mode GL_QCOM_extended_get GL_QCOM_extended_get2 GL_QCOM_tiled_rendering GL_QCOM_writeonly_rendering GL_EXT_sRGB GL_EXT_sRGB_write_con
I/SurfaceFlinger( 170): GL_MAX_TEXTURE_SIZE = 4096
I/SurfaceFlinger( 170): GL_MAX_VIEWPORT_DIMS = 4096
D/SurfaceFlinger( 170): Set power mode=2, type=0 flinger=0xb8e40550
D/VoldCmdListener( 169): cryptfs mountdefaultencrypted
D/Cryptfs ( 169): crypt_ftr->fs_size = 27596800
I/Cryptfs ( 169): Using scrypt with keymaster for cryptfs KDF
D/SurfaceFlinger( 170): shader cache generated - 24 shaders in 658.543518 ms
D/libEGL ( 206): loaded /vendor/lib/egl/libEGL_adreno.so
D/libEGL ( 206): loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D/libEGL ( 206): loaded /vendor/lib/egl/libGLESv2_adreno.so
I/Adreno-EGL( 206): <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/15/15, ab0075f, Id3510ff6dc
E/BootAnimation( 206): couldn't find audio_conf.txt
I/kickstart-qcks( 172): EFS Prepend
I/kickstart-qcks( 172): File:'/firmware/image/efs1.mbn' is available for reading
I/kickstart-qcks( 172): File:'/firmware/image/efs2.mbn' is available for reading
I/kickstart-qcks( 172): File:'/dev/block/platform/msm_sdcc.1/by-name/m9kefs1' is available for reading
I/kickstart-qcks( 172): File:'/dev/block/platform/msm_sdcc.1/by-name/m9kefs2' is available for reading
I/kickstart-qcks( 172): File:'/firmware/image/acdb.mbn' is available for reading
I/kickstart-qcks( 172): File:'/firmware/image/mdm_acdb.img' is available for reading
I/kickstart-qcks( 172): Reading RAW EFS1 partition
I/kickstart-qcks( 172): Running dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/data/qcks/temp.dump bs=1024 count=3072
I/kickstart-qcks( 172): Combining Header1 with RAW EFS1 partition
I/kickstart-qcks( 172): Running cat /firmware/image/efs1.mbn /data/qcks/temp.dump > /data/qcks/efs1.bin
I/kickstart-qcks( 172): Reading RAW EFS2 partition
I/kickstart-qcks( 172): Running dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/data/qcks/temp.dump bs=1024 count=3072
I/kickstart-qcks( 172): Combining Header2 with RAW EFS2 partition
I/kickstart-qcks( 172): Running cat /firmware/image/efs2.mbn /data/qcks/temp.dump > /data/qcks/efs2.bin
I/kickstart-qcks( 172): Reading RAW EFS3 partition
I/kickstart-qcks( 172): Running dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/data/qcks/temp.dump bs=1024 count=3072
I/kickstart-qcks( 172): Combining Header3 with RAW EFS3 partition
I/kickstart-qcks( 172): Running cat /firmware/image/efs3.mbn /data/qcks/temp.dump > /data/qcks/efs3.bin
I/kickstart-qcks( 172): Combining ACDB Header with ACDB binary
I/kickstart-qcks( 172): Running cat /firmware/image/acdb.mbn /firmware/image/mdm_acdb.img > /data/qcks/acdb.bin
I/kickstart-qcks( 172): Loading Sahara images
I/kickstart-qcks( 172): Testing if port "/dev/ks_hsic_bridge" exists
E/kickstart-qcks( 172): RUNNING: /system/bin/ks -w /data/tombstones/mdm/ -p /dev/ks_hsic_bridge -r 21 -s 2:/firmware/image/amss.mbn -s 6:/firmware/image/apps.mbn -s 8:/firmware/image/dsp1.mbn -s 11:/firmware/image/osbl.mbn -s 12:/firmware/image/dsp2.mbn -s 21:/firmware/image/sbl1.mbn -s 22:/firmware/image/sbl2.mbn -s 23:/firmware/image/rpm.mbn -s 28:/firmware/image/dsp3.mbn -s 16:/data/qcks/efs1.bin -s 17:/data/qcks/efs2.bin -s 20:/data/qcks/efs3.bin -s 29:/data/qcks/acdb.bin
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 21, file "/firmware/image/sbl1.mbn"
E/kickstart( 224): 117700 bytes transferred in 0.124s (0.91 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 23, file "/firmware/image/rpm.mbn"
E/kickstart( 224): 105696 bytes transferred in 0.024s (4.24 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 22, file "/firmware/image/sbl2.mbn"
E/kickstart( 224): 242376 bytes transferred in 0.032s (7.27 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 12, file "/firmware/image/dsp2.mbn"
D/QSEECOMAPI: ( 169): QSEECom_start_app sb_length = 0x2000
D/QSEECOMAPI: ( 169): App is not loaded in QSEE
D/QSEECOMAPI: ( 169): Loaded image: APP id = 1
I/Cryptfs ( 169): Signing safely-padded object
D/QSEECOMAPI: ( 169): QSEECom_shutdown_app
D/QSEECOMAPI: ( 169): QSEECom_shutdown_app, app_id = 1
I/Cryptfs ( 169): Enabling support for allow_discards in dmcrypt.
E/kickstart( 224): 32137174 bytes transferred in 2.900s (10.57 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 28, file "/firmware/image/dsp3.mbn"
E/kickstart( 224): 6334186 bytes transferred in 0.568s (10.64 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 8, file "/firmware/image/dsp1.mbn"
E/kickstart( 224): 2688527 bytes transferred in 0.276s (9.30 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 16, file "/data/qcks/efs1.bin"
E/kickstart( 224): 786472 bytes transferred in 0.064s (11.76 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 17, file "/data/qcks/efs2.bin"
E/kickstart( 224): 786472 bytes transferred in 0.064s (11.76 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 20, file "/data/qcks/efs3.bin"
E/kickstart( 224): 786472 bytes transferred in 0.064s (11.76 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 29, file "/data/qcks/acdb.bin"
E/kickstart( 224): 2097192 bytes transferred in 0.160s (12.52 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Wrote to /sys/power/wake_lock
E/kickstart( 224): Requested ID 6, file "/firmware/image/apps.mbn"
E/kickstart( 224): 2630368 bytes transferred in 0.272s (9.23 MBps)
E/kickstart( 224): Wrote to /sys/power/wake_unlock
E/kickstart( 224): Sahara protocol completed
UNSUCESSFUL
Where it hangs either at first boot animations or at 'starting apps':
Code:
I/SystemServer( 585): Location Manager
I/SystemServer( 585): Country Detector
I/SystemServer( 585): Search Service
I/SystemServer( 585): DropBox Service
I/SystemServer( 585): Wallpaper Service
I/SystemServer( 585): Audio Service
I/ServiceManager( 585): Waiting for service media.audio_policy...
W/TelecomManager( 585): Telecom Service not found.
I/ServiceManager( 585): Waiting for service media.audio_policy...
I/ServiceManager( 585): Waiting for service media.audio_policy...
I/ServiceManager( 585): Waiting for service media.audio_policy...
I/ServiceManager( 585): Waiting for service media.audio_policy...
W/AudioSystem( 585): AudioPolicyService not published, waiting...
Where the errors are in very early boot:
Code:
E/kickstart( 583): Requested ID 16, file "/data/qcks/efs1.bin"
E/kickstart( 583): ERROR: function: start_image_transfer:932 Invalid length 40 bytes request to be transmitted
E/kickstart( 583): ERROR: function: start_sahara_based_transfer:279 start_image_transfer failed
E/kickstart( 583): ERROR: function: main:305 Uploading Image using Sahara protocol failed
E/kickstart( 583): Wrote to /sys/power/wake_unlock
I/kickstart-qcks( 172): RetCode = 256
E/kickstart-qcks( 172): ERROR: ks return code was 256, something failed
I/kickstart-qcks( 172): Trying to bring MDM9K out of reset
I/kickstart-qcks( 172): Loading Sahara images
I/kickstart-qcks( 172): Testing if port "/dev/ks_hsic_bridge" exists
E/kickstart-qcks( 172): RUNNING: /system/bin/ks -w /data/tombstones/mdm/ -p /dev/ks_hsic_bridge -r 21 -s 2:/firmware/image/amss.mbn -s 6:/firmware/image/apps.mbn -s 8:/firmware/image/dsp1.mbn -s 11:/firmware/image/osbl.mbn -s 12:/firmware/image/dsp2.mbn -s 21:/firmware/image/sbl1.mbn -s 22:/firmware/image/sbl2.mbn -s 23:/firmware/image/rpm.mbn -s 28:/firmware/image/dsp3.mbn -s 16:/data/qcks/efs1.bin -s 17:/data/qcks/efs2.bin -s 20:/data/qcks/efs3.bin -s 29:/data/qcks/acdb.bin
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 21, file "/firmware/image/sbl1.mbn"
E/kickstart( 596): 117700 bytes transferred in 0.124s (0.91 MBps)
E/kickstart( 596): Wrote to /sys/power/wake_unlock
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 23, file "/firmware/image/rpm.mbn"
E/kickstart( 596): 105696 bytes transferred in 0.016s (6.33 MBps)
E/kickstart( 596): Wrote to /sys/power/wake_unlock
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 22, file "/firmware/image/sbl2.mbn"
E/kickstart( 596): 242376 bytes transferred in 0.024s (9.66 MBps)
E/kickstart( 596): Wrote to /sys/power/wake_unlock
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 12, file "/firmware/image/dsp2.mbn"
E/kickstart( 596): 32137174 bytes transferred in 2.288s (13.39 MBps)
E/kickstart( 596): Wrote to /sys/power/wake_unlock
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 28, file "/firmware/image/dsp3.mbn"
D/ACDB-LOADER( 247): send tabla anc data
D/ACDB-LOADER( 247): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER( 247): done with conversion, anc config size is 148
D/ACDB-LOADER( 247): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER( 247): done with conversion, anc config size is 148
D/ACDB-LOADER( 247): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER( 247): done with conversion, anc config size is 148
D/ACDB-LOADER( 247): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER( 247): done with conversion, anc config size is 148
D/ACDB-LOADER( 247): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER( 247): done with conversion, anc config size is 74
D/ACDB-LOADER( 247): ACDB -> ACDB_CMD_GET_ANC_SETTING
D/ACDB-LOADER( 247): done with conversion, anc config size is 74
D/ACDB-LOADER( 247): ACDB -> init done!
D/ ( 247): csd_client_init
E/ ( 247): csd_client_service_init: Invalid rx device 0, setting to handset
E/ ( 247): csd_client_service_init: Invalid tx device 0, setting to handset
E/QMI_FW ( 247): xport_open: socket creation failed - 1
E/Diag_Lib( 247): Diag_LSM_Init: Failed to open handle to diag driver, error = 2
E/kickstart( 596): 6334186 bytes transferred in 0.460s (13.13 MBps)
E/kickstart( 596): Wrote to /sys/power/wake_unlock
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 8, file "/firmware/image/dsp1.mbn"
I/SamplingProfilerIntegration( 256): Profiling disabled.
D/Zygote ( 256): begin preload
I/Zygote ( 256): Preloading classes...
I/art ( 256): Explicit concurrent mark sweep GC freed 798(36KB) AllocSpace objects, 0(0B) LOS objects, 95% free, 44KB/1068KB, paused 183us total 6.989ms
I/art ( 256): Counter: 1
I/art ( 256): Explicit concurrent mark sweep GC freed 547(33KB) AllocSpace objects, 0(0B) LOS objects, 94% free, 64KB/1088KB, paused 183us total 5.035ms
E/kickstart( 596): 2688527 bytes transferred in 0.239s (10.72 MBps)
E/kickstart( 596): Wrote to /sys/power/wake_unlock
E/kickstart( 596): Wrote to /sys/power/wake_lock
E/kickstart( 596): Requested ID 16, file "/data/qcks/efs1.bin"
E/kickstart( 596): ERROR: function: start_image_transfer:932 Invalid length 40 bytes request to be transmitted
E/kickstart( 596): ERROR: function: start_sahara_based_transfer:279 start_image_transfer failed
E/kickstart( 596): ERROR: function: main:305 Uploading Image using Sahara protocol failed
E/kickstart( 596): Wrote to /sys/power/wake_unlock
Sahara Protocol...
Narrowing down the issue.
Decided to try and restart into safe mode and also with airplane mode on.
Surprise, surprise restarting and the same old error occurred. This time thought I would keep adb rebooting until I saw that the Saraha protocol was successful. Did this 4 times and on the 4th time seemed ok.
It went and optimised apps again (due to unsuccessful boot).
Found this thread about the Sahara Protocol: http://forum.xda-developers.com/showthread.php?t=2403798
zeewox said:
These logs come from legit qcks /ks binaries. They're used to load firmware images into SoC subsystems.
Code:
Usage:
-h --help Display this usage information
-n --noclosedevnode Don't close port since it's vanished
-v --verbose Print verbose messages
-m --memdump Force memory debug mode
-i --image Force sahara image transfer mode
-c --command Force command mode
-p --port Device name for USB driver
-o --old Use old PBL boot structure for Dload
-r --ramdumpimage Image ID which must be transferred before forcing memory dump
-w --where Path to store files received from target
-t --timeout Port timeout (in seconds) to use for Sahara transfer
-d <img_id:file_name> --dload <img_id:file_name> Use DMSS download protocol for loading the image
-s <img_id:file_name> --sahara <img_id:file_name> Use Sahara download protocol for transferring the image
Example usage:
sudo kickstart -p /dev/ttyUSB0 -d 10:dbl.mbn
sudo kickstart -p /dev/ttyUSB0 -s 11:osbl.mbn -s 2:amss.mbn
Click to expand...
Click to collapse
Further update...
Managed to get it into safe mode after four boots. Then turned off SIM Pin and restarted (to get back into normal mode).
Again took about 4 restarts before the Sahara protocol was successful and (after optimising apps agin due to incomplete boots).
Thinking this rules out previous things like storage being full, side-loading system update, resetting cache and installed App problems - as actually the successive reboots that some of these options created were perhaps the key to success - leaving:
* Firmware images on the boot partition corrupting / not being read properly (software fix)
* Hardware issue of the boot partition
* Hardware issue on the qualcomm chipset stopping firmware being loaded
As far as I can tell external hardware variables like temperature have no effect.
hi guys and girls,
I have been heavily profiting from the knowledge on this forum, now i finally had to create an account. I have encountered a situation that i cant find anyone having reported it on the internet, is that even possible? maybe someone can help me.
I have a galaxy s4 value edition, or i9515 or jfvelte. I am trying to do a full phone encryption. i even bought this phone specifically to do that.
When I try it goes like this: I select a password/PIN/pattern, then I select encrypt phone, enter said pin/pw then click encrypt, it shows a sprite screen for some time, then restarts without having been encrypted and without ever showing any kind of error message.
i have TWRP 3.0.2 as recovery and have used it to flash CM 13, Ressurection REmix 5.7.4 and DirtyUnicorn10.6 all with the same effect. no encryption, no error message.
when i run "adb logcat | grep -i 'crypt' " on cyanogen 13, I get the following:
01-05 13:10:47.089 581 764 D CryptdConnector: SND -> {1 cryptfs getfield SystemLocale}
01-05 13:10:47.090 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:10:47.090 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:10:47.091 581 766 D CryptdConnector: RCV <- {200 1 -1}
01-05 13:10:53.801 581 1317 D CryptdConnector: SND -> {2 cryptfs getpw}
01-05 13:10:53.802 206 218 D VoldCryptCmdListener: cryptfs getpw
01-05 13:10:53.802 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:10:53.802 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:10:53.802 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:10:53.802 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:10:53.802 581 766 D CryptdConnector: RCV <- {200 2 -1}
01-05 13:10:53.804 581 1317 D CryptdConnector: SND -> {3 cryptfs clearpw}
01-05 13:10:53.807 206 218 D VoldCryptCmdListener: cryptfs clearpw
01-05 13:10:53.807 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:10:53.807 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:10:53.807 581 766 D CryptdConnector: RCV <- {200 3 0}
01-05 13:10:54.438 1556 1556 V JNIHelp : Registering com/google/android/gms/org/conscrypt/NativeCrypto's 235 native methods...
01-05 13:10:54.463 1556 1556 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:10:54.464 1556 1556 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:10:56.884 1872 1872 V JNIHelp : Registering com/google/android/gms/org/conscrypt/NativeCrypto's 235 native methods...
01-05 13:10:56.953 1872 1872 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:10:56.954 1872 1872 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:10:57.971 1979 1979 V JNIHelp : Registering com/google/android/gms/org/conscrypt/NativeCrypto's 235 native methods...
01-05 13:10:57.988 1979 1979 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:10:57.988 1979 1979 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:11:02.384 2416 2416 V JNIHelp : Registering com/google/android/gms/org/conscrypt/NativeCrypto's 235 native methods...
01-05 13:11:02.404 2416 2416 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:11:02.404 2416 2416 I art : Rejecting re-init on previously-failed class java.lang.Class<com.google.android.gms.org.conscrypt.OpenSSLExtendedSessionImpl>
01-05 13:11:39.561 581 1317 D CryptdConnector: SND -> {4 cryptfs cryptocomplete}
01-05 13:11:39.574 206 218 E Cryptfs : not running with encryption, aborting
01-05 13:11:39.575 581 766 D CryptdConnector: RCV <- {200 4 1}
01-05 13:11:51.470 3202 3202 D CryptfsCommands: ro.crypto.state= unencrypted
01-05 13:12:28.189 1852 1852 D SubSettings: Launching fragment com.android.settings.CryptKeeperSettings
01-05 13:13:33.620 1852 1852 D SubSettings: Launching fragment com.android.settings.CryptKeeperSettings
01-05 13:13:39.747 1852 1852 D SubSettings: Launching fragment com.android.settings.CryptKeeperConfirm
01-05 13:13:54.078 581 602 D CryptdConnector: SND -> {5 cryptfs setfield PatternVisible 0}
01-05 13:13:54.078 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:13:54.078 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:13:54.078 581 766 D CryptdConnector: RCV <- {200 5 0}
01-05 13:13:54.083 581 2539 I ActivityManager: START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from uid 1000 on display 0
01-05 13:13:54.081 581 601 D CryptdConnector: SND -> {6 cryptfs setfield PasswordVisible 1}
01-05 13:13:54.087 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:13:54.087 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:13:54.087 581 766 D CryptdConnector: RCV <- {200 6 0}
01-05 13:13:54.118 581 1274 D CryptdConnector: SND -> {7 cryptfs setfield SystemLocale de-DE}
01-05 13:13:54.118 206 218 I Ext4Crypt: ext4 crypto complete called on /data
01-05 13:13:54.118 206 218 I Ext4Crypt: No master key, so not ext4enc
01-05 13:13:54.119 581 766 D CryptdConnector: RCV <- {200 7 0}
01-05 13:13:54.337 581 630 I ActivityManager: Displayed com.android.settings/.CryptKeeperConfirm$Blank: +192ms
01-05 13:13:54.925 581 890 D CryptdConnector: SND -> {8 cryptfs enablecrypto inplace password [scrubbed]}
01-05 13:13:54.952 206 218 D Cryptfs : Just asked init to shut down class main
01-05 13:14:03.940 206 218 D Cryptfs : unmounting /data succeeded
01-05 13:14:03.947 206 218 I Cryptfs : keymaster module name is Keymaster OpenSSL HAL
01-05 13:14:03.947 206 218 I Cryptfs : keymaster version is 2
01-05 13:14:03.947 206 218 I Cryptfs : Found keymaster0 module, using keymaster0 API.
01-05 13:14:03.947 206 218 I Cryptfs : Using scrypt for cryptfs KDF
01-05 13:14:15.962 206 218 D Cryptfs : Just triggered post_fs_data
01-05 13:15:06.283 206 218 E Cryptfs : post_fs_data timed out!
01-05 13:15:06.283 206 218 E Cryptfs : Error enabling encryption after framework is shutdown, no data changed, restarting system
Click to expand...
Click to collapse
on RessurectionRemix i get:
01-05 12:55:36.772 614 765 D CryptdConnector: SND -> {1 cryptfs getfield SystemLocale}
01-05 12:55:36.773 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:55:36.773 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:55:36.774 614 767 D CryptdConnector: RCV <- {200 1 -1}
01-05 12:55:42.089 614 1160 D CryptdConnector: SND -> {2 cryptfs getpw}
01-05 12:55:42.089 208 220 D VoldCryptCmdListener: cryptfs getpw
01-05 12:55:42.089 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:55:42.089 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:55:42.089 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:55:42.089 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:55:42.089 614 767 D CryptdConnector: RCV <- {200 2 -1}
01-05 12:55:42.090 614 1160 D CryptdConnector: SND -> {3 cryptfs clearpw}
01-05 12:55:42.090 208 220 D VoldCryptCmdListener: cryptfs clearpw
01-05 12:55:42.091 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:55:42.091 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:55:42.091 614 767 D CryptdConnector: RCV <- {200 3 0}
01-05 12:57:51.605 1505 1505 D SubSettings: Launching fragment com.android.settings.CryptKeeperSettings
01-05 12:57:55.878 1505 1505 D SubSettings: Launching fragment com.android.settings.CryptKeeperConfirm
01-05 12:58:01.751 614 899 D CryptdConnector: SND -> {4 cryptfs setfield PatternVisible 0}
01-05 12:58:01.751 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:58:01.751 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:58:01.752 614 767 D CryptdConnector: RCV <- {200 4 0}
01-05 12:58:01.753 614 1245 D CryptdConnector: SND -> {5 cryptfs setfield PasswordVisible 1}
01-05 12:58:01.754 614 1256 I ActivityManager: START u0 {cmp=com.android.settings/.CryptKeeperConfirm$Blank (has extras)} from uid 1000 on display 0
01-05 12:58:01.755 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:58:01.755 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:58:01.755 614 767 D CryptdConnector: RCV <- {200 5 0}
01-05 12:58:01.774 614 629 D CryptdConnector: SND -> {6 cryptfs setfield SystemLocale en-US}
01-05 12:58:01.776 208 220 I Ext4Crypt: ext4 crypto complete called on /data
01-05 12:58:01.776 208 220 I Ext4Crypt: No master key, so not ext4enc
01-05 12:58:01.776 614 767 D CryptdConnector: RCV <- {200 6 0}
01-05 12:58:01.953 614 660 I ActivityManager: Displayed com.android.settings/.CryptKeeperConfirm$Blank: +161ms
01-05 12:58:02.572 614 899 D CryptdConnector: SND -> {7 cryptfs enablecrypto inplace password [scrubbed]}
01-05 12:58:02.598 208 220 D Cryptfs : Just asked init to shut down class main
01-05 12:58:04.668 208 220 D Cryptfs : unmounting /data succeeded
01-05 12:58:04.669 208 220 I Cryptfs : keymaster module name is Keymaster OpenSSL HAL
01-05 12:58:04.669 208 220 I Cryptfs : keymaster version is 2
01-05 12:58:04.669 208 220 I Cryptfs : Found keymaster0 module, using keymaster0 API.
01-05 12:58:04.669 208 220 I Cryptfs : Using scrypt for cryptfs KDF
01-05 12:58:05.905 208 220 D Cryptfs : Just triggered post_fs_data
01-05 12:58:56.095 208 220 E Cryptfs : post_fs_data timed out!
01-05 12:58:56.096 208 220 E Cryptfs : Error enabling encryption after framework is shutdown, no data changed, restarting system
Click to expand...
Click to collapse
can somebody help me to get my phone encrypted?
Did you try disabling supersu or disabling root?
thanks for your suggestion, just tried it, with the same results as before, no change.
can you tell me what was your idea behind disabling root?
I did a google search and found some XDA threads where XDA members were able to encrypt by disabling or removing root.
Since you have already tried many solutions, the only solution left may be to use the phone with a stock ROM.
ok still thanks.
this has been frustrating. To whomever having this problem in the future, this is what workarounds have been sugested on the internet, but haven't worked for me, you might try them, they have helped others:
1. disable root/super su as suggested by audit13
2. try it with a wallcharger, not connected to the computer
3. force horizontal orientation of the screen (yes this has helped some)
4. take out microsd-card and sim-card before encrypting
these are all very strange workarounds, not what i had hoped for. I havent found any record of the error messages i managed to identify on the whole internet.
im thinking about selling the stupid thing, and buying another...
Mad love for LineageOS, wouldn't wanna be without it. Now that we got that out of the way, what is it with the uncertain state of encryption, and why is there so little talk about it? One would think that with a community that puts so much effort into privacy, encryption (or rather lack thereof) would be an issue.
I'm approaching 12 working hours, and still can't for the life of me figure out why it doesn't work. I've read countless posts on reddit and xda, searching DuckDuckGo like crazy, tried 4 different ROMs and no dice at all. Before sliding into insanity, I forced myself to make a pause and ask the community.
TWRP 3.1.1.0 + LOS 14.1 / RR 5.8.4 / AICP 12.1.
Starting encryption instantly throws me into infinite boot loops when Magisk had been present (successfully uninstalling it made no difference), and after so many wipes and flashes I feel like going mad. Arbitrarily I would lose access to recovery a couple times, which forced me to re-flash via Odin. I also tried going back to stock twice and starting over from scratch. Removing magisk from the ROM prior to flashing would end up in flashing error 'invalid zip signature' (something like that).
Finally I managed to boot up again with LOS 14.1 after second stock flash. Here encryption simply does nothing, but at least the phone boots up instead of ending in a loop. I never see the encryption animation, just that android picture for about a second before the device restarts. Of course root is not present, so Magisk most certainly was the problem for the boot loops (even though I uninstalled it).
Because the area is too small to flash GSIs，and I try to expand the system partition 。
The tutorial is as follows
1.flash twrp,into twrp
2.Connecting to a computer，in cmd input “
Code:
adb shell
"
3.input
Code:
sgdisk --delete=33 /dev/block/sda
sgdisk --delete=34 /dev/block/sda
sgdisk --delete=35 /dev/block/sda
and then
Pixel (XL)32G input
Code:
sgdisk --new=33:227142:1275716 --change-name=33:system_a --typecode=33:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
sgdisk --new=34:1275717:2324291 --change-name=34:system_b --typecode=34:77036CD4-03D5-42BB-8ED1-37E5A88BAA34 /dev/block/sda
sgdisk --new=35:2324292:7785285 --change-name=35:userdata --typecode=35:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
Pixel (XL)128G input
Code:
sgdisk --new=33:227142:1537862 --change-name=33:system_a --typecode=33:77036CD4-03D5-42BB-8ED1-37E5A88BAA34 /dev/block/sda
sgdisk --new=34:1537863:2848582 --change-name=34:system_b --typecode=34:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
sgdisk --new=35:2848583:31215429 --change-name=35:userdata --typecode=35:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
4.reboot bootloader
input
Code:
fastboot -w
5.reboot
My English is not very good. I hope you can understand it
{Mod edit}
I'd reckon someone destroying their entire phone due to repartitioning Have you actually tried it yourself to make sure its safe? Plus why would we need to use GSI's anyway, pixel's are loved for custom firmware, and it's extremely easy to build new roms.
djared704 said:
I'd reckon someone destroying their entire phone due to repartitioning Have you actually tried it yourself to make sure its safe? Plus why would we need to use GSI's anyway, pixel's are loved for custom firmware, and it's extremely easy to build new roms.
Click to expand...
Click to collapse
Ok guys
I'm using this method myself, and I've told my friends that they're using it, too. So don't worry about it.
As for GSI, some people like MIUI, OOS, etc., so there will always be someone who will use it.
Wonderlooo said:
As for GSI, some people like MIUI
Click to expand...
Click to collapse
there is nobody that likes miui
---------- Post added at 11:25 PM ---------- Previous post was at 11:21 PM ----------
sudoxd said:
there is nobody that likes miui
Click to expand...
Click to collapse
Sorry, beg to differ. Been using a mi pad4, and the only reason i switched to gestures on 10 was because of the way MIUI had implemented it. It's got tons more features than stock 10. The file manager is brilliant, 3 finger swipe to screenshot, and not to mention quickball. So yeah, I'd gladly extend space for system, like i did on my Nexus 5 to use lineage. I'm glad someone's taken the initiative to do this. Good job OP.
I made an account just to say that THIS DOES NOT WORK AND WILL SOFT BRICK YOUR PHONE
it works on my end, haven't tried installing GSI yet, got tired last week because of the partition too large when installing ANDROID 11, hope this will resolve the issue=)
it was able to flash Android 11, not sure yet if it is going to boot=0
@xicib81757 it does work I followed the guide and successfully changed the partition size. Following the original post creates a 5G+ partition. I did later adjust this down to 3GB. Worked flawlessly.
bitl3ss said:
@xicib81757 it does work I followed the guide and successfully changed the partition size. Following the original post creates a 5G+ partition. I did later adjust this down to 3GB. Worked flawlessly.
Click to expand...
Click to collapse
which post you were talking about, this one works on mine, not sure if it is 5G+ though
The command fastboot -w issues following userdata related error:
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
imna357 said:
it works on my end, haven't tried installing GSI yet, got tired last week because of the partition too large when installing ANDROID 11, hope this will resolve the issue=)
Click to expand...
Click to collapse
android 11 GSI is working?
CrazyBear13 said:
android 11 GSI is working?
Click to expand...
Click to collapse
Nope, tried everything
can you please explain. i flashed pixel experience re-partitioning and now i want to revert back cause the system is taking to much space (10 GB) but i don't know how.
is there an updated way to do this? used latest twrp and commands were succesful but when trying fastboot-w it gives this
Code:
Erasing 'userdata' OKAY [ 1.453s]
CreateProcess failed: The system cannot find the file specified. (2)
fastboot: error: Cannot generate image for userdata
Wonderlooo said:
Because the area is too small to flash GSIs，and I try to expand the system partition 。
The tutorial is as follows
1.flash twrp,into twrp
2.Connecting to a computer，in cmd input “
Code:
adb shell
"
3.input
Code:
sgdisk --delete=33 /dev/block/sda
sgdisk --delete=34 /dev/block/sda
sgdisk --delete=35 /dev/block/sda
and then
Pixel (XL)32G input
Code:
sgdisk --new=33:227142:1275716 --change-name=33:system_a --typecode=33:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
sgdisk --new=34:1275717:2324291 --change-name=34:system_b --typecode=34:77036CD4-03D5-42BB-8ED1-37E5A88BAA34 /dev/block/sda
sgdisk --new=35:2324292:7785285 --change-name=35:userdata --typecode=35:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
Pixel (XL)128G input
Code:
sgdisk --new=33:227142:1537862 --change-name=33:system_a --typecode=33:77036CD4-03D5-42BB-8ED1-37E5A88BAA34 /dev/block/sda
sgdisk --new=34:1537863:2848582 --change-name=34:system_b --typecode=34:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
sgdisk --new=35:2848583:31215429 --change-name=35:userdata --typecode=35:EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 /dev/block/sda
4.reboot bootloader
input
Code:
fastboot -w
5.reboot
My English is not very good. I hope you can understand it
{Mod edit}
Click to expand...
Click to collapse
Hey!!
How to get back to stock partition style??
Searched the whole web couldn't find it...
I accidentally deleted all the partitions, and now the phone cannot be switched on, and pressing the power button does not respond
Basically, the phone is broken
So I remind others to know what they are doing when entering commands
I am posting my sfdisk backup from my untouched partition table on my 32 GiB Sailfish Pixel 1
Mind that this is with absolutely no warranty and as-is. Anyone who uses this is still responsible for their own faults.
Bash:
label: gpt
label-id: 98101B32-BBE2-4BF2-A06E-2BB33D000C20
device: /dev/block/sda
unit: sectors
first-lba: 6
last-lba: 7786490
table-length: 36
sector-size: 4096
/dev/block/sda1 : start= 6, size= 128, type=4A20058D-2D54-0D80-E6CC-4ADDDA723C2A, uuid=00000001-0000-0000-0000-000000000000, name="bootlocker_a", attrs="GUID:48,49,50,51,52"
/dev/block/sda2 : start= 134, size= 128, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000002-0000-0000-0000-000000000000, name="bootlocker_b", attrs="GUID:48,49"
/dev/block/sda3 : start= 262, size= 128, type=4F772165-0F3C-4BA3-BBCB-A829E9C969F9, uuid=00000003-0000-0000-0000-000000000000, name="keymaster_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda4 : start= 390, size= 128, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000004-0000-0000-0000-000000000000, name="keymaster_b", attrs="GUID:48,49"
/dev/block/sda5 : start= 518, size= 512, type=A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4, uuid=00000005-0000-0000-0000-000000000000, name="tz_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda6 : start= 1030, size= 512, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000006-0000-0000-0000-000000000000, name="tz_b", attrs="GUID:48,49"
/dev/block/sda7 : start= 1542, size= 128, type=098DF793-D712-413D-9D4E-89D711772228, uuid=00000007-0000-0000-0000-000000000000, name="rpm_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda8 : start= 1670, size= 128, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000008-0000-0000-0000-000000000000, name="rpm_b", attrs="GUID:48,49"
/dev/block/sda9 : start= 1798, size= 128, type=C00EEF24-7709-43D6-9799-DD2B411E7A3C, uuid=00000009-0000-0000-0000-000000000000, name="pmic_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda10 : start= 1926, size= 128, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=0000000A-0000-0000-0000-000000000000, name="pmic_b", attrs="GUID:48,49"
/dev/block/sda11 : start= 2054, size= 128, type=E1A6A689-0C8D-4CC6-B4E8-55A4320FBD8A, uuid=0000000B-0000-0000-0000-000000000000, name="hyp_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda12 : start= 2182, size= 128, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=0000000C-0000-0000-0000-000000000000, name="hyp_b", attrs="GUID:48,49"
/dev/block/sda13 : start= 2310, size= 64, type=73471795-AB54-43F9-A847-4F72EA5CBEF5, uuid=0000000D-0000-0000-0000-000000000000, name="cmnlib32_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda14 : start= 2374, size= 64, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=0000000E-0000-0000-0000-000000000000, name="cmnlib32_b", attrs="GUID:48,49"
/dev/block/sda15 : start= 2438, size= 64, type=8EA64893-1267-4A1B-947C-7C362ACAAD2C, uuid=0000000F-0000-0000-0000-000000000000, name="cmnlib64_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda16 : start= 2502, size= 64, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000010-0000-0000-0000-000000000000, name="cmnlib64_b", attrs="GUID:48,49"
/dev/block/sda17 : start= 2566, size= 1024, type=400FFDCD-22E0-47E7-9A23-F16ED9382388, uuid=00000011-0000-0000-0000-000000000000, name="aboot_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda18 : start= 3590, size= 1024, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000012-0000-0000-0000-000000000000, name="aboot_b", attrs="GUID:48,49"
/dev/block/sda19 : start= 4614, size= 8192, type=20117F86-E985-4357-B9EE-374BC1D8487D, uuid=00000013-0000-0000-0000-000000000000, name="boot_a", attrs="GUID:48,49,50,52,54"
/dev/block/sda20 : start= 12806, size= 8192, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000014-0000-0000-0000-000000000000, name="boot_b", attrs="GUID:48,49,51,52"
/dev/block/sda21 : start= 20998, size= 8192, type=20117F86-E985-4357-B9EE-374BC1D8487D, uuid=00000015-0000-0000-0000-000000000000, name="hosd_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda22 : start= 29190, size= 8192, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000016-0000-0000-0000-000000000000, name="hosd_b", attrs="GUID:48,49"
/dev/block/sda23 : start= 37382, size= 32, type=F65D4B16-343D-4E25-AAFC-BE99B6556A6D, uuid=00000017-0000-0000-0000-000000000000, name="devcfg_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda24 : start= 37414, size= 32, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000018-0000-0000-0000-000000000000, name="devcfg_b", attrs="GUID:48,49"
/dev/block/sda25 : start= 37446, size= 17920, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=00000019-0000-0000-0000-000000000000, name="modem_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda26 : start= 55366, size= 17920, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=0000001A-0000-0000-0000-000000000000, name="modem_b", attrs="GUID:48,49"
/dev/block/sda27 : start= 73286, size= 64, type=ED9E8101-05FA-46B7-82AA-8D58770D200B, uuid=0000001B-0000-0000-0000-000000000000, name="msadp_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda28 : start= 73350, size= 64, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=0000001C-0000-0000-0000-000000000000, name="msadp_b", attrs="GUID:48,49"
/dev/block/sda29 : start= 73414, size= 64, type=E6E98DA2-E22A-4D12-AB33-169E7DEAA507, uuid=0000001D-0000-0000-0000-000000000000, name="apdp_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda30 : start= 73478, size= 64, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=0000001E-0000-0000-0000-000000000000, name="apdp_b", attrs="GUID:48,49"
/dev/block/sda31 : start= 73542, size= 76800, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=0000001F-0000-0000-0000-000000000000, name="vendor_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda32 : start= 150342, size= 76800, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000020-0000-0000-0000-000000000000, name="vendor_b", attrs="GUID:48,49"
/dev/block/sda33 : start= 227142, size= 524288, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=00000021-0000-0000-0000-000000000000, name="system_a", attrs="GUID:48,49,50,51,52,54"
/dev/block/sda34 : start= 751430, size= 524288, type=77036CD4-03D5-42BB-8ED1-37E5A88BAA34, uuid=00000022-0000-0000-0000-000000000000, name="system_b", attrs="GUID:48,49"
/dev/block/sda35 : start= 1275718, size= 6509568, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=00000023-0000-0000-0000-000000000000, name="userdata", attrs="GUID:48,49"
/dev/block/sda36 : start= 7785286, size= 1205, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=00000024-0000-0000-0000-000000000000, name="reserve0", attrs="GUID:48,49"
On an additional note:
For some reason the Pixel 1 might need a VNDK library to boot.
See:
Google Pixel XL (marlin) - libraries needed to boot · Issue #1196 · phhusson/treble_experimentations
The following libraries are needed to boot the Quack GSI correctly on this device: android.hardware.audio.common-util.so [email protected] libeffectsconfig.so (all under /sy...
github.com
Bootloop on Pixel (sailfish) · Issue #1707 · phhusson/treble_experimentations
Hi, obviously thanks for providing GSI roms. Anyway, I don't have much to say. I tried every possible way to flash the GSI: clean, dirty, from TWRP, from Fastboot, flashing the stock FW and then fl...
github.com
The specific vndklite variant, system-squeak-arm64-ab-vndklite-vanilla.img.xz, was really the first time I got my Pixel 1 to boot any GSI properly:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
I think official Google GMS GSI includes the VNDK library, while the AOSP GSI does not.