Database Info

[Q] I think I killed my Nexus S! Please help! (unlocking process/rooting stuff)

So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!

I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.

nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.

OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?

nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!

Edit: nvm. >_<

kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!

nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..

OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?

http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.

skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness

mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?

Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?

skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img

kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!

skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.

nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.

Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.

nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.

[Q] My Asus TF300T is on stock Android 4.0.3, what to do next?

The darn thing just started nagging me with an update notice that comes back every ten minutes. I read somewhere that updating is going to stop me from doing certain advanced things, so I finally got the last push to go for either CM10 or CleanRom, depending on which one gives me the most advanced and pleasant experience.
But before doing so, it's recommended to get some kind of flash info file or something from it that doesn't come out when upgraded to the latest firmware but does on the old 4.0.3. What would be the best way to go from now on?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

Found something myself, thank me very much!
http://androidroot.mobi/t3_nvflash/
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

do yourself a favor if you gonna go with a custom rom, Energy rom and TWRP recovery!

What are their advantages when compared to CM10 or Clean?
Sent from my Galaxy Nexus using xda app-developers app

This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...

Lex_Michdeandroid said:
This is really annoying... The guide I found really isn't n00b-proof. I have to figure everything out from scratch here. I hate this as much as I love it...
Other helpful stuff I found:
http://www.youtube.com/watch?v=J3ypzUaKxvo
http://forum.xda-developers.com/showthread.php?t=2034866
Going to edit this post along the way to help me remember what I did...
Edit:
Got the APX drivers installed, but now the device isn't getting the USB icon when I go into Fastboot... Wish me luck...
The Universal Naked stuff does not install ADB drivers for me...
Edit2:
So I tried the 'Have disk...' option, now I got to install ADB drivers. Used the Prime drivers, I hope these are the right drivers. The thread below got me to do this:
http://forum.xda-developers.com/showthread.php?t=1830108
Went and installed JDK and SDK as shown in that thread. Because (no **** sherlock) you need ADB stuff to use ADB stuff.
Edit3:
This is really pissing me off and I give up... It says I already have installed ADB, but ADB is nowhere to be found. I guess I'm an idiot and I can't figure this out on my own, time to go to bed. I hope someone with intelligence drops by here in the meantime. Thanks in advance...
Edit4:
I lay here wondering, is my bootloader unlocked? How can I check? Does this have to be unlocked before I go and try the link I posted in my first reply? Stupid questions of course, but I'm learning here...
Click to expand...
Click to collapse
Your tablet will say it is unlocked in the upper left part of the screen when The Asus logo appears at boot.
Sent from my Transformer Pad TF300T using Tapatalk HD

Hi, if your tablet is still on stock 4.0.3 (ICS bootloader), I recommend doing NVflash first
http://forum.xda-developers.com/showthread.php?t=1894867
If you have already updated to JB bootloader it won't work.

It doesn't say Unlocked, so I guess that's why I don't see the USB option when I try to get into Fastboot?
I'm also not able to get ADB commands recognized on my win7x64... Am I doing it wrong? What's the proper method/order of events here? Isn't there a really n00b-proof version of a guide here, or is it something I should write as soon as I get out of this mess and get it working?
Sent from my Galaxy Nexus using xda app-developers app

Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596

