My first post on xda about my first flashing ever. Mirek seems to work. Still need 9 more posts to be able to post on dev forum.
By the way, i plan to install debian on it. Either by replacing winshiiiiiii*, either by doing a install with a shared kernel (but not as chroot as seen in gnu root debian).
Still need to post 9 more posts before i can thank Mirek.
10.
that's 9
By the way it's a very stressing situation when you never flashed a rom.
I plan to remove the windows partitions in order to install the debian system on a separate partition but i first need to back up the partition table of the current installation in order to reinstall windows (in case something go wrong).
Use dd command to Bacup windows partition .
In the future I add that possibility in my flash tool .
7
Thank for your answer.
That's what i did. (In fact, it's the very first thing i did).
But i want to backup the partition table in order to reinstall as origin, even if this will probably never happen.
I want to remove all the msft partition in order to make room for debian root & home and make the data partition larger. I guess it is possible to do so by editing the .tbl file in the partition folder.
But do you know a tool to extract the current partition table ? Or do i have to make it manually ?
You have to make it manually .
If you want know how big is each partition - easy way install partition info ( in that program check advanced view )
Or use terminal ....
With my partitions you have partition editor .
Only diffrences will be on the last 4 petitions /cache / sytem /data and windows last partition .
Or if you install teclast windows then windows create 4 partitions for itself at the end partition tables .
PS I tried boot Debian ....and failed ... looks like in half of booting from usb just usb stoped working ( I have powered usb hub ) .
I finally figured it out for the partition editor. Thanks.
About debian, it's not the usb way i'm talking about but more something like that :
whiteboard.ping.se/Android/Debian
The article is a little old but...
It's less straithforward than usb but you keep the advantage of android (and the drivers) with the full fonctionnality of debian (no chroot).
Oh, i forgot.
The rom is a nice improvement of the system. The battery life lasts far longer.
I had a few bug (apps closing like xprivacy).
There is also semething else. I'm not able anymore to setenforce selinux in enforcing mode. I did it with the Selinuxmodechanger but the change to enforce mode prevented other apps as well selinuxmode changer & terminal emulator to restart.
I had to reboot the device.
Don't change to enforce mode because mods will stop works.
I have a question :
What is exactly efilinux-userdebug.efi ? It seems you flash it before any operation on the device.
This is EFI boot able partition ( small partition ) that allow to boot droidboot in ram disk .
Ok...
I have issue with your rom :
Some apps are crashing (privacy X).... I think there is an issue with permission system.
I had also to screen freezes. May be related to Gravity box or apex, may be both.
I removed animation of the dock swipe from apex settings and now it's ok.
But he selinux issue is a big issue for me, i don't feel it well. It like going outside with just a T-shirt in the middle of the winter.
And i want to try Remix. I will maybe come back to Mirek later.
In order to flash Remix from my debian pc, I adapted your batch script in bash. and your partition.tbl
your excel sheet was inspiring. I backed-up the current partition table with fdisk command for all partition. It give something equals to the excel sheet for the first partitions.
I upload the 2 necessary file (script & partition flash) in the hope you could take a look at it.
teclast_remix_partition.sh :
#!/bin/bash
#Flash osloader & boot from droidboot.img
fastboot flash osloader ROM/efilinux-userdebug.efi
fastboot boot ROM/droidboot.img
fastboot devices
sleep 30
#Wipe ESP
fastboot oem wipe ESP
echo "ESP wiped"
####Start partitionning####
echo "start partitioning"
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl ROM/partition.tbl
fastboot oem partition /tmp/partition.tbl
echo "start erasing..."
####Erase partitions####
fastboot erase system
echo "system erased"
fastboot erase cache
echo "cache erased"
fastboot erase config
echo "config erased"
fastboot erase data
echo "data erased"
fastboot erase logs
echo "logs erased"
fastboot erase factory
echo "factory erased"
fastboot oem stop_partitioning
#Flash partitions
fastboot flash ESP ROM/esp.img
echo "esp flashed"
fastboot flash fastboot ROM/droidboot.img
echo "droidboot flashed"
fastboot flash boot ROM/boot.img
echo "boot flashed"
fastboot flash recovery ROM/recovery.img
echo "recovery flashed"
fastboot flash system ROM/system.img
echo "system flashed"
fastboot continue
echo "All should be OK now"
sleep 10
Click to expand...
Click to collapse
partition.tbl :
partition_table=gpt
create -z /dev/block/mmcblk0
create /dev/block/mmcblk0
boot -p /dev/block/mmcblk0
reload /dev/block/mmcblk0
add -b 40 -s 131072 -t efi -u C12A7328-F81F-11D2-BA4B-00A0C93EC93B -l ESP -T 0 -P 0 /dev/block/mmcblk0
add -b 131112 -s 131072 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF0 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 262184 -s 32768 -t data -u 80868086-8086-8086-8086-000000000100 -l boot -T 3 -P 15 /dev/block/mmcblk0
add -b 294952 -s 32768 -t data -u 80868086-8086-8086-8086-000000000101 -l recovery -T 3 -P 14 /dev/block/mmcblk0
add -b 327720 -s 32768 -t data -u 80868086-8086-8086-8086-000000000102 -l fastboot -T 3 -P 13 /dev/block/mmcblk0
add -b 360488 -s 32768 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF1 -l reserved_1 -T 3 -P 0 /dev/block/mmcblk0
add -b 393256 -s 131072 -t data -u 80868086-8086-8086-8086-000000000104 -l test -T 3 -P 12 /dev/block/mmcblk0
add -b 524328 -s 65536 -t data -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 589864 -s 32768 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 622632 -s 32768 -t data -u 80868086-8086-8086-8086-000000000003 -l misc -T 0 -P 0 /dev/block/mmcblk0
add -b 655400 -s 32768 -t data -u 80868086-8086-8086-8086-000000000004 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 688168 -s 2097152 -t data -u 80868086-8086-8086-8086-000000000005 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 2785320 -s 524288 -t data -u 80868086-8086-8086-8086-000000000006 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 3309608 -s 4194304 -t data -u 80868086-8086-8086-8086-000000000007 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 7503912 -s 50331648 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0
add -b 57835560 -s 31457280 -t data -u 80868086-8086-8086-8086-000000000009 -l debianroot -T 0 -P 0 /dev/block/mmcblk0
add -b 89292840 -s $calc($lba_end-16384) -t data -u 80868086-8086-8086-8086-000000000010 -l debianhome -T 0 -P 0 /dev/block/mmcblk0
reload /dev/block/mmcblk0
Click to expand...
Click to collapse
Is everything ok ?
PS : I don't understand the use of the xml and cmd files, since everything can be done from the batch files
Ok i get it. that's for the intel MFT.
get a huge connectivity problem with the rom : i couldn't g et internet anymore.
I had to make a factory reset.
Hi!
I install mirek190_rom_v7.0 - android Lollipop, I had a few bug (apps closing like facebook, word, powerpoint) and apps OLX are hang, and help only reboot by pressing on 10s power button.
Battery start show full capacity and take on all day after fully discharge and charge on power-off device
And after reboot or shut down when tablet on again, when pressing "last up" soft button i see app what working on last session, they likely didn't close.
In Titanium Backup i cant uninstall, integrate updates 'system' app like Youtube, Apex.. TB wrote "app dont find"
Also on my c9j8 don't work camera.
I can suggest you the remix os rom for x98 on jide website. But you will have to customise it with a kitchen in order to have root access.
You can even build it with malware in it and propose it on the forum, like the russian version proposed by allegator in the teclat-remix thread. (I cheked the adbd binary in the ramdisk with a hexadecimal editor ; at the end there is a fair number of call of external functions).
It seems android herited some of the bad common practices met in the windows world. Coming from the Linux world, Android looks like the Wild West in comparaison.
But the good part is the Android implementation is far more accessible for system programming and general understanding than the desktop versions of linux. It is possible to quickly make your own tweaks.
By the way, the official jide rom offers a great improvement in android gui like a task bar which allow you to switch easily from one app to another. Once you get used to it, you cannot come back to regular android gui.
But you will have to get your hands dirty if you want root access without having to flash dubious 'custom' rom.
If your interested i suggest you to look for kitchen in the search engine and tutorials about ramdisk and kernel. It can take a little time to get it all, but that's not rocket science.
Related
I am using CyanogenMod v3.6.8.1 and I decided I wanted a swap partition.
I partitioned my 2GB SD with a 32MB swap partition and formatted using gparted.
From the shell (using adb) I remounted /dev/block/mtdblock3 with rw and edited /system/etc/fstab and added a line for the swap. Here is what the entire file looks like now:
Code:
/dev/block/mtdblock3 /system yaffs2 rw
/dev/block/mtdblock4 /cache yaffs2 rw
/dev/block/mtdblock5 /data yaffs2 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /system/sd auto rw
/dev/block/mmcblk0p3 none swap sw
/system/modules/modules.sqf /system/modules squashfs ro,loop
/system/xbin/xbin.sqf /system/xbin squashfs ro,loop
I can turn on the swap with 'swapon -a' which works and shows up in /proc/swaps and with the 'free' command, but upon boot, swap isn't activating.
I'm not really familiar with the android init scripts, so I'm not sure how I can enable the swap automatically upon boot. Any advice would be appreciated.
Okay I fixed it.
I downloaded one of Drizzy's roms that I know use swap, extracted, and searched for 'swap' in all the files. I found it in /system/bin/a2sd at the end. Here is what's there:
Code:
if [ -n /dev/block/mmcblk0p3 ];
then
mkswap /dev/block/mmcblk0p3;
fi;
if [ -e /dev/block/mmcblk0p3 ];
then
echo 30 > /proc/sys/vm/swappiness;
swapon /dev/block/mmcblk0p3;
fi;
The first if doesn't make sense to me as it's a string test which will always be true, so I got rid of it and just kept the test for the file existing, but I changed it to -b to be a little more specific (to see if it's a block device), and I commented out the swappiness change to leave it at default.
Im using same rom and i woild love to do this but is there any other way as im totally unfamiliar with adb
turboyo said:
Im using same rom and i woild love to do this but is there any other way as im totally unfamiliar with adb
Click to expand...
Click to collapse
I just used adb because I can use the copy/paste function of my gnome terminal and it's easier than using the shell on the phone itself.
Here is what is needed:
Get into a root shell, either on the phone or using adb.
Code:
mount -t yaffs2 -o rw,remount /dev/block/mtdblock3 /system
vi /system/bin/a2sd
press capital G which will take you to the bottom of the file
press lower case o which will open a line below your cursor for editing.
type in the following:
Code:
if [ -b /dev/block/mmcblk0p3 ];
then
echo 30 > /proc/sys/vm/swappiness;
swapon /dev/block/mmcblk0p3;
fi;
press escape to exit insert mode (I read that in the terminal emulator you have to hold the trackball and press 1 for esc)
type :wq and press enter.
exit terminal and reboot. To see if it's working, get back into a terminal and use the command 'free'
you can also do 'swapon -a' instead of specifying the swap partition itself. Note that the above example uses the third partition of the SD card as the swap.
This also assumes you have already created the swap partition and formatted it as swap.
You can omit the swappiness line to leave it at the linux default of 60.
Hi sorry if i sound noob but i would like to try converting my stock rom from .rfs to ext4 without breaking anything (My setup is exactly as described in my signature). I understand that ketut has created a script to make this happen.
ketut.kumajaya said:
Just want to share my command list to convert Galaxy Ace firmware from rfs to ext4.
Code:
cd /home/user/rfs2ext4
dd if=/dev/zero of=system.rfs bs=4096 count=53696
losetup /dev/loop0 system.rfs
mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=4 -O ^resize_inode,^ext_attr,^huge_file,^has_journal /dev/loop0
tune2fs -c 100 -i 100d -m 0 /dev/loop0
mkdir /tmp/ext4
sudo mount /dev/loop0 /tmp/ext4
chmod 755 fix-*.sh
cp fix-*.sh /tmp
mkdir /tmp/rfs
sudo mount -o loop source/system.rfs /tmp/rfs
sudo cp -a /tmp/rfs/* /tmp/ext4
cd /tmp/ext4
sudo ../fix-system.sh
cd /home/user/rfs2ext4
sudo umount /tmp/ext4
sudo umount /tmp/rfs
dd if=/dev/zero of=data.rfs bs=4096 count=46400
losetup /dev/loop0 data.rfs
mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=16 -O ^resize_inode,^ext_attr,^huge_file /dev/loop0
tune2fs -c 100 -i 100d -m 0 /dev/loop0
mount /dev/loop0 /tmp/ext4
sudo mount -o loop source/data.rfs /tmp/rfs
sudo cp -a /tmp/rfs/* /tmp/ext4
cd /tmp/ext4
sudo ../fix-data.sh
cd /home/user/rfs2ext4
sudo umount /tmp/ext4
sudo umount /tmp/rfs
dd if=/dev/zero of=csc.rfs bs=4096 count=6464
losetup /dev/loop0 csc.rfs
mkfs.ext4 -T ext4 -b 4096 -m 0 -J size=4 -O ^resize_inode,^ext_attr,^huge_file /dev/loop0
tune2fs -c 100 -i 100d -m 0 /dev/loop0
mount /dev/loop0 /tmp/ext4
sudo mount -o loop source/csc.rfs /tmp/rfs
sudo cp -a /tmp/rfs/* /tmp/ext4
cd /tmp/ext4
sudo ../fix-csc.sh
cd /home/user/rfs2ext4
sudo umount /tmp/ext4
sudo umount /tmp/rfs
tar -H ustar -c boot.img recovery.img data.rfs system.rfs > CODE_S5830XWKPN_CL375596_REV03_blackhawk.tar
md5sum -t CODE_S5830XWKPN_CL375596_REV03_blackhawk.tar >> CODE_S5830XWKPN_CL375596_REV03_blackhawk.tar
mv CODE_S5830XWKPN_CL375596_REV03_blackhawk.tar CODE_S5830XWKPN_CL375596_REV03_blackhawk.tar.md5
tar -H ustar -c csc.rfs > CSC_S5830OXXKP7_CL375596_REV03_blackhawk.tar
md5sum -t CSC_S5830OXXKP7_CL375596_REV03_blackhawk.tar >> CSC_S5830OXXKP7_CL375596_REV03_blackhawk.tar
mv CSC_S5830OXXKP7_CL375596_REV03_blackhawk.tar CSC_S5830OXXKP7_CL375596_REV03_blackhawk.tar.md5
tar -H ustar -c arm11boot mibib oemsbl qcsbl > APBOOT_S5830XWKPN_CL375596_REV03.tar
md5sum -t APBOOT_S5830XWKPN_CL375596_REV03.tar >> APBOOT_S5830XWKPN_CL375596_REV03.tar
mv APBOOT_S5830XWKPN_CL375596_REV03.tar CAPBOOT_S5830XWKPN_CL375596_REV03.tar.md5
tar -H ustar -c amss > MODEM_S5830XWKP6_CL375596_REV03.tar
md5sum -t MODEM_S5830XWKP6_CL375596_REV03.tar >> MODEM_S5830XWKP6_CL375596_REV03.tar
mv MODEM_S5830XWKP6_CL375596_REV03.tar MODEM_S5830XWKP6_CL375596_REV03.tar.md5
Click to expand...
Click to collapse
My question is how do you do it? Do you create a .sh script with this and then just run it using script manager or do you have to run this script in recovery?
Thanks
you can do this without scipt it's easy, first,flash CF-Root kernel in recovery , then go to the app drawer then open the EXT4 app, then covert to ext4 this operation will take about 2-3 min in recovery,of course you need to have CWM4,at the end it wiil reboot you phone so enjoy it
Press the thanks butom if I helped
that ketut's script can only be use on odin files, cannot be use on already installed rom. btw cfroot ext4manager app should be able to do it directly from the phone.
slaid480 said:
you can do this without scipt it's easy, first,flash CF-Root kernel in recovery , then go to the app drawer then open the EXT4 app, then covert to ext4 this operation will take about 2-3 min in recovery,of course you need to have CWM4,at the end it wiil reboot you phone so enjoy it
Press the thanks butom if I helped
Click to expand...
Click to collapse
already have CF Root kernel and CWM 5.0.26
an0nym0us_ said:
that ketut's script can only be use on odin files, cannot be use on already installed rom. btw cfroot ext4manager app should be able to do it directly from the phone.
Click to expand...
Click to collapse
ketut mentioned it is possible to do so on a pre-existing ROM but he doesn't recommend it haha.
Hmmm, i do not know why i don't have the ext4manager app even though i am on CF Root b82 kernel. Do i have to download the ext4manager app separately?
=====================================================================================================================
EDIT
I found the ext4manager on chainfire's post. Will install v1.3 and do the necessary file system conversion... and pray it works!
=========================================================
Update
It was my tardiness that led me to use chainfire's original ext4manager where i should have been using the version modified by ketut!
It worked like a breeze, install and the whole thing was done under a minute in recovery. I am very very happy with the results for i managed to gain about 400 points in Quadrant. Well, i couldn't get a OC kernel to work with my Stock ROM but this mod is ain't exactly that bad in coaxing out some performance.
slaid480 said:
you can do this without scipt it's easy, first,flash CF-Root kernel in recovery , then go to the app drawer then open the EXT4 app, then covert to ext4 this operation will take about 2-3 min in recovery,of course you need to have CWM4,at the end it wiil reboot you phone so enjoy it
Press the thanks butom if I helped
Click to expand...
Click to collapse
hey i have installed and tried that but it seems like ext4 manager is showing no ext4 partitions found ? did it converted to ext4 or still am on rfs
Lijop said:
hey i have installed and tried that but it seems like ext4 manager is showing no ext4 partitions found ? did it converted to ext4 or still am on rfs
Click to expand...
Click to collapse
did you use ext4manager from ketut's thread?
http://forum.xda-developers.com/attachment.php?attachmentid=714285&d=1315543936
ext4manager MUST detect your cf root kernel. if it does, it will automatically show the various partitions and the file system applicable.
happily1986 said:
did you use ext4manager from ketut's thread?
http://forum.xda-developers.com/attachment.php?attachmentid=714285&d=1315543936
ext4manager MUST detect your cf root kernel. if it does, it will automatically show the various partitions and the file system applicable.
Click to expand...
Click to collapse
CF-Root-S5830-v3.7-b82-ex. am using this. chainfire stuff
Lijop said:
CF-Root-S5830-v3.7-b82-ex. am using this. chainfire stuff
Click to expand...
Click to collapse
thats just the kernel itself. scroll down and find CF Root S5830 ext4 v1.3 in the post by ketut if you want to. btw the link i posted earlier on is the actual download link for the ext4 manager that has been modified to work for S5830 by ketut.
Will this method work on all Galaxy ACE versions. My wife has the version for Latin America, same as the one sold in Brazil and Chile.
Not sure about the ROM version for this one though.
Does stock ROM kernel even support ext4???
could u help for installing CF Root ?
i have a stock rom 2.3.3
thanks in advance
http://acetips.wordpress.com/2011/10/11/flash-cf-root-ace-gb/
ducutu said:
http://acetips.wordpress.com/2011/10/11/flash-cf-root-ace-gb/
Click to expand...
Click to collapse
Like a Michael Jackson music video...
Q&A for [HACK]Partition Table Tool for LG L90(really more data)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [HACK]Partition Table Tool for LG L90(really more data). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello, I've tried your script but now I'm not able ro mount cache or flash the stock rom. If you could help me this would be great!
http://forum.xda-developers.com/lg-l90/help/flash-stock-rom-t2953340
Kind regards
I think that this is not a fault repartitioning but rather drivers. Try select "CS_EMERGENCY" for PhoneMode.
If you can not to mount cache format try in recovery. If not working try this:
Code:
adb shell
make_ext4fs /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
reboot recovery
BigMajster said:
I think that this is not a fault repartitioning but rather drivers. Try select "CS_EMERGENCY" for PhoneMode.
If you can not to mount cache format try in recovery. If not working try this:
Code:
adb shell
make_ext4fs /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
reboot recovery
Click to expand...
Click to collapse
Hello, thank you for helping me! But when I boot the phone into Cyanogenmod, your commands doesn't work.
Code:
C:\adb>adb shell
$ make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p33
open: Permission denied
$
Edit.: Oh man, just forgot the su! Now I'm able to mount cache! Thanks a lot! But I still can't flash the stock rom. Any idea?
j8o said:
Hello, thank you for helping me! But when I boot the phone into Cyanogenmod, your commands doesn't work.
Code:
C:\adb>adb shell
$ make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p33
open: Permission denied
$
Edit.: Oh man, just forgot the su! Now I'm able to mount cache! Thanks a lot! But I still can't flash the stock rom. Any idea?
Click to expand...
Click to collapse
Code:
adb shell
su
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p32
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p34
reboot recovery
BigMajster said:
Code:
adb shell
su
make_ext4fs /dev/block/mmcblk0p32
make_ext4fs /dev/block/mmcblk0p33
make_ext4fs /dev/block/mmcblk0p34
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p32
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p33
tune2fs -c 0 -i -1 -C -1 /dev/block/mmcblk0p34
reboot recovery
Click to expand...
Click to collapse
I've run all this commands but it didn't helped.
j8o said:
I've run all this commands but it didn't helped.
Click to expand...
Click to collapse
Code:
adb shell
su
parted -s /dev/block/mmcblk0 print
and upload screenshot
BigMajster said:
Code:
adb shell
su
parted -s /dev/block/mmcblk0 print
and upload screenshot
Click to expand...
Click to collapse
Code:
# parted -s /dev/block/mmcblk0 print
sh: parted: not found
#
You boot system, so how problem have you now?
You boot system, so how problem have you now?
Click to expand...
Click to collapse
I'm not able to flash the stock rom.
Update. I get the phone to read adb serial # but it says offline. I'm having trouble trying to flash a custom recovery into it right now. Its a little more own tho.. I spend some time guessing random passwords. Should I stop that? I probably won't pick it by I might do more damage. Dammit my other one a brick too. Now all I have left that work are this galaxe s3 and an evo 4g with a cracked to hell screen. I can experiment on the l90 and the lg lucid till they work or break. Any help is appreciated..
To the op, you might want to put a disclaimer on this thread. Seems a little chancy to me.
[help] D405n stuck after trying tu use "Partition Table tool for LG L90"
Hi,
First this is my first post on this forum, so I can't post directly on the "Partition Table Tool for LG L90" thread
I use candy5 rom and twrp.
My problem is after I have used the partition tool, I have re-flash candy5 custom rom, and now it's stuck at the rom boot, and I'm unable to enter the recovery. So it seems to be bricked :-/
In adb my devices is detect but offline.
Can someone help me?
Thanks.
grizzzlly said:
Hi,
First this is my first post on this forum, so I can't post directly on the "Partition Table Tool for LG L90" thread
I use candy5 rom and twrp.
My problem is after I have used the partition tool, I have re-flash candy5 custom rom, and now it's stuck at the rom boot, and I'm unable to enter the recovery. So it seems to be bricked :-/
In adb my devices is detect but offline.
Can someone help me?
Thanks.
Click to expand...
Click to collapse
What is size of partition? Gapps installed?
I have choose "maximal" option, gapps not installed
Try to install CM11 maybe Candy takes up too much space
yup, but my real problem now is just I can't enter in the recovery.
Why? You can go to recovery by key combo
exactly, the key combo works but the device reboot before entering the recovery.
If you want to restore it to life using this method http://forum.xda-developers.com/lg-l90/general/guide-flash-stock-kdz-offline-lg-l90-t2803479 but select "CS_EMERGENCY" for PhoneMode.
Unless there is no other option.
thanks, ill try this.
But I think it will not work cause my device don't boot and so is no detected on my computer.:crying:
Hi, does anyone have or can anyone get me the gpt partition data blocks and all? Shouldn't really matter what rom. Preferably any of the released stock ones.
Just working on creating an unbrick tool. Potentially resolving the service code error.
Something like this (from a chinese phone so no it won't work and would require my brain in overtime to work it out manually):
add -b 40 -s 131072 -t efi -u C12A7328-F81F-11D2-BA4B-00A0C93EC93B -l ESP -T 0 -P 0 /dev/block/mmcblk0
add -b 131112 -s 131072 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF0 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 262184 -s 32768 -t data -u 80868086-8086-8086-8086-000000000100 -l boot -T 3 -P 15 /dev/block/mmcblk0
add -b 294952 -s 32768 -t data -u 80868086-8086-8086-8086-000000000101 -l recovery -T 3 -P 14 /dev/block/mmcblk0
add -b 327720 -s 32768 -t data -u 80868086-8086-8086-8086-000000000102 -l fastboot -T 3 -P 13 /dev/block/mmcblk0
add -b 360488 -s 32768 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF1 -l reserved_1 -T 3 -P 0 /dev/block/mmcblk0
add -b 393256 -s 131072 -t data -u 80868086-8086-8086-8086-000000000104 -l test -T 3 -P 12 /dev/block/mmcblk0
add -b 524328 -s 65536 -t data -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 589864 -s 32768 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 622632 -s 32768 -t data -u 80868086-8086-8086-8086-000000000003 -l misc -T 0 -P 0 /dev/block/mmcblk0
add -b 655400 -s 32768 -t data -u 80868086-8086-8086-8086-000000000004 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 688168 -s 2097152 -t data -u 80868086-8086-8086-8086-000000000005 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 2785320 -s 524288 -t data -u 80868086-8086-8086-8086-000000000006 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 3309608 -s 3145728 -t data -u 80868086-8086-8086-8086-000000000007 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 6455336 -s 16777216 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0
I've got this data so far and a way to write it if I can get the above
bos mmcblk0p1
bosbackup mmcblk0p2
ulogo mmcblk0p3
logo mmcblk0p4
boot mmcblk0p5
recovery mmcblk0p6
cid mmcblk0p7
sp mmcblk0p8
panic mmcblk0p9
devtree mmcblk0p10
devtreeBackup mmcblk0p11
pds mmcblk0p12
misc mmcblk0p13
cache mmcblk0p14
cdrom mmcblk0p15
system mmcblk0p16
userdata mmcblk0p17
Flacid Monkey said:
Hi, does anyone have or can anyone get me the gpt partition data blocks and all? Shouldn't really matter what rom. Preferably any of the released stock ones.
Just working on creating an unbrick tool. Potentially resolving the service code error.
Something like this (from a chinese phone so no it won't work and would require my brain in overtime to work it out manually):
add -b 40 -s 131072 -t efi -u C12A7328-F81F-11D2-BA4B-00A0C93EC93B -l ESP -T 0 -P 0 /dev/block/mmcblk0
add -b 131112 -s 131072 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF0 -l reserved -T 0 -P 0 /dev/block/mmcblk0
add -b 262184 -s 32768 -t data -u 80868086-8086-8086-8086-000000000100 -l boot -T 3 -P 15 /dev/block/mmcblk0
add -b 294952 -s 32768 -t data -u 80868086-8086-8086-8086-000000000101 -l recovery -T 3 -P 14 /dev/block/mmcblk0
add -b 327720 -s 32768 -t data -u 80868086-8086-8086-8086-000000000102 -l fastboot -T 3 -P 13 /dev/block/mmcblk0
add -b 360488 -s 32768 -t data -u 80868086-8086-8086-8086-FFFFFFFFFFF1 -l reserved_1 -T 3 -P 0 /dev/block/mmcblk0
add -b 393256 -s 131072 -t data -u 80868086-8086-8086-8086-000000000104 -l test -T 3 -P 12 /dev/block/mmcblk0
add -b 524328 -s 65536 -t data -u 80868086-8086-8086-8086-000000000001 -l panic -T 0 -P 0 /dev/block/mmcblk0
add -b 589864 -s 32768 -t data -u 80868086-8086-8086-8086-000000000002 -l factory -T 0 -P 0 /dev/block/mmcblk0
add -b 622632 -s 32768 -t data -u 80868086-8086-8086-8086-000000000003 -l misc -T 0 -P 0 /dev/block/mmcblk0
add -b 655400 -s 32768 -t data -u 80868086-8086-8086-8086-000000000004 -l config -T 0 -P 0 /dev/block/mmcblk0
add -b 688168 -s 2097152 -t data -u 80868086-8086-8086-8086-000000000005 -l cache -T 0 -P 0 /dev/block/mmcblk0
add -b 2785320 -s 524288 -t data -u 80868086-8086-8086-8086-000000000006 -l logs -T 0 -P 0 /dev/block/mmcblk0
add -b 3309608 -s 3145728 -t data -u 80868086-8086-8086-8086-000000000007 -l system -T 0 -P 0 /dev/block/mmcblk0
add -b 6455336 -s 16777216 -t data -u 80868086-8086-8086-8086-000000000008 -l data -T 0 -P 0 /dev/block/mmcblk0
I've got this data so far and a way to write it if I can get the above
bos mmcblk0p1
bosbackup mmcblk0p2
ulogo mmcblk0p3
logo mmcblk0p4
boot mmcblk0p5
recovery mmcblk0p6
cid mmcblk0p7
sp mmcblk0p8
panic mmcblk0p9
devtree mmcblk0p10
devtreeBackup mmcblk0p11
pds mmcblk0p12
misc mmcblk0p13
cache mmcblk0p14
cdrom mmcblk0p15
system mmcblk0p16
userdata mmcblk0p17
Click to expand...
Click to collapse
U can get the gpt.bin from one of the ota 4.4.2 update packages or even from a JB RSD-Lite package.
My phone also dead (software failure somewhere) so can't get u the info from the phone itself.
I setup Lineage 16 on my Xperia X and encrypted the phone. Now whenever I try other ROMS (installed from twrp) it always asks for my encryption password in TWRP and on bootup. I've already tried wiping all of the partitions, I've tried changing the filesystems, I've tried the ADB command ./adb shell recovery --wipe_data --set_filesystem_encryption=off
Encryption is still intact. What can I do to nuke the phone?
I experienced something similar a while ago and if I recall correctly then played around in TWRP with "repair filesystem", and finally I got it working unencrypted again
I was in the same situation. The only way for me was to install a stock fw with Flashtools (while in bootloader mode)...and start again from zero.
Connect to PC and enter recovery
Then type following commands
Caution!!
You will lose all data!!
$ adb shell
# umount /data
# umount /sdcard
# make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
This is pure format command. Encryption will be removed.
But only these commands we loose crypt footer. (We can never re-encrypt)
You had better add these commands also.
$ adb shell
# umount /data
# umount /sdcard
# make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/userdata
(Upper section commands)
# e2fsck -f /dev/block/platform/msm_sdcc.1/by-name/userdata
(You should check "Block count" section)
# resize2fs -f /dev/block/platform/msm_sdcc.1/by-name/userdata xxxxxxxx
Click to expand...
Click to collapse
If "Block count" equals 2991611, type like this (subtract 4 from block count... 2991611-4=2991607)
# resize2fs -f /dev/block/platform/msm_sdcc.1/by-name/userdata 2991607
Click to expand...
Click to collapse