Well, just like the thread title says, i can't flash Sbl.bin neither from Odin nor Heimdall. With Odin it just hangs in Sbl.bin and Heimdall fails after a couple of minutes waiting. Trying to flash it with Heimdall in verbose mode gives an "Error -7". Can someone help me? I'm trying to flash the new bootloaders included with JVK to solve the problem with the screen.
My phone is a Galaxy S I9000T
Thanks in advance.
Same problem here, except that I'm able in theory to flash with Heimdall. However, the result is like I hadn't flashed bootloaders (screen corruption, loss of recovery mode), this only happens with rom XXJVK.
My I9000T (from Telhell) actually runs XWJS8 but with modem TDOJP1 for unknown reason as I don't mix components intentionally.
Try flashing JPU JV1 or any other firmware with the bootloaders and see if you are facing the same issue.
Sent from my GT-I9000 using XDA App
Have you tried flashing the 3 files from Samfirmware?
I tried with the 3 files posted here on XDA and they would never flash.
It just hung... I had to pull the phone because no progress happening. Got the Phone to PC error screen. Luckily was able to force it into download mode again with the three button sequence. Took over a minute of holding the combo to get it there.
So yeah... Just try the 3 sbl files from Samfirmware and they should flash without a hitch.
Flashing bootloaders on their own is a bad idea. Just reflash the whole package.
Hello again,
I can't reflash the whole package because it hangs every time it tries to write the Sbl.bin file. I'm trying to flash the bootloaders because, somehow, i managed to flash the JVK ROM and i have issues with my screen and i can't enter in recovery mode.
I already tried with all of the heimdall bootloaders in Perka's File Stash, but i get the same result. Verbose mode in Heimdall when i try (and fail) to flash Sbl.bin says this:
Uploading secondary bootloader
0%File Part #0... Response: 0 0 0 0 0 0 0 0
File Part #1... Response: 0 0 0 0 1 0 0 0
File Part #2... Response: 0 0 0 0 2 0 0 0
File Part #3... Response: 0 0 0 0 3 0 0 0
File Part #4... Response: 0 0 0 0 4 0 0 0
File Part #5... Response: 0 0 0 0 5 0 0 0
File Part #6... Response: 0 0 0 0 6 0 0 0
File Part #7... Response: 0 0 0 0 7 0 0 0
File Part #8... Response: 0 0 0 0 8 0 0 0
File Part #9... Response: 0 0 0 0 9 0 0 0
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet.
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
Re-attaching kernel driver...
Any idea?
froysm said:
Hello again,
I can't reflash the whole package because it hangs every time it tries to write the Sbl.bin file. I'm trying to flash the bootloaders because, somehow, i managed to flash the JVK ROM and i have issues with my screen and i can't enter in recovery mode.
I already tried with all of the heimdall bootloaders in Perka's File Stash, but i get the same result. Verbose mode in Heimdall when i try (and fail) to flash Sbl.bin says this:
Uploading secondary bootloader
0%File Part #0... Response: 0 0 0 0 0 0 0 0
File Part #1... Response: 0 0 0 0 1 0 0 0
File Part #2... Response: 0 0 0 0 2 0 0 0
File Part #3... Response: 0 0 0 0 3 0 0 0
File Part #4... Response: 0 0 0 0 4 0 0 0
File Part #5... Response: 0 0 0 0 5 0 0 0
File Part #6... Response: 0 0 0 0 6 0 0 0
File Part #7... Response: 0 0 0 0 7 0 0 0
File Part #8... Response: 0 0 0 0 8 0 0 0
File Part #9... Response: 0 0 0 0 9 0 0 0
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet. Retrying
Error -7 whilst receiving packet.
Failed to confirm end of file transfer sequence!
Secondary bootloader upload failed!
Re-attaching kernel driver...
Any idea?
Click to expand...
Click to collapse
Try flashing the complete package, Use Odion 1.7 or 1.8 this will fix the issue
lvvine said:
Try flashing the complete package, Use Odion 1.7 or 1.8 this will fix the issue
Click to expand...
Click to collapse
Nope, i tried with Odin 1.7 and Odin 1.8 and it was the same, it just can't pass from Sbl.bin, any other idea?
froysm said:
Nope, i tried with Odin 1.7 and Odin 1.8 and it was the same, it just can't pass from Sbl.bin, any other idea?
Click to expand...
Click to collapse
Get the bootloaders from my files and flash with heimdall.
Link in my sig.
Perka said:
Get the bootloaders from my files and flash with heimdall.
Link in my sig.
Click to expand...
Click to collapse
I already tried with the 5 Heimdall Bootloaders in your File Stash, but nothing changes.
Are you by any chance trying to flash bootloaders from I9000 International on I9000T?
[Ramad] said:
Are you by any chance trying to flash bootloaders from I9000 International on I9000T?
Click to expand...
Click to collapse
Try the 2.1 single file package meant for your region. You can download it from samfirmware I think.
[Ramad] said:
Are you by any chance trying to flash bootloaders from I9000 International on I9000T?
Click to expand...
Click to collapse
Yes, that is exactly what i am trying to do, the first bootloader passes, but the secondary not. Should i wait for a Gingerbread ROM for my model of Galaxy S?
Lol ... No words ...
froysm said:
Yes, that is exactly what i am trying to do, the first bootloader passes, but the secondary not. Should i wait for a Gingerbread ROM for my model of Galaxy S?
Click to expand...
Click to collapse
Yeah I know exactly what your're talking about. I recommend flasing always with Heimdall, try again flashing bootloaders but before make sure U first put the phone in USB Debugging mode before enter in Download mode. Hope this helps.
froysm said:
Yes, that is exactly what i am trying to do, the first bootloader passes, but the secondary not. Should i wait for a Gingerbread ROM for my model of Galaxy S?
Click to expand...
Click to collapse
Please don't do it, there is a reason that your device refuses to be flashed with the Sbl.bin from the International I9000, don't you agree?
[Ramad] said:
Please don't do it, there is a reason that your device refuses to be flashed with the Sbl.bin from the International I9000, don't you agree?
Click to expand...
Click to collapse
Well, since pretty much everything available for the i9000 also works for the i9000T i thought it would work, i mean, the only the only thing that everyone says is different (In the forums, obviuosly) is that the i9000T uses the 850 band, but i must be wrong. Also, i don't see other i9000T users complaining about bootloaders... maybe they haven't tried... Thanks anyway, i'll stick with FroYo ROMs for the moment.
Froysm, I'm with Telcel as well and I'm experiencing the same!
I flashed it successfully with JPY ROM...
When I tried to update to JS5 ROM, Odin hung at sbl.bin...
And then began my nightmare... It is soft bricked. I can get to Recovery and Download, but the phone is not working beyond that.
I tried to flash back to JPY, and it is booting, but it fails to present the "login screen"... and it keeps vibrating from time to time (every 20 seconds or so)
Someone told me that JPU is the way to go in this cases, but it hangs at sbl.bin as well.
I've read that JM8 (eclair 2.1) should fix this problem, but I've also read that it may hardbrick the phone... so, I'm in a researching stage right now...
Did you soft bick your phone with the sbl.bin issue?
How did you get it back?
I'm kinda savvy in technical stuff, but I'm a newcomer to android, so I'm kinda lost. I don't know if you can help me...
I'm thinking of getting my phone back to telcel and ask for a replacement, but that wouldn't help in my learning. I want to seize this issue to get to know android, but I need someone to lead me or someone that can show me the way... lots of information, and I don't know where to start.
Cheers!
My exact problem is described in the following thread>
http://forum.xda-developers.com/showthread.php?p=12630868#post12630868
Thanks for any help!
Oh, damn Telcel! I'm with Telcel too and I'll be happy to help you.
Sent from my GT-I9000 using Tapatalk
Related
Hi,
I am trying to temp root my device (2.50.405.2) so that I can backup all my app data before I root my device. However I am getting problems. I am using the fre3vo software, and what I get is the following error message.
adb server is out of date. killing...
* daemon started successfully *
612 KB/s (0 bytes in 9796.000s)
15 KB/s (0 bytes in 15837.001s)
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 106
width: 62
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Potential exploit area found at address fbb6c1ff:e01.
Payload verification failed.
Click to expand...
Click to collapse
Anyone seen this before? I heard a factory reset will solve this but I don't want to do this until I have all my app data backed up. I don't want to lose it before i root. Any ideas?
Hi, thought I bump this up to see if anyone would be able to help.
from the Fre3vo thread
#teamwin is proud to announce the Fre3vo tool for the HTC EVO 3D and Sensation!
Click to expand...
Click to collapse
So it would seem to me your problem is that you have neither a EVO 3D or a Sensation, simples!
Nope, it has been used before on other DHD.
http://forum.xda-developers.com/showthread.php?t=905003
My bad, the fre3vo threads are out of date it seems, digging around it suggests that a simple reboot and trying again seems to work, I am assuming it didn't in your case?
done that and it didn't work
I was told over at androidforums to reset the phone, but if I do that I lose my app data. Need to back it up before I root.
springy said:
done that and it didn't work
I was told over at androidforums to reset the phone, but if I do that I lose my app data. Need to back it up before I root.
Click to expand...
Click to collapse
My backup app doesn't require root like titanium backup, you can use it prior to root. once rooted restore and switch to titanium.
naailalzuhir said:
My backup app doesn't require root like titanium backup, you can use it prior to root. once rooted restore and switch to titanium.
Click to expand...
Click to collapse
Again, it doesn't back up the application data. Only the .apk. You need root to do this.
[only mcc models
First flash ota 20110524 to return at original cwm and do wipe data and wipe partion cache
This will make clean instalation
unrar archivehttp://www.mediafire.com/?adu3kmqhxkb8hfi
run nv flash
go recovery
format system
wipe dalvik cache
mount usb
copy update
copy gapps
copy kernel
flash them with same way
done
lcd density at 120
Stable with pershoot tweaks preload
Major bug have been fixed
Sound improved with beats audio
external sdcard fixed
Sleep fixed
Hd video and mkv video format playable with external. Player like mx video
System improved with init.d tweks
new theme ics
camera work with skype
bravia engine drivers added
set 775 permission system/etc/be photo
set 775 permission system/etc/be movie
Kill app via long press choice will help you
To my daughter Jan
malata t8 unofficial cyanogenmod 7.2.0 RC nvflash mode for mcc device
congratulation goes whyberg for that wonderfull work
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Use at your own risk its not my responsibility if brick your device
download firmware
http://www.mediafire.com/?p66bpjp1qeug6vs
download latest gapps
http://www.mediafire.com/?zglnipcv34kdt49
Click to expand...
Click to collapse
unpacks the archive
includes device "-" + "power" (APX mode)
running the batch file download [1GB | 512MB]
after the device goes into overdrive long press power off
includes device "+" + "power" (recovery mode)
now you must input and export usb cable in & out with usb mount from recovery mode until computer regognize your tablet as storage
copy the update zip and gapps zip into
pour through recovery archive with firmware update-cm-7.2.0-RC0-smb_a9701-KANG-signed.zip & and latest gapps on SDCARD
set after "install from SDcard" both before reboot
Click to expand...
Click to collapse
libcamera.so.ziphttp://forum.xda-developers.com/attachment.php?attachmentid=896892&d=1328950465
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Manual
With root explorer paste libcamera.so into
System/lib and give read write permission as the other
Before reboot
Via recovery(libcamera.so-update.zip)http://forum.xda-developers.com/attachment.php?attachmentid=896903&d=1328951238
Skype 2.6.0.95 version worked!!!
Gtalk video not! but in`s not a camera problem...
Click to expand...
Click to collapse
not working
video accelerator
as all gtablet must install externall video code
like
mxvideo apk
Click to expand...
Click to collapse
Best flash player with this rom is 10.3
Working you tube like a charm
New google play without errors
http://i.minus.com/1331477283/iiYu2AW7DQxVWHgoI7qIbA/dJCxyuh2eNq0W.apk
Click to expand...
Click to collapse
you must be carefull
do not partion sd
do not fix permission
it may brick
enjoy
Click to expand...
Click to collapse
confirmed working!!!!!!!
Thanks geowolf........ youre the man
I'd go as far as to say.... Best Malata zpad t8 rom I've found and was easy to install (as per instructions above you need to install zip files BEFORE first boot)
Shame about no camera. Does anyone know of a fix?
I'm off to 4pda. ru to check for updates
camera fix found
hXXp://cyanogenmod.googlecode.com/issues/attachment?aid=44480005000&name=CM07CameraFix.zip&token=HIEuD7abnRfewkHvEaa8YkZSjZg%3A1328138144361
just copy .so files over /system/lib using root explorer and set permissions same as other files
reboot
install included camera.apk if needed
Happy days
Anything for us poor mcb owners?
Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks
cociuba said:
Hello,
I have an evolio neura tablet, which I understand is the romanian version of malata zpad t8, how do I know which serial I have, because as for as I understand there are two types of models MCB and MCC.
-also because I am new to the android family can someone explain step by step how to upgrade the rom?
Thanks
Click to expand...
Click to collapse
Hello
There three models mca. Which doesn't use interval memory and was the easy way to upgrade any ron
Mcb its little confuse what type of nand type are use in previous update of official firmware was problem to install mcc nand type sound errors and. Not compatible firmsware
Only if know what type of you use proceed to this
and mcc with interval memory the things are very dangerous .this nvflash regognize your interval memory as SD card and sdcatd turns as emcc folder
Ihave test it to emmc models.
Under the tap of sim card has the type of memory that you use
Open the tap. And has a specification note with numbers
Something like that ( emmc34567886)
i cant find the serial under the gsm tap, is there another posibility of finding it?
cociuba said:
i cant find the serial under the gsm tap, is there another posibility of finding it?
Click to expand...
Click to collapse
At settings
About option
Give a report
Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!
this is the result from using one of the updates for the tablet, it seems that the update uses the emmc.bat
c:\neura\neura [email protected]>download_EMMC_1G.bat
c:\neura\neura [email protected]>"nvflash.exe" --bct Malata_a02_12Mhz_H5PS1G83EFR-S6C_ 333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct --setbct --bl bootloader.bin --configfile android_fastboot_emmc_full_more.cfg --odmdata 0x3c0c0011 --create --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171411c040a08297
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file:Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct - 4080/4080 bytes sent
Malata_a02_12Mhz_H5PS1G83EFR-S6C_333Mhz_1GB_emmc_THGBM1G6D4EBAI4_x8.bct sent successfully
odm data: 0x3c0c0011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
945472/945472 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
Click to expand...
Click to collapse
EE
bungadudu said:
Hi geowolf,
Many thanks for what you're doing.
I also have an evolio neura - malata zpad t8 rebranded.
In the "about tablet" option I only have:
Model number - Evopad
Android version - 2.2
Baseband version - R2A11
Kernel version - 2.6.32.0-00252-gf1df521-dirty [email protected] #5
Build number - 20110712_EW
Hope it helps.
Also do you think that we could get ics on this?
Thank you!
Click to expand...
Click to collapse
One more
Is rooted ?
If open root directory with root explorer is any directory like emmc. emmb ....
China Malata 3g models are mmc
But Russian 3q models has been moderate with erricson 3g spare even are, or not 3g
Maybe and the Romanian models has been modified
With 3g
Try with root explorer to find mount points
And from market android system info has an option to find mount points
Check it out .
Its to early for ice cream
cant find the mount points but I attached diskstat and partition file
diskstat
7 0 loop0 0 0 0 0 0 0 0 0 0 0 0
7 1 loop1 0 0 0 0 0 0 0 0 0 0 0
7 2 loop2 0 0 0 0 0 0 0 0 0 0 0
7 3 loop3 0 0 0 0 0 0 0 0 0 0 0
7 4 loop4 0 0 0 0 0 0 0 0 0 0 0
7 5 loop5 0 0 0 0 0 0 0 0 0 0 0
7 6 loop6 0 0 0 0 0 0 0 0 0 0 0
7 7 loop7 0 0 0 0 0 0 0 0 0 0 0
179 48 mmcblk3 17433 44474 1532199 120670 136737 577806 3635982 18924640 0 1974930 19139480
179 49 mmcblk3p1 4495 282 286484 26080 3 0 6 20 0 15010 26080
179 50 mmcblk3p2 12 61 290 10 133 6864 27988 57350 0 11350 57360
179 51 mmcblk3p3 9 61 278 20 8 1 36 550 0 550 570
179 52 mmcblk3p4 0 0 0 0 0 0 0 0 0 0 0
179 53 mmcblk3p5 0 0 0 0 0 0 0 0 0 0 0
179 54 mmcblk3p6 9475 27970 846506 75240 115761 534552 2610508 14212670 0 1796540 14288720
179 55 mmcblk3p7 5 0 10 10 0 0 0 0 0 10 10
179 56 mmcblk3p8 3432 16100 398591 19310 20832 36389 997444 4654050 0 276190 4766740
254 0 dm-0 40 0 1066 340 0 0 0 0 0 130 340
254 1 dm-1 805 0 74867 14710 0 0 0 0 0 7710 14710
254 2 dm-2 34 0 478 30 0 0 0 0 0 30 30
254 3 dm-3 406 0 37090 4450 0 0 0 0 0 2180 4450
254 4 dm-4 80 0 6210 1040 0 0 0 0 0 330 1040
254 5 dm-5 118 0 6850 3190 0 0 0 0 0 810 3190
254 6 dm-6 635 0 47366 5750 0 0 0 0 0 2640 5750
Click to expand...
Click to collapse
partition
major minor #blocks name
7 0 2111 loop0
7 1 48888 loop1
7 2 2111 loop2
7 3 30177 loop3
7 4 4190 loop4
7 5 7308 loop5
7 6 24980 loop6
179 48 15648768 mmcblk3
179 49 327680 mmcblk3p1
179 50 65536 mmcblk3p2
179 51 32768 mmcblk3p3
179 52 1 mmcblk3p4
179 53 32768 mmcblk3p5
179 54 2097152 mmcblk3p6
179 55 8192 mmcblk3p7
179 56 13081600 mmcblk3p8
254 0 2110 dm-0
254 1 48888 dm-1
254 2 2110 dm-2
254 3 30177 dm-3
254 4 4189 dm-4
254 5 7308 dm-5
254 6 24979 dm-6
Click to expand...
Click to collapse
cociuba said:
cant find the mount points but I attached diskstat and partition file
diskstat
partition
Click to expand...
Click to collapse
The most important is that previous update you use was emmc
ok, so I can use your build?
if yes please explain one more time the steps, thanks.
also is it possible to use clockworkmod? or how can i make a backup of the rom that I am using
Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english
@whyberg -does gsm work?
cociuba said:
@whyberg -does gsm work?
Click to expand...
Click to collapse
voice? i don't know, F3607gw can't support voice calls
gprs/edge/umts data worked well
whyberg said:
Hello All!
I build this rom from Cyanogen source +
1. kernel from Pershoot(MegaMonstr
2. MDM modems patch (my malata wifi version + F3607GW module with GPS)
3. Camera patch for Skype form toshiba ac100
4. /dev/hands
There are additional wishes?
Sorry for my english
Click to expand...
Click to collapse
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...
I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?
geowolf1000 said:
thanks for all
great job
the post belong to you from now
it would greatfull if post your libcamera .so for working skype
thanks we wait for this long time
i hope for the next...
Click to expand...
Click to collapse
View attachment libcamera.so.zip
Installetion via ADB
1. unzip libcamera.so.zip
2. adb remount
3. adb push libcamera.so /system/lib/libcamera.so
Via recovery(View attachment libcamera.so-update.zip)
Skype from market last version worked!!!
Gtalk video not! but in`s not a camera problem...
cociuba said:
I will soon test your rom, but I would like to know if something goes wrong can I revert to the stock rom, and how?
thanks for your work.
ps: is it possible to install the rom from a linux machine (ubuntu)?
Click to expand...
Click to collapse
Download stock rom from hardware developer website and reinstall it
What device you have?
My working computer under debian
hy cracks
I have a car radio with windows ce - manufacturer lg.
I would like to customize the firmware upgrade (change images....).
somebody has an idea how I can unpack the upgrade.LGU file and pack again later?
can´t find tools for this
thank you for your help
voila !
nordic09 said:
hy cracks
I have a car radio with windows ce - manufacturer lg.
I would like to customize the firmware upgrade (change images....).
somebody has an idea how I can unpack the upgrade.LGU file and pack again later?
can´t find tools for this
thank you for your help
Click to expand...
Click to collapse
here you go - download attachment
it's a tool to convert lgu files to directory and vice versa
to be used in command line this way:
lgu2dir <path to lgu file> <path to folder where where the contents will be unpacked>
ex: lgu2dir upgrade.lgu root
lost_things said:
here you go - download attachment
it's a tool to convert lgu files to directory and vice versa
to be used in command line this way:
lgu2dir <path to lgu file> <path to folder where where the contents will be unpacked>
ex: lgu2dir upgrade.lgu root
Click to expand...
Click to collapse
thank you - you are my hero
the tool works great
you know a way to convert the files back to a lgu-file too?
nordic09 said:
thank you - you are my hero
the tool works great
you know a way to convert the files back to a lgu-file too?
Click to expand...
Click to collapse
yes, see the attachment
Usage: dir2lgu <content name> <in folder> <out lgu file>
thank you again lost_things
lost_things said:
yes, see the attachment
Usage: dir2lgu <content name> <in folder> <out lgu file>
Click to expand...
Click to collapse
Unfortunately dir2lgu does not work on windows xp.
Can you make a version that also works on my old operating system.
Thank you.
need working windows version this one is not win32 valid application or i miss something
thanks
changing only one file within the LGU without extracting anything is possible?
Hello guys, first thanks for the help with the file compression and decompression of the LGU, but I have a problem when compressing the file again made a change in one of the firmware files and recompile the file is not accepted as update my device I believe it has something to do dir2lgu different from the original build program which makes it invalid on the device, so I wonder if there is any header possibilidede the only LGU that change a file without extract, because I need to unlock a device and only need need to change an exe within the LGU, is this possible? who developed these programs that kind of compression they use? I'm 3 months in search of a solution and nothing would be grateful for an answer that will help many people.
need a new lgu2dir for a newer version of .lgu files
Hello guys,
seems like lg made a new version of the car radio with windows ce, and the new .lgu files can not be opened by the old tools.
Thanks.
Same here, new version of lgu, cannot be opened, file signature (or magic number if u prefer) is now ULC2.
And the archive in the lgu container is no more RAR but a Zip tipe, as usual seen inside the file with the hex editor, i tried to cut out the archive but archive won't work i suspect that's somenthing like a byte shift or other kind of "protection".
I have spotted that at address from block 18 to 1B is stored that crc in reverse way.
But i'm not found the way to recover the internal archive.
@lost_things Did you have a new version? (If u are still around here, seems that these posts are the only 2 that you are ever made )
Thank you in advice.
@viberfm
Are you working with new medianav evolution firmware too?
New lgu tools available
Warm thanks ! You made a really great job djeman !!
Works perfectly both for 'old' and 'new' files. Be careful to position appropriate 'content-name' and 'label' when recompressing, your car application may need it to work appropriately.
Hi,
@djeman the new dir2lgu.exe, don't get any options, if you try to pass -l o -u, don't care it create always an lgu0 type, and -n and -p don't work at all, i hope u can fix it.
Thank you for you work anyway
sala_test said:
Hi,
@djeman the new dir2lgu.exe, don't get any options, if you try to pass -l o -u, don't care it create always an lgu0 type, and -n and -p don't work at all, i hope u can fix it.
Thank you for you work anyway
Click to expand...
Click to collapse
+1 same here.
Sorry but all works fine
I'm trying right now in win 7 and win 10, with -u option it crate a lgu0 file, with -n something, it show me the help like I have put something wrong, lgu2dir instead works fine.
@djeman
Tested now:
-u ulc2 format not work as you can see here
Code:
E:\testxda>dir2lgu.exe -u test test.lgu
creating C:\Temp\TFRC451.tmp
file test.txt crc 0
file C:\Temp\TFRC451.tmp crc 8bb6d8f8
E:\testxda>dir
Il volume nell'unità E è Volume
Numero di serie del volume: 7807-6F2B
Directory di E:\testxda
19/05/2016 16:37 <DIR> .
19/05/2016 16:37 <DIR> ..
19/05/2016 16:36 123.392 dir2lgu.exe
19/05/2016 16:36 96.256 lgu2dir.exe
19/05/2016 16:36 <DIR> test
19/05/2016 16:37 1.152 test.lgu
E:\testxda>type test.lgu
LGU0 Ç °ÏÂï 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■- u ■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■■ d▀4DÐ%■ñ╠$‗<í×êÑÆRFyµ+UÊÜØrj½‗┬_8█wÌPG5c%\▄os0╦Ë·ZÉeÍ░:Llü└ │¤=W Rar!»è╝Ý╝ìyRíù┴2NáÑ[¹z`L"µ█"NzDO┐ª┤ï\÷iå^¹Ï2e
and with -n don't do nothing like you can see here:
Code:
E:\testxda>dir2lgu.exe -n comment test test.lgu
Usage: dir2lgu [options] <content name> <in folder> <out lgu file>
-n <name> name label (" " by default)
-l lgu0 format (default)
-u ulc2 format
-p <m1|m2> preset medianav 1 or 2
Arf ... I forget to protect the execution when one argument is missing ^^
Usage: dir2lgu [options] <content name> <in folder> <out lgu file>
-n <name> name label (" " by default)
-l lgu0 format (default)
-u ulc2 format
-p <m1|m2> preset medianav 1 or 2
Click to expand...
Click to collapse
In "dir2lgu.exe -u test test.lgu":
[options] = -u
<content name> = test
<in folder> = test.lgu
<out lgu file> =
And for "dir2lgu.exe -n comment test test.lgu" you have make the same mistake, one argument is missing
djeman said:
Arf ... I forget to protect the execution when one argument is missing ^^
In "dir2lgu.exe -u test test.lgu":
[options] = -u
<content name> = test
<in folder> = test.lgu
<out lgu file> =
And for "dir2lgu.exe -n comment test test.lgu" you have make the same mistake, one argument is missing
Click to expand...
Click to collapse
Oh crap, I have confused the -n option with the <content name>, so to put the content name name i use -n :silly: Ok i made a big mistake, but i'm happy that i'm not the only one, seems that @sala_test had done the same mistake
Ok, so, to avoid other mistakes, what is the -n option "label"? And what is the difference to use -l and -u instead of -p m1 or m2?
Anyway i'm a dumbass , thank you for your work
'dir2lgu -p m1 <content name> <in folder> <out lgu file>' is equal to 'dir2lgu -l -n "*MEDIA-NAV*" <content name> <in folder> <out lgu file>'.
'dir2lgu -p m2 <content name> <in folder> <out lgu file>' is equal to 'dir2lgu -u -n "*MEDIA-NAV2*" <content name> <in folder> <out lgu file>'.
Do not use -p option with an another, it's just for rapid preset.
"content name" is the name of the content of your update, the name shows on the device in the update dialog.
"name label" ... it's a device label, this label is used by the update software, it's a protection to not flash a bad update. All devices do not use it.
Ok @djeman thanks for explaination, thank you
Inviato dal mio Asus Zenfone 2
I tried TowelRoot from this thread but with no success.
http://forum.xda-developers.com/showthread.php?t=2784900
My Setup:
Ubuntu 14.04 x64
i only changed the unzip command in the script to use my local installed unzip.
Code:
==============================================
= =
= Easy Root Tool v12 =
= Supports various Xperia devices =
= created by zxz0O0 =
= =
= http://forum.xda-developers.com/ =
= showthread.php?p=53448680 =
= =
= Many thanks to: =
= - [NUT] =
= - geohot =
= - MohammadAG =
= - cubeundcube =
= - nhnt11 =
= - xsacha =
= =
==============================================
=============================================
Extracting libexploit.so
=============================================
OK!
It looks like you are running Linux
Please make sure ia32-libs is installed if you get any errors
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
Make sure that you authorize the connection
if you get any message on the phone
=============================================
Device found!
=============================================
Getting device variables
=============================================
Device model is SGP621
Firmware is 23.0.1.A.0.167
=============================================
Sending files
=============================================
36 KB/s (1593 bytes in 0.042s)
37 KB/s (1575 bytes in 0.040s)
204 KB/s (9496 bytes in 0.045s)
307 KB/s (13672 bytes in 0.043s)
4802 KB/s (657704 bytes in 0.133s)
Copying kernel module...
851 KB/s (34473 bytes in 0.039s)
19 KB/s (823 bytes in 0.041s)
305 KB/s (13592 bytes in 0.043s)
Kernel version is 3.4.0-perf-gd4d661a
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
19 bytes transferred in 0.001 secs (19000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: patched to 0xFF791C4F
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Loading geohot's towelroot (modified by zxz0O0)
=============================================
301 KB/s (13592 bytes in 0.043s)
4479 KB/s (197320 bytes in 0.043s)
=============================================
Waiting for towelroot to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
Here it stays forever (30min.)
Any ideas?
werty1st said:
I tried TowelRoot from this thread but with no success.
...
Here it stays forever (30min.)
Any ideas?
Click to expand...
Click to collapse
As far as I know, Sony patched the vulnerability used in towelroot a few kernel versions ago. The functions are (partly) still there, but not exploitable anymore. I guess someone needs to find another vulnerability for us to be able to root the device. (Bootloader unlock is not possible as of now as the device is not listed on the Sony Unlocker site)
lowtraxx said:
(Bootloader unlock is not possible as of now as the device is not listed on the Sony Unlocker site)
Click to expand...
Click to collapse
i hope this will be added. from the moment i'm able to backup the DRM keys i will unlock the device.
I ordered the 16G version without LTE here in Germany - should arrive today - i REALLY hope that root will be possible anytime soon, so I can use the app "FolderMount" again to link app-storage to the external sd-card
fattymcdirty said:
I ordered the 16G version without LTE here in Germany - should arrive today - i REALLY hope that root will be possible anytime soon, so I can use the app "FolderMount" again to link app-storage to the external sd-card
Click to expand...
Click to collapse
Lollipop is supposed to unscrewup the Sdcard storage that Kitkat had.
xperia Z3TC
I ordered mine today. I ordered the SGP-621 4G/LTE version to replace my xperia z ultra. I can only hope it will work with T-Mobile USA to use the phone feature with and without Bluetooth. lets hope that you guys get this baby rooted..? :highfive:
jaime4272 said:
I ordered mine today. I ordered the SGP-621 4G/LTE version to replace my xperia z ultra. I can only hope it will work with T-Mobile USA to use the phone feature with and without Bluetooth. lets hope that you guys get this baby rooted..? :highfive:
Click to expand...
Click to collapse
I'm using an SGP-621 on AT&T prepaid. It works as a phone with and without Bluetooth. Without Bluetooth, the tablet uses speakerphone.
-jd
I wonder why the z3ct is not in the official bootloader unlock list on the Sony website? Does it usually take a while? The z3 is on the list already.
jaime4272 said:
I ordered mine today. I ordered the SGP-621 4G/LTE version to replace my xperia z ultra. I can only hope it will work with T-Mobile USA to use the phone feature with and without Bluetooth. lets hope that you guys get this baby rooted..? :highfive:
Click to expand...
Click to collapse
Where did u find the lte version for sale in the US? Thanks.
Deltadroid said:
I wonder why the z3ct is not in the official bootloader unlock list on the Sony website? Does it usually take a while? The z3 is on the list already.
Click to expand...
Click to collapse
Yes it is really frustrating. What's the point of having the kernel sources if we are not able to flash the kernel?
Who should I contact at Sony to express my opinion?
I wonder if Sony is going to do something about the problem with permanently losing the drm keys when unlocking the bootloader so we are unable to fully restore to stock.
For this reason, the resale value of an unlocked device will be much less and it scares away development.
xperia z3 tablet compact
bigcletus said:
Where did u find the lte version for sale in the US? Thanks.
Click to expand...
Click to collapse
I ordered mine from eXpansys USA and it's on it's way. I should get it by Wednesday 12
Purchased 16GB wifi only version in Hong Kong and is using for few days. Waiting for root.
I hope this gets rooted soon because i received mine today with 4G LTE SGP621 in the UK and am waiting to use my rooted apps, also tried towelroot, no luck
eman2001 said:
I hope this gets rooted soon because i received mine today with 4G LTE SGP621 in the UK and am waiting to use my rooted apps, also tried towelroot, no luck
Click to expand...
Click to collapse
Has anyone tried changing the strings in towelroot? Tap the towelroot icon three times and change it to 1337 0 1 0 4 0 or 1337 0 1 0 5 0 or 1337 0 1 0 6 0 and so on.
How long should i wait at each try?
the tab doesn't reboot. the app seems to freeze.
i tried :
1337 0 1 0 1 0 (app hang)
1337 0 1 0 4 0 -> phone not supported
1337 0 1 0 5 0 (app hang)
1337 0 1 0 6 0 (app hang)
1337 0 1 0 7 0 (app hang)
1337 0 1 0 8 0 -> phone not supported
1337 0 1 0 9 0 -> phone not supported
1337 0 1 0 10 0 -> phone not supported
1337 0 1 0 11 0 -> phone not supported
1337 0 1 0 4 1 -> phone not supported
1337 0 1 7380 4 0 (app hang)
Click to expand...
Click to collapse
very sad
werty1st said:
How long should i wait at each try?
the tab doesn't reboot. the app seems to freeze.
i tried :
very sad
Click to expand...
Click to collapse
I got the idea from this post for Z Ultra GPe and thought it may be worth a shot. I haven't used this method as I have a standard ZU, sorry for not being able to give more advice.
http://forum.xda-developers.com/showpost.php?p=52438607&postcount=1
Just managed to unlock my boot loader, next step rooting my tablet, i will find a way somehow fingers crossed :good:
How did you do that?
the device is not listed at http://developer.sonymobile.com/unlockbootloader/unlock-yourboot-loader/
I'm praying for you my man. And hoping that it becomes reality. We need that root A..S..A..Please
I've recently picked up this phone (A2017U), and following the guide from DrakenFX (don't think I can post links yet), the phone was bootloader unlocked and rooted on B20. I then decided to update it to B29 using an additional guide.
Ok, I'm pretty sure I did something stupid here, as I opted to wipe system during the above steps, and there was an error (E: failed to mount..., I think it was). I then flashed SuperSU from TWRP as noted in the above post, but after rebooting, I lost root, and I'm back to the stock recovery. Now, my PC can see the phone fine in regular mode with ADB, but as soon as I do 'adb reboot edl' or 'adb reboot bootloader', I get USB error 43 (device descriptor request failed). I have two integrated USB 3.0 ports on this PC and have tried both, and I've also tried this on another PC (Surface Pro 4) multiple times and with two different cables, with the same result. Both are Windows 10 post anniversary update. I've also reinstalled and tried it pre-anniversary update. I've tried using the Google ADB drivers (version 9.00) to no avail. I can manually add 'Android Bootloader Interface' when error 43 happens, but it gives me error 10 and no amount of uninstalling/reinstalling does the trick. I've also tried FTM, which gives me ADB access and a COM port, but it's right back to error 43 with 'adb reboot edl/adb reboot bootloader'.
Am I missing something, or am I stuck? Is there no way to get it recognized in fastboot mode so I can flash TWRP again?
Check in drakenfx thread on the b29 update, I think i saw note about it in OP
Have you tried going back to b20 using the zte factory firmware image?
When you get to a point you can't recover from, go back to square one and start over.
Since you said you unlocked your bootloader, what happens when you reboot your device? Do you get a weirdly formatted black screen for a few seconds that says something along the lines of "Warning - your device is unlockrr", before booting into the OS? If so, press VolUp or VolDown during that screen, it'll give you booting options. Select Fastboot and it'll reboot into bootloader.
All: thanks for the tips so far. I did manage to go back to B20 stock using ZTE's factory update.zip. Unfortunately, that's as far as I can seem to get. The bootloader is still unlocked (as it indicates when I do 'adb reboot bootloader') but since going back to B20 I no longer get the startup message that tells you so (device can't be trusted). OEM unlocking is still set to 'on' in developer options. I've done the 'update driver software' trick on the USB 3 host controllers but that didn't work. I've also pulled the battery from my motherboard and left it off for a few minutes. That didn't help either, as I still get error 43 when entering fastboot mode. I have a backup of fbop.img prior to unlocking, and a full TWRP backup from B20, but since I don't have root or fastboot I can't flash anything.
Hi all,
Unfortunately, I still can't get any pc to recognize my phone in fastboot mode via any of the above suggestions. I tried this thread titled: "[RESOLVED] fastboot not recognizing phone in bootloader mode" (I can't post links yet), but it didn't work. Neither Kingroot or Kingoroot work either (although some requests have been made in Kingroot). Am I stuck? I don't know of any other way to get my pc or my Surface Pro 4 to recognize the phone in fastboot mode or even to get root.
Knight1314 said:
Hi all,
Unfortunately, I still can't get any pc to recognize my phone in fastboot mode via any of the above suggestions. I tried this thread titled: "[RESOLVED] fastboot not recognizing phone in bootloader mode" (I can't post links yet), but it didn't work. Neither Kingroot or Kingoroot work either (although some requests have been made in Kingroot). Am I stuck? I don't know of any other way to get my pc or my Surface Pro 4 to recognize the phone in fastboot mode or even to get root.
Click to expand...
Click to collapse
You need to revert back to the old drivers in device manager,
When you boot to fastboot the device install the newest drivers and those drivers are a NO GO,
Boot to fastboot and look in Windows device manager , you'll see Android something forgot the name and go to update drivers and manually revert / install driver from 2014, I'm not at home at the moment so can't tell you exactly how.
As soon I get home I'll update this post.
EDIT : CHECK IMAGE about HOW TO Revert to Old drivers.
NOTE : YOU MUST BE IN BOOTLOADER / FASTBOOT MODE.
<snip>
NOTE : YOU MUST BE IN BOOTLOADER / FASTBOOT MODE.[/QUOTE]
Hi DrakenFX,
Thank you for the response. I did try the above, but unfortunately, it didn't work. I tried this on my Surface Pro 4, and when I enter fastboot mode, I get error 43 (device descriptor request failed). I can manually install the drivers from 2014, but if I do, I get error 10. I can uninstall the drivers and reinstall them, but to no avail. I tried this on my PC also, and I don't get error 43. Instead, there is no indication at all when entering fastboot mode. On my PC, I updated the BIOS and the USB 3.0 firmware thinking that would help, but it didn't. This is an Asus 970 Pro Gaming/Aura motherboard. I've tried it in multiple USB ports, both 2.0 and 3.0. Previously I reinstalled Windows (Windows 10) several times on my PC and that didn't help, either. I had drivers from another phone installed (HTC One M9) and thought that might be conflicting, and removed them, but that didn't do anything either.
I know I've got to be missing something totally obvious but I can't for the life of me figure out what that is. The phone is recognized just fine normally, but as soon as I enter fastboot mode, it's no longer recognized. Is it a problem the fastboot partition itself? I've done cat/proc/partitions and it shows a size of 512 for sde6 (which, I believe, is the fastboot partition), so there does appear to be data in it.
Here is the output of cat/proc/mounts:
1|[email protected]_ii:/ $ cat /proc/mounts
rootfs / rootfs ro,seclabel,size=1824140k,nr_inodes=456035 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=1893300k,nr_inodes=473325,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,size=1893300k,nr_inodes=473325,mode=750,gid=1000 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=1893300k,nr_inodes=473325,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/dm-0 /system ext4 ro,seclabel,relatime,discard,data=ordered 0 0
tmpfs /data tmpfs rw,seclabel,nosuid,nodev,noatime,size=262144k,nr_inodes=473325,mode=771,uid=1000,gid=1000 0 0
/dev/block/bootdevice/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/dsp /dsp ext4 ro,seclabel,nosuid,nodev,relatime,data=ordered 0 0
/dev/block/bootdevice/by-name/modem /firmware vfat ro,context=ubject_r:firmware_file:s0,relatime,uid=1000,gid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/bootdevice/by-name/bluetooth /bt_firmware vfat ro,context=ubject_r:bt_firmware_file:s0,relatime,uid=1002,gid=3002,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=1893300k,nr_inodes=473325,mode=755,gid=1000 0 0
/dev/block/dm-1 /data ext4 rw,seclabel,nosuid,nodev,relatime,discard,noauto_da_alloc,resuid=1000,resgid=9990,data=ordered 0 0
/dev/fuse /mnt/runtime/default/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/read/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /mnt/runtime/write/emulated fuse rw,nosuid,nodev,noexec,noatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
I also wanted to do ls -al /dev/block/platform/*/by-name but it returns 'permission denied', which means it needs root, which I don't have.
What do you recommend I should do next?
Edit: for what it's worth, I have a backup of fbop.img prior to unlocking the bootloader, even though I can't do anything with it at this time. The bootloader is still unlocked and 'OEM unlocking' has been left in the on position on each attempt I've made. I've also been able to flash back to B20 using the stock update and that didn't help either.
Find an old PC, with Windows 7, start from scratch. Do not waste your time in the new ones.
I'm trying to find one this week. Found one already, but unfortunately it had too many problems to be of any use. I may have to wait for the weekend for another shot.