Related
On my rooted Defy - how do I install a zip-file??
Like this one;
http://forum.xda-developers.com/showpost.php?p=12426274&postcount=24
install the 2ndinit apk 1.4.2 newer ones wont work with some files
then reboot 2 times.
third reboot: press volume down, when the led is blue.
now choose recovery by pressin vol up or down and power to accept.
then choose costum recovery, and apply zip from sd. choose your file and confirm.
done
hope this answers your question
Thanks, seems simple enough
uh, where do I find 2ndinit.apk
You can find it here.
I know how to install .zip but I have a question. CWM3.1 does not flash some .zip like a baseband or a theme. It says "aborted". I think that the problem is that the file is not signed or something. In CWM2.5.1.8 works but the problem is that CM7 or MIUI changes it to CWM3. So, what should I do?
Thanks!
Works fine, even the mentioned zip-file!
The "issue" is that the latest CWM3.x no longer support "amend scripting" (stored in update-script) and won't apply zip's created with such scripts. Therefore all .zip which where written using the old method should be converted to edify scripting (which use different statements - more details here-).
is there an way to downgrade the 2ndinit? an how-to would be very nice
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
nepotu said:
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
Click to expand...
Click to collapse
and how do i do that? with rootexplorer? what for do i need the file permission? to change it or to set it after changing the files?
Yup. You can replace it using an app like root explorer. And the file permission should be set up after you copy the file (if you have the wrong file permission it won't work).
EDIT: I haven't tried yet to downgrade it this way but that's what I've read on the forum, therefore I cannot guarantee you it will work.
sry for me being a noob. i found the file named recovery in the folder you mentioned. but have got only the file 2ndinit.apk..... where do i get the recovery file from 2ndinit.apk ?
thank you for your time!
You can unpack it using a tool like Apk Manager 4.9 or simply by using 7zip to extract the files from the apk which is in fact some sort of archive. However as I've mentioned in the previous post I didn't tried to downgrade using this method. All I can say is that I've read here on xda about this method, therefore I cannot guarantee you this will work. I think is better to wait someone with more experience to answer.
As an unexperienced user i think i'll wait for a better solution.
As i read, this problem appears quite often, how come that nobody tried to make a solution for this problem?
This is a software unlock for the Motorola Defy
NEW: Jelly Bean roms and ICS roms work!
See the troubleshooting post (post N°2) if you have problems!
Last update: 06/06/2012 ->Troubleshooting section updated (see post 2)
Disclaimer: This manipulation is not risk free. Niether I nor XDA Developpers can be held responsible for damage made upon your phone. Thus, don’t worry we're doing good work and you'll do a backup
Root is needed!
Credits go to yakk from motofan.ru / Special thanks to Labsin for his involvement and help
Note: Not all Baseband versions work with this hack, to know if it will work for you, go to settings-> system info and check if baseband version is "EPU93_U_00.59.01". If it is not indicated there, then try installing defybaseband switcher and look at info in the app
If your baseband version is different, you can try to change it to the one that works (nandroid backup first ) by downloading Baseband_change(EPU93_U_00.59.01).zip, and putting it in /sdcard/, and flashing it via recovery.
Flashing a zip has never been easier
Thanks to labsin, there's an easy flashable.zip that will:
Backup your original two files and put them in the folder "simlock_original_files" on your SD card (safety first )
Apply a modification to init.mapphone_umts.rc
Copy the fixed bp_ptc file
Go into recovery, flash Softunlock_defy_v1.1.zip that fits your baseband version and you're done!
!!YOU MUST REBOOT ONCE AFTER THE OPERATION BEFORE CHANGING SIMS!!
Voila!
Don't forget to reboot phone once!
Only then you can test by rebooting with another simcard
Hit thanks button if i helped you!
Any problems? I'm here to help
Changelog
v1.3:
ICS ROMs are now fully supported!
v1.2:
zip will check if the line to be added already exists, so it doesn't get added more than once
v1.1:
automated zip that will add a line in mapphone_umts and copy fixed pt_ptc in system
Troubleshooting
I have no signal when i put another simcard in my Defy
Have you rebooted at least once BEFORE changing sim cards??Try using Defybaseband switcher to select the correct frequencies for your carrierTry method below
You are still asked the unlock code
- Turn on Airplane Mode
- Run Terminal emulator and type "su" and then "bp_ptc"
- Turn ofr Airplane Mode
Airplane mode won't turn off
Flash the baseband(EPU.0.59..) file in the first post, then play around with your APNs and network settings untill you fix it (see post 308)
You are having trouble unlocking a stock ROM
See Post 260
Proof of success
jorgeoro said:
Holy mother of Jesus, I could unsimlock my defy+ (plus) . Here is what i did (i think some steps could be ignored but is good to know the entire procedure i've done)
1) Because of a failed CM7 flash, first I flashed a 2.3.5 SBF
2) Flashed quarkx 26-feb nightly for defy+ (baseband EPU93_U_00.60.00)
3) Changed to a proper baseband with defy-baseband-switcher v4.0
3) Changed to baseband EPU_U_00.59.01 following steps mentioned in 1st page
4) Flashed softunlock 1.2 for EPU_U_00.59.01
5) Rebooted (still no sim change till this step)
6) Power off the phone and changed SIM
7) Rebooted
8) Almost had an orgasm
I'll be posting links i used later if somebody ask for them
Thanks to all people directly and indirectly involved (very special thanks to crakeron for his help)
Click to expand...
Click to collapse
So I guess i use root explorer to put the files where they go?
thisjustin said:
So I guess i use root explorer to put the files where they go?
Click to expand...
Click to collapse
Correct
A simple copy/paste operation
crakeron said:
Correct
A simple copy/paste operation
Click to expand...
Click to collapse
Ok thanks got it
Update.zip
Made it as an update package so you don't need to use root-explorer...
It should just copy the appropriate files and set the right permissions.
Edit: Now makes a backup to defy_simlock_originals on your sd
labsin said:
Made it as an update package so you don't need to use root-explorer...
It should just copy the appropriate files and set the right permissions.
Click to expand...
Click to collapse
Ready to flash from 2nd-init recovery?
Thank you very much!
flashed via 2nd init now testing just got to find my at&t simcard
Garrafone said:
Ready to flash from 2nd-init recovery?
Thank you very much!
Click to expand...
Click to collapse
Should be that yes. Don't have a locked Defy but should do it.
thisjustin said:
flashed via 2nd init now testing just got to find my at&t simcard
Click to expand...
Click to collapse
Can you pls tell it the zip works? Should be the same as pasting so..
Didn't work with the zip
R you on CM7 and witch version? First post also mentions reboot afterwards with good sim and reboot again with other sim.
Did it work the way mentioned in first post?
labsin said:
Made it as an update package so you don't need to use root-explorer...
It should just copy the appropriate files and set the right permissions.
Click to expand...
Click to collapse
Awesome! Thanks! I'll put this in the OP tonight (with credits of course)
Sent from my 1Ghz CM7 + CM9 Defy
thisjustin said:
Didn't work with the zip
Click to expand...
Click to collapse
labsin said:
R you on CM7 and witch version? First post also mentions reboot afterwards with good sim and reboot again with other sim.
Did it work the way mentioned in first post?
Click to expand...
Click to collapse
I admit: I haven't tried this yet, but I did noticed that the OP says to replace init.mapphone_umts.rc to: /system/bootmenu/2nd-init/ and that your patch copies it to: /system/bootmenu/2nd-boot/ folder...
I'm could be wrong on this, but I believe that most people use 2nd-init boot by default (I've only used 2nd-boot while having ICS as dual boot before). But again; I'm just guessing here and could be totally wrong and it might make no difference...
Cheers, and btw, thanks for teaching me how to backup files [with a zip patch]
My OP say's 2nd-init, are you talking about the flashable zip?
Sent from my 1Ghz CM7 + CM9 Defy
crakeron said:
My OP say's 2nd-init, are you talking about the flashable zip?
Sent from my 1Ghz CM7 + CM9 Defy
Click to expand...
Click to collapse
Yes, the flashable zip replaces the file in 2 nd-boot directory so I thought that it "might" be why it didn't work for that guy...
[] AL [] said:
Yes, the flashable zip replaces the file in 2 nd-boot directory so I thought that it "might" be why it didn't work for that guy...
Click to expand...
Click to collapse
True, i'll modify it quickly
Sent from my 1Ghz CM7 + CM9 Defy
thisjustin said:
Didn't work with the zip
Click to expand...
Click to collapse
retry with the new zip, there was an adress error in the old one (nothing bad, don't worry)
New flashable zip uploaded. Fixed (changed .../2nd_boot/... to ..../2nd-init/....)
Hello, the file /system/bootmenu/2nd-init/init.mapphone_umts.rc provided did not work for me. It did not detect any SIM card.
So I edited the original file to defy me and I added the line "service bp-ptc /system/bin/bp_ptc" around line 194 (This can change depending on your file) after the line "user root" in the section "# Adb over Network"
After the copy on my smartphone with correct permissions, it worked.
If it can help
erghaize said:
Hello, the file /system/bootmenu/2nd-init/init.mapphone_umts.rc provided did not work for me. It did not detect any SIM card.
So I edited the original file to defy me and I added the line "service bp-ptc /system/bin/bp_ptc" around line 194 (This can change depending on your file) after the line "user root" in the section "# Adb over Network"
After the copy on my smartphone with correct permissions, it worked.
If it can help
Click to expand...
Click to collapse
Thanks, seems very usefull
Edit: that line is at the right place in the files i gave so you had a different init.mapphone_umts.rc file probably. What ROM are you running?
I've searched all forums for a solution to make Viper4Android work on Nexus 9.
None has been working for me without killing Chromecast support.
So I've made two solutions to make it work:
TWRP, Root and Busybox is required!
As system app:
In TWRP install V4A_2.3.3.0_[Quality].zip
Boot Android and open V4A
(Uninstall and) Install driver
Reboot Android
As normal app:
In TWRP install V4A_Conf.zip
Boot Android
Install SELinuxModeChanger and set it for "Permissive" mode
Install V4A
Open V4A and install driver
Reboot Android
I've testet with Google Music and Wimp.
PLEASE hit thanks if this helps you!
If you're on another Lollipop device the tricky part in making the V4A driver stick, is to manually edit the audio_effects.conf on the "Vendor" partition. V4A only writes to the system audio_effects.conf.
trackloading said:
I've searched all forums for a solution to make Viper4Android work on Nexus 9.
None has been working for me without killing Chromecast support.
So I've made two solutions to make it work:
TWRP, Root and Busybox is required!
As system app:
In TWRP install V4A_2.3.3.0_[Quality].zip
Boot Android and open V4A
(Uninstall and) Install driver
Reboot Android
As normal app:
In TWRP install V4A_Conf.zip
Boot Android
Install SELinuxModeChanger and set it for "Permissive" mode
Install V4A
Open V4A and install driver
Reboot Android
I've testet with Google Music and Wimp.
PLEASE hit thanks if this helps you!
Click to expand...
Click to collapse
sweet i was looking in the viper4android main thread..i saw ur post. with link.. now i could install viper on my N9..
one question... its better if i flash into system app correct??
Lw00d said:
sweet i was looking in the viper4android main thread..i saw ur post. with link.. now i could install viper on my N9..
one question... its better if i flash into system app correct??
Click to expand...
Click to collapse
That's the one I'm using, so I don't have to be in permissive mode...
I'm getting " unfortunately V4a has stopped" after flashing super quality on Lollipopalooza Rom. any suggestions?
dom2684 said:
I'm getting " unfortunately V4a has stopped" after flashing super quality on Lollipopalooza Rom. any suggestions?
Click to expand...
Click to collapse
I got a similar response with the pure AOSP build, but not with these zips. I used the zips mentioned in the Q&A V4A thread. I think this only works with stock?
igothacked1 said:
I got a similar response with the pure AOSP build, but not with these zips. I used the zips mentioned in the Q&A V4A thread. I think this only works with stock?
Click to expand...
Click to collapse
Ahh gotcha thanks
this work great for me..
what are some preferred settings??
I got around to flashing the Super Quality zip and the V4A_conf.zip on the pure AOSP build. NuPlayer in Dev options is disabled and I'm running SELinux in permissive mode. I still can't get the driver to stick.
igothacked1 said:
I got around to flashing the Super Quality zip and the V4A_conf.zip on the pure AOSP build. NuPlayer in Dev options is disabled and I'm running SELinux in permissive mode. I still can't get the driver to stick.
Click to expand...
Click to collapse
I had to edit the audio_effects.conf file in the Vendor folder to get the driver to stick. Add the lines in Step 6 of the following link: http://www.hacktabs.com/how-to-impr...ity-with-viper4android-audio-drivers-effects/
Leave out the lines for xhifi and look at the screenshot for the location in the file to add the lines.
After you do this, try to add the driver again, then restart.
cor_mann said:
I had to edit the audio_effects.conf file in the Vendor folder to get the driver to stick. Add the lines in Step 6 of the following link: http://www.hacktabs.com/how-to-impr...ity-with-viper4android-audio-drivers-effects/
Leave out the lines for xhifi and look at the screenshot for the location in the file to add the lines.
After you do this, try to add the driver again, then restart.
Click to expand...
Click to collapse
I reverted to a backup before I flashed the Super Quality zip.
Which vendor folder? The /system/vendor/ folder that the driver creates or the /vendor/ folder in root? And the .conf file in /system/vendor/ already contains those lines. Even then, the driver won't stick.
If this provides more information, I'm using Dilligaf's kernel. But I'm positive that wouldn't affect the driver installation.
EDIT: Got it. I copied the audio_effects.conf in the /system/vendor/ folder and replaced the one in the /vendor/ folder. Driver sticks now
igothacked1 said:
I reverted to a backup before I flashed the Super Quality zip.
Which vendor folder? The /system/vendor/ folder that the driver creates or the /vendor/ folder in root? And the .conf file in /system/vendor/ already contains those lines. Even then, the driver won't stick.
If this provides more information, I'm using Dilligaf's kernel. But I'm positive that wouldn't affect the driver installation.
EDIT: Got it. I copied the audio_effects.conf in the /system/vendor/ folder and replaced the one in the /vendor/ folder. Driver sticks now
Click to expand...
Click to collapse
Good to hear. I'm not sure why some people have to add the lines and others don't.
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
trackloading said:
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
Click to expand...
Click to collapse
You're right: I'm running Lollipopalooza ROM. That explains it.
Has anyone got convolver to work? The app sees all my irs files in the kernel folder, just has zero effect. Everything else works for me.
Swift keyed from my N9
mrshades812 said:
Has anyone got convolver to work? The app sees all my irs files in the kernel folder, just has zero effect. Everything else works for me.
Swift keyed from my N9
Click to expand...
Click to collapse
I haven't gotten mine to work either. I just noticed it. However, my Oneplus One has IRS working on 5.0.1. It could be how the driver is behaving?
trackloading said:
Hmmm... The /system/vendor folder is just a shortcut to the /vendor/ folder on my device, so it should be the same...?
I'm on pure stock and as I see the posts, the ones having problems is on other roms or kernels.
Click to expand...
Click to collapse
Igothacked said he was using my kernel/ramdisk, I'm not sure what ROM, but the kernel in my boot.img is completely stock, the only edits were to the ramdisk, and I'm positive that would not effect anything with this. I'm not sure about what Roms were being used, I guess it could make a difference, maybe permissions are slightly different or there is a difference with some symlinks with different roms and stock.
Thanks, also working on stock Acer A1-810 too.
I'm also running theLollipopalooza ROM and had to edit the file manually before the driver would install. All seems to be working fine now though. Thanks☺
Nevermind I re-read
[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
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
remember i have not .zip file in media folder
Mr Hassan said:
hello ,
how can i remove starting verizon logo??? and i don,t want any other logos,
i just need like stock samsung boot, for note 4
Click to expand...
Click to collapse
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
-spektor- said:
You can use a app like this: https://play.google.com/store/apps/details?id=tkstudio.sboot to change boot animation or some ROMS like jasmine rom 7.0 have the original samsung logo boot sequence, for the app to work you need root and read carefully before doing anything. Hope this helps.
Click to expand...
Click to collapse
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Mr Hassan said:
thanks brother for reply i fixed this problem, now i,m in another project , i successfully extract the system,img,ext file,,,,now i edited somethings,
now i want to create again in same file, img,ext4
have you any idea about it?
Click to expand...
Click to collapse
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
-spektor- said:
Well if you mean like accessing and editing system files I'm not how to do edit them but I know that you can use a app like root explore: https://play.google.com/store/apps/details?id=com.speedsoftware.explorer that's the free version the paid one is $3.99 in the US. With that you can move and add files to system folder you can edit permission of files and things of that nature.
Click to expand...
Click to collapse
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Mr Hassan said:
ok brother thanks alot,
but i,m talking about stock rom, i already extracted and edit now its need to repack again
Click to expand...
Click to collapse
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
-spektor- said:
Ah ok, so I found these two threads related to the subject one is for repackaging ODIN files if your using a Samsung: https://forum.xda-developers.com/showthread.php?t=2549712&page=5 and the other is a general tutorial on custom roms https://forum.xda-developers.com/showthread.php?t=2195858 Also this article covers mostly everything about creating and installing ROMS http://lazydroid.com/2011/03/howto-repack-and-sign-rom-image-update-zip-files/ I hope this information helps I do not know much about creating or repackaging roms
Click to expand...
Click to collapse
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Mr Hassan said:
ok again thanks,
i,m in samsung note 4 , and i found lot of threads to repack but not success, coz i,m counfuse about where i start?
and how, is that need just system folder or all file like hidden ,cache etc etc
Click to expand...
Click to collapse
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could help it deals with modifying samsung rom and flashing it. If you want to read more on it here's the link: http://android.stackexchange.com/questions/85703/modifying-samsung-rom-and-flashing-it-on-a-device if you wanted to remove apps or add custom apps to your phone you would modify system file.
But what I thought was important was this;
(I did not write this thread)
< "You should be able to use an archive program on PC and recompress to .tar, .gz, and others. Dont forget to re-sign the archive. Keep a copy of your untouched ROM until you have the modified ROM tested and running.
The ROMs are signed with a signature. When repacking if they don't get signed they will fail in flashing. This link will help explain it.
So basically after downloading the firmware you have to rename it so you can extract the files, change them as you need, recompress them again and re-sign them, so you can flash them using Odin." >
This thread was dealing with modifying CM rom;
< "There are multiple solutions available:
Re-Zip the Image
Advantage: You do it once, and can use the resulting image for multiple devices. That's what I did with CM7.2 for my Milestone 2. Easy enough to do:
create a temporary (empty) folder
unzip the zip file to it
remove unwanted *.apk files from /system/apps (be careful of what you remove, of course)
zip up the directory contents again
Using a graphical ZIP manager (like WinZip or the like), steps would be even easier:
open the zip file with the archive manager
remove the unwanted .apk files
if the ZIP manager requires it, save the manipulated zip
Manually cleanup after flashing, using the shell
This is what ce4 recommended in the comments. It requires you using a terminal emulator on your device:
Flash the image as-is
remove superfluous stuff from the system partition by hand (like rm /system/big/junk/example.mp4)
Manually cleanup after flashing, using other tools
Almost the same as the previous method, but a bit more user-friendly. Disadvantage: this won't do for superflous ringtones and the like:
Flash the image as-is
Use a tool like Titanium Backup or Root Uninstaller to remove unwanted system apps" >
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
-spektor- said:
Well system file is where all the data and software is at basically everything visible on the phone. Maybe this article could
Edit: this link explains the signature of the file: (from google) https://code.google.com/archive/p/zip-signer/
Click to expand...
Click to collapse
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Mr Hassan said:
yes brother i want to remove some apps,. in system
even some edits in bulid prop
and after repack it for odin , thats it,
i create zip and trying to install the via twrp, during installation in end its give some error like this
setup finish with error 7 etc etc
so i reboot ,.....its reboot normal but after boot base band is unknown
i,m working on verizon devise.
in very simple words i,m trying to create rom without verizon apps and some more edits
and that all work in stock rom
Click to expand...
Click to collapse
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
-spektor- said:
.
Click to expand...
Click to collapse
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Mr Hassan said:
Who its looking cool. I'll try tomorrow
But for now brother i want to know its remove the apps. OK and what about bulid.prop? I need to edit it also. And after edit i don't want root anymore .after edit i need in tar format
I know you think I'm made but i know it's possible
Click to expand...
Click to collapse
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
Ok apps done
Bulid done
Now final thing need . repack in ext4 format
I'll check these things tomorrow
-spektor- said:
For build.prop maybe this app could help https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor sorry for lack of knowledge on this subject I've never had to repack a rom before.
Click to expand...
Click to collapse
brother did you found anything for repack ext4 img?
Mr Hassan said:
brother did you found anything for repack ext4 img?
Click to expand...
Click to collapse
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
-spektor- said:
Have you tried this guide? https://forum.xda-developers.com/showthread.php?t=1588461
Click to expand...
Click to collapse
yes but its for linux , and for window 99% unsuccessfully rates , have you try in window ? this ?
now i,m in next step if you have the time so kindly share your experience
https://forum.xda-developers.com/android/help/repack-img-giving-error-odin-invalid-t3577719
Hmmmmm ? I think you want to change the boot animation (white Verizon logo red background? ) if so your gonna need to either need to flash a pre-made zip with Flashfire (can't seem to get it to apply from twrp) or your gonna need to manually copy into the appropriate directory (mount system directory r/w copy then change permissions of the file you copied to 644 and reboot) presumably with a root explorer though doable from terminal
---------- Post added at 07:47 PM ---------- Previous post was at 07:29 PM ----------
-spektor- said:
Ok so I may have found a solution for you it requires a pc and to download a program. You'll need your rom and any apps you would like to insert into it. The program is as simple as right click and delete for any apps you want to remove. The program is made by a developer on XDA named "_Logie" here's the link to the Web page: http://m.tech.firstpost.com/news-analysis/how-to-add-or-remove-apps-from-a-custom-rom-101986.html and the link to the program is on there or here's the direct link: http://www.solidfiles.com/d/da2dd6335d/
This program compiles the ROM into a .zip if you have TWRP recovery you could do a backup of your previous rom before flashing your current one because you'll have to completely wipe every main partition before flashing new rom to ensure you don't run into problems
Edit: backup system, data, and cache because those are the ones you'll need to wipe also before wiping them just in case I would remove any password that locks your phone because if you try to flash a new rom and fails and your left with the recovery file it'll mess up the password, fingerprints will be forget and backup password will be unchangeable and will require a factory reset to be able to change it.
Click to expand...
Click to collapse
Try flashing with flasfire enabling the option mount system r/w and use common paths (probably not necessary but won't hurt) I have had difficulty getting anything other than ROM and gapps to apply from twrp but flashfire seems to work . I'm thinking its due to the fact that flashfire flashes after boot loader and then resets prior to os load.