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.
Since I can't post in the dev forum, I need someone to help. I run driver.exe, then run thunderbolttool.bat
I get "Waiting for Device Connection"
Can someone tell me what's wrong?
http://forum.xda-developers.com/showthread.php?t=1703455
k9cop said:
Since I can't post in the dev forum, I need someone to help. I run driver.exe, then run thunderbolttool.bat
I get "Waiting for Device Connection"
Can someone tell me what's wrong?
http://forum.xda-developers.com/showthread.php?t=1703455
Click to expand...
Click to collapse
Is USB debugging enabled? Maybe try disabling it and re-enabling it
If so, maybe try a different USB cable and/or port
another problem with thunderbolt tool
I'm working on a buddies Thunderbolt, and ran into trouble
Ok I downloaded tool,
extracted it,
ran driver,
ran bat,
then all seemed good untill it hung at waiting for fastboot the second time where moar is mispelled. phone is on the fastboot page
when you rerun it it shows revolutionary, and s off, but if you try to flash cwm it gets to waiting on fastboot and hangs up.
installed superuser from market
try to install busybox and get an error su not found in either of two locations.
installed rom manager from market, but nothing works because cw recovery apparently not installed.
anytime you boot into recovery get a ted triangle with exclamation point.
any good ideas??
refresh my memory of adb process, its been long time since I used it
will factory reset work or will it brick the phone because of the recovery issue??
I realize this is prolly a simple issue to put a missing file into the correct location manually, or with adb, but we have gone above my unassisted pay grade.
any help is appreciated.
Thanks,
Dan
ddivine01 said:
I'm working on a buddies Thunderbolt, and ran into trouble
Ok I downloaded tool,
extracted it,
ran driver,
ran bat,
then all seemed good untill it hung at waiting for fastboot the second time where moar is mispelled. phone is on the fastboot page
when you rerun it it shows revolutionary, and s off, but if you try to flash cwm it gets to waiting on fastboot and hangs up.
installed superuser from market
try to install busybox and get an error su not found in either of two locations.
installed rom manager from market, but nothing works because cw recovery apparently not installed.
anytime you boot into recovery get a ted triangle with exclamation point.
any good ideas??
refresh my memory of adb process, its been long time since I used it
will factory reset work or will it brick the phone because of the recovery issue??
I realize this is prolly a simple issue to put a missing file into the correct location manually, or with adb, but we have gone above my unassisted pay grade.
any help is appreciated.
Thanks,
Dan
Click to expand...
Click to collapse
Moar is spelled like that on purpose haha
But just reboot the phone and run "S-OFF but no root?" in the extras menu.
Can't get ThunderboltTool to work
k9cop said:
Since I can't post in the dev forum, I need someone to help. I run driver.exe, then run thunderbolttool.bat
I get "Waiting for Device Connection"
Can someone tell me what's wrong?
http://forum.xda-developers.com/showthread.php?t=1703455
Click to expand...
Click to collapse
Did you ever get help with this? My phone is doing the same thing. Starts ADB and then displays the "Waiting for device connection"
message.
Anybody have an idea what I'm doing wrong?
Phone has usb debugging on and Stay Awake is on.
When it connects, my PC tells me it sees the usb device, etc. but something is still amiss....
TIA
Did you install the fastboot drivers? Also try running adb devices to make sure it recognizes its connected. I didn't get the luxury of the all in one tool when I rooted so I ended up have to root by inputting all the lines in manually to make the revolutionary tool work. It was good practice with adb though.
Sent from my ADR6400L using Tapatalk 2
My buddy has a Thunderbolt that froze and so he tried flashing another rom but came across a huge issue. He tried wiping data, cache, dalvik-cache, and system (I think this is where he messed up) and when he tried flashing the new rom, it kept aborting installation. After that his recovery kept showing a log error where it couldn't mount recovery logs and also it wouldn't mount system or cache. The recovery seemed damaged at that point, so he went into HBOOT and tried flashing some stock rom through it, I guess it didn't go well because it gave an error and said something about the installed version being lower, not really sure. Now it won't even boot into recovery. Oh and here's the worst part, S-ON.. he doesn't know how to mess around with Androids, he asked if I could fix it for him. Any help would be appreciated, I know the phone was a gift for his fiance and I feel bad, I wanna help before they send it back to HTC.
Sent from my LG-E739 using Tapatalk 2
I have been trying to port a crespo 2.3.5 Rom to the galaxy player 5, I have used the Cosmos .01 Rom as a base and the Crepso being the port. I dont plan on posting this ROM so dont yell at me for stealing or anything. Anyways, I followed a guide here on xda that is supposed to be universal for all devices and that didnt work. So now I used one that was made specifically for the galaxy players. After following all instructions, I get a bootloop. I havent ever done a logcat before and I would be happy to look if someone would let me know how it works. I was just wondering what the main or most likely causes for a bootloop is. That way I could fix it.
A logcat will tell you why it's looping by displaying error messages
Sent from my Galaxy Nexus using xda app-developers app
I knew that part. Is there any way to get to the logcat other than by using the sdk because I dont really have room to install any more software on here.
Sparx639 said:
I knew that part. Is there any way to get to the logcat other than by using the sdk because I dont really have room to install any more software on here.
Click to expand...
Click to collapse
If you don't want to install the sdk, you can always try the automated tool located at my siggy to get the logs(its just ~900kb) and the logs is just around 0.1 - 3mb usually depending on how long have you logged it(the longer you log, the bigger the size)
Thanks, I'm going to have to wait until tomorrow though cause I want some sleep. Typically I can find my own answers on Google but this could be anything and I didn't know how to get a log cat until just recently
Sparx639
I was able to get the tool to work but after flashing the nexus ROM, it fails to boot so how am I supposed to enable USB debugging and retrieve the log cat?
Logcat
To get a log cat, just plug your device into your computer while it's bootlooping, (make sure the drivers are installed, just install Samsung Kies to get drivers), open CMD and CD to you adb directory, and type "adb logcat". You will see an output, it will probably keep repeating the same thing over and over again.
K, I thought the device had to be fully bolted before you can obtain a logcat
Sparx639
After all that time, I have the device booted and everything works except for when recording video and I can't find anything on how to solve it. Any of you guys know what's wrong?
Sparx639 said:
After all that time, I have the device booted and everything works except for when recording video and I can't find anything on how to solve it. Any of you guys know what's wrong?
Click to expand...
Click to collapse
I believe you need to modify media_profiles.xml in/system/etc. The camcorder profile seems to be missing or incorrectly defined. I've just had a quick glance at the Logcat do I might have missed some other stuff
Sent from my Nexus 7 using XDA Premium HD app
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.
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
says S-On . how do i gewt it to say s-off?
LordXombie said:
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
Click to expand...
Click to collapse
Sounds like you need to update to the latest version of ADB/FASTBOOT the "device offline" is usually due to an incomatible older version of ADB. Get the latest version on your PC then make sure that ADB is working before trying fastboot.
LordXombie said:
says S-On . how do i gewt it to say s-off?
Click to expand...
Click to collapse
We don't have an S-off solution for this phone yet but it is not required for root, although you will need to flash jmz's insecure kernel for changes to "/system" to stick after reboot even when rooted,
MiniBlu
i cant seem to get adb to update.
LordXombie said:
i cant seem to get adb to update.
Click to expand...
Click to collapse
Install the latest on your PC from here http://forum.xda-developers.com/showthread.php?t=2317790
MiniBlu
ok so i did that and it is still saying device offline. Now im trying a program i found on here. desire_610_root_v3.exe it was able to reboot the device into bootloader then it brought it into fastboot menu then it started to send the file then it just snags there. the file just keeps saying its sending. i dont know whats going on.
ok it still not getting teh recovery.img on the phone. it just keeps sending it with out doing anything..
ok so this htc is giving me way mopre problems then the htc one vx. i really need help. and now im kind of lost what to do. Currently all i have done is unlocked the device.
ADB says my device is there. Threw cmd i can't get it to fastboot using adb reboot fastboot. all it does it reboot teh device, it wont go to bootloader. I do have bootloader unlocked. when i go and make my device go to bootloader manually i try to do the fastboot flash recovery recovery.img it starts to send the file then fails. unknown error. what am i doing wrong?
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
LordXombie said:
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
Click to expand...
Click to collapse
That's info that more people should have. The right usb cord can be difference between failure & success. I remember I went through 6 different usb cables jailbreaking my atv2.
For this phone, however, I just used the one that came with it. But I found the automated process to be sticky (not a tech term) it seemed to freeze a lot during the process.
I wound up plugging and replugging the usb when it froze.
It rooted my phone, installed twrp but needed to flash jmz kernel manually. The root tool works though. And to be honest, until I read this I didn't even think that a different cable might fix those issues in the automated process.
The other night for fun I rooted an old kindle hd and I needed to unplug and replug to get that to work. I was using the same cable that came with HTC desire.
***Anyone ever use a fastboot cable? Apparently u need one to install a 2nd boot loader on kindle hd and I'm wondering if that type of cable would resolve issues like this? That's a question not a go ahead to try it. I know very little about that and don't know if it could possibly cause more serious issues. They're cheap on eBay and I'm getting one for the kfhd.