Database Develop

Installing CIME into Hero

Guys, I just found this CIME at http://forum.xda-developers.com/showthread.php?t=512530&highlight=hero+cime
Was wondering if:
a. it will install onto a rooted Hero
b. if a rooted Hero will still be able to detect, download and install OTA updates
Advice is much appreciated, thanks!

I just rooted my Hero using this technique and confirm that it works:
http://theunlockr.com/2009/08/08/how-to-gain-root-access-on-your-htc-hero/
The new CIME is nicely installed, and that works well too. Now I'm just not sure if the phone will receive OTA updates. The only thing different is the fact that the phone is rooted.
Gulp.

Right. Thinking logically, since I rooted my phone by following these steps:
15. If the serial number and the word fastboot next to it popped up, then go back to the command prompt on the computer and type
fastboot boot cm-hero-recovery.img
16. Once the phone boots up into the recovery screen type the following in the command prompt on the computer:
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell reboot
17. Once the phone reboots, click the Menu button and click Settings.
18. Goto Applications > Development and check the USB debugging on.
19. While the phone is still plugged in, goto the Command Prompt still up on your computer and type:
adb devices
You should see a serial number, which means the computer is seeing the device.
20. Then type:
adb shell
su
The phone should pop up an su request. Click Always Allow on the phone.
21. Type:
reboot
Logically, I haven't really changed anything else on the phone aside from:
a. copying in 2 APKs, one SU and one Superuser.
b. Setting permissions.
hmmm?

It does work, but with the IME I can only type simplified Chinese in Stroke input though (traditional Chinese is okay for Cangjie)
Now I'd be appreciated if I can get help of getting the attached "default.xml" into /system/customize/CID for displaying Chinese.

That is strange. Did you set TouchInput Chinese settings to use Pinyin?

I actually used the other method to did mine... but I think both ways works ^^

I installed the CIME on my rooted Hero with the method described in the linked thread, and it works like a charm.

Root instructions...

