Hi
I've finished fully automatic unbricker for Sony Xperia Tablet S!
Code:
It wouldn't be possible without xda users, xda community, especially:
deltaztek [SD source],
jappaj [shell access],
NerdiX [beta tester],
and all other users, who helped to get it working!
Source thread where manual solution has been discovered.
Ladies & Gentlemen...
S.onyXT.S [UNBRICKER] !
[What is this?]
S.onyXT.S [UNBRICKER] will unbrick your device firmware,
no need any shell/linux knowledge - step by step, everything automatic.
It will automatically download needed data.
Unbrick process includes:
downloading "magic SD" prepared image (237mb),
downloading proper update data,
decrypting, extracting update data,
auto making "magic SD" - no need win32imager etc.,
uploading update data to device,
at last - unbricking device - flashing system/hidden partitions.
[Requirements]:
- internet connection to download data ,
- adb drivers correctly installed,
- min. 2GB SD card.
[Changelog]:
Code:
[09.02.2014] v1.0:
- initial version.
[To-Do]:
Code:
- datapp flashing - vendor apps fix,
[Screenshots:]
{
"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"
}
[Download]:
Attached to this thread.
[Donate]:
Keep this project alive - don't forget to donate!
br
condi
current_version=1.0
LEGEND ONCE AGAIN....
If only we had something for out older Tabs
Oh well none the less one more step in the right direction
stifilz said:
LEGEND ONCE AGAIN....
If only we had something for out older Tabs
Oh well none the less one more step in the right direction
Click to expand...
Click to collapse
@condi i have a problem and a question....first the question...why when i type the letter in upper case the tools reboot? and when i type il lower case it say unity doesn't specified....but it continue ....how i must put the letter in up or lowercase? and i'm waiting the cold-booting write but it doesn't appear how much it will take?
masterchif92 said:
@condi i have a problem and a question....first the question...why when i type the letter in upper case the tools reboot? and when i type il lower case it say unity doesn't specified....but it continue ....how i must put the letter in up or lowercase? and i'm waiting the cold-booting write but it doesn't appear how much it will take?
Click to expand...
Click to collapse
hi masterchif,
you type drive letter only? or with ":" ?
br
condi
condi said:
hi masterchif,
you type drive letter only? or with ":" ?
br
condi
Click to expand...
Click to collapse
Only che letter in lowercase ....is important if it is in lower or upper? My tablet is brick I think is stopped in Sony logo....u can help me ? I bricked it while trying to install jb from tool flasher but something went wrong
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
Only che letter in lowercase ....is important if it is in lower or upper? My tablet is brick I think is stopped in Sony logo....u can help me ? I bricked it while trying to install jb from tool flasher but something went wrong
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
I've just tried - it worked well. No matter if its uppercase or lowercase - it worked well for me.
What windows version you have?
The only problem occured, when I had opened windows explorer, with sd card opened,
or even with my computer - sd card volume became busy, and unbricker couldn't write.
But to get it work - you have only to close all explorer windows.
Could you make screenshot of the issue?
It write on SD but the problem is when I wait for cold boot....I'll wait 1 hrs and it doesn't appear..... My PC says unknown device and the tablet with the SD on stop on Sony logo no cold-booting write
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
It write on SD but the problem is when I wait for cold boot....I'll wait 1 hrs and it doesn't appear..... My PC says unknown device and the tablet with the SD on stop on Sony logo no cold-booting write
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
Wait wait, what tablet model/version exactly you have?
WiFi tablet s , abile tryng ti install JB i got an error and when it reboot it stays on Sony logo then I try your tools only recovery mode
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
WiFi tablet s , abile tryng ti install JB i got an error and when it reboot it stays on Sony logo then I try your tools only recovery mode
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
I'm sorry but solution is ONLY for 2nd tab gen - XPERIA TABLET S!
br
condi
O....sorry....but u can help me? I have problem with checking region ...I download 001 version that is mine but gives me always SKU error
Inviato dal mio Nexus 5 utilizzando Tapatalk
masterchif92 said:
O....sorry....but u can help me? I have problem with checking region ...I download 001 version that is mine but gives me always SKU error
Inviato dal mio Nexus 5 utilizzando Tapatalk
Click to expand...
Click to collapse
You have softed bricked your device by trying to install jb to your device
Reading is your friend google even more so
This recovery is for the xperia tab s not for the first sony tab s
By trying to install a firmware that does not fit your device nor has it ever
Next time try reading a little bit about the tools you are about to use on your device and what is needed
The sku error is because the device thinks the firmware your trying to flash is the same as the one previous an a conflict arises
So far there is no known recovery from this other than an offical sony repair centre
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
dex9mm said:
You have softed bricked your device by trying to install jb to your device
Reading is your friend google even more so
This recovery is for the xperia tab s not for the first sony tab s
By trying to install a firmware that does not fit your device nor has it ever
Next time try reading a little bit about the tools you are about to use on your device and what is needed
The sku error is because the device thinks the firmware your trying to flash is the same as the one previous an a conflict arises
So far there is no known recovery from this other than an offical sony repair centre
xperia m c1905 stock rooted lb
and sony XTS rooted stock j.b thanks djrbliss
Click to expand...
Click to collapse
I see it now.....very disappointed with Sony.... I'll never buy a Sony tablet or smartphone !!! Now I try two more firmware but if I flashed the xperia tablet s in a tablet s I don't think that I can recover it right ?
Inviato dal mio Nexus 5 utilizzando Tapatalk
condi said:
Hi
I've finished fully automatic unbricker for Sony Xperia Tablet S!
[To-Do]:
Code:
- datapp flashing - vendor apps fix,
br
condi
current_version=1.0
Click to expand...
Click to collapse
hello friend
I saw that you removed the datapp lines in the script
as I wrote in the other topic, links to vendor directory are for a specific country
Sony factory script at first startup wants to choose country then obviously resets symlinks for specific directory.
Now my IR works with Panasonic and other tv... ir database seems well
I must clarify that after the manual procedure in dd mmcblk0p3(and 4), the tablet is not updating correctly in recovery. He wrote in mmcblk0p3 and mmcblk0p9 (vendor0 only), then check passed correctly.
Whether updating with jbr1 or jbr2 file is getting the same result, booted the system1 from mmcblk0p4 with jbr1 (not r2), i.e. not been updated, and sonys app not worked.
I had to dd if=/dev/block/mmcblk0p3(updated thru recovery) of=/dev/block/mmcblk0p4 to be the same, read the post of @jappaj to fix datapp symlinks, then the update went correctly thru recovery from jbr1 to jbr2
EDIT: maybe /data partition (/dev/block/mmcblk0p11) must be formated (factory reset) to triger sony's script to ask for country and autoset correct symlinks
I am waiting for tablet P unbricker release.
i beg you for same tool, but for tablet S !!))
im getting invalid drive specification
what does that mean
this dd.exe did not work as expecded. same problem on my win7 laptop
I have mostly rewritten the script for bash / linux shell
IT WORKED
THANKS @condi
PS: why not trying to use the SD-image to flash KitKat?
i mean, you can pull all mmc images and flash all mmc images via dd, why not writing a custom rom this way? the only problem is the kernel.
mounts of /dev/block/*
mmcblk0p1 -> /configs
-r--r--r-- 1 root root 64 Jan 1 2000 06590E37F8A647D989345317AAFF6A6C
-r--r--r-- 1 root root 242 Jan 1 2000 31850B1B-0DAB-42ce-A498-A73479B7B3EB
-r--r--r-- 1 root root 878 Jan 1 2000 calibration_rear.bin
-r--r--r-- 1 root root 63104 Jan 1 2000 CFBSMXHMUAF48EXTDTCSOH4BXXDDRBFG
-r--r--r-- 1 root root 132 Jan 1 2000 local.propmmcblk0p2 -> /params
-rw------- 1 root root 2 Jan 30 14:43 activate_done
lrwxrwxrwx 1 root root 57 Jan 30 14:43 countries.lst -> /datapp/vendor/vendor0/regioncodelist/SKU002000172608.lst
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 33 Jan 30 14:43 region_checksum.txt
-rw-r--r-- 1 root root 9706 Jan 30 14:43 region.zip
-rw-rw-rw- 1 root root 2 Jan 30 14:43 selected_countrymmcblk0p3 -> /system
mmcblk0p4 -> /system (copy)
mmcblk0p5 -> /cache
(ls /cache/recovery)
-rw-r--r-- 1 root root 45 Jan 1 2000 last_install
-rw-r----- 1 root root 22626 Jan 1 2000 last_log
-rw------- 1 stth stth 18769 Jan 1 2000 logmmcblk0p6 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p7 -> not mounted (64MB, file system?, image not mountable as loop device)
mmcblk0p8 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p9 -> /datapp (vendor)
mmcblk0p10 -> /log
-rw-r--r-- 1 root root 18652 Jan 1 2000 recovery_abort.logmmcblk0p11 -> /data
judging the size of the unknown partitions, mmcblk0p7 could contain the kernel. probably we just have to find the file system on this partition. i guess, sony just skips a part or descrambles the partition while it shows the sony logo (which is always displayed, no matter if you boot into recovery, or the system) also, the hidden.img is flashed there... so... how to get it out?
what are the files in /configs? maybe keys or executables to decrypt the kernel?
does anybody have a log of a successful update in the logs (see mount list above)? is there any information about an updated kernel?
to get the mmc-images, just create the unbricker sd card (it does not break anything if you stop the script after the sd is written)
execute adb shell "/system/xbin/pwn"
then adb pull /dev/block/mmcblk*
on linux, you can mount them with
mount -o loop <image> <mountpoint>
some require root to view files
if anything is broken, we should be able to reflash all mmcblk-images which of couse should be backed up in advance
€:
today i scanned the sd image and the hidden.img seems, that the tablet would boot any kernel that is at position 0x00000400 on a sd card.
you may copy any image from OTA update.zip to that position and it should load it.
$ dd if=unbrick.img of=/dev/sdXXX
$ dd if=hidden.img of=/dev/sdXXX bs=512 seek=2
i tried the kernel from a tablet s on the xts and settings/about/kernel told me it worked!!
sadly, the data in hidden.img looks similiar to kernels of other SE devices, but is somehow scrambled
stth said:
IT WORKED
THANKS @condi
PS: why not trying to use the SD-image to flash KitKat?
i mean, you can pull all mmc images and flash all mmc images via dd, why not writing a custom rom this way? the only problem is the kernel.
mounts of /dev/block/*
mmcblk0p1 -> /configs
-r--r--r-- 1 root root 64 Jan 1 2000 06590E37F8A647D989345317AAFF6A6C
-r--r--r-- 1 root root 242 Jan 1 2000 31850B1B-0DAB-42ce-A498-A73479B7B3EB
-r--r--r-- 1 root root 878 Jan 1 2000 calibration_rear.bin
-r--r--r-- 1 root root 63104 Jan 1 2000 CFBSMXHMUAF48EXTDTCSOH4BXXDDRBFG
-r--r--r-- 1 root root 132 Jan 1 2000 local.propmmcblk0p2 -> /params
-rw------- 1 root root 2 Jan 30 14:43 activate_done
lrwxrwxrwx 1 root root 57 Jan 30 14:43 countries.lst -> /datapp/vendor/vendor0/regioncodelist/SKU002000172608.lst
drwx------ 2 root root 4096 Jan 1 1970 lost+found
-rw-r--r-- 1 root root 33 Jan 30 14:43 region_checksum.txt
-rw-r--r-- 1 root root 9706 Jan 30 14:43 region.zip
-rw-rw-rw- 1 root root 2 Jan 30 14:43 selected_countrymmcblk0p3 -> /system
mmcblk0p4 -> /system (copy)
mmcblk0p5 -> /cache
(ls /cache/recovery)
-rw-r--r-- 1 root root 45 Jan 1 2000 last_install
-rw-r----- 1 root root 22626 Jan 1 2000 last_log
-rw------- 1 stth stth 18769 Jan 1 2000 logmmcblk0p6 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p7 -> not mounted (64MB, file system?, image not mountable as loop device)
mmcblk0p8 -> not mounted (2MB, file system?, image not mountable as loop device)
mmcblk0p9 -> /datapp (vendor)
mmcblk0p10 -> /log
-rw-r--r-- 1 root root 18652 Jan 1 2000 recovery_abort.logmmcblk0p11 -> /data
judging the size of the unknown partitions, mmcblk0p7 could contain the kernel. probably we just have to find the file system on this partition. i guess, sony just skips a part or descrambles the partition while it shows the sony logo (which is always displayed, no matter if you boot into recovery, or the system) also, the hidden.img is flashed there... so... how to get it out?
what are the files in /configs? maybe keys or executables to decrypt the kernel?
does anybody have a log of a successful update in the logs (see mount list above)? is there any information about an updated kernel?
to get the mmc-images, just create the unbricker sd card (it does not break anything if you stop the script after the sd is written)
execute adb shell "/system/xbin/pwn"
then adb pull /dev/block/mmcblk*
on linux, you can mount them with
mount -o loop <image> <mountpoint>
some require root to view files
if anything is broken, we should be able to reflash all mmcblk-images which of couse should be backed up in advance
€:
today i scanned the sd image and the hidden.img seems, that the tablet would boot any kernel that is at position 0x00000400 on a sd card.
you may copy any image from OTA update.zip to that position and it should load it.
$ dd if=unbrick.img of=/dev/sdXXX
$ dd if=hidden.img of=/dev/sdXXX bs=512 seek=2
i tried the kernel from a tablet s on the xts and settings/about/kernel told me it worked!!
sadly, the data in hidden.img looks similiar to kernels of other SE devices, but is somehow scrambled
Click to expand...
Click to collapse
That is just some great work. Were the kernel different? But anyway it could be secure for bootloader check if there is any. Cause it is a tablet s kernel. I have a kernel which have kexec built in for tablet s. I can give it to you for testing if you want. And if you wanna join our hangout, just pm me
Sent from my Sony Tablet S using Tapatalk
Related
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...
Very bad news.
I appear to have had an accident with /efs. Not 100% sure what I did but suspect it related to a product code change.
My SGS2 now will not show an IMEI or connect to the cell network.
I connected with /adb and saw a number of files were updated earlier today
drwxrwxr-x 5 root root 4096 Jan 1 2000 .files
drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei
-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log
-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_data.bak.md5
-rwx------ 1 radio radio 2097152 Jan 1 2011 .nv_data.bak
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5
-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak
-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode
drwx------ 3 system system 4096 Jan 1 2011 dmp
-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone
-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result
-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin
-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data
-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p
-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena
bled
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock
-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata
-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5
-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin
-rw-r--r-- 1 system system 0 Nov 3 18:02 cryptprop_onetimeboot
drwxrwx--x 5 radio system 4096 Nov 3 21:23 .
drwxr-xr-x 21 root root 0 Nov 3 21:58 ..
You can see the changes to nv_data.bin.md5 and nv_data.bin -- I have no idea what crptprop_onetimeboot is but it looks a little suspicious.
Firstly I have a copy of the above as
- a directory on my sdcard
- a dd'd image on my sdcard
- a file copy on my PC (!)
I also see I still have backup files, so with a lot of difficulty (fs kept going read only when trying to copy files, so I ended up renaming the old name to the new name)
ie
.nv_data.bak -> nv_data.bin
.nv_data.bak.md5 -> nv_data.bin.md5
This didn't work (still no service/no imei), so I removed(renamed) the .md5 file -- but it still doesn't work
so it now looks like
# ls -latr
ls -latr
drwxrwxr-x 5 root root 4096 Jan 1 2000 .files
drwxrwxr-x 2 radio radio 4096 Jan 1 2000 imei
-rwx------ 1 radio radio 32 Jan 1 2011 nv_data.bin.md5.orig
-rwx------ 1 radio radio 2097152 Jan 1 2011 nv_data.bin
-rw-rw-rw- 1 radio radio 832 Jan 1 2011 nv.log
-rw-rw-rw- 1 radio radio 1 Jan 1 2011 .nv_state
-rwx------ 1 radio radio 32 Jan 1 2011 .nv_core.bak.md5
-rwx------ 1 radio radio 1048576 Jan 1 2011 .nv_core.bak
-rw-r--r-- 1 root root 1 Jan 1 2011 cryptprop_rebootMode
drwx------ 3 system system 4096 Jan 1 2011 dmp
-rw-r--r-- 1 system system 14 Jan 1 2011 cryptprop_persist.sys.timezone
-rw-r--r-- 1 system system 9 Jan 1 2011 cryptprop_applied_result
-rwxrwxr-- 1 radio radio 880 Jan 1 2011 redata.bin
-rw-rw-rw- 1 system system 6 Aug 12 22:43 calibration_data
-rw-rw-rw- 1 system system 256 Oct 4 15:55 edk_p
-rw-r--r-- 1 system system 3 Nov 2 01:27 cryptprop_persist.sys.language
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lockscreen.password_type
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- 1 system system 6 Nov 2 15:21 cryptprop_lock_pattern_tactile_feedback_ena
bled
-rw-r--r-- 1 system system 5 Nov 2 15:21 cryptprop_lock_pattern_autolock
-rw-r--r-- 1 root root 3 Nov 2 21:08 cryptprop_securewipedata
-rwx------ 1 radio radio 32 Nov 3 17:44 nv_data.bin.md5.bk
-rwx------ 1 radio radio 2097152 Nov 3 17:44 nv_data.bin.bk
-rw-rw-rw- 1 root root 0 Nov 3 20:55 p
drwxrwx--x 5 radio system 4096 Nov 3 21:48 .
-rw-r--r-- 1 system system 0 Nov 3 21:52 cryptprop_onetimeboot
drwxr-xr-x 21 root root 0 Nov 3 21:58 ..
#
[/FONT]
I DID NOT BACKUP EFS beforehand (only just learnt I need to) and know this may now be screwed, but I'm still hopeful I have the original file and just made a silly error.
I could also
- try recreating the whole fs and copying files back
- checking the prod code within the rom (but why?)
- flashing original firmware
- modifying the dd'd image *offline*, swapping the files, and dd'ing the image back
Any advice. PLEASE....
if you have a backup the easiest way I have found is to use root explorer.
go in to the /efs folder, set to read/write, mark everything and delete (not scrictly necessary simply copying over will work) but if you have been tinkering probably better.
then paste all the back up files and folders in
finally reboot (in my experience when something has gone wrong even this is not necessary)
Root explorer is worth every penny
and keep multiple backup's of your /efs on different drives
If this does not work you are screwed. The file contains your IMEI encrypted and the only way to get that restored is by returning it.
oh I just realised you are saying the back up you have is only of it in the current state?
If that's the case you are probably screwed, have you ever used any apps like nitrality or any unlocking tools? they will create copies of your efs folder on the scard in various locations. have you run a file seach on you sdcard to see if there is any copies at all?
if you have no backups of this folder then I think you will find its a return to manufacturer / sevice centre / provider issue.
I *think* I have restored the files -- and the dates look reasonable, as if they were the originals.
I've now flashed an old ROM (KE5) for good measure, but still no signal
One discrepancy I did notice is that after installing a rom there was some bootup message about csc and XEU when copying files.
My original sales code was VOD (UK vodafone). I had then run XEU firmware and just recently tried to set the sales code to XEU using a *# code. I subsequently flashed back to vodafone firmware today.
So somewhere there's a lingering reference to XEU -- this prod code incompatability could be causing the error?
I definately feel I should have the data to fix this -- after all I have the encrypted file, but am not quite sure of all the factors involved (one being "you're stuffed I know")
type *#06# this should display you IMEI number
if this does not match your IMEI from the box then you have not fixed this
if it shows all zeros or 004999010640000 then you are on a generic IMEI number
strangely when I screwed mine up and got the generic one above I was still able to use mine with a vodafone (UK) sim but not an orange on
if this is the case, and there is no efs backup prior to this you might well be screwed.
if this backup is all you have an you believe the .bak file is intact then I believe you will find solutions for deleting the primary version of the file and keeping only the backups and rebooting
the log file should give you more information on how successful this was, but if this was the result of flashing you probably overwrote both primary and backup
*#1234# is returning a reasonable CSC I9100VODKE2
Checking the nv data files, it appears
- the new ones modded today contain XEU
- the original ones contain VOD
This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.
Some remnant of XEU?
*#06# is currently showing blank -- but those .bak files looked fine.
Annoyed and frustrated...
In that case I would try deleting nv_data.bin and nv_data.m5 and rebooting
(assuming you have copies of everything
with just nv_data.bak nv_data.bak.md5
At least with the SGS1 this would work provided those bak files are the originals but the nv.log file will tell you more after the boot.
HOWEVER the SGSII has a lot more in this folder and I do not claim to fully understand them all but if you have a back up it's worth a shot
planetf1 said:
*#1234# is returning a reasonable CSC I9100VODKE2
Checking the nv data files, it appears
- the new ones modded today contain XEU
- the original ones contain VOD
This is consistent with what happened, so I am still confused why the renamed original files do not work, and why there's a reference to multi-csc XEU during bootup.
Some remnant of XEU?
Click to expand...
Click to collapse
Took some inspiration from http://www.communityhosting.net/sgsunlock/i9000.html and decided to check permissions & recreation of md5.
md5 wasn't recreated, so no matter, I had a backup. that is restored, but I don't know if the .bak files are needed. Yet trying to create them I get:
# mv nv_data.bin.md5.orig nv_data.bin.md5
mv nv_data.bin.md5.orig nv_data.bin.md5
# cp nv_data.bin .nv_data.bak
cp nv_data.bin .nv_data.bak
cp: write error: Read-only file system
#
This isn't a space issue.
There could be another cause -- /efs/imei/mps_info.dat contains the 3 characters "XEU" even though the file is dated Jan 2011
So either
- the date has been manually fudged
OR
- the code always was XEU -- unlikely.
I'm currently working on the basis that fundamentally the IMEI is intact, that the original nv_data.bin is intact & that the phone is validating the CSC in mps_info.dat (XEU) against nv_data.bin (VOD) and failing.
Though this wouldn't explain why before the fix, with XEU in the nv_data.bin, it wasn't working
Unless the issue is the filesystem itself. could it be corrupt? Is this in fact why it switched to R/O mode each time? I've tried multiple kernels including insecure. surely they wouldn't all "protect" this fs.
But if this is the case where is fsck? maybe I need to copy the fs image to another linux box with ext4 & inspect/correct before shipping back and dd'ing
Continuing.
Found /system/bin/e2fsck -- ran this against /efs with
# /system/bin/e2fsck /dev/block/mmcblk0p1
/system/bin/e2fsck /dev/block/mmcblk0p1
e2fsck 1.41.11 (14-Mar-2010)
ext2fs_check_if_mount: Can't check if filesystem is mounted due to missing mtab file while determini
ng whether /dev/block/mmcblk0p1 is mounted.
/dev/block/mmcblk0p1 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y>? y
yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: -(3202--3203) +4104
Fix<y>? yes
/dev/block/mmcblk0p1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/block/mmcblk0p1: 60/1280 files (1.7% non-contiguous), 2188/5120 blocks
**** >>> I NOW HAVE AN IMEI <<< ****
AND SIGNAL
LOGGED ONTO VODAFONE
WOOOHAY.
THIS HAS BEEN FUN. LOOK AND LEARN..
and seriously thanks to all the other articles and some moral support here tonight.
Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
planetf1 said:
Continuing.
Going to put back proper firmware , remove dodgy kernels and GET A BIG BEER OR THREE
Click to expand...
Click to collapse
and make several backups of the /efs folder in its current state one would assume
Phone seems working. restoring over a HSPA connection happily, recognized voda sim.
now reinstalling titanium backup and copying down from dropbox...
The final step was restoring from titanium backup.
I had erased my sdcard -- though my backup was on dropbox.
However titanium backup is awful at copying files to/from dropbox -- as is IMO the phone when in "phone/kies" mode.
Finally I simply copied the dropbox directory back in USB debug=mass storage mode which was quick and reliable -- and then restored most items en-masse (I have a pro license).
For the record so far phone is fine - and indeed I've since run a new efs backup
The key takeaways from this are
* Backup efs and save it somewhere offline
* get titanium backup pro. it's good (better if it backed up efs too!)
* usb mass storage mode is the most reliable way for file xfer
* backup efs (again)
* don't get complacent
And of course if you do get a similar problem to mine
a) take a backup of efs with dd if=/dev/mmcXXX of=/mnt/scard/myefs.img (check name - I forget)
b) copy files you can to sdcard
c) copy both of this to a seperate pc
d) Just try running fsck (as above) - If I'd done this sooner I'd have saved hours. I should have gone with the obvious -- I've seen this on enough linux systems in the past to know what was happening but was thrown by no kernel messages.
Thanks for letting us know, might be a nice reference for future problems, especially the filesystem check.
Writing about it also helped keep me sane.giving up and hitting the beer was becoming increasingly attractive.
I do think making the warning about efs clearer would help.backup really should be a must at the earliest opportunity
Sent from my GT-I9100 using Tapatalk
Another thought.do unmount /efs before fsck
Sent from my GT-I9100 using Tapatalk
Unable to restore
I know I had a valid IMEI during the last week or so.
I have flashed several ROM's during the last month.
Last night lost IMEI
Now , no matter what I try, I can't seem to restore my IMEI. I have the fake one that ends in a bunch of zero''s
My SDCARD has a folder called EFS_BACKUP with multiple efs_xxxxxxx.tar.gz files in it. If I extract any of these and try to restore them to the /EFS folder I still have the fake IMEI number.
Please help - I didn't understand all the adb code in this post
Hi there,
/efs is fairly new to me too, to be honest it took hours of careful rooting before I gained some useful knowledge in how that area works.
-- what I would suggest before *anything else* is to copy anything you do have left in /efs. You will need to be root to do this. I found the gui root explorer type tools a bit clunky so I used the android SDK (adb is one of the tools in this package) to help. IF YOU NEED HELP WITH THIS SAY. You need to copy the files to multiple places for safety. Someone OFF your phone, ie on a PC. This is just in case things get worse. Do the same with any of those .gz backups you have. Maybe you'll need them *if* you make things worse...
If you're familiar with linux/unix systems this is all fairly easy, but if you're not it can be quite scary. For example you have to be able to write to /efs as well as list files and move them around. One wrong step and you could make things worse.
If you're unsure perhaps you could find a friend who knows *nix well to help you out. The bottom line is that you need to
a) ensure the right files are in there
b) The filesystem itself was intact
I definately suffered from b -- less sure about a.
What you need to do will depend a fair bit on what files you find in there, and what dates they are.
You said you had some backup files. Are you sure you have some from before the problem started? Can you look inside those backup files (I think winzip or similar will expand them for you). WIthout divoluging the actual contents (since you don't want to share your IMEI with anyone), is there an nv_data.bin file in there? Out of all the files it seems to be the most critical. When's it dated (mine was Jan 2011). If you cant' find that file how about .nv_data.bak - is that a good size, and again an old one.
If you have either of these -- even without anything else I think you can probably recover.
If you can get up and running with adb, a good start would be
adb shell
ls -laR /efs
Thank you very much, fsck method fixed my efs. Phone just broke it while doing nothing :/
I love you
You just saved my Galaxy S2
Yay. Brilliant news
Added xtskit.zip to this post which contains various scripts which can be used to debug various situations! Please use always latest version from this post and AT YOUR OWN RISK!
Decided to start new thread if anybody would still get any adeas for debricking my Xperia Tablet S before I call it unpossible... So, what has happened:
- Tried to upgrade my FI XTS from rooted 6b to rooted JB. Flashing apparently went fine but after reboot I got just Sony logo. Was able to boot to recovery and tried to recover by flashing firmware version 6, but got this error:
Installing update...
Write images to system0...
Write files to vendor0...
Random offset: 0x384
read_mod_link: failed to readlink "/system1/vendor": No such file or directory
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.
Don't know what went wrong when flashing, but my analysis of current state:
* /blflags is set to 1 (because recovery starts to flash system0).
* /system0 contains valid image of that firmware what I use to recover (since it was flashed properly)
* /datapp/vendor0 contains correct data from the same firmware (since files were written properly)
* /system1 is totally corrupted
* /datapp/vendor1 state is unknown
* /staging state is unknown but propably contains valid data from SOME firmware because recovery works, right?
Because of that /system1 corrupted state, recovering won't work as Sonys updater-script will try to read it before flashing /staging.
No, why my XTS does not boot? For me, it seems that /staging contains valid image (because I can get to recovery), doesn't it then contain also valid kernel for system0, right? Does my XTS not boot because:
* /blflags is set to 1. System tries to boot from /system1 and FAILS since it's corrupted. However bootloader does not recognize this and wont flip blfalgs.
OT
* /staging is corrupted
In both cases, I could boot if I could just flip /blflags flag! In first case system would boot using /system0 and everything ok if /staging would have the right kernel for /system0 and since I can flash /system0 no problem. Also if flag would be flipped I could flash /system1 afterwards.
Now, any ideas? How to flip /blflags? I've been trying to poweroff in the middle of booting process but no luck. It just seems bootloader won't flip it no matter what.
Thanks!
- J
ignore post, cant delete
Could somebody confirm, that does hidden.img contain recovery and kernel? Further, could somebody with JB go to recovery and paste the version? I am trying to trace what version my /staging (hidden.img) is, JB or 6b.
My recovery says:
System utility(Rev.39, BL: 0x00000006, EC: 0.21, master)
I think it said the same when I was on 6b so unless JB has the same recovery, my /staging is probably from 6b.
Thanks!
Edit: And please, if anybody have european r6b firmware signed-txs03_300-ota-121116002.zip please share with me! I think my current hidden.img is from that firmware, just perhaps if I flash it, I could recover if the reason I cannot boot is that r6b bootloader won't allow loding r6 or JB system... Heh, I just tried, I can download r6b firmware for EVERY OTHER region but for my own region. Probably download link I got was wrong, but what would be the right link?
One kind soul replied and it seems JB's recovery is Rev.44. So my recovery/bootloader/kernel is from r6b and that's why my JB did not boot. I flashed hidden.img but for some reason it did not work (or I mistyped since I was a bit sleepy when upgrading).
I could try flashing r6b system0 and it could work, but Sony has removed it from their site. Please, anybody, do you have signed-txs03_300-ota-121116002.zip ??? I have r6, but it does not boot.
Just out of curiosity, when I poweron my tablet, kernel probably boots OK since my computer can see SGPT12 device after a while. However, adb does not work as expected so that wont help at all.
Wait what... I just found out, that when I am in recovery console, my computer sees SGPT121 device but does not have driver for it. When device worked, I had drivers. I used "Sony Tablet ADB Driver Automated Installer" to install drivers and when I explored android_winusb.inf I found out that this automated installer installed drivers only for composite adbdev interface, not for single adb interface. So I manually added correct pids etc. and was then able to install drivers and now I can actually see my device booted to recovery:
List of devices attached
0123456789ABCDEF recovery
Shell wont work however as expected so probably still impossible to unbrick, but at least I was able to pull recovery.log:
Starting recovery on Sun Apr 21 10:29:00 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /hwconfigs ext2 /dev/block/mmcblk0p1 (null) 0
2 /configs ext4 /dev/block/mmcblk0p2 (null) 0
3 /system0 ext4 /dev/block/mmcblk0p3 (null) 0
4 /system1 ext4 /dev/block/mmcblk0p4 (null) 0
5 /cache ext4 /dev/block/mmcblk0p5 (null) 0
6 /misc emmc /dev/block/mmcblk0p6 (null) 0
7 /staging ext4 /dev/block/mmcblk0p7 (null) 0
8 /blflags ext4 /dev/block/mmcblk0p8 (null) 0
9 /datapp ext4 /dev/block/mmcblk0p9 (null) 0
10 /log ext4 /dev/block/mmcblk0p10 (null) 0
11 /data ext4 /dev/block/mmcblk0p11 (null) -32768
12 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
13 /boot emmc boot (null) 0
14 /recovery emmc recovery (null) 0
15 /system ext4 system (null) 0
16 /vendor0 ext4 vendor0.img (null) 0
17 /vendor1 ext4 vendor1.img (null) 0
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=TID0142
ro.build.display.id=TID0142
ro.build.version.incremental=121116001
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Nov 16 01:16:55 JST 2012
ro.build.date.utc=1352996215
ro.build.type=user
ro.build.user=integ-build
ro.build.host=build8
ro.build.tags=test-keys
ro.product.model=SGPT12
ro.product.brand=Sony
ro.product.name=SYS_052
ro.product.device=txs03
ro.product.board=txs03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Sony
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=txs03
ro.build.description=SYS_052-user 4.0.3 TID0142 121116001 test-keys
ro.build.fingerprint=Sony/SYS_052/txs03:4.0.3/TID0142/121116001:user/test-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
wifi.wpa_supp_ready=0
persist.tegra.nvmmlite=1
windowsmgr.max_events_per_sec=135
ro.tether.denied=true
ro.sony.sound.enabled=true
ro.sony.display.release=release6b
ro.product-res-path=vendor/framework/SemcGenericUxpRes.apk
ro.sony.autovolume.threshold=10
ro.sony.update.server=info.update.sony.net
ro.sony.update.category_id=ST001
ro.config.alarm_alert=Alarm.ogg
ro.config.notification_sound=Notification.ogg
ro.config.ringtone=Ringtone_XPERIA.ogg
drm.service.enabled=true
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.sony.wifisleep=0
ro.semc.enhance.supported=true
ro.semc.clearaudio.supported=true
ro.somc.dmnorm.supported=true
ro.setupwizard.mode=DISABLED
ro.com.google.gmsversion=4.0_r6
ro.com.google.clientidbase=android-sony
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.sony.wan.ipv6.enable=false
persist.sys.sony.cabc.disable=0
persist.sys.sony.hdmi.disable=0
ro.sony.dlna_dms.enabled=false
ro.somc.social_product_model=PRODUCT_MODEL_TABLET
ro.sony.irremote.protocol_type=2
ro.sony.ols.eula=1
ro.pss.ps1content_disable=1
ro.factorytest=0
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=0x00000006
ro.hardware=txs03
ro.revision=0
init.svc.recovery=running
init.svc.nfx_daemon=running
init.svc.radbd=running
jappaj said:
Wait what... I just found out, that when I am in recovery console, my computer sees SGPT121 device but does not have driver for it. When device worked, I had drivers. I used "Sony Tablet ADB Driver Automated Installer" to install drivers and when I explored android_winusb.inf I found out that this automated installer installed drivers only for composite adbdev interface, not for single adb interface. So I manually added correct pids etc. and was then able to install drivers and now I can actually see my device booted to recovery:
Click to expand...
Click to collapse
I have exactly the same problem.
What do you modify on the android_winusb.inf to install drivers?
Thanks
hui666 said:
I have exactly the same problem.
What do you modify on the android_winusb.inf to install drivers?
Thanks
Click to expand...
Click to collapse
You mean you bricked your XTS like me while trying to flash JB? The we should warn people, it's something related to region, config or something like that.
About your question; edit android_winusb.inf and find rows like this:
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
Then add row like this just after that:
%SingleAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
So it becomes:
;SONY Sony Tablet S
%CompositeAdbInterface% = USB_Install, USB\VID_054C&PID_05B4&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_054C&PID_05B4
There two places where you will find rows likje this, onw for x85 and one for amd64.
After this, boot to recovery and wait that you can see your XTS in device manager. It should shay that there are no drivers etc. Click update driver and browse manuaklly files and find directory which contains that modified file. Install and it should work.
But Sony has locked us out of the shell and effectively nothing can be done to fix anything (thanks sony, lock bootloader, f**k recovery scripts, f**k automatic swtiching between system images, lock recovery adb... what next, you need to be in jail to use next Xperia device?) unless somebody finds exploit. But then we could root also...
Wait, has anybody ever actually tried that would Xperia Tablet S accept upate.zip which is signed with test key just like you sign packages for Tablet S, but ALSO encrypted?
Because error message I get when trying to use such zip is something like cannot desklunvr package... So it is trying to decrypt package and as it is already decrypted, it fails. What happens if we encrypt it? It should be possible since we know how to decrypt!
jappaj said:
Wait, has anybody ever actually tried that would Xperia Tablet S accept upate.zip which is signed with test key just like you sign packages for Tablet S, but ALSO encrypted?
Because error message I get when trying to use such zip is something like cannot desklunvr package... So it is trying to decrypt package and as it is already decrypted, it fails. What happens if we encrypt it? It should be possible since we know how to decrypt!
Click to expand...
Click to collapse
Had jb boot up but no root access so flashed the jb update official and it works fine lost root it takes ages for it to boot and also took a couple of goes with the flasher no big deal only reason for root is custom ROM and until boot loader is unlocked not much need for root
S
Sent from my Wildfire using xda app-developers app
dex9mm said:
Had jb boot up but no root access so flashed the jb update official and it works fine lost root it takes ages for it to boot and also took a couple of goes with the flasher no big deal only reason for root is custom ROM and until boot loader is unlocked not much need for root
S
Sent from my Wildfire using xda app-developers app
Click to expand...
Click to collapse
Oh dear I've just joined the Bricked club tooo......
I tried updated from rooted 6b to Rooted Jelly Bean with condi flasher and I'm now stuck on the Sony screen.
Anyyyy possible fix?
Hi everyone, we are on the same boat. I've tried to flash using S.T.S.Flasher 3.0v the prerooted 4.1.1 rom on my root 4.0.3 R6B tab. My Xperia is US version. It seems that everything worked fine, but at the end I got black screen. On another post I read that a hard reset was needed. Nothing happened. After reboot i got freez on sony's logo. I've done with recovery a factory reset, wiping data etc, but without success.
Now I've downloaded a stock r5 version and flash it but i've seen after first boot that the fw that my dev. is running now is 4.1.1, without root and recovey. Strange but true. Why? i don't really know.
I think that i've done a big mistake flashing it but i think that it was the right thing to do for not using my tab as a coaster for the future.
sfex3best said:
Oh dear I've just joined the Bricked club tooo......
I tried updated from rooted 6b to Rooted Jelly Bean with condi flasher and I'm now stuck on the Sony screen.
Anyyyy possible fix?
Click to expand...
Click to collapse
Can you get to recovery? Try to flash firmware version 6 (not a not b) for your region from there. You are not bricked until you cannot flash from recovery like me...
sfex3best said:
Oh dear I've just joined the Bricked club tooo......
I tried updated from rooted 6b to Rooted Jelly Bean with condi flasher and I'm now stuck on the Sony screen.
Anyyyy possible fix?
Click to expand...
Click to collapse
flashing the stock jb from sony sight and losing root might be best if cant wait to hear back from condi......
not the best solution but from reading others at least shouldnt risk bricking.
Tried installing release 6 from recovery but no luck with that. Tried a few different versions too release 6b and jelly bean but the same error on all of them
{
"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"
}
Need help
Sent from my R800i using xda premium
sfex3best said:
Tried installing release 6 from recovery but no luck with that. Tried a few different versions too release 6b and jelly bean but the same error on all of them
View attachment 1903761
Need help
Sent from my R800i using xda premium
Click to expand...
Click to collapse
I've flashed one of this stock rom . http://forum.xda-developers.com/showpost.php?p=26882762&postcount=3
because when i tried to flash it using recovery i got this error similar to yours:
"Desklunvr update package...
E:Can't desklunvr /sdcard/customs_prerooted_"........".zip
Installation aborted"
I think you'll lose root and recovery, but now should be the only way that i found to skip that error and brings back your tab to life.
I've tried those already I think.
Which one is stock rom out of those tho?
Sent from my R800i using xda premium
I have a US device, so i've downloaded and flashed the ICS r6b for US tablet. Should be both stock rom. If you see the links, are all of sony's web site.
Guys, if you get that "read_mod_link: failed to readlink "/system1/vendor": No such file or directory" error you currently are bricked. There's no way to recover until:
a) Sony releases an update which does not suck and is actually able to recover something (I doubt it since they haven't done it before)
b) Somebody from Sony leaks private key used to sign updates so we can sign our own update.zip (highly unlikely...)
c) Somebody finds a way to crack recovery from recovery itself (possible but I doubt it since it has not happened before)
d) Somebody finds out how to flip /blflags (possible, but I haven't been able to figure out how)
So we are screwed, there's no way to recover for now.
Ps. If anybody from Sony is reading this, please give us update.zip or something else which will flip blflags which would allow us to reover using standard firmware. Otherway you risk receiving bricked tablets to your sevice centers even though they are not really bricked, we just do not have proper update.zip. Highly unlikely though that anybody from Sony is reading this, at least anybody who can make the decision...
jappaj said:
Guys, if you get that "read_mod_link: failed to readlink "/system1/vendor": No such file or directory" error you currently are bricked. There's no way to recover until:
a) Sony releases an update which does not suck and is actually able to recover something (I doubt it since they haven't done it before)
b) Somebody from Sony leaks private key used to sign updates so we can sign our own update.zip (highly unlikely...)
c) Somebody finds a way to crack recovery from recovery itself (possible but I doubt it since it has not happened before)
d) Somebody finds out how to flip /blflags (possible, but I haven't been able to figure out how)
So we are screwed, there's no way to recover for now.
Ps. If anybody from Sony is reading this, please give us update.zip or something else which will flip blflags which would allow us to reover using standard firmware. Otherway you risk receiving bricked tablets to your sevice centers even though they are not really bricked, we just do not have proper update.zip. Highly unlikely though that anybody from Sony is reading this, at least anybody who can make the decision...
Click to expand...
Click to collapse
Man im roight there with you ok evey one who has used the flasher STOP FLASHING
If your stuck on sony screen during flashing But can flash back to ics do and saty there
If it is not booting then I dont have an answer just a warning
I was the first to post about the flsaher giving trouble but nobody checks these fourms till there is a prioblem and thats why people strat at step three and then ask where did I go wrong ive been posting since the twentith so its not like the warning signs wernt there
However if your realy want the update download it via ics then root with condis tool and flasdh
and you boot in to jb there is no root acknowledgement by 3rd party apps there is root due to the kernal condi provides but it is rooted
If
And why is the chager cable so short
Pm me if you need help
Sent from my SGPT12 using xda app-developers app
dont ask for condi by the way hes just got married
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 $
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
craftsvision said:
Hello xda
Seems like I cannot erase all partitions properly. My phone have random reboots problem, and once it boots then it gets stuck at bootloader, so on every reboot I have to re-install OS. It does not matter whichever rom I try it still have same problem.
So what I tried is to erase all partitions in fastboot by command fastboot erase cache, system, etc etc and all other with success.
Then I use FlashOne1.9 to restore my phone completely to zero using QFIL with success installation but phone still kept rebooting, I tried to goto Recovery and here I still see TeamSpain TWRP 3.0.2 installed.
What can be wrong?
I erased all partitions manually + QFIL restore I thought completely erases everything but as I see still no.
Is there a way where I can delete all partitions and then recreate them one by one so there is not even a bit of any preinstalled softwares left.
I read deleting partitions in fastboot but felt it can be risky so I thought to ask a second opinion before proceeding.
Thank you
Click to expand...
Click to collapse
here´s the patition table, if it is of any use for you...
lrwxrwxrwx 1 root root 16 Jan 1 00:12 aboot -> /dev/block/sde16
lrwxrwxrwx 1 root root 16 Jan 1 00:12 abootbak -> /dev/block/sde17
lrwxrwxrwx 1 root root 16 Jan 1 00:12 apdp -> /dev/block/sde29
lrwxrwxrwx 1 root root 16 Jan 1 00:12 bluetooth -> /dev/block/sde22
lrwxrwxrwx 1 root root 16 Jan 1 00:12 boot -> /dev/block/sde18
lrwxrwxrwx 1 root root 15 Jan 1 00:12 bootconfig -> /dev/block/sdf7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cache -> /dev/block/sda3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 cdt -> /dev/block/sdd2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib -> /dev/block/sde25
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64 -> /dev/block/sde27
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlib64bak -> /dev/block/sde28
lrwxrwxrwx 1 root root 16 Jan 1 00:12 cmnlibbak -> /dev/block/sde26
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ddr -> /dev/block/sdd3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfg -> /dev/block/sda6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 devcfgbak -> /dev/block/sda7
lrwxrwxrwx 1 root root 16 Jan 1 00:12 devinfo -> /dev/block/sde21
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dip -> /dev/block/sde14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dpo -> /dev/block/sde31
lrwxrwxrwx 1 root root 16 Jan 1 00:12 dsp -> /dev/block/sde13
lrwxrwxrwx 1 root root 15 Jan 1 00:12 factory -> /dev/block/sdf6
lrwxrwxrwx 1 root root 15 Jan 1 00:12 frp -> /dev/block/sda8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsc -> /dev/block/sdf5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg -> /dev/block/sde7
lrwxrwxrwx 1 root root 15 Jan 1 00:12 fsg_gap -> /dev/block/sde8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hyp -> /dev/block/sde5
lrwxrwxrwx 1 root root 15 Jan 1 00:12 hypbak -> /dev/block/sde6
lrwxrwxrwx 1 root root 16 Jan 1 00:12 kernellog -> /dev/block/sdf14
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymaster -> /dev/block/sde23
lrwxrwxrwx 1 root root 16 Jan 1 00:12 keymasterbak -> /dev/block/sde24
lrwxrwxrwx 1 root root 15 Jan 1 00:12 keystore -> /dev/block/sda5
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvconfig -> /dev/block/sdf10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letveui -> /dev/block/sdf11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvreserve -> /dev/block/sdf13
lrwxrwxrwx 1 root root 16 Jan 1 00:12 letvsecure -> /dev/block/sdf12
lrwxrwxrwx 1 root root 16 Jan 1 00:12 mdtp -> /dev/block/sde15
lrwxrwxrwx 1 root root 15 Jan 1 00:12 misc -> /dev/block/sda4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 modem -> /dev/block/sde12
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1 -> /dev/block/sdf1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst1_gap -> /dev/block/sdf2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2 -> /dev/block/sdf3
lrwxrwxrwx 1 root root 15 Jan 1 00:12 modemst2_gap -> /dev/block/sdf4
lrwxrwxrwx 1 root root 16 Jan 1 00:12 msadp -> /dev/block/sde30
lrwxrwxrwx 1 root root 15 Jan 1 00:12 persist -> /dev/block/sda2
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmic -> /dev/block/sde10
lrwxrwxrwx 1 root root 16 Jan 1 00:12 pmicbak -> /dev/block/sde11
lrwxrwxrwx 1 root root 16 Jan 1 00:12 recovery -> /dev/block/sde20
lrwxrwxrwx 1 root root 15 Jan 1 00:12 recoveryconfig -> /dev/block/sdf9
lrwxrwxrwx 1 root root 15 Jan 1 00:12 reserve -> /dev/block/sdd1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rootconfig -> /dev/block/sdf8
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpm -> /dev/block/sde1
lrwxrwxrwx 1 root root 15 Jan 1 00:12 rpmbak -> /dev/block/sde2
lrwxrwxrwx 1 root root 15 Jan 1 00:12 sec -> /dev/block/sde9
lrwxrwxrwx 1 root root 16 Jan 1 00:12 splash -> /dev/block/sde32
lrwxrwxrwx 1 root root 15 Jan 1 00:12 ssd -> /dev/block/sda1
lrwxrwxrwx 1 root root 16 Jan 1 00:12 sti -> /dev/block/sde33
lrwxrwxrwx 1 root root 16 Jan 1 00:12 system -> /dev/block/sde19cmd
lrwxrwxrwx 1 root root 15 Jan 1 00:12 xblbak -> /dev/block/sdc1
never blank partitions if you don´t have a backup anywhere, meaning: not part of qfil, stockrom customrom (zip or fastboot), not pulled from the/a phone(x820/29)
i would pull any single partitiom first (that are not part of roms etc.) and save it, you shoud be safe to restore the phone to the condidtion as it is now at least.
if you think one of theese could cause the problem, be sure to get the partition images from a working phone before you erase those!
also, backup your efs/qcn!
from what you tell it sounds like a harrdware fault but try! i would also try everything, had success the last time.
it bet it´s a x829, isn´t it?
i have some spare time the rest of the week and already helpded some xda users remotely. if you want i could (try) to help you too.
i´m an it guy, so this is my nature.
good luck
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
craftsvision said:
Yes you are correct i have x829, I bought it online from gearbest.com.
I dont know how this partition table can be useful and I dont even know how to use it.
I have backup of CN26s bootloader and Firmware made via TWRP. Stragnely CN26s boots everytime but have alot of random reboots.
If I install Hexagon Rom from here then it works fine for a day or two https://forum.xda-developers.com/le-max-2/development/rom-hexagonrom-nougat-t3594858
but as soon as its rebooted then I have to restore CN26s bootloader via TWRP then install Hexagon***.zip again and it will start again.
One more thing is that if I only restore bootloader of cn26s while already installed Hexagon then it is not stuck at bootloader screen anymore where it says LeeCo I am not jut a mobilephone blah blah but it also proceeds to Hexagon OS loading Animation but then its stuck there forever...!
If you can help then please tell me, I am willing too to try new things.
Click to expand...
Click to collapse
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
A.N.Droid said:
if you want, install teamviewer and send me your id and password in pm.
connect the phone to pc directly (no hub) and put into edl mode. i know you already did that procedure but i´d like to start from scratch - just to be sure.
we can save the qcn also with qpst so you don´t have to worry about loosing your imei.
open the folder where alll your files are.
i´ll have to check some things on your pc and download some files.
i´m cooking my meal now, then i´m ready. just keep pc and teamviewer on and i´ll login asap.
Click to expand...
Click to collapse
It would be really helpful of you make a video about the complete fix. I have a x821 in which I forgot to remove encryption before flashing a custom ROM and now in twrp there is a system image partition which is 4GB in size and is non accessible. I want to delete that but being inaccessible I an unable to do so.
Can you guide me on how to do that? Can you at least give me the step by step procedure to fix this issue?
Thanks in advance.
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
azzammalik said:
I have also problem of random reboots and fcs no mater what rom I flash.
Any one guide me what to do?
I have clean flashed though twrp.
Didn't use fastboot method? Any one can guide me on this ?
Click to expand...
Click to collapse
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Thanks a lot brother
ThE_MarD said:
Heyyo, first off... Can you please state which version of TWRP you are running and if it is official or not?
Second, have you tried using wipe > format data > yes? I'd recommend doing that... But be warned it completely reformists the internal storage so you'll want to backup everything important off the device first and also have a PC with USB ready to flash ROM and Gapps.
Third, I would recommend flashing new device firmware to ensure it is proper for any ROM you install. I recommend for stability purposes to use x820 CN 30s which can be found on my LineageOS 15.1 for x2 thread.
Fourth, flash the ROM of choice and Gapps (and optionally root program of choice if you want Su rights).
For Oreo ROMs? I highly recommend MindTheGapps arm64 as OpenGapps is still of beta quality for Oreo ROMs and says so when you select it on the OpenGapps website as shown in the picture below. MindTheGapps link can also be found on my LineageOS for x2 thread.
As for which Oreo ROM I'd recommend? Every one has a little bit of difference from the last so I say try them out and see which suits your needs the best. They're all pretty darn good... Except for Resurrection Remix official. The maintainer of that put out one build and then bought a new smartphone and abandoned it lol so yeah avoid the official RR release...
Good luck! :good:
Click to expand...
Click to collapse
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
azzammalik said:
Million times thanks to you bro for answering with lot of details.
1. It's official latest twrp
2. Yes formatted a lot of times.
3. Yeah this is the method I didn't try yet. I will goto your thread and will download official firmware and will let you know after flashing official and afterwards any oreo rom.
4. Never tried any gapps other then opengapps maybe this will solve my problem. I will definitely try this method now.
I have almost flashed all oreo roms and every oreo rom is almost perfect for me except for this annoying bug. I am now heading towards your rom and will report you back after few hours because my mobile data is not that super fast and will download all required files and will flash it later in evening.
Thank you once again.
:fingers-crossed:
Click to expand...
Click to collapse
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
ThE_MarD said:
Heyyo, by chance is your TWRP version 3.2.1-2? That's the latest one I made and is required for the latest versions of LineageOS 15.1 for x2 as it has quota storage support for a minor boost to storage performance.
https://twrp.me/leeco/leecolemax2.html
Hope she works good for you!
Click to expand...
Click to collapse
Hey,
I am here after 12 hours of usage.
Yes, I am using twrp 3.2.1-2.First flashed 30s firmware then flashed rom and gapps which you recommended and then magisk.
And to my amazement I had only 3 fcs right now which are too less then which I have faced before.
Also didn't reboot once in 12 hours but suddenly got 2 reboots in quick succession.
But still it's a lot more usable now as a daily driver for me just because of ya. Maybe problem will come back in a day or two as that happened before too.
But until then it's all OK for now.
A big thanks to you. .
Have a good day ahead
Cheers
Update: not even a single reboot or fc even after installing system less xposed. NO WORDS FOR YA. A BIG THANKYOU
2nd Update: 2nd day of usage. No more fcs. Single reboot. Perfect now.