Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Unless you have s-off or have flashed a new kernel, the system partition is right protected, even when you think it isn't. I think that is what is causing your problem.
Why don't you flash a room that already had root/busybix installed?
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
Sent from my HTC6435LVW using Tapatalk 2
c2a5nn1o4n said:
Hi well this is my second DNA trying to root destroyed the first one lol... Well anyways the first one I downloaded supersu and busybox and figured out it didn't work and I ruined it now.... This is my second phone I have flashed the superuser and binaries. I am figuring out that I have root but its not working correctly.. mostly my changes that I need root for are not lasting through reboot I'm not losing root but I'm losing my changes as in when I delete amazon its gone but when I reboot its back. my only assumption is that its because busybox is missing can anyone confirm this and is there any possible way where I can just get the busybox zip... I have been on the busybox.net website and seen the downloads but I would like confirmation before u destroy this phone to which I hope don't not happen.
Click to expand...
Click to collapse
When first unlocking and rooting my phone, I thought the same thing about busy box. But what you need to do is flash a new kernel first and foremost which will remove write protection.
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2[/QUOTE]
c2a5nn1o4n said:
I'm not really trying to flash a Rom yet personally I was waiting to see if liberty was coming but I guess it wont be coming I'm having a problem with pushing soffbin do I need do fastboot and soffbin in the same folder?
Sent from my HTC6435LVW using Tapatalk 2
Click to expand...
Click to collapse
[/QUOTE]
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access[/QUOTE]
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
c2a5nn1o4n said:
Flashing a Kernel is not flashing a rom. It just helps with battery, gives you sweep2wake, and allows you actual root access
Click to expand...
Click to collapse
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?[/QUOTE]
No, again, you need to flash a kernel first so that you have write permissions
c2a5nn1o4n said:
I'm thinking about flashing viper Rom it seems to be very stable will that fix my problem?
Click to expand...
Click to collapse
Reading your OP and the rest of your comments in this thread, you're all over the place. Things you are doing will not fix your original problem and trying to achieve s-off just because it looks popular and running into difficulties trying to achieve it only adds to problems and confusion. I suggest you step back, slow down and get familiar with terms before you break another phone. While a small portion of the info is EVO 4G specific, you should check these out for general knowledge:
http://androidforums.com/evo-4g-all-things-root/278898-android-partitions-kernels-explained.html
http://androidforums.com/evo-4g-all...ore-information-about-android-partitions.html
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
docnok63 said:
Your root is probably sticking in between boots. As we don't have any ROMs that free up the wasted space in the system folder, it's pointless for you to try to delete apps that you don't want installed. You can simply go into Settings\Apps\All and force stop them and then disable. If that doesn't work, you can use Titanium Backup and hit the middle "Backup/Restore" tab. Click on the app you want and Freeze it (this will stop it from running.) If that doesn't float your boat, you can try to uninstall it.
Click to expand...
Click to collapse
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
You're right. I had assumed he had unlocked and flashed an unsecure boot image before attempting to flash su and busybox. Perhaps I did assume too much. I'll refer him to here in that case.
UrGuardian999 said:
Anything he does with will not stick through the boot because he doesn't really have root access. I had the exact same problem before flashing a writeable kernel. After I flashed DSB 2.5.4 [when I originally was going through the process] that corrected the whole busybox/binaries issue. Using Titanium Backup at this point is pointless as well because after he restarts his phone, they'll all be back.
Edit: Plus it will say you have root without a writeable kernel but you don't have write permissions to have things like uninstalling bloatware stick through a boot.
Click to expand...
Click to collapse
Ok so I have to have busybox? I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
c2a5nn1o4n said:
Ok so I have to have busybox I've downloaded the viper Rom with the boot img I'm downloading cubed 3.1.3 kernal now so I just go into recovery and flash the kernal correct I'm a noon to HTC this is entirely different than by bionic
Click to expand...
Click to collapse
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
UrGuardian999 said:
The Viper Rom has Stock DSB Kernel boot.img zip'd with it. You can flash that rom and flash the Stock DSB modules with it and you'd be good to go
Click to expand...
Click to collapse
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
That's actually the opposite of what actually is the case. The modules are packaged with the rom and you have to flash the boot.img manually.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
c2a5nn1o4n said:
I downloaded the boot.img and the Rom then went to recovery and only the Rom was there how do I flash the boot img manually
Click to expand...
Click to collapse
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
c2a5nn1o4n said:
Nvr mind I understand but do I fastboot the boot img first or after I flash the Rom
Click to expand...
Click to collapse
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
The order doesn't matter
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Also on my other DNA I installed cynogen but not the bootimage and when I would try to reboot I would get messed up lines would that have caused that? If it would my brain has dropped to a new low
If using Cubed 3.1.3 you'll have to reflash the modules though, correct?
UrGuardian999 said:
If using Cubed 3.1.3 you'll have to reflash the modules though
Click to expand...
Click to collapse
Nope still on stock kernal
I'm currently flashing viper as well right now, had to stop and go to work right in the middle of it. My apologies hahah
Related
After installing Gingerth3ory and loving it, my friend then applied the speedtweak and i believe its in an undervolted setting that is causing the phone to powercycle. The phone cant go into recovery to reflash the rom to get rid of the tweak because the P50IMG.zip is still on the SD card, so HBOOT is trying to constantly update that. Is there any way to get rid of the tweak so he can boot up the phone?
Pull the SD card and delete the PG05IMG.zip either with another device or card reader
If you're bootlooping and you have the PG05IMG.zip radio file on your sdcard, the first thing you will need to do is get it off. Use an adapter so you can remove the file using a computer or place the sdcard in another phone and remove it that way. Either way, you need to get that file off to get to recovery to fix your bootloops.
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Ch0s3n0n3 said:
Okay he was just able to get the PC to recognize the sd card and pulled the zip. If he reinstalls the rom will that negate the settings of the speedtweak?
Click to expand...
Click to collapse
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Absolute_Zero said:
It would help if we knew what the "speedtweak" you are speaking of actually is. Either way, he can flash the rom then try to boot. If it doesn't boot then boot back into recovery and wipe data/cache. Flashing just the rom will probably work though if they were just clock/voltage related tweaks.
Click to expand...
Click to collapse
Sorry it was Script Fusion, and yes it was a undervolt and overclock tweak. I had him reflash and it seems all is well. I also told him to delete the Script zip until he reads further and learns about it. I really appreciate your help as I am fluent in Droid X not Thunderbolt lol.
Bad timing (almost a pun)
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
ProfEngr said:
So far I'm having zero luck getting out of the boot loop. Tried hboot w/ the ROM as PG05IMG.zip in the root; no go. Tried wiping cash/data/dalvik in CWR; no go. Tried reflashing the ROM via CWR; reboots before it can complete the operation. Anything else I can try? I guess there's no way to get to the init.d file to wipe the changes made by speedtweak?
Tried the "Normal" setting in speedtweak and that's what started everything.
Click to expand...
Click to collapse
bootloader flashing isn't for the rom. It needs to be flashed in CWR as you later tried. At this point, the only thing you should be naming PG05IMG.zip, placing on your sdcard, and flashing is a radio (if you need to upgrade). But even then, you should have a booting rom first (not mandatory but encouraged).
You are able to make it to recovery, wipe data/cache, and flash a rom? At what point does the flash fail and is there an error reason stated? If you're in recovery the only thing that should be "preventing" the rom from flashing is the rom itself. The speedtweak files should already be gone before the rom even starts flashing since at that point /data, /cache, and /system have already been wiped.
You could try manually wiping each of those partitions multiple times (which never made complete sense to me) or download another rom or another copy of the current rom and try flashing it.
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
ProfEngr said:
I got help from an IRC chat. Reloaded the 'upgrade' PG05IMG from the Tbolt root thread via hboot. That got me back online to where I could reflash.
Just for reference though, it was rebooting itself about 30sec into the ROM flash after the ROM notes/info scrolled on the screen.
Click to expand...
Click to collapse
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Absolute_Zero said:
That is weird. A tweak script that forces you to reflash firmware from the bootloader to fix it? Hmm, I suppose I should look up what this SpeadTweak script actually does for future reference. Either way, glad you got it fixed.
Click to expand...
Click to collapse
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
If I understand your terminology, I need to make a clarification.
The phone was stuck in a loop that would make it as far as the 1st HTC boot screen, buzz, hang, then restart the sequence. I was only able to wipe in CWR. It would reboot shortly after starting a ROM flash. hboot still worked as normal.
I'll look into how to flash just a kernel in case this happens again (HOPE NOT!!!)
For another discussion... After I got things sorted and reflashed the MR2 radio, CWR gives me an error when trying to format /system during Nandroid restore of any of my previous backups.
joshnichols189 said:
No.. Speedtweak.sh is built into imoseyons kernels and it allows you to control your kernel frequencies and governor. You don't have to install via hboot to remove it, all you need to do is flash a new kernel, even one that has Speedtweak.sh would be fine because you need to activate it manually through terminal.
I'm not sure why the OP was rebooting in recovery, that's what all of the phones that were reported as bricks were doing, but they were also rebooting in hboot which the OP wasn't. Obviously it wasn't a brick, but the Speedtweak script doesn't need to be removed via hboot, and it's just weird that the OP was rebooting in recovery.
Sent from my ThunderBolt using XDA Premium App
Click to expand...
Click to collapse
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Absolute_Zero said:
It was my understanding from their posts that they couldn't even flash anything. If it's the kernel itself or even init or bash scripts then flashing the rom clearly would fix that but it does little good if your phone reboots before you can even flash something.
Still not clear on what caused the problems of the two users here but the common denominator was that SpeadTweak script which as I said, someone would need to review to determine what may be causing the problem.
Click to expand...
Click to collapse
I'm by no means saying you're wrong or anything, I was just letting you know what the speedtweak.sh script was since you had mentioned you weren't completely sure. I'm also unsure as to what was amiss with their phones, I just noted that the people who had bricked their phones (via one way or another), were rebooting in recovery, and that's the only time I had heard of rebooting in recovery. Obviously his hboot was fine, it's just very strange that recovery was rebooting because from my understanding recovery uses a completely different kernel than the main ROM.
Nice(?) to know I have a few people scratching their heads over this. Probably won't work, but I'll try to keep out of trouble on this until someone posts what's up.
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
loonatik78 said:
That sounds like the boot loop issue that people were having before the MR2 radio came out, doesn't it?
Click to expand...
Click to collapse
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
joshnichols189 said:
If don't know what issue you mean, there was a bricking issue but this isn't a brick
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
What they were calling a brick really wasn't much of a brick by definition A) because all it did was boot loop, and B) it was recoverable.
We've tested and can confirm this bootstrap recovery is working. Thank you to bane449 for testing. The recovery is a straight APK pull from the Droid X2. Worked thanks to the similarities between devices.
Instructions and download:
http://briefmobile.com/motorola-photon-4g-root-custom-recovery-now-available
Looks successful to me: DroidX2 Recovery GFAN.COM V2.5.1.8
And it booted back into Android properly, even
So what will this allow me to do? What are its advantages? What are the risks?
sub2k1 said:
So what will this allow me to do? What are its advantages? What are the risks?
Click to expand...
Click to collapse
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Forgive my ignorance but what is a "pseudo-Rom"?
kennethpenn said:
CWM allows users to easily install unsigned update packages. This will open up the Photon to pseudo-ROMs, all sorts of modifications, and more.
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
10 chars
I know what ROM's are, never heard anyone say psuedo-ROM.
Lokifish Marz said:
Custom ROMs (if available for the Photon) like MIUI, CM7 etc...
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
mikeyinid said:
I know what ROM's are, never heard anyone say psuedo-ROM.
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Psuedo meaning "not really" a ROM. A locked bootloader will prevent true custom ROMs, but P-ROMs will be possible.
P-ROMs are based off of stock files and modifications. They don't replace the kernel or modem.
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
b-reezy said:
I can't seem to get mine to reboot into CWM. I run the apk, hit install recovery, says installed sucessfully, hit recovery mode and it reboots back into system.
Click to expand...
Click to collapse
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
kennethpenn said:
Make sure your device is plugged into the wall charger when you do Reboot Recovery. That's the only way it'll work since it's a bootstrap recovery.
Click to expand...
Click to collapse
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
brianez21 said:
Can you explain why this is? I'm a little confused as to what makes a "bootstrap recovery" different from a regularly flashed "recovery.img".
Click to expand...
Click to collapse
Caveats:
This is not a *real* recovery. The way this recovery works is by hijacking portions of your boot process during system initialization and starting into recovery instead. So, if you hose your system *COMPLETELY* you will need to SBF. Specifically, if your logwrapper, logwrapper.bin, or hijack binary are missing from /system/bin, you will be screwed.
This is from koush himself concerning droid x/2 bootstrap. I would seriously wait til an sbf surfaces before flashing any of these "psuedo-ROMS" or even just deleting any system apk's. Just my opinion.
sub2k1 said:
Yup i installed this and rebooted into recovery mode. It worked just fine for me. What happens if Sprint releases an OTA update? Can i recover root access or downgrade with this? Sounds like I can't because I can't modify the kernel.
Sent from my MB855 using XDA Premium App
Click to expand...
Click to collapse
Does the phone need to be rooted first in order to installl this recovery apk?
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
mediawiz said:
Is this "ClockworkMod" recovery, or something else? If it's CWM, what version?
Click to expand...
Click to collapse
This is CWM bootstrap. Original one was on the Droid X, created by Koushik Dutta. Then it was ported to the Defy. Then to the Atrix. Next, the Droid X2. Now, the Photon 4G.
V2.5.1.8
Sbf is gonna be your friend when it comes to unrooting and restoring. It will pop up soon.
sub2k1 said:
So what specifically did this do to my phone? What files were modified to allow this to run at bootup? Anybody have any info on this (just in case I want to return my phone to stock.)
Click to expand...
Click to collapse
Sent from my MB855 using XDA App
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
beartrap said:
Once I'm in CWM, is it safe to unplug the charger or does it need to be connected until I exit and reboot?
Click to expand...
Click to collapse
You can unplug.
Sent from the best phone yet!
Okay ive tried rooting this phone like 3 times and i get the same message,
here is a pic hope someone can help,
http://i44.tinypic.com/10f2u87.jpg
Search for super one click root. Use that.
Sent from my SCH-I500 using xda premium
Give Droidstyles guide a try. It is very simple and easy. I swear by it, used myself quit a few times
Sent from my SCH-I500 using XDA App
If you are going to flash another rom don't even bother rooting, there is no need.
It looks like the file system isn't writeable, usually running "adb remount" first will make the file system writeable.
OhioYJ said:
If you are going to flash another rom don't even bother rooting, there is no need.
It looks like the file system isn't writeable, usually running "adb remount" first will make the file system writeable.
Click to expand...
Click to collapse
ok so what would i do if i want miui rom?
am lost i dont get how to flash roms?
i tried 4 and none work all give errors
Are you trying to use ROM MANAGER by chance?
Sent from my SCH-I500 using XDA App
To be honest, it might be easier flashing a custom ROM via odin that's already rooted. Or you can flash CM7. Should take about 10-20 minutes once you have everything you need downloaded.
cj316x said:
ok so what would i do if i want miui rom?
am lost i dont get how to flash roms?
i tried 4 and none work all give errors
Click to expand...
Click to collapse
You need to flash CWM recovery fixed for CM7 using Odin. Then you need to 3-finger into recovery. If the phone boots you'll have to reflash recovery again. The stock kernel reflashes recovery every boot. Once in recovery you can flash Miui.
Miui is what I run, I would recommend you use 916 with JTs 1016 kernel. Or 1028.1 with It's included kernel, or his 115 kernel. 916 Miui is consider the most stable version. I've found 1028.1 to be extremely stable as well. 11-11 wasn't as stable for me so I went back to 1028.1
As icemanwbs said, look up my guide in the general section. just replace cm7 file with miui...seriously it works and is easy to follow. refer to section 3
http://forum.xda-developers.com/showthread.php?t=1238070
Well, two days ago I decided to put ICS on my Amaze. Previous to ICS I was Rooted with S-ON, and Unlocked.
I followed the instructions on the Development section to install ICS on my unlocked, S-ON Amaze. However after I installed CWM, and flashed Superuser, Titanium Backup, or any other root app says I don't have root privileges.
From what I understood, once SU was flashed, the device would be rooted.
I used the All In One Kit to put the CWM Recovery, and flash the SU. I did HTC Steps to unlock the phone (which the AIO Kit helped also)
I tried looking for a solution or something before posting, but I couldn't find one in the 80+ pages of the ICS thread in the Development section.
Thanks in advance!
I initially had an issue flashing Superuser-3.0.7-efghi-signed.zip (found here http://forum.xda-developers.com/showpost.php?p=20992340&postcount=4) because I didn't toggle the signature setting in recovery. Perhaps it didn't flash correctly? Make sure it said it was successful at flashing the zip.
Flash it again.
Wait....I sent this with Tapatalk?
I realized that my tool didn't set the SU permissions. I have to fix that. Just flash the SU zip file and it'll be fine.
jcparks said:
I initially had an issue flashing Superuser-3.0.7-efghi-signed.zip (found here http://forum.xda-developers.com/showpost.php?p=20992340&postcount=4) because I didn't toggle the signature setting in recovery. Perhaps it didn't flash correctly? Make sure it said it was successful at flashing the zip.
Click to expand...
Click to collapse
Got it working! Thankss!!
Please keep all question based threads in the Q&A section.
Thread Moved.
Sent from my Galaxy Note i717, using XDA Premium.
You don't have to be a farmer to know what sh*t smells like.
is there anyway to root your phone with ics on it ? my phone was unrooted b4 i put ics on it.
the show stopper said:
is there anyway to root your phone with ics on it ? my phone was unrooted b4 i put ics on it.
Click to expand...
Click to collapse
You sure can. Detailed instructions posted in development section. Basically you need to unlock bootloader through HTC, flash a custom recovery, load up the superuser zip, then flash it in your custom recovery. More details are given in other posts already.
Sent from my HTC_Amaze_4G using xda premium
Just going to throw this out there. I flashed superuser after installing ICS to get root. It works for most applications, but one app that it doesn't work with is LuckyPatcher (to get rid of those stupid ads in my other apps). For LuckyPatcher to work, I had to install superSU (can be found from the play store). It seems to be my default root app now.
kered424 said:
Just going to throw this out there. I flashed superuser after installing ICS to get root. It works for most applications, but one app that it doesn't work with is LuckyPatcher (to get rid of those stupid ads in my other apps). For LuckyPatcher to work, I had to install superSU (can be found from the play store). It seems to be my default root app now.
Click to expand...
Click to collapse
Did u install busybox after flashing su by chainz?
Sent from my iced out HTC Ruby
glacierguy said:
Did u install busybox after flashing su by chainz?
Sent from my iced out HTC Ruby
Click to expand...
Click to collapse
Yep, LuckyPatcher didn't like it. Installing SuperSU took care of it, and it works fine with all of my other apps.
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle