"EXCUSE ME" If Someone Else Has Something Similar Posted, But I Got Tired Of Reading A Thousand Posts Just To "ALMOST" Get My Question Answered!!
Anyway I Know The Last "OTA" Sent Out From Sprint or HTC (Whoever- Sent It Out) *BROKE* My Ability To Access The "Clockwork Recovery" Menu-Screen!
Since Then I Turned Security From "On to Off" With "Unrevoked-4ever" But I've Read That Even After Flashing "Unrevoked-4ever" It's Possible For Them To Send Me Another "OTA" & Re-break My Root Access!!
Does Anyone Know If What I Read Is "TRUE or Bull-Sh#%".... Am I Really "Unrevoked-4ever"???
1 More Thing What's The Benefits Of A OTA???
Sent from my HERO200 using XDA App
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
Did you do this when you rooted your phone? ^^
Pulled this from [Guide] How to Root Sprint 2.1 CDMA Hero
Twolazyg said:
DISABLE OTA UPDATES!!!!
To disable OTA updates that will patch this exploit, (after rooting and booted after creating a nandroid backup) run the following commands from Command Prompt.
Code:
cd C:\android-sdk-windows\tools
Code:
adb remount
Code:
adb shell
Code:
mv /system/etc/security/otacerts.zip /system/etc/security/otacerts.zip.bak
After doing this, the OTA updates WILL still download, BUT they will not pass signature checks to flash because of the code you just entered.
Did you do this when you rooted your phone? ^^
Pulled this from [Guide] How to Root Sprint 2.1 CDMA Hero
Click to expand...
Click to collapse
No... To Tell You The Truth I Rooted With "Universal Androot" Because I Was Somewhat *NEW* To The Whole "ADB/SDK/ROOT" Thing, But Since I've Probably Learned 20X More Then I Did! But As Far As "ADB" Goes I'm Still Kind Of Scared To Try Out!! Although I Have A Wireless ADB App Installed On My Phone, Does That Work, Or I Should Say Will That Work For The Command You Suggested? Also Thanx For Your Help!!
Sent from my HERO200 using XDA App
PMGRANDS said:
No... To Tell You The Truth I Rooted With "Universal Androot" Because I Was Somewhat *NEW* To The Whole "ADB/SDK/ROOT" Thing, But Since I've Probably Learned 20X More Then I Did! But As Far As "ADB" Goes I'm Still Kind Of Scared To Try Out!! Although I Have A Wireless ADB App Installed On My Phone, Does That Work, Or I Should Say Will That Work For The Command You Suggested? Also Thanx For Your Help!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I've never used an app to root my phone, I followed a guide and did it right the first time. Here is the guide thread. What is the wireless ADB app you're using? Try terminal emulator with the commands, or take 15 min and un-root your phone, then re-root using this guide, that may solve the other issue you're having with the wigets and icons being odd. Let me know how this works for you.
PMGRANDS said:
No... To Tell You The Truth I Rooted With "Universal Androot" Because I Was Somewhat *NEW* To The Whole "ADB/SDK/ROOT" Thing, But Since I've Probably Learned 20X More Then I Did! But As Far As "ADB" Goes I'm Still Kind Of Scared To Try Out!! Although I Have A Wireless ADB App Installed On My Phone, Does That Work, Or I Should Say Will That Work For The Command You Suggested? Also Thanx For Your Help!!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
If you search android Dev section I've posted how to install adb in like 15 min also in the same thread its another guide as well either way you can have adb in 15 or 20 min tops real simple and the commands he posted will work fine I'm mobile @ work so I can't link but good luck
Root-Hack-Mod-Always™
Twolazyg said:
I've never used an app to root my phone, I followed a guide and did it right the first time. Here is the guide thread. What is the wireless ADB app you're using? Try terminal emulator with the commands, or take 15 min and un-root your phone, then re-root using this guide, that may solve the other issue you're having with the wigets and icons being odd. Let me know how this works for you.
Click to expand...
Click to collapse
Okay, I Think I Just Might Do That... Also As Far As The App I Have, It's Called "ADB Wireless", But I Also Have "Terminal Emulator"!! Which One Would You Use?? "Terminal Emulator" Guess That's Why You Posted It Obviously??.... Lol!! 1 More Thing What's The Benefits Of The OTA's?? Seems Like They Only Eff-Up Root Access!! And Thanx Once Again 4 Your Help!!
Sent from my HERO200 using XDA App
laie1472 said:
If you search android Dev section I've posted how to install adb in like 15 min also in the same thread its another guide as well either way you can have adb in 15 or 20 min tops real simple and the commands he posted will work fine I'm mobile @ work so I can't link but good luck
Root-Hack-Mod-Always™
Click to expand...
Click to collapse
Thank You!!
Sent from my HERO200 using XDA App
Related
What is the simplest way to send commands to my phone (HTC Hero CDMA Sprint) through my computer (Mac OS)?
I haven't explored Android SDK yet. I rooted my phone through Terminal and bash_profile file. I'm interested in:
- how to push .apk's to the device
- how to install a recovery image if my phone can't reboot and there is not a recovery image present
Thanks!
Android sdk is the easiest
-------------------------------------
Sent via the XDA Tapatalk App
What I do is use terminal and cd to the Android sdk/tools folder. After that use the ./adb commands, which there are several tutorials for and own your phone. Hope this is clear, doing it on my phone
-------------------------------------
Sent via the XDA Tapatalk App
What I do is use terminal and cd to the Android sdk/tools folder. After that use the ./adb commands, which there are several tutorials for and own your phone. Hope this is clear, doing it on my phone
Click to expand...
Click to collapse
Sweet. Thanks. I've searched the Android SDK site and it seems that I need other software or plunging such as Eclipse and Java. I'm not ruling these out eventually but know I'm not ready to get in this deep yet to start developing apps or customizing roms. Also, after a Google search all the queries came back with options for rooting your device which I've already done. If there's a good easy tutorial, would you mind posting a link?
-------------------------------------
Sent via the XDA Tapatalk App
When I get home from work I'll find something for you.
-------------------------------------
Sent via the XDA Tapatalk App
joshuaharp said:
Sweet. Thanks. I've searched the Android SDK site and it seems that I need other software or plunging such as Eclipse and Java. I'm not ruling these out eventually but know I'm not ready to get in this deep yet to start developing apps or customizing roms. Also, after a Google search all the queries came back with options for rooting your device which I've already done. If there's a good easy tutorial, would you mind posting a link?
-------------------------------------
Sent via the XDA Tapatalk App
Click to expand...
Click to collapse
Just download the 2.1 SDK, cd to Android/SDK/tools, and use ./adb, I think it can tell you some commands too.
I made an app to put my phone in recovery using ./adb so I wouldn't need to go through the trouble everytime, I just go to spotlight, type "recovery", and it puts it into recovery.
I might make an app/interface for Mac OS later for ADB commands (recovery, push files, etc)
derekwilkinson said:
Just download the 2.1 SDK, cd to Android/SDK/tools, and use ./adb, I think it can tell you some commands too.
I made an app to put my phone in recovery using ./adb so I wouldn't need to go through the trouble everytime, I just go to spotlight, type "recovery", and it puts it into recovery.
I might make an app/interface for Mac OS later for ADB commands (recovery, push files, etc)
Click to expand...
Click to collapse
That would be awesome dude...
joshuaharp said:
That would be awesome dude...
Click to expand...
Click to collapse
Don't hold your breath though, I have been working a lot, but I might make it in the next few weeks.
The only main problem is that I'm having trouble getting variables to run in the shell script. I think it might be possible with Automator (or AppleScript), but I will keep trying
Well, even though it may not be useful anymore, here are the links, as promised
Rooting guide for mac (What I used and a great way to get familiar with adb on the mac ) http://forum.xda-developers.com/showthread.php?t=581686
And here's an adb tutorial that was put together at the request of toast on the EVO 4G forum. http://forum.xda-developers.com/showthread.php?t=694250
Just like the title suggests, I need help. I have been working on this for three days and have not accomplished anything.
I have been rooted for six months, flashed many roms, kernels, enabled apps2sd, etc.., etc.., but I do not know how it all works(just to give you a little FYI).
"I do not have a recovery screen anymore." At first I just wasn't able to push a new one, it would tell me "usage flash_image partition.img" or something very similar. I searched for that phrase and found something with it in the G1 forums, tried it(probably should have asked first), and now I don't even have a recovery image. Like I said I've tried almost everything and it may be simple but this is beyond me, someone please help.
Sent from my HERO200 using XDA App
secbrad said:
Just like the title suggests, I need help. I have been working on this for three days and have not accomplished anything.
I have been rooted for six months, flashed many roms, kernels, enabled apps2sd, etc.., etc.., but I do not know how it all works(just to give you a little FYI).
"I do not have a recovery screen anymore." At first I just wasn't able to push a new one, it would tell me "usage flash_image partition.img" or something very similar. I searched for that phrase and found something with it in the G1 forums, tried it(probably should have asked first), and now I don't even have a recovery image. Like I said I've tried almost everything and it may be simple but this is beyond me, someone please help.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
what happens when you hold home then press the power button? Is there any sort of screen if you get a screen you need to install android sdk and flash a new recovery image using adb
bycoo222 said:
what happens when you hold home then press the power button? Is there any sort of screen if you get a screen you need to install android sdk and flash a new recovery image using adb
Click to expand...
Click to collapse
Yes there is a screen, it's the green HTC w/ white background. It will just sit there forever. I am at work right now so I can't do it yet but when I get home I'll try it, hopefully that works.
BTW, from my phone I can't tell if you have a donate button. I was serious about that.
Sent from my HERO200 using XDA App
Try downloading the RUU and then re-rooting your phone. It will be wiped clean from the RUU install then you'll be able to push a new recovery img over. If you don't want to do that my other suggestion is if you can't manually flash the recovery try downloading RomManager from the market and using that to flash a recovery.
As far as why you can't flash a recovery where are you placing the recovery.img when you try? are you doing it from your computer or from your sdcard using a terminal emulator? If its from your computer make sure that the recovery.img is in the tools folder and make sure you type it word for word (caps included) if your trying to do it from the terminal emulator and its on your sdcard the same applies as it must be letter for letter and word for word, but before you can type anything you have to gain root access in the terminal you do this by simply typing su and then enter. SuperUser Permissions will ask you if its ok to use root click ok then type in what you need to.
Since you said you've been trying to flash it I assume you know what to type but if you need it again just ask I'll post it up for you. Hope this helps.
Here's something I wrote a few days ago to help someone who was trying to flash a custom recovery might be helpful.
Flashing a custom recovery is pretty easy there is a couple of ways to do it some find it easier to do by putting it on the sd card and flashing it through a terminal emulator or if you have your htc sync and adb set up already you can throw it on your sd card and type this
Code:
adb remount
Code:
adb shell
Code:
flash_image recovery /sdcard/RA-darchstar.img
You should see this below
Code:
# flash_image recovery /sdcard/RA-darchstar.img
flash_image recovery /sdcard/RA-darchstar.img
#
Reboot into recovery and you should be all set to go. The other way by using the terminal emulator you'll just type in this in:
Code:
su
Accept Root access request from SuperUser Permissions then type:
Code:
flash_image recovery /sdcard/RA-darchstar.img
You should see the same output to know you did it correctly. Hope this helps.
secbrad said:
Yes there is a screen, it's the green HTC w/ white background. It will just sit there forever. I am at work right now so I can't do it yet but when I get home I'll try it, hopefully that works.
BTW, from my phone I can't tell if you have a donate button. I was serious about that.
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
No donate needed
Sent from my HERO200 using XDA App
Also try quick boot to get in to recovery
Sent from my HERO200 using XDA App
Thanks
Thanks everyone for all you help. I ended up being able to do it through terminal. I guess next time I won't wait three days to ask for a thirty second fix.
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Torin_93 said:
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Click to expand...
Click to collapse
Android Development is not for questions or Problems
Please post in the correct Forums
Moving to General
Torin_93 said:
Hey everyone!
I am new to everything about android and just rooted my phone a couple weeks ago. I want to install the decrapified rom burin not 100% sure how to do it. I need CWM to do this right? Can I get back to my original rom if I don't like it or something goes wrong? I also hear some users talking about backing up the device. How do we do this? I know that there are lots of questions and I know some person (maybe two lol) could point me in the right direction. Thank you!
Torin
Click to expand...
Click to collapse
1 yes, you need cwm to put decrapified
2 once u install cwm, make sure ur battery is full (at least 50%, but i'll just say full) and make a backup using cwm of ur current system
3 see: 2
Sent from my VS910 4G using Tapatalk
S.Meezy said:
1 yes, you need cwm to put decrapified
2 once u install cwm, make sure ur battery is full (at least 50%, but i'll just say full) and make a backup using cwm of ur current system
3 see: 2
Sent from my VS910 4G using Tapatalk
Click to expand...
Click to collapse
Awesome thanks. Now I cant get the adb shell to work. ive done it on my dads phone before so im kinda familiar with it but the sdk still seems to be updating or whatever. Should it work when its finished?
Like when I type "adb devices" it says nothing can be found.
What operating system is ur computer on? Make sure you have installed the LG drivers if Windows.. also, doesn't hurt to be up to date w the sdk...
Sent from my VS910 4G using Tapatalk
Running windows 7 sdk updated drivers installed.
Im typing
cd C:\android-sdk\tools\
adb devices
nothing pops up. It says it isnt recognized?
1. install and update adb sdk.
2. Plug your phone in and install the drivers so it is recognized by windows as the revolution.
3. once 1 and 2 are done set your phone to internet only and turn on debugging.
4. now try adb
Torin_93 said:
Running windows 7 sdk updated drivers installed.
Im typing
cd C:\android-sdk\tools\
adb devices
nothing pops up. It says it isnt recognized?
Click to expand...
Click to collapse
also it is cd c:\android-sdk\platform-tools\
Haxcid said:
also it is cd c:\android-sdk\platform-tools\
Click to expand...
Click to collapse
I just figured out it was\platform-tools\
Like wtf they moved it? lol
I also forgot about internet mode. Im going to give it a go and if I bump into any problems I will let you know
Once I try to get su access (after checking adb access) it says not recognized. Why?
Torin_93 said:
Once I try to get su access (after checking adb access) it says not recognized. Why?
Click to expand...
Click to collapse
we're still getting cwm on...? and u already put recovery-cwm-pr1.img on ur sd?
S.Meezy said:
we're still getting cwm on...? and u already put recovery-cwm-pr1.img on ur sd?
Click to expand...
Click to collapse
Yes its there
But the su command wont work
You have skype? I could screen share.
Torin_93 said:
Yes its there
But the su command wont work
You have skype? I could screen share.
Click to expand...
Click to collapse
Make sure your screen is on when you type su so you can accept super user permission on your phone.
Sent from my VS910 4G using XDA Premium App
After I type adb devices I get the list then its:
C:\android-sdk\platform-tools>su
Right?
Cause it says not recognized
No type, adb shell, then at the next line enter su
Sent from my VS910 4G using XDA Premium App
mtmichaelson said:
No type, adb shell, then at the next line enter su
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
Great thanks!!! Im in
cat /dev/zero > /dev/block/mmcblk0p14
write: no space left on device
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
no such file or directory.
Im so confused. Now what.
Thanks for everyones help so far You guys are amazing!
Torin_93 said:
cat /dev/zero > /dev/block/mmcblk0p14
write: no space left on device
cat /sdcard/recovery-cwm-pr1.img > /dev/block/mmcblk0p14
no such file or directory.
Im so confused. Now what.
Thanks for everyones help so far You guys are amazing!
Click to expand...
Click to collapse
If you are copying it in Windows, copy it to the drive marked "internal." If not, then this is telling you that file isn't on your sdcard. You need to move it there.
Its in the internal. Should it go in a folder? What about the fact that it says no space left on device?
I have plenty of space?
Torin_93 said:
Its in the internal. Should it go in a folder? What about the fact that it says no space left on device?
I have plenty of space?
Click to expand...
Click to collapse
It shouldn't need to go in a folder. The error message about space is normal (expected).
Really didn't want to start a new topic, but couldn't find an answer anywhere. I'm trying to flash dg's recovery with adb. When ever I try to push the file I get permission denied. I have su working with adb, and adb is working correctly. What am I doing wrong? Thanks to any one that can help.
Sent from my LG-P925 using XDA App
I am having the same exact problem you are. I am running windows 7 and even tried cmd and run as admin but that didn't work either. Anyway yea any help would be appreciated. Also yes my phone is rooted and in Debug Mode when trying to push recovery.img.
Hmm, sorry I don't know. Fix permissions maybe, if you can? Stupid little things like making sure usb debugging is on?
Just a heads up, questions belong in a different section ("Q&A for Thrill" if it exists, or general I think), they take that stuff pretty seriously around here, and if you end up reading and learning here for a while, you'll understand why!
switch to your ADB directory (or at a command line if you already set your environment variables) and type adb root then try again. It might work
Komodo Rogue said:
Hmm, sorry I don't know. Fix permissions maybe, if you can? Stupid little things like making sure usb debugging is on?
Just a heads up, questions belong in a different section ("Q&A for Thrill" if it exists, or general I think), they take that stuff pretty seriously around here, and if you end up reading and learning here for a while, you'll understand why!
Click to expand...
Click to collapse
I dont think we have a q&a as of right now lol....I dont even know if we have a moderator
Sent from my SAMSUNG-SGH-I997 using XDA App
Sorry if this is the wrong section. No q/a for the thrill. And i didn't know if the general forum was the place for adb question. Again sorry my fault. Thanks for all replays but im still stuck with the same thing.
adb root didn't work. Said adbd cannot run as root in production builds. Also I do have USB Debugging enabled as well as Rooted the device. As for fixing permissions I would need CWM First to be able to get to that option
malickie said:
adb root didn't work. Said adbd cannot run as root in production builds. Also I do have USB Debugging enabled as well as Rooted the device. As for fixing permissions I would need CWM First to be able to get to that option
Click to expand...
Click to collapse
Do this:
open command prompt and type:
adb shell
su (click allow on phone if prompted)
chmod 777 /data
ls -l (then look at the data directory and it's permissions should now be drwxrwxrwx)
Try it again after that. It's because the /data directory is not set to R/W by default.
timbrendelaz said:
Do this:
open command prompt and type:
adb shell
su (click allow on phone if prompted)
chmod 777 /data
ls -l (then look at the data directory and it's permissions should now be drwxrwxrwx)
Try it again after that. It's because the /data directory is not set to R/W by default.
Click to expand...
Click to collapse
Thank You, that did it .
malickie said:
Thank You, that did it .
Click to expand...
Click to collapse
Cool beans
Thanks so much!!!
00mred00 said:
I dont think we have a q&a as of right now lol....I dont even know if we have a moderator
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
It says Mr. Clown is the moderator, and his sticky says not to ask questions. I don't know if I've actually seen him on here though, so I see where you're coming from, the thrill isn't getting much traffic! But you're right, no q&a section.
fn1046 said:
Sorry if this is the wrong section. No q/a for the thrill. And i didn't know if the general forum was the place for adb question. Again sorry my fault. Thanks for all replays but im still stuck with the same thing.
Click to expand...
Click to collapse
Oh hey no worries mate. I really couldn't care less, considering how empty Thrill Development is, and I would have came to the same conclusion as you. All I meant to do was give you a heads up that some people get angry about that kind of thing
Well my issue is i cannot get the recovery.img pushed to the phone...ive downloaded it and don't know where to place it for it to send...when i do adb push recovery.img/data it just gives me a list of all the adb commands. I was gonna try to use root explorer and manually push it but i dont know where to place it...any suggestions?
Put the recovery.img in your android-sdk tools folder before you try to push
Sent from my LG-P925 using XDA App
Hey can one of you guys possibly upload a stock recovery backup. I think mine is borked as I tried to go back to stock and it keeps going into clockworkmod recovery when setting up factory defaults in the stock rom. It would be much appreciated.
thanks
guys I finally have been able to root mu atrix hd on jb . this is what worked for me http://forum.xda-developers.com/showthread.php?p=35905543#post35905543
Did you have partial root previously? If you didn't, a new thread was warranted. If you had partial root, why create a new thread?
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app. i was only able to invoke a root prompt. i looked all over the internet not just the xda forums. i tried mattigriffs root restore. i typed into a command prompt for several hours each day.. all i ever got was a root prompt in adb shell. no prompt on the phone emulator. this is the only page that has worked for me. i noticed right away that the code was written differently than any other that i tried. also the su used is different(it is described as wide open) any way because of this i felt that others who were /are in the same boat. no root. may be able to get root back. I hope that answers your question. have a great day! .
Simple yes or no would have worked. I was hoping that by chance someone was stating that they didn't have root previously and were able to obtain root using this method.
Someone tested if it works on 4.1.1 official without prior recovery Boodoo ota?
Sent from my MB886 using xda premium
ashraf sharif said:
After I upgraded ota to jb. Su ceased to work entirely the binary would not update. and all root apps were no longer working. i did have a su-backup but was getting nowhere in my attempts to use the app.
Click to expand...
Click to collapse
Thats what happened to me as well
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
My question too any idea
Sent from my MB886 using xda premium
sickkside13 said:
Would this work if i havent rooted my device prior tho official jb update
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
If I wasn't at work I would try it.
Lol me 2. I bought the phone online but it already came with jb i didnt knew the bootloader was locked .
Sent from my MB886 using xda premium
I think what that is fake
Sent from my MB886 using xda premium
i am no expert. and from my reading the forums. the consensus is that if you lost root after the upgrade then you have a chance of regaining it. this method was not meant as a root for atrix hd. but it worked for me. one thing that helps is the abilithy to invoke a root prompt in adb shell. i had a su-backup in /system/usr/we-need-root. ,/su-backup; su i was able to achieve shell root only until today. the the commands used are not identical to the ones i have tried for the past 11 days and the su used is described as 'wide open' whatever that means. Another thing i noticed was that the instructions said to download the su from the play store and update the binary while still in adb shell. , instead of rebooting. when i did this the binary finally gained root.I tried alot of methods none worked except for this one.i was not expecting this to work but it did. I dont know why. all i know is it worked for me. if you choose to try this . best of luck and i sincerely hope it works for you too.
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
i got the shell prompt working with these commands found on this page http://forum.xda-developers.com/showthread.php?t=1911261
Code:
adb shell:
$ cd /system/usr/we-need-root
$./su-backup; su (that is a semicolon immediately after the ./su-backup)
# mount -o remount,rw /system
(do what needs to be done)
#exit
... su-backup must have permissions as such: (get permissions by typing this into adb shell: ls -l /system/usr/we-need-root ) If you get an error, than this specifically won't work for you.
Code:
Required su-backup permissions for manual root restore
$ ls -l /system/usr/we-need-root/su-backup
-rwsr-sr-x root ... basically, if you can find a su-backup with proper permissions (and cannot restore root with voodoo or supersu), you can manually use that to repair your root access configuration. Maybe this is well known... but to those who don't this could be useful.
Thanks
Man, I cannot figure this out for some reason.
Sent from my MB886 using xda premium
logging in to adb
cmdru1980 said:
This is gonna sound dumb but, how do I "log in to ADB" (Step 2)? I got the same problem u had and am trying to figure this method out.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
download java developement kit and android sdk
the sdk has a section called tools where you will find fastboot and adb unzip the files and install the drivers.your first cmd will be cd or'change directory" to wherever the adb folder is. then type adb shell. this should restart the daemon. good luck
This is what I get.
Sent from my MB886 using xda premium
Thank you, Ashraf! I think I got it. I really appreciate it!
Sent from my MB886 using xda premium
I am confused
Sent from my MB886 using xda app-developers app
adolfo778 said:
I am confused
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Yeah I'm confused now as well. If the people here did not have partial root to begin with and were running stock Jelly Bean firmware and then went through these steps to get root access, this needs to be made more clear. If these are users that already had root access from a previous attempt but temporarily lost it during the upgrade process, that should be clarified and merged over into another thread and perhaps edited into the first post.