Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
I have this exact same problem right now.
Would love to get a solution for this.
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
COLDrum said:
I have this exact same problem right now.
Would love to get a solution for this.
Click to expand...
Click to collapse
Please post here if you find a working solution for this.
demkantor said:
If you need to extract some files and you have a broken screen do not change android versions as chances are it will make it very difficult to extract any info (as in it will be wiped)
Maybe try a tool like android commander or droid explorer to control device with PC, if this won't work see if you can boot to recovery and use adb in there
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Im on hold when it gets to downgrading so far. Im not familiar with Android Commander, but Droid Explorer requires adb to be working. And that is kinda my whole problem. I cant accept my PC as a secure adb-client since the digitizer is broken (touch input wont work). I hope there is a way to override this through recovery or some other way.
Breakdown:
When connecting device to computer (adb), I have to (on my device) accept my computer as secure. This is a problem since digitizer is broken.
Sent from my Nexus 7 using xda app-developers app
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
demkantor said:
Like I said if these programs don't work use a recovery, if you current recovery won't work then flash a new one with fastboot, I'm pretty sure you'll be able to use adb in recovery without having to authorize, or if you plan on an exact device replacement just make a nanadroid and restore with new device
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Indeed this seems to be a fix. Thanks!
Do you know if there is a way to get rid of the authorization through adb. Are there any files who could be manipulated? Would be great if I could use some sort of screencast-app eg. Droid Explorer.
Sent from my Nexus 7 using xda app-developers app
I'm sure being you can use adb shell in recovery that there is a way, can't say off hand but a bit of digging will probably get you there, it couldn't be all that hard I wouldn't think
Sent from my Nexus 4 using xda premium
Streaker said:
Im in bit of a problem here.
With the new security check in 4.2+ I have to accept my computer on my device when using adb. Fair enough. Problem is I just broke my screen/digitizer and thereby cant accept. I am rooted and have custom recovery. I need adb to extract my data and I want to get screencast work as well.
I hear you say "why not just use the same computer as you rooted it on in the first place". Well thats just not possible anymore..
Device Nexus 7 (2012) android 4.2.2 (rooted and CW recovery)
What options do I have to work around this? All I can think of is downgrading to prior android, but Im not sure how well that will work, neither do I know how to push romfiles without adb.
Help/ideas even opinions is greatly appreciated!
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
I do have more than one instance of ADB.exe installed yes, but does that matter to my problem? My Nexus isnt even showing up in fileexplorer in windows. So I cant access my files. Or am I wrong here?
Sent from my Nexus 7 using xda app-developers app
maxrfon said:
Are you sure you have only 1 instance of the adb.exe and it's the latest one?
Try where adb.exe from commandpromt, you may have another adb.exe somewhere in Windows directory.
Click to expand...
Click to collapse
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Just to be sure I renamed the other ADB.exe and kept only one (v1.0.31). Still gets unauthorized. :/
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
....
maxrfon said:
First: Delete all ADB.exe you can find on your computer.
Second: You have to update the ADB, no matter how - download from internet or using the android SDK. But you need to use the latest version!
Optional: replug the cable and run adb devices. This can make the authorization toast to appear.
Then you will get your device authorized.
BR
Max
Click to expand...
Click to collapse
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Streaker said:
Thanks for trying to help me out here, but are you sure you read my complete firstpost? My problem is I cant accept the authorization on my device. I need a way to get around this security and I hope its possible since I am rooted/unlocked. Just to be sure: I've deleted all instances of ADB and reinstalled it as you suggest. Problem still percists.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have had the same problem with my S4.
After updating ADB i did "adb devices" and got my S4 as offline, and i noticed the popup on my phone, accepted and my samsung is now working fine with ADB.
FYI before the above mention operation i have tried everything, even making sure i run the correct adb.exe but there was no popup.
First of all kill the adb server via task manager then when you start the adb command-line type In ADB root this may solve your problem :thumbup:
Hit thanks if I helped
Sent from my Xperia Live with Walkman using xda app-developers app
Somehow I managed to delete the stock OS and CM on my LG G2 (Verizon) and now my device is stuck on the loading LG screen. I am also getting the unauthorized device when checking ADB devices. I've got TWRP running as the bootloader, but just need to be able to push over the CM file to boot and I'll be good to go. Any suggestions on how to force the file over to the phone?
Boot into your twrp recovery and use adb sideload to flash a ROM from there
Sent from my Nexus 4 using XDA Premium 4 mobile app
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
VreebieZ said:
Unplug USB from your device
Type:
adb kill-server
adb start-server
Replug USB to your device
Go to USB dev
Uncheck USB Debugging
re-Check USB Debugging
*New authorization window should popup*
Type: adb devices
Click to expand...
Click to collapse
I'm having the same problem as the OP... This is impossible. *the screen and digitizer are broken*
The question is "How can I bypass the New authorization, since I can't click anything on my phone". I can't check "USB Debugging" - I need the phone screen and digitizer to do that. come on people, read the post.
Has anyone figured this out? I'm having a similiar problem except my screen isn't broken. I forgot to make a backup and my OS got erased and I'm getting the unauthorized notification in ADB. You have to be able to get into the OS to accept the authorization so I'm at a catch 22. I have a Nexus 7 so I can't swap out a different SD card.
Related
I have changed the build.prop of my rooted TF201 to play the gameloft games.
After changing the TF201 got stuck in a bootloop. I tried the hard reset but it is still not starting.
I read that it is possible to push the orginal build.prop to the TF201 via APX-Mode but i dont now how to do it.
My computer recognizes the TF201 as a Asus Transformer Prime APX mode or in MTP when i start it regular. Unfortunatly i can not get any access to the Data of my TF201.
Is Asus able to see the root and that i changed the build.prop if i sent it to RMA?
Would be so happy if anybody could help me.
Thank you.
(And i know it was stupid to change the build.prop but didnt expected to brick it http://media.xda-developers.com/images/icons/icon9.gif)
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
stf996 said:
Hi there.
I had a week of the same problem. I hadn't deleted anything but mine was in the boot loop too. After trying everything I managed to reinstall the OS by:
1. Downloading firmware from Asus site (it must be same or later version as installed already and must be the one for your region - if you don't know your current version, the small text described in step 4 below will tell you and step 4 can be done multiple times)
2. Freshly formatting a micro SD card with FAT
3. Placing the ZIP file (the zip inside the zip that Asus provide) in the root of SD CARD
4. Restarting the tablet by holding power and volume down until small text appears at top of screen at which point press volume up
Your tablet will boot from the SD card and reinstall your OS.
ALL DATA WILL BE LOST but you'll have a working tablet.
Cheers.
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
clmz88 said:
Thank you for answering!
Unfortunatly did not work for me.
The androidfigure showed up with a red triangle on it and after a minute it restarted into the bootloop.
Any other ideas?
Click to expand...
Click to collapse
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Turge said:
Can't you push the original build.prop via ADB Shell when it's almost booted up?
Code:
adb mount -o ro,remount /dev/block/mmcblk0p1 /system
adb push c:\...\build.prop /system/
Click to expand...
Click to collapse
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
clmz88 said:
I tried it and got the message "can not find device" although my systems shows Android MTP Device in the device manager...
Click to expand...
Click to collapse
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
EDIT: Here you go.
http://forum.xda-developers.com/showthread.php?t=1480428&highlight=bricked
Now don't go doing such stupid things again.
Turge said:
Mine shows up, but only when "Camera (PTP)" is selected instead of "Media device (MTP)" in the "Settings >> Storage >> USB computer connection" section.
But of course, that won't help you in this case since you can't change this setting.
I can't find anything about having to switch to PTP for ADB to work so you may want to post a question about it in the Q&A forum.
Click to expand...
Click to collapse
Ok. Thanks though.
I would be happy about some other ideas
Doktaphex said:
A guy had the exact same problem here last week after changing the build.prop for the exact same reason. He was able to recover his problem using the same method that the root scripts use for writing to data. Let me try and find the thread and you can try to contact him.
Click to expand...
Click to collapse
I already got that thread and asked for his solution.
Im unfortunatly not able to sent him a private message because i am a new member.
clmz88 said:
Ok. Thanks though.
I would be happy about some other ideas
Click to expand...
Click to collapse
EDIT: I'll see what I can do for you, give me some time.
Doktaphex said:
EDIT: I'll see what I can do for you, give me some time.
Click to expand...
Click to collapse
Thank you!!!
clmz88 said:
Thank you!!!
Click to expand...
Click to collapse
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Doktaphex said:
I've sent him a PM for you asking for his solution. I've linked him to this thread.
What software version are you on? .11 .13 or something else.
EDIT:
Do you know how to use ADB?
Does ADB see your device?
Click to expand...
Click to collapse
I actually dont know what version is on my Prime. I did the official update two weeks ago. So it is probably V9.4.2.11.
I have a app called "adb made easy" on my pc and this on can not find my device.
Does your device constantly reboot or does it stay at the boot animation?
Doktaphex said:
Does your device constantly reboot or does it stay at the boot animation?
Click to expand...
Click to collapse
It stays constantly in the boot animation.
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
EDIT: unplug and plug back in a couple of times, does windows make it's usual connection noises?
Doktaphex said:
and adb made easy doesn't have your device listed?
What if you "open CMD for ADB commands" and then in that window type "adb devices" without the quotation marks?
Also what does windows device manager show with regards to android devices?
Click to expand...
Click to collapse
adb made easy and cmd dont show any adb devices.
the devices manager shows
mobile devices: Asus Android MTB Device (could not be started)
windows is always making the pluggingsound
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Doktaphex said:
Wierd, ADB should still see the device as it seemed to when the other guy screwed his build.prop
If I reboot, ADB picks up the device during the boot animation and lets me start interacting straight away.
EDIT: Unfortunately, without ADB, I'm not gonna be able to help any further. Hopefully the guy how recovered his from this state will pop in and be able to help you out.
When and where did you get the device from. If you're still in your return window and feel like being dishonest, then you could take it back to the shop and ask for a replacement. However, if it has to go back to ASUS, I'm fairly certain that they would pick this up straight away, I could be wrong though. They may just look at it see it doesn't boot, reflash it and then test it and send it back.
Click to expand...
Click to collapse
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Turge said:
Is yours setup for PTP or MTP?
Sent from my Transformer Prime TF201 using xda premium
Click to expand...
Click to collapse
I think it is setup for MTP but im not sure about it...
I didnt find a way yet to get access to the prime via usb.
Already tried different drivers, adb, apx but nothing is working.
I rooted my lg on my computer, but I have not connected it since. Everytime I try, it says it does not recognize , that one of the USB devices has malfunctioned. I have installed the lg USB driver 3 different times and still can't get it, I have tried all 5 USB ports I have, same thing. Any ideas
Sent from my LG-E970 using xda app-developers app
I tried restoring to before my first lg driver install, reinstalled driver software, still same error
Sent from my LG-E970 using xda app-developers app
Have you uninstalled the drivers?
If not, with the phone plugged in, go to device manager, find the device, uninstall it, unplug and then replug in your phone.
Yes I did, I'm very computer literate. Turns out a cable can't tell you its bad, the original cable seem to be the problem. Probably why sometimes I get slow charge when plugged into the wall. All may be null and void when I attempt n4 conversion lol , wish me luck!
Sent from my LG-E970 using xda app-developers app
Good luck. I recommend having LGNPST prepped to revert to stock, with the DLLs and the BIN/TOT version of the LG ROM. AFAIK, that's the only way to get back, because of how extensive the N4 conversion is. Reverting with a ZIP ROM in CWM is unlikely to work.
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Sent from my LG-E970 using xda app-developers app
ripbabey said:
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Click to expand...
Click to collapse
The Windows 8 guide works (even if you're in Windows 7):
http://forum.xda-developers.com/showthread.php?t=2013067
Step 5 refers to a folder in a zip file that you get a link to in IRC.
When you go into irc an you !info lgnpst click on other versions and get phantomphreak53's
Click to expand...
Click to collapse
That's the #lg-optimus-g channel on Freenode.
Yes, the DLL refers to "LS970," but it works fine with the E970.
To obtain the files listed in the first four steps, I just Googled them and found Dropbox links.
The TOT/BIN file in question would be this one: http://forum.xda-developers.com/showthread.php?t=1984545
It will take a while to download; the server appears to average 100 KB/s.
As you can seee, it's kind of a pain to set up LGNPST's environment correctly. I recommend taking all of those files and backing them up to a secure location, so that you never need to hunt them down and re-download them again.
The guide also doesn't mention that your phone needs to be in Download Mode to interact with LGNPST. This is achieved by turning the phone off, plugging it into your computer with a USB cable, then holding down the power button and both volume buttons at the same time until the Download Mode indicator shows up on your screen. It may take several attempts; the process appears to have a low tolerance for poor button press timing.
LGNPST will interact with your phone even if Windows no longer recognizes it. I think that's why it remains popular as a last-resort recovery method.
ripbabey said:
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Everything you need is on Team Nocturnals website where the conversion thread is minus lgnpst and the nexus 4 drivers.
After you flash the n4 conversion, boot in recovery and then install the nexus 4 universal naked drivers (Google it, should be the first xda link.) Then you can use adb to fast boot -w and flash a recovery. Just read a little more and you'll realize its not hard at all. Just make sure everything is prepared. Good luck if you try it. It was very interesting to me. I've gone back to stock and came back to the conversion after the sdcard fix
Sent from my Nexus 4 using xda premium
Right now the problem I am having is getting windows to recognize my phone in boot loader/ fast boot which will prevent me from being able to fastboot -w , I have a thread on here should be titled fast boot and recovery. Posted it last night. I'm trying to make sure everything is ready, but my phone and my PC are just trying to fight me every which way lol. I'm going to try another computer and see if things run smoother, I have rooted and unlocked a bunch of phones for friends and myself on my laptop. Wondering if I'm just having a lot of driver conflicts lol
Its not about what you know , but who you know.
You might need to flash your recovery, and possibly lock your bootloader again. What I have seen over my several rooted phones is that sometimes when unlocking them, the binary code doesn't match up and will not allow the battery, USB port, and even screen to work with the software. Won't matter if you unistall or reinstall the drivers. Hope this help!
Sent from my HTC One V using xda premium
WizzyCreator said:
You might need to flash your recovery, and possibly lock your bootloader again. What I have seen over my several rooted phones is that sometimes when unlocking them, the binary code doesn't match up and will not allow the battery, USB port, and even screen to work with the software. Won't matter if you unistall or reinstall the drivers. Hope this help!
Sent from my HTC One V using xda premium
Click to expand...
Click to collapse
Which software are you describing? I have not lgnpst 'd anything yet, it does notice my phone both with phone on and connection settings to lg software, and in download mode. The problem I am currently stuck on is getting my PC to notice my phone in boot loader so I can't use any fb commands. I can talk to my phone when its on through adb commands no problem.
I dont want to get in trouble, the original problem was I could not get windows to notice my phone at all. I fixed that by trying a different USB cord, apparently my original is failing. If you would like to help me more so I don't get yelled at, please post in my other thread titled fast boot and recovery in the qa thread. I really want to attempt this, its my bday. So it would be a awesome little bday present to my flashaholic self
Its not about what you know , but who you know.
ripbabey said:
Yah , I think I'm going to give up on trying, between the cable thing, now I can only talk to my phone through adb, fast boot won't seem to work. Plus I can't find a lgnpst guide anywhere for our phone. No idea where to get the DLL I'm supposed to flash with, nor where to get the files to flash back. This is my first lg, I've been a HTC guy, so I know nothing about lgnpst. Thanks though
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
Man how you using adb ? i wiped system by mistake and now i can access download mode recovery and i tried adb but my pc doesent recocgnize my device installed drivers and stuff and tried all the ports but nothing..so i can't use any tools right now to unbrick,,i can't flash because i have nothing on the internal memory also i'm on e975 i need adb to push a rom onto the sd card please help
Hello XDA-Developers,
I've been a reader here for awhile now learning things about the android development for my devices and used many of your all members TUTs, but now i have came across a big issue that has broke my phone and need assistance getting it back online to be used with my carrier again. Below I'll explain my situation of what happen and what I need to be done so I can use the phone again or least get it back to factory stock so I can get a new phone... I will also offer someone $5-10 via PayPal for the assistance if you can help me get my phone back to the condition needed.
To start it off, I purchased a phone off a guy on craigslist, a AT&T HTC One M7 (Model: PN07120), when I purchased the device it was unlocked so I could use it on my carrier that was the reason I purchased it because I'm with T-Mobile. When I purchased the phone i went to setup the device to my needs and requirements and after two days of having the device, I noticed that the phone still had the previous owners information stored and was setup based on him, so because I didnt know the phone was rooted or anything, I googled how to factory reset my phone, so that way I could set it up to my wants, and requirements and below I'll explain the steps i'm at and what it is doing...
1. Searched google for the how-to method to factory reset my phone...
2. Went to 'Settings App', Backup & Restore, Reset Phone, Erase everything, Selected OK.
3. Followed the steps, phone rebooted..
4. Loaded up to the HTC (green logo) screen and stayed there...
5. Waited a few moments, phone never powered 100% back online just stayed at the HTC welcome logo when you first power phone back on.
6. So then I did the Boot Menu steps, (Hold Powerkey + Volume Down) to get into the boot menu,
7. When I got there it loaded to the boot manager window and I clicked FASTBOOT
8. Loaded new menu/logo "twrp" logo, then went to a menu "team win recovery project v2.6.3.3" with the list of options: INSTALL/WIPE/Backup/Restore/Mount/Settings/Advanced/Reboot.
9. I went to reboot to try to least get the phone booted, then when I was in the option to reboot, it gave me the warning of "No OS Installed", Continue without OS?"
10A. If I selected yes, it told me Install SuperSU, for root, otherwise phone wont be rooted.
10A1. I tried doing INSTALL SUPERSU did nothing..
10B. Did without installing SUPERSU and did nothing too, just when I boot comes back to this same menu Team Win Recovery Project.
So it seems I bricked my device as what everyone calls it to what I believe, I am unsure though or unsure how to fix this. I need to get the device either back to factory resetted to like the device comes out the box, so that I can use it, or what to do to get it back rooted successfully and working to be able to use the phone like i could at first.
I tried contacting the buyer but hes ignoring me now that I told him he told me the device wasnt rooted but the device was rooted and i seemed to have a major problem happen trying to restore the phone to factory defaults to set it up to my requirements...
My concerns and want is..
- My Carrier is T-Mobile USA LTE - So, I would have to get the device to stay UNLOCKED so I can still use the device on my carrier: T-Mobile, as it is a AT&T HTC One M7 Unlocked (Was working fine on my T-Mobile Sim prior to me trying to factory reset, besides the phone was named to the original owner and had all his settings and customizations that i didnt like or want.
- I NEED to get the phone back in a working condition. So please I'm really asking for your help I tried searching a couple articles here but couldnt find anything related to my situation.. This is why I am offering a payment for someone to be able to successfully restore my device back to working condition. Please help me!
- NOTE: When plugged up to the computer via USB Cord it did not connect or anything also. I also did not perform a backup because I didnt need any information that was currently on the device because it was the content and settings of the original owner i bought it from so I wanted to clear it all and set it up to my own.
- Overall, my phone is messed up because I tried factory resetting the device not knowing it was rooted, during the process found out it was rooted and now seem to have a bricked phone and need to know how i can fix it, and get android OS back installed, as it tells me there is NO OS installed when I reboot or try booting the device, and it remains at the HTC Bootlogo when powering it on without holding the power + volume down key to access a boot menu to perform a reset, install, etc, Like I mentioned I just want to restore my phone back to working condition even if that means to have to root the device again, etc. All I'm asking for is someone to either help me with each step or to write a step by step what I would need to do to recover and restore my phone.
Phone: HTC one m7 (AT&T)
Computer; Windows
Thank you,
PM or respond here.
Don't worry you device is not bricked...
Google Android Revolution HD 41.0 for HTC one. Download that ROM.
Second you will have to install android SDK to be able to access adb.exe and fastboot.exe...
Now once you installed the SDK move the ROM ARHD to where adb.exe is located.
run command prompt "CMD" from your computer until you are in the folder where you have you adb.exe
Now on your phone get into recovery TWRP and select advance, in advance the is an option called adb sideload click on it and at the bottom slide the button to initiate that mode.
Back to the computer in which you should be in CMD type command "adb devices" and make sure your device shows up. After successfully seen your device there type "adb sideload file-rom.zip and press enter, make sure the file-rom.zip is the exact name of the ROM you are trying to push into the phone.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Don't worry you device is not bricked...
Google Android Revolution HD 41.0 for HTC one. Download that ROM.
Second you will have to install android SDK to be able to access adb.exe and fastboot.exe...
Now once you installed the SDK move the ROM ARHD to where adb.exe is located.
run command prompt "CMD" from your computer until you are in the folder where you have you adb.exe
Now on your phone get into recovery TWRP and select advance, in advance the is an option called adb sideload click on it and at the bottom slide the button to initiate that mode.
Back to the computer in which you should be in CMD type command "adb devices" and make sure your device shows up. After successfully seen your device there type "adb sideload file-rom.zip and press enter, make sure the file-rom.zip is the exact name of the ROM you are trying to push into the phone.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Where can I find this stuff I need to download? I tried doing a search and got a different version, Android Revolution HD 51.0, but could you please link me to the stuff I need to download on my computer, etc?
Okay I've done the steps you've instructed to me and I'm stuck at after launching the sideload feature on my phone; then going back to the computer and running 'adb devices' and under "List of Attached Devices" there isn't anything listed yet, and the phone says "Starting ADB sideload feature..." is the last line, I'm stuck with what to do...
I downloaded android SDK
downloaded the ROM
moved the ROM to the sdk folder where adb.exe and fastboot.exe are
launched adb sideload feature under advanced on mobile device
went back to the computer and ran, 'adb devices', and list of attached devices is none...
so I'm back at being stuck.
djay1127 said:
Hey again,
Okay I downloaded the android SDK, and I'm downloading the correct ROM now to install. Only questions I have for you is the following...
1) You said to move the ROM to where adb.exe is at... What do you mean by this? I don't have that file on my computer...
Where do I move it too once I have the android SDK downloaded and the rom downloaded...
Click to expand...
Click to collapse
Follow this video
http://android.mobilenicheapps.com/tag/android-sdk-installation
Sent from my HTC One using xda app-developers app
TopoX84 said:
Follow this video
[/url]
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I watched the video and got all of that working and checked based on the video and made sure all was installed, now i'm just still stuck at where you instructed me to do 'adb devices' after launching adb sideload under advanced on mobile, i did that, and i get
List of devices attached...
<nothing>
Then goes back to where I can type another command...
The phone itself screen is on the adb sideload feature, and in the textbox thing, shows the following
Updating partition details...
Starting ADB sideload feature...
then has a Cancel button underneath and then a loading bar underneath that... am I doing something wrong? or missing something?
Do I need to have the USB cord plugged into phone/computer also to do this? or dont have it plugged up...
djay1127 said:
Do I need to have the USB cord plugged into phone/computer also to do this? or dont have it plugged up...
Click to expand...
Click to collapse
In order to do a sideload you have to have the cord plugged to both the phone and the computer...
Sent from my HTC One using xda app-developers app
TopoX84 said:
In order to do a sideload you have to have the cord plugged to both the phone and the computer...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I tried that and still get no devices attached.
djay1127 said:
I tried that and still get no devices attached.
Click to expand...
Click to collapse
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
HTC Manager = no
drivers = i dont know.
Note: I never had the phone plugged up to my computer before when it was working. I had just purchased the phone off of craigslist and the guy didnt inform me it was rooted or anything just that it was unlocked and worked on tmobile and when i got it it had all his info on it so i factory resetted it and it messed everything up as you can see.
So, I dont believe i have anything drivers installed and i know when i plug it up, there are 4 things windows says installing/etc, and only the first one says completed the other 3 fail.
I am using Windows 7.
You help me get my phone back in working condition I will personally paypal you $20.
djay1127 said:
HTC Manager = no
drivers = i dont know.
Note: I never had the phone plugged up to my computer before when it was working. I had just purchased the phone off of craigslist and the guy didnt inform me it was rooted or anything just that it was unlocked and worked on tmobile and when i got it it had all his info on it so i factory resetted it and it messed everything up as you can see.
So, I dont believe i have anything drivers installed and i know when i plug it up, there are 4 things windows says installing/etc, and only the first one says completed the other 3 fail.
I am using Windows 7.
You help me get my phone back in working condition I will personally paypal you $20.
Click to expand...
Click to collapse
Go to this website and download the HTC sync manager
http://www.htc.com/www/software/htc-sync-manager/
Once installed go to control panel > programs and uninstall a program... Look for the HTC sync manager and uninstall it, but leave the htc drivers alone.
Connect the HTC one to the computer and wait for the drivers to install automatically... After they are successfully installed try to run the CMD adb command adb devices
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Okay so I've done all that and after doing what you said, plugging the phone up to the computer everything installs besides the HTC MTP driver when the phone is plugged in. I still tried doing adb devices from cmd prompt to check and that didnt work still, no devices listed.
I get this error under the driver:
This device cannot start. (Code 10)
djay1127 said:
I get this error under the driver:
This device cannot start. (Code 10)
Click to expand...
Click to collapse
Based on what I've been reading that code error might be cause by a corrupted driver installed.
http://support.microsoft.com/kb/943104
Sent from my HTC One using xda app-developers app
TopoX84 said:
Based on what I've been reading that code error might be cause by a corrupted driver installed.
http://support.microsoft.com/kb/943104
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I answered your PM and awaiting for you to pop back up online... I also sent you a PM with some details and also wanted to let you know TV is installed.
djay1127 said:
I answered your PM and awaiting for you to pop back up online... I also sent you a PM with some details and also wanted to let you know TV is installed.
Click to expand...
Click to collapse
was a tough little driver... well the solution as we saw was that instead of trying to make recovery detect the drivers.... what needed to be done first was let fastboot detect drivers "android 1.0" and once that was done... the previous error was gone.
TopoX;
You know this guy right here is clutch in my book.... He actually walked me through step by step, customizing how i needed it, fixing everything, and getting it back up and even though we had to do alot of modifications on my computer-end, him with TeamViewer literally fixed my phone, upgraded my laptop, and got my phone running better then normal and actually showed me how to do everything and taught me things I didn't know how to do with these Android Phones.
I am now very happy and thankful of XDA-Developers for allowing me to get this assistance and for having a great community with members like TopoX who literally saved my ass and restored my phone back to working condition and fixed my laptop all together, even though I was a brand new member with hardly any posts and not really much background, anyone else wouldn't of wasted their time... but he helped and even was up until 3AM ish doing it with me to make sure I got it back to exactly how I wanted...
We had to get the HTC MTP Driver installed correctly which kept failing/getting code error 10 (Unable to start) which if you google the issue it seems ALOT of people get this issue, and we resolved it by fastbooting and letting it install Android 1.0 itself, then manually updating my pc with windows updates and getting rid of the junk to stop corrupting and failing the drivers needed, then getting everything needed to flash my phone and re-root the device getting everything back in a working condition, unlocked, got that done and now phone is working better then before...
I'm currently running Team Win Recovery Project, ARHDOne-61.0 Google Play Edition, Rooted, SuperUser and Unlocked.
I personally wanna thank TopoX for everything he did and dedicating his time to helping resolve the issue for me.
TopoX84 said:
was a tough little driver... well the solution as we saw was that instead of trying to make recovery detect the drivers.... what needed to be done first was let fastboot detect drivers "android 1.0" and once that was done... the previous error was gone.
Click to expand...
Click to collapse
Cool story bro. Seriously..... Cool story.
I love XDA.
If anyone is trying too get in contact with "djay1127", please contact me on this user, my original first account djay1127 I can no longer access the account as I set it up with my Google account, gplus login, and I can no longer access that email, it's closed out. So I created a new account with my main email account and username.
I plan to contact a admin after doing some searching to discuss getting my old account removed, and the posts and crap merged into this account instead...
Regards.
Please forgive my ignorance I am very new to this. I just want to flash the new firmware to the nexus 9 manually. I have downloaded minimal adb and fastboot but it doesn't find my device. I have enabled developer mode and allow usb oem ect but nothing when I type the commands it says waiting for device and nothing happens, obviously I am missing something obvious, but if you could please help me out I would be grateful.
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
Not sure what the first question means??, I think I ran the adb commands at the right directory??
anobium said:
Not sure what the first question means??, I think I ran the adb commands at the right directory??
Click to expand...
Click to collapse
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
AjunNg said:
Means when you connected the device to the PC with USB debugging, there should have been a pop up asking you if you'll let the device blah blah.
You need to press OK.
Click to expand...
Click to collapse
No never had a popup, asking me toconfirm???.
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
AjunNg said:
Did you let your device RSA footprint be recognised?
Did you run adb commands at the right directory?
Click to expand...
Click to collapse
AjunNg said:
Unplug it and replug it until it does.
Uncheck USB debugging and recheck it until it does.
Click to expand...
Click to collapse
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Use Wugfresh's Nexus toolkit, and use the full driver installation.
anobium said:
Think ive found my problem in device manager on my computer the android device has a yellow exclamation mark saying no a driver present, were do I get the android driver for windows??
Click to expand...
Click to collapse
Right click on it. Go to where it lets you pick from a list on your computer. Choose android adb interface driver, or something along those lines
Sent from my Nexus 9 using XDA Free mobile app
AjunNg said:
Use Wugfresh's Nexus toolkit, and use the full driver installation.
Click to expand...
Click to collapse
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
No root needed to update.
anobium said:
This program is the bollocks, for a newbie like me, went through the steps and it recognised my device, only 1 question do I need to root to update stock firmware as I cant see option to update without rooting.
By bollocks I mean brilliant.
Click to expand...
Click to collapse
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Migamix said:
oh you silly English person.
the toolkit will get you back to stock. wug is working on a revision that will properly format the data partition to decrypt the tablet. the tool is best for force flashing and renewing your device as if you just unboxed the device with no root. the option to install a recovery and root the device is used after you are happy with the first boot and freshness of your devices. other tools included are just simplified press of the button commands that save you the time of opening a cmd shell.
key things to remember about the n9, absolutely make sure you enable the OEM unlock in developer options. and to my understanding NEVER uncheck it. there is a thread here about that "feature"
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Ok i get to flashing the image and it goes to quick and comes up with errors saying I have different firmware image on my device?, I thought that was the idea im going from lrx21r to lrx22c, do I have to put I already have the 22c in the option list??.
jd1639 said:
And what's wrong with fastboot? No need for a tool kit
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
there is nothing wrong with ADB, or fastboot, if you use it exclusively, good for you.
as the OP title sais, it is not expected for a new user, and even some experienced users, to have such a firm grasp of the ways of the mighty command line, and the fact that the toolkit gathers all of the files in one convenient place, is not without its bonus. i dont know, nor do i really care who started the whole elitist "toolboxes are for lamers", or whatever. toolboxes are nothing more than their name suggests , tool-boxes, to help when we need it. they are nothing more than an interface to commands, much like you running a GUI on top of your OS, or are also running command line only for your primary computer. xda, is designed and expected to be help for all who want to know, not a pond of elitists that would rather brag they have overclocked their device, water cooled it, but can still make a grilled cheese sandwich on their CPU. i have email accounts older than many of the forum members here, so not too much impresses me in that 1337 area. im here to help if i can, and learn if i need to., so since im here alot, im always learning.
Hey guys I'm trying to unlock my bootloader but adb is having none of it! When I type in adb devices it says list of devices but theres nothing there. And I can't boot into bootloader using adb. This is really starting to grate on my nerves as nothing is working. Am I just doing it wrong? I don't know. Should I have plugged my phone into the laptop before installing minimal adb and fast boot? Should I be switching to file transfer mode and/or photo transfer to install them drivers first? I've tried my previous questions and photo transfer is the only thing that comes up with adb interface in device manager BUT it will not install the driver it just keeps saying searching for drivers. any and all help will be greatly appreciated.
Sent from my LG-H850 using XDA-Developers mobile app
undeadadd said:
Hey guys I'm trying to unlock my bootloader but adb is having none of it! When I type in adb devices it says list of devices but theres nothing there. And I can't boot into bootloader using adb. This is really starting to grate on my nerves as nothing is working. Am I just doing it wrong? I don't know. Should I have plugged my phone into the laptop before installing minimal adb and fast boot? Should I be switching to file transfer mode and/or photo transfer to install them drivers first? I've tried my previous questions and photo transfer is the only thing that comes up with adb interface in device manager BUT it will not install the driver it just keeps saying searching for drivers. any and all help will be greatly appreciated.
Click to expand...
Click to collapse
Switch to mtp, as you already suggested by yourself.
Also Try if you can on another pc, possibly with 7
Sent from my LG G5 using XDA Labs
Killua96 said:
Switch to mtp, as you already suggested by yourself.
Also Try if you can on another pc, possibly with 7
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
Which one is mtp?
Sent from my LG-H850 using XDA-Developers mobile app
undeadadd said:
Which one is mtp?
Click to expand...
Click to collapse
File transfer mode
Sent from my LG G5 using XDA Labs
Killua96 said:
File transfer mode
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
Cheers, I have tried that and still nothing sadly
Sent from my LG-H850 using XDA-Developers mobile app
undeadadd said:
Cheers, I have tried that and still nothing sadly
Click to expand...
Click to collapse
Try to uninstall all lg driver, then connect the G5 in mtp mode and wait for driver installation.
If still doesn't work, as i already said, Try with another pc.
Sent from my LG G5 using XDA Labs
Killua96 said:
Try to uninstall all lg driver, then connect the G5 in mtp mode and wait for driver installation.
If still doesn't work, as i already said, Try with another pc.
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
Cheers I'll give it a go
Sent from my LG-H850 using XDA-Developers mobile app
Killua96 said:
Try to uninstall all lg driver, then connect the G5 in mtp mode and wait for driver installation.
If still doesn't work, as i already said, Try with another pc.
Sent from my LG G5 using XDA Labs
Click to expand...
Click to collapse
so i got adb working and booted into fastboot tried to get device id and now my phone wont turn off and terminal is stuck on waiting for device. ive always hated this part of unlocking/rooting :/
Hold power + vol up or down I don't remember, and it will reboot.
Try fastboot reboot in the terminal (not sur if this will work)
Hunikel said:
Hold power + vol up or down I don't remember, and it will reboot.
Try fastboot reboot in the terminal (not sur if this will work)
Click to expand...
Click to collapse
yeah i can get the phone to reboot now but this bloody thing will not get my device id lol
adb reboot bootloader should work fine.
Try to install official LG drivers on your pc.
Hunikel said:
adb reboot bootloader should work fine.
Try to install official LG drivers on your pc.
Click to expand...
Click to collapse
Where do you get those?
Sent from my LG-H850 using XDA-Developers mobile app
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 Direct link, otherwise http://www.lg.com/us/lgeai/drivers
Hunikel said:
http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 Direct link, otherwise http://www.lg.com/us/lgeai/drivers
Click to expand...
Click to collapse
thanks ill give it a go i just hope it works because once this bloody bits over the rest should be easy as i always have adb issues lol
It happens to everyone don't worry ^^
For me I'm still waiting for a bootloader unlock for my H860...
Enjoy your root features !
Hunikel said:
It happens to everyone don't worry ^^
For me I'm still waiting for a bootloader unlock for my H860...
Enjoy your root features !
Click to expand...
Click to collapse
The rate I'm going my bootloader will never be unlocked lmao. Issue after issue here. I installed official drivers and now adb/fast boot don't find my device again lol
Sent from my LG-H850 using XDA-Developers mobile app
Just to be sur, you activated developper options and checked USB debugging ? Did u have a message on your phone with a key to accept ?
Hunikel said:
Just to be sur, you activated developper options and checked USB debugging ? Did u have a message on your phone with a key to accept ?
Click to expand...
Click to collapse
yeah i eneabled usb debugging and oem unlock options. im currently booted into fastboot but can not do anything after that. when i enter fastboot, device manager starts looking for a driver again.
sorry device manager has an explenation mark but doesnt look for an drivers
I had exactly the same problem, but I solved it. Check my post #306 and previous here:
http://forum.xda-developers.com/showthread.php?t=3363040
My story starts with #289. Good luck.
antykat said:
I had exactly the same problem, but I solved it. Check my post #306 and previous here:
http://forum.xda-developers.com/showthread.php?t=3363040
My story starts with #289. Good luck.
Click to expand...
Click to collapse
i dont have an old backup with old or any drivers thats the problem lol