Related
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
Been modding android devices since the G1 but never got stuck like this before. Already spent hours of searching and googling but couldn't find any definite answer.
My B70 got bricked when using a program to boot into recovery.
Is there any way out or should I just throw it away?
I have a feeling that the device is looking for a recovery on internal SD card and fails. I can see the unit as ADB unit but when trying to connect it says device is offline both in normal boot or in recovery boot.
Been trying putting stock roms on external SD but it never runs it.
Has anyone solved this problem?
Check your SBK version and try to NVFlash
Try to boot recovery/apx wipe permissions /data if possible
post questions in Q&A not Dev
After a lot of examination it has been decided that you have posted this in the wrong section and we shall place it where it should be. Please make sure you post correctly next time.
Like mentioned already, some B70 are SBKv1 meaning nvflashable.
What app did you use to get into recovery causing the "brick"
Can you still get into cwm recovery, ect.
you still have hope if ADB can see it, try to update your driver.
If it work use ADB to push the file you need.
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
The app I used to get into recovery was just a random boot into recovery app. It worked many times before. I don't think taht app caused this, maybe the recovery files where deleted?
df9517 said:
Sorry for wrong thread.
I probably have SBK2 (how to check) because usb just disconnects as soon as I try to run any nvflash stuff.
I also believe that ADB could be the saviour but it says offline. So this could be due to driver issue? Interesting, I shall try on a 32 bit computer.
If I suceed to connect through ADB, can I then flash CWM recovery?
Click to expand...
Click to collapse
You can use SBKdetect to check your SBK version (linux)
Did you have CWM before? Are you rooted?
What is your tablet doing right now? Stuck at the start up screen?
My tablet was previously running rooted ICS WW .11 with CWM.
Now its just stuck at the first boot image. I can go into same image where it tries to run recovery image by holding vol down. I guess it is standard brick.
Not getting anywhere with ADB, device is offline
hmm.. can you cold boot? just hold vol-down and wait?
df9517 said:
Not getting anywhere with ADB, device is offline
Click to expand...
Click to collapse
Search on here for the universal naked driver. Try that or sometime if you can try a different usb port.
Can you get into CWM Manually?
Hold VOL DOWN and POWER for about 10-12 seconds until some small text appears.
Quickly (within 5 seconds) release both buttons and hit VOL UP to enter RCK (Recovery).
If you can get into CWM this way you should be able to clear some caches and see if it will boot. If need be, you may be able to flash a new ROM if need be.
I only got the naked ADB drivers to work. The real ASUS ones does not work. Only tries 64 bit though.
Of course I tried to go into recovery manually.
Actually I now remember that just before this happened I updated CWM through the clockwork app. Probably updated to a version that does not work.
Since you have ADB working, download a CWM flashable .zip from your favorite recovery thread and extract the recoveryblob.
adb push it to /temp/dd or something similar, then run adb shell, su, and (you will need root/busybox on here) dd if=/your/blob/here of=/dev/block/mmcblk0p4.
after running that, run reboot, you should see a blue line and be able to get into a good CWM recovery. never use rom manager.
Thing O doom.
It always says my device is offline using ADB. I have only got naked driver to work.
But now I saw the NVflash for B70+ devices in your post. I will try that tonight.
I have not given up.
Yes, that is probably your only hope if you can't get ADB working, and it just came out! Lucky day
Yes, thank you all!! Finally NVflash for B70+ devices saved my day. Reflashed original ROM.
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Sapphire18 said:
Hello,
I am trying to fix my girlfriends HTC One S, she accidentally dropped it into the bathtub full of water, she picked it up fast, put it to rice so it sucks out the water and applied heat, the phone worked, but the touchscreen is totally unresponsive, is there any way how I could determine if the touchscreen is damaged, or the motherboard? I dont have anyone else around me who would give up their warranty and let me open theirs phone so I could test it. I already disassembled the phone, tried unplugging the connectors, checking if there is any visible water damage, but i got nothing, so either the panel or the motherboard must be damaged, I need some way to determine which one is it.
I will also add a conversation with Awesome, he was trying to help me at first and there are some more information.
The wet phone? I did reply. Is the phone rooted? If its not boot into the boot loader holding the volume down and power and click factory reset see if you get the touchscreen working again. If it doesn't work then you short circuit something but if it works and goes away then its your screen.
If your phone is rooted its gonna be hard to do factory reset.
Sent from my HTC One S using Tapatalk 2
Then I probably did not figure out the answer was for me
Well, the problem with that is, that there are some valuable photos inside and a factory reset would definitely remove them,
I was looking for a solution for backing them up, I got to a software, that can control the phone from PC without the need of being
installed in the phone, there was a slight problem since it required USB debugging to be turned on and it wasn't. So I was browsing
the internet to find out if it is possible to turn on USB debugging from PC, or perhaps somehow, until here on XDA in some thread
someone said it is impossible, so I gave up backing up the data and went straight for the repair, that is why I need somehow to find out
if either motherboard is damaged or digitizer, I have the phone totally disassembled. I am guessing that some touch controller on board is
damaged, since I cant see any visible damage to digitizer, but I am not sure and I do not want to buy wrong part.
Also the phone is not rooted and is using stock ROM.
Thank you
Yes without USB Debuggin its impossible to extract those files, and without u doing a factory reset I really can't think of doing or trying anything else to figure out what may be the problem. Since its water damage you really won't see if its short circuited. I'm more than sure you got a short circuit rather than needing a digitizer. Other than that feel free to open a new thread in the general section of the one s and asking there maybe other users will have other options for you.
Thank you for help.
Click to expand...
Click to collapse
Em so is the bootloader unlocked? you could try to see if adb is working in fastboot or if it is unlocked I think TWRP lets you use adb.
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Sapphire18 said:
Well, its all in stock, so I guess the bootloader is locked, and without USB debugging turned on ADB doesn't recognize the phone.
Click to expand...
Click to collapse
Ok but have you tried adb in fastboot?
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Goatshocker said:
adb in fastboot should work, regardless of the setting in the rom.
What android version is it running? If its running 4.1 you could use an OTG cable and hook up a mouse to control the device.
Click to expand...
Click to collapse
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Darknites said:
Omg so forgot you can use a mouse so going to do that now for no reason lol.
Click to expand...
Click to collapse
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Goatshocker said:
Theres also an app that can share your kb/mouse to your android device, the device will see the kb/mouse as hardware plugged in.
ShareKM its called, works damn good on both my S and TF.
Click to expand...
Click to collapse
Cool think I have a play later.
Okay, here is what I got, the OTG cable is not working, that means the phone doesn't have Android 4.1.
The ShareKM application requires installation into the phone, meaning it is out of question too.
I am experimenting with this ADB in fastboot, but I am not really sure how that fastboot command works when I run ADB.exe trough command prompt and list devices, it show me only my other phone in USB debugging, when I run the fastboot.exe and type adb devices it says "waiting for the device", I do not really know how to work with this with a little guide, it shows me some commands there, i tried the one with rebooting into bootloader, but it still says only "waiting for device".
Could you give me a little guide perhaps link to guide what exactly I am supposed to do to run ADB in fastboot?
I am pretty technical type, dont need noobish explanation.
Thank you
Okay, I managed to get into fastboot, I always thought it is something with the fastboot.exe in SDK Platform-tools, well, anyway, I am inside, it says Fastboot USB, but adb still isnt showing the device in the list.
Also there is a big pink ***LOCKED***, that means that bootloader is locked I guess.
Any other ideas how I could backup the files? or any other suggestions?
Thank you
Moving slowly forward, I was being stupid and I was using the ADB command instead fastboot command, when I am in fastboot mode now, well, trough fastboot command now the PC recognizes the phone, altho what is the next step now?
Thanks again
Yeah, the ShareKM app was never really ment for you, it was more of a suggestion to dark sorry if it confused you.
I ran some quick tests, and yeah Im afraid adb is, in fact, not working in bootloader.
What happens if you boot into recovery? Maybe it works there?
What kind of things do you need to save? Is it just like pictures and stuff from the sdcard?
In that case, you could unlock the bootloader (this will wipe the device data, like applications etc) and install TWRP. Im 100% sure ADB works in TWRP without you needing to use the screen.
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Sapphire18 said:
Just tried booting into recovery, the only thing I am receiving is big red exclamation mark, not sure what it means, I did some digging and it usually appears when someone is trying to do OTA update from custom ROM, strangely, this is original stock ROM.
One S doesn't posses SD card, it has 16Gb internal storage, but is probably divided into some system partition and data partition, if that is what you meant. Yes, it is only some photos and videos.
You said TWRP, as I did some background search, it says touch recovery, that kinda sounds it uses touch, and that is the one thing I can't use.
Or am I mistaken?
Click to expand...
Click to collapse
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Darknites said:
Right you say adb is see your phone now, download Quick ADB Pusher load it and see if you find the sd card if it does just copy over everything you want, it will need to be in pull mode for this.
Click to expand...
Click to collapse
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Sapphire18 said:
It did not work, but I am going to describe everything I did: I started the phone, got into Bootloader, switched into fastboot and connected USB cable, then I started the Quick ADB pusher, switched into pull mode, opened ADB Explorer, but there I dont see anything, only "error: device not found".
Did I do anything wrong, or is it that the Quick ADB pusher doesn't work in fastboot?
Click to expand...
Click to collapse
Em did you try scan under select device?
Darknites said:
Em did you try scan under select device?
Click to expand...
Click to collapse
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Sapphire18 said:
It shows me the phone there, under name SH27NW401121, but when I open the ADB explorer, there is only a folder named
"error: device not found" to me it looks like that Quick ADB pusher doesnt work in fastboot mode.
Click to expand...
Click to collapse
Then I'm out of ideas because unlocking the Bootloader will wipe the sd.
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Goatshocker said:
Indeed, Quick ADB is just a GUI front-end for adb commands. If adb doesnt work in a command line, Quick ADB wont work either.
Theres nothing I can do about that, its not like I can magically force your device into accepting adb commands.
Unlocking the bootloader wont wipe the SD... At least, it didnt for me (just the /Android/ folder).
Things like pictures taken and custom ringtones were still present after the unlocking.
So, ADB doesnt work when youre in recovery either? (the big red exclamation mark)
Click to expand...
Click to collapse
And I am not throwing any blame either, I am just open to every solution
How would unlocking the bootloader help me? so I could put that TWRP inside and do some magic with it?
For the recovery part, I am not really sure how it is supposed to work, but every picture I googled shows some text
along with the exclamation mark, but the only thing I am getting is exclamation mark, and after a while the phone reboots.
I am guessing the recovery either wont load up, or something is wrong, should I try running ADB while that exclamation mark is shown?
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
SevnSins said:
I need to return a broken rooted phone, and have a question before I do so...
the phone has been rooted, and has the HellFire ROM installed. The phone currently won't boot up completely. It gets to the boot animation, and just loops forever. I first thought this was a battery issue, as I'm unable to even do a factory reset or get into download mode. After ordering a new battery, I found this wasn't the issue, and now need to send it back to tmobile.
now my question...
if I send it back, will they be able to tell if it's rooted, since it won't boot up, or is there a way I can make it impossible for them to find out? I've heard I can cook it in the microwave for a few seconds, but I'm not trying to blow anything up. LOL
any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Lgrootnoob said:
Are you sure that you can't key combo into recovery?
If you have the time, make a jig to force your phone into download mode. Then you can use odin to flash stock.
If you are wanting to send it in for warranty because you can't accomplish the tasks above.
Then you have adb access on then run the tool in my signature and use the unroot command.
(It will take a while for adb to start up at the bootscreen but it does startup.)
Just make sure that you have drivers properly installed.
They shouldn't be able to tell the difference.
Click to expand...
Click to collapse
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
SevnSins said:
No, I've tried booting into recovery & download mode both several times, and they both are unsuccessful. When trying recovery, it displays the blue recovery starting text, but never goes into recovery. It just skips to the boot animation, and loops. When trying download mode, as soon as it asks to press volume up or down, the device powers off. it doesn't even give me the time to click anything.
Not sure what you mean by "make a jig to force download mode", but I'll give your second suggestion a try.
thanks
Click to expand...
Click to collapse
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
SevnSins said:
i downloaded your script, placed on a flash drive, and I'm getting the attached errors.
Click to expand...
Click to collapse
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Lgrootnoob said:
Which version of windows?
I have tested this script on four different machines,
It seems that your path variable is most likely messed up.(Unless you manage to find issues with my code which is appreciated too )
If you like then you can post the output of the path command while running adbClient and I can help you fix that problem.
Otherwise use the instadb command to fix this if you don't want to fix your potential path variable problem.
(instadb will install adb to the system)
Back to the topic at hand, Jig
There is a link to making a usb jig. (It is a VERY helpful link, as long as you take the time to read everything [The Xda way ] )
That can get you into download mode.
You can either go find a usb jig online and buy it, or you can make your own.
I also found this at the bottom of the page:
darkamikaze - "I got this from sparkfun. While it's not necessarily buying a complete jig, it saves the hassle of cutting a perfectly working usb cord
https://www.sparkfun.com/products/10031 "
I'm interested in the path thing though, so please do post the output of the path command being used inside the tool.
Click to expand...
Click to collapse
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
SevnSins said:
I'm using Win7
I'm not as familiar with adb as I should be, as I haven't had to use it much through my experiences, so I don't really know my way around it that well.
instadb is asking for username & password info, and I don't know what goes in there.
I don't have a soldering iron, so I'll likely need to buy one it looks like.
I've attached the path output you requested.
thanks for your help
Click to expand...
Click to collapse
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Lgrootnoob said:
Thanks for the path info.
If you want to build it then you can buy a soldering iron, but if you manage to buy an already built jig it might be cheaper and require less time. ey
instadb requires the username of an admin account on your machine and the password for that account. (It elevates user permissions then copies binaries to the system32 folder)
You can do this manually by copying the dlls for adb from the bin folder and the adb and fastboot executables from the bin folder into system32.
After that you shouldn't receive anymore errors.
Thanks for the info, apparently nothing is wrong with the path variable. (Whats weird is the "F:\-" in the photo you attached it should normally be drive letter:\path to adb , F:\bin in a variable)
Try my tool on a local drive. (Its finnicky sometimes )
Click to expand...
Click to collapse
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
SevnSins said:
ok, looks like the script is working now, but I'm getting a "device unauthorized" error. The device is connected, and has the boot animation looping.
i also tried to reboot into recovery from your script, and get the same "device unauthorized" error.
screenshot attached.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Lgrootnoob said:
http://forum.xda-developers.com/showthread.php?t=2401452
Its impossible to use adb at this point. (Never say never: Has adb worked before?)
You have a samsung phone right?
Your phone would have to be working to accept a key on screen for adb access.
The only thing now is the usb jig.
Click to expand...
Click to collapse
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
SevnSins said:
I do have a samsung phone (Galaxy S3), but I don't recall if I ever used adb with this phone. I know I've used it a few times in the past, but that could have been on my G1 & G2.
think I'm just going to put it in the microwave like I used to do my playstations. LOL! I need to get a working phone, and waiting for a jig to ship is going to take a few days I'm sure.
thanks again for all your help
Click to expand...
Click to collapse
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Lgrootnoob said:
Well seems like a repair would leave you with the jig as the only option.
If your house burns down then I got your back there too.
You could just come chill with me.
Just make sure to post pics of your microwaved phone. (Or a video :laugh
Click to expand...
Click to collapse
well... where wasn't a fire, but I got a pretty cool spark. although; it still didn't "kill it" all the way. it's still try to boot up. I just decided to send it in, if they charge me for it, I'll just pay it. my job is taking over my phone bill anyways, so I shouldn't need to worry about it.
thank again for your help :good:
Just got me new-to-me TF700 this afternoon. Trying to root it.
Unlocking was easy (all manufacturers should do it this way).
Now trying to root.
I've downloaded (and copied to /sdcard0) CWM touch for KK (recovery-kk-touch-6046.img)
Press [pwr] +[vol-down] gets me to what appears to be a fastboot screen. I have 3 options "RCK", "Android", and "Wipe data".
None of these lets me run recovery on the CWM image.
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Is there another way to do this - of am I doing the wrong thing anyway?
Not a major deal if I need to order a cable and wait.
Thanks!
PS: tablet is on stock 4.2.1. There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
bobkoure said:
I'd just go into ADB and run from there, but the tablet came without the stock USB cable (the one that plugs in the keyboard port).
Click to expand...
Click to collapse
Without that cable, how do you connect it to the charger?
bobkoure said:
There are a lot of instructions that say, basically, select 'USB' from the fastboot screen. That's not appearing.
Click to expand...
Click to collapse
There are also instructions updated for the current bootloader that tell you that fastboot is already active in the bootloader menu.
bobkoure said:
Also. What the heck is the port next to the headphone jack that looks mike a micro USB, but isn't?
Click to expand...
Click to collapse
Micro HDMI.
You could try if the recently released towelroot works for you until you get your cable.
It came with an aftermarket charger; charger and cable are a single piece. I'm not sure the separate chargers are available at all now.
I saw those instructions - and it looked like I was in fastboot. What I mostly wanted to do was install the CWM image. I think there's a way to do that as recovery, as well, but the img has to get packaged in a zip file with instructions and then named whatever recovery is looking for. Not something I'm going to be able to whack together.
Yeah, realized it was micro HDMI just as soon as I started looking at "tf700 cable". Duh! Removed it from my OP, didn't realize someone had already looked at it and was looking to save someone (you?) some typing. Didn't work.
Time to get a cable.
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
bobkoure said:
Found one of the OEM chargers. $55 + shipping. Not planning to buy.
Click to expand...
Click to collapse
If Towelroot works (it probably will since it does work on the TF701) and you get root, you can use the dd command in terminal to flash the custom recovery. But better do some reading on that! One little typo and you could have yourself a brick.
You cannot flash a custom recovery using the stock recovery however - or did I misunderstand?
You can get by without a USB cable if you can get it rooted, but what if something goes wrong? What if you cannot enter recovery and only fastboot is available?
I would not flash custom software without a working ADB and fastboot connection! And for those you need the USB cable. Get it - you'll regret it if you don't.
berndblb said:
! And for those you need the USB cable. Get it - you'll regret it if you don't.
Click to expand...
Click to collapse
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
bobkoure said:
Oh, I got one. Just was itchin' to get a new ROM. Hoping KK's a bit speedier (it had ought to be) - and it's desperately slow now.
Towelroot, indeed, worked fine. Mixed feelings on that one. It working means basically any app that gets installed can get root. But I'm happy I got root to play with in the couple of days it took Newegg to get a cable to me
Click to expand...
Click to collapse
Good choice getting the cable.
Install SuperSU from the Play Store. That will allow you to control which apps get root.
berndblb said:
Good choice getting the cable.
Install SuperSU from the Play Store.
Click to expand...
Click to collapse
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
bobkoure said:
Did that immediately. Paid for pro ages ago
Now trying to get fastboot via USB.
power off (or reset)
power & [vol dn]
stock JB so it goes right into fastboot (3 selectable icons, no "USB" icon)
connect USB
on win pc cmd line go to adb/fastboot directory
"fastboot devices" gets me... nothing.
Not sure how to get CWM installed without fastboot (?)
Trying to figure out if I maybe have bad win drivers. adb works (e.g. "adb shell" works fine) - not when in fastboot mode, of course.
Any ideas? Pointers to the right drivers (win 64)?
Thanks!
Click to expand...
Click to collapse
Windows is infamous for driver problems.....
Connect the tab in fastboot and open device manager. Near the top you should have an entry for Android device, bootloader mode or something similar, and probably a yellow ! next to it.
Right click it and choose "update driver", let Windows search for it.
If you're lucky it'll install the driver by itself.
If not: What Windows version are you running?
berndblb said:
If not: What Windows version are you running?
Click to expand...
Click to collapse
Win 7 Pro / 64.
If you don't mind, I'm going to re-ask this in the general forum - if it's like other forums, when the question changes tack, often people who might know the exact answer never read it because the title was about the original question.
I put it here
BTW, Got CROMBi-KK on there without fastboot (so without a USB cable ) as follows
towelroot - got root
installed supersu, loaded binaries, uninstalled towelroot
goo.im - open bootloader - installed TWRP
installed CROMBi-KK by copying zip to sdcard0, then install from TWRP.
Even without booting / using a fast external SD card, it's perceptibly faster than the stock JB ROM. I did kind'a like the way the stock JB screen was laid out to make it easy to use while attached to a keyboard (controls at L & R bottom corners where you can easily poke 'em with a thumb.) Ah, well.
Ah yes - forgot about Goo. For quite a while it didn't support flashing TWRP anymore, but it's back.
There's also TWRP Manager (which I haven't tried yet) and Flashify which I really like.
It does make flashing a recovery easier, but.....
Call me old-fashioned, but all of those require Android to run. What if you're stuck in a bootloop and need to flash a recovery, clear partitions in fastboot etc? To get drivers working when the tablet is already compromised can be a challenge - to say the least.
I wouldn't be surprised if we see more and more users here who went your route, never got ADB and fastboot going and find themselves stuck when Android does not boot....
That said, I'm glad you can experience KK goodness now and I'll head over to your new thread - maybe I have another idea