Related
Can anyone definitively explain the reason why some can and some can not unlock their bootloader? I've searched all over the forums and see reasons the span from left to right. I typically just lurk in the background and figure out methods to install custom ROMS on my own, but this unlocking situation is starting to chap my my arse. I've been trying for about two weeks to use the ASUS tool, but it ain't working for me.....I keep getting the same connection message that other's are getting.
Anybody got a good answer or an even better solution?
From what I've read it seems to be because of their method to track who unlocks. It takes your serial number and then they know so they can void the warranty. However a certain amount of numbers also got put on that list. So when you go to use it it doesn't work because it's only a one time deal to prevent from relocking /unlocking. I'm not 100% sure on this because there isn't really any information available but that's what I've heard from a bit of looking around.
Sent from my ASUS Transformer Pad TF300T using xda premium
All I did was download the apk from asus and installed on my tablet and bam unlocked the tablet took 5 minutes if that. What methods are you doing?
Ok so I found this looking around.
http://forum.xda-developers.com/showthread.php?t=1669328
That thread seems to show/explain a lot. Plus maybe reading it will stop double posting.
Sent from my ASUS Transformer Pad TF300T using xda premium
Yeah, saw that post. Tried it too......nada. I've got a C30KCT S/N too.
Just curious for those of you that have successfully unlocked your tablet.....did you happen to register your device's S/N with ASUS?
No registering necessary. Just go here:
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
choose android as your OS and click on Utilities and download the Global link and transfer that apk file to your tablet and run it. You should be be unlocked after running the program and following the on screen instructions.
vel0city said:
No registering necessary. Just go here:
http://usa.asus.com/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
choose android as your OS and click on Utilities and download the Global link and transfer that apk file to your tablet and run it. You should be be unlocked after running the program and following the on screen instructions.
Click to expand...
Click to collapse
The app you just told people to download is the same one that isn't working. The problem they're having with the app is that they get a network error when they run the app. The error is because the user's serial number isn't in the Asus database. This wouldn't be a big deal if you could just tell Asus and ask them to fix it. Unfortunately, the instant you run the app, you lose your warranty, so when you tell them that you ran the app and it didn't work, they tell you you're out of a warranty, and they can't help you.
The only solution anyone's found so far is to keep trying and hope Asus adds your serial to their database.
EndlessDissent said:
The app you just told people to download is the same one that isn't working. The problem they're having with the app is that they get a network error when they run the app. The error is because the user's serial number isn't in the Asus database. This wouldn't be a big deal if you could just tell Asus and ask them to fix it. Unfortunately, the instant you run the app, you lose your warranty, so when you tell them that you ran the app and it didn't work, they tell you you're out of a warranty, and they can't help you.
The only solution anyone's found so far is to keep trying and hope Asus adds your serial to their database.
Click to expand...
Click to collapse
Thanks for the heads up did not know that I guess my friends and I have been lucky then unlocking our bootloaders I mean I unlocked and rooted about 10 tablets and didnt come across this lol.
Yeah, the problem first got attention when a bunch of people weren't getting OTA notifications. Some folks went to devicetracker.asus.com and entered their serial numbers and were told that the serial number was invalid. These same people got tired of waiting for the OTA and decided to just unlock their tablets and install custom ROMs. Unfortunately, they just got a network error. Someone, at some point, called Asus support about the OTA and was told about the database problem. Apparently, it hasn't been completely fixed yet. Eventually, I think, most people either got their OTAs and/or the unlocker started working. There were also reports that downgrading to .17 and doing a factory reset solved the problem for some people but not others. Other people said that clearing data for certain services made it work, but not everyone got that to work, either. The only options you have are to either wait or return the tablet and hope the replacement doesn't have the same problem.
So, if you've received OTA's and registered with device tracker it'd be a safe bet they have you in the their db, right?
Yup. I meet both criteria and just unlocked successfully.
I tried to Unlock my bootloader today using the One click - non htc dev method
and failed miserably. It didn't work and i managed to overwrite my own partitions with the ones used to unlock the bootloader. I officially have a different IMEI then i originally started with.
Having that said i plan on going into ATT tommorrow and getting it replaced under the 30 day warranty, my question now is Even though my imei is different will they still take my phone ?? Will they even Check that? Or am i Royally Screwed.
I stuffed mine up for some reason it didn't like the unlock token so I still had the spoofed partitions on my device so I had the incorrect imei and partitions and my LTE was no longer there it was like the phone didn't know it could do that.
Basically all I did was re-run it - when it's paused I changed the phone's USB connection from charge to disk drive, found the mypartitions folder on the sd card and deleted the contents and put the correct partitions that were on my pc, let it go into fastboot, rebooted the phone into android and then hit any key so it could copy back the correct ones, waited a lil while in android, the phone rebooted and I now have the right imei and my LTE connection back.
I hope that helps.
thejosh86 said:
I stuffed mine up for some reason it didn't like the unlock token so I still had the spoofed partitions on my device so I had the incorrect imei and partitions and my LTE was no longer there it was like the phone didn't know it could do that.
Basically all I did was re-run it - when it's paused I changed the phone's USB connection from charge to disk drive, found the mypartitions folder on the sd card and deleted the contents and put the correct partitions that were on my pc, let it go into fastboot, rebooted the phone into android and then hit any key so it could copy back the correct ones, waited a lil while in android, the phone rebooted and I now have the right imei and my LTE connection back.
I hope that helps.
Click to expand...
Click to collapse
I didn't backup mypartitions at 2nd attempt and lost my original partitions
any chance of dumping mmcblk0p5 & mmcblk0p6 out so I can try to restore LTE?
if you want to give a shot, please use hex editor to change your own IMEI to EIEIEIEIEIEIEIE, mac to 00:11:22:33:44:55 and s/n to HTYMDWSNSNSN in both files before sending them out
here is my post about LTE problem after one click bootloader unlock
http://forum.xda-developers.com/showpost.php?p=28542994&postcount=81
How would i go about dumping the partitions? I would like to try it and see what i can do.
gmanfuzing said:
I tried to Unlock my bootloader today using the One click - non htc dev method
and failed miserably. It didn't work and i managed to overwrite my own partitions with the ones used to unlock the bootloader. I officially have a different IMEI then i originally started with.
Having that said i plan on going into ATT tommorrow and getting it replaced under the 30 day warranty, my question now is Even though my imei is different will they still take my phone ?? Will they even Check that? Or am i Royally Screwed.
Click to expand...
Click to collapse
These posts should be treated like Warez and deleted. Seriously suggesting that you would go to AT&T for an exchange after knowingly voiding your warranty is akin to stealing.
sassafras
So I did the exact same thing as many others. I ran the script more then once and wiped out my IMEI number.
I have put together a fix that may help you restore some of what have been lost. This is a modification of the original script [Found Here] left us with spoofed partitions.
1. Extract this ZIP and run "backup.bat".
2. This will create a "mypartitions" folder containing your mmcblk0p4, mmcblk0p5 and mmcblk0p6
3. Use a HEX editor to modify each of these files to show the correct IMEI. In mmcblk0p6, you should also correct you SN and MAC (if you know it)
4. Run "restore.bat" to restore the modified partitions.
Free Windows Hex Editor
Files to fix the IMEI
Note: I am with AT&T and it is working with LTE. I have read that individuals with Roger's are still having LTE issues even after fixing their IMEI.
Note #2: This process will also allow to create the backup erasen1 is referring to.
sassafras_ said:
These posts should be treated like Warez and deleted. Seriously suggesting that you would go to AT&T for an exchange after knowingly voiding your warranty is akin to stealing.
sassafras
Click to expand...
Click to collapse
wooooooooooooooooh the big "S" word......as gunny wrote: "Until they quit stealing from us, I'll keep stealing from them"
Now I don't believe that this is stealing at all. He was looking for help to try and fix the problem. I ran into this problem as well and would have loved to have a fix for it but the phone I was using started to reboot randomly, hence it getting returned to AT&T. It's only a phone and software, he's not asking for way to spoof his IMEI to get services he didn't pay for, that would be stealing.
Exchanged is hardly stealing imo. Putting limited on so called unlimited data is.
I used the attached tools to flash back my original Telstra partitions but it still give the spoof details in settings info.
Do I need to be in bootloader to do this? I get an error at the -rf command but the partitions say they have been flashed.
thejosh86 said:
I stuffed mine up for some reason it didn't like the unlock token so I still had the spoofed partitions on my device so I had the incorrect imei and partitions and my LTE was no longer there it was like the phone didn't know it could do that.
Basically all I did was re-run it - when it's paused I changed the phone's USB connection from charge to disk drive, found the mypartitions folder on the sd card and deleted the contents and put the correct partitions that were on my pc, let it go into fastboot, rebooted the phone into android and then hit any key so it could copy back the correct ones, waited a lil while in android, the phone rebooted and I now have the right imei and my LTE connection back.
I hope that helps.
Click to expand...
Click to collapse
This method worked for me. Thanks very much.
Crappyvate said:
wooooooooooooooooh the big "S" word......as gunny wrote: "Until they quit stealing from us, I'll keep stealing from them"
Click to expand...
Click to collapse
And yet, the old adage couldn't be more appropriate. Two wrongs don't make it right.
beankid said:
Now I don't believe that this is stealing at all. He was looking for help to try and fix the problem. I ran into this problem as well and would have loved to have a fix for it but the phone I was using started to reboot randomly, hence it getting returned to AT&T. It's only a phone and software, he's not asking for way to spoof his IMEI to get services he didn't pay for, that would be stealing.
Click to expand...
Click to collapse
Once you unlock the bootloader, you acknowledge that doing something as a direct result of said action can void your warranty. If you unlock the bootloader and then the screen dies or the speaker quits, then exchange is reasonable because you've likely suffered hardware failure unrelated to the bootloader unlock. If you unlock the bootloader, stuff the partitions, and render the device inoperable, you have voided your warranty and are not entitled to a fair exchange.
achllles said:
Exchanged is hardly stealing imo. Putting limited on so called unlimited data is.
Click to expand...
Click to collapse
As above. Furthermore, your ad hominem attack doesn't diminish the fact that returning a phone you've willfully damaged is disingenuous at best and stealing at worst. If you threw it against the wall and then took it for exchange, should they be forced to do it?
Every one who exchanges a phone after willfully voiding their warranty and damaging it through their direct actions is costing the rest of us money. It's not fair to you, and it's not fair to me.
....
Moot point anyway, as he seems to have fixed his problem.
sassafras
So I guess this can be used to change the imei then?
mainecrab said:
So I guess this can be used to change the imei then?
Click to expand...
Click to collapse
indeed
sassafras_ said:
And yet, the old adage couldn't be more appropriate. Two wrongs don't make it right.
Once you unlock the bootloader, you acknowledge that doing something as a direct result of said action can void your warranty. If you unlock the bootloader and then the screen dies or the speaker quits, then exchange is reasonable because you've likely suffered hardware failure unrelated to the bootloader unlock. If you unlock the bootloader, stuff the partitions, and render the device inoperable, you have voided your warranty and are not entitled to a fair exchange.
As above. Furthermore, your ad hominem attack doesn't diminish the fact that returning a phone you've willfully damaged is disingenuous at best and stealing at worst. If you threw it against the wall and then took it for exchange, should they be forced to do it?
Every one who exchanges a phone after willfully voiding their warranty and damaging it through their direct actions is costing the rest of us money. It's not fair to you, and it's not fair to me.
....
Moot point anyway, as he seems to have fixed his problem.
sassafras
Click to expand...
Click to collapse
Did he throw it to a wall, damaged it to a point its unusable, and went for an exchange? Two different things imo. He fixed the problem but he probably still doesn't deserve warranty support based on your expectations.
Hey guys...
So I borked my phone doing the unlocked thing, have only just noticed it when I went into a known 4g area and did not change over...
Need to change my IMEI and serial. But I don't know how to use a hex editor!
In my posession I have an old one xl which it's imei and serial match the simtray, i've dumped these to the pc.
I've also dumped my new one xl's dead ones to the pc.
How do I change the details on the old one xl's files?
Sorry guys! HEX_noob
kyl3 said:
Hey guys...
So I borked my phone doing the unlocked thing, have only just noticed it when I went into a known 4g area and did not change over...
Need to change my IMEI and serial. But I don't know how to use a hex editor!
In my posession I have an old one xl which it's imei and serial match the simtray, i've dumped these to the pc.
I've also dumped my new one xl's dead ones to the pc.
How do I change the details on the old one xl's files?
Sorry guys! HEX_noob
Click to expand...
Click to collapse
check out post 6 in this thread....
be really careful though - I bricked my first One XL doing this. got lucky and got another one under warranty.
the other thing you can do is simply upload the files from the old One XL to your device. as long as the IMEI is in the Telstra 'range' you'll get LTE.
Worked out how to use the hex editor.. **** not hard! duhhhh
---------- Post added at 08:08 AM ---------- Previous post was at 07:41 AM ----------
nerk69 said:
So I did the exact same thing as many others. I ran the script more then once and wiped out my IMEI number.
I have put together a fix that may help you restore some of what have been lost. This is a modification of the original script [Found Here] left us with spoofed partitions.
1. Extract this ZIP and run "backup.bat".
2. This will create a "mypartitions" folder containing your mmcblk0p4, mmcblk0p5 and mmcblk0p6
3. Use a HEX editor to modify each of these files to show the correct IMEI. In mmcblk0p6, you should also correct you SN and MAC (if you know it)
4. Run "restore.bat" to restore the modified partitions.
Free Windows Hex Editor
Files to fix the IMEI
Note: I am with AT&T and it is working with LTE. I have read that individuals with Roger's are still having LTE issues even after fixing their IMEI.
Note #2: This process will also allow to create the backup erasen1 is referring to.
Click to expand...
Click to collapse
Hey mate..
I am able to grab the files ok, edited them ok, however when I transfer them back to the phone, your script says all transferred ok, but the details in the phone do not change.
Any tips? Anything I could be doing wrong?
Thanks heaps!
kyl3 said:
Worked out how to use the hex editor.. **** not hard! duhhhh
---------- Post added at 08:08 AM ---------- Previous post was at 07:41 AM ----------
Hey mate..
I am able to grab the files ok, edited them ok, however when I transfer them back to the phone, your script says all transferred ok, but the details in the phone do not change.
Any tips? Anything I could be doing wrong?
Thanks heaps!
Click to expand...
Click to collapse
Did you restart the phone after copying the edited files back in?
Absolutely
I've unlocked, rooted and ROM'ed probably 100 times on 25 different Android phones and tablets, this looks like my first official TF700 paperweight.
I saw another thread with a couple of people who did the same boneheaded thing I did: tried to install CWM the wrong way. Can't get into the ASUS recovery any more, either I hold volume down and get "Booting into recovery" (then hangs, no adb), or I hold volume up instead and I get a blank screen but it IS recognized as an APX device.
NVFLASH can't do anything at this point, the other thread had no good news either. Why ASUS can't have a "reset to factory recovery and bootloader" option is beyond me. Too late to return to NewEgg.
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20). I have a second TF700 that I unlocked, rooted, and installed CWM the right way. Is there any way using NVFLASH to get the blob from there and putting it on my bricked TF700 or is the blob encrypted to the device? I'm likely out of luck if I try to take the S/N sticker from my second TF700 and put it on the bricked one, ASUS will croak on that most likely.
Are there ANY other options? Short of just opening it up and looking at what's inside? That's a $600 visit I'd like to avoid.
Thanks.
ScaryBob said:
ASUS tech support would give me an RMA, BUT the big problem there is that since I put this awesome Skinomi cover on it, the sticker with the S/N had to go (hindsight is 20/20).
Click to expand...
Click to collapse
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Are you saying that Asus won't even initiate the RMA process because you don't know what the serial number is?
What about the box - do you still have it? The serial number is on the box as well...
I would *hope* that the Asus warranty doesn't need to have that stupid sticker in order to get warranty coverage!
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the quick reply.
I used to keep EVERY original box... and yes, I do remember the serial number being there, but the ONE TIME I need the serial number, and all it is is a flimsy sticker on the device itself... And the ONE TIME I don't have the box.
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
It also seems like they would have SOME WAY to just let the end user put back a stock bootloader on the device, then we would all save a lot of time! Other than the fantastic learning experience here, I really want to find a way to salvage this completely useless but fascinating piece of technology.
I wonder if NVidia could help with this... probably not. I guess I'll look.
There must be some way to get a stock bootloader back on my TF700!!!!
Wait a minute man can you boot on Fastboot mode? When you turn on with volume down you can choose the mode to start?
ScaryBob said:
I was able to get the RMA created, but I had to use the serial # of my second TF700. So now, the only way I can send it in would be to move the sticker. I have a funny feeling they'll just send it back saying that this is not the Droid we were RMA'ing for.
Click to expand...
Click to collapse
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
MartyHulskemper said:
Chance is high, for it is embedded in the system somewhere and I doubt they will let the opportunity slip to make you pay. Unfortunately.
As a previous replicant asked: does fastboot work? You could push over a new recovery.img then...
Click to expand...
Click to collapse
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
ScaryBob said:
Right, so if the serial# is etched in a tiny bit of truly ROM, why are they so hell bent on seeing the sticker... I'd gladly pay $50 for a program, blob, or special key sequence that can get me back to a stock bootloader. That would cost ASUS really nothing to provide in terms of loyalty to their brand and saving them countless hours in tech support.
No, I don't think fastboot works. I never get the "fastboot" message on the screen -- either it's stuck on "Booting recovery kernel image" with Power/VolumeDown or a blank screen with Power/VolumeUp (and then recognized with the APX driver). I've tried adb, fastboot, nvflash in both modes, and nada. Is one of those SUPPOSED to work in either of those scenarios? If so, I'll try again... it has now gone beyond the economics and is now in the realm of "the principle of the thing" or "I climbed the mountain because it's there". Plus, I'd really still like to have two operating TF700s.
Click to expand...
Click to collapse
I haven't heard of anyone coming back from where you are. I wish you luck. If you are able to recover somehow on your own, you will be giving this community a great gift by sharing your secret.
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Hi:
My tf700t is bricked, no fastboot, only apx after a bad CMW installation, is there any way to restore or re flash using the tools and obvious understanding that you guys have. I really don’t want to send the device back to asus, and will be willing to donate to your site / cause / developers account if you guys could assist me in this matter. Thanks in advance for your time.
jtrosky said:
Personally, I think I'd send it in for an RMA without any serial number sticker. Did anyone at Asus say that the sticker needs to be in place in order to get warranty coverage? Like you said, I'm sure that they can validate the serial number somehow. Even if you gave the wrong serial number by "mistake" when setting up the RMA, they should be able to tell that it's actually covered by warranty if they can get the serial number. If not, they you have nothing to worry about. So, either way, you should be fine!
Unless they specifically said that "no sticker = no coverage" (which I hope is not the case)...
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I suppose that is an option -- it's not doing me any good as a brick, the worst they can do is send it back.
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
danger-rat said:
I think you'll find that the serial number is probably identified inside the tab somewhere, anyway...
Click to expand...
Click to collapse
In the OP that was mentioned as well, but with the sidenote he didn't really want to open it up.
Mmmh... fastboot not working is not good... not good at all. I don't see any other option then than sending it back and see what ASUS does with it. As you said, the worst they can do is send it back... No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
MartyHulskemper said:
No, actually.... The worst they can do is repair it, permalock the bootloader and THEN send it back.
Click to expand...
Click to collapse
...and charge $380 for it (there was some quote in another thread).
_that said:
...and charge $380 for it (there was some quote in another thread).
Click to expand...
Click to collapse
No, that's if they do absolutely nothing but write a check. (In that thread, at least in my memory, nothing was even actually done on that 700. )
when you guys mean "bad CWM install" what exactly does that mean so we can make sure we can save a few extra souls from doom?
Im pretty sure that is when they install CWM through the Rom Manager app.
mj23kb24 said:
Im pretty sure that is when they install CWM through the Rom Manager app.
Click to expand...
Click to collapse
Yes, since a few days after release (at most), we've known that Rom Manager is not compatible with the TF700. That's why you do not see it in any tutorial. Failure to read before doing leads to bricks in very, very many cases, and the 700's case is no different.
As we've concluded before, in terms of OP relevancy, I guess that sending you expensive baby in anyway would we the way to go (now if you'd only have fastboot available...).
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
WoodenAnts said:
Hey guys, you bunch seem like a smart group, so I hope yous dont mind if i post my problem here as well. Its an odd problem actually. I have CWM, fastboot, all working on my infinity, but cannot for the life of me get it to boot anything. It hangs at the first Asus splash screen and wont move from there. Ive flashed various different roms and recovery always says its successfully installed, but when i reboot it doesnt move past the first splash asus screen. Any ideas, i kinda have exams this week and my notes are on my tablet stupid me. Cheers fellas.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
You need to provide some more info, are you on Jelly Bean or ICS? When this issue started? More details = higher chances to get help and solve your issue.
Lol sorry, i should know this by know. Was a long day. Uhh yes i was on a JB custom rom When the issue started. The rom had a couple hickups so i wanted to go back to my old one, so i did the nornal, nandroid, titanium backup, etc and flashed new rom. I believe what it did was delete the recovery image that it had, and then attempt to put on a new recovery as some roms do (to much annoyance) but this particular time it failed to install the new recovery for one reason or another. So i had no recovery for a while till i flashed it with fastboot, cwm 6.0.14 i think. So i tried doing a restore before this all happened, and recovery said it successfully restored, but when i reboot, it holds on the asus splash screen. Same with any Roms. And yes I wiped everything as well. Is that enough info?
Sent from my GT-I9300 using xda app-developers app
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
adelancker said:
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
Click to expand...
Click to collapse
Really just a guess ... but I think I have read something in other threads about MAC address and mainboard serial number not matching any more once the board has been exchanged. As far as I know, the unlock process contacts the Asus servers and does some kind of checking. I have read from others that had success in contacting Asus support and have them match all the items again.
Please take this with all care, just guessing here ... but maybe you can carry on your search in this direction.
adelancker said:
Hi all,
I sent my Infinity in a couple of weeks ago and after a whole lot of waiting I finally got my hands on it again today!
Sadly, as we all know, you get it back with a locked bootloader.
Usually that's not an issue but the Unlock Tool doesn't work for me.
I tried it a couple of times but no luck so far.
Do I have to revert to ICS to make this work or anything?
Or is there another trick/workaround to solve this issue?
Any help (*ANY* help) would be appreciated
Thanks
Click to expand...
Click to collapse
FordPrefect said:
Really just a guess ... but I think I have read something in other threads about MAC address and mainboard serial number not matching any more once the board has been exchanged. As far as I know, the unlock process contacts the Asus servers and does some kind of checking. I have read from others that had success in contacting Asus support and have them match all the items again.
Please take this with all care, just guessing here ... but maybe you can carry on your search in this direction.
Click to expand...
Click to collapse
This ^^ sounds about right -- I'm sorry, adelancker, but you're the latest in a loooooong line of TF700 owners who got their repaired device with a permlocked bootloader. (And to add insult to injury: I've never heard of anyone getting into contact with ASUS and resolving it -- although one guy tried three times over, and then reported he had contacts within ASUS now that could help resolve the issue. He was selling that unlock ability, but you had to pay a pretty amount in advance... Nice scheme, huh? ) Actually, I've heard of only three XDA-ers having it returned to them with the ability to unlock retained.
Man, this sucks. I really do feel sorry for you!
MartyHulskemper said:
This ^^ sounds about right -- I'm sorry, adelancker, but you're the latest in a loooooong line of TF700 owners who got their repaired device with a permlocked bootloader. (And to add insult to injury: I've never heard of anyone getting into contact with ASUS and resolving it -- although one guy tried three times over, and then reported he had contacts within ASUS now that could help resolve the issue. He was selling that unlock ability, but you had to pay a pretty amount in advance... Nice scheme, huh? ) Actually, I've heard of only three XDA-ers having it returned to them with the ability to unlock retained.
Man, this sucks. I really do feel sorry for you!
Click to expand...
Click to collapse
If this is true, this takes a whole lot of the joy of getting it back away!
Hopefully I will be able to convince them to set things straight.
I'll keep you posted, but I fear the outcome...
Any trick you know of that'll speed my infinity up, without going to custom roms?
I guess rooting should still be succesful? And then what? Install systemtuner, fstrim, browser2ram and see if that's enough?
Doesn't seem like I have an option here
adelancker said:
If this is true, this takes a whole lot of the joy of getting it back away!
Hopefully I will be able to convince them to set things straight.
I'll keep you posted, but I fear the outcome...
Any trick you know of that'll speed my infinity up, without going to custom roms?
I guess rooting should still be succesful? And then what? Install systemtuner, fstrim, browser2ram and see if that's enough?
Doesn't seem like I have an option here
Click to expand...
Click to collapse
Yes, rooting should still work -- I haven't really looked into the downgrade path options and if it requires a custom recovery, though. I'd root it if possible, and then tweak the hell out of it.
I fear as you do, but you might drop ASUS a line anyway -- you've got next to nothing to lose. Take care, and good luck!
I can post up a few build.prop tweaks but without a custom kernel you may still suffer.
Best thing you can do is update to 10.4.4.25 and disable all the asus bloat for now.
What has been said about the MAC address is correct. The success rate of people shipping their tablets into RMA to fix the MAC address issue does not seem very high. People are reporting they get the tablet back with the same issue regarding the unlock tool and unable to get the device tracker or OTA updates to work.
Email Asus support and flat out ask them to check the servers in Taiwan and find out if the MAC address listed in your tablet is the same one on the servers. They have the serial number already will just need you to supply the MAC address. If it comes back saying it is not and you need to RMA it, good luck. Question then becomes did the person responding to the email really check or just saying to RMA it so they can close out your email ticket.
The response I got last week was my tablet not matching what they have on the server and send it in. I'm debating if it's worth spending 15-20 bucks to mail it in, wait 2-3wks, only to get it back with them saying there is nothing wrong with the tablet and still be unable to unlock. That seems to be general outcome. In the email I explained I'm unable to use device tracker, receive OTA updates, or use the unlock tool. I explained the issues with MAC addresses for devices being incorrect on the servers in Taiwan as a known issue causing these problems. I supplied my MAC address that the tablet gives and asked to have them verify what they have.
Sorry to say but only Asus can fix this problem. If you search the forums for this topic you will find threads on it. Some had mentioned trying it with the sd card removed has worked. Give that a try. If you disabled the two tracking programs Asus has in their stock build, turn them back on when you try to unlock. Just keep trying a few times randomly and you might get lucky.
If I ever get my issue resolved I will for sure post in the forums for others.
We had already a thread for this, albeit for new devices:
http://forum.xda-developers.com/showthread.php?t=2146543
Mine works now.
The only success I have read about is 2-3 people asking Support to contact Taiwan / transfer the ticket to Taiwan as they seem to be able to correct the MAC in the systems.
After a week or so they fixed the MAC in their systems and the unlocking works again.
I have requested ASUS Germany to contact Taiwan 1,5 week ago but no luck yet. Still hoping they can work things out and I will keep on pushing.
sbdags said:
I can post up a few build.prop tweaks but without a custom kernel you may still suffer.
Best thing you can do is update to 10.4.4.25 and disable all the asus bloat for now.
Click to expand...
Click to collapse
Thanks! That's what I have done right now Except for the build.prop tweaks.
I can't do those all by myself
adelancker said:
Thanks! That's what I have done right now Except for the build.prop tweaks.
I can't do those all by myself
Click to expand...
Click to collapse
Wary of you doing the build.prop cos if you cause a boot loop you can't restore form recovery. You could reflash the full asus update though right? You comfortable with that?
Also don't forget to force gpu in developer settings.
DarkFire1985 said:
The only success I have read about is 2-3 people asking Support to contact Taiwan / transfer the ticket to Taiwan as they seem to be able to correct the MAC in the systems.
After a week or so they fixed the MAC in their systems and the unlocking works again.
I have requested ASUS Germany to contact Taiwan 1,5 week ago but no luck yet. Still hoping they can work things out and I will keep on pushing.
Click to expand...
Click to collapse
Be careful here - the problem is not always the MAC-address.
For my TF700, Asus had the correct MAC-address stored, but OTAs, Device Tracker and unlocking did not work nevertheless.
From my Logcat entries I saw that the server refused to 'talk' to my tablet, so I assume that the Asus server in Taiwan just didn't know my tablet.
The issue is fixed now BTW, Asus Germany forwarded the ticket to Taiwan.
So if you talk to Asus support, do not insist that the problem is the MAC-address - if your MAC address is correct and you still insist that it is wrong the Asus support won't take you serious anymore.
sbdags said:
Wary of you doing the build.prop cos if you cause a boot loop you can't restore form recovery. You could reflash the full asus update though right? You comfortable with that?
Also don't forget to force gpu in developer settings.
Click to expand...
Click to collapse
Already did! Checked force gpu, disabled all animations,etc.
Just doesn't match up to what did with CRomI
I'll first need to get root, but my tablet isn't recognising the EP201_768_SDUPDATE.zip as an update, I am afraid.
And without that, I can't even get root lol
By the way: I sent a mail to Asus, and they told me to send it in to get the unlock bootloader issue fixed.
Why on earth would they need me to send it in (once again!)?
adelancker said:
Already did! Checked force gpu, disabled all animations,etc.
Just doesn't match up to what did with CRomI
I'll first need to get root, but my tablet isn't recognising the EP201_768_SDUPDATE.zip as an update, I am afraid.
And without that, I can't even get root lol
By the way: I sent a mail to Asus, and they told me to send it in to get the unlock bootloader issue fixed.
Why on earth would they need me to send it in (once again!)?
Click to expand...
Click to collapse
To get that $125 from you a second time?
MartyHulskemper said:
To get that $125 from you a second time?
Click to expand...
Click to collapse
Hahaha ^^
They haven't charged me yet!
Maybe because I was super mega angry in my mail and mentioned the EU-consumer law a million times.
doesn't unlock and presumably void your warranty? I'm surprised they even let you send it in? Or are all of these instances non warranty repairs?
NegativeOne said:
doesn't unlock and presumably void your warranty? I'm surprised they even let you send it in? Or are all of these instances non warranty repairs?
Click to expand...
Click to collapse
What can I say? I am a good negotiator I guess...
Just kidding. If you're European, you can always use this EU consumer protection law, which always has your back for the first 6 months after purchase.
Well I'm just asking because I just got my tablet yesterday and am still deciding whether or not to unlock it.
It seems like asus is pretty nice about repairing unlocked devices though.
And no, I'm in the USA
NegativeOne said:
Well I'm just asking because I just got my tablet yesterday and am still deciding whether or not to unlock it.
It seems like asus is pretty nice about repairing unlocked devices though.
And no, I'm in the USA
Click to expand...
Click to collapse
If you're from the US, I can only recommend you to buy a third party warranty such as the Square Trade one.
After that, you can do whatever you want and you'll never have to worry about losing warranty after unlocking your tf700 ever again.
As a side note, unlock your device as soon as you have time! It makes your device that much quicker.
Just sucks that Asus somehow prevents me from unlocking it after the RMA.
So I just got a Zenphone6 and I'm following this guide to install LineageOS
https://wiki.lineageos.org/devices/I01WD/install
but got hold up at the "Unlocking the bootloader" step, because while running the app on the device it wanted me to agree to a number of terms and also connect to Asus to report my IMEI and possible other info. As I hadn't setup any network connection the app wouldn't proceed.
This disturbed me quite a bit, I've just parted with a fair amount of hard earned cash to buy a piece of hardware and it turned out I couldn't take full control of it.
So my question is, is there any way to sidestep the official unlocking tool?
No
Marlin79 said:
So I just got a Zenphone6 and I'm following this guide to install LineageOS
but got hold up at the "Unlocking the bootloader" step, because while running the app on the device it wanted me to agree to a number of terms and also connect to Asus to report my IMEI and possible other info. As I hadn't setup any network connection the app wouldn't proceed.
This disturbed me quite a bit, I've just parted with a fair amount of hard earned cash to buy a piece of hardware and it turned out I couldn't take full control of it.
So my question is, is there any way to sidestep the official unlocking tool?
Click to expand...
Click to collapse
I want to join this question, I really disappointed by such ASUS's policy. Too bad I can't give the phone back. If I wanted this kind of policy, I'd buy half priced Xiaomi.
By the way, have you tried 'fastboot oem unlock' command after allowing unlocking in Developer Options?
I don't see "Allow OEM Unlock" anywhere in Developer Settings.
Also interested in this. I figured since Asus is supporting devs, they would make unlocking as easy as Google/Oneplus does with their phones. Guess not.
Anyone tried this "unofficial" method?
https://forum.xda-developers.com/showpost.php?p=80113454&postcount=51
Satoso said:
Also interested in this. I figured since Asus is supporting devs, they would make unlocking as easy as Google/Oneplus does with their phones. Guess not.
Anyone tried this "unofficial" method?
https://forum.xda-developers.com/showpost.php?p=80113454&postcount=51
Click to expand...
Click to collapse
I took a plunge and got the phone, and this method doesn't work. Only the official one does, which as OP says will require an internet connect and probably does transmit the IMEI number and so on.
However, it doesn't require you to connect to a Google account as mentioned in the official Lineage instructions. So I guess that's a partial consolation.
Still, since Asus is in touch with the devs here, it would be great if someone can put forth a suggestion to drop this "phone-home" requirement. It's the only way they can compete with the more dev-friendly Oneplus.
I wish that there was a way. I really want to unlock the bootloader but I'm on the 10 beta and the official unlock tool does not work because of this. There doesn't appear to be a way to roll back to P either unfortunately so I'm stuck for now I guess