Hi all,
please tell me how can i root my android device without using of any other application like superoneclick or superuser.
i have sony xperia 10 mini
please help me for this.
thanks in advance.
Have you had a look in the x10 forums?
Why do you not want to use superoneclick? It makes life a lot easier. And superuser is an app that you install during the rooting process to give root apps root access to your phone, its pretty much essential.
And also worng section should be in x10 Q&A
Sent from an ice cream sandwich
[email protected] said:
Hi all,
please tell me how can i root my android device without using of any other application like superoneclick or superuser.
i have sony xperia 10 mini
please help me for this.
thanks in advance.
Click to expand...
Click to collapse
you can use super one clicks, it can root also unroot...i used it for my galaxy mini
i don't want to use any third party application for rooting.
i want to root the my android phone using me application.
please tell me if there is any option of this.
The only other way to root is by using adb here are the instructions http://forum.xda-developers.com/showthread.php?t=739874.
Sent from an ice cream sandwich
when i execute this line from cmd
adb push Superuser.apk /sdcard/Superuser.apk
it return error: device not found
and adb devices also return no device list
[email protected] said:
when i execute this line from cmd
adb push Superuser.apk /sdcard/Superuser.apk
it return error: device not found
and adb devices also return this error (device not found).
Click to expand...
Click to collapse
Did you instal the usb drivers?
Did you enable usb debugging on your device?
Did you connect your device?
Ommadawn101 said:
Did you instal the usb drivers?
Did you enable usb debugging on your device?
Did you connect your device?
Click to expand...
Click to collapse
yes i do all these
[email protected] said:
yes i do all these
Click to expand...
Click to collapse
When you connect your device to your pc, make sure you DO NOT select to mount it (or whatever term is used on your operating system)
and then, if you type on the command line:
adb devices
you should get a result with a device list
if you get no devices, then either you did not install adb, or the usb drivers properly
Follow this to find out if you installed adb properly
http://adrynalyne.us/files/How to install adb.pdf
Ommadawn101 said:
When you connect your device to your pc, make sure you DO NOT select to mount it (or whatever term is used on your operating system)
and then, if you type on the command line:
adb devices
you should get a result with a device list
if you get no devices, then either you did not install adb, or the usb drivers properly
Follow this to find out if you installed adb properly
http://adrynalyne.us/files/How to install adb.pdf
Click to expand...
Click to collapse
when i m connected my samsung mobile its adb interface display in device manager in section of ADB Interface,and adb devices command return the samsung device
but when i connect the sony phone with same method firstly its not display in section of ADB interface in device manager, its display in Sony Ercssion sa0101 section.
and when i run adb devices on cmd its not return any device.
and i found one thing when i use SuperOneClick application and use its root option.
than run adb devices on cmd now its return the sony device and not its work fine.
so i want to connect it from my application without the help of SuperOneClick
please help me what can i do.
[email protected] said:
when i m connected my samsung mobile its adb interface display in device manager in section of ADB Interface,and adb devices command return the samsung device
but when i connect the sony phone with same method firstly its not display in section of ADB interface in device manager, its display in Sony Ercssion sa0101 section.
and when i run adb devices on cmd its not return any device.
and i found one thing when i use SuperOneClick application and use its root option.
than run adb devices on cmd now its return the sony device and not its work fine.
so i want to connect it from my application without the help of SuperOneClick
please help me what can i do.
Click to expand...
Click to collapse
I am not sure I am following you.
If you already used superoneclick and it worked for you, why do you need another way of doing it, without superoneclick?
Also, I don't have any of your devices, so I cannot advise you on them.
Sorry
please understand how can i advice to other use any other application for rooting when he used my application.
Related
dear everybody:
Today I using official software and try to upgrade fireware.
Now mine P-500 hardware information
Software Version:LG-P500-V20d
Android Version:2.3.3
Kernal Version:2.6.35.10-perf
Version No.:GRI40
But when I finish this Job.I find my P-500 cann't rooting.
I hope anybody known this question can teach me how to root.
I already use GingerBreak v1.2 but it doesn't work.
thanks for your help.
from what i have read, you cannot root gingerbread (i may be wrong; however i have never seen anyone root official gingerbread before)
if you want to root your phone, consider downgrading your firmware to froyo (which can be rooted):
http://forum.xda-developers.com/showthread.php?t=1060121
i know it says "upgrade" but really it means upgrade from a previous froyo version. it is called downgrade for you since you are going from 2.3.x to 2.2.2
Thanks for your help.
I know this tip.But I want to know rooting this cellphone and no downgrade fireware.
can u tell me how to do this job.
thanks a lot
titan0818 said:
dear everybody:
Today I using official software and try to upgrade fireware.
Now mine P-500 hardware information
Software Version:LG-P500-V20d
Android Version:2.3.3
Kernal Version:2.6.35.10-perf
Version No.:GRI40
But when I finish this Job.I find my P-500 cann't rooting.
I hope anybody known this question can teach me how to root.
I already use GingerBreak v1.2 but it doesn't work.
thanks for your help.
Click to expand...
Click to collapse
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb...ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/atta...5&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
Thanks for your help.
Now I already rooting.
Way for rooting stock 2.3.3 on optimus v/one
See this I rooted mine and it worked
http://forum.xda-developers.com/showthread.php?t=1200167
terratrix said:
How to root LG Optimus One P500 on gingerbread 2.3.3
1. Be sure that you have installed the original V20 GB ROM
2. if you have it installed and tried different methods to root on it do a factory reset before trying this one
3. Be absolutely sure that you have all the phone-drivers installed when working with the phone in USB debugging mode, if not install them (http://www.mediafire.com/file/t3gvrb...ML_Ver_1.0.msi)
4. Download SuperOneClickv1.9.5-ShortFuse (http://forum.xda-developers.com/atta...5&d=1307984755), after download extract the files into a folder with the same name as the archive.
5. After you extracted the files, go to C:\Windows\System32 and copy the cmd.exe to the folder where you extracted the files, in my case C:\Users\myuser\Desktop\SuperOneClickv1.9.5-ShortFuse\ADB.
6. Enter the phone settings menu, to the Development and tick the USB debugging mode. Connect the USB cable to the phone, wait until it recognizes it
7. right click on cmd.exe from the ADB folder, Run as administrator, than write:
adb devices
adb shell
echo 1 > /data/local/lge_adb.conf (do not close the window)
8. Leave the settings to the SuperOneClick as they are when it opens, click on ROOT and wait, it will say Starting ADB server..., than it will do it's job and than it will appear Waiting for device... it will say ok --- if it freezes while running psneuter do the following:
a. Turn USB Debugging OFF wait until it will appear in the window again Starting ADB server..., after that,
b. Turn USB Debugging ON, and after this trick it will start rooting.
Click to expand...
Click to collapse
can use this method to root also by using v20d for our country ??
XeactorZ said:
can use this method to root also by using v20d for our country ??
Click to expand...
Click to collapse
Yes, i tried it personally.
How to Uninstall Chainfire 3D on bricked Devices ...
Here is the solution
1. Connect USB cable and then restart your phone.Get your phone in Recovery Mode....
2. Check whether your device has been detected in the PC - Device Manager - Android ADB Interface.
2. Run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device"). If Device Isn't Detected You need to install Adb Drivers... Download From: adbdriver.com
3. Run "adb shell" from command prompt. If $ came then Type SU. so it will automatically change to #. ( Means your phone rooted and you gain root permission to delete the Bloody CF3D driver from your phone.
*Tip*If You Get An Error Type "# mount -o rw,remount /system" - Press Enter.
4. Still in shell? Type "sh /cf3d_uninstall.sh"
*Tip*if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
Phone will automatically reboot and will be ready.
Don't Forget To press Thanks.....
:victory::victory::victory::victory::victory::victory::victory::victory:
N'ayam Amarsh'e said:
How to Uninstall Chainfire 3D when bricked Device ...
Here is the solution
1. Connect USB cable and then restart your phone.Get your phone in Recovery Mode....
2. Check whether your device has been detected in the PC - Device Manager - Android ADB Interface.
2. Run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device").
3. Run "adb shell" from command prompt. If $ came then Type SU. so it will automatically change to #. ( Means your phone rooted and you gain root permission to delete the Bloody CF3D driver from your phone.
4. (only for users which have ADB locked or get Operation not Permitted).Then type # mount -o rw,remount /system - Press Enter.
5. Still in shell "sh /cf3d_uninstall.sh"
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
Phone will automatically reboot and will be ready.
:victory::victory::victory::victory::victory::victory::victory::victory::victory:
Click to expand...
Click to collapse
I have my device bricked with Chainfire 3d but when I use adb devices it does not show anything and also it is in Recovery mode.
jxgreat said:
I have my device bricked with Chainfire 3d but when I use adb devices it does not show anything and also it is in Recovery mode.
Click to expand...
Click to collapse
Hi ,
Do You Turned ON USB DEBUGGING If Yes then....
I think you don't have ADB drivers installed... Here You Go - http://adbdriver.com/upload/AdbDriverInstaller.exe
IF NOT
Then I am sorry i can't help, also which phone do you have??
N'ayam Amarsh'e said:
Hi ,
Do You Turned ON USB DEBUGGING If Yes then....
I think you don't have ADB drivers installed... Here You Go - http://adbdriver.com/upload/AdbDriverInstaller.exe
IF NOT
Then I am sorry i can't help, also which phone do you have??
Click to expand...
Click to collapse
No I didn't.
I have Huawei Ascend Y320 U30.
So what should I do now? Through this mobile in junk? I just brought it couple of days ago.
My pc didn't detect any devices when I connecting asus memopad 8 in recorvery mode
is this will work with motorola razr d3 xt919 its bricked with chainfire and please can you give the link of what i neet for this thank you
---------- Post added at 09:48 AM ---------- Previous post was at 09:40 AM ----------
And yes i wiped dilveck cache and factory reset now what will happen please help me
N'ayam Amarsh'e said:
How to Uninstall Chainfire 3D when bricked Device ...
Here is the solution
1. Connect USB cable and then restart your phone.Get your phone in Recovery Mode....
2. Check whether your device has been detected in the PC - Device Manager - Android ADB Interface.
2. Run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device").
3. Run "adb shell" from command prompt. If $ came then Type SU. so it will automatically change to #. ( Means your phone rooted and you gain root permission to delete the Bloody CF3D driver from your phone.
4. (only for users which have ADB locked or get Operation not Permitted).Then type # mount -o rw,remount /system - Press Enter.
5. Still in shell "sh /cf3d_uninstall.sh"
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
Phone will automatically reboot and will be ready.
:victory::victory::victory::victory::victory::victory::victory::victory::victory:
Click to expand...
Click to collapse
I have viewsonic vb734 tablet running gingerbread ROM , its a Chinese tablet. i have root access but I wasn't able find custom recovery , thats why i didn't made nandroid backup , so the thing is that I installed chainfire 3d and now I am stucked on boot loop without any recovery , Is there any way to fix it ? Thanks
heres the link of my device, http://forum.xda-developers.com/showthread.php?t=1393128
huzaifahaziz said:
I have viewsonic vb734 tablet running gingerbread ROM , its a Chinese tablet. i have root access but I wasn't able find custom recovery , thats why i didn't made nandroid backup , so the thing is that I installed chainfire 3d and now I am stucked on boot loop without any recovery , Is there any way to fix it ? Thanks
heres the link of my device, http://forum.xda-developers.com/showthread.php?t=1393128
Click to expand...
Click to collapse
You dont need a custom recovery you can do it with stock ones also
sir tnx for this guide it will help me to unbrick my galaxy y
Thanks
N'ayam Amarsh'e said:
You dont need a custom recovery you can do it with stock ones also
Click to expand...
Click to collapse
Okay, I Will try it .. thanks for the help
hello, please help me I also installed Chainfire 3D on my phone and now it is stuck on the booting screen. please tell what should i do? My device is Lava Iris 404e.
learner4 said:
hello, please help me I also installed Chainfire 3D on my phone and now it is stuck on the booting screen. please tell what should i do? My device is Lava Iris 404e.
Click to expand...
Click to collapse
Did you read post #1? Followed the steps? Should solve your problem.
PS: You can reflash your rom/firmware, it will for sure get rid of CF3D and this bootloop, too.
PS2: I googled your phone model, it runs Android 4.2. CF3D supports officially only 2.1 - 2.3.
Enviado de meu Nexus 4 usando Tapatalk
Yes i tried that step but it gives an error saying that directory not found. I also tried to find the stock rom for my device but its not there on any of the website.
Hey thanks! Now my phone is working. What i needed to do was that when i rebooted my device in recovery mod and plugged it in my pc, my device was not detected even when i installed latest drivers for my device. But when i rebooted my device in factory mode, it was detected so i was able to fix it.:laugh:
Can't access to adb shell
N'ayam Amarsh'e said:
How to Uninstall Chainfire 3D when bricked Device ...
Here is the solution
1. Connect USB cable and then restart your phone.Get your phone in Recovery Mode....
2. Check whether your device has been detected in the PC - Device Manager - Android ADB Interface.
2. Run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device").
3. Run "adb shell" from command prompt. If $ came then Type SU. so it will automatically change to #. ( Means your phone rooted and you gain root permission to delete the Bloody CF3D driver from your phone.
4. (only for users which have ADB locked or get Operation not Permitted).Then type # mount -o rw,remount /system - Press Enter.
5. Still in shell "sh /cf3d_uninstall.sh"
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
Phone will automatically reboot and will be ready.
:victory::victory::victory::victory::victory::victory::victory::victory::victory:
Click to expand...
Click to collapse
I'm pretty sure that my device is detected. But when i type "adb shell", its says, ' /sbin/sh/' failed: permission denied <13>
What do i do? Please help guys!!
I just bricked my device need a stock rom of Alps GT-I9600 mt6572 device
I just bricked my device need a stock rom of Alps GT-I9600 mt6572 device
please someone help me. I'll be great full to you Thanks in advance....and sorry for bad english :crying:
Great Work - Favor to Ask
N'ayam Amarsh'e said:
How to Uninstall Chainfire 3D when bricked Device ...
Here is the solution
1. Connect USB cable and then restart your phone.Get your phone in Recovery Mode....
2. Check whether your device has been detected in the PC - Device Manager - Android ADB Interface.
2. Run "adb devices" - to make sure the phone drivers are ok (should output a long hex string and "device").
3. Run "adb shell" from command prompt. If $ came then Type SU. so it will automatically change to #. ( Means your phone rooted and you gain root permission to delete the Bloody CF3D driver from your phone.
4. (only for users which have ADB locked or get Operation not Permitted).Then type # mount -o rw,remount /system - Press Enter.
5. Still in shell "sh /cf3d_uninstall.sh"
if sh /cf3d_uninstall.sh doesnt work , try 'sh /system/lib/cf3d_uninstall.sh" instead.
Phone will automatically reboot and will be ready.
:victory::victory::victory::victory::victory::victory::victory::victory::victory:
Click to expand...
Click to collapse
Nice clear instructions - Ran into a problem - Believe the cf3d_uninstall.sh is corrupt and desperatly need a copy - Definite donation your way - Thanks!
j518 said:
Nice clear instructions - Ran into a problem - Believe the cf3d_uninstall.sh is corrupt and desperatly need a copy - Definite donation your way - Thanks!
Click to expand...
Click to collapse
Thanks to say but I don't take Donations But Can't give you the file now ... You can reequest someone to pull the file for you... or I think the file isn't corrupt something other is wrong... it generally doesn't happen or It never has happened...
jepoy75 said:
I'm pretty sure that my device is detected. But when i type "adb shell", its says, ' /sbin/sh/' failed: permission denied <13>
What do i do? Please help guys!!
Click to expand...
Click to collapse
This means your phone isn't rooted properly... that's why it shows error...
learner4 said:
hello, please help me I also installed Chainfire 3D on my phone and now it is stuck on the booting screen. please tell what should i do? My device is Lava Iris 404e.
Click to expand...
Click to collapse
Follow My guide....Simple???
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
androidferret said:
Hey guys sorry if this is newb question but I've been looking for hours and just getting overwhelmed.
I have an SPC glow 10.1 cheap tablet purchased in Spain, apparantly a rebranded Chinese tab.
Android version 6.0, tried rooting with Kingoapp APK which was a complete fake waste of time. Tried framaroot, it said the exploits don't work.
Where should I be looking to be able to root something like this? I.e. which app/project like Xposed or Magisk here?
Thanks a lot
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Augustoandro said:
Have you unlocked the bootloader?
Click to expand...
Click to collapse
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
androidferret said:
No, I have not, how would you do that? There is no info on the Internet if I search for this brand name SPC.
Is there a way to find out which Chinese tab this is a rebrand of perhaps? Thanks
Click to expand...
Click to collapse
Please take a backup of ur data before proceeding further.
Try this,
Download adb and Koush Universal adb driver and install them on ur pc, always install the driver first and don't install the drivers adb setup asks u to install.
Run command prompt as administrator.
Open the folder in c drive where adb is installed, u can use file explorer for this.
Press Shift+right click and select open command window here.
Enable USB debugging on your phone and connect it to the pc by a USB cord.
Enter command "adb devices" without quotation marks.
If it shows some device connected, only then proceed further.
Enter command " adb reboot bootloader"
Enter command " fastboot devices", if it shows some device to be connected, only then proceed further.
Enter command " fastboot oem unlock".
Ur phone may then ask for final confirmation on the phone screen, select yes.
When procedure completes, type "fastboot reboot" and ur phone will reboot.
U can now use Kingoroot or any other tool for rooting.
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
androidferret said:
Thanks Augusto, your advice was great,
it worked so far, but it wasn't easy getting there.
Here's what I did for others:
1. Installed adb and fastboot on my computer from Android developers, turn on debugging on tablet
2. Downloaded universal USB driver installer (aka. koush driver)
3. Installed but adb did not see my tablet, turns out the tablet is not in the list for the USB driver installer
4. Downloaded source code for koush driver, had to modify the .inf file as described in one of the comments on the github page,
by copy pasting two of the existing lines in the inf file and replacing with the USB id codes found from Device Manager in Windows 7.
5. After modifying the .inf file was able to install the driver from Device Manager "Update Driver..." for the Android device
6. Finally after this adb was able to see it under "adb devices"
7. Restart to bootloader with the command "adb reboot bootloader", this entered fastboot on my tablet
8. Tried to run "fastboot devices" but again the phone is not seen.
9. Apparently when in fastboot mode, the tablet appears under completely different USB ids which can be seen in Device Manager
10. Had to go back to the same .inf file and add two more lines with the new Device IDs
11. Installed the driver again in Device Manager, "Update driver"...
12. Now fastboot can see it too!
13. Entered the command "fastboot oem unlock", got the message that the unlock failed!
14. Had to restart tablet in normal mode go into Developer Options and set "OEM unlock"
15. Reboot to fastboot, unlock now works! Reboot phone using "fastboot reboot"
A strange thing happened at this point, the little android figure with cogs in his stomach came up for a few seconds, then the OEM logo for a long time,
after waiting a few minutes I force reset it. It started up but the system was completely erased and put into factory state, including completely erasing every single file I had on it,
even pictures, etc., it asked the first install questions from the very beginning. Fortunately I didn't have anything valuable.
So I got this far, now I'd like to root it,
I tried framaroot, not working, I don't trust Kingoroot, any recommendations for the root method from a reliable source?
Click to expand...
Click to collapse
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Augustoandro said:
I told you to take backup of your data beforehand.
I am recommending Kingoroot because I personally used it to root my phone.
Click to expand...
Click to collapse
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
androidferret said:
I know about the backup, I just wasn't expecting it to wipe everything, I don't know why it did that.
As for Kingoroot, I installed the official app from play store which was a completely fake and dangerous looking piece of crap,
it showed like 50 ads asked me to rate it and then some weird pop ups kept coming, and then it did nothing. No message whatsoever.
Thank god my phone wasn't rooted because
I don't know what the lowlifes who do KingoRoot would have done with it.
I don't trust this company to install their software on my computer and I can't believe you guys recommend such an obviously
unscrupulous, malware product to others. Why is KingoRoot even on Google Play, they should be among the trojan trash of the every single antivirus and antimalware.
Click to expand...
Click to collapse
I meant Kingoroot for PC and not Kingoroot Android.
They are different, although from the same company.
Wow it turns out I was using a fake Kingoroot from the Play Store so I take back my comments regarding KingoRoot.
I can't believe the Play Store allows such trash.
Hi All,
Hoping you can help I have an xperia tablet which was on Android 5.1.1 and which i tried to upgrade to 7 and think i may have screwed it up.
I was using lineage OS guidance. I am using ADBdriver tool. Currently the table is stuck in twrp recovery. When in fastboot mode I can use the fastboot devices command and see the device. I can use the fastboot flashboot command and flashboot reboot.
When i try to use the adb push (imagefile) command it says adb: error failed to get feature set : no devices/emulators found.
If i use adb devices command it doesn't see anything.
In device manager I have under android device a device called 'google nexus ADB interface'....not sure if this should say xperia, not sure how to change it. Sony website advises using ADB version 26.0.2 I have tried that and version 26.0.0.
At this point I'd be happy to flash the xperia boot on instead in the hope that would fix it but i don't know where to find it.
Just to add, I have installed the sony flashtool. I can see the device, apparently there is way to put back a sony boot using the tool but I don't know where to get one.
Using 'Emma' I have a working device now but its on 4.4.4. which isn't great! Any ideas?
So I'm not sure what to do and would massively appreciate some help
Thanks
evilistix said:
Hi All,
Hoping you can help I have an xperia tablet which was on Android 5.1.1 and which i tried to upgrade to 7 and think i may have screwed it up.
I was using lineage OS guidance. I am using ADBdriver tool. Currently the table is stuck in twrp recovery. When in fastboot mode I can use the fastboot devices command and see the device. I can use the fastboot flashboot command and flashboot reboot.
When i try to use the adb push (imagefile) command it says adb: error failed to get feature set : no devices/emulators found.
If i use adb devices command it doesn't see anything.
In device manager I have under android device a device called 'google nexus ADB interface'....not sure if this should say xperia, not sure how to change it. Sony website advises using ADB version 26.0.2 I have tried that and version 26.0.0.
At this point I'd be happy to flash the xperia boot on instead in the hope that would fix it but i don't know where to find it.
Just to add, I have installed the sony flashtool. I can see the device, apparently there is way to put back a sony boot using the tool but I don't know where to get one.
Using 'Emma' I have a working device now but its on 4.4.4. which isn't great! Any ideas?
So I'm not sure what to do and would massively appreciate some help
Thanks
Click to expand...
Click to collapse
Upgrade via OTA to latest stock 5.1.1 or via xperia-companion app.
Also you can flash 5.1.1 via Flashtool v0.9.18.6.
Great, thanks for your help.
Not sure if this is the proper place for this question; if not, please move. I picked up an Irulu Expro No. X9 Android tablet on eBay. It seems to work fine, except I can't get past the login screen. I tried many times the various key combinations to get it into recovery mode but none worked. Other suggestions had me putting it in debug mode first, but how to do that if you can't get logged in? I'm not concerned about saving any data, I would just like to be able to use it. I would appreciate any help to solve my problem. Thanx.
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
jwoegerbauer said:
@jrockow
Have you ever tried to check whether the device is accessable by means of ADB?
Code:
adb devices
If it's accessable then you easily can remove the password lock. You do this by launching Android Settings via ADB as shown next:
Code:
adb devices
adb shell am start -a android.settings.SETTINGS
Click to expand...
Click to collapse
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
jrockow said:
Thanx for your quick reply.
adb devices doesn't list anything.
I thought you needed to enable USB debugging for ADB to work?
Don't know how to do that if I can't log in.
Click to expand...
Click to collapse
OK, so I'm somewhat of a rookie when it comes to ADB and FASTBOOT.
I'm not sure I have everything correct. I'm using an app called "Minimal ADB and Fastboot".
I have another tablet, same as the one I can't access, and I have turned on the developer options.
Even with that, I still can't see any devices when I run ADB.
FYI: When I look at devices in my PC it shows up as X9, which I believe is correct.
With my no password tablet, I can actually see all the directories of my Android on my PC.
If I try that with the other one don't see any directories.
jrockow said:
With my no password tablet, I can actually see all the directories of my Android on my PC.
Click to expand...
Click to collapse
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
jrockow said:
I'm using an app called "Minimal ADB and Fastboot".
Click to expand...
Click to collapse
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
jwoegerbauer said:
Android's USB in that case is set to MTP mode, not ADB mode. MTP operates at the file level. Your Android device doesn’t expose its entire storage device to Windows computer. Instead, when you connect a device to your computer, the computer queries the device and the device responds with a list of files and directories it offers.
When Andoid's USB is in ADB mode, device can completely get controlled from Windows computer.
Serious Android device owners use the USB-driver ( AKA ADB ) as provided by device's OEM/Carrier.
Click to expand...
Click to collapse
I was incorrect in my earlier post, when I said I turned on the developer mode on my "good" tablet and I still couldn't access it thru ADB.
I found out I really didn't have it turned on, and when I did I was able to execute the ADB commands.
That gets me back to my earlier post about not being able to turn on the developer mode on my "bad" tablet if I can't log in.
I would think with all the guys working on this stuff someone has come up with a way to get around a lost password?
I remind you, I tried the power+volume sequence many times, many ways, so I need a different approach; if there is one?
Thanx.
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
jwoegerbauer said:
@jrockow
Because the tablet can't connect with PC via ADB then wondering why you don't contact seller of the tablet? Unlock Screen Password always can be done with Google Account Android device initially was bound to.
Click to expand...
Click to collapse
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
jrockow said:
I have already reached out to the seller. However, he knows nothing of the history of the tablet. He's just a guy who collects tons of electronics and sells them on eBay.
What really frustrates me is I can quite easily get my "good" tablet to enter recovery mode with the power+vol combination. I have tried many, many times to duplicate the same combo on the "bad" tablet and it just jumps over the recovery mode and boots to the logon screen.
Is it possible someone made some change to the tablet that won't allow it to go into recovery?
Click to expand...
Click to collapse
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
jrockow said:
So, I've come to the conclusion that what I'm asking for just can't be done.
Can't enter reset with any key combo I've tried; can't use ADB because debugging not on; can't go to Google because I don't know who owned the phone before me.
If this were a PC device, there are multiple apps available to get around a lost password. I've done it many times.
I was really hoping there would be some Android genius out there who could help.
What a shame to realize that a perfectly good working device might as well be thrown in the trash.
Click to expand...
Click to collapse
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
jwoegerbauer said:
If you know that the phone basically supports ADB, if the phone has a slot for external SD-card, if you can boot into Recovery Mode, if the Recovery Mode allows you to "apply update from sd-card" then you by means of an OTA can enable USB-debugging, then you can access the phone via ADB.
Currently I'm working on such an UPDATE.ZIP and will, if it's bug free, it publish here on XDA.
Personally don't own a phone what supports ADB: it's a HUAWEI Y7 2019. If you are willing to become a tester let me know it. I'll then PM you the link to the UPDATE.ZIP.
Click to expand...
Click to collapse
If I could boot into Recovery Mode my problem would be solved.