[DEV][Tool]TF300 NVFlash - Testers required! - Transformer TF300T Android Development

Update - Nvflash is now released. See post at http://forum.xda-developers.com/showthread.php?p=31756256
We (AndroidRoot.Mobi) have been working on bringing nvflash to the TF300. This is now a reality.
Before we release, we want to test it a bit more to weed out any potential issues. We have already tested on some devices, but just to be on the safe side.
So in short, we need testers with a TF300 that is:
* Unlocked
* Running ICS with ICS bootloader
* Host PC running linux or Windows and able to install necessary drivers and find necessary tools.
We prefer people able to join the #asus-transformer irc channel on irc.freenode.net, because realtime makes testing easier!
Unfortunately, nvflash won't be possible for people who already upgraded to the official JB release (unless someone finds a way to downgrade to ICS rom & bootloader). Once you have nvflash on your device, it's safe to upgrade.

Is there any chance you will be able to get it working on the new bootloader eventually?

What do you expect from testers...
I have limited time, but can test.
Running Ubuntu 12.04 and have a working cm10 and AOSP 4.1.1_r4 build environment (ROM development for another device)
Verstuurd van mijn Transformer Pad TF300T met Tapatalk

scanno said:
What do you expect from testers...
I have limited time, but can test.
Running Ubuntu 12.04 and have a working cm10 and AOSP 4.1.1_r4 build environment (ROM development for another device)
Click to expand...
Click to collapse
We expect you to:
a) be on IRC so we can talk to you.
b) be on the ICS bootloader, and have not accepted the official OTA for JB (because this includes the new bootloader)
c) flash a custom bootloader as per our instructions (pre-tested)
d) generate nvflash blobs that you will be able to use to gain nvflash access (no impact on your current rom)
It's really not that hard.

i may be willing to help try this out, but after sumtin like this gets released do you think the ubuntu dev's will begin to port over dual boot linux now that we will have nvflash, i mean isnt that why we cant have linux dual boot yet because we had no nvflash. but wever i am on stock ics rooted, and bootloader unlocked. no custom recovery though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

bige914 said:
i may be willing to help try this out, but after sumtin like this gets released do you think the ubuntu dev's will begin to port over dual boot linux now that we will have nvflash, i mean isnt that why we cant have linux dual boot yet because we had no nvflash. but wever i am on stock ics rooted, and bootloader unlocked. no custom recovery though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
canonical do not port ubuntu to devices like this, only third parties like myself do, and part of the problem is lack of device.
if you have seen the tf201 ubuntu setup you will see nvflash is not a requirement though

bige914 said:
i may be willing to help try this out, but after sumtin like this gets released do you think the ubuntu dev's will begin to port over dual boot linux now that we will have nvflash, i mean isnt that why we cant have linux dual boot yet because we had no nvflash. but wever i am on stock ics rooted, and bootloader unlocked. no custom recovery though.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
Lilstevie's statement is quite accurate, however, one thing nvflash does bring is the ability to play with a hell of a lot more things without fearing that you could brick your device!
This is really the beauty of having nvflash. Pretty much no matter what you do (software wise), you can always recover!

lilstevie said:
canonical do not port ubuntu to devices like this, only third parties like myself do, and part of the problem is lack of device.
if you have seen the tf201 ubuntu setup you will see nvflash is not a requirement though
Click to expand...
Click to collapse
so then i ask, do you think anyone will port it over from the tf201 to the tf300t. cause chroot ubuntu can be a pain in the ass.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

bige914 said:
so then i ask, do you think anyone will port it over from the tf201 to the tf300t. cause chroot ubuntu can be a pain in the ass.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
As soon as nvflash for TF300 becomes available, many more devs/regular people will get involved for they won't risk bricking their devices. It´ll be just a matter of time.

cant wait
Valantur said:
As soon as nvflash for TF300 becomes available, many more devs/regular people will get involved for they won't risk bricking their devices. It´ll be just a matter of time.
Click to expand...
Click to collapse
i hope they do port it over, cause id love to see it running alone on such a wonderful device, i mean i got ubuntu 10 through vnc running on mine really nice, and i found the number 1 free vnc client that actually can use a native mouse or scroller pad which would be what is on the device keyboard dock, who knows maybe in a few months, we will start to see some progress ?

