Related
Hey gius Im trying to reboot via terminal but I cant seem to get it to work. Keep getting "Nor premited!" error.
I tried with both commands and am using a rooted G2 with stock rom.
su reboot - same error
su reboot now- same error.
any ideas? I know there are apps to do it but why is it not working via terminal?
Any reason why you can't just hold the button in and press reboot?
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
ohgood said:
$ su -
# shutdown -r now
it shoulda outta do it then
for just turning off:
# shutdown -h now
Click to expand...
Click to collapse
Hmm Tried that right now and it says shutdown: not found.
I'm getting the same error! I only tried terminal when Gscript Lite gave me a "not permited". Don't know if it's related, but terminal always starts with $ rather than #. The weirdest part is that it DID work through ADB.
I'm S-OFF, root verified. Has anyone else seen this? I've been searching the forums for a while now...
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
I get busybox: not found, but since I initially thought it was a busybox issue, I have already updated busybox. Per Titanium Backup, I have version 1.18.4-Titanium. Could it be the titanium busybox?
PanCubano said:
Try
$ su
# busybox killall system_server
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
Having a similar problem with rebooting from terminal "not permitted", I am using Virtuous Unity,and my phone is rooted etc,anybody having any joy getting reboot from terminal working?double checked busybox permissions and are RWX so whats going on???????????????????
Ok restored my nandroid backup of CM7 and reboot from terminal works so for the problem is connected to Virtuous Unity.
got it ! command is:
$su
#reboot -f
hay presto!!!!!!!
EDIT BUT when using a gscripts reboot doesnt work???????????
I have to use the command busybox killall system_server in the script????
I dont get it,what is the problem !!!!!!!!!!!!!!!!
xsteven77x said:
Any reason why you can't just hold the button in and press reboot?
Click to expand...
Click to collapse
This.
Sent from Space using Tapatalk Pro
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
bombadier said:
I know I could, just trying to understand the android system,how it works and why the reboot command works on CM 7 but not on Virtuous Unity, the search for a solution continues...........................
Click to expand...
Click to collapse
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
mjasmin said:
I had the same problem on rooted stock, and it has since gone away since I put on CM7. The reason is that it is not just reboot that didn't work. Almost no scripts would run either, and those can be quite helpful. I believe it's a symptom of something larger, but I can't quite place my finger on what.
Click to expand...
Click to collapse
I can get reboot -f which works but I have to use busybox killall_server to get it work from a script,have tried a few things but literature on the subject is pretty sparse,its not so important but would still like to understand the whole process, but I seem to be in the minority trying to solve this.......
Why I have to use reboot -f on Unity where reboot will do on CM is a mystery,have found a file that seems to define functions on Unity(virtuous-functions.sh), have tried adding REBOOT="$BUSYBOX reboot" to this but doesn't help.
reboot -f it is then!
I'm out of ideas. I've asked before but got no where. I figured a picture may help. I can root and get all the way to cm 7.0.3 but anything 1.2 update related fails. I've tried using the cwm flashable update but that fails too.
The pic is from a fresh 1.0. (I've tried 1.1 also.)
Sent from my DROIDX using XDA Premium App
USE THIS http://forum.xda-developers.com/showthread.php?t=1000957 with a sandisk 8 gb class 4 chip.....
Call it a day.... use CM7.1 RC, its very stable.... if you need to update to nightlies, its simple as just copy the downloaded file onto the external memory card.
Yeah that is a last resort. I plan on giving that nook to my brother who is android illiterate. How did everything get borked anyway?
I bypassed the registration and my nook info looks like this
Sent from my DROIDX using XDA Premium App
OH CRAP.... looks like some sort of internal corruption....
Do a complete wipe......
THEN Do the SDCard install...
It's seemless to the user... THere is no bootup screen or anything... The nook will automatically boot to the sd first.... so he won't need to know anything...
if he is REALLY not too literate, then he can just pull the sd, and it boots into the nook.
Ok....I'm not sure what kind of SD card I have... it just says micro SD hc 4gb with a circle with a 4 in it.
So I'm assuming its a class 4 SD card...not sure the brand though
Sent from my DROIDX using XDA Premium App
oman0123 said:
Ok....I'm not sure what kind of SD card I have... it just says micro SD hc 4gb with a circle with a 4 in it.
So I'm assuming its a class 4 SD card...not sure the brand though
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
It will work fine..... class 4 is good enough
Also if anybody knows a fix for whatever happened I would much rather do that than running off of sd
Also Thanks for the help slider. At least I know he will at least have the current cm if I can't find a fix
Sent from my DROIDX using XDA Premium App
oman0123 said:
Also if anybody knows a fix for whatever happened I would much rather do that than running off of sd
Sent from my DROIDX using XDA Premium App
Click to expand...
Click to collapse
Did you try to wipe it? under settings?
slider2828 said:
Did you try to wipe it? under settings?
Click to expand...
Click to collapse
Yup wont let me. Says: deregister device failed with error: user not registered (E_NOT_REGISTERED)
Sent from my DROIDX using XDA Premium App
Looks like your "ROM" got corrupted... it is a partition (/dev/mmcblk0p2) that is mounted r/w as /rom
Check and see if you have partition mmcblk0p3 and if rombackup.zip is in there...
Boot off CWM bootable uSD... then try the following:
adb shell mkdir /tmp
adb shell mount /dev/block/mmcblk0p3 /tmp
adb shell ls /tmp
if rombackup.zip is there... you're fine... we can fix it.
Wow I've been rooting for about 3 years and have never ever used adb. Crazy right? Can anybody point me in the right direction ?
Sent from my DROIDX using XDA Premium App
can that be done in terminal emulator or do I gotta go and install adb and whatever else on my computer?
term emulator would work.
DizzyDen said:
Looks like your "ROM" got corrupted... it is a partition (/dev/mmcblk0p2) that is mounted r/w as /rom
Check and see if you have partition mmcblk0p3 and if rombackup.zip is in there...
Boot off CWM bootable uSD... then try the following:
adb shell mkdir /tmp
adb shell mount /dev/block/mmcblk0p3 /tmp
adb shell ls /tmp
if rombackup.zip is there... you're fine... we can fix it.
Click to expand...
Click to collapse
Ok I tried adb shell mkdir /tmp and i get mkdir: cant create directory /tmp: read only file system.
Tried adb shell mount /dev/block/mmcblk0p3 /tmp, it fails and says no such file or directory.
does this mean if I want the newest versions of cm7 I gotta do it off sd?
Arrrgh been trying all night. I hope there's still a way and its not completely borked
Sent from my DROIDX using XDA Premium App
oman0123 said:
Ok I tried adb shell mkdir /tmp and i get mkdir: cant create directory /tmp: read only file system.
Tried adb shell mount /dev/block/mmcblk0p3 /tmp, it fails and says no such file or directory.
does this mean if I want the newest versions of cm7 I gotta do it off sd?
Click to expand...
Click to collapse
You could still run CM7 off of EMMC... we're just trying to salvage your device specific information if there's any hope... which I truly think there is.
oman0123 said:
Arrrgh been trying all night. I hope there's still a way and its not completely borked
Click to expand...
Click to collapse
Sorry... was at work... didn't have a chance to reply...
try adb remount
before the other steps above... if you get an error then you will need to
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
One of those two should work from CWM bootable uSD... then the steps I listed above will work... IF you have the rombackup.zip file... we'll help you through fixing your issues.
DizzyDen said:
You could still run CM7 off of EMMC... we're just trying to salvage your device specific information if there's any hope... which I truly think there is.
Sorry... was at work... didn't have a chance to reply...
try adb remount
before the other steps above... if you get an error then you will need to
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
One of those two should work from CWM bootable uSD... then the steps I listed above will work... IF you have the rombackup.zip file... we'll help you through fixing your issues.
Click to expand...
Click to collapse
I got the same error messages after the remount but the "adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system" seemed liked it work. it didnt say anything though
It won't give you a message saying it was successful... just try the other commands to see if you have backuprom.zip on partition 3. If its there... we can fix the issues... if not.. we have to make stuff up to fix it
You can do the same thing for partition 2 (where the device specific stuff is stored unzipped) by creating directory called tmp2 and mounting /dev/block/mmcblk0p2 to it... in that one 3 specific files you're looking for are:
DeviceID
MACAddress
SerialNumber
Those are plain text type files (but not DOS or windows formatted.. so you can view them, but don't edit them in notepad)
DizzyDen said:
It won't give you a message saying it was successful... just try the other commands to see if you have backuprom.zip on partition 3. If its there... we can fix the issues... if not.. we have to make stuff up to fix it
You can do the same thing for partition 2 (where the device specific stuff is stored unzipped) by creating directory called tmp2 and mounting /dev/block/mmcblk0p2 to it... in that one 3 specific files you're looking for are:
DeviceID
MACAddress
SerialNumber
Those are plain text type files (but not DOS or windows formatted.. so you can view them, but don't edit them in notepad)
Click to expand...
Click to collapse
Ok you are gonna have to help me with that. I wouldnt even know where to begin. We all gotta push our limits right? haha
Check your PM... give me a call if you want.
I gave you some bad commands.... this should work:
adb shell mount -O remount /remount, rw /dev/block/mmcblk0p5 /system
adb shell mkdir /system/tmp
adb shell mount /dev/block/mmcblk0p3 /system/tmp
adb shell ls -l /system/tmp
then
adb shell mkdir /system/tmp2
adb shell mount /dev/block/mmcblk0p2 /system/tmp2
adb shell ls -l /system/tmp2
OR
adb shell
mkdir /system/tmp
etc.
etc.
Since you have the rombackup.zip on mmcblk0p3 try this...
extract attached file... then run the resettofactory.cmd file... it will copy the BootCnt file to /rom and make it think its on 8th failed boot.
after a few hours in Irc with fellow continuiniuumers. i tested a gps fix on locking gps in navigation.
Special thank youz:
Imnuts (for source file and cmds)
Samuelhadams (for proof on test)
Logan302 (adb help)
what you need:
adb installed (and working )
gps.conf: here
in adb enter these cmds:
adb shell mount -o remount,rw /dev/block/stl9 /system
adb push gps.conf /system/etc
adb shell reboot
or
what you need:
any file manager app that mounts the system r/w (read write)
aps.conf on sdcard
copy gps.conf from sdcard and go to /system/etc folder,
click mount r/w button or however you are mounting system r/w
paste
reboot
or
flash via CWM: Here
Gps was broken? With ec07 or ec03?
Sent from my SCH-I400 using XDA App
abby_nitewolf said:
Gps was broken? With ec07 or ec03?
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
There were issues with gps unable to lock after the phone had been on for awhile.
Sent from my SCH-I400 using XDA App
The link is down
trailblazer101 said:
The link is down
Click to expand...
Click to collapse
Do you need it?
trailblazer101 said:
The link is down
Click to expand...
Click to collapse
Updated sorry
Sent from my SCH-I400 using xda premium
my gps was working fine on ec07
Bierce22 said:
my gps was working fine on ec07
Click to expand...
Click to collapse
It seems to be a hit or miss thing. Minw does too. Some people have issues, though.
I'm not here for a long time. I'm here for a good time. To hell with the red wine. Pour me some moonshine. - King George
ADB help
Hey, just a few questions. I'm brand new to ADB tools.
I got my cmd prompt to show me the serial of my device using adb devices. Im sure this means my adb tools are working. Ive only installed SDB tools and platform tools.
Do I need to download the 2.2 tools?
The problem is when I type in the first cmd i get a operation error.
2nd question is how do I get all of your gps.config code into the cmd prompt. Do I place the file somewhere on my computer for it to be recognized in your second cmd step.
Thanks in advanced.
minirome said:
Hey, just a few questions. I'm brand new to ADB tools.
I got my cmd prompt to show me the serial of my device using adb devices. Im sure this means my adb tools are working. Ive only installed SDB tools and platform tools.
Do I need to download the 2.2 tools?
The problem is when I type in the first cmd i get a operation error.
2nd question is how do I get all of your gps.config code into the cmd prompt. Do I place the file somewhere on my computer for it to be recognized in your second cmd step.
Thanks in advanced.
Click to expand...
Click to collapse
You can push manually with a file manager. Its in op also.
Also the GPS. Conf is a file.
Sent from my SCH-I400 using xda premium
Why am I getting the operations error anyways? Should I be working off of tools or platform tools?
Sent from my SCH-I400 using XDA App
Ive tried a lot of different ways to get it to work and I think ive gotten to the point where it might be something else other than my commands. I just get a mountperation not permitted. The following is an example of what I typed. The $ sign was created after I typed in adb shell.
1 "adb shell
2 $mount -o remount,rw /dev/block/stl9 /system
3 mountperation not permitted"
Tell me I did something wrong.
You need to "su" before you try and mount -_-
Sent from my SCH-I400 using xda premium
trailblazer101 said:
You need to "su" before you try and mount -_-
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
I messed around with that for awhile and I think I got a little further. I seem to still get a little stuck after I mount.
1. /android-sdk/platform-tools>adb shell
2. $su
3. #mount -o remount,rw /dev/block/stl9 /system
4. mount -o remount,rw /dev/block/stl9 /system
5. #
On line 4 the cmd prompt just spits that back out at me and it ends up back at # again. How do I know it mounted and how do I begin the pushing process. My gps.conf file is in my platform-tools folder. Thanks!
Throw me a bone. Im so close! I can feel it!
How do I get gps.conf file?
link in OP just takes me to a page with a lot of text-No download.
Right click and click save as or save link as. It should automatically name it as gps.conf
Sent from my SCH-I400 using XDA App
Minirome, are you simply he'll Benton pushing this thing via adb? If not, and you just want to get your gps to work, copy the thing to your sd card, download es file explorer, and cnp the thing to the proper dir
Release your inhibitions, feel the rain on your skin, no one else can feel it for you. only you can let it in - Natasha Bedingfield
Works pissah after renaming and replacing using Root Explorer. Grabs the GPS signal wickid quick!
Peace,
Ray
Txwolf1980 said:
Minirome, are you simply he'll Benton pushing this thing via adb? If not, and you just want to get your gps to work, copy the thing to your sd card, download es file explorer, and cnp the thing to the proper dir
Release your inhibitions, feel the rain on your skin, no one else can feel it for you. only you can let it in - Natasha Bedingfield
Click to expand...
Click to collapse
Haha yes I am pretty bent on using adb. I just wanted to gain some experience with it. I might break down soon...unless someone says something. I think I've made progress.
Sent from my SCH-I400 using XDA App
Anyone else try Xposedon the S4? I gave it a go and went into a freeze at the ATT boot animation.
Can anyone help me out? Is there any other option besides a factory restore through Kies?
I don't think I can ADB at this point...
ZPaul2Fresh8 said:
Anyone else try Xposedon the S4? I gave it a go and went into a freeze at the ATT boot animation.
Can anyone help me out? Is there any other option besides a factory restore through Kies?
I don't think I can ADB at this point...
Click to expand...
Click to collapse
The xposed framework in this post works fine on mine.
http://forum.xda-developers.com/showthread.php?p=41159454
And ya, you can use the odin that adamoutler posted in this post to return to stock.
http://forum.xda-developers.com/showthread.php?t=2261573
PS, search is your friend..
sulpher said:
The xposed framework in this post works fine on mine.
http://forum.xda-developers.com/showthread.php?p=41159454
And ya, you can use the odin that adamoutler posted in this post to return to stock.
http://forum.xda-developers.com/showthread.php?t=2261573
PS, search is your friend..
Click to expand...
Click to collapse
Yes I am currently unzipping the firmware (I will keep this in a safe place) to restore.
And I was using the 2.1.3 version, so I will try again with the 2.1.4. Rovo should have updated his OP to show this newer version.
ZPaul2Fresh8 said:
Yes I am currently unzipping the firmware (I will keep this in a safe place) to restore.
And I was using the 2.1.3 version, so I will try again with the 2.1.4. Rovo should have updated his OP to show this newer version.
Click to expand...
Click to collapse
Ya i think it was just a test version, he said he would update the OP after he had some confirms that it works. Which he's had now... prolly just hasn't gotten to it yet.
to get out of a soft brick, this is what I did:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
cd system/xbin
rm /system/bin/app_process
mv /system/bin/app_process.orig /system/bin/app_process
reboot
mcmb03 said:
to get out of a soft brick, this is what I did:
Code:
adb shell
mount -o rw,remount /dev/block/mmcblk0p1 /system
cd system/xbin
rm /system/bin/app_process
mv /system/bin/app_process.orig /system/bin/app_process
reboot
Click to expand...
Click to collapse
Thanks that's what I was looking for. I already restored with Odin though and the best part is that no data was lost whatsoever. :beer:
Sent from my SAMSUNG-SGH-I337 using xda premium
ZPaul2Fresh8 said:
Thanks that's what I was looking for. I already restored with Odin though and the best part is that no data was lost whatsoever. :beer:
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
No worries glad you got it sorted out :good: Thought it may be useful to someone.
Sent from my SAMSUNG-SGH-I337 using xda premium
adb shell error closed
mcmb03 said:
to get out of a soft brick, this is what I did:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
cd system/xbin
rm /system/bin/app_process
mv /system/bin/app_process.orig /system/bin/app_process
reboot
Click to expand...
Click to collapse
after typing in adb shell and hitting enter im getting an error:closed tried multiple times and restarted my phone and pc
ramw24 said:
after typing in adb shell and hitting enter im getting an error:closed tried multiple times and restarted my phone and pc
Click to expand...
Click to collapse
Make sure your phone is at the at&t logo. Try typing
adb devices
to be sure it's recognized by the computer
I was softbricking until I installed the newest xposed version. Works great
perfect!!! BTW dont use icon themer it caused soft brick, but this fixed it wonderfully
ericos123 said:
perfect!!! BTW dont use icon themer it caused soft brick, but this fixed it wonderfully
Click to expand...
Click to collapse
the dev just released an update for S4's and you should no longer softbrick. I tested the beta for him before he pushed to the play store
mcmb03 said:
the dev just released an update for S4's and you should no longer softbrick. I tested the beta for him before he pushed to the play store
Click to expand...
Click to collapse
Do you have the apk file when trying install I get an error
ericos123 said:
Do you have the apk file when trying install I get an error
Click to expand...
Click to collapse
since it's a paid app, I can't give it to you sorry :angel:
mcmb03 said:
since it's a paid app, I can't give it to you sorry :angel:
Click to expand...
Click to collapse
What about the app from the xda thread its on 1.5
How to disable xposed framework via adb.
access adb and use the following. Helped me out a lot.
adb shell
su
mkdir /data/data/de.robv.android.xposed.installer/conf/disabled
How to run this command
mcmb03 said:
to get out of a soft brick, this is what I did:
Code:
adb shell
su
mount -o rw,remount /dev/block/mmcblk0p1 /system
cd system/xbin
rm /system/bin/app_process
mv /system/bin/app_process.orig /system/bin/app_process
reboot
Click to expand...
Click to collapse
Hi I softbricked my panasonic eluga icon while installing xposed framework. Now it is stuck on the screen with the name panasonic on it. I am able to get to the recovery screen but should i wipe the data for the phone to work again.
I tried running adb shell in adb command window only to get an error list of devices attached
0123456789abcdef device offline
then i choose "apply update from adb" on the recovery screen and when i try adb shell it says list of devices attached 0123456789abcdef sideload
I am completely dumb with mobile phone and android part. I am totally helpless and do not know what to do. Please help
If there is a video where you can point me to, it will be greatly appreciated sir.
---------- Post added at 08:22 AM ---------- Previous post was at 07:32 AM ----------
With all due respect for everyone, For panasonic eluga users I dont see much assistance available around. So let me tell you how i came out of the softbrick mode. I was continuously getting the panasonic screen beyond which I could not go. It was stuck on the word panasonic. Then what i did was I wiped the data whcih is factory reset by going to the recovery mode (recovery mode can be found by Pressing the power button and volume up button simultaneously).
All this time the mobile was connected to the PC via the usb cable. I then restarted the mobile twice with the device connected to the PC. Nothing happened. Went to ADB command window, searched for adb devices nothing found. Then I took the cable out of the mobile and tried to go into recovery mode again and it restarted with a message stating optimising app 1 of 35 and then it went right onto the startscreen asking me for foofle aco**** details.
I know this doesnt make much sense but this is how i got my phone going from soft brick mode.
Hello every one,
I'm trying to root my Nexus 4 and I messed up. Can't boot the phone except in recovery mode in TWRP. If a try to boot I got ''Google'' on a black screen and that's it. Don't know what to do from there.
I started to root with Windows 7, but I want to continue with Ubuntu on my computer if it's possible.
Any advice to where to start from?
Thanks,
Martin
What did you do to get to where you are? Without more info I'm going to tell you to boot into the bootloader and flash the factory image
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
jd1639 said:
Without more info I'm going to tell you to boot into the bootloader and flash the factory image
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the awnser, but don't know how to ''flash'' the factory image
mchenier said:
Thanks for the awnser, but don't know how to ''flash'' the factory image
Click to expand...
Click to collapse
Read this http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
jd1639 said:
Read this http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks, I'm going to take a look
mchenier said:
Thanks, I'm going to take a look
Click to expand...
Click to collapse
Wait a minute, before you flash the factory images. What exactly happened?
vinc10 said:
Wait a minute, before you flash the factory images. What exactly happened?
Click to expand...
Click to collapse
I followed a procedure (in french) and got stock on these lines:
Installation de SuperSU et Busybox :
Vous êtes sur TWRP
Sur le smartphone faites : Wipe > Advanced Wipe > Dalvik Cache (case cochée) > Cache (case cochée) > Swipe to Wipe
Sur le smartphone faites : Mount > System (case cochée)
Wasn't able to wipe Dalvik and after that and for some reasons was not able to connect to the phone from the Windows 7 computer. I'm not certain of what happen after, I probably erase important files on the Nexus with the TWRP menu.
This is what I got when booting in safe mode
Sounds like you wiped your system and internal sd card and now don't have anything to boot into. You could use adb to push a rom zip to your internal sd and install it with twrp. Or you could sideload it with twrp. Or you could flash the factory image and start all over.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Sounds like you wiped your system and internal sd card and now don't have anything to boot into. You could use adb to push a rom zip to your internal sd and install it with twrp. Or you could sideload it with twrp. Or you could flash the factory image and start all over.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I think I can push a rom zip to the sd card. Where can I find a rom?
Thanks
mchenier said:
I think I can push a rom zip to the sd card. Where can I find a rom?
Thanks
Click to expand...
Click to collapse
Where you on a particular rom before or just stock?
Edit, this is from the development forum. It's stock 4.4.4. http://forum.xda-developers.com/showthread.php?p=50453541
Edit,edit, also, when you flash super su you don't need to do the wipes your French procedure told you to do. Just flash super su in twrp, use the install.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Where you on a particular rom before or just stock?
Edit, this is from the development forum. It's stock 4.4.4. http://forum.xda-developers.com/showthread.php?p=50453541
Edit,edit, also, when you flash super su you don't need to do the wipes your French procedure told you to do. Just flash super su in twrp, use the install.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Well, don't know what to do at this moment.
1. Should I try to complete the '' french'' procedure? I tried to continue with those command:
adb push busybox /system/xbin
adb push supersu.zip /sdcard
adb shell
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install /system/xbin/
exit
But got a error message at chmod :
chmod 04755 /system/xbin/busybox /system/xbin/busybox --install /system/xbin/
unknown option -- install
BusyBox v1.21.1-jb bionic (2013-07-25 21:23 +0100) multi-call binary.
Usage: chmod [-R] MODE[,MODE]... FILE...
Each MODE is one or more of the letters ugoa, one of the
symbols +-= and one or more of the letters rwxst
-R Recurse
Then I pushed the mako_Kitkat.zip and supersu and try to install from TWRAP but both failed. Is there an order to do it?
mchenier said:
Well, don't know what to do at this moment.
1. Should I try to complete the '' french'' procedure? I tried to continue with those command:
adb push busybox /system/xbin
adb push supersu.zip /sdcard
adb shell
chmod 04755 /system/xbin/busybox
/system/xbin/busybox --install /system/xbin/
exit
But got a error message at chmod :
chmod 04755 /system/xbin/busybox /system/xbin/busybox --install /system/xbin/
unknown option -- install
BusyBox v1.21.1-jb bionic (2013-07-25 21:23 +0100) multi-call binary.
Usage: chmod [-R] MODE[,MODE]... FILE...
Each MODE is one or more of the letters ugoa, one of the
symbols +-= and one or more of the letters rwxst
-RRecurse
Then I pushed the mako_Kitkat.zip and supersu and try to install from TWRAP but both failed. Is there an order to do it?
Click to expand...
Click to collapse
I'm not sure why the rom you tried to flash failed. You should flash the rom first and then super su. I think at this point I'd flash the factory image. Just download it and extract it. Then double click on the flash-all.bat with your phone booted into the bootloader and connected to your usb port. You'll then need to flash the twrp recovery image in fastboot to get twrp back on your phone.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You'll then need to flash the twrp recovery image in fastboot to get twrp back on your phone.
Click to expand...
Click to collapse
I'm not sure to understand what do you mean by flashing the TWRP recovery image. I will have to reinstall TWRP on the phone after that? Restart all the procedure I did first?
mchenier said:
I'm not sure to understand what do you mean by flashing the TWRP recovery image. I will have to reinstall TWRP on the phone after that? Restart all the procedure I did first?
Click to expand...
Click to collapse
If you flash the factory, yes, you'll have to start all over
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If you flash the factory, yes, you'll have to start all over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
OK thanks.
mchenier said:
OK thanks.
Click to expand...
Click to collapse
It's done, thanks a lot for your help. It was easier for me on a Linux system. I didn't root it this time. I just want to know if it will resolve the problem I had with the phone (closing randomly and at the end wasn't even able to open it)
mchenier said:
It's done, thanks a lot for your help. It was easier for me on a Linux system. I didn't root it this time. I just want to know if it will resolve the problem I had with the phone (closing randomly and at the end wasn't even able to open it)
Click to expand...
Click to collapse
Glad to hear it's working
Sent from my Nexus 5 using XDA Free mobile app