Hello,
I am starting this thread in the hopes of spurring some investigation into how to unlock the Samsung Galaxy Ace 2(X) without paying for an unlock code or for a service box such as Octoplus etc. All other methods for unlocking Samsung devices (dialer code, nv_data etc) do not work on this device.
I have made a little bit of progress on my own device, the GT-S7560m or Galaxy Ace 2X, outlined here. Unfortunately, I cannot provide a method to unlock as of yet, as the method I currently have found will replace the target device IMEI with the IMEI of the 'donor' device. I have not found a way to change the IMEI back (yet).
First, what I did was simple: Root the phone and backup all partitions other than /system, /data, /cache (/dev/block/mmcblk0pX) I did this a couple of times in between reboots and factory resets to have multiple backups as well as to see if any partitions change after reboots or resets.
It turns out that there are five partitions which change (slightly or drastically) after reboots/resets. These are:
mmcblk0p9
mmcblk0p10
mmcblk0p11
mmcblk0p13
mmcblk0p19 (/efs, found via mount command)
Since the S7560M does not have a GPT partition table, I can't find the labels for what these partitions actually are. 11,13 and 19 are mostly blank, while 9 and 10 are chock full.
Next, I bought an unlock service on eBay. Once unlocked, I took another image of all the partitions, and compared which ones were changed (locked vs unlocked). Unsurprisingly, the same five partitions were different.
To narrow it down, I the flashed back the locked versions of these partitions until my simlock returned.
mmcblk0p9 is the partition that holds the simlock data
I tested flashing only p9 and, indeed, simlock disappeared and reappeared according to the version being flashed. I have multiple devices to test with at the moment, so I took the unlocked p9 from Phone A and flashed it to Phone B, and sure enough, Phone B could then accept foreign SIM cards.
Unfortunately, this also changed Phone B's IMEI to that of Phone A
I tried various tools to attempt to zero out the IMEI (so that the partition image can be shared between devices and the end-user can then restore their proper IMEI) to no avail. It seems the NV items on this device are locked or read-only for some reason.
CDMA Workshop, NV Items Reader-Writer, QPST, QXDM, all these tools are able to read NV items fine, but when trying to write back NV item 550 ue_imei it inevitably fails. In QPST an unknown error (0x80004005) is thrown when writing, whereas in QXDM the program states "No DIAG response received" when attempting to write the NV item. I tried multiple phones, PCs and versions of Windows with the same error.
You'll recall that on other devices such as the GS3, QPST/QXDM/etc works perfectly fine to restore the IMEI through NV editing.
I believe mmcblk0p9 is the 'real' EFS partition, holding the NV items for the device. It also seems to be encrypted, since I cannot find the IMEI in hex nor decimal format inside it, yet the IMEI is changed when the partition is cross-flashed. Across phones and even simply rebooting, the partition almost completely changes, save for a header and a couple of other bytes.
In order to unlock the device freely, I believe the next step is to either decrypt mmcblk0p9, or find a way to get QPST/QXDM to write to the phone
If you have any thoughts/experience, feel free to post below! I am sort of stuck here.
This is a REALLY interesting thread. We need more of these! I know that to unlock my good old Galaxy Gio, you had to pull the bml5 partition and look at it with a hex editor to find 8 digits surrounded by nonsense symbols. Unlocking this device is gonna be MUCH harder, but maybe we just need to look at one of the 5 partitions you mentioned with a hex editor? I have no need of unlocking my device, nor have I ever actually tried it, but I'd like to get involved in this. Tell me, what happens when you insert a foreign sim card into your Ace II X (then you power it on or reboot it)? Does a dialog pop up asking for a code?
Dont bother with tools from market, they are made for units with samsung and qualcomm cpus. Ace2/S3 mini/S Advance/Xperia Sola/Xperia U and few others use NovaThor cpu from ST-Ericsson. So you should look in that direction. I have posted partition info here http://forum.xda-developers.com/showpost.php?p=42096782&postcount=22
You should also look those threads about partitions and some other info:
http://forum.xda-developers.com/showthread.php?t=2145464
http://forum.xda-developers.com/showthread.php?t=2352064
http://forum.xda-developers.com/showthread.php?t=2389395
http://forum.xda-developers.com/showthread.php?t=2132670
IIRC imei is most likely in cspsa partition, but encrypted. Search also for binaries in /system/lib/tee.
Some things i think may help further:
- gap betwwen partitions
- serial number is not encrypted, you can find it by searching the dump
If you want you can buy development board for NovaThor pretty cheap at http://shop.strato.com/epages/61428605.sf/en_GB/?ViewObjectID=11538 as this platform seems dead since ST-Ericsson split and so is with price of the board.
For i8160/p/l (and for all phones with novathor soc) the imei, serial and simlock data is on cspsa_fs that's 100%, but it's encrypted and I think there is a hash check or something similar because if you edit something (no matter what) in cspsa partition dump after reflashing the modem completely stops working - no signal, no imei.
Szaby59 said:
For i8160/p/l (and for all phones with novathor soc) the imei, serial and simlock data is on cspsa_fs that's 100%, but it's encrypted and I think there is a hash check or something similar because if you edit something (no matter what) in cspsa partition dump after reflashing the modem completely stops working - no signal, no imei.
Click to expand...
Click to collapse
angrybb said:
Dont bother with tools from market, they are made for units with samsung and qualcomm cpus. Ace2/S3 mini/S Advance/Xperia Sola/Xperia U and few others use NovaThor cpu from ST-Ericsson. So you should look in that direction. I have posted partition info here http://forum.xda-developers.com/showpost.php?p=42096782&postcount=22
You should also look those threads about partitions and some other info:
http://forum.xda-developers.com/showthread.php?t=2145464
http://forum.xda-developers.com/showthread.php?t=2352064
http://forum.xda-developers.com/showthread.php?t=2389395
http://forum.xda-developers.com/showthread.php?t=2132670
IIRC imei is most likely in cspsa partition, but encrypted. Search also for binaries in /system/lib/tee.
Some things i think may help further:
- gap betwwen partitions
- serial number is not encrypted, you can find it by searching the dump
If you want you can buy development board for NovaThor pretty cheap at http://shop.strato.com/epages/61428605.sf/en_GB/?ViewObjectID=11538 as this platform seems dead since ST-Ericsson split and so is with price of the board.
Click to expand...
Click to collapse
You guys are mistaken. The device being discussed is not the Ace II, but instead the Ace II X (same as S7560 Galaxy Trend or S7562 S Duos but with single sim). It does have a Snapdragon S1 clocked to 1 GHz (MSM7227A) with an Adreno 200 GPU. @op maybe you should modify the thread name to Ace II X instead of Ace 2 (X). It makes it less misleading.
angrybb said:
Dont bother with tools from market, they are made for units with samsung and qualcomm cpus. Ace2/S3 mini/S Advance/Xperia Sola/Xperia U and few others use NovaThor cpu from ST-Ericsson. So you should look in that direction. I have posted partition info here http://forum.xda-developers.com/showpost.php?p=42096782&postcount=22
You should also look those threads about partitions and some other info:
http://forum.xda-developers.com/showthread.php?t=2145464
http://forum.xda-developers.com/showthread.php?t=2352064
http://forum.xda-developers.com/showthread.php?t=2389395
http://forum.xda-developers.com/showthread.php?t=2132670
IIRC imei is most likely in cspsa partition, but encrypted. Search also for binaries in /system/lib/tee.
Some things i think may help further:
- gap betwwen partitions
- serial number is not encrypted, you can find it by searching the dump
If you want you can buy development board for NovaThor pretty cheap at http://shop.strato.com/epages/61428605.sf/en_GB/?ViewObjectID=11538 as this platform seems dead since ST-Ericsson split and so is with price of the board.
Click to expand...
Click to collapse
wrong thread dude..
---------- Post added at 08:59 PM ---------- Previous post was at 08:59 PM ----------
Codename13 said:
You guys are mistaken. The device being discussed is not the Ace II, but instead the Ace II X (same as S7560 Galaxy Trend or S7562 S Duos but with single sim). It does have a Snapdragon S1 clocked to 1 GHz (MSM7227A) with an Adreno 200 GPU. @op maybe you should modify the thread name to Ace II X instead of Ace 2 (X). It makes it less misleading.
Click to expand...
Click to collapse
they should read the entire thread first right?(first post) see how observent they are
Is this thread dead?
Codename13 said:
Is this thread dead?
Click to expand...
Click to collapse
I think so
---------- Post added at 09:21 PM ---------- Previous post was at 08:35 PM ----------
krazykipa said:
Hello,
I am starting this thread in the hopes of spurring some investigation into how to unlock the Samsung Galaxy Ace 2(X) without paying for an unlock code or for a service box such as Octoplus etc. All other methods for unlocking Samsung devices (dialer code, nv_data etc) do not work on this device.
I have made a little bit of progress on my own device, the GT-S7560m or Galaxy Ace 2X, outlined here. Unfortunately, I cannot provide a method to unlock as of yet, as the method I currently have found will replace the target device IMEI with the IMEI of the 'donor' device. I have not found a way to change the IMEI back (yet).
First, what I did was simple: Root the phone and backup all partitions other than /system, /data, /cache (/dev/block/mmcblk0pX) I did this a couple of times in between reboots and factory resets to have multiple backups as well as to see if any partitions change after reboots or resets.
It turns out that there are five partitions which change (slightly or drastically) after reboots/resets. These are:
mmcblk0p9
mmcblk0p10
mmcblk0p11
mmcblk0p13
mmcblk0p19 (/efs, found via mount command)
Since the S7560M does not have a GPT partition table, I can't find the labels for what these partitions actually are. 11,13 and 19 are mostly blank, while 9 and 10 are chock full.
Next, I bought an unlock service on eBay. Once unlocked, I took another image of all the partitions, and compared which ones were changed (locked vs unlocked). Unsurprisingly, the same five partitions were different.
To narrow it down, I the flashed back the locked versions of these partitions until my simlock returned.
mmcblk0p9 is the partition that holds the simlock data
I tested flashing only p9 and, indeed, simlock disappeared and reappeared according to the version being flashed. I have multiple devices to test with at the moment, so I took the unlocked p9 from Phone A and flashed it to Phone B, and sure enough, Phone B could then accept foreign SIM cards.
Unfortunately, this also changed Phone B's IMEI to that of Phone A
I tried various tools to attempt to zero out the IMEI (so that the partition image can be shared between devices and the end-user can then restore their proper IMEI) to no avail. It seems the NV items on this device are locked or read-only for some reason.
CDMA Workshop, NV Items Reader-Writer, QPST, QXDM, all these tools are able to read NV items fine, but when trying to write back NV item 550 ue_imei it inevitably fails. In QPST an unknown error (0x80004005) is thrown when writing, whereas in QXDM the program states "No DIAG response received" when attempting to write the NV item. I tried multiple phones, PCs and versions of Windows with the same error.
You'll recall that on other devices such as the GS3, QPST/QXDM/etc works perfectly fine to restore the IMEI through NV editing.
I believe mmcblk0p9 is the 'real' EFS partition, holding the NV items for the device. It also seems to be encrypted, since I cannot find the IMEI in hex nor decimal format inside it, yet the IMEI is changed when the partition is cross-flashed. Across phones and even simply rebooting, the partition almost completely changes, save for a header and a couple of other bytes.
In order to unlock the device freely, I believe the next step is to either decrypt mmcblk0p9, or find a way to get QPST/QXDM to write to the phone
If you have any thoughts/experience, feel free to post below! I am sort of stuck here.
Click to expand...
Click to collapse
Can you post a zip file op your efs folder?
Thanks in advance.
Hello all,
Unfortunately at this point I have sold all the Ace 2X units I had previously. I wasn't really getting anywhere anyway and ended up buying a Z3X box. Thread can be closed, or feel free to continue in my absence. Good luck!
I'd like if we, as developers working together, could get this done. Just a question: Is there an issue if we share the same IMEI? Why can't one of us pay to unlock our device, then share our mmcblk0p9 with others? Would it cause problems if others flashed our efs partition to their device?
Codename13 said:
I'd like if we, as developers working together, could get this done. Just a question: Is there an issue if we share the same IMEI? Why can't one of us pay to unlock our device, then share our mmcblk0p9 with others? Would it cause problems if others flashed our efs partition to their device?
Click to expand...
Click to collapse
1- multiple phones with the same IMEI on the same network cause problems for all other (the only reason this can normally happen is your phone losing signal or crashing then reconnecting, so it's reasonable for the phone company to drop all other active links when it connects again)
2- on the U8500 Sonys, the role of CSPSA, EFS and some other firmware partitions is done by the "TA" partition. We know parts of it are signed (with different keys, some specific to the individual hardware) and changing them results in hard bricks... not terribly related to this phone, but the moral is that without knowledge about this undocumented binary sequence that is partition 9 (probably requiring a JTAG backup and trial and error) we common mortals can't afford to experiment blindly
Hello,
An S7560M came through my hands again, and I've taken the time to capture the data that is sent to the proprietary Z3X server for generating the unlock codes. The tool bypasses the MSL, reads some data from the modem, sends it to the server for analysis, and sends back your unlock code(s). If anybody is good at cryptography or data analysis, feel free to analyze the Wireshark dump that contains all the data. Somehow, the unlock code shown in the screenshot is attainable with only that data.
I myself have no idea how to get from there to an unlock code on my own. The only modification I've made is removing the serial number of my Z3X equipment in the dump for security. The IMEI and SN do not appear to be transmitted in the dump, but I've removed them from the screenshot.
Hope this helps, good luck.
krazykipa said:
Hello,
An S7560M came through my hands again, and I've taken the time to capture the data that is sent to the proprietary Z3X server for generating the unlock codes. The tool bypasses the MSL, reads some data from the modem, sends it to the server for analysis, and sends back your unlock code(s). If anybody is good at cryptography or data analysis, feel free to analyze the Wireshark dump that contains all the data. Somehow, the unlock code shown in the screenshot is attainable with only that data.
I myself have no idea how to get from there to an unlock code on my own. The only modification I've made is removing the serial number of my Z3X equipment in the dump for security. The IMEI and SN do not appear to be transmitted in the dump, but I've removed them from the screenshot.
Hope this helps, good luck.
Click to expand...
Click to collapse
Not sure how to help, but this is some serious looking stuff! I downloaded your attachment, extracted S7560M.pcapng and I converted it to S7560M.pcap using this guide. I then tried opening it and Ubuntu searched for a program that could open it. I got Wireshark and was able to open it. I'm guessing that's no such sort of hacking, right? Anyways, I'd like to help out. In the image you uploaded in that 7z archive, what is the unlock code? I want to scour the data in the Wireshark dump and see if I can find any correlations between the data in the image and the data in the dump. All I have to guess at this time is that all the code is hex, and it probably translates to decimal.
In the screenshot the unlock code is the NET lock code. The other numbers and * # are dialer codes (for unlocking direct from dialer without inserting a foreign SIM) but the actual code is 30385735.
If i understand it right the sim-partition is 9?
Why whe can't just share that partition from someone who payed for unlocking his device and changing imei (there are some tuts on xda)?
imei
the unlock code is based on the imei..
somebody unlocked his phone based just on his imei and the name of his carrier over the internet..
Anas Karbila said:
If i understand it right the sim-partition is 9?
Why whe can't just share that partition from someone who payed for unlocking his device and changing imei (there are some tuts on xda)?
Click to expand...
Click to collapse
I'll say this again, Partition 9 is unique to each phone. Another way of seeing it is: two people own the same car, when one person is driving the car, the other person can't drive the car, vice versa. You can't duplicate that car, because each numberplate is specific to one car.
Likewise, you can't copy partition 9 to another phone, because it would be the same as using the same numberplate on two different cars. The partition 9 includes the IMEI, if you will, the "numberplate" of the phone.
Mod Edit
Changing imei numbers is illegal.
Any such discussion is not allowed on XDA
Thread closed
malybru
Forum Moderator
What's up guys,
My cell phone is with hardbrick and as there is no solution for it, I wonder if I can use it for anything else, or even sell the spare parts.
Or is it possible for me to buy only one part to make the X722 work?
Thank you for your attention.
Hello, I've read in a forum, of people who have managed to change the motherboard, by one of x720.
I think the motherboard is sold by aliexpress, but I do not know if it compensates.
Base plate expenses, waiting for shipment, look for technical service that does, surely without guarantee of success ...
I think the best thing is to try to sell it.
Greetings.
Keep it. Who knows, there may be a fix in the future. Besides that, you live and you learn. I've bricked an Android tablet myself (a rather old and obscure one at that); I know that feeling of despair. It's just best to just learn your lessons and move on. Stick to Xiaomi and not LeEco from now on--Xiaomi phones have so much more support. Stick to popular phones and even if you brick your phone, it'll probably end up being an easy to fix soft brick.
Case in point--my Galaxy Tab A. I had so many issues loading TWRP, Xposed, and a custom ROM onto that thing, but I kept preserving and ended up with a great ROM with lots of customization. Halfway through my trials, I nearly gave up because the tablet refused to boot. It took hours upon hours to start up and I thought I was doomed. But I kept trying and eventually got somewhere. Not with my other tablet, though--I screwed up the partition, which usually means an irreversible brick, unless you're able to restore the partition table (I wasn't). So now it sits at the bottom of my closet, dead.
Xiaomi is so cheap, you just buy new phone to replace the bricked one. I found Xiaomi work excellent even just a midrange with Sd625, worth every cent.
So guys,
It's possible to unbrick LePro3 x722
how we can do it?
with a proper qfil file for that device (x720 will not work)
how we can get that file?
Well, since leeco is not sharing, we need to backup from a functional device, the only alternative I know is to use a tool that backups that, but for that we need a box or a specific pendrive
check here: https://www.youtube.com/watch?v=Xqjy9QyvFJE
When we get a backup that can be used in qfil, we will be able to unbrick another devices!
If someone knows a way to make qfil backup without a box, please post here
Someone start a GoFundMe for that box and I wouldn't mind donating. But are you 100% sure it works for UFS 2.0 storage as well? It's what the Pro3 uses.
EDIT: looked through some questions and answers on the box's page, and it can't. Box only works for phones with eMMC storage. Oh well.
Then again, the site's Downloads page does mention UFS. But...
Provisioning UFS is a irrecoverable ONE time operation so make sure to select correct "provisioning xml"
Click to expand...
Click to collapse
Sounds worrying.
That's bad news :s
sk8223 said:
Someone start a GoFundMe for that box and I wouldn't mind donating. But are you 100% sure it works for UFS 2.0 storage as well? It's what the Pro3 uses.
EDIT: looked through some questions and answers on the box's page, and it can't. Box only works for phones with eMMC storage. Oh well.
Then again, the site's Downloads page does mention UFS. But...
Sounds worrying.
Click to expand...
Click to collapse
And that box http://www.sharkgsm.com/pro_detail.asp?id=759, does it not work?
I don't know about that box, since I know nothing of QFIL, and I'm not entirely sure that one would work either. It can't just be UFS, it has to be UFS 2.0, surely. Then again I have no experience with partitioning or QFIL.
I was searching about a bit, and I found one recent thread about the x722's QFIL: http://bbs.ydss.cn/thread-1104933-1-1.html
First post says this (via Google Translate):
Can we decompress the qfil package from Max2 and then delete all the img files inside and then extract the img files from the fastboot package in pro3 and copy them into max2 folder and then proceed to the 9008 mode flashing machine, No brick machine, can not try, but can not - try, max2 Brush Brush bag there, 32g version of the corresponding 32g version
Click to expand...
Click to collapse
This is just a theory, who knows if it actually works. Someone ought to try to restore their 32GB x722 with the Max 2 32GB's QFIL file (the internal storage size needs to correspond to your device's size).
It seems that even the Chinese are searching for QFIL files! It's weird that there's not a single QFIL file available for this device, free or paid. I know a lot of Chinese users like to hide files behind paywalls and such.
Now, I did find this, but it's paywalled, meaning you have to log in and probably buy it using the forum's currency or real currency:
http://www.bstdn.com/forum.php?mod=viewthread&tid=4852
This QFIL file is supposedly for the x722(?) but IDK if that's true or not.
I also found this thread: http://www.18095.com/thread-382783-1-1.html
But when I log in with Weibo, it takes me to some newbie page, and I can't even access the forum. My user group probably can't view any threads. Weird. Chinese forums are so irritating.
sk8223 said:
I don't know about that box, since I know nothing of QFIL, and I'm not entirely sure that one would work either. It can't just be UFS, it has to be UFS 2.0, surely. Then again I have no experience with partitioning or QFIL.
I was searching about a bit, and I found one recent thread about the x722's QFIL: http://bbs.ydss.cn/thread-1104933-1-1.html
First post says this (via Google Translate):
This is just a theory, who knows if it actually works. Someone ought to try to restore their 32GB x722 with the Max 2 32GB's QFIL file (the internal storage size needs to correspond to your device's size).
It seems that even the Chinese are searching for QFIL files! It's weird that there's not a single QFIL file available for this device, free or paid. I know a lot of Chinese users like to hide files behind paywalls and such.
Now, I did find this, but it's paywalled, meaning you have to log in and probably buy it using the forum's currency or real currency:
http://www.bstdn.com/forum.php?mod=viewthread&tid=4852
This QFIL file is supposedly for the x722(?) but IDK if that's true or not.
I also found this thread: http://www.18095.com/thread-382783-1-1.html
But when I log in with Weibo, it takes me to some newbie page, and I can't even access the forum. My user group probably can't view any threads. Weird. Chinese forums are so irritating.
Click to expand...
Click to collapse
That qfil is the one that already exists.
If it says x720 .... x728 ... or another does not work.
X722 is different.
The lemax 2 is already tested without success.
prog_ufs_firehose_8996_ddr.elf and prog_ufs_firehose_8996_lite.elf are specific to each terminal. It is not worth X720 ... X728 or X2.
The boxes cost the same or more than a new terminal.
You have to look for a software shortcut, but there is no terminal to experiment with.
Greetings.
F.J.V said:
That qfil is the one that already exists.
If it says x720 .... x728 ... or another does not work.
X722 is different.
The lemax 2 is already tested without success.
prog_ufs_firehose_8996_ddr.elf and prog_ufs_firehose_8996_lite.elf are specific to each terminal. It is not worth X720 ... X728 or X2.
The boxes cost the same or more than a new terminal.
You have to look for a software shortcut, but there is no terminal to experiment with.
Greetings.
Click to expand...
Click to collapse
The one from the second link is letv乐视X720 X722 QFIL救砖包 黑屏9008救砖包 解决不开机 无法进fastboot, but I don't know if it's already been tried here without success or not. Is this just the ZL1 QFIL? Then it's weird that it's labelled as x722. In any case, I can't verify my account since the forum chose to send the verification email to some weird sina.com email address and not mine... and I can't change it, either.
Someone else will have to first set up a sina.com email address for their Weibo account and then sign in via Weibo to get access to that thread.
sk8223 said:
The one from the second link is letv乐视X720 X722 QFIL救砖包 黑屏9008救砖包 解决不开机 无法进fastboot, but I don't know if it's already been tried here without success or not. Is this just the ZL1 QFIL? Then it's weird that it's labelled as x722. In any case, I can't verify my account since the forum chose to send the verification email to some weird sina.com email address and not mine... and I can't change it, either.
Someone else will have to first set up a sina.com email address for their Weibo account and then sign in via Weibo to get access to that thread.
Click to expand...
Click to collapse
I already downloaded it a couple of days ago.
It is not qfil, it is a rom 20S to install with flashone but via fastboot, not edl.
in a few days I will upload it, but being via fastboot will not work with a blocked bootloader.
It is not the same 20S as that of bangood, it seems more recent because of the numbering, but it is still 20S.
It also has the verification system of the official 26S, so I do not think it is advisable, it may also block the bootloader.
Greetings.
I have a couple of Xiaomi Pocophones F1. I have set up one of them with the most recent LineageOS (rooted the device, edited a lot of system settings, installed and configured some apps) and would like to distribute the OS as an image to other devices of the same model. Is there a way?
I tried NANDroid from the TWRP recovery with PIN (secure startup) disabled before creating the backup as well as on the target device. Unfortunately, the result ist not bootable. I restored Boot, System, and Data partition.
Am I doing something wrong? Are there other ways (aside from professional MDM)?
EDIT: Sorry for the double-posting in the Pocophone sub-forum. I figured that it is not really a Pocophone-limited question.
The only way you will pull that off is compiling the rom yourself with the changes you want.
Never flash a nandroid from another device as they copy devixe spicific files.
I see. I was afraid that was the case and it makes sense.
Out of curiosity: could you come up with some example of those files from the top of your head?
pegnose said:
I see. I was afraid that was the case and it makes sense.
Out of curiosity: could you come up with some example of those files from the top of your head?
Click to expand...
Click to collapse
The main one is the efs fields hich contains the imei as well as another fields used to identify the device from other.
Ah, of course. Thank you again!
PS: You look a little like Batman.
.
Hi forum!
So I own a Project Tango Development Kit Tablet (device name: Yellowstone) which appears to be a Tango-purposed Nvidia Shield K1 tablet. There's just a few threads about the yellowstone in the Shield forum and it's an old device now, that's why I'm posting the question here, in the hopes that the question is not device-related but something more general.
So, I wanted to use this tablet and the stock ROM just made it bootloop ad infinitum. Nothing I did could make it boot. So I went to the Shield forum and I found a TWRP image that would work on it. I rooted it, installed TWRP and I installed a ROM that I found around an old thread. So far so good, the tablet now boots but the audio, microphone and camera doesn't work. I want to use it as an intercom system so, that's the stuff I really want it to be in a working state.
By chance I found a LineageOS 16 ROM for the yellowstone (https://updater.oddsolutions.us/yellowstone) but it's description says "PSCI Repartition ONLY". The author hasn't replied to me to what it means. Googling doesn't give useful results regrettably. So I wonder if anyone around this parts could enlighten me about what is it, and how can it be performed?
Many thanks!
REPARTITION ONLY:
I guess it means that /system and /vendor partitions must get re-partitioned ( increasing their sizes ) what must be done before flashing the ROM.
This usually is done by a "Repartition Pack".
PSCI:
The Power State Coordination Interface (PSCI) is an ARM standard introduced for its new ARMv8 64bit architecture to virtualize CPU power management across exception levels i.e. between software working at different privilege levels: OS kernel, hypervisor and Secure Platform Firmware (SPF).
jwoegerbauer said:
REPARTITION ONLY:
I guess it means that /system and /vendor partitions must get re-partitioned ( increasing their sizes ) what must be done before flashing the ROM.
This usually is done by a "Repartition Pack".
PSCI:
The Power State Coordination Interface (PSCI) is an ARM standard introduced for its new ARMv8 64bit architecture to virtualize CPU power management across exception levels i.e. between software working at different privilege levels: OS kernel, hypervisor and Secure Platform Firmware (SPF).
Click to expand...
Click to collapse
Ahaaa, that's excellent information. I guess they're separated concepts then, not directly related. I'll have to contact the owner then for the repartition pack. Many thanks!
Darius_bd said:
Ahaaa, that's excellent information. I guess they're separated concepts then, not directly related. I'll have to contact the owner then for the repartition pack. Many thanks!
Click to expand...
Click to collapse
Did you ever get a response from npjohnson? I've been folliwing his roms for tango for about a year (if not longer) he did say he was aiming to bring it as an official lineage build......but while i see it's been in development. Nothings been released.
So i am interested to know if you got a response.
Darius_bd said:
Ahaaa, that's excellent information. I guess they're separated concepts then, not directly related. I'll have to contact the owner then for the repartition pack. Many thanks!
Click to expand...
Click to collapse
I also am interested in whether or not you found the PSCI for Android 9. I have a Tango I am wanting to put to use.