[Q] Unlocking X10 - XPERIA X10 Q&A, Help & Troubleshooting

OK first of all... I don't have an X10... based on the fact that there is an unlock utility out there I am guessing that it would be possible to extract the unlock code. What I need from you guys is someone to do
Code:
adb shell
mount
ls /dev/
ls /dev/block/
and paste the results here
I helped figure out the unlock method, wrote the original scripts, and wrote the guide here for the Samsung Galaxy S unlock and I am hoping to be able to do the same for you guys.
Let me know if this would be useful.
If someone has already bought an unlock code and would be willing to help please PM me.

Sounds like a worthwhile project given that there is an ' instant unlock' method advertised by htccode.com, those guys must have already worked it out.
Good luck anyway (I have no programming knowledge, sorry)
Sent from my X10i using XDA App

dagentooboy said:
OK first of all... I don't have an X10... based on the fact that there is an unlock utility out there I am guessing that it would be possible to extract the unlock code. What I need from you guys is someone to do
Code:
adb shell
mount
ls /dev/
ls /dev/block/
and paste the results here
I helped figure out the unlock method, wrote the original scripts, and wrote the guide here for the Samsung Galaxy S unlock and I am hoping to be able to do the same for you guys.
Let me know if this would be useful.
If someone has already bought an unlock code and would be willing to help please PM me.
Click to expand...
Click to collapse
Here are the results of your request:
ls /dev/ said:
$ ls /dev/
ls /dev/
dun
cpuctl
video20
timer
bma150
es209ra_touch
mtd
msm_camera
ppp
q6venc
vdec
diag
graphics
oncrpc
smdcntl2
smdcntl1
smdcntl0
ttyHSUSB1
ttyHSUSB0
ptmx
console
tty
smd21
smd36
smd27
smd7
smd0
kgsl
system_bus_freq
network_throughput
network_latency
cpu_dma_latency
log
binder
akm8973_aot
akm8973_daemon
alarm
keychord
uinput
android_adb_enable
android_adb
tgt
es209ra_proximity
pmem_gpu1
pmem_gpu0
pmem_adsp
pmem
fuse
ashmem
msm_qcelp_in
msm_evrc_in
msm_audio_dev_ctrl
msm_amr_in
msm_amr
msm_voice
msm_dtmf
msm_mp3
msm_aac_in
msm_aac
msm_pcm_in
msm_pcm
nmea
qmi2
qmi1
qmi0
smem_log
mem_notify
kmsg
urandom
random
block
full
zero
null
kmem
mem
controlC0
pcmC0D0c
pcmC0D0p
rtc1
rtc0
i2c-1
i2c-0
card0
ttyHS1
ttyMSM0
input
socket
pts
Click to expand...
Click to collapse
ls /dev/block/ said:
$ ls /dev/block/
ls /dev/block/
vold
mtdblock3
mtdblock2
mtdblock1
mtdblock0
loop7
loop6
loop5
loop4
loop3
loop2
loop1
loop0
ram7
ram6
ram5
ram4
ram3
ram2
ram1
ram0
mmcblk0p3
mmcblk0p1
mmcblk0
Click to expand...
Click to collapse

hrking2000 said:
Sounds like a worthwhile project given that there is an ' instant unlock' method advertised by htccode.com, those guys must have already worked it out.
Good luck anyway (I have no programming knowledge, sorry)
Sent from my X10i using XDA App
Click to expand...
Click to collapse
But this is clearly not a free method.​

And mine...
/ $ mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,mode=755)
devpts on /dev/pts type devpts (rw,mode=600)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
tmpfs on /sqlite_stmt_journals type tmpfs (rw,size=4096k)
/dev/block/mtdblock2 on /system type yaffs2 (ro)
/dev/block/mtdblock3 on /data type yaffs2 (rw,nosuid,nodev)
/dev/block/mtdblock1 on /cache type yaffs2 (rw,nosuid,nodev)
DxDrmServerIpc on /data/DxDrm/fuse type fuse.DxDrmServerIpc (rw,nosuid,nodev,user_id=0,group_id=0,allow_other)
/dev/block//vold/179:1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8)
/ $ ls /dev
akm8973_aot mem_notify qmi0
akm8973_daemon msm_aac qmi1
alarm msm_aac_in qmi2
android_adb msm_amr random
android_adb_enable msm_amr_in rtc0
ashmem msm_audio_dev_ctrl rtc1
binder msm_camera smd0
block msm_dtmf smd21
bma150 msm_evrc_in smd27
card0 msm_mp3 smd36
console msm_pcm smd7
controlC0 msm_pcm_in smdcntl0
cpu_dma_latency msm_qcelp_in smdcntl1
cpuctl msm_voice smdcntl2
diag mtd smem_log
dun network_latency socket
es209ra_proximity network_throughput system_bus_freq
es209ra_touch nmea tgt
full null timer
fuse oncrpc tty
graphics pcmC0D0c ttyHS1
i2c-0 pcmC0D0p ttyHSUSB0
i2c-1 pmem ttyHSUSB1
input pmem_adsp ttyMSM0
keychord pmem_gpu0 uinput
kgsl pmem_gpu1 urandom
kmem ppp vdec
kmsg ptmx video20
log pts zero
mem q6venc
/ $ ls /dev/block
loop0 loop4 mmcblk0 mtdblock2 ram2 ram6
loop1 loop5 mmcblk0p1 mtdblock3 ram3 ram7
loop2 loop6 mtdblock0 ram0 ram4 vold
loop3 loop7 mtdblock1 ram1 ram5
Click to expand...
Click to collapse

rogmar said:
But this is clearly not a free method.​
Click to expand...
Click to collapse
I know that it is not a free method that is why I was supporting the OP'S efforts. (I was just mentioning it as it may be a useful reference if they can work out how htccode do it.)
Sent from my X10i using XDA App

I would like to see what is in /data/DxDrm/fuse
Is it a file or a directory?
Also what is in /dev/pts
Also if anyone has already paid for an unlock and could dump their whole filesystem to a .zip and send it with the unlock code to me that would be helpful.
IF I find the code this will be a free method (although you will be more then welcome to donate)

dagentooboy said:
I would like to see what is in /data/DxDrm/fuse
Is it a file or a directory?
Also what is in /dev/pts
Also if anyone has already paid for an unlock and could dump their whole filesystem to a .zip and send it with the unlock code to me that would be helpful.
IF I find the code this will be a free method (although you will be more then welcome to donate)
Click to expand...
Click to collapse
sorry to say it guys but nothing to do here. Samsung unlocker bases its stuff on the fact that samsung phones store their lock code on a visible partition, quite accesible. Nowhere near to sony ericsson. Samsung developers are nice people
Fuse is a loopback filesystem. You can enter the directory if you have root privileges. the filesystem isnt changed when you enter nck. The code is stored on trimm area as far as I know...
Sent from my X10i using XDA App

biktor_gj said:
Nowhere near to sony ericsson. Samsung developers are nice people /QUOTE]
true, I always envied the Omnia HD users for their custom roms, while I had to stick with my vivaz to the crappy original firmware.
samsung may not have the best devs but at least they dont spend all their brain power on how to prevent users from tampering with their precious firmware.
Click to expand...
Click to collapse

biktor_gj said:
sorry to say it guys but nothing to do here. Samsung unlocker bases its stuff on the fact that samsung phones store their lock code on a visible partition, quite accesible. Nowhere near to sony ericsson. Samsung developers are nice people
Fuse is a loopback filesystem. You can enter the directory if you have root privileges. the filesystem isnt changed when you enter nck. The code is stored on trimm area as far as I know...
Sent from my X10i using XDA App
Click to expand...
Click to collapse
So without a phone that is a no go? I was hopeful BTW if someone wants to donate a phone I would be more then willing to give it a shot but it is looking less hopeful then the SGS :'(

A method you could go about this is literally search the entire phone for the unlock code (if someone bought a working one). I do not see how that would work though because on the Captivate at least it is encoded in a HEX format. But a script should be writable to extract each file from its HEX format and then search for the code. Leave it for a few hours and you should find the file. The only thing that worries me is that the x10 is a different maker. If all AT&T phones had the unlock file stored locally and it was unique to att then the Galaxy S unlock would only work on the Captivate

nbs11 said:
A method you could go about this is literally search the entire phone for the unlock code (if someone bought a working one). I do not see how that would work though because on the Captivate at least it is encoded in a HEX format. But a script should be writable to extract each file from its HEX format and then search for the code. Leave it for a few hours and you should find the file. The only thing that worries me is that the x10 is a different maker. If all AT&T phones had the unlock file stored locally and it was unique to att then the Galaxy S unlock would only work on the Captivate
Click to expand...
Click to collapse
That was sort of where I was going. A quick Linux script should be able to search every file for the code. That is why I need a full backup of the filesystem and the unlock code for one of these phones.

