[Q] Already Rooted Honeycomb Preview v4 Exists? - Nook Color General

Is there an already rooted version of deeper-blue's Honeycomb preview image v4 anywhere?
I'm at wits end getting connected through ADB to my NC on my Laptop (running Ubuntu). I've tried about every walk through I can find. Including the one on NookDevs. I've had no issues connecting to other devices through ADB in the past.
I'd love to be able to use adbWireless. However I have to root before I can do that which requires ADB access ...
So I was just curious if there's an "already rooted" image floating around anywhere? I couldn't find one on XDA. I figure if it's not posted here it doesn't exist. I thought I'd ask though.
Edit: Looking for one that boots off of the SDCard

Like this?
http://forum.xda-developers.com/showthread.php?t=947071

Keep in mind to use that su update. The one in that link had a advertisement line if code after requesting su so it messes alot of stuff up. The su update is in a cm7 gapps thread in android development
Sent from one of those missing Droids

RickOSidhe said:
Like this?
http://forum.xda-developers.com/showthread.php?t=947071
Click to expand...
Click to collapse
I was actually looking for one that boots off of the SDCard. Sorry I should have specified that. I've updated my first post. I'll most likely flash to internal memory when the official Honeycomb source is released and there's a final version.
altimax98 said:
Keep in mind to use that su update. The one in that link had a advertisement line if code after requesting su so it messes alot of stuff up. The su update is in a cm7 gapps thread in android development
Sent from one of those missing Droids
Click to expand...
Click to collapse
Thanks for the heads up on that.

Related

Android Developer New Nexus One Owner Questions

