Develop Bugs

How i can unrooting my HTC Hero?

Hello!
I am use this Tutorial to rooting my Hero: http://forum.xda-developers.com/showthread.php?t=543571
How i can unrooting my Hero? I think, its possible, because the boot.img dont replaced with a other rom...
I found this Command *thanks!*:
* adb shell mount /system
* adb shell rm /system/app/Superuser.apk (if you have it)
* adb push su /system/bin/
* reboot
Click to expand...
Click to collapse
.. the problem is, i havent the original su
Can someone upload the original su?
Do I need to change the rights?
*from Tutorial*
adb shell chmod 4755 /system/bin/su
Click to expand...
Click to collapse
Big Thanks! Nice Community!
*sorry, my english is very bad >.< xD*

My advice would be, keep reading. Page 5 or 6 IIRR has Dayzee's guide which is what I used to root mine, but IIRR she tells you how to unroot again

If you did a Nandroid backup first you could just restore from that?

@ak1ra1nblack: I dont found..
@badgaz: I haven't a backup...
I need the original su file and the original rights for
adb shell chmod 4755 /system/bin/su
Thanks!

Ok, Close please ~~

tur0kx said:
Ok, Close please ~~
Click to expand...
Click to collapse
did you manage to unroot it! IF so share with us the complete steps and link to original su file!

If someone can provide us with an original SU file or a changed back one (Maybe enlightener can help?) then I'll add it in the guide - I don't have it in there yet, though there is code to remove superuser.apk and repush it if it goes wrong which might be what the other poster was thinking about. I do think rooting state can be reversed if you did this method, so lets see if we can get an unrooted SU (or do we just have to remove su file altogether to be virgin again?)
Hugs to all - Dayzee

I just checked.
I restored my nandroid backup.
I booted the cm-recovery mounted /system.
and now in /system/bin there is no su.
I expected this already.
To unroot removing su and SuperUser.apk should be enough.
BR
phlo

Ok is there somebody that could please clarify on the specific steps to unroot the phone?
I don't like to guess at all with these kind of things for obvious reasons

Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot

tur0kx said:
Open Windows Console and connect Hero with PC
write this:
fastboot boot cm-hero-recovery.img
adb shell mount /system
adb shell rm /system/app/Superuser.apk
adb shell rm /system/bin/su
adb shell reboot
Click to expand...
Click to collapse
That is nice, should be in the wiki.
How about unrooting by flashing back backed up .img files? Witch file to restore? How?

[DEPRECATED][GUIDE] Temporary root your Desire Z

HTC Vision // Desire Z Temporary Rooting
1. Download this package: MegaUpload
2. Copy the content of the package in a folder called "temproot" in your SDCard root.
3. Execute this script:
Code:
#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cd /data/local/tmp/
chmod 755 *
./rageagainstthecage-arm5.bin
ps
4. Restart Terminal Emulator
5. Execute this script:
Code:
#!/system/bin/sh
/data/local/tmp/busybox killall rageagainstthecage-arm5.bin
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
/data/local/tmp/busybox cp /sdcard/temproot/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /sdcard/temproot/su /system/bin/su
/data/local/tmp/busybox cp /sdcard/temproot/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
Now your phone is temporairily rooted and you can even get root on adb.
Thanks to:
*- C-Skills for the exploit
*- Guys in G2 section for testing it.

Sweet
but what do we do to get full root access?

There is no full root yet for either this device or g2. You will see that later

M9x3mos said:
There is no full root yet for either this device or g2. You will see that later
Click to expand...
Click to collapse
excited
wonder if the "z" and G2 can use the same Recovery image and Roms..or wil it be like htc magic and My touch ?

G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.

kholk said:
G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.
Click to expand...
Click to collapse
any idea if the G2 is a test unit or retail unit? i want senseui (sad i know, but im a sucker for nice graphic)

Correction. The Desire Z rom currently be flashed to G2 but the PC10IMG.zip original G2 rom does work on the Desire Z

I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"

Anyone try overclocking it yet?

waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
Are there any errors?
Please provide more details, it's only a file copy...