they are also claiming to do it instantly: gsmliberty.net/shop/sony-ericsson-xperia-x10-unlocking-pm-1883.html . Is ther some way to know what files do these software edit?
i m looking for a xperia unlock bt they are all too costly options

I used cellunlocker , not cheap at $39.99 (£26), but one of the few options that had reports of working success without waiting for days when I searched by google.
Pretty costly deal, but they do not issue you a code, the automated software connects to your X10 through the USB cable and then runs some script ?
Anyway not an ideal situation as their instruction emails are poor and confusing as one email mentions a code, then the other send a garbled email link to download mediafire.com/?4gdpmmohrb7mk74(cell unlockers.zip) if that helps
(it wont work as it connected remotely and requires credits to be pre-paid).

could youupload your full backup of the filesystem and see if it helps dagentooboy at all please? maybe he can compare a locked and unlocked firmware thats the same version.

tigger69 said:
could youupload your full backup of the filesystem and see if it helps dagentooboy at all please? maybe he can compare a locked and unlocked firmware thats the same version.
Click to expand...
Click to collapse
Really the firmware of any phone and the unlock code that goes with it would be a great place to start. I can always set up an emulator to run some of the files... if I figure out where they need to be.
EDIT: Thanks for the .zip .... I will try to figure out what they are doing.

also I am guessing that their program has to have adb compiled in. BTW that zip you sent me has a trojan in it... good thing I am only running windows in a VM

dagentooboy said:
also I am guessing that their program has to have adb compiled in. BTW that zip you sent me has a trojan in it... good thing I am only running windows in a VM
Click to expand...
Click to collapse
Yeah AVG was stopping it running originally properly, but after some googling it is a false positive it seems.
Sorry forgot to mention it.
TBH although mine did get unlocked, the process of using them is something I would not recommend to anyone, as mentioned already the email and instructions are hardly clear and the process is full of other little quirk.

any prgress on this ? i will soon be ordering an unlock because there seems to be no cheap solution available

hi....
when this project will be completed?
in my country unlocking this phone is costing me more then 100$.
plz help

Related

[REQ] Toshiba folio 100 BCT and partition dumps

I have somehow messed up my folio 100, and its BCT and bootloader information.
So im hoping someone else with little experience, knows how to use the nvflash utilities and dump the information for me and send me a link on where to get it.
the combo to get into bootloader mode is: POWER button pressed 4 times + VOL- key and it will go into bootloader mode.
I can extract these tomorrow evening.
Can you be clearer with the bootload sequence?
Tried to get the booload seq. Ended up with a partial reset of settings...
tshoulihane said:
I can extract these tomorrow evening.
Can you be clearer with the bootload sequence?
Tried to get the booload seq. Ended up with a partial reset of settings...
Click to expand...
Click to collapse
well, i dont think you should try it..!!
another user did, he ended up with a semi-bricked device too.. so thanks but now the fun stops.. it seems that Toshiba included a very,very bad key combo that terminates the device to a deadlocked machine..
so ill just figure out another way to get the partitions off it.. but my 4xpower + vol- is really scary, do NOT try it
at least until is cleared on how to get out of this bootloader state again.
I dumped the partitions which are visible from android already. Don't quite know what got resentment with your key sequence - DATA wiped? Some of the preloaded apps are broken now, but they were a bit broken before.
tshoulihane said:
I dumped the partitions which are visible from android already. Don't quite know what got resentment with your key sequence - DATA wiped? Some of the preloaded apps are broken now, but they were a bit broken before.
Click to expand...
Click to collapse
so you mean, you can extract all partitions from a shell?
ie. bootloader of partition2 and so forward?
i didnt notice that all 8 partitions were accessable there?
can you upload the dump of them somewhere?
A guy made the dumps of the ROM (not the recovery image though) on the forum of Frandroid DOT fr but I cannot post you the link directly here (anti spam as I do not have many messages on the forum).
I will PM you (if it allows me)
bootoo said:
A guy made the dumps of the ROM (not the recovery image though) on the forum of Frandroid DOT fr but I cannot post you the link directly here (anti spam as I do not have many messages on the forum).
I will PM you (if it allows me)
Click to expand...
Click to collapse
i have the dump of the /system i need all of the other partitions ie. 0 to 8
i cannot restore system, as i got no bootable tablet at all, i need raw partition dumps which i hope can be used using nvflash
Is it possible to extract opera mobile 10.1 apk?
toca79 said:
Is it possible to extract opera mobile 10.1 apk?
Click to expand...
Click to collapse
look for it here
Dexter_nlb said:
look for it here
Click to expand...
Click to collapse
Thx a lot found it.
I think the resolution is too high though.
Hi Dex, did you was able to restore your bricked folio?
roglio said:
Hi Dex, did you was able to restore your bricked folio?
Click to expand...
Click to collapse
decided to get another one..
ok!
I was hoping you did it because I'm a little tired of android (apple fan ).
My idea was to build and flash linux (ubuntu 10.10 works on toshiba AC100).
But if there isn't a way to restore the factory default (bootloader, etc.), I'll give up.
roglio said:
My idea was to build and flash linux (ubuntu 10.10 works on toshiba AC100).
Click to expand...
Click to collapse
when i was debugging bootloader configs, i was provided some config files that Ac100 users said would work on our folio, but i see now partition setup is very different, so we need to make proper configs for our folio before experimenting with the bootloader..
again, as you metion backup seems to do , when recover seems unavailable currently. it will be hard to verify if the parition table layout is working.
Hi,
sorry, maybe I missunderstood someting, but I cannot understand your problem in reading out the whole flash.
1. I have opened / disassembled my Filio 100. And like I have suspected there is a 16GB micoSD card connected (soldered) to the PCB and fixed with glue. One could read out the whole flash in a card reader.
2. You have fully access to the microSD card out of Android:
/dev/block/mmcblk0
sh-4.1# cd /dev/block
cd /dev/block
sh-4.1# pwd
pwd
/dev/block
sh-4.1# ls -l
ls -l
brw------- root root 254, 1 2010-12-07 08:46 dm-1
brw------- root root 254, 0 2010-12-07 08:46 dm-0
drwxr-xr-x root root 2010-12-07 08:45 vold
brw------- root root 179, 17 2010-12-07 08:45 mmcblk1p1
brw------- root root 179, 16 2010-12-07 08:45 mmcblk1
brw------- root root 7, 7 2010-12-07 08:45 loop7
brw------- root root 7, 6 2010-12-07 08:45 loop6
brw------- root root 7, 5 2010-12-07 08:45 loop5
brw------- root root 7, 4 2010-12-07 08:45 loop4
brw------- root root 7, 3 2010-12-07 08:45 loop3
brw------- root root 7, 2 2010-12-07 08:45 loop2
brw------- root root 7, 1 2010-12-07 08:45 loop1
brw------- root root 7, 0 2010-12-07 08:45 loop0
brw------- root root 179, 8 2010-12-07 08:45 mmcblk0p8
brw------- root root 179, 7 2010-12-07 08:45 mmcblk0p7
brw------- root root 179, 6 2010-12-07 08:45 mmcblk0p6
brw------- root root 179, 5 2010-12-07 08:45 mmcblk0p5
brw------- root root 179, 4 2010-12-07 08:45 mmcblk0p4
brw------- root root 179, 3 2010-12-07 08:45 mmcblk0p3
brw------- root root 179, 2 2010-12-07 08:45 mmcblk0p2
brw------- root root 179, 1 2010-12-07 08:45 mmcblk0p1
brw------- root root 179, 0 2010-12-07 08:45 mmcblk0
sh-4.1#
Regards, Artem
Hi DerArtem! Nice first post indeed!!!!
Thank you for your information.
A micro SD soldered is a nice gift from toshiba!!! This means upgrades, full dumps, etc.
Great
A request: could you please post some pictures?
DerArtem said:
sorry, maybe I missunderstood someting, but I cannot understand your problem in reading out the whole flash.
Click to expand...
Click to collapse
did i write i had problem dumping the entire mmc device? not really.
Yes, you misunderstood,Writing a proper cfg file describing the different areas is required.. dumping is easy part, documenting is harder..
but feel free to contribute and document the .cfg file for bootloader, that is of course appreciated...
I just got back from my business trip, and finally had some more time to take a closer look at the device.
roglio said:
Hi DerArtem! Nice first post indeed!!!!
Thank you for your information.
A micro SD soldered is a nice gift from toshiba!!! This means upgrades, full dumps, etc.
Great
A request: could you please post some pictures?
Click to expand...
Click to collapse
The device has a warranty seal inside. If you open the device completly the seal will break. I have just opened the device soo far, that the seal will not break. To make photos I will have to open it copletly. I will think about it....
Dexter_nlb said:
did i write i had problem dumping the entire mmc device? not really.
Yes, you misunderstood,Writing a proper cfg file describing the different areas is required.. dumping is easy part, documenting is harder..
but feel free to contribute and document the .cfg file for bootloader, that is of course appreciated...
Click to expand...
Click to collapse
Ok, I see. I have duped the mmc and mounted the partitions on my pc:
Here is the partition table on my PC:
Code:
[email protected] ~/bin/folio $ /sbin/fdisk -u -l folio.img
Platte folio.img: 15.9 GByte, 15920005120 Byte
1 Köpfe, 63 Sektoren/Spur, 493551 Zylinder, zusammen 31093760 Sektoren
Einheiten = Sektoren von 1 × 512 = 512 Bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Gerät boot. Anfang Ende Blöcke Id System
folio.img1 2048 526335 262144 83 Linux (/system)
folio.img2 526336 2623487 1048576 83 Linux (/cache)
folio.img3 2623488 2627583 2048 83 Linux (/misc)
folio.img4 2627584 31093759 14233088 5 Erweiterte
folio.img5 2628608 2644991 8192 83 Linux (???)
folio.img6 2646016 4743167 1048576 83 Linux (/data)
folio.img7 4744192 4754431 5120 83 Linux (???)
folio.img8 4755456 31093759 13169152 83 Linux (13G - storage)
Now you can mount the partitions on your pc:
Code:
sudo mount -o loop,ro,offset=$((512*2048)) folio.img /mnt/floppy/
I was not able to find the kernel or the bootloader or the root partition in the dump. I have also checked it with a hex editor.
Is the Folio using an other storage for kernel and bootloder? Does it have more NOR/NAND flash inside?
While looking at the size of the microSD (15920005120 bytes) I think that the bootloader is hiding a part of the microSD from the OS where the kernel and the bootloader are...
Where is the .cfg file you are talking about located?
DerArtem said:
Where is the .cfg file you are talking about located?
Click to expand...
Click to collapse
its a file assoiciated with the nvflash utility. search for the toshiba AC100 or here for more details for them it works fine.
the part 5 and 7 are boot kernel(8Mbyte) + recovery kernel(5Mbyte) , bootloader is as i know from ac100 on part0 , but thats not 100% yet.
Dexter_nlb said:
the part 5 and 7 are boot kernel(8Mbyte) + recovery kernel(5Mbyte) , bootloader is as i know from ac100 on part0 , but thats not 100% yet.
Click to expand...
Click to collapse
So, I have checked part 5 and 7. The content is the same like in boot.img and recovery.img. So the BCT is somewhere else...

