Related
(Avis aux intéressés, j'ai traduit mon message en français, et reparti une discussion sur Frandroid.)
Hello,
I managed to map the partitions on the Gio 5660M (Bell Canada, 2.3.4, MUGK3) in order to extract an ODIN flashable complete stock backup.
I have also made a stock, rooted ROM backup by working in a hex editor. Other tools that helped the mapping were Winmerge, to do file comparisons with an Euro 5660 ROM, and Notepad++ for string searches.
Those with a 5660M that are experiencing issues after flashing Euro 5660 ROMs that have been posted here now have the possibility of flashing back their original radio and kernel.
ROM development and deployment is going to be safer going forward.
I copied the blocks with the dd command as follows:
dd if=/dev/block/bml1 of=/sdcard/bml1 bs=4096
WARNING!!! DO NOT dd /dev/block/stl5 as there have been multiple reports of bricking following reading it. We already know that this block contains the EFS partition, including the SIM-lock code. You can however dd bml5 without issue from a "live" phone. If you absolutely want stl5, you may get it by using a rooted custom recovery.
From what I've gathered bml is essentially a lower level interface to the same blocks accessed by stl, but the results differ somewhat in resulting file size.
Here are the results:
Code:
/dev/block/bml1 MIBIB
/dev/block/bml2 QCSBL
/dev/block/bml3 OEMSBL
/dev/block/bml4 AMSS
/dev/block/bml6 Essentially empty, with a FSR_STL string at the beginning.
/dev/block/bml7 arm11boot
/dev/block/bml8 boot.img. My initial assumption was based on the .ops file supplied with the Euro ROM I've done my comparisons with. This has since been confirmed with actual flashing.
/dev/block/bml9 recovery.img for the same reasons as above.
/dev/block/bml10 Essentially empty. Mine has a BMC string at the beginning which matches the CSC code on this phone, followed by an ON and an OFF.
/dev/block/bml11 Empty. \xFF all around.
/dev/block/bml12 Seems to contain the same RFS data as stl12, but with an additional 8 megs of data/padding, not readable by MagicISO.
/dev/block/bml13 Like 12 above, but user data
/dev/block/bml14 As above, but the almost empty partition
/dev/block/stl1 cannot open for read
/dev/block/stl2 cannot open for read
/dev/block/stl3 cannot open for read
/dev/block/stl4 cannot open for read
/dev/block/stl6 Empty: contains only \xFF
/dev/block/stl7 cannot open for read
/dev/block/stl8 cannot open for read
/dev/block/stl9 cannot open for read
/dev/block/stl10 cannot open for read
/dev/block/stl11 cannot open for read
/dev/block/stl12 system.rfs - is flashable as-is once tarballed. Also contains the CSC files as we're taking this from a "live" installation, contrary to an OEM provided image. (My image is also rooted for the same reason.)
/dev/block/stl13 data.rfs - User data partition
/dev/block/stl14 cache.rfs - Odin hangs when I try to flash it. Use CWM and dd back into place from the SD card.
From what I see we can't repartition our phones like the GT-I9000 guys do, so there are no PIT files to worry about. Only the OPS files which ODIN uses. We're not able to flash with Heimdall in its current configuration as it requires a PIT file.
GT-S5660M_MUGKG3_stock_rooted_ROM_v2.7z (101.46 MB)
Un7-Zip, flash tarball with Odin using the "One Package" option. Tested working on my phone. I think it goes without saying that flashing this is at your own risk.
(PDA: S5660MUGKG3 PHONE: S5660MUGKG3 CSC: S5660MBMCKG3)
Tutorial on flashing with Odin, with link for the appropriate version for our phone.
I've released my custom 5660M ROM, ArpegGioMod.
Goodbye,
Darkshado
Wow,
Thank you very much. The screen brightness issues and problems connecting to the mobile 3G network were very troublesome.
I will be flashing this ROM back to my s5660m.
THANK YOU!
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Cool! Please, pretty please let me know as soon as possible how it turns out. When do you plan on trying this? This afternoon or later tonight?
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Good luck,
Darkshado
Coolty said:
STATUS UPDATE:
I have successfully flashed the image to my phone, i had to rename factory.rfs to system.rfs in order for ODIN to flash successfully. Also, it may not be important but I noticed that your image is missing the csc.rfs file.
I copied it from another ROM but it still didn't take it.
Even with the CSC.RFS file missing, it SEEMS to work GREAT! No more screen issues or 3G problems so far, I will keep you updated!
Again, thank you for uploading this, Hopefully soon there will be a CM7 for the s5660m!
Click to expand...
Click to collapse
Great! You just made my day!
About the missing CSC file: CSC is an acronym for Carrier/Country Specific Code. The csc.rfs file is a partition image file that, as far as I can tell, is merged with the contents of the system.rfs partition. In our case, the CSC file would contain the APN settings, as well as the Bell proprietary apps like self-serve and remote PVR.
Instead, since I took the system partition from a live phone, the CSC content is already in the system.rfs partition. I think the idea behind this is that Samsung can release new CSC packages without having to update the whole firmware when "new" carriers add the phone to their lineup.
I'll see if I can edit the RFS partitions, (maybe by mounting them on the phone directly?) if so, I would be able to unroot, and make that separate CSC partition as well. That would make the backup completely stock, as if it came right from Samsung.
Another, simpler solution would be to modify the OPS file to skip the CSC partition.
One question: did you re-tar each file individually for ODIN to take them?
CM7 port: I'd love to have one on that phone as well, but I'm not in a position to tackle that project, yet. The good news is that since we now have a way to bring the phone back to stock, we can experiment safely.
Goodbye,
Darkshado
Depending on how much you feel at ease with experimenting, you might be able to make a modified OPS file and new tar archive to flash only AMSS and boot.img to your system. Boot in recovery to wipe cache and dalvik-cache, then reboot the phone in normal mode. *If* things go according to plan you'd be left with a custom ROM'ed and functional phone. Otherwise just flash the whole thing back to stock.
Click to expand...
Click to collapse
I will try this as well, will let you know the status of that as soon as I get to that. I am pretty confident with flashing phones by now
One question: did you re-tar each file individually for ODIN to take them?
Click to expand...
Click to collapse
No, I use linux so it was an easy process of copying the factory.rfs to my HDD, renaming it to system.rfs, deleting factory.rfs from TAR, and then adding system.rfs to the TAR file.
Let me know if you want me to try anything else, as I have access to linux and am pretty knowledgeable when it comes to things of that nature.
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Step by Step guide for Noobs?
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
red02 said:
Hello,
My Samsung Gio S5660M is on an infinite loop.
Will this method fix the issue?
Can someone kindly give a step-by-step guide to this method (starting from what software/driver needed)?
Thanks a lot.
Click to expand...
Click to collapse
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Coolty said:
I can confirm that replacing amss and boot.img for 5660m from custom firmware meant for the 5660 works perfectly. I am using this tar: GioPro-1_2-LITE-by_ZimniY-S5660XXKQ6_S5660XXKQ5_S5660SEBKQ1.tar AND the GioPro 1.3 update zip. No screen issues or 3G problems. If you like I can upload the edited ROM for ODIN.
Click to expand...
Click to collapse
if you could post it, that would be much appreciated!!
steez003 said:
if you could post it, that would be much appreciated!!
Click to expand...
Click to collapse
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Coolty said:
Why is your phone stuck in an infinite loop? What did you do to cause this?
did you somehow overwrote stl5(the efs partition afaik) while trying to unlock your phone?
Click to expand...
Click to collapse
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
red02 said:
Hello Coolty,
Yes, that's exactly what happened. I tried to unlock it using Andorid Terminal Emulator, and although it gave me the unlock code, it fell into infinite loop upon restart.
Will your uploaded file fix this problem?
What would possibly provide a detailed guide on how to use the file?
Thanks.
Click to expand...
Click to collapse
Hi,
I'm not one for explaining things in great detail, but the basic breakdown of the things you need (google is your friend) are:
1) Odin_Multi_Downloader_v4.42
2) The USB drivers for your phone (Hint: Samsung Kies)
3) OPS File (for this phone, I recommend GIO_v1.0.OPS)
4) Either a single TAR file or multiple files (eg, appboot, PDA, etc) For the file I am uploading it will be a single TAR file which is a package that includes all the things needed.
Then, you just remove the battery in your phone, unplug it from USB or wall charger, put battery back in, hold vol down + HOME + power until you see a screen (you may have to press a vol key after that, read the screen to see if you need to) Your screen on the phone should say DOWNLOADING... This is when you:
1) connect phone to computer via USB after installing drivers (kies, usb driver)
2) make sure kies is closed
3) run ODIN
4) choose the proper OPS file
5) click single package
6) choose the TAR file you want to flash to your phone
That's it!
EDIT:
I am providing some forum links that may better explain how to do what you need done:
How to unbrick (for samsung ACE, but applies to the 5660m) http://forum.xda-developers.com/showthread.php?t=1071970
How to use ODIN to flash your phone: http://forum.xda-developers.com/showpost.php?p=16979859&postcount=549
And of course, the great bible of GIO 5660 links and information: http://forum.xda-developers.com/showthread.php?t=1209425
I have updated my previous post to include the download link to the fixed rom for use with the s5660m.
(search for "s5660m by coolty" on the forums to find it)
Coolty said:
I am currently in the process of uploading the edited TAR file to megaupload. The file is rather large so it may take another hour or so to complete. I will update this post when it is completed.
EDIT:
Here you go! GioPro 1.2 LITE edited for use with the Samsung Galaxy s5660m
Gio Pro 1.2 LITE updated for canadian s5660m by coolty
Click to expand...
Click to collapse
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Will this help at at all with a blank IMEI? I assume this would only help for people flashing back to stock firmware or recovering from a non-bootable or reboot loop phone?
steez003 said:
Thanks! I ended up flashing my phone and I have run into a problem. For some reason Wifi won't work in GioPro. It says 'Turning on...' and then it will say 'Error'. Any ideas?
Thanks
Click to expand...
Click to collapse
I'm also running into the same issue
Sent from my Nexus S using XDA App
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Waqasshazad: Maybe wiping the caches will help, but the issues might be due to running a 5660 on a 5660M as well. We know the kernels and modems aren't compatible, it may go a bit further. By the way, it's spelled factory.
MacrossFX: I've seen mentions of people dd'ing their stl5 partition into a file and then back on the phone, but I'm unsure this worked in the end. I'm afraid your only solution might involve a shipment to the service center...
ClockworkMod Recovery for the Samsung Galaxy Gio GT-S5660
http://forum.xda-developers.com/showpost.php?p=16980117&postcount=559
May be this can backup for you , too with s5660m , i have tested on Gt s5660 and it worked perfectly fine..
waqasshahzad1986 said:
Thats why i recommend you guys always do a factory reset before and after flashing , these glitches , like gps issue , wifi , stuck on boot logo , won't happen if you properly fectory reset before and after flashing....
Click to expand...
Click to collapse
I followed your instructional video and did do a factory reset before and after. Maybe i'll try reflashing it again tonight and see what happens.
[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer
jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:
Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.
Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:
Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks
Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.
jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)
Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.
Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original
I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?
Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.
Congratulations @jen.magnolis
Well done
Hey guys,
It seems more and more people are receiving the new version of the P8000:
- Stock Android 6
- New fingerprint scanner that is moved slightly higher and is able to unlock phone from screen-off (I confirm this is working)
- Sim 2 is combined with the micro-sd (I haven't tried whether you can have them both in at the same time)
- Somethings new about the display, since people are reporting errors with it after flashing older roms.
Warning: do NOT flash other roms. We have no way to unbrick the soft bricks yet!
---
Other topics that refer to this version:
http://forum.xda-developers.com/elephone-p8000/general/rom-p8000-t3431571
http://forum.xda-developers.com/elephone-p8000/help/stock-rom-p8000b-t3434477
http://forum.xda-developers.com/elephone-p8000/general/p8000-version-announced-t3346848
---
For development:
- The phone does not come pre-rooted. We have no way to flash custom recovery yet. Any tips for getting root? I've tried such tools as Kingo and vRoot, they don't work.
- We need the blocks file (scatter file) for SP Flash Tools. MTKDroidTools reports "unknown rom structure". Any help? Would love to start working on this.
Looking forward to hearing from others who have this version/who can help me with these questions.
Thanks!
Emile
Nice! Can you provide a dump from /system and /boot maybe?
BlueFlame4 said:
Nice! Can you provide a dump from /system and /boot maybe?
Click to expand...
Click to collapse
I would, if I knew how to. Any pointers?
Emileh said:
I would, if I knew how to. Any pointers?
Click to expand...
Click to collapse
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
BlueFlame4 said:
Sure thing. On a rooted device, go into adb shell.
Then use "mount" command to check which partitions are mounted. One should be "/dev/block/platform/mtk-msdc.0/by-name/system" or similar. Use "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/emulated/0/system.img bs=1M" to dump the system to the internal sdcard to the file "system.img". If adb complains that bs=1M is an invalid option, try again without that one. A system dump can take some time where you will not get any feedback, so be patient there
Do the same for boot. So "/dev/block/platform/mtk-msdc.0/by-name/boot" should be the way to go for the path. I cannot tell the definite pathes on Android 6.0 but I am rather sure they are more or less like this.
If you run into troubles, just ask
Click to expand...
Click to collapse
Thank you for your great instructions! The problem is that we've yet to achieve root on this device. We don't have a custom recovery for this version of the P8000 yet and other 'standard' methods of rooting don't work for me.
(I'm pretty solid in shell, so I'll do this afterwards, but I guess root is actually the first step).
// Edit to say: it does not come pre-rooted
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
flo1k said:
Since the elephone support on facebook didn't realize there are two different versions of the P8000 available, I still need a ROM to unbrick my phone.
Click to expand...
Click to collapse
Ok, we know that, but doesn't really help us
Can you write them an e-mail?
I will do
Edit: OK, see if there will be an answer.
Thank you flo1k!
I have e-mailed as well, and would like to post on the Elephone forum, but don't seem to have access (because of minimum post count, I guess)
Anyone willing to ask for a ROM for the new P8000 on the forum there?
ROM Dump
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
FrauHofrat said:
@BlueFlame4
I can provide ROM dump in two versions:
1) a dump from adress 0000 0000 to 9d80 0000 (apr. 2.5 GB in one file)
2) a readback generated with the scatter.txt of the 'old' 5.1 stock ROM (apr. 2.8 GB seperated in 23 files)
Click to expand...
Click to collapse
The second choice looks promising
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
FrauHofrat said:
Maybe a stupid question
where shall I upload the files - any preferred webspace?
I'm uploading the files - because they contain my NVRAM I send the link as PM as soon as the upload is finished
Click to expand...
Click to collapse
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Just checking thank you for your help in any case!! Really looking forward to it.
// edit: ah, you just used the old scatter file. But does that one work for this version?
Emileh said:
Are you sure we're talking about the same version of the P8000? Cause as far as I know there isn't 5.1 available for this version... Right?
Click to expand...
Click to collapse
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
// edit: ah, you just used the old scatter file. But does that one work for this version?
Click to expand...
Click to collapse
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
FrauHofrat said:
No, there is only one Firmware available - the mysterious P8000_6.0_20160516.
Btw, this Phone contains a new mainboard model "K06TS-L-V2.0.3" - the 'old' mainboard is moder "K05T...."
No, it doesn't work resp. the phone boots with this firmware, but the LCD-driver is the wrong one - the display only shows coloured lines and blurry spots. And there are probabely some more bugs ....
Click to expand...
Click to collapse
But if the phone boots with the firmware, doesnt that mean that the scatter file of the regular P8000 works? Since it flashes the firmware correctly.
The problem is that I was not able to flash the 'readback files' to the faulty phone.
When selecting 'Only Download' at SP-Flashtool I got the error "PMT... must be download"
When selecting 'Firmware Upgrade" I got some BROM error code
In both cases I used the same scatter,txt which I used to 'readback' the firmware from the working phone
Actually I have to correct my statement in post #15:
I flashed the faulty phone with the last 5.1 stock ROM (160711) - with this stock ROM the phone boots up but LCD (and probably more things) is not working.
I have actually gotten alot further
You have the use the scatter.txt from Android 6.0, which works perfectly fine. I have been able to extract boot.img, system.img and recovery.img that way (using Readback in SP Flash Tools)
Which ones do you need?
They probably flash fine (only thing I've flashed so far are custom recoveries, and although my ported PhilZ starts, I havent gotten it to mount anything.)
A little warning: don't use anything that has anything to do with Android 5.1. Those scatter files don't work
These are great news!
"Which ones do you need?"
Probably all of them
Ok this contains the scatter file, preloader, system.img, boot.img and stock recovery.img
https://ehaffmans.stackstorage.com/index.php/s/uKGKCir0BociydU
You need SP Flash Tools v5, select the scatter file first, then deselect everything, and only select these 4 and manually select the correct files.
Btw, the name of the preloader file is wrong, don't worry. It came from this phone
I am of course not responsible for anything!
Can you guys please confirm this doesn't contain anything personal? Like personal files or IMEI or something. Thanks!
Friends !
I wanted to rip off some LG Software ( eg. Weather, Calender, Health etc) and ALL Google
Software from my KDZ File and flash this modified KDZ then onto my G4.
I´ve tested out some Custom Roms like LineageOS, Resurection and some other, all Google Free but they all drain out my Batterie fast or has some other issues.
The best working Rom for me is the Original V20g.
My G4 is rooted with Magisk. In TWRP i used GKillerExtreme.zip to eliminate all Google Stuff but after cleaning there are some Google Apps still on the Phone and can´t delete them.
So my Idea is to modify my KDZ file before flashing on the Phone.
------------------------------
I followed these Post to extract all Files from the KDZ:
https://forum.xda-developers.com/showthread.php?t=2666967
After extracting the *.dz file also i have a lot of *.bin files now.
So, how to working on with these *.bin Files now, how to open them, delete some Files are contained in the *.bin File and rebuild a flashable File?
Maybe there is a existing workaround here on XDA ?
Thank you all for a little Help.
-Ralf-
Foto-AG said:
Friends !
I wanted to rip off some LG Software ( eg. Weather, Calender, Health etc) and ALL Google
Software from my KDZ File and flash this modified KDZ then onto my G4.
I´ve tested out some Custom Roms like LineageOS, Resurection and some other, all Google Free but they all drain out my Batterie fast or has some other issues.
The best working Rom for me is the Original V20g.
My G4 is rooted with Magisk. In TWRP i used GKillerExtreme.zip to eliminate all Google Stuff but after cleaning there are some Google Apps still on the Phone and can´t delete them.
So my Idea is to modify my KDZ file before flashing on the Phone.
------------------------------
I followed these Post to extract all Files from the KDZ:
https://forum.xda-developers.com/showthread.php?t=2666967
After extracting the *.dz file also i have a lot of *.bin files now.
So, how to working on with these *.bin Files now, how to open them, delete some Files are contained in the *.bin File and rebuild a flashable File?
Maybe there is a existing workaround here on XDA ?
Thank you all for a little Help.
-Ralf-
Click to expand...
Click to collapse
Don't know how you would rebuild it - I guess you would need to use a twrp script to flash them onto the partitions
As for modifying them, depends on the bin file. For system, you can mount it on Linux to a folder
E.g.
Code:
mkdir ./extractedSystem
sudo mount ./system.bin ./extractedSystem
Then you can access it through that folder. When you are done...
Code:
sudo umount ./extractedSystem
Extract: SALT
Mount: SALT (Advanced menu)
Flash: SALT (v4)
Ah yea and btw: you can't create your own kdz. Well you can but you can't flash it as it must be signed.
Sent from my LG-H815 using XDA Labs
ThePiGuy said:
Don't know how you would rebuild it - I guess you would need to use a twrp script to flash them onto the partitions
As for modifying them, depends on the bin file. For system, you can mount it on Linux to a folder
E.g.
Then you can access it through that folder. When you are done...
Click to expand...
Click to collapse
Thank you very much. To mount a bin file as a Drive in Linux (FWUL ) is the Key. All other steps i will find in the next Days. Thx again.
steadfasterX said:
Extract: SALT
Mount: SALT (Advanced menu)
Flash: SALT (v4)
Ah yea and btw: you can't create your own kdz. Well you can but you can't flash it as it must be signed.
Click to expand...
Click to collapse
Thank you steadfasterx. I was think about to check Salt out too. I was reading about Salt alot and give it a try in the evening. Thx.
Foto-AG said:
Thank you steadfasterx. I was think about to check Salt out too. I was reading about Salt alot and give it a try in the evening. Thx.
Click to expand...
Click to collapse
when you use FWUL SALT is included
the flashing part of SALT is still in beta testing state thats why v4 is not (public) available yet ..
.
ThePiGuy said:
Don't know how you would rebuild it - I guess you would need to use a twrp script to flash them onto the partitions
As for modifying them, depends on the bin file. For system, you can mount it on Linux to a folder
E.g.
Then you can access it through that folder. When you are done...
Click to expand...
Click to collapse
Hey.
Doesnt work for me. Getting error in Terminal.
Mount: /home/android/extractedSystem: wrong fs type, bad option, bad superblock on /dev/loop1, missing codepage or helper program, or other error.
So, im not so involved into Linux and have no idea whats wrong. Ive test with all .bin files but the error message pops up on every.bin file
My FWUL version is 2.7, the 8GB version on USB Stick.
Im pretty sure i did something wrong :angel:
Greetings
Ralf
steadfasterX said:
when you use FWUL SALT is included
the flashing part of SALT is still in beta testing state thats why v4 is not (public) available yet ..
.
Click to expand...
Click to collapse
Hey....
Hmmm no can not find SALT. No Icon, no Folder, unknown command in Terminal. Search term for salt give me no result.
Using FWUL 2.7 8GB version. FWUL did some little updates but still no SALT.
-Ralf-
Foto-AG said:
Hey....
Hmmm no can not find SALT. No Icon, no Folder, unknown command in Terminal. Search term for salt give me no result.
Using FWUL 2.7 8GB version. FWUL did some little updates but still no SALT.
-Ralf-
Click to expand...
Click to collapse
Consider to read through whats included in FWUL : https://forum.xda-developers.com/showpost.php?p=70272684&postcount=3
.. there are even screenshots..
.
steadfasterX said:
Consider to read through whats included in FWUL : https://forum.xda-developers.com/showpost.php?p=70272684&postcount=3
.. there are even screenshots..
.
Click to expand...
Click to collapse
Many thx. But i dont have the Samsung and LG Folder on the Desktop.
Will download FWUL tomorrow from XDA. My FWUL was dl from an other Website because i have speed issues when dl from XDA or the Androidhosting Service. More then 5 hrs for dl the FWUL image, somewhere in Texas or other US- State.
Thank you btw for your Support me.
Foto-AG said:
Many thx. But i dont have the Samsung and LG Folder on the Desktop.
Will download FWUL tomorrow from XDA. My FWUL was dl from an other Website because i have speed issues when dl from XDA or the Androidhosting Service. More then 5 hrs for dl the FWUL image, somewhere in Texas or other US- State.
Thank you btw for your Support me.
Click to expand...
Click to collapse
yea AFH can be slow..
you can use a nightly or my mirror here:
http://leech.binbash.it:8008/FWUL/
("stable" contains the 2.7)
btw tonight a new nightly is planned (if all goes well)
steadfasterX said:
yea AFH can be slow..
you can use a nightly or my mirror here:
http://leech.binbash.it:8008/FWUL/
("stable" contains the 2.7)
btw tonight a new nightly is planned (if all goes well)
Click to expand...
Click to collapse
Hey. My little response....
I did it and ripped off most of all the Bloatwares. Google is complete out off my Phone now and don't wont it back. It was a very hard and long process to eliminate all the Stuff. Alot of failures was coming up, alot of new image installings and start again over because i delered some Mainfeatures or essential Routines etc. OMG i don't want do this again in my life lol.
So its better to flash a google free Rom.
Okay, only my little response for this thread and Big Thanks to Steadyfast for the last Supports !
My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
cbb77 said:
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
Click to expand...
Click to collapse
thanks for the info, i saw a few threads a few days ago about secure storage and did it manually which didn't help with the issue. similarly neither does the module for Majisk . a case of keep looking i guess. any other suggestions will be very much appreciated
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
cbb77 said:
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
Click to expand...
Click to collapse
Cheers will give it a go - at this point i have nothing to lose, just taken a fresh backup so nothing ventured nothing gained
its stuck no boot while removing secure_storrage module from majisk
Oddly having tried the suggestion above of removing the majisk module the device no longer boots it gets stuck on the Samsung logo. For some reason the vendor partition is no longer able to mount.. Completed a restore eventually to get it to boot. Disabling the module yields the same result. no vendor partition and no boot. Going back to an earlier backup prior to the module being installed
The plot thickens
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
c6pea said:
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
Click to expand...
Click to collapse
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Boot failure when LIbs replaced
ashyx said:
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Click to expand...
Click to collapse
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
c6pea said:
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
Click to expand...
Click to collapse
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
ashyx said:
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
Click to expand...
Click to collapse
Thanks for the assist
It occurs only when the Libs are changed.
Originally using the majsic module to install the libs it couldn't overwrite the files as they are in use. modifying the build.prop seemed to resolve that but as soon as those libs are change either manually through terminal or via the installer i end up with a soft brick LOL
its Bugging me!!!
Interestingly
Once the device hangs.
Simply restoring the vendor partition doesn't fix the boot issue.
In order to get the device to boot I have to restore /data (you don't need to restore /vendor just /data)
oddly restoring the /data partition restores the 2 library files in /vendor to their respective originals
Majisk zip extraction issue
so I have resolved the Bluetooth issue, Rather having majisk install the module i just downloaded it and extracted the contents and discovered that upon zip extraction the contents of each file were appended to themselves. see screenshot "confused.jpg" of the readme.md - so in relation to the library files, the files being installed were double in size hence corrupt.
ie /vendor/lib/secure_storage.so should =308kb the file being insatalled in my /vendor/lib partition was 616kb the 64 bit library was also double the size it should have been.
infarct all the files within the Zip had the same issue.
so i extracted the Zip contents on my pc and transferred the library files via usb. made the relevant changes to build.prop and stopped the secure_storage deamon. Machine now boots and Bluetooth pairings are retained across reboots.
Small Wins
Any one have a clue why the files would double up on content??????
built in zip extractor
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
c6pea said:
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
Click to expand...
Click to collapse
7zip is the extraction utility you want. Winzip is pants.
ashyx said:
7zip is the extraction utility you want. Winzip is pants.
Click to expand...
Click to collapse
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
c6pea said:
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
Click to expand...
Click to collapse
Same for winrar, closed source bloated rubbish.
7zip supports practically every format and totally ad free.