pjc21 said:
Have a look here for ICS bootloader unlock tool
http://forum.xda-developers.com/showthread.php?t=1667596
Click to expand...
Click to collapse
Perhaps I'm not really looking in the right location, but the Asus website says I need to choose an operating system and gives me no option to choose. This way I'm not able to download the apk...
Edit:
Tried clicking the links with the tab and it started the download... Device now has an unlocked bootloader. On to the next one...
Edit2:
Ah, now I get it. Pay attention to where that Android SDK stuff is being installed. Mine got installed in the folder I unpacked the installation files! So somewhere 256 folders deep on the Desktop was the right 'adb.exe' file. Make sure the tf300_nvflashpack files are in the same directory and open the command prompt there. After that I got back to the http://androidroot.mobi/t3_nvflash/ website and entered the commands. One moment please, back in a flash!
Edit3:
Now I have 5 files in /mnt/sdcard/AndroidRoot and I uploaded them to my Dropbox. I'm guessing they are the right files...
blob.bin
blob.log
bootloader.ebt
create.bct
recovery.bct
To be sure I uploaded them all.
Copied these files into the SDK folder, along with the other zipped files for nvflash so the nvflash command works to get the other three backup files.
Edit4:
Went on following the guide and checked the video to see if I was really going the right way. Finally I have all files backed up. Goddamn what a journey, but it makes you grow a pair of balls. Now on to the next hurdle, getting a proper ROM, because stock is really getting on my nerves.
So CleanRom, CM10 or Energy ROM? Should I first upgrade to JB? Without or with the popup I'm constantly getting?

