Database Users

Working Superuser for TB Sense

This is actually relevant to more than just the Thunderbolt. It fixes Superuser problems with numerous newer Sense releases.
http://forum.xda-developers.com/showthread.php?t=886999
My su binary is already being provided via the root thread but the matching Superuser is not. Without the matching patched Superuser, you'll see FCs when apps request root if the Superuser app itself is open.
Just apply the update zip from the aforementioned thread to fix it. ROM builders should use my patched version as well.

Please update to this, I will be fixing the tutorial as soon as I can, and noting it here.

Rafi, good to see you on the bolt. Looks like we will get a virtuous Rom too. Ran your Rom on the inc till I got run over by the desire z, hd craze.
Sent from my Thunderbolt!

Hmm, not sure if I should do this. I ran fix permissions in Rom Manager and it seemed to take care of all the problems. Everything's been working fine since then. What do you guys suggest?

i see no reason to mess with it if your set up is currently working

jacobk said:
i see no reason to mess with it if your set up is currently working
Click to expand...
Click to collapse
I agree - however, in my case, nothing was solving the FC's - so I put in this SU and all is right with the world.
I think it's worth trying if all other permissions methods are failing - it certainly "feels" more stable.

This fixes su issues while the superuser app is open.
Flash it.

Thank you rmk & jcase

even aftere re rooting fix my su issue i ran this and i feel su runs wayyyyy smoother now for apps that need su.

jacobk said:
i see no reason to mess with it if your set up is currently working
Click to expand...
Click to collapse
There is simply no way any newer Sense ROM works correctly without this patched version. You *will* ultimately encounter issues.
Don't believe me, try this. Open up the Superuser app itself, connect via adb shell, su system, su root. Observe hang. This is just an example, there are numerous other ways to have the issue occur.

RafficaX said:
even aftere re rooting fix my su issue i ran this and i feel su runs wayyyyy smoother now for apps that need su.
Click to expand...
Click to collapse
Good. maybe you can apologize now in the debloat rom thread instead of trying to smear my name.

can you just post it in here...i dont like guessing games...i see 2 links to pull requests on github...i dont know wtf that means. some of us dont speak computer 120% fluently..

MYxdaUSERNAME said:
can you just post it in here...i dont like guessing games...i see 2 links to pull requests on github...i dont know wtf that means. some of us dont speak computer 120% fluently..
Click to expand...
Click to collapse
Haha scroll down the page!! There's a flashable zip
sent from my Thunderbolt

for christ's sake...big blue letters. i thought that was the top of his sig..but he lost me at github.
good to go...i do remember a few force closes that never amounted to anything serious last night...

doodoostains said:
Hmm, not sure if I should do this. I ran fix permissions in Rom Manager and it seemed to take care of all the problems. Everything's been working fine since then. What do you guys suggest?
Click to expand...
Click to collapse
This was working for me until I rebooted. Once I did, everything was back to how it was.
I just applied the patch, restarted. VOILA! SU is working again. Thanks rmk40!

Superuser is acting up after working fine earlier. How can i boot into clockwork without rom manager anyone? thanks

frodsteamin2 said:
Superuser is acting up after working fine earlier. How can i boot into clockwork without rom manager anyone? thanks
Click to expand...
Click to collapse
Turn off phone. Hold volume down when booting up.
Sent from my ADR6400L using XDA App

Was able to get into CWR after a reboot, flashed. Thank you!
Edit * this fixed all my issues. . Thanks again

evilmunkeh said:
Turn off phone. Hold volume down when booting up.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Thank you for the response, my newbness was the problem as there was a file on sd card that keep trying to install when trying what you mentioned above.

Still getting FC's in SU after flashing... Did I miss something?
Never mind, fixed after running a program that required root.
Thanks!
Sent from my ADR6400L using XDA App

Trouble with root

Ok, so I ran the superoneclick and it says it was successful and I have superuser on my phone but if I try to use any root programs like titanium backup it says I'm not rooted, any suggestions?