Originally posted by Stetsonaw at androidforums...
Please be aware that I did not write these instructions. I only posted them. Stetsonaw wrote these instructions. While comfortable in ADB and have rooted my phone many times in testing as well as rolled back the versions etc... I have no more insight into how or why it is not working for you. If you followed the directions exactly on a version 4 phone, this should work no problem.
Haxcid
Links to the necessary files are listed at the bottom.
Remember, I am not at fault if you brick your phone, now, proceed.
Connect your phone in charge only mode to install the LG Bootstrapper and drivers, or grab the LG Universal Drivers.
Change your USB Mode to Internet Connection
Go into Settings/Applications/Development and ensure USB Debugging is turned on
If all goes according to plan, you should see the ADB Ladybug icon in your notification bar
I updated the Rootzwiki page with the same info found below.
Busybox actually comes installed by LG on the Revo, how awesome is that??
Download the rageagainstthecage binary
Download the SU binary
Move these files to the same directory your adb.exe is in.
Code:
The > and # characters below illustrate the prompt
you should have, if you have the $ when you go into adb shell,
exit out and type 'adb usb' then go back into adb shell and
you should see the #
Open Command prompt (either use the Windows Key+R and type cmd or start/run, then type cmd)
32-bit users: >cd c:\program files\android\android-sdk\platform-tools
64-bit users: >cd c:\program files (x86)\android\android-sdk\platform-tools
Or >cd (whatever directory adb is in)
>adb devices (verifies you are connected)
>adb push rageagainstthecage-arm5.bin /data/local/temp/rage
(if the above command fails due to read-only, type 'adb usb' then 'adb root' to validate root status, then 'adb devices' again to verify connection)
>adb push su /data/local/temp/su
>adb shell chmod 777 /data/local/temp/rage
>adb shell ./data/local/temp/rage
>adb shell (If this gives you a $ prompt instead of a # prompt, type 'su', if that fails, 'exit', 'adb usb' like above.)
#mount -o remount,rw -t ext3 /dev/mmcblk0p12 /system
#busybox cp /data/local/temp/su /system/bin/su
#chmod 6755 /system/bin/su
Verify the file is in place w/correct permissions
#cd /system/bin
#ls -l *su
After the ls command you should see the following returned by the system:
-rwsr-sr-x root root 26248 2011-05-29 01:09 su
At this point, you may way to remove the files you put in /data/local/temp (optional):
#rm /data/local/temp/su
#rm /data/local/temp/rage
continue with commands
#reboot
Download and install SuperUser from the Market
Thanks Zennmaster, _mrbirdman_ for finding the linux routes and birdman for helping me out, and droidx8971 for helping me find all the information possible!
http://wikifilez.com/Root Files/revolution/rageagainstthecage-arm5.bin
http://wikifilez.com/Root Files/revolution/su
https://market.android.com/details?id=com.noshufou.android.su&feature=search_result
http://www.lg.com/us/support/mc-support/drivers/LGAndroidDriver_Ver_1.0_All.exe

Just a note for some. The rageagainstthecage bin file may be detected as a virus/trojan. It is not. You may want to disable your antivirus before downloading the .bin file.
I run avira on my desktop and it caught the file as a virus everytime I downloaded it and then deleted it. Avast on my laptop however did not.
Root is simple if you follow the instructions. You need to make sure that adb recognizes your device. Takes 5 minutes to complete, took me longer to install adb again and update it.

Any reason to not use the one click method? Seems to be working

bwhxeon said:
Any reason to not use the one click method? Seems to be working
Click to expand...
Click to collapse
No idea. I have not used the one click. Create a thread for it. I posted what I know which is adb.

Successfully Rooted
with RootzWiki instructions for Windows, needed the remount and busybox lines to overcome the permission denied when pushing su.

Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .

MXFrodo195 said:
Hey guys, either using S1C or ADB Commands, have we found out if it's possible to unroot this as long as you Nand Backup the stock rom then unroot from there yet? Just because I got this phone as a filler/4g unl. lock and got buyback on it from best buy so I could buy a dual/quad later on when they come out .
Click to expand...
Click to collapse
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.

Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
Oh ya I know, I just always keep a stock one, on the Inc if you factory reset from an AOSP rom, you'd bootloop, so you had to make sure you were on a Sense 1.0 or stock rom(from my experience), so I was just making sure it was no big deal to go back.
Any idea when we will have cw on this?

Haxcid said:
Doing a factory reset I believe will unroot you. There is no nand back up at this time. We are waiting for a recovery mod.
Click to expand...
Click to collapse
I tried the factory reset. I am still rooted.

navycow said:
I tried the factory reset. I am still rooted.
Click to expand...
Click to collapse
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App

MXFrodo195 said:
That's what i figured. Can anyone verify if you remove SU and Rage through adb will it unroot?
Sent from my VS910 4G using XDA Premium App
Click to expand...
Click to collapse
If you have to return your device, simply remove the superuser app, after you unfreeze anything you may have frozen then factory reset. They honestly will never know it was rooted. The only way now that you can really tell is the super user app from market.

Just so everyone knows. SuperOneClick can root and unroot this phone ok.

navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Thank you for confirming this. My revolution just came in the mail today!

Thanks for posting this here for me Haxcid!
Sent from 1885

navycow said:
Just so everyone knows. SuperOneClick can root and unroot this phone ok.
Click to expand...
Click to collapse
Cool thanks for checking. Any benefits for ADB over S1C? Can't wait to finally root and freeze half these apps. I think we need a few more twitters to praise koush for a recovery on this beast.
Sent from my VS910 4G using XDA Premium App

Is there recovery for this now? Did I miss something?

stetsonaw said:
Is there recovery for this now? Did I miss something?
Click to expand...
Click to collapse
No No, I was saying we need to praise Koush's good work so he will make one faster .
And Stetsonaw, any idea if I root through ADB, can I unroot with S1C, since it uses the same idea.
S1C for whatever reason will not run(tried three computers, a XP, Vista, and Win7 lol), it keeps freezing at the same spot, everytime.

Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.

stetsonaw said:
Should be able to, since S1C does what the ADB method does... or you could just delete the 'su' file out of /system/bin and /system/xbin (if it's there) to unroot.
EDIT: I couldn't get S1C to open on my desktop, and my laptop, which would open the program, would bluescreen when i connected the phone, so i had no choice but to do it the ADB way.
Click to expand...
Click to collapse
Hmmm, ya now my computer for whatever reason won't open up ADB through command. This is getting irritating lol. Should be nice and simple, but it just won't go through. If I downloaded the SDK Manager like 4 months ago, it shouldn't matter, correct?

make sure you change directory to wherever your adb.exe is located... as in:
Code:
cd C:\Program Files\Android\android-sdk-windows\platform-tools

[Fixed] Power button broken. Stuck in stock recovery mode.

Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Edit: Service centre fixed it. Turns out its a pretty complex issue.
Click to expand...
Click to collapse

you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot

nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
Hello, thank YOU very much! I got it to reboot properly and working. And I learnt a lot in the meantime.
Words cannot express my gratitude right now.
I have another question though, is it possible for me to wipe partition cache thru adb?

yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot

nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
Okay, so I tried to do what you suggested, and got stuck at adb root. This is what I got in return:
"Adbd root cannot run as root in production builds"
So what I did was to skip to the second step,
"adb shell"
This is what I got in return:
[email protected]:/ $
I entered the command "su", granted su access on my phone using supersu (got a pop-up) and got this:
[email protected]:/ #
Moving on, I entered "cache /mount" and it repeatedly failed to mount.
I read up a bit of it and it seems like its because my bootloader is not unlocked.
But given the fact that my power button is malfunctioned, I cannot unlock it by normal means. I gave some thought onto PhilZ safe kernel but then the fact that my phone is susceptible to brick if I unlock the bootloader (there will be a data wipe right?) makes me stuck at where I am now.
What are your recommendations?
Additional info on eMMC:
[email protected]:/sys/class/block/mmcblk0/device # cat cid | cut -b 19,20
gives back: 19 (susceptible)
[email protected]:/sys/class/block/mmcblk0/device # cat name hwrev fwrev manfid oemid date type
gives:
Name: VYL00M
HwRev: 0x0
FwRev: 0x0 (not completely safe)
Manfid: 0x000015
Oemid: 0x0100
Date: 01/2012
Type: MMC

nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
you saved me big time!!

I have almost the same problem
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?

FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
Did you find a solution for this?

My Samsung j7 is stuck in recovery mode and power button is broken...and my USB debugging is also ON but phone is NOT detecting On PC...not even in DEVICE MANAGER...I checked in ADB deveices command but still nothing...help me....

FluffyBunneh said:
I bootlooped my tab and forgot to turn on debugging option. I used framaroot for rooting. Only way to make my tab go back to normal is by factory resetting through recovery mode but my Power button isnt working help pls?
Click to expand...
Click to collapse
I also have the same problem, my phone is now stuck in recovery, and without power button I am not able to bring it out of recovery mode, did you manage to find a fix for this? My phone is not getting listed in "adb devices"!

Phone:SM J200G
After installing stock rom via odin
I enter into recovery mode and forget to on USB debugging. Also my power button dead.
What to do? Now?

nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore

I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.

nokiamodeln91 said:
you could try adb.. you need to first install adb .. its included in the android SDK package. eg http://forum.xda-developers.com/showthread.php?t=1241935
once installed.. boot into recovery... connect phone to pc.. go to the adb folder and run command prompt in there.
then use command
adb devices
<the output should show a device connected> if yes then
adb reboot
Click to expand...
Click to collapse
please help i have the same problem but my device is not recognized

bryll1022 said:
hey i got the same problem when i charged my phone after it turn of (low bat). Recovery mode suddenly showed up and i cant choose reboot system now because the lock button is stuck. So i tried the adb and installed it but when i tried to use it . it cant find my device the usb cord is 100% working and idk what to do anymore
Click to expand...
Click to collapse
please help i have the same problem

MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
did you find a solution i have the same problem

MaeButArt said:
I'm having the exact same problem. My power button is broke, I put the phone into Recovery Mode and now I can't get out. ADB can't find my device so I can't use that either. I have no idea what to do.
Click to expand...
Click to collapse
same did anyone find solution for this?

nokiamodeln91 said:
yes using adb shell, you will get the access to file system.
for this adb should run as root.
adb root
adb shell > this should give a # and not $
mount /cache
ls > this should list the files. check for cache folder
rm -r cache
same way dalvik cache (if you want)
cd data
ls > lists dalvik cache
rm -r dalvik-cache
adb reboot
Click to expand...
Click to collapse
when i plug my phone to pc its not connecting if i use commang adb reboot its say "error: no devices/emulators found"

Ive encounter that problem with j4 + what i did is just let the battery run out after that be ready to press button for download mode and insert charging cable to phone, hope this will help on your problem

x33eraser said:
Hello, I am very new to this forum. I searched everywhere but couldn't find an answer to my problem. I really appreciate it if you can help me as I am a total noob in android.
Previously my power button was a little buggy, it works on and off, and I solved it by wiping the partition cache in stock recovery <e3>.
My power button completely stopped working today for no reason that I know off.
Out of frustration, I tried what I did last time by booting into recovery mode (using quickboot this time) but then to realise that I can't choose anything/ get out of the recovery mode.
Nothing works by removing the battery. When the battery is reinserted, it boots back into recovery.
My phone is rooted, non CWM. Has a bad eMMC chip with a susceptible kernel. (latest update from KiES, no custom ROMs)
I got this phone as a prize, so there's no warranty that comes with it.
What can I do now? I have heard of this ADB thing but I have no idea how it works. Does it help? If so, how?
Thank you.
Click to expand...
Click to collapse
Sorry i hope i post this right first timer your guide didnt workt but i found a workaround:
usbc to usb adapter i tryed a mouse not working but my cheab truest cxt tastatur ACCEPTED THE ENTER BUTTON
and i came out of this because only repair loking cost 60 bucks .not with me i hope this help others too
i am doing a tiktok video on it(guide) PrestigeWorldWideUS
buy usbc to usb adapter i try your keybords sorry my english

adb device not found

the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off

RedBlackPellet said:
the device is not found however I installed the drivers and I am using windows 7 I tried it with another computer and it didn't work
and it works with the recovery I want it to work to gain s-off
Click to expand...
Click to collapse
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

nkk71 said:
check FAQ#2: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2
Click to expand...
Click to collapse
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks

RedBlackPellet said:
I tried with different devices laptops and mobiles and I always get device not found and different adb sdks
Click to expand...
Click to collapse
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.

Seanie280672 said:
if your booted into a rom, do you have usb debugging enabled ?
its in system, developer options, if you cant see developer options then goto about - software information - more - and tap build number 7 times, it will count down and eventually say you are now a developer, you should now see developer options in your system menu.
when you enable usb debugging and plug your phone into the computer.....eventually.....and sometimes it takes a while, you will get a pop up on your phone saying your computer wants to connect to this device, allow or deny, I suggest you allow.
if you don't get the message, then with the phone still plugged into the computer, open developer options again and disable usb debugging, then enable it again.
Click to expand...
Click to collapse
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline

RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
im at a loss, sorry I couldn't help any further, but if its doing it with different devices, it has to be a software issue, especially as you say its working in recovery and bootloader, the only thingf I picked out from your picture is it states your adb is out of date, but you say you've tried that too, all I can suggest is you try this one.
http://forum.xda-developers.com/showthread.php?t=2588979
also where did you get the drivers from

RedBlackPellet said:
and sometimes device offline
Click to expand...
Click to collapse
reboot PC and phone, use a USB2 port

RedBlackPellet said:
Ofcourse i even tried different devices and cables and I always get device not found and simetimes device offline
Click to expand...
Click to collapse
why are you using an adb shell to push the file? push the file using adb and then enter the shell to chmod the "ff" file (I suppose you are pushing firewater but your renamed the file to "ff" ?) And btw "adb devices" will not output your device ID from an adb shell.
Code:
adb devices
adb push ff /data/local/tmp
then
Code:
adb shell
su ---> [COLOR="blue"]to get a # prompt[/COLOR]
chmod 775 /data/local/tmp/ff [COLOR="Blue"]--> to give read/write/execute permission[/COLOR]
/data/local/tmp/ff

How to Solve 'Unauthorize Device' in ADB

Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot

Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app

speedyjay said:
Install the Android SDK or install the OnePlus 3 drivers
Sent from my ONEPLUS A3003 using XDA-Developers mobile app
Click to expand...
Click to collapse
What does the Android SDK do mate?
I never used it before, so would be great if u can give me some hints
Thanks

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.

android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).

I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app

tdamocles said:
Make sure debugging is clicked on under developer options in the main menu. Then disconnect the phone from the pc and reboot the pc. Reconnect the phone after it reboots and hope that you get the adb prompt on the phone again.
Click to expand...
Click to collapse
Le_Zouave said:
android sdk have the latest tools including latest ADB. There is ADB standalone install, that means that if you tell us that you have the latest ADB, that only mean that someone extracted the ADB and lastest fastboot and did a repack and in the end it's not an official repack.
but "disable the debug permission" reset all the recorded device for debug so you should have another prompt.
If in the end you don't have another prompt, verify you adb version by installing the lastest android SDK, uninstall and reinstall the oneplus drivers.
Then if no prompt there is 2 choices :
- wipe the phone, it will reset the prompt for sure, 100%
- use another computer (well you have to have another computer).
Click to expand...
Click to collapse
Hello sir, i've been trying all of this method, include the wipe the phone (except using another computer) but still no prompt re-appear. Another advice would be greatly appreciated.
Thanks

joho5 said:
I have a computer at home where this happened and I have never been able to straighten it out...tried everything.
Sent from my ONEPLUS A3000 using XDA-Developers mobile app
Click to expand...
Click to collapse
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho

toughkid said:
Then how's in the end it goes mate? Do you root your phone? I just wanna root it, if u got any other way except the adb that would be great tho
Click to expand...
Click to collapse
Have you checked all of your USB ports? I know in the past (with other phones), problems arise if you're not using a direct USB port (one soldered into your MoBo).

toughkid said:
Hello, im using O+ 3 and just installed the Oxygen 3.2.2 OS
I wanna root it but got problem because my ADB says unauthorized
Ive already tried to dig some similar case and possible answers thru the internet but none of them work for me
Ive tried to enable disable the debug permission
I also already make sure my ADB is the latest one.
Also already try to delete the 'adb_key' files from my PC (im using windows 7 64bit)
The problem is most user which has similar problem with me got the 'authorized debug prompt' popped up again on their phone, but its not working on my phone.
It appear only one time at the very first time i connect it to my phone, but i accidentaly click 'cancel' on that prompt
But after that it never re-appeared again.
Can someone kindly help me? Thanks a lot
Click to expand...
Click to collapse
Go to Control Panel > Hardware and Sound > Device Manager > expand Universal Serial Bus controllers. Now connect your phone. You'll now see USB Mass Storage Device. Right click on it. Select Properties, then go to Details. In the Details section, under Property, select Hardware ids. You'll then see the device id. It will be shown something like this: USB\VID_2A70&PID_9011&MI_01. From this you have to take the 2A70 code ~ the code between the first _ and &. Now go to desktop and create a new text document and copy paste this using your device id as shown:
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x2A70
Now open the Save As menu. In Save As type select All Files. Save the file as adb_usb.ini
Copy this .ini file from desktop and paste it in C:\Users\YourPCName\.android
Disconnect your phone, reboot your pc. Now with USB Debugging turned on, connect your phone to your pc, you'll surely get the permission thingy popup in your phone.

For completion:
If you DO NOT have access to your phone for any reason but still want to use ADB you can simply boot your phone into TWRP and follow these steps.
Windows:
1. Open %userprofile%\.android
2. Copy "adbkey.pub" to your phone (adb push %userprofile%\.android\adbkey.pub /sdcard/adb_keys)
3. Switch to your phone.
4. Go to Advanced > Open Terminal
5. Type in "stop adbd"
6. Move "adb_keys" from /sdcard to /data/misc/adb (mv /sdcard/adb_keys /data/misc/adb/adb_keys)
7. Type in "start adbd"
8. Switch to computer
9. Type "adb shell setprop persist.service.adb.enable 1"
10. Type "adb shell setprop persist.sys.usb.config mtp,adb"
11. Reboot your phone - DONE
Linux / Maybe Mac:
Same steps, but use "~/" instead of "%userprofile%"
Please note:
You may have to repeat the steps 1-7 after boot when still not having permissions so it makes sense to use cp (copy) instead of mv (move) and only repeat steps 5-7.
Edit: Please also check if your drivers are all installed and enabled.
Sent from my OnePlus 2 using XDA Labs

?k