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.
Related
hey im not sure if i am the right section but i tried to search but none of the solutions i have found worked please help..
I apologize if i am in the wrong section
dr690n said:
hey im not sure if i am the right section but i tried to search but none of the solutions i have found worked please help..
I apologize if i am in the wrong section
Click to expand...
Click to collapse
1) Download the following file: http://xeno.bemaniso.ws/Launcher2.apk
2) Place file on the root of your SD Card.
3) Reboot into recovery, same method that you use to flash roms.
4) Under Clockwork, select Partitions.
5) Mount System through Clockwork
6) Unplug and Re-Plug in USB Cord to device or else you won't be able to continue.
7) Open a command prompt or whatever you use to use ADB, type adb shell
8) cd /system/app
9) rm ADWLauncher.apk
10) cp /sdcard/Launcher2.apk /system/app/
11) exit
12) Reboot phone normally.
Next time you flash a rom use winrar or 7zip to open the zip (do not unzip or extract it!!!). Go to system/app/adwlauncher.apk and delete it. Then drag and drop whatever launcher you want to use. Flash the new rom and you're done.
KCRic said:
Next time you flash a rom use winrar or 7zip to open the zip (do not unzip or extract it!!!). Go to system/app/adwlauncher.apk and delete it. Then drag and drop whatever launcher you want to use. Flash the new rom and you're done.
Click to expand...
Click to collapse
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
Clockwork let us flash unsingned .zip files, there is an option and you choose if you want clockwork to check if the files are singed or not, and as long as you dont screw and move stuff where is not supposed to be your not gonna get an "installaion aborted" message.... i always do that to remove apps i dont use from system/app before i flash the rom and i've never had a problem
but back on topic... yeah you can do what the second post says, or if you dont want launcher2 just install the launcher you want to use from the market or sdcard if you have the apk, set it to deafult home app then go to recovery and do steps 4 to 9 and reboot, adw should be gone.
Once you get everything set up, resigning is simple. Since you don't have to resign with this method though, that task it pointless.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
I've never signed any of my rooms, ever. If you modify everything without unzipping it, using 7zip or the default package manager in ubuntu, there's no need to, regardless of what it is that you're replacing/modifying.
Hayzie said:
I thought stuff like that never works. ROM's and any other files such as apk's are usually signed. Therefore any modifications won't work and the package is corrupt unless you re-sign it. At least in my experience.
Click to expand...
Click to collapse
I just rename whatever I'm replacing it with to ADWLauncher and switch it out before I flash lol.
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?
Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
[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
Hi friends;
I have HTC M8 Marshmallow with Sense 7.
I rooted my device with SuperSU 2.65.
But;
I can't edit build.prob file in system folder.
I can't put apk and lib files to system->priv-app folder.
In fact ;
I edited build.prob file in system folder. (I used Root Explorer)
I put apk and lib files to system->priv-app folder.
But, after I rebooted device edited build.prob file returned original and
deleted apk and lib file that I put to system->priv-app folder.
Before these applications I mounted system folder R/W
Why did this happen?
How can i solve this?
musti35 said:
Hi friends;
I have HTC M8 Marshmallow with Sense 7.
I rooted my device with SuperSU 2.65.
But;
I can't edit build.prob file in system folder.
I can't put apk and lib files to system->priv-app folder.
In fact ;
I edited build.prob file in system folder. (I used Root Explorer)
I put apk and lib files to system->priv-app folder.
But, after I rebooted device edited build.prob file returned original and
deleted apk and lib file that I put to system->priv-app folder.
Before these applications I mounted system folder R/W
Why did this happen?
How can i solve this?
Click to expand...
Click to collapse
Flash disable WP mod. http://forum.xda-developers.com/attachment.php?attachmentid=3564071&d=1449168286
Thank you very much.
Now everything is OK
musti35 said:
Thank you very much.
Now everything is OK
Click to expand...
Click to collapse
Add [SOLVED] to the title, so that other people can find this solution.
Imotep95 said:
Flash disable WP mod. http://forum.xda-developers.com/attachment.php?attachmentid=3564071&d=1449168286
Click to expand...
Click to collapse
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
skshakeel said:
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
Click to expand...
Click to collapse
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Sent from my htc_m8 using XDA Labs
justinchao740 said:
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Click to expand...
Click to collapse
You can't edit system files while your device s-on,you need wp module or custom kernel with wp module to edit system
Some m8 roms have this module implemented ( if not all roms )
Sent from my HTC M8 using XDA Labs
skshakeel said:
I got same problem...Can I get this zip for HTC Desire 630 phone plzzz....
Click to expand...
Click to collapse
Hi
Earlier i see a post by @ckpv5 about adb manager Qtadb i can't find the post right now ( on mobile and it's hard to find )
https://qtadb.wordpress.com/download/
You can use this tool to remove system files
Reboot to twrp and mount system then connect the device with pc ( usb ) and start the tool from your pc
Give it a try
Sent from my HTC M8 using XDA Labs
justinchao740 said:
Because super su is system less root, you won't be able to edit the system files. I don't even know how that mod worked
Click to expand...
Click to collapse
You've got it wrong. Systemless root isn't the reason system is not writable. The same will occur with traditional root.
The system is write protected on this device (regardless of root method). You need the kernel mode to disable the write protection.
redpoint73 said:
You've got it wrong. Systemless root isn't the reason system is not writable. The same will occur with traditional root.
The system is write protected on this device (regardless of root method). You need the kernel mode to disable the write protection.
Click to expand...
Click to collapse
well thats what happened to me. I rooted with super su, it won't let me edit any build.prop or system files. But after i rooted with system root, it worked
Hi need help
Same problem in my device my device is not in too development
So I try to find solution on Google and find this thread..
Can I flash this file in my device my device is HTC desire 630 and also running in mm version.
So can I try to flash this file...???
vaibhav1 said:
Same problem in my device my device is not in too development
So I try to find solution on Google and find this thread..
Can I flash this file in my device my device is HTC desire 630 and also running in mm version.
So can I try to flash this file...???
Click to expand...
Click to collapse
No, it won't work. Kernels (and therefore kernel mods) are device specific. It won't work, and may harm your phone.
If the phone is rooted, you can try to mount system in a file explorer app, and apply the desired changes, to see if they stick (survive a reboot). Some folks have had success with that approach.
Be careful, and backup files accordingly. Or otherwise know how to return to stock, if anything goes wrong. Changes to system under root can result in unpredicted problems.
Further than that, I probably can't help; as I have no specific knowledge of your device.
redpoint73 said:
No, it won't work. Kernels (and therefore kernel mods) are device specific. It won't work, and may harm your phone.
If the phone is rooted, you can try to mount system in a file explorer app, and apply the desired changes, to see if they stick (survive a reboot). Some folks have had success with that approach.
Be careful, and backup files accordingly. Or otherwise know how to return to stock, if anything goes wrong. Changes to system under root can result in unpredicted problems.
Further than that, I probably can't help; as I have no specific knowledge of your device.
Click to expand...
Click to collapse
I try script but not working..
Thanks for you help