First of all, the thread about omap4boot: http://forum.xda-developers.com/showthread.php?t=1971014
I didn't create this tool, I just found out a way to make it works with our phone, and maybe I'm not the first (tested under Windows 7 Ultimate 32-bit).
What do you need:
omap4boot, get it from original thread.
Extract omap4boot archive somewhere like C:\omap4boot (I will use this path in the tutorial).
Power off your phone and remove the battery.
Connect your phone (still without the battery) to the PC.
You will hear the sound of a new driver, then the sound of a driver when it disconnects continiusly.
Start -> Right click on "Computer" -> "Manage".
On the left column, click on "Device manager".
You will see a device that appear and disappear under "Other/Unknown Devices".
You must right click on the unknown device before it disappear, once clicked select "Driver Update". (You can use this tip to make the process easier http://forum.xda-developers.com/showthread.php?p=51019004).
Click on the second button (manually install driver) and insert the "usb_drv_windows" path (C:\omap4boot\usb_drv_windows) and install the driver.
Disconnect the phone from the PC and power it off.
Open a command prompt (Win+R, type cmd and press Enter).
Type the following command in the command prompt:
Code:
cd C:\omap4boot
start-fastboot.bat
Now input 3 (Prada 3.0 P940) and press enter.
Plug the phone without battery to the PC, when the tool says "Wait 5 seconds" put the battery in your phone.
(The first time that you do this, you have to install the drivers again. Repeat step 9)
At the other prompts answer always "N", this could be important.
Now you can use fastboot on L9 Next times you can start from step 12.
{
"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"
}
(the red rettangle isn't important here )
Sorry for my english, if someone wants to review the tutorial just send me a PM.
I test it when I do recovery.img (we need to sign it, I will try with prada keys).
Has anyone tried to flash something?
Do you think it won't brick our phone. It flashes new u-boot.
On W8 x64 when I install driver I get Not signed INF.
What FW have you got? 10g or other?
artas182x said:
I test it when I do recovery.img (we need to sign it, I will try with prada keys).
Has anyone tried to flash something?
Do you think it won't brick our phone. It flashes new u-boot.
On W8 x64 when I install driver I get Not signed INF.
What FW have you got? 10g or other?
Click to expand...
Click to collapse
I flashed some stock partitions (recovery, boot) on ITALIAN WIND 10D but I can't confirm if the security error appear or not now.
When i tried to flash system.img fastboot said something like "file too large".
At the step 15 I said to answer N, otherwise the tool should flash new u-boot and I'm not sure if it works on our L9.
Maybe on a 64-bit system you have to disable the driver signature check, the bad thing is that (on Windows 7) you have to do it manually at every boot.
Odp: fastboot on our L9 with omap4boot
I try this today. Maybe it's a way to soft unbrick our l9 (without kdz).
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
artas182x said:
I try this today. Maybe it's a way to soft unbrick our l9 (without kdz).
Wysyłane z mojego LG-P760 za pomocą Tapatalk 2
Click to expand...
Click to collapse
Yes this should make the phone unbrickable (i think a backup is needed), but as I said I got problems flashing the system.img.
Also, if we get a security error flashing a custom recovery/boot.img we can restore the original recovery/boot.img in seconds without LG Support Tool.
R: fastboot on our L9 with omap4boot
Se need to try u boot from Prada..maybe work!
Inviato dal mio LG-P760 con Tapatalk 2
Bootloader is LK MAY-2012 in Prada 3.0 and our L9. It can work.
artas182x said:
Bootloader is LK MAY-2012 in Prada 3.0 and our L9. It can work.
Click to expand...
Click to collapse
I can try but how to restore the stock u-boot if things won't going well?
I think we can restore with kdz, but I'm not sure.
artas182x said:
I think we can restore with kdz, but I'm not sure.
Click to expand...
Click to collapse
Looking in the omap4boot's files seems that it dumps "x" and "u" partitions (when it dumps the locked loader).
I will backup those partitions to have a possibility of restore with fastboot.
Should I follow the procedure for Prada P940?
i think as same as you,if you can get into recovery, in theory you could install kdz rom.
Maybe I did something wrong but it didn't work..
What I've done:
Start fastboot
When the tools asked for u-boot replace, I said "Y".
fastboot replaced u-boot, then I ran "fastboot reboot".
Black screen. Removed battery and USB, polugged in battery and press power, still black screen.
Started fastboot again and ran "fastboot flash u-boot u.img" (u.img was my backup of u partition)
Then the phone restarted normally with "fastboot reboot".
I was on 10D Wind ITA. The black screen is scary :silly: but this confirms that with fastboot we can restore every partition.
I tried to restore system and phone restarted like in your phone.
artas182x said:
I tried to restore system and phone restarted like in your phone.
Click to expand...
Click to collapse
How did you restore system? fastboot said to me "remote: data too large" or similar.
I didn't restore system beacuse it reboot phone. Have you got good system dump. I did correct system dump using dd if= of=.
artas182x said:
I didn't restore system beacuse it reboot phone. Have you got good system dump. I did correct system dump using dd if= of=.
Click to expand...
Click to collapse
These are the commands that I used some time ago to restore the phone (without the recovery):
Code:
#adb shell su -c busybox dd if=/sdcard/BACKUP/boot.img of=/dev/block/mmcblk0p3
#adb shell su -c busybox dd if=/sdcard/BACKUP/cache.img of=/dev/block/mmcblk0p12
#adb shell su -c busybox dd if=/sdcard/BACKUP/divxkey.img of=/dev/block/mmcblk0p5
#adb shell su -c busybox dd if=/sdcard/BACKUP/fota.img of=/dev/block/mmcblk0p8
#adb shell su -c busybox dd if=/sdcard/BACKUP/misc.img of=/dev/block/mmcblk0p6
#adb shell su -c busybox dd if=/sdcard/BACKUP/mlt.img of=/dev/block/mmcblk0p14
#adb shell su -c busybox dd if=/sdcard/BACKUP/nv.img of=/dev/block/mmcblk0p7
#adb shell su -c busybox dd if=/sdcard/BACKUP/persist.img of=/dev/block/mmcblk0p13
#adb shell su -c busybox dd if=/sdcard/BACKUP/recovery.img of=/dev/block/mmcblk0p4
#adb shell su -c busybox dd if=/sdcard/BACKUP/reserved.img of=/dev/block/mmcblk0p9
#adb shell su -c busybox dd if=/sdcard/BACKUP/u.img of=/dev/block/mmcblk0p2
#adb shell su -c busybox dd if=/sdcard/BACKUP/x.img of=/dev/block/mmcblk0p1
#adb shell su -c busybox dd if=/sdcard/BACKUP/userdata.img of=/dev/block/mmcblk0p11
#adb shell su -c busybox dd if=/sdcard/BACKUP/system.img of=/dev/block/mmcblk0p10
I obtained the imgs with the inverse command.
Anyway you mean you got a black screen?
Has anyone had any luck restoring system.img?
Ive been thinking of different theories on how to save those who updated to 10G on P769BK. One of which is making a system.img dump from a phone that was able to preserve root with Voodo OTA restore and using this tool to flash onto phones that lost it.
I'm not too familiar with fastboot commands but if anyone can help me with how to pull the system partition and reflash to another phone I'll gladly guinea pig...got a couple of these suckers lying around
Jrkoffjonson said:
Has anyone had any luck restoring system.img?
Ive been thinking of different theories on how to save those who updated to 10G on P769BK. One of which is making a system.img dump from a phone that was able to preserve root with Voodo OTA restore and using this tool to flash onto phones that lost it.
I'm not too familiar with fastboot commands but if anyone can help me with how to pull the system partition and reflash to another phone I'll gladly guinea pig...got a couple of these suckers lying around
Click to expand...
Click to collapse
It seems that system partition is too big to flash with fastboot, the only way to restore is with dd but a rooted phone is needed.
sguerrini97 said:
It seems that system partition is too big to flash with fastboot, the only way to restore is with dd but a rooted phone is needed.
Click to expand...
Click to collapse
Well that stinks, so much for that idea :'[
System dump file
After downloading the zip linked in the OP I found a dump batch file called 'dump_prada.bat' in the zip.
Took a look into it and modified it to work with our device to do an easy system wide dump.
It works, but only if you have an external sd card as our internal storage is too small to hold the files before transferring to the computer.
I'm attaching it as a .txt file- just rename it to full_dump.bat and run as admin.
Not taking any credit for the original script..
Related
All credits go to pulpoff2 for this! This is not by me, I am merely the messenger. Only thing I did was to ask pulpoff for the files and a tutorial With his permission I will share it with you.
This will provide you with a fresh and unmodified 2.1-system, exactly like you would do the official update - only exception is that it is rooted. So all the apps and games of the official firmware are available and nothing else. You can remove the crap (like the games or timescape for example) by yourself after doing the steps below.
UPDATE:
There is a newer ROM by propc you can use instead of this one. Look here:
http://forum.xda-developers.com/showthread.php?t=888427
-- NEW --
propc kindly provides us with a shellscript to automate the steps below. See here for the script and a short manual:
http://forum.xda-developers.com/showpost.php?p=10067921&postcount=120
If the script doesn't work for you or you prefer to do things the manual way, you may use the steps below.
Download these files:
x8-2.1rooted.img.yaffs.rar
and
ISO-8859-1__unyaffs-arm.rar
Also download the 2.1-firmware from here or here. Unpack it on your computer and delete the "system.sin".
Unpack "x8rooted.img", "busybox" and "unyaffs" to SDcard.
You need 1.6 with root on your phone. By the way, all the data on your phone will be lost after doing the following steps, so making a backup is advised.
Use "adb shell" to connect to your phone and become su:
Code:
su
Copy "busybox" and "unyaffs" to /data/local/tmp. (Pulpoff says you should copy to /sbin, but this requires remounting with busybox. I copied to /sbin, but I think /data/local/tmp should work just fine)
Code:
cd /data/local/tmp
cat /sdcard/busybox > busybox
cat /sdcard/unyaffs > unyaffs
chmod the files to make them executable:
Code:
chmod 755 busybox
chmod 755 unyaffs
EDIT: If you want to copy the files to /sbin (like pulpoff2 advises), you can do this OPTIONAL step:
EDIT2: It was confirmed that this is indeed not necessary!
Remount the root directory to make /sbin writable. Then copy the files over and change the working directory to /sbin:
Code:
[strike]
./busybox mount -o remount,rw /
./busybox cp -prf busybox /sbin/
./busybox cp -prf unyaffs /sbin/
cd /sbin[/strike]
Remount /system as writable:
Code:
mount -o remount,rw /dev/block/mtdblock0 /system
Switch to busybox shell:
Code:
./busybox sh
Remove /system (yes, really!). It's normal to get errors because of the "lost+found"-folders. Ignore the errors.
Code:
./busybox rm -r /system
Unpack pre-rooted image to system. It should output "end of image" if it finishes correctly.
Code:
./unyaffs /sdcard/x8rooted.img /system
Your phone won't boot anymore now and it will crash as soon as you try to use it - that's normal! Go to next step.
Just remove the battery and the usb-cable from the phone, then re-attach the battery. Flash 2.1-kernel (without system.sin !!) using the flasher-tool by Bin4ry. If the flasher gives you an error because of a missing "loader.sin" you can take this file from the 1.6-firmware. Refer to Bin4ry's thread to learn how to use his flasher and how to enter flash-mode on your phone.
The phone should now boot, although the first boot can take a little while. If you get into a boot-loop or you just see the white sony ericsson logo (not the green one after the animation) for several minutes, it probably didn't work and you have to start over again by flashing 1.6.
This was written as I remember how I did it by myself. It worked for me at first try! If it works for you, please click the thanks-button. It will make me feel better
After you have your nice rooted 2.1 you probably want to enable JIT for a nice performance boost.
But does it have root? Bad reading.
{
"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"
}
a-k-t-w said:
But does it have root?
Click to expand...
Click to collapse
Absolutely. But no busybox. So if you plan to enable JIT, you have to copy busybox to /system/bin by yourself.
a-k-t-w said:
But does it have root? Bad reading.
Click to expand...
Click to collapse
of course it is rooted.
now we know what to do with unyaffs.
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
csengoi said:
2 things:
1. I've bought the phone with 1.6 android, but I was unable to root it with any method, then I've upgraded to 2.1 update 1. Is there any way to root it?
2. I have Hungarian language. Does it contain Hungarian language?
Click to expand...
Click to collapse
1: There is no way to directly root a phone with 2.1. You need to go back to 1.6, root it and then follow the above steps.
2: I guess so. As far as I know the firmware is the same for all countries.
Works like a charm! I removed the /system folder contents one by one though, using the method from the previous thread. Anyway, the first time I tried, unyaffs exited before extracting all the files (maybe the phone ran out of memory?). I didn't notice it and went on to flash the phone, ending up stuck at the Sony Ericsson logo. So, make sure that unyaffs reports that it has reached the "end of image" before moving on to the next step!
Thanks!!
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
isaac12 said:
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
how to proceed?
Click to expand...
Click to collapse
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
---dobule post--- sorry
trapacska said:
in adb shell:
enter su and you have to look your mobile screen because it will ask you to allow su. (if you rooted well your phone)
i had this problem when i didn't press the allow button in superuser confirmation.
Click to expand...
Click to collapse
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
WARR10r said:
does it mount data.img on sdcard???
or i'll need to use chargemon from previous way?
Click to expand...
Click to collapse
This has nothing to do with App2SD. Also the ROM gets loaded from internal flash, not from sdcard. The result is the same as with the official update, but with root.
If you want to have /data on sdcard, use the modified chargemon or neptun2's method.
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
try adding ./ before
gully666uk said:
I'm totally new to android but somehow i managed to get to number 8, and I have no idea how to switch to busybox shell, can somebody explain this bit in lamens terms please.
Click to expand...
Click to collapse
You should still be in "/data/local/tmp" as the working directory (check with "pwd"-command). If you followed the steps correctly, you should have a working busybox-file in there. So just type "busybox sh". If it looks like it does nothing, it's all right
isaac12 said:
rooted phone yes
su confirmed
cd /data/local/tmp
cat /sdcard/busybox > busybox invalid lenght
cat /sdcard/unyaffs > unyaffs invalid lenght
Click to expand...
Click to collapse
try to use another su. i rooted my x8 with superoneclick 1.5.0
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Sectoras said:
I got stuck at SE logo for at least 10mins, it doesnt re-boot cycle although..
Click to expand...
Click to collapse
That's way too long, something isn't right there. To start over again you have to flash back to 1.6.
Ok I had not realised the superuser permissions was not popping up on my phone that's sorted now. I get to number 8 again and it said permission denied
Hello,
i wish to create an update.zip to copy fonts from the zip into the system/fonts/ folder because i delete them and kept one font but it seems android doesn't boot with one font only need other fonts to be there (or atleast matching the names) to be able to boot.
adb push doesn't work giving me permission denied because /system is not mounted R/W (which i do using Super Manager for example)
i read other update.zip files and it seems i need to create CERT.SF and MANIFEST.MF files in META-INF , but it seems there are some SHA1-Digest: below each file (is this a md5checksum?) so i can't just replace file names and apply it
any ideas how can i do it without Wipe data/factory reset ? (and if factory reset is my last option would fonts be returned or factory reset doesn't get fonts back? i feel not)
Thanks
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
l0st.prophet said:
The app below will sign the zip and allow you to flash it. You just need to put the zip inside the folder and call it 'update.zip'
Click to expand...
Click to collapse
Thank you , any chance there i a Linux version out there? i'm using adb on ubuntu
and for CERT.SF and MANIFEST.MF i just create them manually based on any update.zip file i download earlier?
I'm on windows now and i've signed the file, when i try to apply it from recovery i get
E:signature verification filed
Installation aborted
what i'm missing?
attached my signed update.zip
it seems i had a folder update inside the zip
i have re-created one and signed it and still same error
attached the file
btw as i'm rooted and i used to su from adb shell and terminal emulator earier, any idea why su not working now?
$ su
[1] + Stopped (signal) su
$
[1] Segmentation fault su
$
is it because i'm on the HeRO logo boot screen ? it didnt get in yet?
btw for linux/ubuntu users who want to sign on linux you can use this:
Code:
java -jar signapk.jar testkey.x509.pem testkey.pk8 update.zip update_signed.zip
inside the Auto Sign folder
after signing on linux i get the following:
E: failed to read footer from / sdcard/update.zip (I/O error)
E:signature verification failed.
Installation aborted
First of all, please use the edit button, posting 6 times in a row is very hard to read, and is considered bumping your own thread which is a quick way to lose friends.
Secondly, the autoSign program creates a file called update_signed.zip which is the file you need to flash, the cert and manifest files are created by the process, you don't need to touch them. I have attached a signed version of your zip
I resigned it for you, see attachment. I use "androsign" I found here somewhere on XDA, maybe go look for it. It is a very easy tool edit: Too late
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
First of all , sorry for the multiple posts
second i've tried both update-signed.zip and update_signed.zip and both of them gave me the same error
{
"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"
}
*P.S: sorry if i'm not allowed to put an image ill delete it
EDIT:
riemervdzee said:
When you are in "adb shell" you should have SU rights already.
Otherwise there is an option in adb to switch to SU rights, just type in "adb help" of a howto.
Click to expand...
Click to collapse
i tried to the help i didn't find how to set su in the right roots?
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
riemervdzee said:
Have you flashed an alternative recovery at all? This one looks like the default one.
And look at the first error, it asks for a path in /cache/... Just get amon_ra recovery This way you can select which zip you want to flash (as long as they are in the root of the sd-card).
And from "adb help":
"adb root - restarts the adbd daemon with root permissions".
However seen you still have the original recovery, that probably won't work in recovery.
You said you rooted the device already right? maybe you can move the files with adb then when the ROM is trying to start, and after everything works get a real recovery where you can do something.
Click to expand...
Click to collapse
yeah i tried the adb root already but getting "adbd cannot run as root in production builds"
yes i'm rooted and everything is fine
btw why deleting fonts prevents the phone from booting although there is one font there "not the default one"
what i want is to push the font files into the phone but getting the error i mentioned earlier that its not mounted as as R/W:
[email protected]:~/linux_adb_fastboot/hero_fonts$ for i in `cat list`; do adb push $i /system/fonts/$i ; done
failed to copy 'DroidSerif-Bold.ttf' to '/system/fonts/DroidSerif-Bold.ttf': Read-only file system
failed to copy 'DroidSerif-Regular.ttf' to '/system/fonts/DroidSerif-Regular.ttf': Read-only file system
failed to copy 'DroidSerif-Italic.ttf' to '/system/fonts/DroidSerif-Italic.ttf': Read-only file system
failed to copy 'DroidSansMono.ttf' to '/system/fonts/DroidSansMono.ttf': Read-only file system
failed to copy 'DroidSansFallback.ttf' to '/system/fonts/DroidSansFallback.ttf': Read-only file system
failed to copy 'DroidSerif-BoldItalic.ttf' to '/system/fonts/DroidSerif-BoldItalic.ttf': Read-only file system
failed to copy 'DroidSans-Bold.ttf' to '/system/fonts/DroidSans-Bold.ttf': Read-only file system
failed to copy 'Clockopia.ttf' to '/system/fonts/Clockopia.ttf': Read-only file system
failed to copy 'DroidSans.ttf' to '/system/fonts/DroidSans.ttf': Read-only file system
and yes adb remount doesn't work
[email protected]:~/linux_adb_fastboot/hero_fonts$ adb remount
remount failed: Operation not permitted
You have "rooted" your phone but you can't get adb root? That is contradictory
But since I'm in a good mood. Try to boot up the phone on your ROM, so not in recovery or bootloader. Then try to remount.
If remount is still failing, you don't have root.
Maybe you should also read your stuff a bit in before attempting anything. You are kinda screwing up your phone here.
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Bashar . said:
Yes i'm sure i'm rooted i had universal root which i can root and unroot, and before deleting the fonts i used to do su and get root
also to confirm im rooted i used to use Market Access to access US and other markets to buy (since my country only has free apps not paid yet)
i didn't get the part of botting up the phone using my ROM ?
also a side question when booting the phone normally (i think this is what you meant about booting into the ROM?) and it stays on the HeRO logo as you can see i can access the adb shell etc.. so the phone is actually responding but not booting because of the fonts not there? or something else could be broken ?
Click to expand...
Click to collapse
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
riemervdzee said:
Read "adb logcat" or in adb shell, use the linux command "dmesg" to see what is wrong.
And yes, with booting your ROM I mean the normal boot process. But probably android won't start as it can't find the fonts (they are essential).
And really... Read your stuff. You deleted fonts but didn't put any new there yet? You are asking for problems, while you ask us to solve it.
Then you come up with the plan to flash the new fonts, but you don't have a customized recovery.
Click to expand...
Click to collapse
I did put one font there, but my mistake is not renaming it as the default font names that was there, i thought it would scan the fonts folder and use ANY font listed there
but seems not...
catlog shows im missing the fonts: http://dpaste.org/ADyJ/
dmesg output: http://dpaste.org/8IGw/
i never thought the recover it had won't let met flash the fonts
EDIT: i tried the mv command as linux user but my main problem is that its a read only system
[email protected]:~$ adb shell
$ cd system
$ cd fonts
$ ls
DroidSansArabic.ttf
$ mv
USAGE: mv <source...> <destination>
$ mv DroidSansArabic.ttf DroidSans.ttf
failed on 'DroidSansArabic.ttf' - Read-only file system
$
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
riemervdzee said:
You can't do "adb remount" when starting normally? You have rooted the ROM, not the recovery (which refuses root access, as it is still the default one).
If everything fails, you can always do a RUU. (google "hero RUU"), this will reset everything as HTC wants it. Then you start from scratch again.
Click to expand...
Click to collapse
yeah it seems thats my only option
I was hoping to learn by fixing, i'll flash it tomorrow then
now back to the question, why the update.zip that we were trying to sign is not flashable or signable ? what might be the reason? is it because i didn't root the recovery ?
i tried an stock Hero rom and still gives me invalid signature, i can't apply any rom at all now or what?
there is a logo of the telcom operators at the first screen while booting , no mater which version of kdz i flashed on the phone ,it appears always .
so i just wonder how i can remove it ?
is there some body can give me an idea or some links to the guide threads ?
is there any body can help me ???
which logo? we dont see any on our p765 except LG logo. take screenshot with another camera and post.
cmahendra said:
which logo? we dont see any on our p765 except LG logo. take screenshot with another camera and post.
Click to expand...
Click to collapse
the phone is ordered by China Union Communication Company. and it replaced the lg logo with it's 3g logo like this.
{
"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"
}
cmahendra said:
which logo? we dont see any on our p765 except LG logo. take screenshot with another camera and post.
Click to expand...
Click to collapse
I think the OP has a ROM (comes with the phone) with operator's mod, just like my P769 that shows T-Mobile.
Yes, the boot animation can be replaced. On easy way to do it, with a ROOTed phone, is to use this app:
https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations
flashing any latest matching rom from archive will replace it.
But its strange. You flashed hongkong v20d , right? you still have china logo?
mrmathematica said:
I think the OP has a ROM (comes with the phone) with operator's mod, just like my P769 that shows T-Mobile.
Yes, the boot animation can be replaced. On easy way to do it, with a ROOTed phone, is to use this app:
https://play.google.com/store/apps/details?id=com.jrummy.apps.boot.animations
Click to expand...
Click to collapse
no you disunderstood me . it's not an animation . but it's a picture which will stay some seconds before the boot animation of LG .
but thank you for your answer .
cmahendra said:
flashing any latest matching rom from archive will replace it.
But its strange. You flashed hongkong v20d , right? you still have china logo?
Click to expand...
Click to collapse
yes it's very strange ,and i flashed hongkong v20d .
and somebody told me if i flashed the kdz with the cable , the logo will disappear . but it doesn't work for me .
so i think should i "wipe data factory reset" and "wipe cache" before flashing ?
but when i tried to boot into recovery mod with "vol up" + "home" + "power" ,it just appear a "recovery mode" tip which tell me to remove and replace the battery and then reboot . nothing i can do .
then i tried to flash the recovery.img with adb commands . when i reboot into recovery with adb command "adb reboot recovery" the phone reboot into a dead robot .
so i don't know what i can do ......
PS : MY PHONE IS WITH LOCKED BOOTLOADER .
I think the splash screen you are talking about is included in uboot.
Which L9 model do you have ?
Lelus said:
I think the splash screen you are talking about is included in uboot.
Which L9 model do you have ?
Click to expand...
Click to collapse
model number : LG-P765
Baseband version : L6260_MODEM_SIC_01.1230.00
Kernel version : 3.0.31
Build number : JZO54K
mylk said:
model number : LG-P765
Baseband version : L6260_MODEM_SIC_01.1230.00
Kernel version : 3.0.31
Build number : JZO54K
Click to expand...
Click to collapse
use at your own risk
backup your current xloader and uboot and ask someone with rooted jb p765 (non-branded) to do the same
Code:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
then you restore nonbranded xloader and uboot
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
if something goes wrong and your phone doesn't boot you can restore your original files by using fastboot
Code:
fastboot flash x-loader p1.bin
fastboot flash u-boot p2.bin
mylk said:
MY p765 is from the mainland , so there is a logo of wo3g while booting .
lelus told me to replace the "xloader and u-boot" with them from other's unbranded phone , so i think it shoud be a P765 which is bought from HONGKONG and flashed on JB of V20D and it should be rooted .
and if you have a phone like that . can you backup your current xloader and uboot with the following code
Code:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
i can ensure this will do nothing but extract files from your phone . and it will not do harm to your phone . trust me !!!
if you succeed , copy your two files (p2.bin and p1.bin) . and mailed to me ([email protected]) . if you can't find them in your exernal_sd . open the file holder "dev" and set it read and write . then try again .
thank you very much .
Click to expand...
Click to collapse
Yes, at the moment I am on V20D P765 Hongkong Rom and both the files are attached here in Zip Format.
Stop making multiple threads for single issue. You may be reported by me or someone. (Actually reported)
Hope this helps.
use at your own risk
backup your current xloader and uboot and ask someone with rooted jb p765 (non-branded) to do the same
Code:
adb shell su -c busybox dd if=/dev/block/mmcblk0p2 of=/sdcard/external_sd/p2.bin
adb shell su -c busybox dd if=/dev/block/mmcblk0p1 of=/sdcard/external_sd/p1.bin
then you restore nonbranded xloader and uboot
Code:
adb shell su -c busybox dd if=/sdcard/external_sd/p2.bin of=/dev/block/mmcblk0p2
adb shell su -c busybox dd if=/sdcard/external_sd/p1.bin of=/dev/block/mmcblk0p1
if something goes wrong and your phone doesn't boot you can restore your original files by using fastboot
Code:
fastboot flash x-loader p1.bin
fastboot flash u-boot p2.bin
Click to expand...
Click to collapse
thank you very much .i think your method is OK , but i didn't boot into fastboot , so i didn't replace the files , but i flashed the EUROPEAN V20C OPEN . and the logo disappeared . thank you very much again .!!!
Yes, at the moment I am on V20D P765 Hongkong Rom and both the files are attached here in Zip Format.
Stop making multiple threads for single issue. You may be reported by me or someone. (Actually reported)
Click to expand...
Click to collapse
thank you for your help and your advices . i didn't use the files and i flashed the EUROPEAN V20C OPEN and the logo disappeared . thank you very much again .!!!
mylk said:
thank you for your help and your advices . i didn't use the files and i flashed the EUROPEAN V20C OPEN and the logo disappeared . thank you very much again .!!!
Click to expand...
Click to collapse
this is what i suggested u in 6th post.:silly:
can some one pull
can some one pull out x loader and uboot for lg p769
@aequitas3
As requested by you in PM, here are the P1 and P2 files from my UNLOCKED BOOTLOADER P765 V20D Hongkong.
http://www.multiupload.nl/Y7RBMGQINH
Posting here because it may be available to others also who may be interested.
Just to clarify so people won't start flashing these blindly, there is no difference in xloader p1 and uboot p2 whether phone has the bootloader unlocked or not and flashing above files alone won't unlock it.
i cant make it work.i have a bricked p768,can get to fastboot but always failed,partition does not existwhile tryng to write u-boot and x-loader.does this means that emmc is fried or what?
its the boot splash image
you need to rip the boot.img and change a particular file
if you are on stock, it'll be a pretty long process extracting the boot.img from a kdz.
and as far as i know, it wont work on a locked bootloader
This requires S-OFF to use, follow at your own risk!
This will let you unlock your bootloader without htcdev and also let you change your hboot watermark from RELOCKED back to stock LOCKED.
Advantages:
No having your data partition wiped
The ability to get back to 100% stock without any visual trace of having unlocked your bootloader
Does not modify the hboot so works independently and can be used with any hboot version
Works whether you've updated to KitKat or not as the specific block is not remapped by the OTA.
Credits:
scotty1223: I've linked to his M7 thread a few times in our old Desire 601 thread, now that we have our own section I figured I'd post the information here so people could better find and take advantage of it.Requirements:
ADB installed on your computer
Drivers for your phone installed on your computer (HTC Sync Manager will do that for you).
Device must be S-OFF
Device must be rooted
First Things First:
Before you do anything it is highly recommended that you backup the section of your phone this guide will be modifying.
Open a command prompt in your adb folder
Type adb shell and press enter.
Type su and press enter if needed to a get a root shell.
Type/paste dd if="/dev/block/mmcblk0p3" of="/storage/ext_sd/mmcblk0p3.img" and press enter
Now it will be backed up to your external SDCARD and we can continue.
Unlock your Bootloader:
Open a command prompt in your adb folder and do the following:
Type adb shell and press enter
Type su and press enter if needed to get a root shell
Rather than type it is recommended you paste the following:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 and press enter
Type exit and press enter
Type exit and press enter if needed to return to a normal command prompt
Type adb reboot bootloader and press enter
Verify you are now UNLOCKED
Regain your LOCKED status:
Open a command prompt in your adb folder and do the following:
Type adb shell and press enter
Type su and press enter if needed to get a root shell
Rather than type it is recommended you paste the following:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 and press enter
Type adb reboot bootloader and press enter
Verify you are now LOCKED
Notes:
I have personally tested this on my ZARA_CL both before and after updating to KitKat.
Confirmed by other users to work for ZARA_UL as well.
{
"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"
}
the unlock process is worked on my zara_ul....i dont know about the regain locked status
Lock\unlock worked on my Zara_UL (Europe). Thanks for guide.
Good looking out Duir, I know this will come in handy for me someday. Especially since it doesn't wipe ur data like HTC dev unlock process usually does.
Sent from my Virgin Mobile CDMA HTC Desire 601 zara_cl
I don't understand how to do this after updating to KK. You have to have root to gain #, right? And you can't root without a custom recovery. But you can't flash a custom recovery with a locked bootloader. So, which step am I missing here? My adb shell only accepts $.
Smellie2 said:
I don't understand how to do this after updating to KK. You have to have root to gain #, right? And you can't root without a custom recovery. But you can't flash a custom recovery with a locked bootloader. So, which step am I missing here? My adb shell only accepts $.
Click to expand...
Click to collapse
Flashing recovery through fastboot requires unlocked bootloader, but with S-OFF you can make a zip file and bootloader will flash it automatically.
-Duir- said:
Flashing recovery through fastboot requires unlocked bootloader, but with S-OFF you can make a zip file and bootloader will flash it automatically.
Click to expand...
Click to collapse
And now the question you have been waiting for: how do I do that?
And when I have the zip file, do I just put it on my internal sd and reboot into bootloader?
Smellie2 said:
And now the question you have been waiting for: how do I do that?
And when I have the zip file, do I just put it on my internal sd and reboot into bootloader?
Click to expand...
Click to collapse
I have a guide for that here.
-Duir- said:
I have a guide for that here.
Click to expand...
Click to collapse
I'm sorry for the stupid question, but how can I download the android.txt file? It doesn't download, it just opens. I thought of copying the tekst in it, but I have a vague recollection of a special way to save a txt file or it doesn't work. Or is that just in java?
EDIT: never mind, just tried and it worked!
Works great!
-Duir- said:
This requires S-OFF to use, follow at your own risk!
This will let you unlock your bootloader without htcdev and also let you change your hboot watermark from RELOCKED back to stock LOCKED.
Advantages:
No having your data partition wiped
The ability to get back to 100% stock without any visual trace of having unlocked your bootloader
Does not modify the hboot so works independently and can be used with any hboot version
Works whether you've updated to KitKat or not as the specific block is not remapped by the OTA.
Credits:
scotty1223: I've linked to his M7 thread a few times in our old Desire 601 thread, now that we have our own section I figured I'd post the information here so people could better find and take advantage of it.Requirements:
ADB installed on your computer
Drivers for your phone installed on your computer (HTC Sync Manager will do that for you).
Device must be S-OFF
Device must be rooted
First Things First:
Before you do anything it is highly recommended that you backup the section of your phone this guide will be modifying.
Open a command prompt in your adb folder
Type adb shell and press enter.
Type su and press enter if needed to a get a root shell.
Type/paste dd if="/dev/block/mmcblk0p3" of="/storage/ext_sd/mmcblk0p3.img" and press enter
Now it will be backed up to your external SDCARD and we can continue.
Unlock your Bootloader:
Open a command prompt in your adb folder and do the following:
Type adb shell and press enter
Type su and press enter if needed to get a root shell
Rather than type it is recommended you paste the following:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 and press enter
Type exit and press enter
Type exit and press enter if needed to return to a normal command prompt
Type adb reboot bootloader and press enter
Verify you are now UNLOCKED
Regain your LOCKED status:
Open a command prompt in your adb folder and do the following:
Type adb shell and press enter
Type su and press enter if needed to get a root shell
Rather than type it is recommended you paste the following:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 and press enter
Type adb reboot bootloader and press enter
Verify you are now LOCKED
Notes:
I have personally tested this on my ZARA_CL both before and after updating to KitKat.
Confirmed by other users to work for ZARA_UL as well.
[/
Click to expand...
Click to collapse
I have locked the bootloader by using
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796 command.
then I used
adb reboot bootloader comant to reboot.
When it's executes the HTC Desire601(zara ul) the screen got off but it will not getting turn on again and also will not be able to charge the mobile.
Team Win Recovery Project v3.0.0.0 for D605
{
"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"
}
HOW TO INSTALL:
Flash from old recovery:
Reboot to your current recovery.
And flash the archive.
Flash recovery.img without custom recovery:
Extract contents on your PC
Copy loki_flash and recovery.img to you phone's SD card via MTP connection
Download and start Android Terminal Emulator from Play Store
From terminal emulator type: $ su
Then type (assuming files from zip were copied to external SD card root) :
# cp /storage/external_SD/loki_flash /storage/external_SD/recovery.img /data/local/tmp
# cd /data/local/tmp
# chmod 777 loki_flash
# ./loki_flash recovery recovery.img
# reboot recovery
DOWNLOAD:
Link to flash from recovery:
https://mega.nz/#!fo8DCDbb!wvN9GTN7xzuTGnNMBfu4UwmAo7culclt88qb-qJoZLI
Link to flash without recovery:
https://mega.nz/#!y1dk0KwS!HAwU-Pi6jgfQPe3c1yID9WmX76X_afdNpTpToPbfqSA
STATUS:
Stable (but I have not tested)
Nice work, thx (will you end cm12?)
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Downgrade to jb
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Ag0n1a said:
@JackPOtaTo try with another version of windows, i had the same on win7, no problem in win8
Sent with my CM11 Lg D605
Click to expand...
Click to collapse
I have win 10. And i bricked (Hard) LG l9 II
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Ag0n1a said:
As far as I know this device is not possible to hardbrick.
Again, if your problem is "Loki aboot version does not match device" then your device is not bricked probably
Click to expand...
Click to collapse
I don't know where you guys get your information from but stop saying phones are not possible to hard brick and spread this word around. It is very easy to hardbrick any phone with root.
I will go just in a little bit of detail to show you.
How does your computer boot?
The hardware you have (CPU, GPU, Memory etc) are searched for (physical addresses) by the motherboard by the BIOS. Delete or erase the BIOS and I bet you any sum that your computer will stop doing anything (starts and sits idle just fans spinning).
With this analogy the BIOS of any mobile device is the bootloader. In the bootloader, that is located on the eMMC (embedded Multi Media Controller; like an SSD but with the controller of memory in the silicon die). eMMC is partitioned like a hard disk.
Your phone has an integrated Primary Loader in the CPU (this is what Qcom 9008 is). By shorting pins you change the boot order. If you short correct pins you can send data into memory (RAM) from the CPU and then write it on the eMMC (if you have the correct communication). This is where the HEX programmer comes in. This is how Qualcomm tools know how to communicate with the SOC.
The 2nd loader is on the eMMC. By default all CPU's boot from eMMC. SBL1->aboot and so on is the bootchain. Where hardware is initialized and recognized. Destroy and of those partitions and you will have a hardbrick (either fallback to 9008 automatically because eMMC is empty or not recognized at all).
Well I ended up giving you kind of a full information. Just stop trowing around this thing "phones can't be hardbricked". Hardbrick describes the state where a phone can't enter the last emergency mode provided by the manufacture (Emergency in this case). And generally buttons don't work, screen isn't either and so on.
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Ag0n1a said:
Never said that phones cannot be hardbricked....
I said that installing this rom will not hardbrick your phone, cuz only contain kernel and syspartition... plus, if the software prevents u from make changes because the aboot version doesn't match, how can u hardbrick it?
Thanks for the explanation though, learned couple of spec terms...
Click to expand...
Click to collapse
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
A
neutrondev said:
If you flash an aboot version that does fail the check of the bootchain you have a hardbrick.
Click to expand...
Click to collapse
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Ag0n1a said:
A
With this method you can not, the moment it says the aboot version is different it doesn't allow the copy of it. I had this error 5-6 times before I could successfully change the aboot and all those times in between my phone was always turning on as normal...
If then you are able to flash an aboot version that doesn't match then u r unlucky...
Anyway I'm for sure not as expert as you, but I'm just reporting my experience
Click to expand...
Click to collapse
Yeah you are right. That is just a message it will not flash it for you. But if you see that message and try to flash a lower aboot without flashing full KDZ you are in big trouble.
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
AWESOME1092387456 said:
Can someone "Loki-fy" or something on TWRP because i am in need to use cwm 6.0.5.1 by varcian
Click to expand...
Click to collapse
For me the installation works but don't install it... i've installed cm12 and it sayed secure booting failed
and backup/restore doesn't work, it corrupted /data partition but i resolved it.
Kaszke said:
Downgrade to jb
Click to expand...
Click to collapse
How? I couldn't find a working link for a stock jb.
Cristi73 said:
How? I couldn't find a working link for a stock jb.
Click to expand...
Click to collapse
http://lg-phone-firmware.com/index.php?id_mod=37
Find the kdz that coresponds to your region/carrier.
goooooooooD!!!! amazing job ))))
JackPOtaTo said:
I Have problem: Loki aboot version does not match device. (LG D605 kitkat 4.4.2) Root:yes
Click to expand...
Click to collapse
hey here is the solution body
II Flash
GOTO D605 RECOVRY (folder) hold shift and right click on the mouse then open window command here
then copy the commands on the cmd
you need to have adb driver installed and here the download link http://www.mediafire.com/download/u6pdpy77sonjyqh/D605+RECOVRY.rar
1 adb push aboot.img /data/local/tmp
2 adb shell
3 su
4 dd if=/data/local/tmp/aboot.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
4 exit
5 exit
6 adb push loki_flash /data/local/tmp
7 adb push recovery.img /data/local/tmp
8 adb shell
9 su
10 cd /data/local/tmp
11 chmod 777 loki_flash
12 ./loki_flash recovery recovery.img
13 reboot recovery
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
sedi21 said:
Hi all! I followed the procedure in terminal emulator from JB with root (through impactor)and I installed successfully twrp.
Then I installed CM11 by Varcain but the phone gives me the message "Secure booting Error! Cause: boot certification verify" .. I really can't figure out the problem after hours of search... can someone help me please?
Now I have to use kdz to reinstall JB?
EDIT: Sorry, The solution is easy, I must unlock the bootloader before flashing cm11... I forgot it! So the problem is not related to twrp
Click to expand...
Click to collapse
but how did you unlock it? because i don't know how to unlock mine and i don't think its possible