Hi everyone, I am a somewhat new Android Developer, I am in the final stages of developing my first Android application targetted at 2.1/2.2 with a MinSDK version of API 5.
I just purchased a Nexus One directly from Google the GSM 3G 900/AWS/2100MHz version that is supposed to work with T-Mobile, but I did not sign a T-Mobile contract.
Here are my my questions,
1.) Is my phone unlocked?
2.) What is the easiest way to get a rooted 2.2 (Froyo/API Level 8) Android OS?
3.) Does ADB work out of the box?
Thanks a ton,
JBDynamics
JBDynamics said:
Hi everyone, I am a somewhat new Android Developer, I am in the final stages of developing my first Android application targetted at 2.1/2.2 with a MinSDK version of API 4.
I just purchased a Nexus One directly from Google the GSM 3G 900/AWS/2100MHz version that is supposed to work with T-Mobile, but I did not sign a T-Mobile contract.
Here are my my questions,
1.) Is my phone unlocked?
2.) What is the easiest way to get a rooted 2.2 API 8 Android OS?
3.) Does ADB work out of the box?
Thanks a ton,
JBDynamics
Click to expand...
Click to collapse
Wrong section!
Should be Q&A (third in 10 minutes!)
Im from France so I'll skip the first one (but it should be unlocked).
2. rooted API? I don't know what it means, but just install the latest SDK and a 2.2 ROM
3. adb is runing on the phone, just activate "usb debugging" in Settings/Applications
adb is in the android-sdk/tools folder
hope it helped a little
leonnib4, thanks for the info. As long as ADB works, then I should have an elevated shell (super user shell) just by issuing 'adb shell' then I should be able to run commands with su. Thanks! Basically, I need to be able to insert my own kernel modules with insmod which requires super user permission/root access (uid=0).
I really can't wait until I get my Nexus One!
JBDynamics said:
leonnib4, thanks for the info. As long as ADB works, then I should have an elevated shell (super user shell) just by issuing 'adb shell' then I should be able to run commands with su. Thanks! Basically, I need to be able to insert my own kernel modules with insmod which requires super user permission/root access (uid=0).
I really can't wait until I get my Nexus One!
Click to expand...
Click to collapse
Your gonna have to root for SU. ADB works but you won't get SU permissions....
TFJ4 said:
Your gonna have to root for SU. ADB works but you won't get SU permissions....
Click to expand...
Click to collapse
Exacly.
adb is a the "Android DeBugging tool".
It provides you a shell access to to phone in almost any situation (even boot).
But it does not gives you root!
Can you point me in the direction of a rooted 2.2 ROM or the procedure to gain super user access? I was developing BlackBerry applications for a while and just came back to the Android platform a couple weeks ago so I am out of the loop on the latest information about Android. I found the post for the 2.1 ROM and T-Mobile/AT&T instructions, but I think I am getting an Unlocked Nexus One since I ordered directly from Google via my Android Developer account. If nobody has come out with a ROM and recovery image yet, please point me in the direction of the nexus one specific commands needed to build Froyo for the Nexus One (http://source.android.com/ is partially deprecated and not really updated for Nexus One and 2.2 build instructions). So I'm not sure exactly what to do to set myself up for super user access.
Thanks guys!
- JBDynamics
JBDynamics said:
Can you point me in the direction of a rooted 2.2 ROM? Or point me in the direction of the nexus one specific commands needed to build Froyo for the Nexus One (code.google.com is partially deprecated and not fully updated for the Nexus One and 2.2). I can always modify permissions and give myself SU access before the build, but if someone already has a good build, I'd rather not waste my time.
Thanks guys!
- JBDynamics
Click to expand...
Click to collapse
Get AOSP code from source.android.com or find a ROM in Development forum
Is Leo's Froyo 1.1.0 build the best thing around right now? Seems like his SparePartsMod is pretty cool.
JBDynamics said:
Is Leo's Froyo 1.1.0 build the best thing around right now? Seems like his SparePartsMod is pretty cool.
Click to expand...
Click to collapse
I guess you're not asking me... lol
Try it, what could you loose?
just nanbackup in case
I do not wipe data
Thanks for the tips! Will definitely backup first.

[Q] Problems with enabling sideloading

Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
goosefraba91 said:
Okay everybody, first off let me apologize, as I am sure that this is asked quite a bit. However, I am not very savvy with using terminal and such to enable sideloading on my Captivate, and I cannot get any of the methods to work properly.
I started off with the Unleash the Beast root on my phone, then for some reason I thought that froyo was out as an official update, because when I went to check for an update, it would download a package, reboot my phone, then tell me that the update could not be applied. So, thinking that it was due to the root, I had to use Odin to get Unleash the Beast off the phone; however, whatever "update" the phone was attempting to apply still would not work. So I reverted back to root the phone. I have used the One Click Root to program, I have installed BusyBox, and allowed SuperUser access. I am trying to enable sideloading so that I can download the Market Access app, but I am having troubles getting it to work. I have a Mac, and I have used many methods to try and enable it, but no matter what I do it will not work.
Again, I apologize for my ignorance. I have searched all over, and I still can't get this stuff to work. If anybody could provide any assistance, it would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
Could you provide a little more information about your phone? Is it stock JF6 with just root? If not provide firmware information and anything else that might be useful
P.S. Questions belong in the Q&A section
I'm not really sure what JF6 is haha...After I used Odin and set it back to stock conditions, the only thing I did was use the One Click Root.
As far as sideloading goes, the One Click De-Cripple method on page 2 of the general forum worked for me. If you want to know what version your phone is, go to the about phone section under your settings menu. If you need or want to upgrade to JH7, which was the last OTA update from ATT, do a search and there are a few options out there for that.
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
goosefraba91 said:
Well unfortunately I cannot use OCD on Mac..I tried to do the command prompts, but the su is asking for a password, which is odd because the way I understand it, it shouldn't be doing that
Click to expand...
Click to collapse
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
miztaken1312 said:
You did type adb shell first right? Then you should get a "$" where you then type su. It then echoes back su and you should see a "#".
From what you just said, it sounds like you're attempting to get root access on your mac through terminal, which in that case should be your password.
Click to expand...
Click to collapse
Ok, I got that to work. Now I'm just having trouble entering the code for mac. Like I said, I'm not very savvy with this stuff, so pardon my ignorance, haha.
I'm using the method in the "How to: Remove (Almost) Every Trace of AT&T" thread. (I would post a link, but since I'm a new user, it won't let me)
Is there anything different that I need to put into terminal other than the "./adb"?
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Roof King said:
I tried to paste the link to this thread but being a new member I am not allowed to post a link because of spam issues. Do a google search for "how to enable non market apps on captivate consolidated" and this will be the first xda thread that comes up.
This thread gives several methods for permanent enabling of sideloading. Being a noob, all of them were a little intimidating to me except for METHOD 3. You don't need a computer and you can do it all on your phone with Root Explorer, SQ Lite, and Terminal Emulator which are all available on the market. The step by step is pretty good and I have done it twice with no issues.
Click to expand...
Click to collapse
That method worked great. Thank you!
No prob!
Happy Modding!
Glad you got it working. For the record, the next time you guys wanna post links, just replace the http in the front with hxxp. Most people will fix it when they copy/paste it
Sent from my Captivate

[Root] Z4Root

We've heard that you can root the LG Optimus 2X with Z4Root. Is it permanent or temporary?
No supporting evidence just yet, but rooting this phone should be a piece of cake.
I used Z4root on two samples of the 2X, no issues what so ever. These were however pre-release roms, but I couldn't imagine any differences from the final release.
And yes, it's permanent. I had some app testing to do and tried Z4root just for fun and it worked like a charm.
//Dave
Cool. I have already ordered one. Is the root reversible? E.g. can one root an unroot as if nothing happened?
I'm holding the 2x in my hand right now and unrooted it. (didn't try adb on it for confirmation but tried clocksync, which refused access (superuser has disappeared as well). Rerooting at the moment.
Once again this is a pre relase rom so I can't guarantee that the final ROM will have the same functionality.
//Dave
dave79 said:
I'm holding the 2x in my hand right now and unrooted it. (didn't try adb on it for confirmation but tried clocksync, which refused access (superuser has disappeared as well). Rerooting at the moment.
Once again this is a pre relase rom so I can't guarantee that the final ROM will have the same functionality.
//Dave
Click to expand...
Click to collapse
Thanks. Can't wait to get my hands on one.
Good news dave. My understanding is that the main issues with the Optimus 2x so far have been regarding the massive amount of bloat apps as well as some instability in day to day operations (browser and messaging seems to crash from time to time).
Are you experiencing these? Would you be able to remove some of the bloat apps and see if it breaks anything in the LG rom?
UHOH!
Bantu85 said:
Good news dave. My understanding is that the main issues with the Optimus 2x so far have been regarding the massive amount of bloat apps as well as some instability in day to day operations (browser and messaging seems to crash from time to time).
Are you experiencing these? Would you be able to remove some of the bloat apps and see if it breaks anything in the LG rom?
Click to expand...
Click to collapse
I'll take a look at it, I've got an early version of the 2x which I'll try to push the new system dump to. I've rooted it and while using adb shell it looks like I've bricked it! uhoh!
Bricking a pre-production version of the best phone on the planet isn't quite what I wanted to do! I'm stuck in a boot loop and I manage to get a limited connection when booting it into the bootloader. However, probably because of pre-production status, the bootloader will let me go up and down using the volume keys, but it won't let me select any of the options!
When in the bootloader, I do have some type of recognized connection via the PC. DDMS recognizes the phone, ADB doesn't let me access it.
I'll chill on doing anything to the "good" phone for now (hope you understand)... but if I get the bricked one started, I'm back in the game .
Feel free giving me tips or trix to get it up and running.
from a somewhat uneasy Dave
dave79 said:
Feel free giving me tips or trix to get it up and running.
from a somewhat uneasy Dave
Click to expand...
Click to collapse
Have you tried using the power button or one of the other buttons to select an option in the bootmenu?
GIR said:
Have you tried using the power button or one of the other buttons to select an option in the bootmenu?
Click to expand...
Click to collapse
I sure did, thanx anyways. I've used every button available incl, the touch screen corners, tapping on the selection itself.
//Dave
Z4root doesn't work with my sample
No way to root
pocketAM said:
Z4root doesn't work with my sample
No way to root
Click to expand...
Click to collapse
Do you have a preproduction model like Dave or a sales sample?
On mine Z4root simply quits...after saying "Aquiring root shell" ... will try an other version, hope that will work...
Do you have a temporary root? After z4root locks? I tried with a later rom and got the same issue. However after accessing it with ADB shell it clearly has root "#" is showing and I have permissions I otherwise wouldn't have. However it seems like the root is temporary. Weird thing... I'll continue hunting for alternative solutions.
BTW, my other X2 may rest in peace. After a friend helping me out we managed to get the phone into fastboot, the kernel must have been intact, the system was completely wiped. Pushed the system through ADB and rebooted. Now we can't get it into fastboot at all... RIP ;(
//Dave
dave79 said:
Do you have a temporary root? After z4root locks? I tried with a later rom and got the same issue. However after accessing it with ADB shell it clearly has root "#" is showing and I have permissions I otherwise wouldn't have. However it seems like the root is temporary. Weird thing... I'll continue hunting for alternative solutions.
BTW, my other X2 may rest in peace. After a friend helping me out we managed to get the phone into fastboot, the kernel must have been intact, the system was completely wiped. Pushed the system through ADB and rebooted. Now we can't get it into fastboot at all... RIP ;(
//Dave
Click to expand...
Click to collapse
Wow, sorry to hear your loss...sad story.
Anyway, I heard that it is possible to root 2.2.1 devices with Super One Click, but I can't get my Optimus 2x connected to adb, somehow Windows 7 doesn't wanna install the downloaded Google USB Drivers...
The reason Z4root doesn't work on firmwares 2.2< is that the exploit it uses to gain root rights has been fixed in those newer versions
GIR said:
Do you have a preproduction model like Dave or a sales sample?
Click to expand...
Click to collapse
sales sample x press
After update OTA to version LS670ZVC, machine is unable to be rooted at this time. I am sure someone is working on it.
I returned this previously rooted phone Saturday feb 12 for replacement due to HW fault. Got new phone home and saw the phone was auto-updating to the LS670ZVC version. Which kept me from using Zroot as I did in the past. Drat! Tried many tricks found on other android forums to try and root.
The skinny of it is, if this update was applied OTA, we are SOL for now. If you updated using LG software via computer, you can root it still. If you haven't updated from version 9, don't do it until an exploit is released.
I have another thread going on this same issue. I have tried using superoneclick. Even though everything looked ok it didn't make a difference. Did a root checker it said busybox was ok and I know that SU is ok. Just looks like they "fixed" the exploit for now...
Sent from my LS670 using XDA App
domi007 said:
Wow, sorry to hear your loss...sad story.
Anyway, I heard that it is possible to root 2.2.1 devices with Super One Click, but I can't get my Optimus 2x connected to adb, somehow Windows 7 doesn't wanna install the downloaded Google USB Drivers...
The reason Z4root doesn't work on firmwares 2.2< is that the exploit it uses to gain root rights has been fixed in those newer versions
Click to expand...
Click to collapse
Mmmm, sad about the old one, however I got my second device so I'll unroot my it and then try the SuperOneClick option.. I'll let you know. Once again this is a sample but the rom is dated from 2010-12-14 so it must be quite close to production ROMs.
//Dave
Post removed by User.

How do I root the frk76 OTA update?

I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)
Don't know what the above means
Does 2.3.1 work without modification?
While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?
Noob needing help
sir_lunatic said:
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
Click to expand...
Click to collapse
Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.
Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.
I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.
As there anyone out there who can assist?
Thanks much in advance!
sir_lunatic said:
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
Click to expand...
Click to collapse
how does one get an older version of SuperOneClick 1.7?
envoy510 said:
Does 2.3.1 work without modification?
Click to expand...
Click to collapse
As per i know it does not.
Pete has a stock rooted FRK76 Rom on his website, fyi
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
flukehawkins said:
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.
Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Click to expand...
Click to collapse
The rageagainstthecage exploit works for the FRK76 build, but I couldn't get SuperOneClick to run without crashing, so I just did it manually.
Download SuperOneClick 1.7
Extract, and use the rageagainstthecage, busybox, su, Superuser.apk with this guide: http://forum.xda-developers.com/showpost.php?p=8315805&postcount=2
The only difference is the block device /system is mounted from (the guide says mtdblock3, and I think on the droid it is mtdblock4). Just type `mount` on the command line and look for the line that has /system and check the mount path.
I used superoneclick 1.7 to root a stock frk76.
On a note to new users...if you are on windows 7, I could not get it to work. I had an old xp machine that I downloaded soc1.7 to, when I first tried to run it, my PC posted an error about .net 2.0 framework. I Google, found, and downloaded the net 2 0 framework and it worked instantly.
It did not give me recovery. I used rsdlite and only rsd recovery after I rooted it to install cwm. Once you install cwm go directly to it and flash your new rom.
For me, after I rooted and had a stock rom, my recovery would not survive a reboot. But after moving cm7 and gapps to my SD card, re-rsd recovery. Booted directly to recovery. Flashed. Once booted I went to rom manager and had it reflash cwm recovery again and it never had another issue.
My steps may sound confusing but this is what I did.
I do not have sdk setup completely on my laptop and found this to be extremely easy. It works 100% and supplied no errors. I hope this helps someone else.
Is there a RUU i can run to unroot my phone?
YoungCorruptionV2.0 said:
Is there a RUU i can run to unroot my phone?
Click to expand...
Click to collapse
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
stkiswr said:
No ruu on here but you can simply flash an unrooted stock rom and accept updates thru Verizon.
Click to expand...
Click to collapse
Ah okay thanks for the tip. I'll look in the development section for one
YoungCorruptionV2.0 said:
Ah okay thanks for the tip. I'll look in the development section for one
Click to expand...
Click to collapse
You may be able to find it on rom manager but def can find it on peter Alfonso site