kholk said:
Are there any errors?
Please provide more details, it's only a file copy...
Click to expand...
Click to collapse
Link is down kind sir. I found this one Droid2Root.rar from another forum.

waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
It gives you an axxs denied when you try that. says "cp: permission denied." I can't ls inside of /data either.

do changes persist?
If I do this temp root and install busybox or tether, will the changes be wiped out on restart?

"cp: permission denied." Yes this is the error code I get.
"export PATH=/data/local/bin:$PATH
$ $ #! /system/bin/sh
$ cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cp: permission denied
$"
That's exactly what it appears on the terminal.

I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?

The file is no longer available. Can someone repost it?
Thanks

Hmm, yep same problem, cp gives me a permission denied, and the folder /data is a system file seems like we don't have any access to it. on the example, seems like there's # instead of $ which means it has admin access, how did you get to that state? sorry android noob here :-\

stian230 said:
I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?
Click to expand...
Click to collapse
Actually no, and its covered in many threads, and I'm sure the op doesn't want the discussion started again.

There isn't any chip that will magically transform your HTC Vision in an airplane / automobile / house / cigarette industry.

script?
Could somebody help with packaging this as a script so we could re-root simply?

Cant get root! Help plz!

Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!

tranceonline said:
Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!
Click to expand...
Click to collapse
1 & 2 ...
Who can say? You could spend some time examining logcat and dmesg outputs but why? May as well just accept it went wrong and start again.
3.
You want this RUU file.
The most reliable method to flash it would be here. Make it into a pd98img.zip.
4.
After using the visionary r14 tool to temproot I then used this excellent tool to get permanent root. The tool can be used to get eng hboot s-off if you want it as well.
You should also get radio s-off using another excellent tool. Radio s-off is the single best thing you can do to protect yourself from rogue OTA updates which kill root.
5. If your phone explodes its not my fault.
I'm not sure why I'm helping a guy like you though. Fancy forking innocent children
EDIT: Just corrected my post slightly.

i'll try what u said.
I dont know why the rage command forked all the children
I am only thankfull, i did not have had to see that!!
so i am in the bootloader, first it says "no blablaimg.nbh" and so on, than it starts checking the pd98img.zip and after that, its back in the main menu of the bootloader and nothing happens

If you get stuck I'll try my best to help if I'm still around.

it doesn't ask me if i want to flash. first it loads when its says "Checking pd98img.zip" and a blue bar at the right upper corner starts loading. after that, it says "checking pd98img.zip"
when thats finished, nothing happens.
than i reboot my phone and everything is like before
it says "System UID Inconsistent" and i can press "I'm feeling lucky"
Edit: Just saw, that the browser is fully gone! no app in the list anymore!
Edit1: In the zip is an exe file? is this correckt? or is this file only for flashing through pc?
Edit3 LOL: i did a factory reset in the bootloader.
everything is back to stock and working fine now!

OMFG THATS A FU***ING JOKE!!
I did a factory reset to stock, configurated everything and what do my eyes see?
the superuser.apk! i tried SU in erminal and got SU rights! WTF???
how did THAT happen??
i dont know, but i have root now.
Tried to reboot and root stays permanent. This is ok for now i think.
Becaus i read that a Custom ROM don't gives u sooo much advantage, ill stay at stock with root for now. it runs fine and until it starts lagging to much or something else, i'll stay at stock ROM i think
Thank you very much for your help mox !

Ok, now there is another problem.
I have root, setcpu and terminal work fine. Titanium backup les too and says busybox is working too. Solo I wanted to use root explorer and delete some Stuff out of the /system/app folder. Things like amazon mp3 and so on. But I can't get read write rights in that folder. Why that? Can anyone help plz?
Sent from my Desire HD using XDA App

[GUIDE] How to Unroot Bell Desire Z

