QUESTION!
Good evening all. I'm brand spankin' new to this and have a question (which is more of an issue ).
So..
Rooted my Prime, and the "Unlock Device Tool" gives me the following error message: "An unknown error occurs, which may be a network connection issue. please wait and try again later".
Now, I've installed everything correctly and noticed a similar thread regarding this, but the verbatim of the error message was different. I'm unable to boot into recovery--when I do, the Android falls down with an exclamation mark coming out of his chest. Poor guy, must be painful..
Anyway, can anyone lend me a hand?
Thanks in advance.
Maybe you should install CWM recovery first...
You can use ROMManager to do this.
Oh and we guys here in these forums love to see actual thread titles...
Oh and we love to have threads in the right section too...
Diamondback is correct, we do like thread titles.......but I would also try looking to make sure when you have your prime plugged in via usb to your computer that you have the correct drivers installed I had that issue as well till I put the right drivers in. I used the naked drivers posted here works great has I have 4 android devices and it doesnt require to reinstall a driver for each device everytime you connect the device to the computer.
http://forum.xda-developers.com/showthread.php?t=1426502&highlight=naked
And boom goes the dynamite..
I apologize, gentleman..I thought I had constructed an appropriate thread title and posted in the correct forum. Apparently, I was mistaken.
Regardless, your suggestion (Ultraman666) did the trick. I really appreciate your help! Thanks a bunch! Huge help. Pumped.
Awesome glad to help at one point or another we have all been there!!!!
Sent from my Transformer Prime TF201 using Tapatalk
Hey There
Also a noob here. I was wondering what you did KMayock87.
I'm having the exact same issue with my Transformer Prime. I've got no issues with getting OTA's and my serial number is showing up and valid. But when I try to Unlock, always the same message for a month now.
Laubot said:
Hey There
Also a noob here. I was wondering what you did KMayock87.
I'm having the exact same issue with my Transformer Prime. I've got no issues with getting OTA's and my serial number is showing up and valid. But when I try to Unlock, always the same message for a month now.
Click to expand...
Click to collapse
The same question with this guy!
Laubot said:
Hey There
Also a noob here. I was wondering what you did KMayock87.
I'm having the exact same issue with my Transformer Prime. I've got no issues with getting OTA's and my serial number is showing up and valid. But when I try to Unlock, always the same message for a month now.
Click to expand...
Click to collapse
duy_ctytvxdkg said:
The same question with this guy!
Click to expand...
Click to collapse
Ultraman666 said:
Diamondback is correct, we do like thread titles.......but I would also try looking to make sure when you have your prime plugged in via usb to your computer that you have the correct drivers installed I had that issue as well till I put the right drivers in. I used the naked drivers posted here works great has I have 4 android devices and it doesnt require to reinstall a driver for each device everytime you connect the device to the computer.
http://forum.xda-developers.com/showthread.php?t=1426502&highlight=naked
Click to expand...
Click to collapse
The issue was bad drivers. Download the naked drivers utility, duly linked by Ultraman666, and follow through with whatever it needs and you should be fine.
-----------------------------------------------------
BTW, OP, as stated a little more in the title will pull more people that know what's up to the thread. As it is right now you're just catching us Curious Georges. Anyway, welcome, glad the issue is solved!
buxtahuda said:
The issue was bad drivers. Download the naked drivers utility, duly linked by Ultraman666, and follow through with whatever it needs and you should be fine.
-----------------------------------------------------
BTW, OP, as stated a little more in the title will pull more people that know what's up to the thread. As it is right now you're just catching us Curious Georges. Anyway, welcome, glad the issue is solved!
Click to expand...
Click to collapse
It's a wrong point bro.
May I explain:
Already upgrade .21
Now, if I want to root I have to do some steps:
1. Unlock bootloader
2. Install CVW
3. downgrade to .15 via CVW
4. Root with viperMOD PrimeTime v4.5
Normally, step 1 will run without any issue. this time always receive this error:
"An unknown error occurs, which may be a network connection issue. please wait and try again later"
It only run on the tablet, no need to connect to PC so I'm quite sure it not the driver problem.
duy_ctytvxdkg said:
It's a wrong point bro.
May I explain:
Already upgrade .21
Now, if I want to root I have to do some steps:
1. Unlock bootloader
2. Install CVW
3. downgrade to .15 via CVW
4. Root with viperMOD PrimeTime v4.5
Normally, step 1 will run without any issue. this time always receive this error:
"An unknown error occurs, which may be a network connection issue. please wait and try again later"
It only run on the tablet, no need to connect to PC so I'm quite sure it not the driver problem.
Click to expand...
Click to collapse
Got ya. So you're voiding warranty just as a round-a-bout for root?
I'm not sure what the issue would be, and ASUS doesn't seem too keen on providing support even for the unlock utility. Keep looking around, maybe try PM'ing Gary from one of his stickies; let us know if you find a solution.
buxtahuda said:
Let us know if you find a solution.
Click to expand...
Click to collapse
I've just returned it to store
Related
-please read the whole thread-
:The point of this thread.
Find a way to get flash mode to stay active longer, Gives you more time to work and experiment"
The point of basing it on on the newer driver is that there may be something in them that will give us access to Fastboot"
Hopefully use that to get to the boot loader.
:--
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be useful.
It ejects when flash mode isn't used i think.
Sent from my X10i
jockep said:
It ejects when flash mode isn't used i think.
Sent from my X10i
Click to expand...
Click to collapse
No.
please just listen to me.
If any developer is interested in this PM me and i will explain.
Just a note but you may want to mention which version of the flash tool you are having issues with.
exsulis said:
Just a note but you may want to mention which version of the flash tool you are having issues with.
Click to expand...
Click to collapse
Please.. as i said DEVELOPERS ONLY.
PLEASE DON'T spam.
I'm not talking about the flash tool.
i don't think it has anything to do with the driver, as much as the phone's flashmode behavior itself.
ie the computer recognises the device device differently whether its in regular usb mode, debugging, mounted, flashmode, etc.
i think what it's experiencing is flashmode turns off if there's a delay, and changes usb mode. the computer sees the change as "device A" no longer there and "device B" now there. the computer will see the different usb modes as separate devices since there will be separate ID's for the mode.
if there was a way to keep the phone in flashmode, this would fix the problem. but there's no way of doing that without changing and reflashing fastboot/bootloader.
Then perhaps a driver that acts more like the drivers for the newer phones.
I think.. Fast boot could easily be accessed this way.
And all we need is for it to load that driver and to test using this command.
fastboot.exe -i 0x0fce getvar version
This is all speculation.. but call it a lucky hunch.
If i am wrong then the mods may delete this thread and XDA may ridicule me.
If anyone does manage to do this.
The credit is all yours.
No.. now i am sure the X10's driver may be buggy.
Hold the flash button and insert your charging lead using the wall charger.
You will notice it stays in flash mode for much longer.
I may be wrong.. but test it.
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
but don't get me wrong, if you or any devs know of a way to exploit it, by all means go to it!
svtfmook said:
that's because the data signal sent doesn't receive an answer at all.
in simple as possible terms:
when plugged into a computer, it sends the signal that it's flashmode, computer resonds "ok", device signals back "instruct", if the computer responds, it flashes, if there's no response in the defined time, the phone reboots out of flashmode.
i doubt that this could be used as an exploit, else we would have been able to fake SEUS or PCC into flashing a custom bootloader.
Click to expand...
Click to collapse
I know this.. But i would like to get a few more developer opinions on this.
OmegaRED^ said:
I know this.. But i would like to get a few more developer opinions on this.
Click to expand...
Click to collapse
no doubt. would be cool if it could be exploited.
svtfmook said:
no doubt. would be cool if it could be exploited.
Click to expand...
Click to collapse
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
OmegaRED^ said:
I hope.. that i am right.
But my gut tells me something is there.
If anyone does achieve this
"no need to credit me"
Click to expand...
Click to collapse
Never head that on the x10 forums
Sent from my X10i using XDA App
rtblittlebrown said:
Never head that on the x10 forums
Sent from my X10i using XDA App
Click to expand...
Click to collapse
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
OmegaRED^ said:
This is not about me... but us the x10 users.
I hope that a few developers will pay attention to this idea.
Click to expand...
Click to collapse
If other devs had that attitude they may already have picked this thread up
Seems you may have fallen foul of someones temper tantrum
Sorry for the spam
OmegaRED^ said:
Weird.. for some reason now when ever i reboot my phone it goes into flash mode automatically.
Click to expand...
Click to collapse
If your plugged into your charger that happens on older rom's with charge when off problems
Sent from my X10 using XDA App
OmegaRED^ said:
I noticed today that there is a bug in the x10 flash driver that forcefully ejects the device from flash mode after a delay if it does not get initialized.
I am looking for someone that can make that driver stop ejecting the device.
"This is for real.."
Do not spam here "there is method to my madness"
Perhaps even act more like the driver used to unlock the newer phones.
But for the x10.
The file i attached may be usefull.
Click to expand...
Click to collapse
Not to throw a spanner in the works BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Edit: also some more research it indicates the its the android generic open driver inf
asmanthebell said:
Not to throw a spanner in the work BUT! Just so you know the driver you have installed is designed for the later Xperia Phones like the play etc perhaps if you removed the driver deleted the software that goes with it then re-installed the CORRECT driver then you would have less of a "Buggy" driver as you put it! Sorry for the put down but dont wanna get you carried away!
Click to expand...
Click to collapse
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
This is why i asked for developers only to reply.
OmegaRED^ said:
Um.. no.
I think you misunderstood.
Currently i have the X10 driver installed on my system.
Maybe you should re read the whole thread.
I am not asking for help on how to install drivers.
or what drivers to install.
Click to expand...
Click to collapse
Sigh!
1. Do you know and understand what an .inf file is?
2. Do you know how interacts with an operation system?
3. Can you post the rest of driver i.e the .cat file and .sys to go with the inf?
hey all! great forum... former se x10 mini user... getting my atrix today!
my main question is: i want to install greyblur after rooting but there are always warnings about not installing it on the BELL version... yet i see, via their signatures, that many bell users have it installed... the guide for greyblur does not have specific instructions for bell, just has big warning in red saying not to install it on bell!
so how do i get it working?? what do i need? i'm pretty handy with android, so no need to have crazy detailed help...
thanks everyone! looking forward to learning more and more about this great device!!
ryan
watchyourbreath said:
hey all! great forum... former se x10 mini user... getting my atrix today!
my main question is: i want to install greyblur after rooting but there are always warnings about not installing it on the BELL version... yet i see, via their signatures, that many bell users have it installed... the guide for greyblur does not have specific instructions for bell, just has big warning in red saying not to install it on bell!
so how do i get it working?? what do i need? i'm pretty handy with android, so no need to have crazy detailed help...
thanks everyone! looking forward to learning more and more about this great device!!
ryan
Click to expand...
Click to collapse
See the thread called "SBF/root/deodex 2.1.1 SBF" or something along those lines (in this forum). In order to get greyblur/GingerBlur working on a bell phone you have to flash an international SBF file. Right now the most current is 2.1.1, a generic SBF (leaked from France). Just be warned that flashing this will void your warranty. However, it hasn't caused any issues itself and wont CAUSE anything on your device to fail at all, if you get into trouble its most likely just bad luck with hardware and if you REALLY need to return your phone there is a general way to make it seem like you've gone back to stock, that you can do with the help of forum members here if needed.
Not trying to scare you off, I've done this myself. I'm just making sure you understand the risks. Hope this post helps you understand what you're getting into and where to go for further info.
Also, this should be in Q&A section, not dev.
Sent from my MB860 using XDA Premium App
not scared at all! thanks for the PERFECT response!
Moved to proper forum.
ok, i'm going through the steps but for some reason the x64 drivers won't install (yes i have 64-bit windows.). says this:
"The system administrator has set policies to prevent this installation."
i assumed they weren't required.
nothing happens when i run rds before plugging in phone. when i reboot the phone, i see the rds protocol message, i run rds on my pc, plug in the phone and nothing happens....
thoughts?
I know nothing about windows sorry bruvva
I do know that once you are running a p rom pretty much everything becomes compatible
Sent from my Googletron
watchyourbreath said:
ok, i'm going through the steps but for some reason the x64 drivers won't install (yes i have 64-bit windows.). says this:
"The system administrator has set policies to prevent this installation."
i assumed they weren't required.
nothing happens when i run rds before plugging in phone. when i reboot the phone, i see the rds protocol message, i run rds on my pc, plug in the phone and nothing happens....
thoughts?
Click to expand...
Click to collapse
well the drivers do need to be installed, you can find the necessary drivers in an executable package here although i can't tell you whether admin restrictions will block that too. might be easiest to find a PC where you can do stuff as an admin depending on your current system's configs.
once drivers are installed your PC will recognize device when in RSD mode.
I would assume that the login on your comp is not set as an administrator. You have to be logged on as an administrator to modify system files or drivers in windows.
You could also try right clicking the usb driver installation exe and choose "run as administrator".
Sent from my Cool Blue Atrix on Bell using the XDA Premium App.
Hey
Regarding the Win 64 driver, I had the same issue, until I realised the link given in the thread about 2.1.1/Greyblur for the driver lead to a corrupted file (~ 500 kb) even using a download manager. I downloaded them from elsewhere (Motorola Website) and the error message disappeared without having anything else to do.
Hope that helps!
Guillaume
Actually got the whole thing going a while back... sorry for not checking back!
I am officially enamoured by this phone......... the start of a beautiful and complex relationship ...
And yeah, I suspected that it had something to do with corrupt file... tried a few diff sites but all seemed the same... eventually tried a diff usb port and it worked...
Sent from my MB860 using XDA App
So....I wanted to un root and and return my prime back to stock so I did the dumb thing by un rooting my prime and then doing a factory reset from the settings menu.
Now when I rebot my prime it keeps coming back to CWM and I can't get it to flash my recovery, though I know why. Its the recovery of a custom rom, a rom that needed to have the prime rooted.
Another ****ty thing is that I can't get my computer to recognize the prime. I see it in my device manager, but I can't get the USB drivers to install. I was hoping to use my micro sd card and install the stock rom, but I can't seem to find it when I look for it in CWM. I really need your help folks and I hope that some of you really smart people can help me.
Thanks
Kyle
kac7418 said:
So....I wanted to un root and and return my prime back to stock so I did the dumb thing by un rooting my prime and then doing a factory reset from the settings menu.
Now when I rebot my prime it keeps coming back to CWM and I can't get it to flash my recovery, though I know why. Its the recovery of a custom rom, a rom that needed to have the prime rooted.
Another ****ty thing is that I can't get my computer to recognize the prime. I see it in my device manager, but I can't get the USB drivers to install. I was hoping to use my micro sd card and install the stock rom, but I can't seem to find it when I look for it in CWM. I really need your help folks and I hope that some of you really smart people can help me.
Thanks
Kyle
Click to expand...
Click to collapse
Easy, Go to http://forum.xda-developers.com/showthread.php?t=1514088 and follow Brick 1a... Next time search the forums before you post.
Sorry to be a pain, but i did all of that. What I am having trouble doing is setting up the adb, (I have watched all the youtube vids and forum post I can find) I can't get my computer to link with my prime. I have watched every video and read as much as I can, but can't see to get drivers installed.
I can tried USBDreview, following every step on every forum I can find. When I go to device manager it says "transformer" with a yellow !, but I can't get any type of driver to work.
Trust I am not trying to be a pain, but I have google and read a ton, I just can't figure it out.
kac7418 said:
Sorry to be a pain, but i did all of that. What I am having trouble doing is setting up the adb, (I have watched all the youtube vids and forum post I can find) I can't get my computer to link with my prime. I have watched every video and read as much as I can, but can't see to get drivers installed.
I can tried USBDreview, following every step on every forum I can find. When I go to device manager it says "transformer" with a yellow !, but I can't get any type of driver to work.
Trust I am not trying to be a pain, but I have google and read a ton, I just can't figure it out.
Click to expand...
Click to collapse
download and install the android sdk.
DID that, but some I go to the command prompt it wont find any devices and I have tried and tried to get the right drivers. I just can't get it installed. Right now I am trying to figure out Universal Naked Driver Beta 0.6.2 on how to install it to see that will work.
I will keep trying
Ok the Naked Driver worked, well I think it did.....in my device manager its now saying Asus Transformer Prime ADB Interface.....I am now starting from the begining with ADB.
I am sure I will have more questions please post if you have any tips or suggestions
and THANK YOU again.
Kyle
I've downloaded all of the necessary files and drivers for Adam Outler's Once click root and bootloader unlock method but it never seems to get started. I run the Casual, and click the large "Do It" button, but then nothing happens. I don't get the prompt to continue and the "do it" button simply turns grey. I've let it sit for a while and still nothing.
I've uninstalled/reinstalled drivers as well as re-downloaded the Casual.
I've flashed with Odin back to stock.
I've installed Kies.
I'm running Win 7.
I've noticed others on YouTube have stated they have the same issue but I haven't been able to find a solution. Any help would be much appreciated.
Thanks!
could you spare a link for the drivers please? sorry im not any help but im trying to figure this out too....
almo40192 said:
could you spare a link for the drivers please? sorry im not any help but im trying to figure this out too....
Click to expand...
Click to collapse
Wish I could man, but I can't post links yet because I'm still considered a new user.
The best thing to do is delete your current drivers in device manager then plug your phone back in and let windows install them itself. You could also try Samsung Kies.
Here's a link to the Samsung drivers... hope its helps
https://rapidshare.com/#!download|9...|0|1|referer-D5C0B416112024B8E29A2190DD43125B
Have u tried running casual as administrator... not sure if that'll help or not..
TaPpEd from my TwEaKeD N2
Has anyone had this issue?
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
What procedure are you using to unlock? The WTF process is the one that I believe has worked the best for most people... and that doesn't have anything special on the phone screen, so I'm thinking you're using some app or script?
dsk1000 said:
I'm stuck on waiting for all devices in adb.. My phone screen has a menu with three choices, one of them is flash unlock.bin. Should I keep waiting for all devices for how long in adb?
Click to expand...
Click to collapse
Yea, I'm following that one. I read somewhere about AMD PCs causing problems. My phone shows when I use adb devices. So should I be a little more patient or what?
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
schwinn8 said:
No, the processes are quick. AMD Ryzens typically have issues, but it's only because of the USB driver they use. I've heard a few Intels have issues sometimes as well.
The key is, you just need to try other computers... this is the "hardest" thing to do, but it's really the only solution to that issue. The process takes under a second, so it's not a patience issue.
For the record, my older laptop with an AMD A9 CPU did the process fine... so, again, it's not a CPU issue, but a driver issue for the USB, apparently...
Click to expand...
Click to collapse
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
dsk1000 said:
Thanks for the reply..I'm super new to adb..but I am following wtf instructions. I will keep researching..and asking questions. Thanks. PS I haven't rooted anything since my lg g3..
Click to expand...
Click to collapse
Some people had to use 2 or 3 computers. An older one with Intel CPU works best (especially if it has USB 2.0), but yes an AMD can work. As noted by @schwinn8 Ryzens are no go. One guy was upset because he had superfast gaming computer and we kept telling him to try another computer. He borrowed his brother's mediocre laptop and BOOM, worked. Another guy dug some old laptop out of his closet and it worked.
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
Also, try the steps mentioned in Wtf troubleshooting section.
Other than that you may have to mess around in the device manager section to see if the phone is detected properly or not.
(if there's a problem with the driver the device will show up as unknown android device or something)
dsk1000 said:
Thanks for the reply...i was just reading about adb making sure it wasn't something i was doing wrong. Even tried on an old iMac that i had installed linux on. "Waiting for device..." So..still reading and learning to be patient. Thank you
Click to expand...
Click to collapse
You said "patient"... just to reiterate, this process doesn't take longer on a computer that says "waiting for device". It's a fast process, so if it's not happening within a few seconds, it won't work on that setup, period. Don't waste your time waiting - get another machine/cable/etc (check the troubleshooting steps to find other possible issues... the computer is usually the biggest problem to overcome, but the most successful).
Good news, i unlocked my phone and installed twrp, then i had to stop the process (wtf)
i still need to make a backup in TWRP and flash two more files from wtf notes. I cannot seem to be able to reboot into TWRP from ADB. thanks in advance
The oem is greyed out in developer mode and says its unlocked. Idk?
Glad to hear you got it unlocked.
In the WTF post it says that the developer mode may remain grayed out after being flipped... this is normal. It comes back after some time. Of course, you don't want to toggle it again anyway, since you're unlocked...
When i go to use an app to boot into twrp..it tells me its not rooted.
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Used getvar..unlocked.
Well its done..used an old hp A6 with linuxmint. I found linux to be straightforward and easy when trying to root my phone. No jumping thru hoops and juggling stuff.
Any recommendations for remodeling the phone? Boot to twrp..roms..ect?
dsk1000 said:
When i go to use an app to boot into twrp..it tells me its not rooted.
Click to expand...
Click to collapse
Bootloader unlocked is not rooted. It's just the prerequisite to being rooted. Then you install TWRP custom recovery and then use that to flash Magisk. It's all in the WTF Instructions. Also be sure to use the version of Magisk in the WTF Instructions, at least initially.
Thanks..ive got magisk from the instructions. It wants to update..should?
Once you are booted into Android, you can update Magisk to some degree. I forget the last version I had but I recall I could go to 20.x or something without issue. But there is always a risk of having issues if you update to the latest version... so be prepared to go back to the one on the WTF thread if the phone has issues. In other words, don't do this last minute or without a PC to work from... because it could fail.
The only time you have to use the old Magisk is during that first boot with it... once you're booted through, you have been able to update to newer versions. But unless you need some specific feature of the newest version, I might suggest leaving it alone...
I read somewhere..when i upgrade on US 998 20b, i need to move up to 20c?
Also, do i use the "twrp version. 20c"?