[Q] bionic jb 98.72.22 su binary help! root access?

So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
linux minimal screen shot, and unbuntu hang up
DanRyan85 said:
You need to go back to what has been proven to work. Moto chopper 2. Not to be insulting BUT I know from experience, just BC you can't get something to work the first couple of times you try it doesn't mean it does not work. Period. Now, where did you get hung up on the Ubuntu exploit? List all that you did.
Sent from my XT875 using xda premium
Click to expand...
Click to collapse
Well, not to be insulting, but it was my understanding that moto chopper would only work if temp rooted or had gained root acess previously? I may be wrong. Anyways, the prob. with unbuntu is thing i guess froze (but still ran) after patiently running it like six hours. Last screen at was installing-reinstalling previous "somethings" but I figured need a system clean and would try again. gotta be easier way. so here is my linux minimal screenshot attempt. running root bionic jb ovf file. noticed where it starting going wrong is
chmod: pwn: operation not permitted.
rooting phone...
phone may appear to.......
/system/bin/sh: /storage/rfs0/pwn: not found <-------Right here i noticed the file path on the phone and it's ---> storage/rfs1 Would that have something to do w/ it?
nothing ever vibrates and reboots in flash. got bad flash or something?
MotoChopper works on non TI (OMAP) CPus that are in Motoroal devices.
Coincidentally, it also works on ASUS Tranformer Infinity (and the Prime as well, IIRC).
It does not work on the BIONIC.
The method that works on rooting the JB build on the BIONIC is one that is based upon the older RAZR method - see http://www.droidrzr.com/index.php/topic/16518-root-motoshare-2-old-bug-new-exploit/
Bionic and JB OVA flash superuser binary outdated
Naughtybutbritt said:
So from the beginning I updated from notification on phone from 4.0.4 to 4.1.2. Then bricked after trying to gain root acess. Finally able to flash jb 98.72.22. Tried for days to find a root that worked. Couldn't get motochopper to gain root. Tried god knows how many others. Finally got virtual box, imported Root_Bionic_JB.ova and still wouldn't work. Keep coming across su binary issues. The closest i got was with the virtual box installing superuser. But when I trying to update the binary says unable and to send a log report. What am i doing wrong? is it a step im missing when unzipping to desktop? everything goes smooth until cmd gets to rooting, then says failed. cleaning. press enter to reboot and close. Im about to lose my mind! Please some assistance. I sick of failing every attempt from every suggest forum (quietly sobbing )
Click to expand...
Click to collapse
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
To Naughty: Sorry about the mix up that was what I meant to say Moto share 2 NOT Motochopper. I had all the same problems as you after some number of tries with motoshare2 I was in business.
To martin: have you already tried the motoshare 2 on Ubuntu?
Sent from my XT875 using xda premium
toddmartin- you're gonna love me...i gotcha
toddmartin said:
I am having same issue. Using Marty OVA in virtual box. works great, no issues w/ samba or USB. Root is successfully run. however.
root checker indicated that I am not rooted and as mentioned above, superuser needs to update the binaries.
" the Superuser binary (su) must be updated
please choose an installation method
recovery mode installation is recommended for HTC devices.
Cancel <> Recovery Install<> Install
hit install
there was an error installing superuser. Please send a log of the error to the developer.
<ok>
wonder if I could replace the superuser.adk file in the /home/guest/share directory with a newer adk file?
could not get post on droidrzr.com on a thread there. ( link not permitted by Noobs )
Marty45714 informed us He posted this here as well. can anyone answer this?
T
Click to expand...
Click to collapse
Ok so using virtual box the ova Root_Bionic_JB_20130501-4 the fourth ubdate of the orginal release. Now i suggest erasing all superuser apps installed your self and anything to do with them. When it's done right, it will appear on it's own and work flawlessly. No uncertianties about it. Then i've posted a screen shot of the commands with notes to help understand easiest. The instant the command to press hardware key or power/or each volume itself is the instant you want to press it. Now the reboot is instantious kinda itself and gotta be noticing phone unless have ungodly long boot up let me know if the screen shot helped what you were asking.

Categories

Resources