Hello,
I've had a few requests for help unrooting the Bell Desire Z for warranty purposes.
If you've noticed, there isn't a specific guide for us Bell users, while T-Mobile customers have like a dozen guides scattered around. I figured this out and I should share it.
The really tricky part was figuring out how to get rid of superuser.apk and also get s-on and Bell's CID in the right order, but it turns out it's simple haha. Unfortunately there was not guide for me, so I had to figure this out trial and error and piecing it together from other random posts. I'm not a dev/hacker (well, maybe now I am a novice hacker), so it was a big deal for me (lol) and I can relate to the frustration that comes from not having a good resource.
The exact build my phone shipped with was 1.34.666.5 and other phones may have shipped with other builds, but I've determined that the way Bell operates is that they send their phones to a 3rd party repair facility, and they don't check this (or don't care). However, they may still check whether or not the phone is rooted. So let's unroot it.
DISCLAIMER: Do your own research. I am not responsible for anything bad that happens to your phone after this point (but I will take credit for your success!! ). I used this method successfully and everything worked great. But proceed with caution. If you are unsure, do some looking around. CHECK YOUR MD5 SUMS! Easy MD5 is in the market, and is great.
0. If you have flashed a new radio, flash the old radio back. This one:
http://www.mediafire.com/?9cb8a7jwxob8o6r
NOTE: I'm leaving specific details out of this because if you don't know how to do this, that means you haven't done it before, and you don't need to do this step, and should probably avoid flashing new radios anyway.
1. Download this file:
https://rcpt.yousendit.com/1317004046/ea1de40db3968b867573327c903231bf
-unzip it, and place the folders in /sdcard/clockworkmod/backup/
(recovery will check the md5 sums for you)
2. Reboot into recovery (assuming you have the clockworkmod recovery).
-Do a factory reset (yes, you will lose all your apps etc if you didn't back up)
-Choose Backup/Restore, Advanced Restore, Stock DZ System, System.img
-Choose Backup/Restore, Advanced Restore, Stock DZ Boot, Boot.img
-Reboot
3. Download
http://dl.dropbox.com/u/15272013/Flash Recovery Files.zip
Unzip those files to the root of your sdcard.
PLEASE CHECK THE MD5 of recovery.img AFTER you have unzipped it and placed it on your sdcard!! Sometimes if you check an md5 on your pc and then copy it over, you could still have an error, and then you'll be in a bit of trouble!
md5 of recovery.img: id5d280af717f9afd7ce1c3285c129bc
4. Download the following file:
http://cmw.22aaf3.com/common/gfree_07.zip
md5 (of entire folder): 6916cf05b0805aeac9effdc1725aaa12
unzip and place the file gfree on the root of your sdcard
3. Install Terminal Emulator from the Market. This all needs to be done in the same Terminal Session. Type
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod 777 /data/local/tmp/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Now when you reboot your phone, you will have an unrooted phone, stock. For clarity, you have:
-Stock, Unrooted Bell ROM 1.34.666.5
-Stock, Matching Radio
-S-Off HBoot
-Proper Bell CID
-Superuser.apk nowhere to be found
The only loose ends are that flash_image will still be in your /system/bin and if you flashed the eng hboot, your hboot number may not match. I'm 99.9% certain nobody at the repair facility will look or care about it. Also, I'd prefer you avoid flashing your hboot, since that is singly the most risky thing you can do with your phone.
If anybody knows whether the flash_image binary works in /data/local/tmp, let me know and I'll edit the post.
Note: when you get your phone back, it will have the latest GB RUU on it. This will give you a bit of trouble re-rooting it. There is no way around having them flash the latest firmware on it, since it's the very first thing they do before they diagnose your phone.
Thanks to Football for information on shipped builds and mxpxboi for his rooted 1.34.666.5 nandroid files.
Cheers!
JT

jontornblom said:
3. Install Terminal Emulator from the Market. This all needs to be done in the same Terminal Session. Type
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod777 /system/bin/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Click to expand...
Click to collapse
Thanks for the help jontornblom. Quick question:
I am receiving the error message saying /system/bin/gfree no such directory.
Any Tips?

Merzennary said:
Thanks for the help jontornblom. Quick question:
I am receiving the error message saying /system/bin/gfree no such directory.
Any Tips?
Click to expand...
Click to collapse
Did you accidentally type a "/" after gfree?
Sent from my Nexus 6 like tears in rain.

good job - thx for this guide

jontornblom said:
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod777 /system/bin/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Click to expand...
Click to collapse
There are a couple of small typos in this code. In the second chmod there should be a space between "chmod" and "777". More importantly though, that second chmod should be on "/data/local/tmp/gfree" since that's where it's been copied
Sent from my Desire Z running CM7.

steviewevie said:
There are a couple of small typos in this code. In the second chmod there should be a space between "chmod" and "777". More importantly though, that second chmod should be on "/data/local/tmp/gfree" since that's where it's been copied
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
Thanks! Sorry about that =( I will edit the OP
Edit: okay, typos fixed. My apologies to anyone who ran into trouble because of this.
Sent from my Nexus 6 like tears in rain.

jontornblom said:
Hello,
1. Download this file:
...yousendit.com/1317004046/....3968b867573327c903231bf
-unzip it, and place the folders in /sdcard/clockworkmod/backup/
(recovery will check the md5 sums for you)
Click to expand...
Click to collapse
Could someone re-upload file from step 1?

Hi,
I too could use the file from Step 1. And there is a little urgency as I need to get my DZ back to stock as soon as possible.
Your help is appreciated...greatly!
Thanks.

ADB system remount FAIL

hi, quick question .
im trying to remount the system folder to R\W , but seems like no luck .
adb remount
*permission denied
adb shell
Code:
C:\android sdk\sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o rw,remount /system
mount -o rw,remount /system
[email protected]:/ #
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\android sdk\sdk\platform-tools>adb push C:\Users\HOME\Desktop\build.prop /sys
tem
failed to copy 'C:\Users\HOME\Desktop\build.prop' to '/system/build.prop': Permi
ssion denied
shell - fail
normal remount -fail
whats next.any suggestions?

cant do that yet, you need kernel with unsecure adb .

Helloworld294 said:
cant do that yet, you need kernel with unsecure adb .
Click to expand...
Click to collapse
Means I can't tweak my phone safely? (1 bootloop and I'm on stock again? )

subwoffer13 said:
Means I can't tweak my phone safely? (1 bootloop and I'm on stock again? )
Click to expand...
Click to collapse
You bootloop you're on stock again, with formatted /data/media of course.
EDIT: So I downloaded adb insecure from playstore by chainfire and it seems to work actually. Its $2 though.
Sent from my LG-D852 using Tapatalk

Helloworld294 said:
You bootloop you're on stock again, with formatted /data/media of course.
EDIT: So I downloaded adb insecure from playstore by chainf
ire and it seems to work actually. Its $2 though.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
Well, just bought it too.going to slepp right now, tomorrow hopefully I'll be able to push and pull files with adb.

subwoffer13 said:
Well, just bought it too.going to slepp right now, tomorrow hopefully I'll be able to push and pull files with adb.
Click to expand...
Click to collapse
Before pulling/pushing anything from system
run 'chmod 777 /system'
And before pushing/pulling any file chmod 666 the file and after dont ever forget to chmod 644 any system or data file after pushing or else you gonna end up in bootloop.
Sent from my LG-D852 using Tapatalk

Helloworld294 said:
Before pulling/pushing anything from system
run 'chmod 777 /system'
And before pushing/pulling any file chmod 666 the file and after dont ever forget to chmod 644 any system or data file after pushing or else you gonna end up in bootloop.
Sent from my LG-D852 using Tapatalk
Click to expand...
Click to collapse
.ok , i am a bit confused .i understand that every time im pulling or pushing i should fix the permissions. Bit what is the exact order ?
Shouldn't i just make sure the file im only pushing is 644 (rw-r-r)?
Lets say for example , i want to push stock "build.prop" to system .
What are the steps?

subwoffer13 said:
.ok , i am a bit confused .i understand that every time im pulling or pushing i should fix the permissions. Bit what is the exact order ?
Shouldn't i just make sure the file im only pushing is 644 (rw-r-r)?
Lets say for example , i want to push stock "build.prop" to system .
What are the steps?
Click to expand...
Click to collapse
Mount everything and do su and all that then chmod 777 /system
Then do the push "adb push 'source file location' /system/build.prop
Then do chmod 644 /system/build.prop
All done.
Sent from my LG-D852 using Tapatalk