Related
So here's an odd one i can't put my finger on.
So i used the RUU to go back to stock unrooted, to install the leaked OTA for the radio update. It all worked properly.
I used unrevoked3 to root the phone again. Also worked perfectly.
When using a terminal emulator on the phone i can issue the "su" command and all is well, however when i reboot into recovery and try to issue the "su" command it wonderfully tells me that it cannot find the "su" command.
What step did i miss guys, i've been over this a few times, now trying to get things pinned down, but i just can't figure this one out.
obsidianblackhawk said:
So here's an odd one i can't put my finger on.
So i used the RUU to go back to stock unrooted, to install the leaked OTA for the radio update. It all worked properly.
I used unrevoked3 to root the phone again. Also worked perfectly.
When using a terminal emulator on the phone i can issue the "su" command and all is well, however when i reboot into recovery and try to issue the "su" command it wonderfully tells me that it cannot find the "su" command.
What step did i miss guys, i've been over this a few times, now trying to get things pinned down, but i just can't figure this one out.
Click to expand...
Click to collapse
You are fine. By default, you are already SU in an adb recovery shell, if booted into CWM. If you want to actually do things with SU, you want to mount your system partition.
Oh, and BTW, this belongs in general.
ah ha that's what i was missing. Thanks!!!!
MODS: Can someone please move this to general.
Edit: Interestingly enough, i have mounted the system partition in recovery, and am still getting the same error. /sbin/sh: su: not found.
There should be no need to execute su in recovery as you are already su when in recovery (as shown by the hash sign at the prompt, #).
What is it you're trying to accomplish? Try doing it without explicitly using su as a command?
Sent from my ADR6300 using XDA App
bcgaynor82 said:
There should be no need to execute su in recovery as you are already su when in recovery (as shown by the hash sign at the prompt, #).
What is it you're trying to accomplish? Try doing it without explicitly using su as a command?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
lolol, linux on a desktop i can handle. Linux on a phone for some reason though is confusing me. I did end up trying to do what i was after without issuing a su command and whoa it worked. Thanks for the advise.
Hello everyone!
I unrooted my Droid X, and I was wondering how I remove Clockwork Recovery? Whenever I have my Droid X plugged into my computer the Clockwork Mod shows up. Is there anyway to remove it with a program or something? Or anyway just to remove Clockwork Recovery? Thank you!
Thanks for the help
SysAdmin-X said:
Removing BOOTSTRAP COMPLETELY (You only need to follow these steps if you WANT to remove Droid X bootstrap by Koush, this is not installed on your phone by default).
If you would like to completely remove Droid X bootstrap from your phone, here is what you need to do:
1) connect your phone to ur pc in charge only mode. Make sure it is recognized by adb
A) open command prompt and type "adb devices" (hit enter, your phone should show up)
2) in the command prompt, type "adb shell" (press enter)
3) type "su" (press enter)
4) type "mount -o rw, remount /dev/block/mtdblock4 /system" (press enter)
5) type "cp /system/bin/logwrapper.bin /system/bin/logwrapper"(press enter)
6) type "adb reboot" (press enter)
Your phone will reboot after typing adb reboot, and may take a little bit longer to boot the first time after bootstrap is removed (it may not, I just haven't gone through this process in a while).
Bootstrap should now be completely removed.
Click to expand...
Click to collapse
Hope this helps
just a quick tip: i tried this method and discovered that there was still a problem with the logwrapper file... after much searching i found this. it is a clean logwrapper file that you can replace the old one with if you still have issues as i did.
clean logwrapper file
make sure that you check the permissions of the original and ensure that the new ones match
use adb or root explorer to push this to the system/bin folder on your phone.
steveojp said:
Hello everyone!
I unrooted my Droid X, and I was wondering how I remove Clockwork Recovery? Whenever I have my Droid X plugged into my computer the Clockwork Mod shows up. Is there anyway to remove it with a program or something? Or anyway just to remove Clockwork Recovery? Thank you!
Thanks for the help
Click to expand...
Click to collapse
Would sbfing be easier to remove the recovery and bootstrap? At least that's what I think would be easiest, maybe its just me.
Devices:
DroidX Liberty v2.0 (Current)
Droid 1
Moto Cliq
HaXERxPaYLaY said:
Would sbfing be easier to remove the recovery and bootstrap? At least that's what I think would be easiest, maybe its just me.
Devices:
DroidX Liberty v2.0 (Current)
Droid 1
Moto Cliq
Click to expand...
Click to collapse
yea i am sure that it is, if you can sbf (i can't on milestonex) and if you want to wipe everything out. but if you simply want to remove the bootstrap then i would do this.
SBFing would be the easiest thing to do. Just be sure to back up all your data that you would like to keep through the SBF.
I would use an app such as MyBackup Free to back up all your goods and what not.
Guides to SBFing can be found all over the Internet. You will need to use the .602 SBF file.
Sent from my DROIDX using XDA App
I was attempting to root my 6.2.1 and successfully had superuser installed and rooted. When I tried moving the Android Marketplace into the /system/apps/ folder it wouldn't appear so I checked all the write permissions and still no luck. I reverted back but must have deselected all of the permissions because now in my /systems/ folder the /app permissions are d---------.
The result is the Fire is stuck on the "Kindle Fire" boot screen and will go no further. When I try all of the fixes it prevents me from going into the adb shell as root, with either a "Stopped (signal)" or "Segmentation fault" error when I type in "su" or "su -".
None of the other tools such as zergRush work because they can't write to the file system and can't elevate to shell root in order to do so. This thread: http://forum.xda-developers.com/showthread.php?t=1356257 doesn't work either because in order to gain temp root, it requires zergRush. Any help on gaining shell root would be appreciated and any additional details can be provided.
Did you try the lastest KF utility v.7? Your not alone with this problem...
I'm in the same boat as you. I tried for 2 days to fix it to no avail and finally decided I was SOL without one of of these "factory cables". The other day I did a support chat with amazon and they are sending me a new kindle. My main gripe with the kindle is there is no way to easily factory reset because of the lack of hardware buttons. Think I'm gonna wait for a cyanogenmod 9 rom before I mess with the replacement... Good luck.
Sent from my HD7 T9292 using XDA Windows Phone 7 App
Had this problem last night
Already trying to hack your Christmas present?
I had this problem last night. Stuck on boot screen and powering down and up didnt fix. This is what what fixed it for me.
Go into CMD and type this, with the kindle connect via usb,
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
Used KF Utility 6
I haven't had success with v7 yet, but will try when I get back. I had trouble with KF Util on Windows 7 so went back to XP. Will try Ubuntu next because it's easier to navigate the command line. Is there any difference between v6 and 7 with respect to elevating shell privileges?
Yeah follow the command... I think we are stuck on fastboot!
Well at least I'm not the only one who did this. Same issue... Tried to copy the marketplace APK and it wouldn't appear. Changed permissions and am now stuck at boot splash. Executing "fastboot -i 0x1949 oem idme bootmode 4000" simply hangs at "<waiting for device>".
No shell root, no progress
I've tried unrooting with KF utility v7 to no avail. One problem could be that I had Burrito Root on the Fire prior to the bricking, but how I can remove it at this point is beyond me. I can't run the fastboot commands without being in shell root, and KFUtilityv7 doesn't work without those credentials.
Some errors: "(idme) Invalid permission"; "reboot: Operation not permitted". These are seen when I try to put it in recovery mode. FYI, my ADB status is online and my computer sees it, the ADB Rooted status says "No" and I'm in Boot Status 4000 (Normal).
When I try running BurritoRoot it goes through a process, says "Elevating the Shell" and then errors out with "adbd cannot run as root in production builds"
Then below this it says "Root Activated" and "The Kindle is successfully in root mode."
Here is the output from my attempts at installing Permanent Root with KFUtility v7:
***********************************************
* Root Activated *
***********************************************
The kindle is successfully running in root mode.
mount: Operation not permitted
mount: Operation not permitted
failed to copy 'files\su' to '/system/xbin/su': Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
Unable to chmod /system/xbin/su: Read-only file system
2114 KB/s (843503 bytes in 0.389s)
Error: Could not access the Package Manager. Is the system running?
***********************************************
* Root Installed *
***********************************************
Permanent root has been installed.
With great power, comes great responsibility.
Please be careful with how you use root.
It is HIGHLY recommended you have TWRP installed before using root.
****************************************************
At this point you can see the mount operations were not successful because you cannot gain root in the shell with su. I am going to try this through my Ubuntu build and see if I can gain privileges through Linux.
Hi. Same problem here. Changed the /system/app permissions by mistake and the Fire won´t pass the loading screen.
I think the only hope we have is that someone finds a way to root from adb.
According to GregDDC:
GregDDC said:
I had the same issue and fixed it with a recovery cable.
The process was simple, just short the 1st and 4th pins on a microUSB cable and boot into recovery/fastboot. You can find all the information here (link) and here (http://forum.xda-developers.com/showthread.php?t=1392693&page=3). I accomplished everything using Kindle Fire Tools.7 I hope this helps.
Click to expand...
Click to collapse
I just don't have the dexterity to fashion my own cable.
Sent from my SPH-D710 using XDA App
Sent from my SPH-D710 using XDA App
I have the same problem. I get the boot-loop with the kindle fire logo. I can access the file system, but most commands give me a seg or permission error. ZergRush doesn't work so fast boot won't work.
I'm trying to get a factory programming cable off here or make my own. That should bypass the whole root issue and put you directly into fast boot so you can load a kindle rom or cm7 or whatever.
Think I'll wait for my wife to go to work tomorrow so I can spend the day working on a cable without distraction. ;-)
Sent from my SPH-D710 using XDA App
Seriously, you most likely don't need the Factory cable to fix your problems. Just do some more reading. There are more than enough threads on these issues to provide you with a clue on how to get out of or into what you are trying to do.
Care to give us a clue on the solution then? I have scoured both this and other threads.
Sent from my SPH-D710 using XDA App
If you cant boot into the OS, you cant get root again.
If you cant boot into TWRP, you cant get it fixed.
If you were romping around with root, with no recovery installed, its likely bricked.
Get a factory cable, or send it back. Learn from the mistake and install a recovery.
Exactly correct (unfortunately) Vasheypooh. At the crossroads of waiting for another temp root through adb our practice my soldering skills.
Sent from my SPH-D710 using XDA App
Factory cable will be the solution for me i'm from canada.
Vashypooh said:
If you cant boot into the OS, you cant get root again.
If you cant boot into TWRP, you cant get it fixed.
If you were romping around with root, with no recovery installed, its likely bricked.
Get a factory cable, or send it back. Learn from the mistake and install a recovery.
Click to expand...
Click to collapse
i've come to the same conclusion unfortunately. this is only my second attempt at rooting an android device and it's wildly different from the process for the previous device i was working with, so since the instructions i was using didn't mention installing a recovery, i failed to do that myself. my kindle is going to the "Your kindle had detected a problem and must clear App storage" on every boot and all attempts to communicate with it have failed. looks like a cable or a new device are my only options at this point. i will definitely be using a recovery of some kind from now on!
rcabls said:
I was attempting to root my 6.2.1 and successfully had superuser installed and rooted. When I tried moving the Android Marketplace into the /system/apps/ folder it wouldn't appear so I checked all the write permissions and still no luck. I reverted back but must have deselected all of the permissions because now in my /systems/ folder the /app permissions are d---------.
The result is the Fire is stuck on the "Kindle Fire" boot screen and will go no further. When I try all of the fixes it prevents me from going into the adb shell as root, with either a "Stopped (signal)" or "Segmentation fault" error when I type in "su" or "su -".
None of the other tools such as zergRush work because they can't write to the file system and can't elevate to shell root in order to do so. This thread: http://forum.xda-developers.com/showthread.php?t=1356257 doesn't work either because in order to gain temp root, it requires zergRush. Any help on gaining shell root would be appreciated and any additional details can be provided.
Click to expand...
Click to collapse
I have exact same issue. Can someone help. I can't get rooted using any of the tools available today.
HELP!
This is because you changed the properties on all the files in /system.
Why would you do that?
su no longer has permissions to run.
If you can't get into recovery, you likely need a factory cable to fix.
Here is a quick guide on how to unroot the latest RUU 5.07. It seems that quite a few people are having trouble unrooting their device or running an official RUU while being on the latest update, or a ROM based on the latest update.
The problem is that HTC has fixed the bootloader (in particular Hboot 2.18) so that it will reject any PC36IMG.zip official software or RUU files that update previous operating systems on the phone (a S-ON phone). You would usually need a RUU (I'm calling both the PC3IMG.zip file and the RUU file an RUU) that is for your current operating system. If your phone is on the latest 5.07 update or a ROM that is based on the 5.07 update, then latest RUU that exist is for the Evo with RUU Supersonic 4.67. 5.07 never came out, done intentionally by HTC I believe. So none of the RUUs which exist today will work with the 5.07 update. The problem exist because the phone's misc partition is updated whenever you accept an update or run a RUU from HTC, or even flash a ROM. There are other cases as well. The only way to run an official RUU on a phone that is not currently S-OFF is either to downgrade the phone's misc partition, or to turn the phone S-OFF (which you will still have to flash the phone's misc partition to do).
What I've done is put together a quick guide for those who need (or just insist) on unrooting their Evo. It is brief and only for a PC (not a Mac). Hopefully, someone in the future can provide further details or make it Mac friendly or even more user friendly because I don't have a Mac, nor the time to spend to make this guide perfect. I have another phone too to deal with. Remember too, that everything is done at your own risk. So if something goes wrong, well you knew the risks.
For this guide I'm going to assume that you are on Hboot 2.18, the phone is S-ON, the bootloader is unlocked (UNLOCKED), and that the phone's ROM is currently rooted. If not, then this is not the right guide for you.
1. Download this zip file. It contains the necessary files that you will need.
https://dl.dropbox.com/u/38127313/sdk.zip
2. Plug your phone into your computer. Then go to Settings/Applications and uncheck Fastboot. Then goto Development and make sure that USB debugging is now checked. If you have a custom ROM, then the locations of these settings may be slightly different.
If you need the HTC drivers, then I have also included the drivers.exe file that you must run from your computer to install the "MyHtc" drivers that you must have under the computer's device manager when the phone is plug in.
3. Next, unzip the file to a folder, preferably sdk. Rename the "PC36IMG_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15.00.0808_NV_2.15_release_220182_signed" file to PC36IMG.zip (not PC36IMG.zip.zip). Place the phone into "Disk drive, then copy the PC36IMG.zip file to your sdcard. Afterwards, don't forget to change the phone back to "Charge only".
4. Next you will need to open a command prompt at the folder where you extracted the files. If you are not familiar or uncomfortable with adb commands, then I cannot help you here.
5. Type or copy the below commands exactly as they appear.
adb push flash_image /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb push mtd-eng.img /data/local <ENTER>
(This places the file on your phone in the /data/local directory).
adb shell <ENTER>
(You should see either a dollar sign ($) or a pound sign (#) at your prompt, depending on your ROM. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
su <ENTER>
(You might not need this command depending on your ROM, and also you should check to see if your phone is asking for superuser permissions. If everything went Ok, you should now see a pound (#) sign at your prompt. If you do not then something went wrong. And, No the phone will not brick if you should stop at this point).
cd /data/local <ENTER>
(You need to be in the directory where you put the flash_image and mtd-eng.img files).
chmod 755 flash_image <ENTER>
(flash_image needs to be assigned permissions).
./flash_image misc mtd-eng.img <ENTER>
(This is the most critical step here).
reboot bootloader <ENTER>
(I prefer this step, as it is much faster than pulling the battery and all that other stuff that people suggest).
The phone should now reboot directly into the bootloader. Also the phone will now be locked again (LOCKED OWW) regardless of its previous state. Next hit the power button. It will then take some time to read the PC36IMG.zip file. If everything went Ok, then it should ask you whether or not you want to accept the update, which means that your misc partition was successfully downgraded, and now you can successfully run the RUU.
EDIT: I have to re-upload the sdk.zip file, because the original one had a problem with the PC36IMG.zip file. It should be available shortly. The one I added does work this time; however, the phone may have to be updated in order to bring it back to the latest bootloader and update. It's not the latest RUU 4.67, but the second latest 4.54. I cannot believe that something was wrong with that file. Also, instead of the PC36IMG.zip file that I added, you could also use any other PC36IMG.zip file or a RUU.exe file from HTC. They should work as well. I would not recommend a RUU below Supersonic 3.70. I'm going to upload some of these as well when I get a chance. I have like all of them.
Re: How to unroot the latest RUU (5.07)
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
CNexus said:
You should put "[GUIDE]" in the title, right now it seems like a question
Just a thought anyway.
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
Thanks for the advice. I'm currently re-uploading the sdk.zip file. Something went wrong with the PC36IMG file. It should be available again in a little while.
I wonder if you can help me?
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
---------- Post added at 09:12 PM ---------- Previous post was at 09:05 PM ----------
6foot5nbad said:
I have a problem with an Evo I got from someone, it mostly gets stuck in a bootloop but sometimes it actually boots all the way up. As your guide mentioned, I'm not able to RUU because its on the 5.0.7. I think the phone was rooted because it had a few .apk's that require root including su.apk. I did a factory reset while the phone was on a sprint account but it didn't fix the issue........ long story short, I noticed the bootlooping stopped when she got off the phone, so I figured the bootloop was caused by the data running through it or something. Today I turned the phone on and fooled around with it for about an hour before I decided to put it on my pageplus account because my verizon droid razr was stolen yesterday, as soon as I did the esn swap with the pageplus rep the phone started the bootlooping again. So I came across your post and luckily got the phone to boot up and began following your guide...... when i got to the "su" I didn't get "#" sign and permission was denied. I noticed the su.apk was not in the app draw so I downloaded it, I also installed root explorer to see if I get root access, no luck. Since then I can't get the Evo to boot up..... So finally my question, is it possible to execute your guide in fastboot or is there a way to push su through fastboot via adb?
Click to expand...
Click to collapse
BTW, Bootloader is still unlocked
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery /path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
CNexus said:
If bootloader is unlocked, flash a recovery through fastboot
Code:
fastboot flash recovery path/to/RECOVERY_NAME_HERE
Most likely RECOVERY_NAME will end with ".img" so the command would be like this:
Code:
fastboot flash recovery / path/to/recovery-evo.img
After that, search google for a "zip" file named "su-signed-efghi.zip", look for a hit on goo.im (search "evo 4g su-signed-efghi.zip") and download and place it on your sdcard
Boot into recovery (VolDown + Power, then user volume keys to navigate and power key to select recovery)
Then choose "flash zip" and locate the "su-signed-efghi.zip" file and flash it
You should now have the su binary installed in the correct place
Sent from my PG06100
Click to expand...
Click to collapse
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
update
6foot5nbad said:
Thanks for your quick response. Been trying that but its been going into a bootloop after I select recovery from hboot. Can't boot into recovery at all I was thinking about using adb to flash a stock recovery but all the recovery.img's i come across.... seem to be for an older hboot and/or system. Also I don't want to attempt anything that will make things worse. I've rooted dozens of Evo's on hboot 2.18 and I have a good Idea of how adb works. I'm wondering if that if I can manage to get S-Off will the phone be able to take an RUU then? or is there anyway to push a older flash_image to trick RUU into updating? I guess the question I should ask is what would you do if your evo would barely boot normally and couldn't get into recovery? the only thing that does work consistently is Hboot and I can't launch recovery through adb nor hboot.
Click to expand...
Click to collapse
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
---------- Post added at 01:22 AM ---------- Previous post was at 01:11 AM ----------
6foot5nbad said:
I found and exploit on TacoRoot that will get me temp root access without booting into recovery as long as I had an recovery log in /data/data/recovery/log (stock preferably). So I would greatly appreciate if someone can post the file here. I want to attempt to use the exploit to get temp root access then use this guide to get to the point where i can use an RUU.
Click to expand...
Click to collapse
Also, I would need help on how to push the recovery log file to /data/data/recovery/log if possible or would it simply be adb push log /data/data/recovery/ ?
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
CNexus said:
An RUU would only work if you had a lower or equal version on your phone than the RUU
As for your actual issue....you cant use adb while its in the bootloader, phone has to be fully booted if you want to do anything with adb
The only thing you can do while in hboot is to use fastboot
Try running:
Code:
fastboot reboot recovery
And see if that gets you into recovery
Sent from my PG06100
Click to expand...
Click to collapse
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
---------- Post added at 12:24 PM ---------- Previous post was at 11:59 AM ----------
6foot5nbad said:
Yes, I've tried -fastboot reboot recovery- in fastboot, just goes into a boot loop....... I did get the phone to stay booted overnight, I think as long as the battery is fully charged it stays on, and I can use adb now. The main issue now is that I can't boot into recovery therefore, like I mentioned it just goes into a bootloop and the battery discharges if I let the phone bootloop while trying to boot into recovery. Also, I noticed that the phone won't boot normally unless I have a full charge (Green Light). I think I just need the recovery log file, my thinking is if I can put the log file in the the correct location I can trick the phone into thinking it booted into recovery. If I can get temp root access then I use this guide to relock the bootloader and be able to use an RUU. Do you think that's possible?
Click to expand...
Click to collapse
I forgot to mention, the TacoRoot Exploit requires the recovery log file (http://rootzwiki.com/topic/13713-tacoroot-htc-universal-root-exploit-12-30-2011/) to be in /data/data/recovery/ directory, so it requires a user to boot into recovery to create the log file, and I can't boot into recovery.... so my idea is to push the recovery log file to /data/data/recovery/log cause thats where the exploit is looking for the log file. I'm hoping that will prevent me from having to boot into recovery which is where I'm getting stuck on the tacoroot exploit. With shortydoggs guide, I'm getting stuck at the "su" command cause the evo (for some reason) isn't rooted anymore. So my plan is to get me temp root with TacoRoot so I can get "#" and continue with shortydoggs guide. Not sure if that's possible but at this point its my only option since I can't get into recovery to flash su.zip nor can I RUU cause I'm on 5.0.7 which has no RUU.
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Sent from my PG06100
Thanks!!!
shortydoggg said:
I can give you the file, but it's hard to get it to work without that recovery. You have to extract out of the zip file and then push it to the /data/data/recovery directory. I tried it myself and I can adb push it, but when doing the tacoroot --root, I get an error "/data/local/tacoroot.sh: cannot create /data/local.prop: permission denied".
EDIT: I uploaded the two files that you need. You need to unzip the two files. Then push the log file to the /data/data/recovery directory, and the local.prop file to the /data/ directory. Getting them there will be up to you, as I'm not the most Linux educated person out there. I'm only able to push the files because my phone is already rooted. Hopefully you figure it out or someone more familiar with Linux (adb) commands can help you. Then, the "adb shell /data/local/tacoroot.sh --root" command is a breeze.
Click to expand...
Click to collapse
Thank you and CNexus. I'll try it and let you know how it went. I probably will fool around with it tomorrow sometime so I'll get back to you then. Going back a little, after I pushed flash_image and mtd-eng.img to data/local/, I noticed a blue status bar while in hboot, I'm assumming its searching for the pg36img.img update...... that said, is it necessary to push those files again?? BTW, great guide and write up. Thanks for everything. http://forum.xda-developers.com/images/smilies/good.gif
---------- Post added at 10:51 PM ---------- Previous post was at 10:46 PM ----------
Thanks for your help, I'll let you know how it goes tomorrow.
CNexus said:
Code:
adb push tacoroot.sh /data/local/tacoroot.sh
adb shell chmod /data/local/tacoroot.sh
adb shell sh /data/local/tacoroot.sh --setup
#should give an error after line above, its fine because you're pushing the local.prop yourself
adb push local.prop /data/local.prop
adb shell sh /data/local/tacoroot.sh --root
If anything goes wrong or it doesnt work, run this to revert
Code:
adb shell sh /data/local/tacoroot.sh --undo
I would've posted the tacoroot.sh for you since I use it in my shift utility to root your phone, but I wasn't sure if it was universal for all HTC devices or just for the evo shift. Sorry about that.
Thanks for your help, I'll let you know how it goes tomorrow.
Sent from my PG06100
Click to expand...
Click to collapse
Hi, Just wondering if you would mind re-uploading the original files? The link is broken, and I'd really like to unroot my phone, so it would be really appreciated. Thanks heaps!
I would really appreciate some help on this one... I attempted to flash the updated Mahdi Rom (09/20 build) this morning. I'm using the latest Philz Recovery if that matters. I performed the normal wipe procedure and when I went to flash the rom it told me the file was invalid. I think I might have tried to use a zip that wasn't fully downloaded.
I didn't have any other recoveries on my phone (I know... not smart) so I need to figure out how to flash a new rom without using recovery. I'm not completely hopeless and I'm willing to do what it takes to get my phone back!
Any help would be great! Thanks.
Have you tried adb? Your phone will be called sideload when you command adb devices.
Sent from my LG-D800 using Tapatalk
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Rogueharvest said:
I haven't yet been able to since I don't have access to a windows PC at the moment, just a MAC. Can it be performed there?
Click to expand...
Click to collapse
You can load adb on Mac. I believe there's a zip somewhere on xda with only the three files need, or download the package from Android. Place it in whatever your username folder is too make life easier. Also add ./ (dot slash) before every command.
Here's the command order for my setup.
cd Android/platform-tools
./adb devices
./adb sideload **DRAG FILE INTO TERMINAL**
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Update: I think I figured it out. The command prompt needed to be reinitiated.
Thanks again for you help! Moments like that are always a little scary!
Rogueharvest said:
Thank you for your help. I got ADB to load on my mac but it won't accept the prompt to sideload. Am I missing something perhaps?
Click to expand...
Click to collapse
Does it recognize sideload when you type ./adb devices? If not and you're in adb on Philz unplug/replug the charger.