ieftm said:
We expect you to:
a) be on IRC so we can talk to you.
b) be on the ICS bootloader, and have not accepted the official OTA for JB (because this includes the new bootloader)
c) flash a custom bootloader as per our instructions (pre-tested)
d) generate nvflash blobs that you will be able to use to gain nvflash access (no impact on your current rom)
It's really not that hard.
Click to expand...
Click to collapse
I am on the ICS bootloader, and registered on freenode. What are the changes of getting a brick (because of flashing a new bootloader...)
Verstuurd van mijn HTC Vision met Tapatalk

scanno said:
I am on the ICS bootloader, and registered on freenode. What are the changes of getting a brick (because of flashing a new bootloader...)
Verstuurd van mijn HTC Vision met Tapatalk
Click to expand...
Click to collapse
About the same risk as flashing a new ASUS rom.
Our mods are well tested on TF201 so it definitely does work. The biggest risk is if something goes wrong during flashing (e.g. before you have nvflash files), you're hardbricked. (ASUS can fix it of course, but..)
So in short, things to make sure before trying anything like this:
That both APX and fastboot drivers are installed [Windows only]
That you have working fastboot tool available
That you don't use a dock while doing it.
That device is fully charged.
The above minimizes the risk considerably!

To bad I'm on that stupid JB bootloader... Had I just searched better for it. I would almost sell the Tablet to get a new one! xD And to try this and help.

rayman said:
About the same risk as flashing a new ASUS rom.
Our mods are well tested on TF201 so it definitely does work. The biggest risk is if something goes wrong during flashing (e.g. before you have nvflash files), you're hardbricked. (ASUS can fix it of course, but..)
So in short, things to make sure before trying anything like this:
That both APX and fastboot drivers are installed [Windows only]
That you have working fastboot tool available
That you don't use a dock while doing it.
That device is fully charged.
The above minimizes the risk considerably!
Click to expand...
Click to collapse
Ah well lets try it. Have some time tomorrow.
I am running Ubuntu 12.04 so no driver problems. Fastboot is available (linux version offcourse)
Verstuurd van mijn HTC Vision met Tapatalk

rayman said:
About the same risk as flashing a new ASUS rom.
Our mods are well tested on TF201 so it definitely does work. The biggest risk is if something goes wrong during flashing (e.g. before you have nvflash files), you're hardbricked. (ASUS can fix it of course, but..)
So in short, things to make sure before trying anything like this:
That both APX and fastboot drivers are installed [Windows only]
That you have working fastboot tool available
That you don't use a dock while doing it.
That device is fully charged.
The above minimizes the risk considerably!
Click to expand...
Click to collapse
May I ask how many people flashed the new bootloader (with nvflash support) on their TF300s? And how many of them ended up with a brick?
Thanks

Valantur said:
May I ask how many people flashed the new bootloader (with nvflash support) on their TF300s? And how many of them ended up with a brick?
Thanks
Click to expand...
Click to collapse
I've flashed new bootloader and i'm bricked . I've no acces in fastboot mod, When i press vol down+ power i have no menu

leclasheur22 said:
I've flashed new bootloader and i'm bricked . I've no acces in fastboot mod, When i press vol down+ power i have no menu
Click to expand...
Click to collapse
Just to clarify - He did *not* flash our bootloader, so he's really not answering your question.

Valantur said:
May I ask how many people flashed the new bootloader (with nvflash support) on their TF300s? And how many of them ended up with a brick?
Thanks
Click to expand...
Click to collapse
No bricks so far.
We had some bricks on TF201, where people deviated from the guide and hardbricked.
Flashing bootloader is dangerous by nature - but so far our modified bootloaders has worked at least as well as non-modified ones.

rayman said:
Just to clarify - He did *not* flash our bootloader, so he's really not answering your question.
Click to expand...
Click to collapse
No solution is possible to flash all ( ics, jb , custom ) bootloader with apx mode ? sorry i noobs

rayman said:
No bricks so far.
We had some bricks on TF201, where people deviated from the guide and hardbricked.
Flashing bootloader is dangerous by nature - but so far our modified bootloaders has worked at least as well as non-modified ones.
Click to expand...
Click to collapse
What kind of modifications did you make? I mean the bootloader is closed and no sources available AFAIK.
Verstuurd van mijn HTC Vision met Tapatalk
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
leclasheur22 said:
No sulution is possible to flash bootloader with apx mode ? sorry i noobs
Click to expand...
Click to collapse
Flashing the bootloader should enable flashing the bootloader in apx mode.
Verstuurd van mijn HTC Vision met Tapatalk