Lex,
You have alot of the same questions I do/did, and I have your original post open in another window to respond to all your questions. I'm working on writing a guide for all this stuff so this is rather helpful. If I respond to a question twice, please forgive me as I'm literally just going down the list and answering em as I read em.
In your first post, the file you're referring to is gathered via NVFlash. I haven't used NVFlash yet, but what I understand is that if you use this tool it basically backs up your ICS (4.0.3) bootloader information. The newest firmware change is to Android Jelly Bean (4.1.1) and that re-locks your bootloader. Once you go to JB, you cannot go back. So this servers as a backup (again, this is just how I interpret the information from their website. I don't know how correct my interpretations are, and have actually opened a thread to ask for clarification about this program).
For the drivers, all I did was download the android SDK and install the 'android tools' and "extra - google drivers' from the list. My laptop was just recently wiped-out so I have no prior drivers installed, nor have I connected my tablet to my computer yet (just got a replacement tablet last weekend). I didn't use the universal driver or any other add-ons. Just use the SDK, it will install drivers, and then it will detect your device. I verified this by typing "adb devices" in command prompt and it detected the serial # of my device.
Within that same post, you had some confusion about ADB. It's just an executable, and you have to use the command prompt window from whichever directory it is installed to. So once you unzip the Android SDK or wherever you installed ADB to, use the command line commands "cd directory/where/adb/is/installed" to navigate to it, or use shift + right click within that folder and it will have an option to "open command prompt here" with admin privileges. That makes life a bit easier. Other people also install their SDK to C:\android\SDK or something similar, so it's less to type.
In order to determine if your bootloader is unlocked, look at your tablet in the top left hand corner when it boots up. It will say "Device is unlocked" and list a bunch of numbers (which if I remember correctly would just be the firmware information). Your device will not be unlocked until you actually download the unlock tool from asus' website and push the file via adb to your tablet and install it. That is, you have to take a very specific, very advanced overt action to unlock it. Nothing else and no one else can do it for you nor can it be done accidentally.
Next post (#8 in the thread): You are correct that fastboot will not show unless you are unlocked. I just verified this on my not-unlocked, not-rooted new tablet, and cannot enter fastboot mode. Your ADB commands wont work if your drivers are not correctly installed.
Post #10: You have to select "Android" under the OS drop-down box to find the unlocker app. As for the location of the ADB.exe, mine was found in this subfolder within the android SDK: <whereveryouunzippedit>\Android SDK x86_64\adt-bundle-windows-x86_64\sdk\platform-tools
That folder contained the correct (and I think only) adb.exe I needed.
For your last part, I think you should try out a number of ROM's to see which you like best. I've tried all the major ones (CM9, CM10, CleanRom, Hydro, Blackbean, and some of the stock rooted/de-odexed) ROMs and used Blackbean for the longest time because of how slick it looks (all black) and how easy it is on my eyes.
Make sure you document the steps you took so you can remember them in the future. I'm working on writing a guide right now and documenting my steps to go from a stock, locked, and not-rooted tablet to a rooted unlocked and custom flash tablet.
I really hope I was able to clarify some things. I am by NO MEANS an expert but I've spent many hours experimenting and think that I wish I had someone to answer my questions when I was first learning, rather than learning by mistake.
Hopefully this helps,
Opethfan89

Hi, I use Energy rom which I find pretty good, you will need to update to JB first as Energy, CM10 & Clean rom are all JB bootloader compliant. My tab came with JB pre installed so not sure what the best way to update is but would assume since you still have stock recovery would be with OTA update (popup notice). Here is a guide to update to JB but I think this is if you have already installed a custom recovery as it looks like you flash back to stock recovery first, thats why I think if your getting update notice and still have stock recovery, go with that.
http://forum.xda-developers.com/showthread.php?t=1845377
Once you have updated to JB stock here is a guide to install custom recovery (CWM or TWRP), root & install custom roms.
http://forum.xda-developers.com/showthread.php?t=2041627
Here is link to TWRP recovery (I had issues with CWM).
http://forum.xda-developers.com/showthread.php?t=1672108
Hope this helps.

opethfan89 said:
Lex,
You have alot of the same questions I do/did,
[..]
Hopefully this helps,
Opethfan89
Click to expand...
Click to collapse
I can only click the thanks button once, but I clicked the f- out of it that one time. Although I already got to the point where my stuff is backed up, it is really good for my/our fellow adventure-seekers to have an answer to these FAQuestions. It's awesome you took the time and effort to type that much words to help out someone you don't even know. Thanks again!
pjc21 said:
Hi, I use Energy rom which I find pretty good,
[..]
Hope this helps.
Click to expand...
Click to collapse
Same goes for you! Tomorrow I will be trying as much ROMS as I can to see which one suits me best. Also repeating this process is the best way to learn something and since I'm unbrickable, I am going to flash the hell out of it for a few days. I'll try to post my steps and findings here so I (and perhaps others with the same trouble) can benefit from it in the future.

Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:

pjc21 said:
Also I think when you update to JB your bootloader will be locked again (new bootloader), the above guide on root, customs roms also has info and links on unlocking JB bootloader. Glad I could help, have fun :good:
Click to expand...
Click to collapse
It's upgrading now. Of course I forgot I lost root with the last OTA update and I forgot to make sure I rooted the thing so it was able to use the rootkeeper after upgrading to JB. I hope there is some documentation on rooting JB, because at the time this all happened root was not possible yet. It's past 1 AM over here, so I guess it's best to save this quest for later when I had some sleep.
Edit:
Just for kicks I tried 'Root Checker' and it said 'no root'. Then I saw 'Rootkeeper' was installed. Opened it up, tapped the restore button... Device rooted! Guess my memory is really failing big time... One down, # to go.
Edit2:
Installed TWRP:
Just downloaded the .blob from their website and
put it in the platform-tools folder.
Then renamed it to TWRP.blob.
Turned off tablet,
plugged in USB cable in the tablet ONLY,
hold volumeDown button,
plug into laptop holding button,
waiting...
choose USB logo,
open cmd-line in the platform-tools folder,
run command: "fastboot -i 0x0B05 flash recovery twrp.blob"
waiting...
Done. Let's see if it works...
Edit3:
At first I didn't understand how to get into TWRP (DOH!),
Hold volDown, power on, choose RCK.
Edit4:
Been having a fight with TWRP when I try to install CM10.1 (latest nightly: 20130121). Gives me an error status 7 or something...
Code:
Verifying update package...
assert failed: getprop("ro.product.device") == "tf300t" ||
getprop("ro.build.product") == "tf300t"
E:Error in /external_sdcard/CROMS/****.zip
(Status 7)
Error flashing zip ' /external_sdcard/CROMS/****.zip'
Of course, ****.zip is a long filename I didn't want to type completely here.
Will try to figure out whats wrong later today, first I'm going to try restoring the backup I made earlier, just to see how a complete backup works when the tablet is wiped back to factory settings.
Edit5:
The backup stuff is really cool! My tablet is back the way it was even though I wiped it completely!
Back to the ROM rumble... baked_tf300t_blackbean-6_jb-bl_b6.zip gives me the same error. Starting to get annoyed again... Let's try something different, CleanROM. Download is taking ages... I'm restoring again, so I can use the tablet for the rest of the day. As soon as I feel like it I will try again, for now I'm giving it 'the finger'.
Edit6:
Cleanrom is installing now. I guess CM (baked is CM based right?) was causing some trouble...
Done installing...
Wipe Cache/Dalvik...
Reboot...
Android is upgrading...
Might need to choose the small font, my screen is really clogged up with stuff. Didn't expect to keep my settings etc., thought it would be completely wiped. I'm going to restore and then reinstall with the highest DPI setting first, then I'll wander around the rom to check if I like it.
Edit7:
I think I'll stick with this one for a few days, runs fine if you ask me, maybe take the time to finally update my Galaxy Nexus to CM...

Lenovo IdeaTab A2107A-F

I am starting this thread to hopefully encourage discussion on the Lenovo A2107A-F tablet variant.
I am aware there is an existing thread on the A2107 here:
http://forum.xda-developers.com/showthread.php?t=1982334
but that thread is concentrating on the A-H (dual sim + wifi) variant which is somewhat different from the A-F (wifi only).
So far I have not found any custom rom development, which is disappointing as the stock rom leaves a lot to be desired IMHO. While the current OTA update is fine for web surfing, reading emails etc, HD video playback (particularly YouTube HD) is very poor. Also the recent OTA update forces an optimization of apps on bootup which leads to long boot times
You can root and install CWM by following steps 1-5 from the 1st post here:
http://forum.xda-developers.com/showthread.php?t=2044496
Note that "-Update 3-" mentioned in the post does not appear to work for the A-F model!
So, has anybody any leads on possible development on this tab?
Any tips on improving performance?

My first tip:
If after installing CWM you cannot get to the CWM recovery screen after powering down the device, look for for the file "/system/reboot-from-recovery.p". If it's there, either delete it or move it to some other place. This file restores the default recovery on a system reboot.
I got bitten by this a couple of times

Thanks for starting a separate thread for the A2107A-F. I'm new to Android devices and just got this one two weeks ago. I'd like to get rid of several of the apps that I have no use for and from what I understand that means I have to root it. I got lost in the details of the other thread, but I tried reading all of it. I'm on Vista and somewhere along the line I installed one of the suggested ADB drivers via PDAnet. Device Manager is showing Android Phone and under that Android ADB Interface. I wasn't sure if that matched closely enough with the step-by-step threads since I don't really think of the device as a phone, so I've been holding off on going further. I've tried using a few other drivers that were suggested in the large thread and some other threads, but Vista always tells me the current driver is the most up-to-date one.
Do you know if it's okay for it to say Android Phone rather than something else?
Thanks. I've got some other questions about the specifics of some of the other steps, but this is probably enough to get started.

My apologies in advance if my posts are too long and my questions are too basic for these forums. Feel free to point me somewhere else based on what I'm asking for. I'd honestly appreciate any leads towards my goal of getting rid of the bloat on this device and making it more responsive. (Wow! The portrait to landscape lag is really bugging me now after reading around here).
Anyway, my primary purpose is to remove the seemingly unneeded programs, services and widgets that come with the tablet. Maybe I'm just ignorant about these things, but at this time things like messaging (IMO), mapping, and some of the other default features are of no use to me. They seem to be eating up a lot of resources. I can kill some of the services I think they are associated with, but they keep popping back up.
I did watch the "noob" video (color me a tiny ant to be squashed) and did try to search for an answer to get me even started. I've read the huge main A2107A thread (80+ pages) and tried three of the suggested ADB drivers with my Vista 32 setup for my A2107A-F. The only one that even seemed to connect was ADPnet and it showed the tablet as a Android Phone. Maybe I'm just too paranoid, but after the multiple "brick" posts I'd like to make sure I'm on the right path before trying to "root" the device which appears to be the first step in removing all the extra stuff Lenovo added.
Not that it matters, but I've had the tablet for almost two weeks now and my favorite things are Slacker Radio, Scrabble, Roll It and Zen pinball. I do play Words with Friends with my wife, but I don't like it since some of the words they allow are not valid in Scrabble (which I used to play as an expert competitively face-to-face).
If you are so inclined, feel free to PM me for a Scrabble game. I promise I will not use anything other than my brain and the built in dictionary to make my plays. (I'm a bit rusty since I gave up competitive Scrabble in 2006).
So, long story short... Thanks in advance for any and all advice you can give on slimming down the Lenovo A2107A-F. And if you want an honest Scrabble challenge feel free to PM me.

As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root! You need to make that USB debugging is turned on on your device you have an entry in the device manager for ADB Interface (expand on the device which you have showing up).
I am no expert, and I struggled with this on my first go also
Once rooted you can then install Titanium Backup from the play store and use it to get rid of the bloatware! Proceed with caution however as it is possible to remove critical system apps!

degsie said:
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root!
Click to expand...
Click to collapse
Thanks! That's the type of test suggestion I was looking for to make sure I was on the right path with the driver.

So has anyone tried creating a rom for this tab yet? I've been doing some research into porting another rom to work on the A2107A-F, but want to make sure there isn't one already.

I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app

ssenemosewa said:
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
Click to expand...
Click to collapse
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!

Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?

ssenemosewa said:
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
Click to expand...
Click to collapse
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".

Kevin147 said:
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Click to expand...
Click to collapse
Although I have my A2107A rooted and tweaked to my satisfaction, there are a few lingering issues that I'd hoped an update would correct:
1) The neutered Bluetooth stack. The tablet is supposed to work with Bluetooth keyboards, mice, etc. It doesn't. Although I've gotten it to talk to an external GPS module, other Bluetooth data connections simply will not work. Oh, and Bluetooth audio? Forget about it!
2) Some settings that are present in stock ICS builds are just omitted in this one. As an example, the ability to specify a default TTS voice. It's present under settings in my wife's tablet and every other ICS build I've ever encountered. Not this one!
Sent from my IdeaTab A2107A-F using xda app-developers app

Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I was rooted too, lost root access (only with some apps!) after the 130221 update Feb 28. I'll try the same root procedure as before to see if I can get it back. Glad to see a thread on the popular US version A2107A-F. Maybe someone will port Jelly Bean to this tablet! Doesn't appear Lenovo wants to do it...
Rob

I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?

degsie said:
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
Click to expand...
Click to collapse
I'm in exactly the same boat as you. I'm getting the same exact error. except that I do not have CWM installed (I am rooted though). Perhaps there's a problem with the update.zip?
Something odd that I noticed however: After the tablet reboots into recovery mode, the update fails, and I go to browse for the update.zip, the sdcard/googleota directory is missing (along with everything that follows it alphabetically). They reappear upon normal boot. I've tried copying it to a directory closer to the beginning of the alphabet and it does show up while in recovery mode. But it still will not install.
Maybe I somehow do not have the available space to perform the update? Is that possible? I show plenty of available space on both sdcards. Could we somehow be below a certain ROM space threshold necessary for an update?

I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...

degsie said:
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
Click to expand...
Click to collapse
Well, I am running a stock rom. I am unwilling to "mess with success" until there's a 100% reproducible way of recovering if it fails. And, so far, everything I've read in the other A2107A thread has been hit or miss for the A2107A-F people.
Anyway, If the update is performing a verification test, then it my "virgin stock ROM" should certainly pass it. The only thing that I did is to root it. Hmmm...could the update be testing for that and refusing to install if it detects a rooted device? I would tend to doubt that, since the previous ota update went just fine. I lost root in the process but easily reapplied it afterward.
Thoughts?

Interestingly, I flashed the A2107A-F_S483_121115 rom (again, found in another thread) as I was having verification problems with the OTA update just released from lenovo which was available from the A2107A-F_S484_121211 flashed rom. While the S483_121115 rom appears to be older, I no longer get the option to update via OTA as the tablet is telling me that my s/w is up to date! Go figure.

It's really too bad this device hasn't taken off. If I actually knew how to dev then I would start developng ROMs for it. I'm enjoying it now that I have root and got rid of bloat.

Hey guys. Just wanted to say if someone can send me a stock rom and be willing to test, I'll try to do up a good rom for the -f models. I'd use mine for the stock rom, but I've edited a lot of the system, so no go there. If you have the stock rom or want to be a tester, let me know.

[Q] SOLVED: Help - KitKat upgrade from stock... ish.

So, I did a stupid thing this morning. I spent the last, probably, five hours backing up all of my apps and data from my TF300, and once that was all done, I wiped the data on my tablet. "What makes that stupid?" What makes that stupid is, it was a miracle that I ever actually managed to root this thing in the first place, and now, I don't know a) if it's still rooted (I doubt it), and b) if I'm even mentally capable of rooting it again (I doubt it).
So, here's my situation, and if someone could just dumb down the steps for me and point me in the right direction, that's all I need. I got my tablet, I don't know, probably early 2012. I can tell you that the tablet is on ICS 4.0.3, and the build number is 9.4.3.29-20120511. It's also unlocked, I don't know if that needed to be mentioned. Now, things are better since I wiped the data on this mother, but ICS, on this tablet in particular, is slow as balls, and I'm done with it, I want KitKat. But I am so far beyond lost after what I did that if I try to work my own way out of it, I'm going to brick this thing.
I wiped the data because I was trying to do something involving the Fastboot menu or something like that. Whenever I selected the USB icon and hit up on the volume strip, the tablet just locks cold. I figured whatever caused that, would probably go away with a data wipe. It didn't. So now my data's gone, my apps are gone, my tablet's not rooted anymore, I have no idea how to get to KitKat, I can't sleep at night, it burns when I pee... let's focus on the tablet stuff for now, I'm signed up to some forums for the other stuff.
I know most of the people that read this topic will be inclined to say, "You're an idiot, read this, this, and this, and take care of it yourself." I know I'm Androidiot, and I'm humbly asking for help. Again, I'm just petrified of following the wrong topic and ruining the whole thing, so if someone could tell me how I'd go about upgrading my tablet from stock ICS to KitKat, I'd appreciate the hell out of it.

Just a little bump, not too big... no love for Tim?

Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2

zlazaar said:
Normally, you need to install the latest stock ROM from ASUS in order to recover a functional device & by the way upgrade your bootloader.
Things done, you can proceed to install recovery and kitkat.
Better explanations here : http://forum.xda-developers.com/showpost.php?p=53738192&postcount=2
Click to expand...
Click to collapse
Thank you, Zlazaar!
Well, it seems that after my device was wiped, it still didn't remove CWM as a bootloader or whatever, I don't know what I'm saying. When I hold down the power and volume down buttons, I could wait like ten seconds for fastboot, or I could tap vol up to enter the "RCK" menu. I don't know what that means. But I go into it, and I'm at the CWM menu, I think it was 5.5.0.4. You probably know better than me if I need to do anything further than that with CWM, but I should be good on that, right?
I'm almost going to go to the sites that you mentioned to download files and get more information on how to use it all. I appreciate your help, because without it, I'm sitting on an unrooted stock ROM with only most of my apps, because oh yeah, like 70 apps forgot to transfer with that backup I did... so, whoopee.
Thank you again, buddy!

The goal is kitkat, right ?
So, in order to get it you need 2 important things :
1- The latest bootloader, yours can't handle kitkat.
2- a custom recovery supporting kitkat, i.e i'm using TWRP 2.7.1.0 (link in my signature), your CWM is outdated.
The only way i know to update the bootloader is to flash Stock ROM via fastboot as described in tutorial.

I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol

Here is the driver : Universal Naked Driver
After install, you can use fastboot and complet other steps.

Tim 13 said:
I got some really stupid questions... apparently it's been entirely too long since I've messed with any of this.
What's a bootloader? I know mine's unlocked, but I didn't know there were versions of it. Is it the blob file I got from Asus?
And I have my tablet hooked up to my PC, it's on the fastboot menu wait for input from USB. When I go to the command prompt, I've tried to push TWRP to the device, but when I start a command with "adb push," it just tells me that it doesn't know what to do with that command. Same thing happened with fastboot, but then I realize I didn't have fastboot installed, so I tried to install it and it complained about a missing dll file on my computer, and I think I'm about ready to give up. lol
Click to expand...
Click to collapse
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck

b..c said:
Ok Tim so the GOAL IS: 4.4 KITKAT CORRECT?
This is the process overview. This is a review.
Step 1 Upgrade the bootloader. Why? Inorder to flash a 4.4 rom you need a Jelly Bean 4.2 bootloader. How? Do as zlazarr suggests by flashing the lastest stock version V10.6.1.27.5 on your tf300t. Flashing the latest stock rom will update your bootloader. And here's another helpful guide.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/ Remember that the SKU has to match!
Step 2 Follow this guide.
http://www.transformerforums.com/fo...nstall-roms-tf300-jelly-bean-kitkat-roms.html
It guides you on how to unlock your bootloader which you already have and it shows you how to install twrp. After installing twrp MAKE A BACKUP!
NOTE: If using the command method on the link fails repetitively use the app rashr to install the twrp version in the link
Step 3 Upgrade twrp to vr 2.7.0.0 or higher. Refer to step 2 link on the post about 4.4 kitkat.
Step 4 Install a 4.4 kk rom. I recomend the lastest snapshot of Cyanogen Mod 11. The download is on their wiki.
And then your done! Don't give up! The hardest part I find is using the command prompt! Look for work arounds. AND SEARCH FOR METHODS!
Goodluck
Click to expand...
Click to collapse
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!

Tim 13 said:
Okay, so I've started work on this finally, but I think I might be having some trouble. I flashed the latest stock ROM onto my baby and restarted the tab like the article said, but now it's taking a very long time to load. I don't know if it's supposed to be taking this long, considering I'm pretty sure it wiped the data on it (flashing a ROM wipes data, doesn't it?), so I'd assume that removing the weight of those apps would make startup lightning quick.
I have the ASUS logo and the spinny circle. And it's just spinning and spinning and spinning and spinning. Is this a problem?
I'm going to let it spin spin spin spin spin for like five more minutes, and then I might go cry for a while.
EDIT: I cried too soon, it loaded for a long time then came to a menu that says "Android is upgrading..." and it's optimizing the apps, or apptimizing, that were apparently NOT wiped when I flashed a new ROM. lol, so I'm back on track. So far, so good. Thank you for the detailed guide, I appreciate it!
Further edit: And I'm also done rooting and flashing to KK 4.4. Thank you for dumbass-proofing the process for me, it is incredibly highly appreciated. I didn't kill my tablet!
Click to expand...
Click to collapse
Hi Tim13,
I'm glad to hear that everything went well and my guide helped you!:good: And to answer your question flashing doesn't wipe your data. You have to manually wipe it. And lol:laugh::good: that you didn't kill your tab. I hope you find your tab faster and useful again!

It's just as slow and useless as it was. But honestly, the flashing process was fun, and I learned from it. Plus, TWRP and Cyanogen mod are awesome, and now I know that. lol

Great to see you up and running @Tim 13 :good:
Can you add SOLVED to the thread title
Thx Josh

No, I'm not gonna do that.
I'm just kidding. You're all right, darling. :good:
Edit: Actually, not being a douche, I can't figure out how to edit the thread title. I went to edit the first post and I can't change the title of the post... I'm gonna look around for how to do it a bit more but after that I'm gonna go to bed.
DOUBLE EDIT: Got it, as you can see. Thanks to all that helped out!

Updating advice please ! Reroot failure

Hi everybody ! Ill try to keep it simple as I'm sure its covered somewhere but here goes ....
Ive been using my shield portable, rooted, for ages now no problems.
Like many Ive updated it in short ever since nothing whatsoever has worked properly , most annoyingly the screen doing backflips when you go near it and hundreds endless strange updates when rebooting.
Anyway I don't think you or I or any of us want to waste time trying to figure out why its done any of this but I just want to be able to fix it. I guess I'm going to have to start again somehow! its worth noting here that all my backup apps like Helium now don't seem to work.
After the update I of course ReRooted and it appears fine from boot loader , still says unlocked. but upon usage its clearly very confused about whether its rooted or not !
In short its useless. Advice please My kung Fu warriors
May your arrows fly straight and true

I have no idea about the various issues, but I would perform a factory reset, and clear cache and dalvik cache using at least 3 swipes per each function. The method of rooting I recommend is by flashing a zip of SuperSU from a custom recovery menu. CWM or TWRP are both available for the NSP. After flashing SuperSU, when you reboot and go into SuperSu you'll see that it's installed (locked down tighter) as a system app.
Downloads:
SuperSU (latest stable version) v2.65
CWM Recovery Menu (latest version) v6.0.4.4
TWRP (Modified recovery (based on TWRP v2.8.7.0)
Sorry. This is the best I can offer you right now. If this doesn't work I would reflash the stock images of whatever OTA you wanna be on. The images can be found @:
SHIELD Open Source Resources and Drivers. You'll need at least the platform-tools portion of the Android SDK (to use Fastboot to flash from recovery). A user friendly PC app that can basically do all this sort of stuff is Shield Ram v1.1. You might find that easier to use.
Oh and here's the latest Minimal ADB and Fastboot Drivers installer [v1.3.1]
If you need further help, let me know.

Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again

[/COLOR]
Marrhead said:
Hi ! Thanks for the good advice.
I should have mentioned, I'm using a Mac now.
From what I understand it's still possible , maybe
Even easier.....
Sorry to throw a spanner in your super helpful works !
Thanks again
Click to expand...
Click to collapse
Yeah, pretty much the rule is generally "as long as you can still see the screen, it's probably fixable". Sounds to me like your best bet, would be to download the OTA you wanna be on, and flash a new install to your Shield. It's the quickest way from A-B. I'm about 99% sure that this would solve the problem (as long as you re-root it properly). Though if you have your reasons, you can try some of the other things first. You're welcome and let me know how things go!

So where does one get the latest OTA?
cheers

Marrhead said:
So where does one get the latest OTA?
cheers
Click to expand...
Click to collapse
I did link up the main Nvidia page that would lead to the OTA images, but here's a direct link to DL just the OTAs:
Edit: you can get there through the link I included in my previous post: SHIELD Open Source Resources and Drivers. I'm having issues with editing posts, and all sorts of odd **** with the link trying to post a more direct link. It's an Nvidia site, just scroll down to Shield Portable Recovery OS Images (something like that).
Unfortunately there are only Linux and Windows downloads available. I'm not sure what your best option would be, as you have a Mac. You could contact Nvidia support, and see what they say about it. Sorry, but I don't think I can probably help much more than this.When I contacted Nvidia support about a year ago, they were pretty helpful. Hopefully you get this sorted soon. Oh and the OTAs are flashed via a terminal/command prompt. So if you can emulate DOS on your Mac (which I don't see why not...DOSbox? maybe) then that sounds to me like the solution.

Ok , hit another brick wall. Im using a windows computer now, followed all the instructions i can find, and now the bootloader seems dysfunctional.
Ive got adb and fastboot and its recognising the device but once rebooted into bootloader which loads fine, the commands say no device found and nothing works in this mode.
If i hit recovery mode then a little dead android appears! poor little guy.
I tried shield ram but it had same problems, seems to run fine but cant find shield once its in bootloader...
Ive got the image zip of the update i want to flash but no idea if im doing it right- not sure how to use it.
Help!