Related
Hello:
I sent my NEXUS in to SAMSUNG for a touch screen non-responsive on the left side issue. The tech stated there were no problems with my NEXUS S!
Upon turning it on, there is a padlock on the botton of the Google splash screen.
I called Samsung and the "level 3" tech said that my phone was now locked to T-mobile. I though that was BS.
Anyway what is it and, can I get it back to normal? My wife has the same phone and here does not have any problems so far.
I've attached a pic of the screen that shows the padlock. Thanks for the help.
Chiefdroid
that means your phone is unlocked as far as I know. I did my first unlocking and rooting of my nexus last night. When I went through the unlocking process, the "unlocked padlock" started to appear on my startup. If you hold "volume up" and the power button and turn the phone on. it should say unlocked on the fastboot screen...
You have unlocked the bootloader my young Jedi.
Sent from my Nexus S using XDA App
yup, unlocked bootloader.
thats not a bad thing, its a wonderful thing!
lol you rooted your phone and unlocked the bootloader. that is what that lock symbol means. did you forget, or not do this on purpose?
Thanks to all that replied!! I kinda figured that is what it was.. Like I said I didn't do it, the Samsung repair facility in Texas unlocked it. I called the Nexus S support line and the Level 3 tech said " When we reflashed your software, it locks your phone into the T-mobile network" and that was after she went down the hall and consulted with the "developers", Samsung tech support is a Joke. One day I'm gunna root this thing!
Thanks Again Guys.
And to the XDA moderator, sorry I posted in wrong section initially, rookie mistake..
Anybody know how to remove this lock symbol? How to re-lock the bootloader again?
soulja786 said:
Anybody know how to remove this lock symbol? How to re-lock the bootloader again?
Click to expand...
Click to collapse
fastboot oem lock
about op, what sensitive issue did you notice in your screen?
thiagodark said:
fastboot oem lock
about op, what sensitive issue did you notice in your screen?
Click to expand...
Click to collapse
Ive tried that but it doesnt work, I can reboot the bootloader via cmd but the above command has no effect? Any ideas why?
Thanks
soulja786 said:
Ive tried that but it doesnt work, I can reboot the bootloader via cmd but the above command has no effect? Any ideas why?
Thanks
Click to expand...
Click to collapse
several ideas, what error did it show? what is shown in device manager when you plug your phone in the pc in bootloader?
edit: how did you unlock it?!
Try this, these guys do a great job if breaking things down.
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Sent from my Nexus S 4G using XDA Premium App
thiagodark said:
several ideas, what error did it show? what is shown in device manager when you plug your phone in the pc in bootloader?
edit: how did you unlock it?!
Click to expand...
Click to collapse
When I go type in 'fastboot devices' or 'Adb devices' it says
"list of devices attached:" and nothing underneath it .....
I have tried updating drivers via PDAnet .... still nothing.
the drivers I have are 'ADB interface'.
Am I missing drivers specific for bootloader or something??
Basically, the phone wouldnt restore or factory reset, so I decided to root it? so I found a new '1 click root and recovery'.
Once I run the script, it unlocked bootloader and also reset my phone which worked great. Only thing I want to do now is remove the open padlock icon on the google screen (which I think is by re-locking bootloader) but when I put in the typical 'fastboot oem lock' nothing happens .....
Much appreciate the help, thanks.
You got to remove everything "custom" (cwm recovery, user roms etc) from the device before you can lock the bootloader again.
When you are trying to lock your bootloader it doesn't do anything because your device isn't correctly recognized by windows, this is prolly due to missing/wrong drivers (try uninstalling old ones and then follow the unlockr guide to rooting your phone/installing adb, http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/).
rentaric said:
You got to remove everything "custom" (cwm recovery, user roms etc) from the device before you can lock the bootloader again.
When you are trying to lock your bootloader it doesn't do anything because your device isn't correctly recognized by windows, this is prolly due to missing/wrong drivers (try uninstalling old ones and then follow the unlockr guide to rooting your phone/installing adb, http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/).
Click to expand...
Click to collapse
are you positive sure that i can't lock my bootloader with customs kernels, roms or recoveries? i don't think that's entirely true!
soulja786 said:
When I go type in 'fastboot devices' or 'Adb devices' it says
"list of devices attached:" and nothing underneath it .....
I have tried updating drivers via PDAnet .... still nothing.
the drivers I have are 'ADB interface'.
Am I missing drivers specific for bootloader or something??
Basically, the phone wouldnt restore or factory reset, so I decided to root it? so I found a new '1 click root and recovery'.
Once I run the script, it unlocked bootloader and also reset my phone which worked great. Only thing I want to do now is remove the open padlock icon on the google screen (which I think is by re-locking bootloader) but when I put in the typical 'fastboot oem lock' nothing happens .....
Much appreciate the help, thanks.
Click to expand...
Click to collapse
what is your phone 4g or gsm?!
I've got a Nexus S that got screwed up from the 2.3.6 OTA. It can go into fastboot mode and recovery mode but it will not boot into Android. When you try to unlock the bootloader you get the unlock screen, can select yes but when you press power the device just hangs. If you go into download mode you get a screen about unlocking the bootloader. Odin detects the device, retrieves the pit, sends the image you want to flash to the phone and the phone says image verified. Then it just does nothing. Odin just sits there and there is no other feedback on the device. It looks like if the bootloader is locked you cannot flash with Odin either. Or at least if the device goes into the strange unlock bootloader screen instead of the true download mode screen Odin flashes fail. I have searched and searched and cannot find a resolution to this problem. Has anyone figured out why some devices hang when you try to unlock the bootloader and has anyone found a way to work around this problem. I am trying to help a guy out and don't want to give him back his phone telling him there is simply nothing I can do for him. He has a TMO device in Thailand. Samsung service here will only service phones sold in Thailand through authorized channels. Since it has a TMO model number they won't touch it.
push clockwork with fastboot
tylerwatt12 said:
push clockwork with fastboot
Click to expand...
Click to collapse
Can't. Clockwork recovery image is sent to the phone. Then it says failed because bootloader lockaed, use "fastboot oem unlock" to unlock the bootloader. And on the phone it says something like Flash FailedState LOCKEDbootloader.
Without being to unlock the bootloader no image can be flashed. I even tried a stock boot image just for a test and it was rejected in the same manner. With the bootloader being locked down it won't let me flash anything. I would need a stock signed rom with android-info.txt and android-product.txt files. I have yet to find one. I think that would flash the phone.
Odin is a no go also. The images are pushed to the phone, the phone verifies the images and then doesn't flash them due to the bootloader being locked. And in download mode I don't get the shovel guy I get a screen telling me to unlock the bootloader but I am connecting in the manner that Odin can see and talk to the phone. The phone just refuses to flash the images once they are downloaded to it.
same for my nexus s,how to solve it?thx
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
splinter701 said:
I'm also having the problems here.
However, I simply cant get fastboot to work. It is continually stuck on 'waiting for device' (since the 2.3.6 OTA update).
I tried to flash an old 2.3.4 stock ROM I had on my SDcard, but recovery wont let me. ClockworkMod also cant be flashed because of the fastboot problem.
Yes, I checked that my drivers are up to date, I've tried using fastboot from both windows 7 and Ubuntu 11.04.
Click to expand...
Click to collapse
Do you mean getting stuck when you try to unlock the bootloader (fastboot oem unlock) or can you not even get into the bootloader at all.
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
maybe try on another pc?
splinter701 said:
I can get into the bootloader with "adb reboot-bootloader" or just holding the power and volumeup keys on. However, no fastboot commands work at all. My lock state = unlocked, but even though I have the superuser app installed, I dont have root access.
All the problems started when I foolishly applied the OTA update from 2.3.4 to 2.3.6.
Click to expand...
Click to collapse
Reinstall drivers?
Sent from my Nexus S 4G using xda premium
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
http://m.youtube.com/#/watch?deskto...e.com/watch?v=xwe4sWH67dk&v=xwe4sWH67dk&gl=US
Sent from my Nexus S using xda premium
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
splinter701 said:
Thanks so much YourMainDude! I usually avoid videos for instructions on this kind of thing, but this one was actually good.
For anyone who comes across this thread again, the tools you need seem to be in the SDK but do not work. The tools that work are at the website of the above video-maker (I cant post links yet, but if you search google for 'nexussrootnew.zip' the first hit should be the website nexusshacks.com)
I'll be installing cyanogenmod I think, since I'd rather that I never again have an OTA update from google.
Click to expand...
Click to collapse
=] your most welcome sir
Sent from my Nexus S using xda premium
YourMainDude said:
Had the same problem ... but there's a YouTube video where the guy shows how to root any nexus device... here's the link but view from the PC because within the video there's a link saying that this video is old and to click the box within the video screen
Also there should be a link that says Nexussrootnew ... click on it to download and extract it and move it to C drive... within the file Ull have the USB drivers superuser ... recovery. Once moved into C drive open Command Prompt and type:
>cd c:\Nexussrootnew "enter"
>Fastboot Device"s" < Forgot lol
>FastBoot OEM Unlock
Just Follow the step in the video and Ull be fine
"REMEMBER Watch Video Via PC"
link
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I tried this but it still requires bootloader to be unlocked so it didn't work. My problem is similar to OP's. My phone appears to offer the bootloader unlock option, but selecting 'yes' to unlock fails to actually unlock. So nothing else works to restore the ROM. Though the phone does accept commands from adb just fine.
Anyway, I'm just posting this in case anyone else has the the same issue w/ bootloader not unlocking.
Hi I just brought new nexus s phone from vodaphone Australia.and its network lock.please any one help me or guide me.so I am able to Unlock phone.
Thanks in advanced
Sent from my Nexus S using XDA App
i found solution now
unlocking the Bootloader
Warning: Unlocking the Nexus S's bootloader will void the warranty.
If the Bootloader on the Nexus S has already been unlocked, you may skip this section.
You will need fastboot on the computer to unlock the bootloader on the Nexus S. Follow the Android SDK guide, to get the fastboot on the computer.
Power the Nexus S down, and hold Volume Up & the Power button until booted into the bootloader. You should see a white screen with three skating androids.
Connect the Nexus S to the computer via USB.
On the computer, open terminal and run:
fastboot oem unlock
On the Nexus S, a prompt will open up asking you if you are sure you want to unlock the bootloader and again warning you that doing so will void your warranty. If you agree to these terms, press Volume Up to select Yes, and then press the Power button to confirm.
NOTE: Unlocking the bootloader wipes the device.
The Nexus S will reboot.
Installing the ClockworkMod Recovery Image
If you have already flashed a custom recovery image, skip this section.
Download the latest version of the ClockworkMod Recovery:
ClockworkMod Recovery 5.0.2.0: Download
Place the ClockworkMod Recovery Image in the same folder as fastboot (the /tools folder with the Android SDK folder).
Power the Nexus S down, and hold Volume Up & the Power button until booted into the bootloader. You should see a white screen with three skating androids.
Connect the Nexus S to the computer via USB.
On the computer, open terminal and run:
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
The ClockworkMod Recovery should now be installed on the Nexus S.
Ref-http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Thanks to XDA and everybody who help me to solve this problem and hope this guide help new bee like me on
The Nexus S should not be network locked. It may not run on all frequencies (from Voda AU, most likely 850mhz), because it was not made to.
What makes you think it is network locked?
I did try to other sim and not working. And I call customer care they told me its locked to vodaphone n only work on vodaphone network.if u want to unlock then you have to pay money......any help???????plz new to nexus forum
Sent from my Nexus S using XDA App
I too have a aus vodafone nexus s. When i unlocked bootloader and rooted it, it was sim unlocked.
I've not heard of a single case where the sim was locked on a Vodafone AU Nexus S. A locked phone would tell you the sim card is not compatible, did any error message come up?
Also, try a different sim card from another company.
How u unlock bootloader n root can u guide me
Sent from my Nexus S using XDA App
My Nexus S i9023 came with GB and a T-mobile simlock. (no branding) After rooting and installing a custom ICS ROM (NexusBeam at the time) it accepts any SIM...
aadis said:
How u unlock bootloader n root can u guide me
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Dev section and general section , there are dozens guides
i rooted and unlocked bootloader form http://www.nexusshacks.com
Ok, so i've read up that your able to fastboot a new recovery, but i havnt been able to find a link with a stock recovery kernel.
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Bootloader (1.00 e) released by "WW_epad-10.4.4.20-20121026" A03
The story is i've bought it some while ago of course, and its been lieing around on the table for a few months.. Basically busy life and other ****. Yesterday i looked at it and was, oh right! Turn it on, and it bootloop on me, apparently common issue with a JB version. herpaderpa on android but fck that..
And when i use a update file on the sd card, i cant install that to update the stock firmware due to the dead droid with the triangle..
From what i can gather around, if i have fastboot option, then its unlocked ? Yes, no ?
If so, could anyone give a hint as to whut the duck i've missed when reading the big full guide thread on the infinity Im starting to become rather desperat. Never had this kind of behaviour with my android devices before, Sure a goofed usb driver for fastboot here and there.. But never a dead droid with triangle..
SOLUTION :
Follow this chaps guide http://forum.xda-developers.com/showthread.php?t=1755576
using his alternative method, and at step 2.
DO AS HE WRITES! Using upper case letters on the file your moving to the sd card, EP201_768_SDUPDATE.zip as such! It works!
My droid kept showing up dead, untill i changed to upper case letters... Then the darn thing came to life!
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
_that said:
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
Click to expand...
Click to collapse
In that case, how can i go about bringing my tablet out of this infernal boot thing? I've tried flashing the twrp kernel, but i dont see any change, when i sent the flash it dit get a blue bar on the bootloader indicated full. So i assumed it could send the loader..
Basically i just want to firmware upgrade with the latest stock firmware, But i tried dumping the file on an sd card, and then go into the bootloader But it did not recognize it and start an update. also i couldnt go into the RCK selection, due to the dead droid.
What exactly did you do, exactly which file(s) did you try to flash, and what exactly happened? And does "I couldn't go into the RCK selection" mean that you never see the bootloader menu, that it doesn't work, or that you don't know how to use it?
Ok, basically, when i start the pad, it never goes beyon the ASUS screen.
Im able to get into the bootloader, here i have 4 icons, RCK, Android, USB, Wipe Data.
When i select RCK it brings the dead droid after a droid thats working.
If i enter USB i can use fastboot. What i've tried here is to do the http://www.teamw.in/project Twrp recovery using http://forum.xda-developers.com/showthread.php?t=1833212 guide *** Custom Recovery Installation ***
However i dont think that it ever was sent to the tablet. Not sure.
I know how to move around in bootloader power + volume down = mennu, then tap the volume to switch between icons, and the other volume to select.
Power + other volume = AXP iirc in stead of bootlaoder.
Did not try to flash any files when the dead droid thing / bootloop started. I basically did an OTA update iirc to a newer version a good while ago. And then life became fcked for me for a periode so playing with the tablet wasnt really an option for enjoyment. It then drained of battery of course, and here now after having it charged up. i realise about this odd bootloop for one of the older droid software versions.
theorion said:
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Click to expand...
Click to collapse
_that said:
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on.
Click to expand...
Click to collapse
Do you already know if your device is unlocked?
_that said:
Do you already know if your device is unlocked?
Click to expand...
Click to collapse
No, it does not say unlocked any where
theorion said:
No, it does not say unlocked any where
Click to expand...
Click to collapse
OK, that explains why installing TWRP didn't work.
Now if you would describe in detail what you did to install the latest firmware, maybe someone could tell you why that didn't work.
Did you unzip the downloaded firmware update once (the result being another zip file)?
The unzipped zip is what you have to put on your sd card. Then the recovery should recognize it when you boot.
If that does not work, try to rename the unzipped zip: EP201_768_SDUPDATE.zip
and put that file into the root of you sd card.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
1. Downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.8 Only for WW SKU (Android 4.2.1) from the TF700F download page selecting android as os.
2. Have a 2gb microsd, i formated as fat 32, using all standard alocation and stuff with windows' own formatting tool.
3. I unzipped the downloaded ZIP file so i have a WW_epad-user-10.6.1.14.8.zip that now contains a meta-inf folder, and a blob file.
4. renamed the zip file to ep201_768_sdupdate.zip, however i did use lowercase... Could that be the issue ? Basically i presumed that the uppercase was only to make people aware of a change.
5. boot the device using the power + volume, and enter recovery mode.
6. Dead droid..
Update as i was writing this, i thought, though it wasn't said specificly, i renamed the EP201_768_SDUPDATE to uppercase, and decided to give that a go.. Now the droid is working its ass off...
F**** i feel like a complete bloddy retard! Gawd i hope it works now then...
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
theorion said:
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
Click to expand...
Click to collapse
Oh yeah, Linux is case sensitive alright. Get the case wrong and it has no idea what you talkin' bout Willis.
Ladies and Gents,
Received a tf700t from a friend who dabbles without reading. Not me, I swear! I've looked around and don't see an obvious lead so I will outline my situation and hope:
- Got a tf700t from a friend.
- He only gave it to me because he "attempted to flash a custom rom after unlocking the bootloader... and something else" without backing up blobs.
- Attempting to boot normally results in: "device is unlocked" screen... forever.
- Boot with Power+Volume_down results in:
"device is unlocked.
android cardhu-user bootloader <2.10 e > released by 'US_epad-9.4.5.26-20120720' A03
checking for android ota recovery
booting recovery kernel image"
- Can't seem to get device recognized by fastboot or adb.
Any guidance would be appreciated.
PS. XDA needs an additional 'post icon' wich looks like a brick with a ? on top of it
Thanks,
Sockky
You got a tablet with an ICS bootloader. If your friend tried to flash anything current - no wonder you're in a stuck boot....
Now the questions is: Did he flash a custom reocvery? And if yes - which one?
So boot to the bootloader menu (you should have 4 icons), use Volume Down to highlight RCK and Volume Up to enter recovery.
If you get an Android keeling over with an open belly you have the stock recovery. If not, the custom recovery should boot. Note name and version.
If you have a custom recovery you can use it to flash a current bootloader. If you have the stock recovery you have to manually flash the Asus firmware to get you current.
Post your answers and we take from it there.
berndblb said:
You got a tablet with an ICS bootloader. If your friend tried to flash anything current - no wonder you're in a stuck boot....
Now the questions is: Did he flash a custom reocvery? And if yes - which one?
So boot to the bootloader menu (you should have 4 icons), use Volume Down to highlight RCK and Volume Up to enter recovery.
If you get an Android keeling over with an open belly you have the stock recovery. If not, the custom recovery should boot. Note name and version.
If you have a custom recovery you can use it to flash a current bootloader. If you have the stock recovery you have to manually flash the Asus firmware to get you current.
Post your answers and we take from it there.
Click to expand...
Click to collapse
Very much appreciate the response.
- What recovery, I can't tell and I'm pretty sure he won't be able to either. I will assume cwm because of popularity.
- When I "power+volume_down", I am presented with the aforementioned "android cardhu-user(2.10 e) ... " message. I don't get any sick android (keeling over) or any other option.
Thanks again and anxiously awaiting your reply!
Sockky
sockky said:
Very much appreciate the response.
- What recovery, I can't tell and I'm pretty sure he won't be able to either. I will assume cwm because of popularity.
- When I "power+volume_down", I am presented with the aforementioned "android cardhu-user(2.10 e) ... " message. I don't get any sick android (keeling over) or any other option.
Thanks again and anxiously awaiting your reply!
Sockky
Click to expand...
Click to collapse
Ummm - on that screen with your bootlaoder version. You don't have 4 icons? RCK, Android, USB and Wipe Data?
berndblb said:
Ummm - on that screen with your bootlaoder version. You don't have 4 icons? RCK, Android, USB and Wipe Data?
Click to expand...
Click to collapse
I only get the message, as quoted in the top left of the screen, with the asus logo in the middle "ASUS, inspiring inovation...". nothing in terms of options.
Thanks,
Sockky
So I've led myself to 'https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/' and outlook looks positive except for the fact that I can't get to the point of "Checking for RCK image".
It would be beautiful if I could get some fastboot love on this thing. Drivers working on windows and same thing on linux.
"fastboot devices" returns nothing.
sockky said:
So I've led myself to 'https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/' and outlook looks positive except for the fact that I can't get to the point of "Checking for RCK image".
It would be beautiful if I could get some fastboot love on this thing. Drivers working on windows and same thing on linux.
"fastboot devices" returns nothing.
Click to expand...
Click to collapse
It is apparent to me that I'm going to need access to fastboot in order to move forward and that doesn't seem to be an option at this point. Given the notes I've posted on my bootloader, does anybody know of a way to recover/restore fastboot access? I'm beginning to think there is no hope for this device...
sockky said:
It is apparent to me that I'm going to need access to fastboot in order to move forward and that doesn't seem to be an option at this point. Given the notes I've posted on my bootloader, does anybody know of a way to recover/restore fastboot access? I'm beginning to think there is no hope for this device...
Click to expand...
Click to collapse
It can be very difficult to get fastboot to work with a borked tablet. What did you try?
Android SDK? The 15 second ADB tool? Minimal adb fastboot tool?
Are you using the original cable?
A USB 2.0 port, not 3.0?
The problem is on ICS you ahd to select the USB icon from the bootloader menu to get to fastboot mode - and you don't seem to get to that screen...
Sorry, wish I could be more helpful....
berndblb said:
It can be very difficult to get fastboot to work with a borked tablet. What did you try?
Android SDK? The 15 second ADB tool? Minimal adb fastboot tool?
Are you using the original cable?
A USB 2.0 port, not 3.0?
The problem is on ICS you ahd to select the USB icon from the bootloader menu to get to fastboot mode - and you don't seem to get to that screen...
Sorry, wish I could be more helpful....
Click to expand...
Click to collapse
I used Android SDK from a windows machine as well as a linux mint machine. I use both of these machines regularly for this type of thing so I don't think there is an issue with either environment.
Is there any way to do a factory-default type thing via aix mode? I can actually get the device in this mode -just not sure if there's anything I can do...
Yes to original cable and usb 2.0.
Thanks again... really appreciate it. This device is very new and shiny -I wonder if the cost of getting asus to fix it would be greater than grabbing one from ebay...
sockky said:
I used Android SDK from a windows machine as well as a linux mint machine. I use both of these machines regularly for this type of thing so I don't think there is an issue with either environment.
Is there any way to do a factory-default type thing via aix mode? I can actually get the device in this mode -just not sure if there's anything I can do...
Yes to original cable and usb 2.0.
Thanks again... really appreciate it. This device is very new and shiny -I wonder if the cost of getting asus to fix it would be greater than grabbing one from ebay...
Click to expand...
Click to collapse
You may be in luck since you're on a pre .30 bootloader. The nvflash thread you linked to earlier was for JB roms. You are still on ICS. Check this out: http://forum.xda-developers.com/showthread.php?t=1901479