Related
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
YouthTeam said:
Making defy miui patchrom JB4.2，and it has finished.
But can‘t reboot into system. and can't adb logcat :crying:
===============
$ adb devices
List of devices attached
0123456789ABCDEF unauthorized
$ adb shell
error: device unauthorized. Please check the confirmation dialog on your device
===============
In system, I know how to Allow USB debugging
but It can not enter into SYSTEM now， how to solve the adb devices unauthorized?
Android Debug Bridge version is 1.0.31
Help me~
Click to expand...
Click to collapse
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
also check for developer->usb debugging notify...
Anarkista7 said:
First Ensure that your cell phone is rooted. after that...
On the same window option in System Settings - Find an option called "Root Access" and select "Apps and ADB" option.
I hope its help you
Click to expand...
Click to collapse
I was having the same problem. I also had a box that said 'USB debugging notify' checked and didn't notice the device asking for permission to run adb right after I did the kill-server and start-server. As soon as I hit 'ok' the unauthorized problem went away.
Thanks to all on the thread.
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
problem
I am having a similar problem as well. My old Samsung Galaxy S is stuck on bootloop. Home button is dead so I cannot acces download mode/recovery mode manually and in adb device is unfortunately unauthorized
Any way to go around this ?
unauthorized device, unable to adb anything
[email protected]:~$ adb reboot bootloader
error: device unauthorized. Please check the confirmation dialog on your device.
[email protected]:~$
[email protected]:~$ adb devices
List of devices attached
FA2BDS501095 unauthorized
With the phone connected via usb I went to Dev. Options, unchecked USB Debugging then rechecked it, instantly the confirmation dialog box came up regarding the RSA Key for my laptop. Check the box so it remembers your computer and hit save.
Same Problem! Phone stuck on Samsung logo
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
are that problem was solved?
how?
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
No RSA key dialoge either
I have seen some RSA key apps but they are for creating keys. How can I get the dialoge to come up. I have a HTC One M8 831c ROOTED twrp recovery BadSeeds Stock Rooted ROM SuperSU PRO updated. Its on a Harman Kardon Edition which seems to be a little off from the other versions.
emko7 said:
What do you do if the RSA key dialog never comes up?
I have root, I have usb debugging enabled.
I've tried revoking authorizations.
I've tried adb kill-server followed by adb start-server
I've tried changing from MTP to MSC (those are the only two options I have)
I've tried on both an Xperia Z2 and an Xperia Z3 Tablet compact.
Both have the same problem.
Click to expand...
Click to collapse
I have the same exact problem as you. Have you found a solution?
same problem
I have root
have deleted critical system files via titanium backup
i have USB debugging enabled
have revoked authorizations
i have systemui error which loops every time I boot
no home button functionality
no actual phone application any longer
no drop-down notification available, however banner notifications do present themselves only to disappear out of reach above the screen edge.
I have done everything the previous poster mentioned, and my problem is virtually identical to theirs.
Due to these particular circumstances, I am unable to receive the RSA prompt menu and authorize ADB.
I have root access but cannot enter ADB into root mode due to unauthorized device errors.
i am unable to do anything with shell functions as well
my phone is practically disabled at this point, to do anything useful is a daunting task of escaping and passing by the looping systemui error in order to slip into subsequent menus/functions.
The only solution I have found is to rebuild the boot.img file such that it excludes the RSA protocol or over-rides it.
factory restore does not remount vendor partition files no luck restoring from SD or cache.
I am sure I could rebuild the file but I would be pushing my boundaries, something I don't have particular time for at this moment. Being too busy with academics that currently dont encompass coding, I have no time to study on this one...
I will be happy to do my due diligence whatever the case may be, however...I need some answers. My phone is out of commission.
Same problem, did u get the solution?
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
Please help me. I rooted my phone with the procedure given at:
wiki.cyanogenmod.org/w/Install_CM_for_nicki
Now , after doing
fastboot flash boot boot.img
fastboot reboot
i did -> wipe data/factory reset.
after that when i tried -> adb sideload <my cm12.1 package name>.zip
i am getting this msg.
error: device unauthorized. Please check the confirmation dialog on your device.
when i typed -> adb devices
i got my device unauthorised.
Please help me, i am desperate.
for some reason I dont get the adb authorize box on my watch anymore (to adb reboot bootloader) its says "error: device unauthorized. Please check the confirmation dialog on your device." but there is no way to enable the authorisation anymore.
I also face this problem with pop 2 4.5 5042d; unauthorized and phone in bootloop with no fastboot
No OS installed so not able to Allow USB debugging.
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
---------- Post added at 10:03 AM ---------- Previous post was at 09:10 AM ----------
Im_Rohit said:
I accidentally Wipe all data using TWRP. Now no OS is installed so not able to allow USB debugging. and adb showing unauthorised device error. Because of it not able to push anything into my phone.
Can somebody help me with this???
Click to expand...
Click to collapse
I used OTG instead of internal storage and it works.
jleonardol said:
I'm having the same problem, but a bit worst.
I accidentally erased my OS, so how can I solve that issue without an OS?
Click to expand...
Click to collapse
same problem--- any idea to solve my problem???
thanks
abhi26 said:
So guys,
I am stuck with this really bad problem : http://forum.xda-developers.com/galaxy-s3/help/nand-write-start-completewrite-t1846867/page4
and essentially my phone is unable to start up and gets stuck at the Samsung Logo.
So I am faced with the same error message of phone being detected by adb but unauthorized. Is there any way to access the root of the device overriding the authorization?
I had done adb before so it has to be checked within the settings.
Thanks a lot! Any help is appreciated!
Click to expand...
Click to collapse
Your phone might be bricked. Did you recently try to root it?
bit late to the party, but this worked for me
I had RSA ADB fingerprint issues, worked for ages then stopped working, went through every forum post and nothing worked, then found this post.... stackoverflow.com/questions/31638582/android-adb-devices-unauthorized[/url]
opening a cmd prompt in this location C:\Users\<your user name>\AppData\Local\Android\sdk\platform-tools and running adb from here and it worked straight from the off.
i've spent 2 nights working on this, so if it helps anyone
my screen broke and picture is completely ****ed and useless.
is it possible to enable USB debugging without using the touch screen? i want to mirror the phone to a laptop and pull my work hour sheet
edit : As of today - 28th June, this method ONLY works on the H815 EU models
update 26th July : Please go check the dream team's ROOT thread located here : [ROOT] TMO/VZW/ATT/SPRINT/INTL Root your LG G4 with Low Effort Root!
Thanks @thecubed , @autoprime , @IllegalArgument & @jcase for their hard work
Hi guys, a quick step by step guide to how I was able to unlock, install TWRP and Root my H815. Please don't hold me responsible if any issues arise with your phone. If you do this, you take your own responsibilities.
I tend to download all the tools in a single folder so it is easier to manage.
The LG Site:
1. go to this LINK and register.
2. you will get a confirmation email.
3. go to this LINK to unlock your bootloader (you will find the information on how to get your IMEI and Device ID lower in the post)
Your PC :
1. Be sure to have the LG drivers (i connected my phone first, it automatically installed the drivers on the computer.
update 27th July : thanks @the_scotsman in case you have driver issues please download these provided by @autoprime : LGUnitedMobile_Win_Driver_Ver_3.14.1
2. Be sure you have installed the ADB stuff that can be found here : Minimal ADB & Fastboot & ADB Installer (type Y to all the questions asked)
Install Minimal ADB first. Then type Y to all the questions the ADB installer asks. Close both windows once done.
Download TWRP 2.8.7. for H815:
1. go to this LINK and download it. Add it to your folder
Download SuperSu 2.46:
1. Download SuperSu 2.46 HERE (thanks @Chainfire ) and add it to your folder
PC & G4 love :
Once you are sure you have completed all the above tasks start rolling :
A. Enter your IMEI on the LG page
- you can find your IMEI on the G4 by going to settings > about phone > status
B. Get your Device ID:
1. hook up your LG on your PC (be sure not to be locked on your lockscreen, That USB debugging is checked and OEM checked in the Developer Options)
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
4. You will see two lines of number. Copy them and paste them together (to make one line) in the the Device ID fields on the LG site.
5 type :
Code:
fastboot reboot
5. close CMD
5. click Confirm on the site and you will receive by email a file called : unlock.bin.
Unlocking your bootloader:
1. once you get your LG email, save the unlock.bin in your folder
2. launch CMD from the folder (hold shift, right click the folder)
3. in CMD type :
Code:
adb reboot bootloader
4. once your phone is rebooted in bootloader type :
Code:
fastboot flash unlock unlock.bin
5. then reboot your phone by typing :
Code:
fastboot reboot
Normally your phone now has it's bootloader unlocked. When it boots you should see a message on the top left of the screen saying that.
COPY SuperSu and the downloaded TWRP file onto your phone (i put it in the download folder in the phone, not the SD) so you are ready for the next steps
Booting TWRP via ADB and bootloader mode
I personally think this was the easiest way to be able to root and clean install TWRP. Be sure your TWRP is in the folder.
1. Launch CMD from the folder (hold shift, right click the folder)
2. type (again) :
Code:
adb reboot bootloader
3. once your phone reboots and is in bootloader mode type :
Code:
fastboot boot TWRP2861.img
the new name of the file
or
Code:
fastboot boot p1.img
if you didn't rename it.
4. now you will reboot into TWRP.
Installing SuperSu
1. once you are in TWRP click install and go find your SuperSu file.
2. Swipe to install.
3. Once installation is done, reboot to system.
Once you have rebooted into the OS you will find the SuperSu app. Download the TWRP manager just to have it handy. And now i would install the TWRP file you have copied on your phone with flashify. I think it's a great tool.
2 ways to do it:
1. locate the file, click on it and choose to open with flashify then choose recovery and follow the steps
2. find the file via flashify and install.
(Don't download TWRP for H815 in the TWRP manager or Flashify as they are not fixed by @wolfgart (correct me if I am wrong))
once all this done and rebooted. Your phone will have TWRP and would be Rooted. Choose the TWRP manager to boot into recovery when you want.
I preferred to reboot the phone every time just to be sure...
If you have any comments, or i wrote something wrong, don't hesitate to correct me.
Have fun
UPDATE : Thanks to @autoprime you can also update your H815 EU to the latest Stock ROM : 10C (don't forget to thank him, as those guys are working hard to make your life easier!)
@the_scotsman, maybe you can pin this to help the lost souls until a one app does it all appears?
Well that was quick.
mediumraresteak said:
Well that was quick.
Click to expand...
Click to collapse
Looks like it depends on getting info from LG... let's see how long that lasts!
Forgive me if im mistaken but there are already like 3 threads about this i believe.
Sent from my LG-H815 using Tapatalk
I read the LG boot unlock affects streaming services. Can you tell me if it's still possible to stream music from the google play music app, and also YouTube ? Cheers.
barondebxl said:
Forgive me if im mistaken but there are already like 3 threads about this i believe.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have seen threads discussing about it yes, but haven't seen a clear guide on "how to" do it. Please enlighten me and i will ask this thread to be deleted. I don't like multi threads on the same subject, so i would be the first to ask that this thread be deleted.
pcoulson said:
I read the LG boot unlock affects streaming services. Can you tell me if it's still possible to stream music from the google play music app, and also YouTube ? Cheers.
Click to expand...
Click to collapse
I haven't had any issues with DRM, Camera or netflix streaming
SAO said:
I have seen threads discussing about it yes, but haven't seen a clear guide on "how to" do it. Please enlighten me and i will ask this thread to be deleted. I don't like multi threads on the same subject, so i would be the first to ask that this thread be deleted.
I haven't had any issues with DRM, Camera or netflix streaming
Click to expand...
Click to collapse
Yeah there arent any other guide, just threads discussing it. It just seems a lot since the LG site is pretty clear and self explanatory.
Sent from my LG-H815 using Tapatalk
I'm stuck on "fastboot oem device-id" command in cmd. Everything up to that point goes smoothly.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
I have USB debugging on, also the OEM unlock is checked in development options.
Eclap78 said:
I'm stuck on "fastboot oem device-id" command in cmd.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
Click to expand...
Click to collapse
unplug your device, if you can't restart it, by keeping your finger pressed for 10 seconds on the power button, take battery out.
Once you put the battery back in, restart the phone, plug in the phone in the computer, restart the CMD, and start the procedure again. :
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
SAO said:
unplug your device, if you can't restart it, by keeping your finger pressed for 10 seconds on the power button, take battery out.
Once you put the battery back in, restart the phone, plug in the phone in the computer, restart the CMD, and start the procedure again. :
2. launch your CMD and type:
Code:
adb reboot bootloader
your phone will reboot
3. type this to get your Device ID
Code:
fastboot oem device-id
Click to expand...
Click to collapse
I've tried this a few times now, same outcome, same thing, don't get a code, only get the 3 options and the power off 10 second thing, which doesn't work btw, have to pull battery every time
The numbers should show on your CMD window on your computer not the phone.
If the CMD window only shows "waiting for device", did you try to shut the CMD windows?
SAO said:
The numbers should show on your CMD window on your computer not the phone.
If the CMD window only shows "waiting for device", did you try to shut the CMD windows?
Click to expand...
Click to collapse
ah, thought they were supposed to show on the phone screen.
not sure what you mean by shutting the cmd window? I just get stuck on that "waiting for device" message in cmd, at which point I unplugged the phone, did a battery pull and tried again. I've tried about 5 times now, I double checked everything, have all the drivers installed etc.
Oh, and I do have the h815 EU version of the G4. I'll keep digging.
Could someone try out netflix, camera, divx files, YouTube and all the things that people were afraid of loosing. I for myself would really like to root but I dont want to loose any functions by doing that.
Sent from my LG-H815 using Tapatalk
Pyrres said:
Could someone try out netflix, camera, divx files, YouTube and all the things that people were afraid of loosing. I for myself would really like to root but I dont want to loose any functions by doing that.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I have no issues with Netflix, divx, camera or YouTube.
Just a reminder that this does not work with all H815's as of 6/5/15. I think those of us that got a non EU region specific H815's get stuck when requesting a bootloader unlock from LG. Most of us are getting "not found suffix" when trying to submit the IMEI# and device ID. Note: trying different internet browsers does nothing, so don't bother.
We'll have to wait for LG to either approve all region G4's or another method. Cheers for making a guide though.
AhsanU said:
Just a reminder that this does not work with all H815's as of 6/5/15. I think those of us that got a non EU region specific H815's get stuck when requesting a bootloader unlock from LG. Most of us are getting "not found suffix" when trying to submit the IMEI# and device ID. Note: trying different internet browsers does nothing, so don't bother.
We'll have to wait for LG to either approve all region G4's or another method. Cheers for making a guide though.
Click to expand...
Click to collapse
Thanks for the heads up.. i have put this in red in the first post.
Eclap78 said:
I'm stuck on "fastboot oem device-id" command in cmd. Everything up to that point goes smoothly.
command line says "waiting for device" and the phone screen doesn't show phone ID, but gives me options 1-3. 1 being to show device ID, can't remember what the other ones are now. But I can't select "1". What am I doing wrong?
I have USB debugging on, also the OEM unlock is checked in development options.
Click to expand...
Click to collapse
Got the same Problem and fixed it, because, that are restriction/Firewall/Domaincontroler/Groupright Problems on ur PC.
Here the link, were i short explain my problem. http://forum.xda-developers.com/g4/general/howto-unlock-twrp-root-1-thread-t3130538
And now i see there is a HOWTO Thread
SO i have doubled it :crying:
But same answers like here "we got like 5 Threads", but like u said @SAO NOT 1Thread were all-in-one is explained! :good:
Is there a reason why we have to temporarily boot into TWRP to install root and then install TWRP via a secondary method?
Like, why can't we just do a "fastboot flash recovery twrp.img" command to install TWRP like most other devices with an unlocked bootloader?
Does this method break DRM?
takuhii said:
Does this method break DRM?
Click to expand...
Click to collapse
yes
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
alpheus said:
Hi guys,
I searched forums, web with no positive results. So I start a new thread. Here is the situation: one day my Nexus S (Worldwide edition) froze on restarting with the Google Logo on the screen. Every time I try to turn the phone on it stacks at Google logo. When in the fastboot mode the status is Locked. Every time I try fastboot oem unlock I get Phone’s prompt with Yes or Not to unlock bootloader and after choosing Yes, the status doesn’t change to Unlock. Tried on Linux, Mac, Windows (drivers installed successfully), the same result. Tried to force Flash Stock + Unroot in Wugfresh, doesn’t work due to the Locked Bootloader.
typing "adb devices" in cmd (should return the device number) shows:
List of devices attached
......
Empty line above
Any word of advise how to force Unlocking the Bootloader would be greatly appreciated. Please help. Thank you!
Click to expand...
Click to collapse
It looks like your device is not recognized in Fastboot mode...
Have you turned on USB Debugging while connecting PC and Allow in Device when Prompt some message ..
Go to fastboot mode and write this command... fastboot devices
If it will give you a message like this
List of devices
1235456785164
Then your devices is successfully recognized...:good:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
ERROR: could not get pipe properties
3331E6EBCA6000EC fastboot
Click to expand...
Click to collapse
fastboot oem unlock - gives the following:
ERROR: could not get pipe properties
...
FAILED (remote: Erase Fail)
finished. total time: 4.753s
Click to expand...
Click to collapse
alpheus said:
It is not recognized by adb devices, but:
fastboot devices - gives the following output:
fastboot oem unlock - gives the following:
Click to expand...
Click to collapse
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
Thanks, I tried 3 different cables on 3 different operating systems, with the same problem unlocking the fastboot. When I send fastboot oem unlock the device opens a prompt with Yes or No choice, but after choosing Yes, it stays Locked
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
demkantor said:
Pretty sure you have a bad USB cable, the error means the fastboot binaries are working on PC but can not connect to device, often this is due to a bad USB cable or port
Try a new cable, one you can verify works transferring data
Click to expand...
Click to collapse
demkantor said:
Something indeed is strange...
So fastboot is for bootloader and adb is for within os and in recovery.
Try booting into recovery and see if adb works, also boot normal into your bootloop and see if adb works there too
Click to expand...
Click to collapse
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
alpheus said:
Loading into basic recovery and trying to wipe data/factory reset - doesn't work. adb devices returns the following output:
./adb-linux devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
****empty line here****
Somehow, adb doesn't recognize the device, whereas fastboot devices shows it.
Is there a way to flash new bootmode with the currently locked bootloader?
Thank you!
Click to expand...
Click to collapse
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
UPDATE (resolved)
Here is an update. Hope this would help others with similar issue, as I've read many threads and folks complaining that they weren't able to unlock fastboot and further root their Nexus S, and who can't boot the phone, which stacked with Google Logo (soft loop). This was the case with my device and finally I got it resolved. I've read some guy tried to hit the phone and after that he was able to boot phone normally. It related to some hardware electrical circle issue. Anyways, I tried to hit my phone by placing it under the direct sun in balcony for some time until the phone got hot and then power it on. And ooops, my phone started booting passed by that Google Logo which was the good sign. Once the phone booted up, I went ahead and activated USB debugging and restarted the phone into the Fastboot mode. while the phone was still hot and in Fastboot mode I run "fastboot oem unlock" and hey, fastboot is Unlocked! Again, this was done while the phone was hot, any previous attempts (read above) weren't successful. From that point, I went ahead and rooted my Nexus S by Nexus Root Toolkit, available on wugfresh.com/nrt, without a slightest problem. Now my phone is fully rooted, bootable and working fine. I thank all who replied to my thread and tried to help and hope this info would help someone with the similar issue.
Rushabh22 said:
I am damn Sure What's Your problem is, ADB is not working..
PROCEDURE:-
1) Download My attachement and unzip it and Place it in Folder...
See image 1.png
2) Go to that folder and Press CTRL+SHIFT+ Right click on mouse and Select Open Command Window here..
See image 2.png
3) Now type here Fastboot devices and Now you will get Those list of devices Number..
See image 3.png
If Everything will be done as Procedure and you will get List of devices Number... Now, You type those command for Unlocking bootloader and Root Your Devices...:good:
Hope this Guide will help..
Click to expand...
Click to collapse
Thank you for your help and suggestions.
Q Mobile X 32
bootloader oem unlock problem
plz help
Q-mobile said:
Q Mobile X 32
bootloader oem unlock problem
plz help
Click to expand...
Click to collapse
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Setting.Out said:
Wrong device thread..
Try here..
https://forum.xda-developers.com/showthread.php?t=2363923
Click to expand...
Click to collapse
can you help me in rooting Qmobile x32
Q-mobile said:
can you help me in rooting Qmobile x32
Click to expand...
Click to collapse
That thread didn't help?
Here's what the guide says...
Hi all,
Is there already a way to root the brand new Lenovo Yoga Tab 3 pro?
I want to buy it, but I can't imagine having an unrooted device...
Envoyé de mon LG-H815 en utilisant Tapatalk
Up?
misteurz said:
Up?
Click to expand...
Click to collapse
i have no idea not having access to such a device, but considering the similar hardware with the YT2 model (well better a little but not by that much) it should work with the exact same method uset for YT2. so yes 99% that it's root-able (maybe even unlock-able, someone on your thread asked me, yet he did not sent nothing no files when asked so i don't know much about the internals of YT3)
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
misteurz said:
Thanks for your answer.
So if I try this (T4 I think):
http://forum.xda-developers.com/showpost.php?p=57543871&postcount=1
It won't brick my device? It will work, or not work but no brick?
Click to expand...
Click to collapse
there are other ways of knowing whether that or maybe even other new commands work, i would need from someone to send me a dump of his fastboot partition so i can check inside (my bet is that what works on YT2 willdo on YT3 too... and i am pretty sure it will work up to YT100 knowing how Lenovo works )
I don't have the tablet yet, so I can't have the files you need. Who has the yoga tab pro 3?
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Shug69 said:
I have it but I can't seem to find working adb/fastboot drivers. Stuck on device unknown.
OK drivers sorted but getting an unknown OEM command on both T3 and T4. so no joy yet
Click to expand...
Click to collapse
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
ionioni said:
1. the easy way:
- if anyone has access to the droidboot.img and can send it (from the rom, did not found any on my quick searches, or maybe when you do an OTA, don't install it yet and look inside)
2. a little more complicated one (working on 1050 and could work on your tab) will NOT CHANGE anything on your tab all happens in memory and gets lost at reboot:
- download tmp-root-1050F-lollipop.zip from here and extract
- place your tab in DnX mode: PowerOff, then while pressing boh VolUp&voulDown (and keep them pressed) press Pwr to start (keeping vols pressed), release Pwr when the logo show and in a few sec the screen will say "Fastboot starting..." and hang on that message (you are in DnX mode now)
- run the exe downloaded, follow the instructions if all is well (hopefully) it will open a temporary root shell where you can do stuff otherwise not possible on the "after boot to Android" environment
- open a new Windows command prompt (cmd) and enter some commands:
adb shell "dd if=/dev/block/mmcblk0p5 of=/tmp/fastboot.img"
adb pull /tmp/fastboot.img
send me that file so i can look into it and see what is changed on your tab
this is just some preliminary, if the temp_root works (let's hope) many things besides rooting are possible, but for rooting the easiest way would be to adapt the existing method from YT2 to whatever is changed on your tab
Click to expand...
Click to collapse
Hallo,
Thank you for your work. I have a little bit afraid of this method .
Too bad that there are so few users here . But the Tab is still so new.
Perhaps an even experiencer user dares. Sorry !!!
At Weekend i will take your method and send you the file.
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Shug69 said:
Unfortunately the tmp-root seems not to be working. Dnx mode - no problem and the .exe file starts but sticks on the preparing to push files line. On the tab after a few seconds a service menu appears ( board test, rf calibration etc.) Option 5 on this menu is droidboot but this crashes the .exe file. If someone else wants to confirm it's not my (old and messed up windows 7) machine then it seems pretty riskfree
Just noticed a tiny message on tablet ( must be a screen resolution thing) shortly after executing .exe about certificate verification failing.
Click to expand...
Click to collapse
we tried. it was rejected by the bios right from start and never even got the chance to load (that message means just that).
somehow, someway we must get a fastboot image so we can see what can we use (grab from the tab or from stock rom).
i've seen your stock rom avail yet i don't know if they are legit (they seem). also is a payed one.
one more try:
go in fastboot (droidboot) mode and try and see what these commands will output (to see if at least one is still valid):
fastboot flash /tmp/some_small_file some_small_file (use a real file ofcourse, to see if we can still write to the device)
fastboot oem unzip
fastboot oem fastboot2adb
fastboot oem factory2tmp
(they won't do nothing in this config, yet we'll be able to see if meaybe one is still working, ie it doesnt say 'unknown command')
Flash file gives cannot load,; the others give unknown command.
Shug69 said:
Flash file gives cannot load,; the others give unknown command.
Click to expand...
Click to collapse
try again the fastboot flash (i edited the syntax in the prev post)
however, i think that a droidboot.img will make things a lot more easier
so whoever grabs a stock rom...
So, @Shug69, did you try the edited commands?
Envoyé de mon LG-H815 en utilisant Tapatalk
Been travelling. Can try tomorrow but I agree we need to find a ROM. The site ionioni linked to may be legit but 25 bucks to find out seems a bit steep.
ok. back at pc - sure i'd bricked it there - ran 'fastboot oem unlock' and it unlocked the bootloader. woudnt boot normal though afterwards and it took several reboots after ' fastboot oem lock' to get past the Lenovo logo. Device is wiped of course
My experience has been a little different so far. Just picked up the tablet today.
I toggled Allow OEM unlock and enabled debugging in Developer Options. I installed the Lenovo Suite software (which was really just a driver pack) then ran adb reboot bootloader to reboot. It got me to a Lenovo splash.
fastboot oem unlock didn't work for me. It gave me an error message:
Code:
fastboot oem unlock
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.005s
Running fastboot oem unlock-go worked immediately and the tablet rebooted to the typical Android factory wipe screen. Could be coincidental, but I got an OTA notice after I did the whole first-time Android setup. I denied the update, but copied down the update name: YT3-X50F_S000015_150917_ROW_TO_YT3-X50f_S000016_151002_ROW
Hey everyone, kingroot now works to root the yoga 3 8".
Not on the pro unfortunately.
?
Envoyé de mon LG-H815 en utilisant Tapatalk
Thank you
ElrosMinyatur said:
Hey everyone, kingroot now works to root the yoga 3 8".
Click to expand...
Click to collapse
Great news. I have confirmed that it works using my non-Pro Yoga Tab 3 8". Do I need to keep the Kingroot app installed after I have unroot device? The only issue I have is updating the SU binary in SuperSU. More to come after I debloat my device.
Thank you once again.
Spunky168
"The Original Taepo Dong"
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
ZSparda said:
Hello! I don't know if there might a be a solution for this problem, we've tried many stuff that's been posted here on the forums but ended up in the same results, so no luck. My friend's Moto G5 Plus "bricked" itself while updating to Oreo some time ago, wasn't rooted or anything, bootloader wasn't unlocked either. We can access the recovery menu with "power + vol+", but any option we try to use ends up with the message "Failed to pass validation, backup to fastboot". Some of the solutions I've tried require the bootloader to be unlocked, but I haven't been able to unlock it since my friend never checked the "Allow OEM unlock" option. He took the phone to the official service but they said they couldn't do anything and wanted to sell him a new phone. Any help is appreciated. Thanks in advance!
Click to expand...
Click to collapse
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Wolfcity said:
Would be helpful to know what exactly you've done to rescue that device.
For example, did you try to wipe the complete device and fastboot flash the latest signed Oreo firmware?
Is the device recognised by a PC?
What about using Lenovo Motorola Smart Assistant?
Click to expand...
Click to collapse
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
ZSparda said:
Hey! From what he told me, at first he was able to access the recovery menu, when then little Android with the red mark shows up, then he used the Smart Assistant and after that he gets the validation error message that I mentioned. I suppose the Smart Assistant made things worse? The device was initially recognised by the PC, but now it isn't. We tried to flash the stock firmware and unlock the bootloader but we didn't have any luck either. Since the PC didn't recognized it anymore we tried a few things to make it work but ended up giving up.
Click to expand...
Click to collapse
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Wolfcity said:
So you can't get to the screen with the dead android (fastboot mode) or recovery with the key combination (power and vol down/power and vol up)? You should be able to get there and check the connection by typing
fastboot devices
or
adb devices
Is the battery full enough to start?
Do you see the device in Windows devices manager?
Click to expand...
Click to collapse
I tried to attach a couple of screenshots but I get the "bad request" message here. Anyways, when we do a normal boot we get the validation error message and we are sent directly to fastboot menu, but there we cannot choose any options because all of them lead to the error message again.
It's been a couple of weeks now but the last time we tried doing something, the device wasn't showing up in device administrator nor being recognized by adb.
As regards to the battery, we've left it charge up for some hours, so I guess that's not a problem, although we cannot see the percentage.
[email protected] said:
PC should recognise it at very worst, as qhsusb_bulk. Your PC must be in test mode, and then when you connect look in device manager, under usb devices, and a hard bricked phone will show as qhsusb_bulk. Anything else, you should be able to communicate with ADB/fastboot, as Wolfcity stated. If it does show as qhsusb_bulk, you will need to use vaches' blankflash to recover the unit.
Click to expand...
Click to collapse
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
ZSparda said:
I'll tell him to check if it shows up as qhsusb_bulk and update here. Could you explain a bit more or link to a thread about vache's blankflash? What is it exactly?
Click to expand...
Click to collapse
This thread is long, but alot of good info on hard bricked Moto G5 plus devices.
Code:
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
To get PC in test mode
Code:
Here is how to turn on or off the Test Mode feature in Windows 10.
IMPORTANT: Please remember that turning off the Test Mode feature may force the program/driver which is not digitally signed stop working.
Step 1: Open Command Prompt as administrator. To do so, type CMD in Start menu search to see Command Prompt in the search result. Right-click on Command Prompt entry and then click Run as administrator option. Click Yes button when you see the User Account Control screen.
Step 2: At the Command Prompt window, execute the following commands:
To enable the Test Mode:
Bcdedit.exe -set TESTSIGNING ON
To disable the Test Mode:
Bcdedit.exe -set TESTSIGNING OFF
If the above command didn’t work, this one must work:
Bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
Bcdedit.exe -set TESTSIGNING OFF
You may exit the Command Prompt now.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Thanks! I'll send him all these so he can try. I'll update as soon as possible.
[email protected] said:
This thread is long, but alot of good info on hard bricked Moto G5 plus devices. To get PC in test mode
Click to expand...
Click to collapse
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
ZSparda said:
Update: The PC detects the phone as Android Device > Mot Composite ADB Interface.
But once in adb, adb devices isn't working. It doesn't recognize the device.
Click to expand...
Click to collapse
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about
Code:
fastboot devices
? It should show the device #. ADB doesn't always show devices.
[email protected] said:
It is recognizing the device, " Mot Composite ADB Interface" is correct.How about ? It should show the device #. ADB doesn't always show devices.
Click to expand...
Click to collapse
Yes! Fastboot devices shows the device! So now we have to procede with the flashblank.zip and all that from the other post right? Also sorry for the late reply, I've been pretty busy these past days so I left him with all the work.