Database Users

rooting problems

hey. i have no clue why but my g1 isnt get rooted. ive did everything in the unlockrs step if you go to theunlockr.com. everything went successful and exactly what his did but when i go to terminal and type su it says permission denied.when i power on using camera and end it goes to android on skateboards(i doont not that matters). anyone have any ideas

mr.johnsexydavis911 said:
hey. i have no clue why but my g1 isnt get rooted. ive did everything in the unlockrs step if you go to theunlockr.com. everything went successful and exactly what his did but when i go to terminal and type su it says permission denied.when i power on using camera and end it goes to android on skateboards(i doont not that matters). anyone have any ideas
Click to expand...
Click to collapse
I followed the unlockr's steps to help David test out his new guides, and I never had a problem. If your going into terminal and typing "su" and getting the permission denied message, that means everything DIDN'T go successfully. The skating androids when in bootloader means that you have an SPL that allows you to upload custom ROMs but says nothing about whether you have root. Follow the steps again paying particular attention to each one.

If you really want to root your phone easily and without problems or confusion, follow this guy's instructions:
http://www.youtube.com/watch?v=xOo2V9qCauc

Main Version Is Older! Update Fail! Message

Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate

Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.

I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.

jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?

xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?

try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.

jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!

xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.

g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?

xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.

I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.

It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0

Rooting OTB 2.1 Eris

I have now Rooted Two 2.1 Eris the last few days. I dont know if this has been covered, I did a search and honestly searching here is a little fetch.
This is a place holder.
POST here if you want to know how to root 2.1 or post here and let me know if its already been known how to root.
Here is the Phone Information and Specs of the one i just rooted.
Firmware Version
2.1
Baseband
2.42.00.04.12
Kernel Verison
2.6.29-8a03cb9a
[email protected] #1
Build Number
2.36.605.1 CL165907 Release-keys
Software Number
2.36.605.1
Browser Version
WebKit 3.1
PRL Version
58005
ERI Version
5

Were the specs like this before or after the rooting?

After the root.
I should have got the specs before the root. I can tell you how to do it if you have a 2.1 its fast.
I just want someone on here to verify it.

Sure why not.

Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.

FireSokar said:
Just post how to do it instead of trying to drag on a thread and make yourself big, I honestly dont think you did root them or you would of posted a tutorial. prove me wrong... go for it.
Click to expand...
Click to collapse
Yeah honestly I'm with this guy ^.

Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.

amoamare said:
Trust me i dont need to make myself big on xda i could care less.
Heres what I have been doing on them, push the 1.5 root to the phone reboot recovery install like you would root on 1.5 It should complete.
You will notice when it reboots that YOU DO NOT HAVE SUPER USER.
What i did was went to my cmd prompt typed adb shell, i have #. So i proceeded with installing recovery.
Once installing the new recovery i adb reboot recovery again. This time you get the green letters with the recovery, I installed the offical2.1with root over the OTB 2.1 with root. Pretty much you could install any rom with root on it.
Wiped and rebooted. Now i have 2.1 with superuser and root.
Click to expand...
Click to collapse
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.

Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.

amoamare said:
Okay so I initially didnt think i would have to spell this out.
Push PB00IMG.zip to root of the SDCARD on a 2.1 OTB eris.
Adb reboot recovery apply the PB00IMG.zip
Wait for complete and reboot phone.
When the phone boots up you WILL NOT HAVE THE SUPERUSER installed. Instead if you go to your cmd prompt and type adb shell you get the # < then install the recovery-RA-eris-v1.6.2.img and flash image as usual.
Reboot recovery this time you get the Green Letters Recovery.
Click to expand...
Click to collapse
I would like it if you spelled it out even more. I am not familiar with all the ADB shell commands, so could you list the exact command for each step? That would help me out greatly, thanks!

AcidRoot said:
Correct me if I'm wrong but by 1.5 root you mean the 1.5 to 2.1 rooted update and that only works for phones running 1.5 which we already had. Now there trying to get root for the 2.1 leaks/ota. not to mention i think the 1.5 root was a PB00IMG.zip which is not for recovery.
Click to expand...
Click to collapse
He is trying to tell you that he has the old root method working on 2.1.
I know that he has done this on two devices. One fresh out the box with 2.1 and one that was updated to 2.1.
I am looking for a 2.1 Eris myself to duplicate.
I personally remember having a problem loading the root file on a 2.1 Eris, but I only tried one of them. Then I left it alone.
I think I gave up too easy when I was told that it could not be done with that file.

Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
version 1.47 or 1.49?

