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.
Related
I have read many times over now jcase method and have tried it twice now without success- clearly I am doing something wrong. I have working adb on my pc and all the prerequisite files in the correct directory. I seem to be going wrong at the "adb restore backup.ab" point- it says allow it to restore but in my terminal that process is very quick and the phone does nothing. Am I not waiting long enough?...and appears as if nothing else happens so I go to first terminal and stop it as directions say...but after that the next important 5 code steps say failed or file not found-is that what is supposed to happen?...I finish the remaining steps and then head to htc un unlock but it comes back FAILED Anyone with success have any tips?? I'm stumped...but not bricked...yet!
are you connected to the internet during that time ?
Allowing it to restore means to acknowledge it on the phone itself. Touch the appropriate button on the phone.
Sent from my HTC6435LVW using xda premium
Unlock your phone and click the allow button.
Sent from my GT-P7510 using xda app-developers app
And after touching the "allow" button,, be prepared to wait several minutes. That command is restoring a 300 mob for. It takes awhile.
Sent from my Nexus 7 using Tapatalk 2
more Q's
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
After using the adb restore command, you should turn your phone screen on, and there should be a message waiting that is asking you to confirm that you want to restore.
If you aren't seeing that message after turning your phone screen on, then it sounds like your adb might be too old, our you got a bad download of backup.ab
Sent from my HTC6435LVW using Tapatalk 2
rootntootn said:
Appreciate the help guys! So I should see a message on my phone that requires me to allow? That I did not see or do...sounds hopefull. I have been thinking my adb version was not supporting restore as when I did the restore step all I see is like a help screen, with no direction to allow, or continue or yes/no.....and yes I was connected to internet...should I not be? Won't be able to try this again till tonight but really appreciate the help!
Click to expand...
Click to collapse
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
munchy_cool said:
I made this mistake last night
is the backup.ab file in the same folder as the adb command is?
I forgot to move the backup file and that is when you get the help screen..
Click to expand...
Click to collapse
Will check all this stuff out, all sounds like it's pointing me in the right direction and I am a bit complsive so I will get there sooner or later, any other thoughts will be greatly appreciated and investigated...I think my files are where they are supposed to be BUT I will check and re-check
try it and let us know dude ..do not proceed until you are sure backup is done
Ok...some success, did it in win 8 but I think it was my version of adb that was the problem..not version of windows or files-however I had a zillion files and shortcuts on 7 and I was getting confused so I switched.
I did now get the backup to run, unlocked and allowed on phone...let it finish and all seemed great but last step before reboot...the "adb shell dd if=/sdcard/CIDBLOCK.img of=/dev/block/mmcblk0p5" code returned something like permission denied? Anyway I did reboot and did try for the hell of it, to unlock at HTC...but of course It FAILED. I did not factory reset this time so I am thinking maybe that's the problem and will try again later. Any other thoughts on this demise?
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
munchy_cool said:
Maybe windows 8 is the problem
droid DNA \m/ √[π]¶~™
Click to expand...
Click to collapse
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Done Deal
rootntootn said:
Could be except that it did work up to that (almost) last step...I did read to factory reboot before trying again but I did not...mostly because I was lazy...but also because the image files were already in my phone storage anyway and that,s what the first few steps do...I started from backup.ab code part so I will do the whole deal over...later-burned at the moment.
Click to expand...
Click to collapse
Well...It all finally went well!! Can't thank members enough for all the help...I will pay it forward!!
Hi all, it's my first post here
My Galaxy S II (stock ROM/recovery) has fallen into a reboot loop while I was texting and I'm positive I didn't install new apps recently, so I can't really tell it's an app bug. Last thing I did before texting was disabling Swype.
All I know is that TouchWiz now crashes after boot displaying its usual dialog window.
In addition to that, I've just broken the display, so I can't see anything going on screen...
How can I recover pictures from the internal storage? How can I stop the reboot loop long enough to back up everything with Kies?
I've tried booting in safe mode but the phone keeps on rebooting and I have no visual feedback of successful activation of safe mode. Prior to breaking the screen I could access the stock recovery, so I guess I can still do it, if needed.
TIA,
Andrea
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Explorer23 said:
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Click to expand...
Click to collapse
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
don't know
I don't think that it's possible to recover the data on your device's internal storage now. Rest if anything works do post your experience here with respective procedure or snapshots.
For more attractive deals "Just Dial":- +1 516 515 9871
lo_Spocchioso said:
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
Click to expand...
Click to collapse
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number). Then type in "adb pull <location on phone> <location on computer (optionally)>. If you want more info about commands, just type "adb" and you'll get everything listed. That should be it ... if it works in first place :fingers-crossed:
EDIT: Stock recovery should do fine.
Explorer23 said:
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number).
Click to expand...
Click to collapse
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
lo_Spocchioso said:
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
Click to expand...
Click to collapse
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based. So you can't do much if your screen is broken. I suggested ADB because it was the only option that would work for sure and you don't need screen for it ...
But ... maybe there still is a way ... You could try reinstalling ROM via ODIN and syncing with Kies. Download stock ROM for your country and carrier from www.sammobile.com/firmwares, get your phone into download mode and insatall via Odin. This should work. You're not doing any factory resets, wipes or anything - just "dirty flashing" the ROM over existing one, so data and (most) apps remain untouched. Then you can try connecting with Kies. From there I don't know exactly how stuff works (don't have a Samsung device), but hope it can launch without touching anything on the phone.
I suggest removing the SIM card before trying, so it doesn't get stuck on PIN unlock screen.
This is really your last chance ...
Your next option is changing the screen
Good luck
Explorer23 said:
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based.
Click to expand...
Click to collapse
You're right but, if I'm not mistaken, CWM "touch" file manager can also be used with the physical buttons. I've never tried that, can anybody please confirm?
You could try reinstalling ROM via ODIN and syncing with Kies.
Click to expand...
Click to collapse
That's actually an excellent idea! Now, I only need to be sure that, after re-flashing, the device will be immeditely accessible by Kies straight after boot without further intervention...
Your next option is changing the screen
Click to expand...
Click to collapse
True, but I'd rather grow brain cells than shell out money
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.
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Only thing I can suggest, because it's happened to me, is to make sure you have the correct, most current device drivers loaded on your PC.
Sent from my HTC6525LVW using Tapatalk
they are correct up to date and most current.
HellRayzer said:
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Click to expand...
Click to collapse
Are you unlocked, s-off, and rooted? Do you have developer options activated on your phone? Please explain what you´ve done up till now.
What happens when you type adb reboot. Does it start and not find it or come back with command not recognized?
Sent from my HTC6525LVW using xda app-developers app
i was having issues myself. then I found this thread and things worked again. http://forum.xda-developers.com/showthread.php?t=2588979
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
HellRayzer said:
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
Click to expand...
Click to collapse
my rumrunner folder was still in my downloads folder no where near my adb files and everything worked ok for me. also my Max shows up as a media device also but adb/fastboot still working fine. did you try to reinstall your adb with the link I provided in the above post, its the only thing that helped me when I was having pretty much the same problem as you.
you may also need to unlocked dev tools in your settings... have you done that yet
Where and how do you unlock developer tools...haven't found that under anything in the settings?
HellRayzer said:
Where and how do you unlock developer tools...haven't found that under anything in the settings?
Click to expand...
Click to collapse
Enter Settings, then scroll down to about... pick "Software Information" -- then "More" --- Then press the "Build" 8 times fast. You´ll then have access to the developer tools.
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
HellRayzer said:
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
Click to expand...
Click to collapse
When you type in adb devices, can you see your seriel number?
RayHeath said:
When you type in adb devices, can you see your seriel number?
Click to expand...
Click to collapse
no. it says list of devices, then it's blank.
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Ok, I´m not sure what you time zone is, but I can help you tomorrow. It´s 10pm here right now, and I´m gonna hit the hay soon. When you´re online tomorrow, pm me. I´ll log in, and we´ll start.
Hey relax bud, do me a favor and PM and I will help you out with everything and getting your phone to be recognized by dab and fast boot and make sure you properly s-off unlock and root if that's what you are trying to accomplish! Hit me up, I have nothing going on tonight so I can jump right in to it with you right away
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Have Win XP or server 2003?!?
This: http://forum.xda-developers.com/showthread.php?p=49045175
Don't know if you guys ever got this issue solved or not. I'm having the same issue S-on, cannot get adb devices command to recognize my t6spr for the life of me. on Hboot 2.46, it will detect the USB device malfunction if I put the device in fastboot mode, but thats about it. Device manager shows Unknown USB (Device Descriptor Request Failed). Tried the KB update for devices that fail enumeration on Windows 8.1 for x64 but the update package said my system is not affected so that never installed. Tried the alternative miniadb pakage previously mentioned but didnt seem to have an affect installing fastboot, adb, and drivers, across the system universally. Just not having any luck apparently. I guess I could just sell the phone Tampered and Unlocked haha with no fingerprint scanner functionality, flash ViperRom or some other stock look alike ROM. Was just really hoping to go back completely stock. At one point it time I was trying different PCs to see if it was just a system issue for me. Occasionally it seemed like if I let it sit in Fastboot AC it would eventually get detected and flip over to Fastboot USB long enough for me to push a couple commands to the phone. I have the right RUU but it dosent do me any good if the computer cant see the phone haha. Now no computer seems to recognize it. It all seemed to happen after I tried to S-Off the device with Firewater's method. Idk if I bricked something because it never worked or changed a CID or some other ID to where the USB isnt recognizable, but all I can get this phone to do is take an electric current from the USB, lol thats about it. I thought I had it fixed enough to where I knew what to do if i absolutely needed to get fastboot to recognize the phone but now, nothing.
Just a curiousity question here....a bad usb cable can produce this also...read through posts didnt see anyone trying a new cable...
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Edit:
No luck yet, but I remember a way I did before.It's not quite the same situation but...
I left the kindle on for a long time, and pressed the power button beyond the point from where it showed out of battery screen. It had like no batterypower at ALL. Yhen i plugged back up to PC and...
I'm trying it out now, if anyone is in the same position as me do the same!
Remember,charge only about 1-2%,if it doesn't work!
Thank you guys a LOT for support! I am in process of getting adb and stuff to work on linux...
let's see how it goes...
ferrouskid said:
Hey guys
I got root, but then I changed the build prop to the one given in this thread: http://forum.xda-developers.com/showthread.php?t=2782159
However it didn't boot properly,i.e. only the grey logo showed up, then black screen. No bootloop.
Then I thought factory reset would fix it?
no. now the pc doesn't recognise it. Please help! Same grey logo stuff but no PC recognition.
Click to expand...
Click to collapse
Does adb work ?
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No, unfortunately!
Patrick4 said:
Does adb work ?
Click to expand...
Click to collapse
No,
well
ferrouskid said:
No,
Click to expand...
Click to collapse
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
jimyv said:
That sucks..I didnt try to swap my whole prop build though.. I just modified my mine..I did it with rommanager lite...I do remember a permission problem if u did swap files or used file manager instead of propbuild editer...has any one got brave enough to try the fastboot option one row under the root option in chinese app?
Click to expand...
Click to collapse
Man any ideas?
Thanks
Hashcode and I have talked about it. There IS a working fastboot, but you can't get to it with a fastboot cable, and it's very buggy and not too useful. So it sounds like you are SOL. Sorry. :/
Sent from my Amazon Tate using Tapatalk
?
ferrouskid said:
Man any ideas?
Thanks
Click to expand...
Click to collapse
Fastboot system files?
jimyv said:
Fastboot system files?
Click to expand...
Click to collapse
Wait I know android cowboy had the same problem some time ago. I'll ask him.
ferrouskid said:
Wait I know android cowboy had the same problem some time ago. I'll ask him.
Click to expand...
Click to collapse
If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.
http://forum.xda-developers.com/showthread.php?t=2588608 QUOTE=ferrouskid;53393803]If anyone is in the same situation as me,I'm trying stuff out. First things first,I remember I bricked the kindle a while back. I made sure it was out of battery and then charged it a LITTLE and tried. doing that now.[/QUOTE]
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
HI, you did the factory reset, too?
ARUSTORI said:
HI, you did the factory reset, too?
Click to expand...
Click to collapse
I didn't, though you should try my solution (I'd got a black screen after the grey logo).
I'm sorry but I won't try the factory reset to see if it works
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Ause said:
I have the same problem currently, I'll use ubuntu and see if my kindle can get recognized, the cable I'm using also has a light on it so atleast we know its not dead lol.
Click to expand...
Click to collapse
I'll be over the moon if this works, adb is installed, now waiting for flat kindle to charge...
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Please expand on that. Thank you so much.
Ptiwee said:
Hi,
I was in the same situation. Luckily, the Kindle was semi-recognized with Linux (adb devices shows ??????? with no permissions), I just had to add the udev rules to allow the device listed in lsusb and then I was able to chmod build.prop to get everything back to work.
Hope it helps
Click to expand...
Click to collapse
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
ferrouskid said:
Can you please give the commands that you used?
That would be very helpful...
Thanks a lot for the help though
Click to expand...
Click to collapse
Connect your device to your computer.
By typing "adb devices", you should get this output :
Code:
List of devices attached
???????????? no permissions
Then type "lsusb" and note the ID of the Google Device (Should be 18d1:0001, but I'm not sure you will get the same).
Edit the file "/etc/udev/rules.d/51-android.rules" and add the following lines (If the file doesn't exists create it). Replace 18d1 and 0001 with the values you get in lsusb :
Code:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0666"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="0001",SYMLINK+="android_fastboot"
Run "sudo chmod a+r /etc/udev/rules.d/51-android.rules".
Restart your computer and you should be access your device using "adb shell".
Follow this post to restore your device : http://forum.xda-developers.com/showpost.php?p=53388919&postcount=23
Crap. I dont have access to a linux OS..ill have to call amazon i think.
Sent from my LG-D800 using XDA Premium 4 mobile app