Super oneclick only gives you temporary root, so after you reboot you loose root. On most phones it gives you permanent root but the way the kernel is designed on the intercept it doesn't work. There is an app in the intercept 2.2 development thread at sdx-developers that gives you permanent root and flashes cm recovery to allow you to flash zips to install mods roms and themes!!easy to use!!
Sent from my SPH-M910 using Tapatalk

Jstew83 said:
Ok, so I ran the superoneclick and it says it was successful and I have superuser on my phone but if I try to use any root programs like titanium backup it says I'm not rooted, any suggestions?
Click to expand...
Click to collapse
Would highly recommend you click over to the dev section - link posted that will give you perma root. Quite simple to do.

b_randon14 said:
... the way the kernel is designed on the intercept it doesn't work. There is an app in the intercept 2.2 development thread at sdx-developers that gives you permanent root and flashes cm recovery to allow you to flash zips to install mods roms and themes!!easy to use!! ...
Click to expand...
Click to collapse
I was wondering why my Intercept wasn't holding root... one thing about that app: you have to change the .ch (or is it .sh) files to use stl5. They're written for stl9.
Also, I've used this app about 50 times on my Intercept and it's not working. Its just adding more files to my phone, causing it to slow down more. If it doesn't work and you want a break, use adb shell to delete the files added. I tried using SuperOneClick in combination with the SDX app and that didn't work either. My suggestion is to use SuperOneClick for temp root and flash a rooted kernel and ROM, which is what I'm going to do at some point.
Sent from my SPH-M910 using Tapatalk

caderyn19 said:
I was wondering why my Intercept wasn't holding root... one thing about that app: you have to change the .ch (or is it .sh) files to use stl5. They're written for stl9.
Also, I've used this app about 50 times on my Intercept and it's not working. Its just adding more files to my phone, causing it to slow down more. If it doesn't work and you want a break, use adb shell to delete the files added. I tried using SuperOneClick in combination with the SDX app and that didn't work either. My suggestion is to use SuperOneClick for temp root and flash a rooted kernel and ROM, which is what I'm going to do at some point.
Sent from my SPH-M910 using Tapatalk
Click to expand...
Click to collapse
Hmmmm sounds like you are making things more complex then they actually are - took me about 5 seconds to gain perma root without any file name changes.

entropy.of.avarice said:
Hmmmm sounds like you are making things more complex then they actually are - took me about 5 seconds to gain perma root without any file name changes.
Click to expand...
Click to collapse
That's me! I did that with my Wii also lol!
The OneClickRoot program just isn't working for me. I only mentioned the stl5 thing because someone else mentioned it in the SDX thread hosting this program, figured I'd mention it because it's several posts in. I changed mine because SuperOneClick said my mount point was /.../.../stl5 (the ...s are directories I don't remember).
[EDIT] Instead of doing all that, try the post below me. if that doesn't work, just break it down and do it manually... Flash a rooted kernel, then recovery, make your backups, then flash custom roms. I was using all stock when I first wrote the post, but now I'm using SlapKernel, bROM, and CM01 recovery. I WAS making it too complicated lol!

caderyn19 said:
That's me! I did that with my Wii also lol!
The OneClickRoot program just isn't working for me. I only mentioned the stl5 thing because someone else mentioned it in the SDX thread hosting this program, figured I'd mention it because it's several posts in. I changed mine because SuperOneClick said my mount point was /.../.../stl5 (the ...s are directories I don't remember).
Click to expand...
Click to collapse
So strange. Try this: worked for me, all you need to do is check allow non market programs in your settings, download and install this apk - run it and gain perm root. Does this work for you?
http://forum.xda-developers.com/showthread.php?t=1135825

yes that may work