amoamare said:
Exactly I was told it could not be done.
What happend was the one out of box I ended up launching the Root with out checking if it was 1.5 or 2.1 When the phone wouldnt reboot after trying to root i wiped the handset. It loaded after some time like 15 mins. I looked for the Superuser program and it wasnt installed.
Ended up checking software version it was 2.1. A little fustrated I ran my script for cricket WITCH REQUIRES ROOT.
It rebooted the phone and what did i notice my **** was on the phone without root. So i thought. I check adb shell and i got the #. So i hit up installing recovery and i was able to install it so i install the official 2.1 with root rom to get the superuser apk on the phone.
Click to expand...
Click to collapse
What was the boot screen like? The Green Android people that wave at you or the HTC "quietly brilliant" screen

Holy **** It works!

I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
No when you took the phone out of the box and started it for the first time after the green androids on skate boards did little green android guys wave or did you get the htc quietly brillant

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
HBOOT version I believe.

PusherRobot said:
Holy **** It works!
Click to expand...
Click to collapse
Hey man, what are the commands you used? I pushed PB00IMG.zip to the sdcard, but when I do > adb reboot recovery , it simply restarts and shows that phone icon with the red triangle over it. When I manually pressed power and volume down, the same error as always occurs (version is older). What am I doing wrong?

amoamare said:
I dont remember boot screen.
as far as version 1.47 or 1.49
Im not sure what your asking here, version of the PBIMG i used ?
Click to expand...
Click to collapse
Well congratulations, you found a bass ackwards way to root a phone with a (more than likely) 1.47 bootloader. We've had it for months, welcome to the party. Although, You're a little late...

Froyo Root

Is there any word when the unrevoked team will release a version of unrevoked that will work on Froyo? I messed up and loaded the OTA RUU and did not unrevoke forever before doing this. I have tried downgrading back to 2.1, but have had no luck. Every time I launch the RUU, the phone disconnect, so the RUU cannot read the phone. When I close the RUU, the phone reconnects.
If anyone has a fix for this, then maybe I can downgrade to 2.1 and then do the update correctly. Otherwise, I will have to wait on the unrevoked team.
Thanks
Sent from my ADR6300 using XDA App

Just put this on the root of your SD card as PB31IMG.zip, boot into hboot, and hope it doesn't complain about the radio version. Then use unrevoked3 for clockwork, unrevoked forever for s-off, and re-flash the RUU.

If this is the stock 2.1, I tried it. The system rejected it because it was an earlier version. Thanks.
Sent from my ADR6300 using XDA App

This should help
http://forum.xda-developers.com/showthread.php?t=768295

What about the exploid for DX that works with Evo as well. Has anyone tried this on an OTA 2.2 Inc? It would be a bummer to have to downgrade to upgrade again.

TNS201 said:
This should help
http://forum.xda-developers.com/showthread.php?t=768295
Click to expand...
Click to collapse
TIS201. I will give this s try when I get home from work. Looks promising. Thanks. Will let you guys know how it goes.
Sent from my HTC Droid Incredible using XDA App

TNS201 said:
This should help
http://forum.xda-developers.com/showthread.php?t=768295
Click to expand...
Click to collapse
OK. I gave this a try and all looked good until I rebooted the phone. Once again the bootloader said I was trying to load an older image and would not load. So, I looked around and found some other links. In the end, what I found that in the instructions, step 6 says:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
In another forum I found a difference in the instructions in that it used 777 instead of 0755. I tried this and the phone loaded the PB31IMG.zip file as it should. The only problem I then had was there was something wrong with the file and I was stuck in the bootloader. I downloaded a different image and tried again. This one also loaded and this time the phone booted just fine. I now have the phone back to stock with 2.1 Update1.
Thanks for your help. I think after I get everything back up and running, I will post the steps with the correct data. Now, to reroot the phone and this time load unrevoke forever.

2.3.4 Latest OTA[2.77.651.8] Downgrade!!

