Related
Ok so i just found out today about the WM6 upgrade for the xv6700 so i decided to try it.
I have a Verizon XV6700 with bootloader v1.04
i used the rom from http://forum.ppcgeeks.com/showthread.php?t=7671
i downloaded the one that says Verizon not the Verizon with bootloader 1.02
I run a pc with windows vista
here is what i did step by step
I put the ppc into bootloader mode and then connected it to the pc via usb
then i opened the exe file from my desktop and followed the directions and then clicked install
it then popped up a little window saying checking the information on your device....please wait.... and below it it said dont disconnect your device until the update is complete...
i read that the update takes about 7 mins i allowed it to sit at this for 20 mins and it still did nothing...so i disconnected the usb and then tried to restart the phone and everytime i turn it on it goes straight back to the bootloader screen i cant get out of it...is there anyway for me to get my phone to work? did i brick it? If anyone can help me it would be greatly appreciated
geez, looks like i am not the only one messing up here. I regret this fancy roms by now... but search on PPCgeeks.com some article called "stuck on BL screen" or stuck on bootloader, there''s a little exe you run to get out of it. good luck
i got mine stuck too, but no on the BL.
I am running Windows 7 x64 I have no idea if following this guide on another operating system will work, this is just a step by step of EXACTLY how I did this, Not to say this is the only way. I have tested other methods and I have put in different variables and I have successfully gotten it to work several times in a row doing it this way while following jp4756's guide. I am sure this is not the only way to accomplish root, however this worked for me perfectly. PLEASE don't skimp out on any step. There is no shortcut here just follow the steps and jp4756's guide to the TEE!!!
Step 1.
Uninstall pdanet/htc sync/ any other thing you installed to get all this to work before
Unplug phone from computer usb cables and have phone powered on and in settings menu
Step 2.
download USBDeview(install it) easy to google it
download HTC SYNC(do NOT install it yet) for mytouch slide easy to google it
Step 3.
While in settings menu go to Application
go to Development
and check the box USB debugging
Step 4.
In settings go to Connect to PC
touch Default connection type and choose Sync
At this point you have the phone not plugged in, you have the setting on the phone changed, you have dowloaded usbdeview and installed it, and have htc sync dowloaded
Step 5.
Start USBDeview(some may have to right click the exe and run as administrator) and delete all android drivers and mytouch drivers, anything relating to android
Install HTC SYNC and let it completely install
Step 6.
Plug phone into computer and let the computer auto install drivers etc...
Step 7.
turn the phone off. Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button ) After it does its little thing your computer will beep and start auto installing drivers and stuff
Step 8.
If everything has gone according to plan in Device Manager it will show Android 1.0 or w/e with a exclamation point. Right click on that and choose Update Driver Software
2 options pop up choose Browse my Computer
then choose Let me Pick from list...
a list will appear giving lots of choices
choose Android Phone should be the first choice that says android....
then 3 options will appear, choose the 3rd one that has Composite in it and choose okay.
Step 9.
Now select Recovery from the bootloader menu
after it is done doing its thing completely 2 things will happen
1) In device manager you will now have something under disk drives
2) USBDeview a new driver will pop up at the end of the list, something like this:
Port_#0004.Hub_#0004 T-Mobile myTouch 3G Slide USB Device Mass Storage Yes No No No E: HT05RPS05696 6/16/2010 4:00:58 PM 6/16/2010 4:07:35 PM 0bb4 0ff9 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device
Step 10.
This new driver to appear shows Yes under the Connection column. This needs to be disabled. Right click on it and choose Disable Selected Device
after about 10 seconds it should no longer say Yes under connection column, if this does not happen then you are not running it under Admin.
Okay so now you are literally almost freaking there.
Step 11.
Now basically all you have to do is follow jp4756's guide starting with step 5. Im going to assume you already understand steps 1-4 in his guide. And you already have the package listed in his guide as well. You have already put those files where they belong
Step 12.
Okay so we are basically following his guide now. first things first
5. run the update.zip it will fail(MUST DO)
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery) <--- Basically while the phone is rebooting you are just hitting up arrow enter up arrow enter up arrow enter up arrow enter in CMD. You will know when you can stop when the CMD freezes for a sex, computer makes beeping noises and the phone reboots basically. It is headed for recovery and we must switch our command now
8.type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine) <---- Basically after you know its headed for recovery you change command to adb devices and you repeat previous procedure, up arrow enter up arrow enter up arrow enter etc.... I did not use loop, i did this all manually.
This may take a few tries, if it does not show offline then go back to step 6 rinse and repeat. You go back and forth just a few times and you will have it. Literally within about 3 tries you should accomplish the annoying goal of having offline stay there.
My job is done, follow guide and continue on your quest for root
There is no guarantee this will work for everyone. I am not claiming that this is 100% Im just giving an explanation as to how i got it and what might have been causing everyones trouble. Results may vary
Thank you to all the devs who made this possible and jp4756 for his wonderful guide
Wow that is just way to much stuff there...
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
Also It just might be your computer so I would try and use a different one if you can.
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
Sorry that we all can't be as cool as you jnight666, but some of us are having real problems with no apparent explanation. I am an IT professional with access to every kind of computer used in the modern world, and trust me, I've tried all the ones that apply. Rubbing it in our faces that it was just so easy for you is just rude.
THE DRIVER MAKES NO DIFFERENCE FOLKS. IF YOU CHANGES DRIVERS AND THEN IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON MANY DIFFERENT DRIVERS.
THE CONNECT TO PC SETTING ON THE PHONE DOES NOT MAKE A DIFFERENCE IN FASTBOOT/RECOVRY FOLKS. IF YOU CHANGED THIS SETTING AND IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON VARIOUS DIFFERENT SETTINGS.
That being said, this didn't solve mine. I still cannot root.
And Yes, my cap locks was on purpose.
Okay, please dont come in here and start telling me how my method is wrong. I already stated there are other ways to accomplish it. I had already stated that this isnt 100%. I am merely offering an exact procedure that i duplicated SEVERAL times, with it working for me every time. If this isnt how you accomplished it then pls, theres no reason for you to be in this thread posting negative comments.
With that said fermunky, did you follow the procedure to the tee? - btw im not assuming anything so please dont take it personal. Im just trying to help ppl : )
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Completely understandable, and definitely no disrespect to you or anyone here
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
And if anyone want to say anything about this I'll go load up my Pentium III machine and see if it works on that...
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
3 different computers 3 different op systems installed uninstalled drivers different programs etc...some phones are hard to root its a ambiguous situation
Yeah sorry I wasn't trying to be rude.
I was just trying to be helpful, sorry if it came out that way...
I also have the loop not working issue but i usually only happens once or twice..
I feel your pain I had trouble with the push Update.zip part of this thing and I was trying it for hours...
I was just trying to tell you what worked for me...
If you tried different computer and still no luck then im guessing its the Phone that is the issue or the USB Cable...
gofizzle said:
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
Click to expand...
Click to collapse
You definitely don't want to do that, as one of them is one that you need to be connected once you finally get to see offline stay. Are you rebooting using the method described in jp4756's guide? meaning your rebooting using the recovery option reboot, then in command doing the adb reboot recovery, then once you no the phone is gonna boot into recovery you switch to spamming adb devices? When you say your in a loop it sounds to me maybe your not doing the adb devices after the phone listened to your adb reboot recovery command
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
before plugging your phone into your computer a single time, can you confirm that you started up USBDeview and uninstalled every single driver related to android, or mytouch or htc etc... Also before ever plugging your phone in a single time did you install htc completely?
Code3VW said:
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click to expand...
Click to collapse
Right Click Android Phone - Properties - Driver - Update Driver - Browse My Computer - Let me pick from a list of device drivers (click this, don't give it the path in the upper box) - Have Disk - Browse to yours C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 - click androidusb.inf and select Open - OK - Unclick Show compatible hardware - Select "T-Mobile myTouch 3G Slide" - Next - All Done.
after getting some sleep and starting fresh, i tried this method again this morning. on the fourth or fifth try i got my slide to stick in offline mode. so then i unplugged it and plugged it back in to get into recovery. lost it, and now im on my 50th or so try to get it back to offline mode.
i need a stiff drink lol
it seems partially a driver issue and also an adb issue i thinks. it connects 'when it feels like it'
i'll report back if i make any progress.
btw im doing this on XP Pro SP3 fully updated
edit: I also noticed when adb does catch the slide, 2 instances of adb are running, then one closes and loses the phone. maybe this will help solve some of the problems
You've misunderstood that post. Only one instance of ADB will show when the loop is not running. Once you start the loop, another instance of ADB will show up and disappear many times. This is normal. As long as only one instance is showing before loop, you are fine.
fermunky said:
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Click to expand...
Click to collapse
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
mtjnkee said:
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
maybe your downloads were corrupted. that's really strange...
man, that really sucks! I am truely sorry...
after spending 20 hours or so on rooting, I really feel your pain.
After I reboot into recovery mode and then use adb to check for my device I never get it to show up. Just so I am clear when you say 'spamming your device' you mean after reboot and rapidly entering the reboot recovery command, then looking for device with adb devices command. I never get it to show.
Thanks for the reply!
No devices in adb?
So I had this same problem with my MT3G. Type in "adb devices" kills the last device and it lists connected devices and NONE were listed. Not sure exactly what I did, but did eventually get it working. (I was trying to use the emulator)
Now though I'm having the same problem with my wife's MTS. Any ideas?
Hi everyone. I have a Droid 2 that I flashed Liberty on. As of yesterday, I was just fine with it but then it began to do weirdo things like repeating key presses uncontrollably and sending calls to voicemail rather than answering them like normal. So, using ROM manager I went to find a free ROM to try and also upgraded Clockwork Mod at the same time. Now, I cannot boot into Clockwork Mod and the screen is stuck on the green Android icon. I can, however, use ADB to do things but am on a Mac so most of the threads of I've read are either PC or strictly Linux related.
What I have tried to accomplish: adb push command to put another update.zip file on the sd card but shell told me that I couldn't move it to a folder (found that kinda odd)... also tried to put a recovery.img in the root folder and reboot but nothing happened... booted into the standard recovery deleted data & cache and rebooted... nothing seems to work.
I don't have a landline so I'm really, really stuck. Can someone please either tell me what to do or point me where I can get Mac specific advice? Thank you!!!
Well first off since your on a icrap why dont you have a windows VM on your mac?
Aside from that the only thing i could recommend is using the SBF file and reflashing your phone since you are having issues with clockwork and then start over reinstalling clockwork and reinstalling Liberty on your D2
Hopefully this link helps even though its for PC
http://www.droid-life.com/2011/09/0...k-to-stock-2-2-to-receive-gingerbread-update/
Honestly, that's not very nice at all. It's a very stellar machine... the answer to you question is that I've maxed out my RAM at 3GB and to run ANY VM solution requires a buttload of memory resources.
I've seen a lot of posts about SBF files but how in the world do I get it on my phone? I've tried ADB PUSH command but I keep getting told that it won't upload because it's a "folder". It's the strangest **** I've ever seen. The folder is RW so I can't imagine what it's complaining about.
Thank you for the link, though. I will indeed check it out.
Winblows doesn't recognize the device while in bootloader
I get through #5 but am stuck because damned Winblows doesn't recognize the device while in bootloader!!! HELP!!!!!
*Make sure your battery is fully charged.
1. Download and install Motorola USB drivers that fit your Windows system. [Download]
2. Download and install RSD Lite 4.8. [Download]
3. Download the Droid2 SBF file from above to your PC.
4. Unzip that file to somewhere other than your desktop.
5. Open RSD Lite, tap the “…” button, find the 2.3.20 SBF file that you just unzipped and select it.
6. Plug your phone into your computer and turn it off.
7. Boot into bootloader by holding the Up Arrow and then holding Power until the screen flashes.
Should say “Battery OK – OK to Program – Transfer Mode: USB”
8. Click the start button and allow your phone to flash 2.2 (2.3.20 Blur).
9. When your phone gets to 100% and reboots, you are all done.
10. If your phone reboots and has a bunch of Force Closes, you need to factory reset.
11. Boot your phone into recovery using ADB and command “adb reboot recovery.”
12. Run a factory reset/wipe data. Reboot your phone and accept the update.
FINALLY after a solid 11 hours of monkeying around with the blasted thing...
I have my Droid 2 back... however, I'm posting my experiences here in the event that someone in my situation needs answers:
At the time of this writing, this is the software that's available and necessary to bring your phone back from the dead:
RSDLite5.5.msi - Downloadable from here: http://www.4shared.com/file/no12cF9K/RSDLite55.html
Motorola_End_User_Driver_Installation_5.2.0_32bit.msi - Downloadable from here: http://www.mediafire.com/?71c12qc4a1svqza
VM Ware 4!!!! (Especially if you're running Snow Leopard or Lion)
Windows 7 (my version is Ultimate but I don't believe it matters what version you have)
DO NOT USE the free, open source, Virtual Box! You will be spinning your wheels needlessly and driving yourself batty for HOURS if you try. After borrowing a copy of VMWare Fusion 4, my phone was back up and running in 30 minutes...
So, use the link that fatalfury suggested (http://www.droid-life.com/2011/09/0...k-to-stock-2-2-to-receive-gingerbread-update/) and substitute the software above... you'll be back in a flash... pun intended!
Well good to hear the link i provided worked with the exception of certain files.
The only reason why i mocked the mac is because there are a lot of things Mac's are unable to do when it comes to hacking certain programs or hardware and i always have to goes back to using windows to make it work. Thats the only reason why i said it.
Also which version of vbox did you use? i usually use it from the link below. never had problems before on Mac computers.
https://www.virtualbox.org/wiki/Downloads
Completely Bricked Droid 2
I was in the process of flashing Cyanogenmod 7 onto my friend's Droid 2 and after being stuck at the boot up Motorola symbol my friend removed the battery and now it won't turn on at all. I've been searching for fixes all over the place and I can't find anything useful. I would prefer a good fix with a PC but a fix with a mac will work as well. Can anyone help me out please?
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
greyphox said:
Hi Guys
Another rooting/flashing noob here that's messed up his N7 sorry
I know there's other threads with similair issues but they all advise fixes involving using adb connection and usb debugging which I cannot do (explained below)
My device will turn on, it goes to the google logo with the green start icon, I can select and go into bootloader and recovery, if I press start it says booting failed in the upper left corner and will go no further.
My device is plugged in via usb, i have the latest rookit 1.5.5, and sdk installed etc, i also have the naked drivers and the factory images from google on my pc.
The machine came with 4.1.2 installed (nakasi-jzo54k).
To mess it up, somewhere in between updating to 4.2, rooting and unrooting it, and flashing it i must have done something wrong but being a happy button bashing noob I don't know what exactly...
And yes I also didn't make a backup of any kind because well I'm just a moron and lesson well learnt.
So yeah, I have no adb connection, can't go into debuging mode and it won't boot.
Does anybody know if there is anyway I can restore my tablet please? Any help would be hugely appreciated!
Many thanks
Click to expand...
Click to collapse
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Wilks3y said:
If you got half way through rooting, what has happened to your ADB?
Try the option "Return to stock and Flash stock image" try that.
What message does ADB give you etc?
Click to expand...
Click to collapse
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
greyphox said:
Hi thanks
Well when I run 'adb devices' in dos the device does not come up, blank etc
but if in the advanced utilities section of the rookit it will reboot it and say connected etc when i try to boot/flash image for bootloader, system, recovery etc but always goes back to google logo and won't boo up, can still get into bootloader and recovery though
i fully rooted it and unrooted it, i tried to flash 4.1.1 to see if i could thats when this all started
if i try flash stock + unroot option (device is on/normal) sub option the rootkit tries to check adb status and says not connected etc which makes sense as dos won't detect it, if this helps in device manager its coming up as...
samsung android phone
android bootloader interface
so i that driver in rootkit to manually install the naked drivers in device manager and it will say they are up to date etc
so the advanced utilities section for boot/flash image will communicate but no other.....
flash stock root used to detect it but even then in dos it would give me the 'too many links error'
I just hope there is a solution.... and i hope all that makes sense sorry
Cheers
Click to expand...
Click to collapse
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
nexus toolkit from dev section
ngoralph said:
nexus toolkit from dev section
Click to expand...
Click to collapse
Have you even read what hes said?
He's already tried the toolkit...
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
The first step in the full driver guide in wugs kit is to enable usb debugging which i cannot do though as it won't power on.......
I have added the environmental variabes before yes sorry, qbkings utube vids showed me how to do that
Just tried these steps
toolkit home screen, flash stock + unroot (softbricked bootloop)
then naksaki 4.2 jzo54k, auto download and extract.
it got to dos stage and i get 'Failed bootloader is locked'
??? thanks again
Wilks3y said:
Have you added ADB to your envioronment varibles?
If not,
Control Panel -> Advanced -> Envioronment Variables, then add the path to your SDK folder to it, after the other variables (Variables are separated using ; )
Also, try to install the drivers, using Wug's method, thats THE ONLY ONE that worked for me, unistall anything to do with nexus before hand.
Goto Device manager, find anything that involves Nexus or Android.
Then Start the "Full Driver Method" on Wugs kit.
This should sort your driver issue.
Then the Nexus should be visible through ADB.
PS- Your adb isnt broken if its accepting the commands.
The reason your device isnt listed, is the Drivers.
You have driver issues, so try the what I just stated and let me know .
Click to expand...
Click to collapse
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
greyphox said:
OK unlocked it via the main unlock option on rootkit and it unlocked ok, so im now re-trying te softbricked option to flash etc and its currently.. writing system...
Click to expand...
Click to collapse
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Wilks3y said:
Sounds good mate !
Need any extra help drop us a PM I'd be happy to lend a hand.
Click to expand...
Click to collapse
MOOOOOO!
It wrote to the system ok and now its hanging on erasing user data, googled and its happend to others.......
OK, more help please, been hanging for5 mins lol
Issue Fixed I think, he PM'd me.
Unlocked but... what do I do now?
Newbie but old or old but newbie - With the need and not just a curious want, to be able to "rename" my Nexus 7 v1 so I can see a friendly name in my old DD-WRTed Linksys GL, I finally had enough gumption to try rooting this tablet.
So, I was excited that when I used Nexus Root Toolkit v1.6.8 on my Nexus 7 v1, following the "easy and visual" steps, I actually managed to unlock this device. But when it came to the "root" part, the ADB repeatedly failed to recognize this tablet. I tried all the suggested steps and remedies, but so far, nada.
The tablet now boots past the white "Google" with an unlocked icon at the bottom, but nothing beyond thea big white "right-arrow" on the screen. I can choose a Wi-Fi signal to connect to, but that's it.
This is my first tablet and I have been playing with it for the past 3 months. I know people here are more than willing to help, so thank you in advance.
BTW, I am not that young to spend hours way past sleeping time to scour for answers and piece it together.
Wilks3y said:
Issue Fixed I think, he PM'd me.
Click to expand...
Click to collapse
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Kindred Mole said:
Could you let me know his solution as I have exactly the same problem and have used all of his previous (unsuccessful) fixes myself?
Click to expand...
Click to collapse
+1
This worked for me...
Download the image file for your device which you can find at the Google Developer's site
Copy the uncompressed files from the image archive to the platform-tools folder of the Android SDK
Use the up and down volume on the device to get into bootloader mode. Connect the device to a usb port.
Open a command prompt in the platform tools folder and run the flash-all batch file to load the image to your device. After a few minutes I got the happy X logo to get me back to a blank slate.
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
bennatpjose said:
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
Click to expand...
Click to collapse
have you tried to flash a pre-rooted JB?
Sabyn said:
have you tried to flash a pre-rooted JB?
Click to expand...
Click to collapse
is there a guide somewhere
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
to flash a version of JB? come on my page , i can give you a link to my dropbox , there is anything you need
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
i also have an e617g on 4.1.2 bell network id like to root and unlock the bootloader so i can install cwm and finally swap roms, this is a nice phone but it barely exists on the web any help would be greatly appreciated, thanks in advance
Never mind figured it out myself. I may post a guide here soon. Seeing as any help I ask for is ignored. I'd rather help than hold back
Turn your lG-e617g into an LG-e610 then root it and install cyanogenmod.
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
I had already tried that but i keep getting the bloody error in KDZ
03:58:19 : Launching SW update
03:58:19 : Unpacking KDZ
03:58:21 : KDZ file extraced
03:58:21 : Extract file error
03:58:23 : ===FINISHED===
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse
That happens when the kdz file is corrupted. Redownload the firmware and try again
its more than likely a bad connection causing a bad download also are you starting off with an e617g or e610?
Will all app data, contacts, etc. be lost using this method? Thanks in advance!
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse
yes definitely back up
r4nd0m14m said:
yes definitely back up
Click to expand...
Click to collapse
Does this method actually unlock the network too? Can I use fido sim card? would it work?