caderyn19 said:
That's me! I did that with my Wii also lol!
The OneClickRoot program just isn't working for me. I only mentioned the stl5 thing because someone else mentioned it in the SDX thread hosting this program, figured I'd mention it because it's several posts in. I changed mine because SuperOneClick said my mount point was /.../.../stl5 (the ...s are directories I don't remember).
[EDIT] Instead of doing all that, try the post below me. if that doesn't work, just break it down and do it manually... Flash a rooted kernel, then recovery, make your backups, then flash custom roms. I was using all stock when I first wrote the post, but now I'm using SlapKernel, bROM, and CM01 recovery. I WAS making it too complicated lol!
Click to expand...
Click to collapse
damn glad you got it running - you are further then me now on my Intercept - all I have is root so I can use my 3g as a wifi hotspot for my Acer Iconia a500 tablet need to look into custom roms for the intercept, the Virgin Mobile stock 2.2 is so slow :-(

Stock is somewhat slow. Make sure you read the directions though with rom flashing. I messed up my phone for a few hours from not doing the steps correctly with a certain rom. All sorts of fun! I flashed a rooted stock kernel from sdx, as well as stock rom (idk if roms are rooted? Its depends on the kernel right? Ill google it...) and a kernel package that has some tweaks to the stock (or any) kernel. I gotta say, adding Zeam launcher to a rooted and tweaked stock is running quite well for me.
Sent from my SPH-M910 using Tapatalk

Bricked Nexus S

I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark

You can mount your sdcard from recovery, there is an option for mounts in the first menu. Then transfer whatever file you want to flash.
Sent from my Nexus S using xda premium

It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.

Please post the exact model of your phone and the exact file you flashed, and the exact CWM recovery file you flashed.

Also, if you can get to recovery you haven't bricked your phone
If you haven't done it already I'd also flash superuser. If you are after a stable ROM based on CM7, I'm using NSCollab 1.0.39 and works very well.
Sent from my Nexus S using xda premium

mcdanish said:
It doesn't work. Ther phone shows up for a split second in Windows file explorer and then closes again.
Click to expand...
Click to collapse
Which drivers do you have installed, just the ones from the Android SDK? what Windows do you have?
Sent from my Nexus S using xda premium

mcdanish said:
I am in a bit of a pickle. I rooted my brand new Nexus S, but in the excitement, I accidentally flashed a kernel for Cyanogenmod first instead og the ROM first, THEN the CM7. Now it won't go pass the unlocked bootscreen. I have searched for solutions, but can't find any. If only the Nexus S had a SD card, I would know what to do, but how do I get a stock kernel transferred to the phone when I can only get it into Clockwork mod? I tried factiory reset and all, but it is not the problem, it is the kernel. I can get into CWM but nothing happens when I try to mout USB storage to transfer files and/or new kernel..... Help, anyone? Please?
Benny. Denmark
Click to expand...
Click to collapse
when you flashed cyanogenmod after flashing the kernel, cyanogenmod automagically overwrote the kernel that you flashed first, so thats not the issue. try wiping data, then reflash cyanogenmod and the gapps.

simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.

mcdanish said:
simms22, the issue occurred because after flashing the kernel, I could not flash anything because it just halted on the Google screen with the open padlock. I have now uninstalled and reinstalled the Samsung drivers, and it helped, I then could see the phone in Windows Explorer and was able to transfer a new kernel and a new ROM, which actually was the NSCollab which I like because of the speed. Thanks all for helping me out. Have a nice one.
Click to expand...
Click to collapse
ahh, i misread what you wrote. im glad that it got straightened out anyways

Good to hear
NSCollab 1.0.39 is pretty stable with the Matr1x 5.5 kernel it comes with and you'll notice a better battery life too.
Sent from my Nexus S using xda premium

[RECOVERY] Clockworkmod Recovery TOUCH 5.5.0.4 | everything works except adb (5/15)

I am currently working on porting gweedo's touch recovery to the touchpad. So far I have a working clockworkmod 5.5.0.4 with the cool battery percentage mod but the touch part is not ready yet.
I just wanted to release this as a fully functional recovery (except adb).
1) boot into clockworkmod
2) mounts and storage >> mount /boot
3) adb push uImage.CWMRT5504 /boot/uImage.CWMRT5504
4) reboot and see it in the moboot menu
The touchscreen driver doesnt work but this is a completely working clockworkmod recovery (backups, restore, installing zips, etc.) (except adb)
Thanks
uImage.CWMRT5504 (install file)
LINK: HERE
KNOWN ISSUES:​
- touchscreen doesnt work (yet)
- adb doesnt work in recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Changelog:
- fixed the mount points to be a fully functional recovery. (thanks gdanko)