Hey guys, so since the latest OTA, we haven't been able to downgrade nor root the shift, if we were on the latest OTA. I've been hunting through methods for downgrading and rooting, but nothing came about that actually worked. Finally having a free mind after my AP Physics exam, I got a train of though going, and tried Indirect's downgrade method, which yes, failed. What happened is when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. Using quick root and Indirect's method of downgrading, I managed to downgrade to Android 2.2, and got to root my phone, then flash some ROMs.
Solution:
When you are in the step in Indirect's tutorial where you use the
Code:
[COLOR="Red"]adb shell sh /data/local/tmp/taco --setup[/COLOR]
command, you'll notice that tacroot doesn't have the permissions to reboot, at that time, you have to open lyriquidperfection's "HTC Quick Root v1.1.13" application and execute the reboot to recovery command through it by clicking on the drop down in reboot options, and choosing to reboot to recovery.
When you are at the step in the tutorial when you boot to hboot in order to downgrade, you can use the Quick Root application to reboot to bootloader where you flash your downgraded PG06IMG.zip.
Links:
Indirect's - Root and downgrade for Android 2.3.4
lyriquidperfection's - HTC Quick Root v1.1.13
If any clarification is needed, please post below, this is simply a quick guide to allow people to downgrade and if they choose, root it or flash a ROM. I take NO responsibility in what you do with your device nor when you void your warranty. I take NO credit for neither Indirect's method of downgrading, nor lriquidperfection's application, though I would appreciate a thanks for my compiling this "quick guide" to help you downgrade your device. If you're looking for credits on the method and application, they should be found at those posts.
Good luck,
John
*If you want to flash a rooted version of this update, go to this thread
Just keep in mind you can't flash a new ROM to your phone until you downgrade.
local.prop: permission denied resolution by CNexus: his post
For anyone else who has problems, here's what I did. if you get the message
Code:
local.prop: permission denied
After running
Code:
adb shell sh /data/local/tmp/taco --root
Then simply run the following command again (step 2 of Indirect's method)
Code:
adb shell chmod 755 /data/local/tmp/taco
The problem is that your phone resets the permissions of that directory, so it doesn't let tacoroot execute and do its thing.

Nice
Sent from my HTC Evo Shift using xda app-developers app

BigSplit said:
Nice
Sent from my HTC Evo Shift using xda app-developers app
Click to expand...
Click to collapse
Thanks, glad to see people appreciating this

Very nice, and much appreciated . Hellua nice find.

Very nice find, I would triple thanks if I could
ICS rom, here I come.
Sent from my PG06100 using xda premium

Might want to add the Software Number to the OP

indirects method for 2.3.4 wouldnt work for me on the latest ota but lyriquidperfection's - HTC Quick Root v1.1.13 method rooted like a charm. i was running completely stock 2.3.4 latest with the newest hboot and with some force and annoyance managed to somehow trick the new hboot into doing the downgrade to 2.2 and i was able to get s-off/full root again.
if i can figure out what exactly i did ill post it up for everyone but im not entirely sure. it mightve been a fluke.
all i know for sure is after i got root with lyriquidperfection's - HTC Quick Root v1.1.13
i dd the misc.img a ****load of times and then dd the eng hboot a ****load of times until it <------like 30 times in a row each lol, one after another the other.
it forced the hboot to relock the htcdev unlock and accidentally took the 2.2 downgrade (PG06IMG.zip) so i could switch hboots again.
its a helluva gamble but if anyone else has unlocked through htcdev and is willing to gamble on it have fun, if you brick it isnt my fault and i hold no responsibility over it. i think i pissed the phone off and it gave up but it worked for me. it was really a combination of using the lyriquidperfection's - HTC Quick Root v1.1.13, indirects root method, and vicodans method.

OP: so you tried my method and it failed too?

VICODAN said:
OP: so you tried my method and it failed too?
Click to expand...
Click to collapse
I believe I may have come across it. This weekend I may go back to 2.3.4 to test out some other solutions, mix and match, just to see what over all works.

JohnnyCakeXM said:
I believe I may have come across it. This weekend I may go back to 2.3.4 to test out some other solutions, mix and match, just to see what over all works.
Click to expand...
Click to collapse
yeah, i had to do a complete mashup to get my hboot to take the 2.2 downgrade, im still trying to remember how i did it and debating on taking the gamble again myself

Lol, i'm just fine with this method. Worked for me, therefore I am satisfied,

JohnnyCakeXM just a suggestion, but you may want to give a little more detail in the OP. Maybe a Step by Step .

prboy1969 said:
JohnnyCakeXM just a suggestion, but you may want to give a little more detail in the OP. Maybe a Step by Step .
Click to expand...
Click to collapse
Basically he just used a reboot app to do the needed reboots since taco couldn't and everything else is done by script
Sent from my miTouch-4G-Slide using Tapatalk 2

strapped365 said:
Basically he just used a reboot app to do the needed reboots since taco couldn't and everything else is done by script
Sent from my miTouch-4G-Slide using Tapatalk 2
Click to expand...
Click to collapse
I understand what he did . It's just I've received a few PM's asking what his steps are. So rather then explain it every time, I figured I'd give him a heads up to give a more detailed OP for the newbs.
TEAM MiK
MikROMs Since 3/13/11

Moved from THIS thread.
---
prboy1969 said:
Well I think you would've be better off posting in JohnnyCakeXM's thread. Might want to think about moving this discussion over there. But anyway. It sounds like you did not actually complete the first part of the process.
A factory Reset isn't going to do it.
Click to expand...
Click to collapse
Well thats the problem, to complete the first part, I need to get that menu to show up again, but it won't and just gives me the recovery icon
But any ideas? I was thinking of running the 2.3.4 RUU, but it may not take because of the OTA, so idk
Sent from my PG06100 using xda premium

CNexus said:
Ok, so today I got around to rooting my phone, running the latest OTA with JohnnyCakeXM's process
I ran the command that was denied "adb shell sh /data/local/tmp/taco --setup"
Gives error (expected)
Rebooted through HTC Quickroot, pressed the 3 buttons and got the "cache files" error
It gave me the "Android System Recovery <3e>" menu...but then I kinda just pulled the battery instead of selecting "Reboot system now"
Now whenever I try to go through this again to get to the "3e" menu, it just stays stuck in recovery (with the ! sign) after I press VolUp + VolDown + Power
Any help as to how to get to that menu again?
Click to expand...
Click to collapse
CNexus said:
Moved from THIS thread.
Well thats the problem, to complete the first part, I need to get that menu to show up again, but it won't and just gives me the recovery icon
But any ideas? I was thinking of running the 2.3.4 RUU, but it may not take because of the OTA, so idk
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I do not think the 2.3.4 RUU is going to work for you. The issue I believe is that you didn't actually complete Indirects part of the method.
The command " adb shell sh /data/local/tmp/taco --setup " should have gone through before you went any further. I would try starting the whole process over again.

I'll take care of it some time tonight, or tomorrow. Just will have to re-flash stock 2.3.4 to ensure everything is in order and I'll even make a video for it. Text tutorial will come first, when it does.

prboy1969 said:
I do not think the 2.3.4 RUU is going to work for you. The issue I believe is that you didn't actually complete Indirects part of the method.
The command " adb shell sh /data/local/tmp/taco --setup " should have gone through before you went any further. I would try starting the whole process over again.
Click to expand...
Click to collapse
Thats the reason why JohnnyCakeXM posted this thread in the first place...? Because the command DOESN'T go through completely so you need to use some third party program to do the reboots for you
EDIT: Yes, I have gone through it multiple times and even checked my cables and everything to make sure that none of that was the problem before I even posted here
Sent from my PG06100 using xda premium

CNexus said:
Thats the reason why JohnnyCakeXM posted this thread in the first place...? Because the command DOESN'T go through completely so you need to use some third party program to do the reboots for you
EDIT: Yes, I have gone through it multiple times and even checked my cables and everything to make sure that none of that was the problem before I even posted here
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
What he said in the OP was :
" when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. "
So unless I'm not reading his OP incorrectly ( which is a possibility ) , the command has to go through. But it will fail to reboot, then you use Quick Root to do the Reboots. Again this is why I suggested a Clearer Step by Step OP. So that the process can be more easily followed, and diagnosed if there is an issue . It leaves a lot less to interpretation.

prboy1969 said:
What he said in the OP was :
" when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. "
So unless I'm not reading his OP incorrectly ( which is a possibility ) , the command has to go through. But it will fail to reboot, then you use Quick Root to do the Reboots. Again this is why I suggested a Clearer Step by Step OP. So that the process can be more easily followed, and diagnosed if there is an issue . It leaves a lot less to interpretation.
Click to expand...
Click to collapse
Yes, I ran tacoroot --setup, waited for the error, and then rebooted through Quickroot
I think I said this in my original post in the other thread..?
Sent from my PG06100 using xda premium