Related

TF300T Bootloader Unlocked!

Taken from here:
http://forum.xda-developers.com/showpost.php?p=26422045&postcount=84
Quote from the Asus Global website, on the tab "download" choose "Android" as OS, then browse to "Utilities" and download the bootloader unlock tool, it dates from 22 may 2012:
http://support.asus.com/download.asp...mzkQ4yoz5WzBrW
Unlock Device App: Unlock boot loader.
Notice:
1. Only suitable for Andriod4.0 Ice Cream Sandwich OS version.
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions;the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
※This tool now only works with TF300T ICS of TW,US,WW SKU. It won’t work on other devices.
http://dl.dropbox.com/u/25830232/UnLock_Device_App_V7.apk - APK
Amazing!
I'm proud to announce that I'm going to start porting CyanogenMod 9 to this little thing
XpLoDWilD said:
Amazing!
I'm proud to announce that I'm going to start porting CyanogenMod 9 to this little thing
Click to expand...
Click to collapse
Device here ready to run it
is it true you cant lock it again?
I dont wanna unlock and then it breaks and Im at a loss.
Awesome news! Hopefully someone will figure out a way to re-lock the device if something goes wrong.
Nekromantik said:
is it true you cant lock it again?
I dont wanna unlock and then it breaks and Im at a loss.
Click to expand...
Click to collapse
If Asus says it's true, then it's true, since they made it . But maybe some smart XDA dev will find a way to re-lock it.
maspro said:
If Asus says it's true, then it's true, since they made it . But maybe some smart XDA dev will find a way to re-lock it.
Click to expand...
Click to collapse
Thanks.
I may wait and see if anyone does come up with a way to relock.
That and the less bright screen are only thing holding me back as I want to use it outside and its getting to summer so will be bright out.
Nekromantik said:
is it true you cant lock it again?
I dont wanna unlock and then it breaks and Im at a loss.
Click to expand...
Click to collapse
I'm with you on this one lol
Sent from my ASUS Transformer Pad TF300T using XDA
One a recovery is adapted hopefully there will a stock recovery made.
Sent from my VS910 4G using xda premium
Giggity!!!
Sent from my Galaxy Nexus using Tapatalk
Still can't mine unlocked though, keeps saying network error
Just unlocked by bootloader! AWESOME! Cant wait for a custom recovery and new roms!
Hopefully TWRP will be ported over.
I am hoping for AOKP!
Anyone able to unlock a bricked tab? That would be top notch...
Nevermind, I see it's a .apk file
Now we can have the stock ROM rooted without any modifications so we can get root without downgrading our firmware. New kernels, too?
Im receiving this tablet in the mail this week.
Im hoping for a quick port of CWM and then CM9 or AOKP to follow.
great circumstances to walk into!
SilentStormer said:
Im receiving this tablet in the mail this week.
Im hoping for a quick port of CWM and then CM9 or AOKP to follow.
great circumstances to walk into!
Click to expand...
Click to collapse
No doubt. I just got this tab on Sunday after a month of researching and was super bummed that the bootloader was locked.
Does the release of the bootloader, mean it will be easier to root and not have to do the downgrade any longer?
I spent last night to no avail trying to downgrade (the adb access was an issue, which I might have solved today, but haven't put the time in to test it out).
If it means that I won't have to do the downgrade and it might be end up having easier steps to root, then I think (being too much a newbie in tablets) I should wait.
Just wanted to know if that is what this release means?
Thanks!
Rob
rlanza1054 said:
Does the release of the bootloader, mean it will be easier to root and not have to do the downgrade any longer?
I spent last night to no avail trying to downgrade (the adb access was an issue, which I might have solved today, but haven't put the time in to test it out).
If it means that I won't have to do the downgrade and it might be end up having easier steps to root, then I think (being too much a newbie in tablets) I should wait.
Just wanted to know if that is what this release means?
Thanks!
Rob
Click to expand...
Click to collapse
Bootloader means custom recovery and then custom ROM's. If you intend to continue running stock rom and merely want to be rooted, then you may still need to figure out the downgrade issue. If you just wanna run cm 9, then you could just continue to wait patiently. Sounds like you oughta figure out ur adb issue either way, though.
Sent from my ASUS Transformer Pad TF300T using Tapatalk

[DEV][TOOL][BRICKPROOF]TF300 NVFlash release!

After a hard day of extra testing, we're proud to announce Nvflash for TF300.
This release allows unlocked devices to create a set of device-specific files that lets you access nvflash.
Once the procedure is done, you will always be able to recover any software brick (even bootloader!) as long as you keep your files safe!
NOTE:
THIS REQUIRES A NON-BRICKED AND UNLOCKED DEVICE. IT WON'T WORK ON ALREADY BRICKED DEVICES
THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
More details at http://androidroot.mobi/?p=480
Important note: License: Due to the nature of wheelie and the importance of people always using the latest version, Wheelie is NOT redistributable! You are allowed to download it and use it, but you are not allowed to redistribute it in any way - this means no GUI's including it, no reposting zips/tar.gz's and similar! At a later date, we will be releasing our source code and relicense it as GPL.
Enjoy
- AndroidRoot.Mobi Team
Members: rayman, lilstevie, kmdm, Bumble-Bee (XDA: apache14), IEF (XDA: IEFtm)
NOTE: If anyone wishes to donate, http://androidroot.mobi/donations/ is place to do it! DO NOT DONATE DIRECTLY TO ME.
Nice, I'll have to give this try. Its good to have a safety net.
So once I have generated the files and have NvFlash working, would I be able to then flash the new JB from Asus and then use the NvFlash files to go back to ICS bootloader?
PS: This thread should be pinned.
wideopn11 said:
Nice, I'll have to give this try. Its good to have a safety net.
So once I have generated the files and have NvFlash working, would I be able to then flash the new JB from Asus and then use the NvFlash files to go back to ICS bootloader?
PS: This thread should be pinned.
Click to expand...
Click to collapse
Yes! Once you have these files, you can move back and forth between any rom/bootloader you desire. ASUS can do nothing to prevent it once you have the files for your device!
It also essentially makes your device brick proof (assuming you carefully follow our guide and do the backups!), so development gets a lot more safe
Yyyeeeeeahhhhh
THIS IS AWESOME!! Thank you guys so much for all your hard work.
I followed the process as explained in the guide and everything went perfectly.
For anyone there still on the fence... give it a go! The whole process takes 2-3 minutes. Just make sure you don't skip any step of the process and keep your generated files in 3 or 4 different locations (thumbdrive, cloud, external HD and the TF300 in my case).
Kudos to all of you again!
Now I am really pissed that I took the JB updated
Gold job
Envoyé depuis mon LT18i
Even working perfectly on the TF300TG(!) used windows 7 x64 for the whole process...
There are any hopes working nvflash for JB BOOTLOADER? Or is it impossible?
rayman said:
[*]THIS ONLY WORKS IF YOU HAVE A PRE-JB BOOTLOADER
[/LIST]
[/COLOR][/SIZE][/B]
Click to expand...
Click to collapse
What do you mean with Pre-JB bootloader?
You mean OTA JB from ASUS?
w0uter said:
What do you mean with Pre-JB bootloader?
You mean OTA JB from ASUS?
Click to expand...
Click to collapse
Yes
Sent from my Nexus S 4G using Tapatalk 2
w0uter said:
What do you mean with Pre-JB bootloader?
You mean OTA JB from ASUS?
Click to expand...
Click to collapse
You need to be on ICS Bootloader...so yes,if you updated to Jelly Bean using the OTA or the official rom from Asus site you CAN'T use this.
Pretoriano80 said:
You need to be on ICS Bootloader...so yes,if you updated to Jelly Bean using the OTA or the official rom from Asus site you CAN'T use this.
Click to expand...
Click to collapse
Please don't abuse me because I may have missed any pertinent discussion but is there any thing in the works to eventually develop this to be workable with the JB Kernels and mods? :fingers-crossed:
I would guess there will be a way to downgrade and at this point you will be fine
Sent from my ASUS Transformer Pad TF300TG using xda app-developers app
Sorted in APX mode and installing drivers now!
Sweet backed up all files to Laptop/Tablet/Drive/Dropbox!
Not sure how to use NVFlash but at least I know its there if required!
I followed all the steps to the letter (I think) because everything worked up to and included generated the 5 files (blob.bin, blob.log, bootloader.ebt, create.bct, recovery.bct) which I saved to like 4 places lol, but I can't seem to get into APX mode. When ever I hold volume up and power I just end up in CWM recovery. Am I missing something?
wideopn11 said:
I followed all the steps to the letter (I think) because everything worked up to and included generated the 5 files (blob.bin, blob.log, bootloader.ebt, create.bct, recovery.bct) which I saved to like 4 places lol, but I can't seem to get into APX mode. When ever I hold volume up and power I just end up in CWM recovery. Am I missing something?
Click to expand...
Click to collapse
Yeah just reboot the tablet and hold VOL + and it will go into APX mode
Northern-Loop said:
Yeah just reboot the tablet and hold VOL + and it will go into APX mode
Click to expand...
Click to collapse
Ok thanks that worked. Now I am in APX mode, which driver do I point it at? It's not finding the driver automatically.
Edit: nevermind I had the driver, just needed to point to the right folder to install it. #facepalm
wideopn11 said:
Ok thanks that worked. Now I am in APX mode, which driver do I point it at? It's not finding the driver automatically.
Click to expand...
Click to collapse
Its on the guide main page http://forum.xda-developers.com/showthread.php?t=1426502
Awesome! Thanks for all the help. Is there some info on how to use NvFlash with these shiny new backups?
I can't use this - already on jb, but still wanted to extend thanks. I'm sure this is a gem to many. Well done devs.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Noob-friendly] Poor man's FlashTool

Version 3 released! Check for even more simplicity and a new UI! NO more copying!
Click to expand...
Click to collapse
If you're experiencing errors, please report them either in the thread or PM me.
Please report ANY errors or typos you come across, I made this in 4 hours without a single break, so there's bound to be an error somewhere
What's new:
-Completely rewritten (ACTUALLY written, not VB)
-Even simpler! NO MORE COPYING!
-Even smaller in disk size!
-No tutorial needed! Yes, it's that easy -- just read carefully and don't panic
There's still no way to:
-relock the bootloader
-flash FTF files
_____________________________________________________________________________________________
Note: Inside the Fastboot.rar, there are fastboot drivers for 2012 Xperias. Install them if you dont have them yet. Those are the only useful files you need from that folder, everything else (both adb and fastboot) are already contained in the new BU.zip!
TESTING:
Reported working Windows versions:
Windows 7 x86
Windows 7 x64
Windows Vista x86
WANT TO HELP?
Then test it and report your phone model and windows version (x64/x86, service pack etc.) -- send me a PM
Please do... You can always flash a kernel or recovery.
Thanks for helping me and all those noobs out
About the attachments:
-Fastboot; contains adb and fastboot, plus Xperia 2012 Windows drivers
-BootloaderUnlock; contains the old PMFT - version 2 (kind of useless unless you understand everything it says in there)
-nexus; the NEW PMFT - version 3 -- if you already have the drivers, this is all you need
someone755 said:
I've been getting some questions on PM lately, about 'how to unlock my bootloader'...
So, fed up with those infinite PMs, I quickly put this together (30 minutes, not much).
It's not much, and I've only tested it for one minute, but it should help the average noob user get their bootloader unlocked.
(I've only tested this on a x86 Win7 PC, so please help me find out where this works on.)
So, the basic idea is, that the noob user extracts the attached adb and fastboot .zip file and extracts it to disk C: (I'll make options for other drives later on, I just need to know whether or not this works). The user then opens up the program inside BootloaderUnlock (and installs it), and, after many warnings, gets to a screen where he is told to input his Bootloader unlock code (obtained from Sony's website).
The program then warns the user a little more, just to make sure he understands, and then, two lines of text show up.
The user enters those lines of text into the console window (the fastboot.exe he extracted at the beginning) and Viola!
If all steps have been done correctly, he now has an unlocked bootloader
It's a simple, yet fool-proof concept, tested on a complete phone moron (after reading some instructions on Sony's unlock site).
Please help me test this, as this may be really helpful to those that don't understand FlashTool and don't have an idea how to do it via the official method.
Also, if you don't understand, there are some instructions within the program (written in VB, so you may need NET framework... MAY need it...)
Thanks for helping me and all those noobs out
Note: extract the fastboot.rar to C:, so you will have the fastboot.exe in C:\Fastboot\fastboot.exe
Note: Inside the Fastboot.rar, there are fastboot drivers for Xperias. Install then if you dont have them yet.
Note: The BootloaderUnlock.rar is a visual basic program. Please help me test it on different Windows systems (XP, Vista, 7, 8, 2000; all both x86 and x64)
Click to expand...
Click to collapse
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app
derrickdroid said:
A way to get a noobs phone bricked?!
Sent from my LT28at using xda app-developers app
Click to expand...
Click to collapse
No it wouldn't. It'll either work or not
Sent from my Jellybean Xperia S
Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...
someone755 said:
Yeah, it's actually the same as Sony's way, this program just tells the user what to write into the CMD window.
You can't brick your phone with this, because it either suceeds or fails. Either gain or no gain (and no loss) for the user...
Click to expand...
Click to collapse
i think he was referring to:
IF you are so beginner that you aren't able to even unlock your bootloader
THEN you could be so newbie to brick it
That's possible, if you're pointing to the fact they could brick their phone after unlocking the bootloader.
But before the unlock, no, it wouldn't be possible...
But hey, some people might have trouble with windows and are new to it. (I know many linux users that are forced to use windows for their phones that could use tools like this for their phones (not Sony, but others...)...)
So can this way unlock any bootloader even if it says bootloader locked? Thanks
Sent from my LT28i using xda app-developers app
Nope.
Did you not read the first post?
It's the same as the official method, but simplified...
Nothing's changed, basically, so it can't do more and it can't do less!
Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app
Its not the phone, it's the carrier...
mcmanone said:
Ok thanks just dont understand why they sell ones that can and others you cant unlock oh well
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
It's because companies like AT&T give locked down phones away for free with a service contract. That way they can lock some services to make you pay more. For example AT&T makes you pay an additional monthly fee for the use of tethering (only when you use the att stock Rom, it's free on generic version )
From Jaramie's LT28at
2012Xperia SOFT-BRICK Recovery Thread
So I guess it's great in my country;
you don't get a 'free' phone, you pay at least 1€ (depending on the plan you chose; I chose the one where I get to pay 370€ for a nozomi)
You can always trade your phone on Swappa (you have loads of ads on CM's sites and forums) and get an unlockable one...
what is the difference between this tool and this one?
http://forum.xda-developers.com/showthread.php?t=1794800
This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...
someone755 said:
This one, you can't flash things with, and you don't need a ton of downloads...
Yours is actually a program that uses FlashTool... It has flashtool included in the libs, which means:
1. You download the program AND the giant FlashTool
2. It can flash FTF, IMG and SIN files (because this is flashtool after all...)
I came up with my method for people with bad internet and limited storage...
It actually is the official method, but with a "paste-press-copy-paste" procedure, although the main idea is about the same as all the others...
Basically, every method is based on the official way, but there's a bit of variation here and there...
Click to expand...
Click to collapse
okay thanks....
DOWNLOADING
Let the Noob try it !!
Hey Guys,
I am a Noob and have been trying to unlock my bootloader for about a week now, I have tried a few methods without any joy.
I will give this a go and will report back if it works or not. :laugh:
Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...
someone755 said:
Your problem might be one of these, if it doesn't work:
1. Your phone is not in fastboot mode -- did you check that?
2. You don't have the right drivers installed on your PC -- or do you?
3. Your phone's bootloader may not be unlockable -- now, if you didn't check that, you really are a noob.
4. Your unlock code is incorrect -- that was the case with me, but in the end that was the only problem...
Click to expand...
Click to collapse
Hi,
Thanks for the reply, the problem i have is with the drivers. I have tried different solutions as posted here and on the web.
But still could not get the drivers to work??
I will try this method as it states the drivers are included. If it all works awesome, if not then I fail and will forever be stuck with stock rom's.
Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?
someone755 said:
Which windows are you running (vista, 7, 8, is it 32 or 64 bit?)?
Also, did you try with FlashTool's drivers?
Click to expand...
Click to collapse
I'm running windows 7 on a 64 bit laptop.
Tried the flashtool drivers also but still no joy, I check in device management for S1 and each time there is a problem installing the drivers.
I still have a PC running vista so might give that a try if all else fails.
Thanks for your help so far, will keep you updated with how I get on

[Q] R800a on Rogers, help getting fastboot working!

Hi all!
Okay so I'm ready to bash my face off something till I die... lol I've been up all night screwing with my xperia play from rogers. First I did the touchpoint method to unlock the bootloader and s1tool confirms that it's unlocked. However, no fastboot and when I punch in the code provided by SE to see the value of "bootloader unlock allowed"... it's still "no". From what I understand the touchpoint method shouldn't change this value. However because this value is still set, I have a feeling that this is why I can't enable fastboot.
I'm trying to flash a custom jellybean rom using flashtool and because of the aforementioned situation, I can't. I'm wondering if anyone can point me in the right direction to get fastboot working. I hate that I've paid through the nose for all the android devices I own and I yet I still don't technically own them. Anyway I won't rant....
P.S. Just to be verbose, when I do fastboot.exe devices... just hangs saying waiting for device. Device shows up in Device Manager but is code 31 cannot start. Also if I hold search and plug in USB or any of those combos I absolutely cannot get a blue light. I can also assure anyone that I've spent probably 8 hours straight googling the bleep out of this issue and working on it so I'm not being lazy I've just reached the limits of what I can do on my own and am begging for any help that is available!
Thanks in advance!
Also just more info, I've got the devices rooted if that makes anything simpler or opens up options. I'm also wondering if this might be a driver issue because I was doing this on my windows 8 machine and from 7 up you have to do a bunch of stupid temporary system configurations to allow unsigned drivers plus wondering if it's a driver incompatibility issue. If that's the case can I use flashtool on my linux machine? Something I'll look in to... just wanted to post as much info as I can. Thanks again!
So no one in this forum has any idea?
No one here has absolutely any idea about what I can or can't do with this bootloader situation? Wow....
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
psxpetey said:
You dont have fastboot thats why but you can flash. Ftf custom kernels
Sent from my LT28i using xda app-developers app
Click to expand...
Click to collapse
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Furinax said:
Pardon my ignorance.... but you mean I can flash a custom kernel on my rogers r800a that will have fastboot? I'm asking basically because theres a working jellybean rom it but without fastboot I can't use flashtool to flash this custom rom. I'm a bit of a noob sorry and I ought not to be with what I do for a living. lol
Click to expand...
Click to collapse
When you do test point unlock you don't get fast boot you have to use flash mode and .ft kernel and whatnot go into flash tool and press boot loader unlock it should fail and say its already unlocked
Sent from my R800i using xda app-developers app
Got it!
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Furinax said:
After much struggle.. I've got it all working and running slimbean. It's quite a huge pain in the rear to get set up so I'll post a complete guide on this thread afterward... especially considering that this thread comes up in top google search results for me when I look up "unlock bootloader R800a" and other such similar phrases.
Click to expand...
Click to collapse
So uh... what happened to the guide?
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
Honestly this was almost a year ago and I ended up chucking that damn phone out and getting my wife a new one. I barely remember the whole process I just remember it being about 3-4 days of me being intensely angry and frustrated lol. I do recall it involved ripping apart the phone and shorting out certain pins that are covered by the sticker under the battery, but I believe that portion was for unlocking the sim, I really can't remember. I'll see if I can dust off those brain cells and get the whole thing back and post nfo if successful.
someguymartin said:
So uh... what happened to the guide?
Click to expand...
Click to collapse
This I used as for part of the process:
https://www.youtube.com/watch?v=zM8lWE4Layc
However I don't believe this tutorial includes unlocking the bootloader. I believe sony provides a utility or something to unlock the bootloader but you're missing fastboot. I think the process involved flashing a custom kernel, not sure. I'll keep digging into my memory and post more nfo back later. Kernel was Lupus kernel I recall that much.
Edit:
Here is complete guide with bootloader unlock process explained as well.
http://forum.xda-developers.com/showthread.php?t=2187172
More links http://unlockbootloader.sonymobile.com - but as I recall this doesn't work for rogers branded r800a.

[Q] May have bricked my N7 (deb)

So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
jahames said:
So, first, the moral of this story is don't do stuff like this at 2AM after a long day at work.
Tonight, I decided to root my N7 and mess around with a few different roms. Well, apparently I didn't read pages carefully enough because I am now the proud owner of a deb tablet with a flo bootloader on it. My fastboot screen reads:
PRODUCT NAME - deb
VARIANT - deb 32G
...
BOOTLOADER VERSION - FLO-04.02
BASEBAND VERSION - DEB-GOO_2.37.0_1024
I realized this when trying to install CM11, and got errors saying the package was for deb but device is flo.
I've tried to flash factory, but it still leaves me with the incorrect bootloader. FWIW, I'm doing this on a Mac, and won't have access to a PC for at least a few days. Any help would be really appreciated
Click to expand...
Click to collapse
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
StuMcBill said:
Have you just tried flashing the bootloader independently? Instead of flashing the full factory package?
On Mac the command will be ./fastboot flash bootloader <name of bootloader>.img
Hope this helps?
Stewart
Click to expand...
Click to collapse
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
jahames said:
Yeah...gave that a shot too. Flash works, but when I reboot, it still gives me the flo bootloader
Click to expand...
Click to collapse
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
StuMcBill said:
Hmmm, weird! Are you totally sure you haven't downloaded the flo factory image by mistake? I know you will have checked already, but I can't really think of anything else?
Maybe try flashing an older bootloader version?
Click to expand...
Click to collapse
Was working with the 4.4.2 image. Going to give the 4.4 a shot now
Same thing with 4.4...still stuck with the flo bootloader
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
jahames said:
Ok, I was able to flash back to stock, but when trying to flash the CM11 deb image, I got the same error, saying that the package is for deb but this is a flo. Help please?
Click to expand...
Click to collapse
You flashed a recovery for flo. Flash one for deb.
Edit:
http://techerrata.com/browse/twrp2/deb
Reasonably sure I had a deb recovery, but apparently redownloading and reflashing the CWM image did the trick. Thanks!
if you ever have problems try nexus root toolkit. It works wonders if you ever severely mess up any nexus device.
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
same issue
Richieboy67 said:
Wug is also really good for this.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
skfalco said:
I am sorry what is WUG, today a guy arrived to my shop with the same problem, wonder if anyone has a solution? thanks
Click to expand...
Click to collapse
It is here
http://www.wugfresh.com/
It is a toolkit that makes these things very easy. I have used this many times and have never had any issues with it.
---------- Post added at 09:52 PM ---------- Previous post was at 09:50 PM ----------
LinearEquation said:
Wug's has a toolkit. I prefere fastboot over toolkits.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Richieboy67 said:
Well for beginners the toolkits make things very simple. This one has been around for a very long time and is very stable. I have never had any issues with this at all.
Just have to be sure you follow the simple instructions and make the right selections in the menus.. easy peasy..
Click to expand...
Click to collapse
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
LinearEquation said:
I'm not doubting wug's toolkit. He obviously does a great job with it. I was new once too and I know once I discovered how easy it was to use commands it was like a new world. No more waiting on scripts and hoping tool kits would be updated, etc. Everyone has to learn and so I always offer fastboot options. There is also something to be said about working and earning your way to a mod versus a quick one click. My opinion, and you know what they say about opinions :good:
Click to expand...
Click to collapse
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Richieboy67 said:
Yes, I agree in some ways but not everyone wants to mess around all the time. Some people just want to take care of it and forget about it.
Personally I work with php,html,mysql and I also have to use ssh commands every day. When doing something simple such as a rom change I just prefer to open the toolkit and not worry about commands.
I agree if you plan on getting deeply into it then it would be best to learn everything and not reply on the toolkits.
Just my opinion though and I was talking about someone who may be doing this for the first time. Commands and the instructions can be very confusing when doing any of this for the first time.
Click to expand...
Click to collapse
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
LinearEquation said:
Relying on a toolkit can be disastrous because not all toolkits are alike and I have seen some brick devices. You don't have to want to get "deep" into Android to learn a little something. Some want a quick fix with no understanding of what they're doing do and others want to learn what's going on. There are many tablets that can only be restored with fastboot commands because no toolkit exists.
Click to expand...
Click to collapse
While not disastrous, I kind of know what you mean, I started with Wug's (and it is a great toolkit), but once I flashed my own kernel (I used francos app to autoflash so did not have to use recovery or fastboot), I did not realize that by using Wug's a week later that it would flash over that kernel to run those commands and NOT replace francos (I found I was back on stock), lucky by then I had learned enough to recover and no damage was done, but it does point out that my reliance had caused me more work and a bit of worry in the long run.
Still Wug's NRT is a great toolkit...but it should be used as a tool, not a replacement for knowing what to do without it.

Categories

Resources