Pretty cool man!
Sent from my Touchpad using xda premium

good job man
Sent from my SGH-T989 using xda premium

I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?

Can't wait to try this out. Keep the work going.

Can someone post mirrors for the downloads. They are both down.

LinuxNewb said:
I played around and it works pretty well! No bugs that I could find.
The only feedback I would give is that when you flash ROMs it sucks that the soft touch keys on the screen get in way of a lot of the wording. The horizontal blue line also would strike through words and it looks cruddy.
Any way to change where the message output is placed?
Click to expand...
Click to collapse
this should be fixed in this beta 14. and also the links are updated to an unlimited bandwidth server.

I hate to be "that guy," but I looked into this before and I don't think you can get the touchscreen working. On the TouchPad, the screen is controlled by a userland-based driver versus a kernel based driver. That's swell, but since CWM is basically only a kernel, it can't load the driver. I'd love to have someone prove me wrong, really. I just couldn't figure out a way to load it on CWM
Also, you're compiling it wrong if it only works temporarily when flashed. I believe that's like "make kernel" (or the equivalent, it's been awhile lol). I can'r remember the correct command, but I might have solved it by compiling CM and then removing the recovery portion? *shrug*
Good luck, though! I meant this to be taken as someone sharing their knowledge to help others, not as a deterrent. Please, continue with this and make an awesome CWM!

I'm not a kernel/recovery dev so I wouldn't even know where to begin looking at this but I know there was a touch based recovery back before CM9 called TeamWin Recovery Project (TWRP). Maybe it might help to look back at how they got it working and see if the same process can be used for CWM?
Here's the link to the original thread with TWRP thread.
http://forum.xda-developers.com/showthread.php?t=1400649
Hope it helps. I would like to see this work. I love the touch based CWM on my GNex.

Is this still in development?

so finally got mounts to work so this is now a fully functional recovery. the only things not working are the touch options and adb. once i get ts_srv to initialize then swipe gestures will finally work. but for now its still at least a good recovery.

So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA

blckngldhwk said:
So everything in the touch recovery works besides the touch?
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.

sk8erwitskil said:
LOL not sure if you are trying to be a smart-a** or honestly asking. you must not be asking for reals since the OP answers that question.
its still an updated CWM from the original 5.0.2.6. so its still better than the one from before.
Click to expand...
Click to collapse
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.

famewolf said:
Well in the previous post he mentions adb does NOT work in this new version and I'd consider that a critical part of recovery. Any info on progress related to that? Great work.
Click to expand...
Click to collapse
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA

you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest

sk8erwitskil said:
Yes I agree that adb is a critical part. I'll be looking at init.rc to why adb isn't starting. Just haven't had a chance yet.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
You may want to search on "Aroma File Manager" (gui file manager you kick off from within recovery by installing the .zip) and see if you can potentially add a direct link to it in recovery...that would be VERY useful addon nobody else currently has as aroma file manager is relatively new.

The aroma touch installers are on most of the roms for my Xperia Arc. I wouldn't say nobody's using them yet as its the latest trend amongst developers. An aroma installer could benefit the touchpad community for those who want to choose what they do and don't want in the rom. But I'm gunna assume for the moment that if a touch recovery won't recognize touch that aroma probably won't work either.

Matt Devo said:
you should really edit the main subject line, since no adb and no touch do not equal "FULLY WORKING RECOVERY." Not sure why anyone would bother using it at this point to be honest
Click to expand...
Click to collapse
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA

sk8erwitskil said:
Well it is a fully functional recovery. Any recovery aspect you need (backup, restore, install, fix permissions) ALL work. Therefore, it's a working recovery. Touch is an extra and not a requirement to use recovery. So next time you should try thinking before you put down your ignorant ideas.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yes but you say Fully Working and Touch... well if adb is nonfunctional then its not FULLY functional and if Touch isn't working then its not TOUCH then is it... so yes... the thread should be pulled or the title modified
Sent from my cm_tenderloin using Tapatalk 2

[Q] hyperdrive stuck at splash screen

I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?

I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.

motel6man said:
I hate to double post but if anyone has any ideas as to why this is happening I'm going to try and redownload and try loki patch I don't know if it's needed but I will try.
Click to expand...
Click to collapse
Same problem here,
I'm going to try and install a kernel through TWRP. I've tried a fresh root / loki install, same issue.
For me, I remember having to install an AT&T compatibility pack.zip file on previous Hyperdrive releases, like RLS 10.
I tried to install RLS15 and at the very end of install, it says this:
Flashing Kernel
file_getprop: failed to stat"/tmp/aroma/kernel.prop": No such file or
directory
However, for some reason, after trying to install this new release, I was not able to restore data in TWRP from a backup of RLS 10. I was able to restore to a non-rooted backup (i don't know how), and it appears that I am not rooted anymore, and I don't think I have superuser anymore. So, I'm not exactly sure where to start.

Glad to see I'm not the only one this is happening to. Please let me know if you figure it out. I noticed the same thing but thought I seen someone else say that it was nothing.

so i redownloaded all files and nothing. tried loki patch and nothing. tried kt kernel because i seen another post with someone saying it was the only one that worked for them and nothing. im still stuck on splash screen. please if anyone knows how to fix this please let me know im desperate now. i really want to try this rom so any help would be greatly appreciated. thanks

Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?

Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium

d9vabder said:
Same here =/
Flashing a kernel before ROM didn't do anything.
I'm starting to think that we don't have Super User installed anymore, I tried re-installing some BackUps (rooted backups)
and TWRP said something like, you don't have SuperUser instyalled, want to install it? *Slide to Install* Phone quickly reboots (not showing any proof of Super User being installed in TWRP emulator) and still no effect.
When I get some time ill look into how to install SuperUser, which I thought was already put on when we root.
Have you tried installing any other ROMS with success?
Click to expand...
Click to collapse
I haven't tried any other roms yet. I haven't really seen any that I liked.
d9vabder said:
Are you still on MDL? I am, and im starting to think i need to just go ahead and do the update from AT&T, and then switching over to Safestrap recovery, but i hope i can find another solution before doing all that.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I'm still on mdl. I'm going to keep looking around for a solution. Please let us know if you found a way to fix it.
Also heres a screen shot of my info

motel6man said:
I've tried asking this in the q&a section on the main thread but I think I'm being ignored because I'm asking a question about the at&t version inside a Verizon thread. Idk. But I've tried installing hyperdrive rls15 and I follow the instructions on the main page for at&t and I get to where I need to reboot and wait 10 mins. Well it just stays on the splash screen. I've tried repeating the install 4 time's now amd the same results. I found a tooic saying fix permissions but it fails. I'm sorry if this has been asked already. I have looked through several different threads but I may have overlooked it. My phone baseband is I337UCUAMDL im on 4.2.2 and have twrp v2.5.0.2 as my recovery. I've also verified the md5. any suggestions?
Click to expand...
Click to collapse
Are you using Safe strap?
I was having the same problem after like 4 tries i figured out that every time I would download this it would go into the internal memory when it should have gone into the xd. I had to move folders manually. After that everything has been working correctly.

Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium

d9vabder said:
Do you know what folders have to be moved and where?
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
I created a new one on the xd card named it roms so I won't forget.

All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium

d9vabder said:
All I did was go to Mounts in TWRP recovery and mounted my microSD card and this fixed the problem.
Sent from my SAMSUNG-SGH-I337 using xda premium
Click to expand...
Click to collapse
cool im going to go try it in a few mins thanks
i tried mounting both internal and external and still nothing can you go through the steps you did from start to finish maybe im missing something

Okay, so the first thing i did was mount my microSD(external sd) then a full wipe. Even though i was mounted to my sd card, i still had to navigate to my internal memory to select the zips i wanted to flash. I first installed an older release of Hyperdrive Rom, and during installation, i selected Full Wipe option again. i also added my AT&T compatibility pack.zip to be flashed right after the ROM. Also, i dont know if this affected anything, but i tried installing the T-Mobile compatibility pack on a previous attempt. I read somewhere where some1 did this and it worked for them, but it didnt work for me until i did another install of RLS15 and the ATT pack.
Hope this can help you
Sent from my SAMSUNG-SGH-I337 using xda premium