You must be rooted to do this
Using your favorite File Manager with root permissions:
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
That should be it.
gg AT&T carrier garbage
thanks for post!
Thanks. Everyone is crying for nothing, took only 30 sec to remove the boot screen.
Bjray said:
Thanks. Everyone is crying for nothing
Click to expand...
Click to collapse
Well it could have been much more difficult but yes there seems to be a great deal of fretting about this phone and AT&T. Actually about the N6 (Nexus in Name Only) in general.
that was easy as hell! thanks! now I just need to find out how to get rid of those AT&T ringtones.
edit: found em in the same directory, can just remove em.
Thank you for this. I had a feeling it couldn't be too hard to get rid of. I .bak'd all of those stupid at&t ringtones too.
P1 Wookie said:
Thank you for this. I had a feeling it couldn't be too hard to get rid of. I .bak'd all of those stupid at&t ringtones too.
Click to expand...
Click to collapse
I did the same as well.
P1 Wookie said:
I .bak'd all of those stupid at&t ringtones too.
Click to expand...
Click to collapse
There's an (earlier) AT&T un-customizing thread.
g33k3r said:
You must be rooted to do this
Using your favorite File Manager with root permissions:
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
That should be it.
Click to expand...
Click to collapse
Out of curiosity, is there anything else on the /oem partition? Can someone post a complete file listing or partition image? Are there any driver/binary blobs, or are those all in /vendor? I imagine a "format /OEM" function will be really handy to have in all custome recoveries going forward, as an easy way to remove bloat without rooting.
DA6030 said:
Out of curiosity, is there anything else on the /oem partition? Can someone post a complete file listing or partition image? Are there any driver/binary blobs, or are those all in /vendor? I imagine a "format /OEM" function will be really handy to have in all custome recoveries going forward, as an easy way to remove bloat without rooting.
Click to expand...
Click to collapse
The partition is empty on Sprint.
Sent from my Nexus 6 using Tapatalk
DA6030 said:
Out of curiosity, is there anything else on the /oem partition? Can someone post a complete file listing or partition image? Are there any driver/binary blobs, or are those all in /vendor? I imagine a "format /OEM" function will be really handy to have in all custome recoveries going forward, as an easy way to remove bloat without rooting.
Click to expand...
Click to collapse
Here is what was in mine:
/oem/lost+found/
(empty)
/oem/media/
/oem/media/ringtones/
/oem/media/ringtones/ATT_Catch_Me.mp3
/oem/media/ringtones/ATT_Firefly.mp3
/oem/media/ringtones/ATT_Play_On.mp3
/oem/media/ringtones/ATT_Stargazer.mp3
/oem/media/bootanimation.zip
/oem/oem.prop
oem.prop contains one line:
"ro.config.ringtone=ATT_Firefly.mp3"
The entire oem partition looks completely useless and should be safe to nuke.
Edit:
I emptied the oem partition entirely. Going to do a quick round of testing and make sure nothing is messed up and report back.
Editx2: back!
Everything is working great. The only thing I noticed is that the call ringtone was initially set to "Unknown ringtone" after first boot. It was probably set by oem.prop and then couldn't find it after that. Just changed it to a different tone, works great.
My accelometer stopped working, can anyone make a backup of the AT&T oem partition, or grab the files and send them my way. I would be greatly appreciative.
Nopcodex90 said:
My accelometer stopped working, can anyone make a backup of the AT&T oem partition, or grab the files and send them my way. I would be greatly appreciative.
Click to expand...
Click to collapse
Did you ever get this resolved?
Nopcodex90 said:
My accelometer stopped working, can anyone make a backup of the AT&T oem partition, or grab the files and send them my way. I would be greatly appreciative.
Click to expand...
Click to collapse
See this post in the Remove AT&T Carrier customization open thread for a backup file of the AT&T oem directory. Although I don't think that there is anything in that directory that would effect your accelerometer.
Quick question: I just ordered a Nexus 6 from AT&T, and when my 18 month Next period is over, how can I get the AT&T logo back on to the phone?
pyrogoggles said:
Quick question: I just ordered a Nexus 6 from AT&T, and when my 18 month Next period is over, how can I get the AT&T logo back on to the phone?
Click to expand...
Click to collapse
They won't notice it is gone, and probably wouldn't care if they did notice. I returned two phones through Next, all they did was a factory wipe, didn't check any settings.
pyrogoggles said:
Quick question: I just ordered a Nexus 6 from AT&T, and when my 18 month Next period is over, how can I get the AT&T logo back on to the phone?
Click to expand...
Click to collapse
as already stated. they wont care. i sent back my ATT HTC One m8 after converting it to GPE. They just care if its damaged and powers on.
Wait so just deleting the bootanimation.zip will fix the att boot screen?
Itzamistry said:
Wait so just deleting the bootanimation.zip will fix the att boot screen?
Click to expand...
Click to collapse
The OP in this thread is an unattributed lift from <remove-att-carrier-customization-thread>
Note the identical text.
1: Open /oem/media
2: Mount r/w.
3: Remove or rename the file bootanimation.zip
4: Reboot
Click to expand...
Click to collapse
Please read the original. Note that rebooting isn't required. It's only to verify you renamed the correct file.
Since I haven't rooted mine yet I wonder if I can do this or disable it using sideload? Any thoughts?
Related
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
bigrushdog said:
Just a quick heads up. Moto was handing out DMCA notices on sysdumps. You may wanna save it for those who make it to #xoom on freenode.
Click to expand...
Click to collapse
Moto can suck an egg...will post link on my site :-D
Feel free to post the link on irc...
teamdefuse.com
Angdroid said:
Click HERE
Working on trying to get some deodex love going...
Just got Xoom WiFi tonight, let me know what I can do to help out the xoom wifi community.
Click to expand...
Click to collapse
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
ericdabbs said:
I am curious. How were you able to extract the stock system dump image for the wifi version? Could you put down instructions since I am trying to learn these things.
Click to expand...
Click to collapse
Install latest moto drivers
Install Android SDK
Enable USB Debug in Xoom settings
Open command prompt
Create new directory
CD to new directory
At command prompt type: adb pull /
files will be dumped to current path of command prompt
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
jwtyler said:
I Got the one (well, couple a clicks) root and unroot covered. You can check that one off the list. Thread open over yonder if you want to give it a spin... I am just uploading the newest version that one click updates to HRI66.
Click to expand...
Click to collapse
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
1 is being worked on...NVM...Check out jwtyler one click root thread.
2 & 4 Going to try the same method that was used for Droid2 and DroidX. Create module for OC. I have not had time yet to look at kernel but I see someone is already creating kernels so should be able to do it from kernel with multiple settings; not sure if kernel behaves same way as it does in Droid.
3 Not sure if bootstrap (clockwork recovery) is available yet for Xoom WiFi but if it is just make a backup before you mod anything.
Not sure what you are talking about with 5 and 6 ... I am a Xoom noob, only been out of box for a couple of hours
ericizzy1 said:
good, will be looking for it. NOW, an easy way to overclock to 1.5 would be wonderfull...
Click to expand...
Click to collapse
Sweet
Drop me a line if you want to try to bang out some stuff together...
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
ericdabbs said:
Thanks Angdroid for the system dump. I downloaded a copy of the system dump for kicks. I will keep it on my hard drive in case anyone loses it and needs a backup copy.
Hopefully we can create a stock boot.img soon for us wifi owners in case something goes wrong or need to return it to factory state. It looks like from the system dump we have access to the stock bcm4329.ko wifi driver.
Click to expand...
Click to collapse
Any word on the stock boot.img?
fabian29906 said:
Any word on the stock boot.img?
Click to expand...
Click to collapse
I am not a developer. I just meant a community as a whole come up with the files for the stock boot.img.
Still no word from Motorola of providing the stock boot.img for the wifi Xoom.
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
sausalito said:
Do you think it's possible to extract languages in Wifi firmware to flash 3g xoom?
Or flash with entire wifi firmware?
Click to expand...
Click to collapse
What do you mean? are you talking about the ./system/vendor/firmware/fw_bcm4329.bin
I just compared the two system images for both devices
fw_bcm4329_mfg.bin is the only file with a matching checksum..
I gotta run.. otherwise i'd check the version with a hex editor..
I doubt you're talking about the wifi firmware anyways..
ericizzy1 said:
1. one click root and unroot
2. safe way to over clock
3. a way to relock the xoom and bring to factory default
4. overclocikng
5. voodoo color fix
6. voodoo sound fix
lets start with that
thanks
Click to expand...
Click to collapse
Ya! A color calibration app would be awesome!
Azrael X 4.0
100mbit:
http://gititbit.ch/xRx3 - Xoom_Wifi_3.0.1.zip
That's what I did for this image. http://www.mediafire.com/file/2fknnmy6nw6i19n/StockWiFiSystem.zip
Note, you need to be able to mount a YAFS2 filesystem to read the contents.
Blades said:
I don't think the adb pull way is the best way at it.
Creating an actual image using dd will retain symlinks and mod perms (not owners).. but it also won't dump a bunch of tiny >1kb files on your computer (whose cluster size may be over 4kb).. plus you can mount it as a loop device..
adb shell
# busybox dd if=/dev/block/platform/sdhci-tegra.3/by-name/system of=/mnt/sdcard/system.img
and then if you want
adb pull /mnt/sdcard/system.img
but I wouldn't.. just using the mtp interface is faster..
Click to expand...
Click to collapse
Sent from my Xoom using Tapatalk
can someone post the 3.1 wifi-model USA system
(i need build.prop)
Project Cheesecake
CAUTION, ACCIDENTAL FLASHING OF A DOWNLOADED BUILD MAY END UP ON A HARD BRICK. YOU'VE BEEN WARMED.
Cant get any simpler than that, today we all got to work together and find as many international builds as possible in the test servers before they are remove.
Getting into the test servers is actually very very simple!Requirements!
You need to be on the latest android for your distributor.
(bell, telstra, tmobile uk, orange, etc)
You need to be rooted
(and must own root explorer.)
You also need Tenfars Bootstrap CWM.-How can i search the test servers.-
(one of these steps will have you erase your data, back up if needed)1. Download the file here. (cavalynts test cloud setup)
2. Open the zip and extract the files into your sdcard or internal memory
3. Using root explorer move those files into their correct places (just follow folder setup, where they came from is where they go)
4. Reboot into CWM and wipe data, and cache. (the warning).
5. Now reboot, and when the setup screen appears, press the menu key (the one all the way to the left) and set-up your wifi
6. in the same menu all the way to the right there will be a magical option "Set up Cloud"
7. Open that optin pick a cloud, and then follow the set up accound process like normal (do not use your real names emails or password, doh!)
A list of servers and whats been found.
Master-lab.blurdev.com
HKTW(dl), 45.0.7(dl orange uk)
master-demo.blurdev.com
master-dev.blurdev.com
master-qa1.blurdev.com
master-qa2.blurdev.com
4.5.40(dl att), 45.2.12(dl bell)
master-qa3.blurdev.com
4.5.91(dl att)
master-qa4.blurdev.com
master-staging1.blurdev.com
master-sdc1.svcmot.com
master-blur.svcmot.com
33.99(not dl bell)
master-homer.blurdev.com
master-bart.blurdev.com
master-lisa.blurdev.com
master-maggie.blurdev.com
master-marge.blurdev.com
master-bqa1.blurdev.com
master-bqa2.blurdev.com
testcloud01-sdc1.blurdev.com
DO NOT INSTALL WHAT YOU DOWNLOAD, HIT THE INSTALL LATER. THIS IS NOT A COMPETITION TO GET ON LATEST BUILD QUICKER. BE CAREFUL OR YOU WILL HARD BRICK.
Read next post to learn how to retrieve it and sent it to US over at webchat.freenode.net #moto-atrix
Stop pressing thanks and start joining in the download fest.
How to retrieve the OTA safely.
1. Once the OTA finishes downloading, it will ask you if you want to install
(press INSTAL LATER)
INSTALLING THIS MAY END UP IN A HARD BRICK, AS IN KAPUTS YOUR PHONE DOES NOT WORK, AS IN YOUR PHONE IS BROKEN FOREVER, AS IN F*CK THE PHONE HARD BRICKED.
2. Open Root Explorer and go to the cache folder in the root of your phone and retrive the ATA .zip
(it be easy to know which of all the things in there is the ota.)
3. Move it to your sd card and from there to your pc.
4. sharing it with the devs. Please upload this on Multiupload, and either sent me the PM with the link, or PM us on IRC.
THERES A MILLION WARNINGS BUT THERES ALWAYS SOMEONE WHO DOES SOMETHNG STUPID AND CRIES. DONT ALLOW THIS TO HAPPEN TONIGHT
Is step 4 factory reset? Just checking
Is there any way AT&T users can help out? Just go through the same process?
Sent from my MB860 using XDA Premium App
yes it is, be careful and get goodies
Magnetox said:
Is step 4 factory reset? Just checking
Click to expand...
Click to collapse
yes but is a bit more complicated, you can simply flash the zip up there on 183. and then get a build.prop for any version and replace yours with it. now to download its the tricky part
you are going to needs to be rooted
and once the download starts you are gonna want to open a shell
abd shell
su
cd /cache
trail - -(not sure what options they where) file.zip >/destination/file.zip
is easier to let them do it themselves.
Sinful Animosity said:
Is there any way AT&T users can help out? Just go through the same process?
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
EDIT: samcripp beat me to it...
might wanna toss this in your OP somewhere
http://forum.xda-developers.com/showthread.php?t=1164323
also, where does meta-inf go? there is no meta-inf folder to overwrite so should I just plop it in anyways? only system was an overwrite
I'm on retail france 2.1.1, during setup it does not give me a cloud option.
I've installed the file through CWM and done a factory reset. Any ideas?
jaysnip said:
I'm on retail france 2.1.1, during setup it does not give me a cloud option.
I've installed the file through CWM and done a factory reset. Any ideas?
Click to expand...
Click to collapse
You cant install through CWM you have to place them in manually as in the instructions
if you have root explorer go over to your files and on top at the right theres a yellow button with read 0, click it and it will say write 1, then do it again
it remounds your system
jaysnip said:
I'm on retail france 2.1.1, during setup it does not give me a cloud option.
I've installed the file through CWM and done a factory reset. Any ideas?
Click to expand...
Click to collapse
doing the back-up now. on bell. going to start from the bottom of the list and work my way up I assume I only upload if I find a different file than what you have?
Where does the META-INF folder go then? In root? I guess what I want to know is where those certs are supposed to end up.
y2whisper said:
doing the back-up now. on bell. going to start from the bottom of the list and work my way up I assume I only upload if I find a different file than what you have?
Click to expand...
Click to collapse
if you find something like 2.3.3 that is particularly interesting because that is where we found our unlock from att (2.3.4 did not have this). I am talking in android versions not att/bell specific. Of course upload anything unique and we will inspect it to see if there is an unlockable bootloader inside =D
Come on guys we need to bring more attention to this! i will try the french SBF but it would help if someone could send me the Build.prop because i would rather not stray from the bell firmware, but if i have to i will to help out.
jaysnip said:
Where does the META-INF folder go then? In root? I guess what I want to know is where those certs are supposed to end up.
Click to expand...
Click to collapse
this file does not go in ours, those folders hold the script
Ratchet556 said:
Come on guys we need to bring more attention to this! i will try the french SBF but it would help if someone could send me the Build.prop because i would rather not stray from the bell firmware, but if i have to i will to help out.
Click to expand...
Click to collapse
if you are in linux you can download any of the sbf, and sbf_flash
and do the following comand to split it sbf_flash -x sbf.sbf
the simply mount the image
perfect will do. I also am not sure where to put the META-INF folder. just putting it under / didn't seem to work
Ratchet556 said:
Come on guys we need to bring more attention to this! i will try the french SBF but it would help if someone could send me the Build.prop because i would rather not stray from the bell firmware, but if i have to i will to help out.
Click to expand...
Click to collapse
I have it. pulling it up.
This solution works for anyone that doesn't want to root their device.
however required a unlocked boot loader.
you can use TWRP file manager to replace below files. (hence not needing root).
(or someone can kindly create a flashable)
I have recomplied the power.shamu.so (replacing the missing codes from https://android.googlesource.com/device/moto/shamu/+/2084f7d0cf50baf394759d175bc28ad80cf7cace^!/ )
What this does is also re-enable the double-tap to wake.
to use,
backup a copy of
/system/lib/hw/power.shamu.so
then copy the attached power.shamu.so to /system/lib/hw/
change the permission of power.shamu.so to 0644
then boot your device. volia... you now have double tap to wake again.
Note. this has been tested with my own nexus 6.
Thanks. I think this would be better in themes n apps section though.
Thank you Sir! I'm going to remove the app and try this on Elix-R!
EDIT: Works great! Thank you again.
Which permissions are 0644?
smalltownbird said:
Which permissions are 0644?
Click to expand...
Click to collapse
User: R,W
Group: R
Other: R
Thanks that's what I thought I just wanted to make sure
Can I just flash the zip file that's in the beginning of the thread? Also would I need to re-install after wiping and flashing different roms or will it stay?
Figured it out.
No Worky on Slim
mr_clean5953 said:
No Worky on Slim
Click to expand...
Click to collapse
Working fine here. You probably never set permissions
suzook said:
Working fine here. You probably never set permissions
Click to expand...
Click to collapse
I did. And triple checked it
mr_clean5953 said:
I did. And triple checked it
Click to expand...
Click to collapse
Strange working here on beta 8
suzook said:
Strange working here on beta 8
Click to expand...
Click to collapse
I redownloaded and reloaded the file and its working fine now
Awesome
.....working like charm....
Sent from my Nexus 6 using XDA Free mobile app
Working great here!!! Thank you.
Stock ROM...
Sent from my Nexus 6 using Tapatalk
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
BeansTown106 said:
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
Click to expand...
Click to collapse
You can do it from recovery which has system access even if the ROM doesnt have root privileges.
What I am wondering though is if you can use fastboot to simply boot recovery without flashing it, and would you be able to do that command without unlocking the bootloader? Or does booting a custom system file require it to be unlocked?
BeansTown106 said:
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
Click to expand...
Click to collapse
Idea is just like rooting.
You need to some how replace the power.shamu.so once, and thats it.
Some people dont like phones to be rooted, as some software are really particular with root such as 'good for ent' or banking app. Idea is so that these people can still have doible tap to wake.
Hence you require a unlocked boot loader.
Eg, i guess i can also repack the file to a flashable zip, then user can just flash from recovery.
Note, i found that your tap needs to be quite consistant (can't be too fast or slow. There is a specific window)
what about pocket detection? (proximity sensor)
antiochasylum said:
what about pocket detection? (proximity sensor)
Click to expand...
Click to collapse
Don't think there is such feature. One you Mentioned is ambient display which I choose to switch off. As I believe it might detect lots of false pick up.
Awesome! Works great!
Stock rom
Sent from my Nexus 6 using Tapatalk
I would like to change the boot animation on my Verizon G4, but I'm scared to without TWRP. I was curious if any of you braver souls have done so successfully yet?
Lightshield said:
I would like to change the boot animation on my Verizon G4, but I'm scared to without TWRP. I was curious if any of you braver souls have done so successfully yet?
Click to expand...
Click to collapse
You won't be able to without a recovery
Ah, ok. I thought all you had to do was use something like Root Browser to move a new Bootanimation.zip to the System Media folder.
Good thing I asked first!
Lightshield said:
Ah, ok. I thought all you had to do was use something like Root Browser to move a new Bootanimation.zip to the System Media folder.
Good thing I asked first!
Click to expand...
Click to collapse
Not sure if it works that way, but I def wouldn't try it haha
well.. worst case.. you cant boot back into system and have to reflash the system.img thru download mode. keep the rooted system.img on internal sdcard for any risky changes. then ur only a few minutes away from a fix. but as long as u set the proper permissions on the files you're replacing it should go ok and you wont even run into this worst case situation.
with that said.. I don't own the vzw model so I havent swapped theirs out specifically.. but I have changed my boot ani on my h815. if you're not sure which permissions you need to set on the file... just view the permissions of the original file thru rootexplorer/es file explorer... then set those back to your new file afterwards.
Lightshield said:
I would like to change the boot animation on my Verizon G4, but I'm scared to without TWRP. I was curious if any of you braver souls have done so successfully yet?
Click to expand...
Click to collapse
Just rename the old bootanimation zip to .bak move the one you want into place and change permissions to 644 in root browser.
Unless the boot loader checks file sizes and signatures which I doubt for the boot animations.
Yeah, I tried it yesterday. It bootlooped twice then booted with no bootanimation. YMMV
bilbobrian said:
Yeah, I tried it yesterday. It bootlooped twice then booted with no bootanimation. YMMV
Click to expand...
Click to collapse
Your permissions were wrong you want them to be 644.
I used solid explorer on my T-Mobile unit to remove that gods awful boot sound and install the nexus boot animation, forgot to set permissions and that's what happened boot without animation
godsfilth said:
Your permissions were wrong you want them to be 644.
I used solid explorer on my T-Mobile unit to remove that gods awful boot sound and install the nexus boot animation, forgot to set permissions and that's what happened boot without animation
Click to expand...
Click to collapse
i did the same. the goddamn at&t poweron.ogg is annoying as hell.
Yeah, I have liveboot running, and a wireframe spinning android dude animation in the background. Little more interesting than the default.
I got brave and decided to try out some boot animations I downloaded the other day from a G3 Boot Animation thread.
I moved them with Root Browser and made sure to set permissions to 644 and it worked!
For some reason though the one I download of the Super heroes that change? Maybe you know what I'm talking about. Had it on Nexus 6 and it was fast and fluid. On the G4 here it was in slow motion and stuttering. Don't know if that's a fault of the -G4 or the source file though.
Bottom line, changing the Bootanimation.zip manually works just fine as long as you remember to set the permissions.
Worked for me too
Dennisg34 said:
Not sure if it works that way, but I def wouldn't try it haha
Click to expand...
Click to collapse
Sure you can. I did just that on a rooted AT&T version. Used Root Explorer, renamed existing file to .orig. Copied new file from SD card. rebooted, and boom.
Changed my bootanimation the minute we got root. Using the stock LG instead of the Verizon one.
slick_shoes said:
Changed my bootanimation the minute we got root. Using the stock LG instead of the Verizon one.
Click to expand...
Click to collapse
Mind posting it? Thanks.
Worked great. I use the LG G3 Matrix Boot Animation found here on xda. Couldn't find any shutdown Animation. Renamed BOTH (bootanimation and shutdown Animation from zip to zip.back). Works great. No Shutdown Animation anymore is just fine with me! [emoji1]
Sent from outer space using telepathy
---------- Post added at 01:50 PM ---------- Previous post was at 01:47 PM ----------
Lightshield said:
I moved them with Root Browser and made sure to set permissions to 644 and it worked!
For some reason though the one I download of the Super heroes that change? Maybe you know what I'm talking about. Had it on Nexus 6 and it was fast and fluid. On the G4 here it was in slow motion and stuttering. Don't know if that's a fault of the -G4 or the source file though..
Click to expand...
Click to collapse
Did you remember to set the Stick Bit? If not, does it help with the stuttering?
Sent from outer space using telepathy
Not sure what the Stick Bit is.
Set/change the permissions... how do you do that? I have and use root explorer, first thing i did with root was remove a lot of UI sounds entirely (.bak for their original files) includingthe startup sounds.
d00mz said:
Sure you can. I did just that on a rooted AT&T version. Used Root Explorer, renamed existing file to .orig. Copied new file from SD card. rebooted, and boom.
Click to expand...
Click to collapse
Dont forget to set the permission to 644 also.
roosta said:
Set/change the permissions... how do you do that? I have and use root explorer, first thing i did with root was remove a lot of UI sounds entirely (.bak for their original files) includingthe startup sounds.
Click to expand...
Click to collapse
In root explorer long press the file and in the pop up select permissions. 0644 looks like a backwards 7 in the checkboxes.
20degrees said:
Mind posting it? Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3168785
Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT
This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.
How is this any easier than the original method....if anything this requires even more work
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.
psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP
Can this be used to inject Xposed as well for those of us with locked BLs.
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.
psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!
Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?
kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.
The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem
hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx
How to calculator extractly bs/seek/count ?
Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013
optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.
ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys
djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.
hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?