[DEVS] Droid X2 CDT Table

Hello,
Here is something potentially useful for the devs.
I took some time the past few days to experiment a bit with my phone and work on my hexdump skills. After a few days, I came up with some interesting results which I think is worth posting.
CDT Table for Droid X2
After unpacking and experimenting a bit with the two SBF files for the DX2, I noticed an interesting pattern develop in CG3 (Code Group?). CG3 describes the CDT (Code Description Table?) which defines contents of the SBF file by each CG and where in flash memory space the CG is installed (I'd publish that too but I'm not trusting what Depacker 1.3 is telling me). I used the DX1 CDT file (found in CG31) as a reference but was hard since the format changed between the DX1 and the DX2. There is a pattern and here is what I currently have.
HTML:
CDT Entry # CDT Start Byte CDT Name CG# Signed Partition Location within Partition Signature Location Exists in SBF
1 0x0010 rdl.bin ? ? ? ? ? ?
2 0x0058 ptable 2 N ? 0x00000000 - 0x000057FF - Y
3 0x00A0 cdt.bin 3 Y mmcblk0p2 0x00000000 - 0x0007FFFF 0x0007F7FC - 0x0007FC52 Y
4 0x00E8 configtable 39 Y ? 0x00000000 - 0x002FFFFF 0x002FF7FC - 0x002FFC50 Y
5 0x0130 partitiontable 40 ? ? ? ? N
6 0x0178 bootloader 42 Y mmcblk0p1 0x00000000 - 0x002FFFFF 0x002FF7FC - 0x002FFC50 Y
7 0x01c0 mbr 45 ? ? ? ? N
8 0x0208 ebb 46 ? ? ? ? N
9 0x0250 microboot 47 Y mmcblk0p1 0x00300000 - 0x0037FFFF 0x0037F7FC - 0x0037FC52 Y
10 0x0298 pds 51 N mmcblk0p3 0x00000000 - 0x001FFFFF - N
11 0x02E0 ebr 52 ? ? ? ? N
12 0x0328 sp 53 ? ? ? ? N
13 0x0370 cid 54 ? ? ? ? N
14 0x03B8 misc 55 ? ? ? ? N
15 0x0400 logo.bin 56 N ? 0x00000000 - 0x00031FFF - Y
16 0x0448 kpanic 57 ? ? ? ? N
17 0x0490 recovery 58 Y mmcblk0p10 0x00000000 - 0x007FFFFF 0x007FF7FC - 0x007FFC52 Y
18 0x04D8 boot 59 Y mmcblk0p11 0x00000000 - 0x007FFFFF 0x007FF7FC - 0x007FFC52 Y
19 0x0520 system 60 N mmcblk0p12 0x00000000 - 0x1C1FFFFF - Y
20 0x0568 webtop 61 ? ? ? ? N
21 0x05B0 cdrom 62 N mmcblk0p14 0x00000000 - 0x013FFFFF - Y
22 0x05F8 cache 63 N mmcblk0p15 0x00000000 - 0x133FFFFF - N
23 0x0640 userdata 64 N mmcblk0p16 0x00000000 - 0x7FFFFFFF - N
24 0x0688 preinstall 65 N mmcblk0p17 0x00000000 - 0x12BFFFFF - Y
25 0x06D0 sdcard 66 N mmcblk1 - - N
I also tried to map the CGs to partitions in /dev/block. It some cases it was really simple especially since most of the bottom of the table is already mounted (adb shell cat /proc/partitions). The others I had to pull a data copy (e.g. adb shell su -c "dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard-ext/Dev/Partitions/mmcblk0p1.img"), copied the blocks to the computer and did hex compares for the first 0x300 or so bytes. In some cases (particularly mmcblk0p1 where the bootloader and the microboot are made one block together), two CG files are flashed onto one partition back-to-back. In that case I got a bit lucky with hex searching.
Things got more interesting when comparing SBFs of the DX2's sister phones (Atrix 4G and Photon 4G). It turns out not only the table is located in the same CG (CG3) but it also follows the same byte order. Either the names and CG numbers are slightly different (Atrix) or the table is identical to the DX2 with a few extra entries (Photon). Here is what I have.
HTML:
CDT Entry # CDT Start Byte DX2 CDT Name DX2 CG# Atrix CDT Name Atrix CG# Photon CDT Name Photon CG#
1 0x0010 rdl.bin ? rdl.bin ? rdl.bin ?
2 0x0058 ptable 2 ptable 2 ptable 2
3 0x00A0 cdt.bin 3 CDT.bin 3 cdt.bin 3
4 0x00E8 configtable 39 BCT.bin 42 configtable 39
5 0x0130 partitiontable 40 PT.bin 43 partitiontable 40
6 0x0178 bootloader 42 EBT.bin 44 bootloader 42
7 0x01c0 mbr 45 MBR.bin 45 mbr 45
8 0x0208 ebb 46 EBB.bin 46 ebb 46
9 0x0250 microboot 47 NVC.bin 47 microboot 47
10 0x0298 pds 51 PDS.bin 48 pds 51
11 0x02E0 ebr 52 EBR.bin 49 ebr 52
12 0x0328 sp 53 SP.bin 50 sp 53
13 0x0370 cid 54 CID.bin 51 cid 54
14 0x03B8 misc 55 MSC.bin 52 misc 55
15 0x0400 logo.bin 56 LOG.bin 53 logo.bin 56
16 0x0448 kpanic 57 KPA.bin 54 kpanic 57
17 0x0490 recovery 58 SOS.bin 55 recovery 58
18 0x04D8 boot 59 LND.bin 56 boot 59
19 0x0520 system 60 APP.bin 57 system 60
20 0x0568 webtop 61 OSH.bin 58 webtop 61
21 0x05B0 cdrom 62 CDR.bin 59 cdrom 62
22 0x05F8 cache 63 CAC.bin 60 cache 63
23 0x0640 userdata 64 UDA.bin 61 userdata 64
24 0x0688 preinstall 65 PIA.bin 62 preinstall 65
25 0x06D0 sdcard 66 SDC.bin 63 sdcard 66
26 0x0718 EBF.bin 64 gpt 67
27 0x0760 NVF.bin 65
Verification
One thought must be going through your head is "how is this single digit poster coming up with this stuff?" One, despite not being a true dev, I like looking at low level code and have some experience with it. Second, I encourage that someone takes the time verify my findings by replicating the methods I used as well as provide any thoughts on making low level hex analysis useful.
SBFs Used:
Droid X2: VRZ_MB870_DTN-14.8_1FF_01.sbf
Atrix 4G: OLYFR_U4_1.5.2_SIGNED.sbf
Photon 4G: 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM-release-keys-signed-Sprint-US.sbf
Procedure
- Take a SBF file
- Unpack using Moto Android Depacker 1.3
- Open CG3 in a hex editor (Hex Fiend is free for MacOSX)
- Find the location where an ASCII name starts (e.g. 0x0178 = bootloader, see tables above)
- Exactly 0x21 bytes from the start of the name is the CG value in hex
Thoughts
This analysis comes to mind two things:
1. A "Full" SBF does not mean it has all the partitions. - There is a possibility of bricking your phone beyond belief and even an SBF may not save you.
2. The DX2 seems to be really close to its siblings (Atrix 4G and especially Photon 4G). - I hate the idea gets thrown around of "Don't use Atrix mods unless you like bricks" without any real technical explanation as to why not. I'm not saying that people tomorrow should flash Atrix SBFs onto DX2 phones. I am saying that we (the DX2 community) should be aware and work closely with the other sister communities to know EXACTLY where the differences between the two phones lie. And hopefully the communities can contribute something that everyone can benefit (i.e. DX2 and Photon 4G ports of the Atrix bootloader unlock).
I'll experiment with a few other ideas I have in mind and I'll post them as I find something. Thanks for reading.
- mostKnownUnknown
As this makes no sense to me as a whole, I definetely agree with the similarity of Atrix and DX2.
I am guessing we could [somewhat] easily port the IHOP sbf unlock straight to our phone, and give us an unlocked bootloader.
Very thorough research! Well done!
religi0n said:
As this makes no sense to me as a whole, I definetely agree with the similarity of Atrix and DX2.
I am guessing we could [somewhat] easily port the IHOP sbf unlock straight to our phone, and give us an unlocked bootloader.
Click to expand...
Click to collapse
I doubt this quite a bit, as even the international version of the Atrix required a different SBF for IHOP, and with the X2, we're talking about different amount of RAM (which, coincidentally, was actually an issue with the international Atrix), and a different radio/chipset. However, it isn't a stretch to imagine that a couple of devoted devs could figure out a way to port the unlocked bootloader, especially since the Tenfar System Recovery worked with minimal modifications. So, hopefully.
jeffster888 said:
I doubt this quite a bit, as even the international version of the Atrix required a different SBF for IHOP, and with the X2, we're talking about different amount of RAM (which, coincidentally, was actually an issue with the international Atrix), and a different radio/chipset. However, it isn't a stretch to imagine that a couple of devoted devs could figure out a way to port the unlocked bootloader, especially since the Tenfar System Recovery worked with minimal modifications. So, hopefully.
Click to expand...
Click to collapse
I agree with you. Could we get a unlocked boot loader ported? Possibly but leaning into to the "won't work area".
The real problem is right now, the people with the know how either don't have a device to experiment with or they don't care/to frustrated with (motorola, the og x never being cracked), or they're just to interested in another device. For what ever reason, it seems like the heavy hitters are mostly just ignoring the X2, for now (hopefully).
Sent from my DROID X2 using XDA Premium App
religi0n said:
As this makes no sense to me as a whole, I definetely agree with the similarity of Atrix and DX2.
I am guessing we could [somewhat] easily port the IHOP sbf unlock straight to our phone, and give us an unlocked bootloader.
Click to expand...
Click to collapse
Yeah. Sorry if this seems a bit overwhelming. I'd figure to get the data out there first and generate some thoughts. Here's a little bit of background.
So memory in your phone is broken up into a number of partitions. This is much like how you would break up your hard drive into a number of partitions if you plan to install multiple OSes on to your computer. Instead, partitions on your phone are there to organize the data into groups for certain functionality.
If you have adb running, you can verify what partitions you have by running "adb shell cat /proc/partitions":
HTML:
./adb shell cat /proc/partitions
major minor #blocks name
179 0 7804416 mmcblk0
179 1 3584 mmcblk0p1
179 2 512 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 2048 mmcblk0p9
179 10 8192 mmcblk0p10
179 11 8192 mmcblk0p11
179 12 460800 mmcblk0p12
179 13 512 mmcblk0p13
179 14 20480 mmcblk0p14
179 15 315392 mmcblk0p15
179 16 2097152 mmcblk0p16
179 17 307200 mmcblk0p17
179 18 4574208 mmcblk0p18
179 32 7774208 mmcblk1
179 33 7773184 mmcblk1p1
Some partitions (particularly the bottom of the table) are easy to figure out since they are mounted when the operating system is run and you can open its file structure (usually with root).
HTML:
./adb shell mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext3 rw,relatime,data=ordered 0 0
/dev/block/mmcblk0p16 /data ext3 rw,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/mmcblk0p15 /cache ext3 rw,nosuid,nodev,noatime,nodiratime,data=ordered 0 0
/dev/block/mmcblk0p3 /pds ext3 rw,nosuid,noexec,relatime,data=ordered 0 0
/dev/block/mmcblk0p17 /preinstall ext3 ro,noatime,nodiratime,data=ordered 0 0
However, most of the partitions are not in a file format that you can mount. And it's hard to figure out that the partition is used for. Since access to the partitions are located in "/dev/block/", I've begun pulling partition images from the phone and trying some low level hex/byte analysis with our SBF's CG data.
For example, in the table from my first post, CG42 (bootloader) and CG47 (microboot) get flashed onto the same memory partition (mmcblk0p1). This has some weird complications which we need to be aware of. Both CG42 and CG47 are already signed. So when I analyzed mmcblk0p1, there are actually two sets of signature data in that partition. I'm not sure what the consequences are for messing with a double-signed partition but at least it's information that we can be aware of now.
As for the bootloader, I actually doubt we can do a direct port of the Atrix unlocker. I don't think it's a memory addressing issue (since most of the partitions have a fixed size and are filled with 0xFF blank data at the end if necessary). I think I'll be getting around the signature checking. If you open any of the bootloader unlock SBFs from Atrix's Project Pudding, all of them are signed and the signatures are not the same between the unlockers for Atrix ATT vs. Atrix Bell. Wasn't the unlock SBFs a leak from Moto's development servers? If so, since it came from Moto, I severely doubt that Moto would use the same private key between carriers, let alone between phones.
As a whole, I plan to learn as much about my phone as possible even if I need to delve down into byte data and assembly code. If we want an unlocked bootloader, I'm going to at least try to do something about it rather than sit on my butt and pray to the phone gods. If anything, we'll learn something new about this phone which is at least something since there is so little DX2 data out there.
I am in love with you bro.
If you get us an unlocked bootloader, I will give you $500 cash in person.
Sent from my ADR6350
Avelnan said:
$500 cash in person.
Click to expand...
Click to collapse
And you will have the love and admiration of hundreds of people.
Is there anything I can do to help in this process? I sort of followed what you saying...
Sent from my DROID X2 using XDA Premium App
Ihatepullups said:
Is there anything I can do to help in this process? I sort of followed what you saying...
Click to expand...
Click to collapse
Let's hack moto's servers and download all the development crap we can for the DX2! ;D
Kidding aside, I too also am wondering if there is anything I can do to help.
Edit: @Mostknownunknown How did you unpack the .sbf file? I can't figure it out..
0vermind said:
Let's hack moto's servers and download all the development crap we can for the DX2! ;D
Kidding aside, I too also am wondering if there is anything I can do to help.
Edit: @Mostknownunknown How did you unpack the .sbf file? I can't figure it out..
Click to expand...
Click to collapse
He Mentioned Something About Depacker 1.3.
0vermind said:
Edit: @Mostknownunknown How did you unpack the .sbf file? I can't figure it out..
Click to expand...
Click to collapse
Yeah. Sorry. It would be good if people knew how to get the tools.
After doing some plenty of google searching, Skrilax_CZ's SBF Depacker 1.3 works in unpacking SBFs from terga-based moto phones. Apparently, SBFs have been in use through the Moto RAZR days, but the format keeps changing. Skrilax_CZ's 1.3 version is the only one I know that works.
Since I can't post links yet:
modmymobile.com/forums/402-general-motorola-android/530781-sbf-depacker-1-3-03-22-2011-a.html
Any good hex editor is useful. I'm a Macbook Pro user so I've found Hexfiend. Google it.
0vermind said:
Kidding aside, I too also am wondering if there is anything I can do to help.
Click to expand...
Click to collapse
I have some ideas. But the more I'm researching Pudding, the more it seems impossible for a port. But I'll share my thoughts once I get out of work.
Hello again,
Here are some conclusions I came up when I researched Atrix Pudding:
1. Pudding bootloader has the component that issues the unlock command (fastboot oem unlock #).
2. The unlock command causes a "fuse" to be burned in the phone's hardware.
3. Pudding bootloader has the component that recognizes the phone as unlocked.
Here are my thoughts:
1. The Pudding bootloader can take in the phone id to issue the unlock. Whereas the DX2 bootloader has the command (fastboot oem unlock) but no implementation if you send it your phone id number (fastboot oem unlock #).
2. When the unlock is issued, a bit in your hardware changes. (Most people call it a "fuse". I think it's probably a small EEPROM since as a company, I would probably like to re-lock it if I could.) People who have worked on Pudding have found an indication to see if you are unlocked (see http://forum.xda-developers.com/showthread.php?p=16003820&highlight=fuse#post16003820). You can look up that same indication on the DX2 (adb shell, su, cat /sys/firmware/fuse/ReservedOdm) and mine reads 10000000000010001000100000000. I think this file is only a place holder for the fuse indications since overwriting it does not work.
3. I asked around if SBF-ing to original after unlocking re-locks you. Apparently, it sorta does and it sorta doesn't. SBF-ing to original after unlock removes the UNLOCKED at boot up and prevents you from flashing custom kernels and recovery. But when you re-flash Pudding again, the UNLOCKED appears and you can flash custom kernels and recovery without having to re-issue the unlock command (fastboot oem unlock #). This means that there is something in the Pudding bootloader which recognizes the unlock fuse.
This actually depresses me a bit. My initial thought about the bootloader is that the unlocked indication was held in a hidden partition that isn't SBFed. So if I verified the Atrix partitions before and after the unlock, I could determine what changed in a partition and attempt to apply the change to the DX2.
But since #2 is true and the unlocked indication is located external to the partition, the only way to unlock the DX2 is to feed the "fuse" component with the right commands to "burn". There's no coping a file/partiton that will give you the unlock.
#3 is interesting in that the bootloader needs to have the processing to test if you are unlocked and allow for the unlock. Which means that we need to mess with the bootloader in order to add this processing (since I'm pretty sure the DX2 bootloader doesn't have it). This was another item that I kinda wanted to avoid since I don't think we can easily inject new code into the bootloader because of the signature. Also, if we mess up with the bootloader partition, there is a strong possibility that the phone won't make it to the fastboot or rsd protocol setup and we'd be stuck with a hard brick.
I still have plenty of questions which are still good investigates/discussion points from here.
- What are the commands the bootloader gives to the "fuse" component to request an unlock?
- Is there a way to log/monitor bootloader commands?
- Can you instruct the "fuse" component a request for an unlock after the kernel is loaded? (Holy grail here - an APK-packaged unlocker)
- In the pudding bootloader, where is the check for the unlocked indication? (possible exploit to always indicate to the bootloader that the phone is unlocked without calling the external fuse check)
- Where in the DX2 bootloader does the signature check occur?
Again, I'm not a pure dev so I'm not thinking of implementation of anything here. I'm taking the academic approach of trying to discover some loophole and then asking a dev later to package and implement it. Also, I ask you to think and analyze for the sake of understanding our phone. The more info definitely helps no matter how little it is.
Thanks,
mostKnownUnknown
This is some great reading. Really, I love the research standpoint you are taking.
If I may comment, I do not think an APK packaged unlocker would be possible because the bootloader is called at system startup.
Just like if you have GRUB installed on your computer, you cant call GRUB to boot up to your Linux box from your windoze.
The ODM fuse is read at every boot. If you were to go into stock android recovery, it reads the ODM fuse. It says Reading ODM Fuse: 1.
I am not sure what that could mean, but maybe its a true/false indicator? As in if it Read the ODM Fuse as 0, we could be unlocked.
That is what I would have to say, nothing as much as you just my ideas.
There's gotta be an exploit or something that we can do, maybe some kind of code injection, something similar to 2nd-init, that allows some kind of injected code that loads our custom kernel. I flash a lot of phones for people. I've actually made it into a business here where I live, and one of the phones I flashed, the mytouch 4g, it initially wouldn't root, and I remember there was an update.zip exploit someone posted that you "flashed" in stock recovery and it would run a small exploit and open clockwork mod recovery, and it worked very well.
There's gotta be something, some kind of exploit. I used to do tons of programming in the past, I'm so not ready to let this one go. I know there has to be a way. Encrypted? Bullsh*t. Everything is hackable.
Thanks for your research though!! This is wayyyy interesting. I love it. I want to get my hands on an Atrix... haha.
religi0n said:
This is some great reading. Really, I love the research standpoint you are taking.
If I may comment, I do not think an APK packaged unlocker would be possible because the bootloader is called at system startup.
Just like if you have GRUB installed on your computer, you cant call GRUB to boot up to your Linux box from your windoze.
The ODM fuse is read at every boot. If you were to go into stock android recovery, it reads the ODM fuse. It says Reading ODM Fuse: 1.
I am not sure what that could mean, but maybe its a true/false indicator? As in if it Read the ODM Fuse as 0, we could be unlocked.
That is what I would have to say, nothing as much as you just my ideas.
Click to expand...
Click to collapse
I like where you are going with this, although that's not entirely true about not being able to call Grub from windows. You can tell the computer to reboot into Grub, but yeah you can't run grub on top of Windows.
Avelnan said:
I am in love with you bro.
If you get us an unlocked bootloader, I will give you $500 cash in person.
Sent from my ADR6350
Click to expand...
Click to collapse
There is a bounty thread here:
http://forum.xda-developers.com/showthread.php?t=1224166
At least $750 has been pledged already! Avelnan, can we add your $500 to the pot?
Spread the word!
Sent from my DROID X2 using Tapatalk
I think this thread needs to be bumped to the top. This has the potential to be a big help in the bootloader unlock process (if it happens).
I never even saw this thread! Where did this guy go? I could have sworn I saw him post recently!
AtLemacks said:
I never even saw this thread! Where did this guy go? I could have sworn I saw him post recently!
Click to expand...
Click to collapse
IDK. This was a hot topic for all of Aug then all the sudden nothing.
first of all bump!
second thanks for this I enjoy learning all this new information, anything else interesting you have to share you have found?

[EOS]-[ROM][4-august-12][PEN/WIFI/3G][JellyBean/411] DextersJB v1.5

ROM is discontinued for VIEW, use YNC's latest update
DextersJB​
i would test it out but i gotta charge my view its been dusty since i got my N7 lol
Thank you!
first.. thank you for trying to save VIEW.. there is no much going on here. but if you can save our dying VIEW, even slight attempt is greatly appreciated.
I will test this. I am kind of new on tablet but I will test and report back to you. here we go..:good:
Dexter_nlb said:
i would like to see if i can utilize the JB on View.
for this i have changed the kernel and partitions(removed those i do not know atm).
and uploading my test image for someone to test. Download it here MD5 06096eea121b5ec534830fcf97072fc4
HC hboot is required here, GB boot is not supported.
please if someone can help and test it, it will be great.
REMEMBER to factory reset, before installing this rom
I would also like to see a "mount" output run in as shell. so i know what partitions are different, besides /system i know for now.
Click to expand...
Click to collapse
myowin said:
first.. thank you for trying to save VIEW.. there is no much going on here. but if you can save our dying VIEW, even slight attempt is greatly appreciated.
I will test this. I am kind of new on tablet but I will test and report back to you. here we go..:good:
Click to expand...
Click to collapse
it if dos not boot at first try (showing a X after 20-30 seconds)..
maybe change the /system/build.prop in the zip.
replace everything you see in th build.prop with "flyer" with "express" .
save it and copy it back into the zip and replace the original one.
in the /system/lib/hw , rename files you see with "flyer" in the name, replace that with "express" too. ie lights.express.so
flash it once more and see if it helps.
Pulled, will try in about an hour when she charges back up. Apparently I left my wifi on..seems to drain a little more in ICS.
Will report back
Dexter_nlb said:
I would also like to see a "mount" output run in as shell. so i know what partitions are different, besides /system i know for now.
Click to expand...
Click to collapse
Code:
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p26 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p30 /data ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p31 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
/dev/block/mmcblk0p34 /devlog ext4 rw,nosuid,nodev,noatime,barrier=1,nodelalloc,data=ordered 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/data/d /data/d debugfs rw,relatime 0 0
/dev/block/vold/179:65 /mnt/sdcard2 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:36 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:36 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
and during installation:
Code:
AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers
ROM Name : FlyerJB-view
ROM Version : 1.0
ROM Author : dexter_nlb
Device : view/express-3g
Start at : Fri Jul 27 16:36:10 2012
script aborted: file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
Installer Error (Status 7)
End at : Fri Jul 27 16:36:10 2012
install finished, rebooted, stuck on white HTC bootscreen.
adb detects the device
Code:
$ ./adb devices
List of devices attached
HT16THY00941 device
but can't connect
Code:
$ ./adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
thanks,
just what i needed here.
Sounds cool. From what I have read we will lose Flash if we go to JB. Is this correct?
Stopping support for Flash by Adobe now in favor of HTML5 is sort of like closing all gas stations in favor of electric. Great idea, terrible timing. HTML5 is nowhere near ubiquitous.
** Ring up yncconsulting. I'm sure he would want to help on this.
boastt said:
and during installation:
Code:
AROMA INSTALLER version 2.00
(c) 2012 by amarullz xda-developers
ROM Name : FlyerJB-view
ROM Version : 1.0
ROM Author : dexter_nlb
Device : view/express-3g
Start at : Fri Jul 27 16:36:10 2012
script aborted: file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
file_getprop: failed to stat "/tmp/aroma-data/wipe.prop": No such file or directory
Installer Error (Status 7)
[/QUOTE]
can you replace META-INF\com\google\android\updater-script
in the zip you downloaded first with the updater-script in the zip attached to this post and try again.
the reboot is because it probably only wiped, but not unpacked anything to the partition.
Click to expand...
Click to collapse
Dexter_nlb said:
can you replace META-INF\com\google\android\updater-script
in the zip you downloaded first with the updater-script in the zip attached to this post and try again.
the reboot is because it probably only wiped, but not unpacked anything to the partition.
Click to expand...
Click to collapse
Done. Install went smooth. Theres a long delay waiting for a sim card, then the "Insert SIM card" shows up with a "skip" button.
Overall, it seems pretty solid for what it should be.
Compared to your thread for the flyer: mic doesn't work, GPS seems to not even exist on the device, using that UMS doesn' work, if scrolling in chrome is part of the 2d hardware acceleration then it feels slow
boastt said:
Done. Install went smooth. Theres a long delay waiting for a sim card, then the "Insert SIM card" shows up with a "skip" button.
Overall, it seems pretty solid for what it should be.
Compared to your thread for the flyer: mic doesn't work, GPS seems to not even exist on the device, using that UMS doesn' work, if scrolling in chrome is part of the 2d hardware acceleration then it feels slow
Click to expand...
Click to collapse
thanks for the confirmation, no matter if its good or bad.
i believe its possible to make a generic edition and let the installer detect which parts belong to which hardware.
ill look into that.
the hardware issues, probably relate to the files /system/lib/hw where light/sensor/gps is for the flyer and probably differ from the view edition.
for the mic part, i believe those files are for flyer, which needs to be view specific as well.
anyways, thanks, its good to know it can be made working on view as well.
quick search on google, shows that Chrome is not as fast as stock browser, which might be was regular chrome users experience? JB is new and not all apps are adapted? maybe thats why this keeps coming back as being a problem, but might not be a build problem, but Chrome being less compatible.
mitchellvii said:
Sounds cool. From what I have read we will lose Flash if we go to JB. Is this correct?
Stopping support for Flash by Adobe now in favor of HTML5 is sort of like closing all gas stations in favor of electric. Great idea, terrible timing. HTML5 is nowhere near ubiquitous.
** Ring up yncconsulting. I'm sure he would want to help on this.
Click to expand...
Click to collapse
You can still use flash. You just cannot download it from the market but the ICS version works just fine.
In what ways is JB significantly better than ICS or GB in order to sacrifice some functionality to run it in your opinion? Not snarking here - I really would like to know.
In my personal experience, GB on this tablet is just fine. It can be overclocked and everything works, but of course I'd love the latest and the greatest if there is some noticeable performance pop.
"Not snarking here" - ehum.
mitchellvii said:
In what ways is JB significantly better than ICS or GB in order to sacrifice some functionality to run it in your opinion? Not snarking here - I really would like to know.
In my personal experience, GB on this tablet is just fine. It can be overclocked and everything works, but of course I'd love the latest and the greatest if there is some noticeable performance pop.
Click to expand...
Click to collapse
its all just a challenge and development tests/teasers.. for some it can easily be a daily driver, for others too much is definately not working.
I do not have it for the pen, so thats no priority personally.
but media playback for me, can be important, for now i just switch to SD when im on youtube.
but generally, there is alot of difference in the drivers and how framework and JB differs, i do not want to repeat , but it is for better, if just we can make more work better.
JB/ICS is alot better experience especially comparing our less good HC adaption.
JB kills GB. i'm running JB on my nexus and it's SO quick!
thanks for your hard work here, i hope we can get something running! we sort of have an ICS rom, but JB is what ICS should have been from the start..i'm pumped!
Yeah HC was pretty lame. Its really too bad the way HTC just completely abandoned what was an expensive device at the time.
I have a pen but really don't use it much anymore anyway. 7 inch tablet is just a little too small to comfortably write on anyway. I guess for me fast internet browsing and solid Netflix are the most important things.
Sent from my SPH-D710 using Tapatalk 2
Great work. I'm interested in testing once I can flash in a normal fashion (not sure how to switch out the zip file etc.)
Sent from my PG41200 using xda app-developers app
Thanks for the development of JB on the view, been thinking of trying to port some of the roms from the flyer lately. I'm not much of a developer so the fresh thread here is greatly appreciated.
Sent from my PG86100 using xda app-developers app
Runs great so far! A few minor issues but won't take much to iron out.

Cannot connect to PC, internal storage unavailable, SD card damaged

Device: Arnova Gbook (ereader)
OS: Android 4.0.3
Kernel version: Linux 3.0.8
I was using my tablet at an airport and everything was fine before I shutoff my phone for the flight to take off. I turned it back on once the plane reached cruising altitude. I got an indicator that my SD card was damaged, which makes no absolutely no sense. also, my apps disappeared...
Problems are:
-When I connect to PC, tapping "Turn on USB storage" nothing happens, only the lile circle indicates that it is doing something but it does nothing...
-Settings>Storage: "Unfortunately, Settings has stopped."
next to the clock it says "Damaged SD card. SD card damaged, you may have to reformat it." There is not SD card in the slot, but it still says this.
-Cannot push an SD card into the slot: It doesnt stay there even if i push it to the maximum inside. No "click sound" either.
-Cant do anything only using the internet, internal storage is not reachable in any way thus i cant install newer rom too.
Did a factory reset (Settings>factory reset) but couldnt help, still the same... I beg you guyz for your help!
Anyone?
up
...having the Same Problem
dyingsoulwow said:
up
Click to expand...
Click to collapse
So it looks like I'm having the same problem with the same gear. I tried several cures to no avail.
But First the Tech Specs of my Arnova GBook:
Manufactor: VIMICRO
Model: ANGB
CPU: ARMv 7 rev 2 (v7l)
Memory: RAM 337, ROM 0.91, SDCard 0 MB (at the Moment more to that later)
Android: 4.0.3
BuildID: generic_vortex-userdebug 4.0.3 IML74K 1.0 test-keys
Linux Version: 3.0.8-vimicro([email protected]) (gcc Version 4.4.3)
I copied some files to the mounted exSDCard (4gb noname) when my tablet suddenly died and the only way to reanimate it was by factory resetting it.
The Problem istself seems to relate to the inability to mount a Nonformated SDCard that i can not format because it is not proberly mounted.
I have no clue how to root the tablet. I tried a set of instruction from a french website, but since i don't speak french i'm not sure if the google translator gave me the right directions.
I tried to mount it the SDCard via terminal. Format it connecting the gbook to an ubuntu box and a lot of system tools available via googles play store.
USB connection shows the drives but I'm not abel to mount or list the contents of it. In general the System is booting up and i am able to install apps from Google Play. Since i can't mount any external devices i am not abel to transfer files via other means because the gbook wants to copy them to the interna SDCard (wich is not available ).
I am looking for any possible solution. If there is an alternate Frimware i will try it.
Thanks in advance for any offered Help!
Lanman99
Still trying...
Any solution i found using Google, Bing and DuckDuckGo seems to require Root Access. Has somebody successfully rooted an Arnova GBook?
Or is there really no possibel solution for a dummy user to fix this problem. It seems to boil down that i cannot mount device mmcblk0 to sdcard because "access denied".
Did anybody face a similar problem and fixed it without root?
Tried several SDCard tools to no avail...
ES File Explorer is showing me that everthing i need is there but still, every try to mount the internal storage is leading to permission denied. I'm stating to love Android
Well if there is no root, is it possible to write a shell script to revive the internal SDCard and run that with elevated rights?
ES File manager is showing the directory entry with 0 MB. Since i am a novice in Android Systems i am just not sure if that means anything.
Maybe i'm wasting my time on a piece of chinaware but this nut i still too tempting to ignore. It's just that with my limited Linux knowlegde it seems that mounting a device and formating it afterward sounds not to troublsome or am i completely lost. After asking Google, bing and some other SEs it is not that uncommon but none of the cures i found worked for my GBook.
What am i missing?
Stil no answer from Arnova on my request for a stockrom Download. Somebody got an Idea where elsee i could find a ROM image for an Arnove GBook or does anybody know if there is an alternative Firmware available?
I was able to connect to my Device via ADB
mount is delivering the following:
rootfs on / type rootfs (ro,relatime)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
ubi0_0 on /system type ubifs (ro,noatime,no_chk_data_crc,compr=lzo)
ubi1_0 on /data type ubifs (rw,nosuid,nodev,noatime,bulk_read,no_chk_data_crc,compr=lzo)
ubi2_0 on /cache type ubifs (rw,nosuid,nodev,noatime,bulk_read,no_chk_data_crc,compr=lzo)
none on /proc/bus/usb type usbfs (rw,relatime,devmode=666)
The list under /dev/block/vold has three entries:
179:0 179:1 and 7:0
Cat /proc/partitions delivers:
31 0 10240 mtdblock0
31 1 12288 mtdblock1
31 2 120832 mtdblock2
31 3 45056 mtdblock3
31 4 524288 mtdblock4
31 5 1048576 mtdblock5
31 6 262144 mtdblock6
31 7 2169856 mtdblock7
179 0 3909632 mmcblk0
179 1 3905536 mmcblk0p1
Please I am a complete Android Noob. Is there somebody able to guide me to a Point where i can start to patch all this together.
I am able to find pieces here, but i'm not getting the broad picture.
Next try...
using Root Many by Bin4ry http://forum.xda-developers.com/showthread.php?t=1886460 to get into my device I got following results:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (20.04.2013) v29 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-dr
ivers are installed correctly!
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Above file not found warning ARE NOT ERRORS, it is intended to be this way!
Normal Mode enabled!
.
Pushing busybox....
2207 KB/s (1085140 bytes in 0.480s)
Pushing su binary ....
2185 KB/s (380532 bytes in 0.170s)
Pushing Superuser app
2309 KB/s (1468798 bytes in 0.621s)
Making busybox runable ...
.
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
After reboot the gbook is throwing "unfortunately UI has stopped" and "unfortunately settings has stopped". Nothing works until i factory reset it again (at least something i am growing really good at) and I'm back to square one.
Other means of editing files within the system via ADB are only leading to access denied or system is in read only mode.
Any other ideas?
By using Archtablet.com's method: "http://www.arctablet.com/blog/forum/firmware-development/dumping-firmware-on-arnova-g2-arnova-g3-and-other-rockchip-based-tablets/" i tried to get an Firmwareimage. They tried to Help me out but again disaster struck. Ubuntu 13.04 with usblib installed failed to even recognize the GBook. Trying it with Windows and adb i need (what a surprise) root rights.
So next question is: Is there any general way to read out a tablet firmware without rooting or is it always up to the vendor to just screw things to their Liking ?
I know i should quit this beast, but stubborn as ever i keep banging my head against the wall .
Lanman99

[ROM][PORT][JB 4.1.2] Nabixus 0.1beta for Nabi 2

This is a port of stock the Nexus7 (Grouper) 4.1.2 ROM with the Nabi 2 OTA 2.4.6 as the base. Everything seems to be working but as the title says it is a beta and so not fully tested....FLASH AT YOUR OWN RISK!!!!
Couple of things to be aware of: You have to update some of the apps before they work (Chrome for instance) and when adjusting the brightness it is possible to turn the screen all the way black, don't panic, just slide it back to the right...oh, and if you try to skip turning on the wifi it still tries to connect but it will eventually time out. If anyone actually uses the Nabi camera I have found that the Nexus 7 Camera app from the play store will work, other ones might also but I tested that one. There are no HDMI settings right now because the Nexus didn't have that port but the HDMI does work.
Screenshot:
{
"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"
}
Instructions:
1. Make a full TWRP backup to external sdcard!!! AND make sure your backup works!!!
2. Download the zip and place it on your external sdcard.
3. Wipe everything except external sdcard.
4. Install the zip.
5. Wipe cache and davlik again for good measure.
6. Reboot and do a little happy dance!!! (First boot takes a while so don't freak after 30 secs, lol)
Download: Nabixus_beta0.1.zip , Mirror1, or Mirror2
MD5: b334707cf14b2ad4e552d6a7a3b48fcd
Let me know what you think, I know there's room for improvement....and I'll fix this post up some at some point, give me a break it's my first time!!
reserved
reserved 2
First! LOL. Glad you got it going. If you need any help or any stock files from my newly acquired Nexus 7, let me know. I can make a complete nandroid if needed.
Additional screenshots!
Can't spend too much time fooling around with it before the kids get up, but looks good for now! Thanks for the awesome work!
Just to report, all is well with the port. Just getting a bit of screen flicker but that is due to the low brightness level. It has gone away since I have raised it up all the way. All apps updating fine via Playstore and OTG USB working great as well. Side loading a lot of what I call my "Power Rooting Apps". This reminds me of the nexus 7 I just got LOL. Great job!
Dude! YOU ROCK....
Now when my son upgrades, I'll be able to use the nabi for kodi (xbmc) on the tv.
Sent from my Nexus 7 using Tapatalk
Awesome, can't wait till I have a moment free to give this a try!
Sent from my Nexus 10 using Tapatalk
@n3wt GREAT job, just wanted to know if I build CyanogenMod for Nexus 7 2012; could you port CyanogenMod over to Nabi?
katinatez said:
@n3wt GREAT job, just wanted to know if I build CyanogenMod for Nexus 7 2012; could you port CyanogenMod over to Nabi?
Click to expand...
Click to collapse
I've been trying to port CM the past few days and keep getting stuck at a never ending boot animation. So yeah, if you guys could give it a shot that would be great, lol.
katinatez said:
if I build CyanogenMod for Nexus 7 2012; could you port CyanogenMod over to Nabi?
Click to expand...
Click to collapse
maybe. aicjofs suggested that the kernel might be too different though. I have a cm with tablet ui for the Nexus that I was looking at but I'm toying with the idea of trying to get a working kernel compiled. ... That way we could just build a rom for the nabi.
It took a lot of hours to get to this point though so whatever comes next will be after a bit of rest.
I'm really happy that you guys are liking this one, feel free to take it and mod it and what not.
SMcC2 said:
I've been trying to port CM the past few days and keep getting stuck at a never ending boot animation. So yeah, if you guys could give it a shot that would be great, lol.
Click to expand...
Click to collapse
Do you have adb working?
ROFL
Anyone else get the email
"Hello from Google: Get the most out of your Nexus 7" ?
n3wt said:
Do you have adb working?
Click to expand...
Click to collapse
I had it working at one point, but don't remember how I had gotten there.
I've been using these links as resources:
How to Build CyanogenMod for Grouper
How to Port CyanogenMod to new Devices
Kernel Building for CyanogenMod
The instructions for building on Grouper say to pull the proprietary blobs from a device with CyanogenMod already installed. I don't have that option.
Note:
Your device should already be running a build of CyanogenMod for the branch you wish to build for the extract-files.sh script to function properly. Nexus users: While it maybe be tempting to run the script on stock Android, and in fact it may succeed, realize that some of the blobs CyanogenMod uses are modified or otherwise different from stock blobs (e.g. Adreno graphics libraries). Save yourself some trouble and install a copy of CyanogenMod on your device before extracting blobs.
Click to expand...
Click to collapse
The instructions for porting to new devices says
Create extract-files.sh and setup-makefiles.sh scripts to pull those blob files from the device using adb and put them in the right /vendor/ directory. There are plenty of examples available for other devices.
Create an .mk Makefile to copy those files to the $OUT folder during the build process and put them in the right place. Again, use other devices as a guide for what this Makefile should look like. An example filename might be BoardConfigVendor.mk
Make sure that the Makefile you just created is included from your main BoardConfig.mk via a command such as -include vendor/[vendor]/[codename]/BoardConfigVendor.mk. Again, existing devices can illustrate how this is done.
Click to expand...
Click to collapse
I don't think I'm getting everything when I do that and that's where my problem is...
maybe. aicjofs suggested that the kernel might be too different though.
Click to expand...
Click to collapse
The Nabi kernel should be based on AOSP, so that is the best ROM's to work with for best compatibility. AOKP, and CM being there own breed might need some kernel mods. For example on current Qualcomm devices CM is using CAF code and AOSP is using google kernel code. Just an example
Anyone else get the email
Click to expand...
Click to collapse
Could be this in build.prop.
ro.build.fingerprint=google/nakasi/grouper:4.1.2/JZO54K/485486:user/release-keys
or a special bit of code in email program.
Create extract-files.sh and setup-makefiles.sh scripts to pull those blob files from the device using adb and put them in the right /vendor/ directory. There are plenty of examples available for other devices.
Click to expand...
Click to collapse
Yeah you have to do it all manually(make proprietary-files.txt). I did it once but it was all manual, and I could have missed something, it took hours. I also remember having a failure pulling the firmware files in the /vendor directory. You can look at what I did in attached
@n3wt You should write up some of your secret sauce, would help those guys mimic what you did on other ROM's
aicjofs said:
Yeah you have to do it all manually(make proprietary-files.txt). I did it once but it was all manual, and I could have missed something, it took hours. I also remember having a failure pulling the firmware files in the /vendor directory. You can look at what I did in attached
Click to expand...
Click to collapse
I was afraid it might have to be done manually.
SMcC2 said:
I've been trying to port CM the past few days and keep getting stuck at a never ending boot animation. So yeah, if you guys could give it a shot that would be great, lol.
Click to expand...
Click to collapse
Same here LOL. I have been trying to port CleanRom 4.0.0 JB 4.3 from my Nexus 7 but am stuck at the 4 rotating orbs. I have the boot image decompiled and the complete System files from my Nexus 7 if anyone would like to give it a try.
aicjofs said:
@n3wt You should write up some of your secret sauce, would help those guys mimic what you did on other ROM's
Click to expand...
Click to collapse
Yes please, I have dissected the rom to see the differences and have gotten as far as I have so far. It is very time consuming for sure. I have 4.1.2 Modded to the bone at the moment.
In case anyone wants the info:Off my Nexus 7 Running CleanRom 4.0.0 4.3 JB.
Code:
(dev/block/platform/sdhci-tegra.3/by-name)
[email protected]:/ $ cat /proc/partitions
cat /proc/partitions
major minor #blocks name
7 0 2111 loop0
7 1 11466 loop1
7 2 9387 loop2
7 3 4190 loop3
7 4 28098 loop4
7 5 61362 loop5
7 6 8348 loop6
7 7 53046 loop7
179 0 31178752 mmcblk0
179 1 12288 mmcblk0p1
179 2 8192 mmcblk0p2
179 3 665600 mmcblk0p3
179 4 453632 mmcblk0p4
179 5 512 mmcblk0p5
179 6 10240 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 512 mmcblk0p8
179 9 30014464 mmcblk0p9
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
254 0 2110 dm-0
254 1 11466 dm-1
254 2 9387 dm-2
254 3 4189 dm-3
254 4 28098 dm-4
254 5 61362 dm-5
254 6 8347 dm-6
254 7 53046 dm-7
7 8 2111 loop8
254 8 2110 dm-8
=============================================
[email protected]:/ $ ls -al /dev/block/platform/sdhci-tegra.3/by-name
ls -al /dev/block/platform/sdhci-tegra.3/by-name
lrwxrwxrwx root root 2014-10-04 12:29 APP -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-10-04 12:29 CAC -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-10-04 12:29 LNX -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-10-04 12:29 MDA -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-10-04 12:29 MSC -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-10-04 12:29 PER -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-10-04 12:29 SOS -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-10-04 12:29 UDA -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-10-04 12:29 USP -> /dev/block/mmcblk0p6
[COLOR=Red]=============================================[/COLOR]
[COLOR=DarkRed][B]( fstab.grouper )[/B][/COLOR]
[COLOR=Red]==================================[/COLOR]
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 noatime,nodiratime,nodev,noauto_da_alloc wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nodiratime,nosuid,nodev,data=writeback,noauto_da_alloc,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nodiratime,nosuid,nodev,data=writeback,noauto_da_alloc,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci /storage/usbdisk vfat defaults voldmanaged=usbdisk:auto
[COLOR=Red]---------------------------------------------[/COLOR]
[B][COLOR=DarkRed]( fstab.grouper~ )[/COLOR][/B]
[COLOR=Red]-------------------------------------[/COLOR]
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA
/dev/block/platform/sdhci-tegra.3/by-name/MSC /misc emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/LNX /boot emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/SOS /recovery emmc defaults defaults
/dev/block/platform/sdhci-tegra.3/by-name/USP /staging emmc defaults defaults
/devices/platform/tegra-ehci /storage/usbdisk vfat defaults voldmanaged=usbdisk:auto
SMcC2 said:
I was afraid it might have to be done manually.
Click to expand...
Click to collapse
Well look over the zip I posted maybe it can save some time.
DarkAngel said:
Same here LOL. I have been trying to port CleanRom 4.0.0 JB 4.3
Click to expand...
Click to collapse
Above 4.2 you will need SElinux support in kernel, so I don't 4.3 is going to work.
aicjofs said:
Well look over the zip I posted maybe it can save some time.
Above 4.2 you will need SElinux support in kernel, so I don't 4.3 is going to work.
Click to expand...
Click to collapse
I know but I had to try.
You think I could just ls the vendor file and copy it in to a text file with the right format?
Here is an example from my HTC...
[email protected]:/ $ cd system
[email protected]:/system $ cd vendor
[email protected]:/system/vendor $ ls */*
etc/audio_effects.conf
firmware/acdb.mbn
firmware/apps.mbn
firmware/bcm4335_prepatch.hcd
firmware/dsp1.mbn
firmware/dsp2.mbn
firmware/dsp3.mbn
firmware/efs1.mbn
firmware/efs2.mbn
firmware/efs3.mbn
firmware/htc61.mbn
firmware/htc62.mbn
firmware/htc63.mbn
firmware/htc64.mbn
firmware/htc65.mbn
firmware/htccdma.mbn
firmware/htcnvbak.mbn
firmware/htcrcust.mbn
firmware/htcrfnv.mbn
firmware/htcsmem.mbn
firmware/htcssmem.mbn
keymaster.b00
keymaster.b01
keymaster.b02
keymaster.b03
keymaster.mdt
firmware/mdm_acdb.img
firmware/q6.b00
firmware/q6.b01
firmware/q6.b03
firmware/q6.b04
firmware/q6.b05
firmware/q6.b06
firmware/q6.mdt
firmware/rpm.mbn
firmware/sbl1.mbn
firmware/sbl1_82.mbn
firmware/sbl1_92.mbn
firmware/sbl1_96.mbn
firmware/sbl2.mbn
eglsubAndroid.so
libEGL_adreno.so
libGLESv1_CM_adreno.so
libGLESv2S3D_adreno.so
libGLESv2_adreno.so
libq3dtools_adreno.so
power.msm8960.so
lib/libC2D2.so
lib/libQSEEComAPI.so
lib/libRSDriver_adreno.so
lib/libWVStreamControlAPI_L1.so
lib/libadreno_utils.so
lib/libbt-vendor.so
lib/libc2d30-a3xx.so
lib/libc2d30.so
lib/libgsl.so
lib/libllvm-a3xx.so
lib/libqc-opt.so
lib/librs_adreno.so
lib/librs_adreno_sha1.so
lib/libsc-a3xx.so
lib/libwvm.so
detection
recognition
[email protected]:/system/vendor $

Categories

Resources