Database Users

[TF300TG][Guide] Flashing back the original stock ROM

Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Disclaimer:
By following this guide, you will have to issue commands that risk to damage (aka. brick) your tablet or at least void your warranty. I won't be responsible for any damage made to your device. You've been warned.
Click to expand...
Click to collapse
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
fastboot -i 0x0B05 reboot
Click to expand...
Click to collapse
And there you have ! You are now back to stock ROM with fully working 3G

Thanks a lot for this, I found these instructions on Wolf's thread but wasnt sure it would work with our devices, Thanks for taking the first big step.
Questions.
1. Does this wipe your data?
2. Does CWM still work after?

AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173

Hi, followed the steps but it didnt work for me
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796653 KB)...
OKAY [137.443s]
writing 'system'...
FAILED (remote: ()
finished. total time: 138.477s
The Tab shows
Failed to process command flash:system error(0x170003)
The progress bar is showing under the USB logo with 1% blue, after hold power down I'm back into Onyx Rom
Any Thoughts?

I had the same problem and I just issued the same command a second time and it worked just fine
Try to format your /system (under the mounts and storage option) from CWM and wipe data and cache.

2nd time a charm!
Worked fine the second time i ran the command,
Im back to stock again :good:
I will wait for a 3G friendly Rom before flashing again
Thanks for your help
---------- Post added at 05:59 PM ---------- Previous post was at 05:42 PM ----------
Auliyaa said:
AFAIK, this will wipe your data, remove CWM and uninstall root. Your device's bootloader will still stay unlocked though.
You will have to flash CWM back using this guide: http://forum.xda-developers.com/showthread.php?t=1668173
Click to expand...
Click to collapse
Yip Sends you back to total stock
Stock Recovery
Stock Rom
only thing that sticks is Unlocked Bootloader

Thanks a million. This worked for me as well after 2 tries. Saved my $400!

Thanks heaps for this
I ended up in trouble when I flashed the TF300T firmware by mistake. It kept freezing and rebooting on me after that little stuff up.
Anyhow before I did that I made a backup with CWM, and after I restored it my 3G was gone but everything else worked fine.
Manual updates were failed though and they still do. At least I have my 3G back :victory:
So this method would probably work for upgrading to .40 as well, but it means a complete datawipe!
I'm sure there are many of us in the same boat now. I guess we will just have to wait and hope that some kind person makes a recovery image for the TF300TG?

Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
I got a question, i had problems with the touch since the last update, so i want to go back to the original, so my question is to perform this do i have to have the bootloader unlocked?

Auliyaa said:
Hi everyone,
[*] Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Click to expand...
Click to collapse
Hi, any idea why i dont have this 'USB icon' ?? i have 'wipe data' and an android icon that performs a cold boot.

Any idea why this will seemingly flash fine, but go to bootloop when I fastboot -i 0x0b05 reboot the tab?

Don't work for me
Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?

hy
i'm having a problem with my tf300t...when i turn it on it shows the asus logo and in the upper left it show device is unlocked...but i can't enter the menu showing rck and the other 3 icons...i really don't know what to do...
then there is another thing...tried to install driver...i get to the part where the tablet is visible, but with the vol up and reset with a pin...it then shuts down and if i try to power it up it dissapears from the device manager...also...if i don't turn it up, the driver can't be installed...i tried every method...please help...
can i retun it to the repair service this way or i will loose my waranty?
sorry if the spelling isn't correct...i don't speak english fluently
waiting a response...thanks in advance

Auliyaa said:
Hi everyone,
I'm owning A TF300TG model and I recently tried to flash one of the ROMS referrenced on those forums and by doing so I found out that my tablet had lost the 3G features so I had to flash back the Asus stock ROM to get it back.
Since I saw many of you got trouble reinstalling the stock ROM, I decided to write a quick guide on how to do it so everyone could get their tablet fully working again
Note: For the record, when I did the following operations, I already had unlocked the bootloader and installed the CWM recovery.
Download the stock ROM zip file on Asus website (current version is [WW | TW]_epaduser9_4_4_28_1UpdateLauncher.zip) for the TF300TG tablet. Be sure to download the firmware matching your SKU.
Unzip the downloaded file, you will get another archive called , unzip this one too
You should end up with several file, with one of them called blob
For the next step, you will need to install the Android SDK to get the fastboot utility. If you do not know how to use fastboot, you should take a look at this guide.
Once you have installed fastboot, boot your tablet into fastboot mode (Plugin your tablet on your computer's USB, Hold down Power+VolDown, dont press VolUp when prompted, select the USB icon and press VolUp)
Open a command line terminal and navigate to the folder containing the blob file.
Then type the following command:
fastboot -i 0x0B05 flash system blob
For some reason, the transfer seems to fail from time to time, if so, just try again by going back to previous step.
Once the transfer is done and you get that sweet "SUCCESS" printed on your screen, just type the following command to reboot your tablet:
And there you have ! You are now back to stock ROM with fully working 3G
Click to expand...
Click to collapse
Using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
is a tad wrong. It works, but only by accident.
You should be using
fastboot -i 0x0B05 flash staging blob
Click to expand...
Click to collapse
The technical reason for why your command works, is because the nvidia bootloader writes files to the staging area before writing it to the partition you specify.
What essentially happens is:
Blob is written to staging
Blob is copied to system (meaning non-booting system)
On reboot, blob is "extracted" from staging and properly flashed.
Step 3 is what makes it work in the end, but you are causing an extra unneeded write to the flash (step 2 is not really needed) (In this case it works, but it potentially increases the risk of bricking)

thx didn´t know that. So all the howto´s are wrong

benoitvdh said:
Hi, followed the steps but it didnt work for me too
Fastboot copies the file but after when it tries to flash it gives an error
sending 'system' (796581 KB)...
OKAY [129.964s]
writing 'system'...
FAILED (remote: (InvalidState))
finished. total time: 182.134s
The Tab shows
signature mismatch
Can you help me?
Click to expand...
Click to collapse
Your probably running Jellybean, if so this HOWTO does'nt work.

Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.

Blackdrag said:
Question: What exactly is supposed to happen? First I tried it and got the fail and did it a second time and it seemingly worked. In my command prompt it ended with
"writing 'system' ... OKAY"
and wasn't doing anything after that in the command prompt and on the tablet there was a full status bar so it looked like whatever it was doing it was finished? So I held the power button and I think it was a boot loop ... it just was the ASUS screen with the spinning circle. So I just did it again, failed the first time did it again and now I am where I left off. I guess I will wait a while and see if it says "SUCCESS" on my tablet? And if not I will put in the reboot command? (I probably should have tried that last time instead of holding the power button I forgot about the last couple lines of the guide )
EDIT: Or is it cuz I am flashing the wrong SKU? I didn't know what one my tablet is supposed to be ... its a cyanogenmod build so I don't think I cant find what the SKU is supposed to be. I went with US SKU because I live in the United States but I don't know if that's what it is
EDIT2: After waiting a while with no "SUCCESS" Windows said that adb.exe crashed or something. So I put in the reboot command but now it seems to be stuck on the ASUS loading screen again.
Click to expand...
Click to collapse
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:

Success!
Hazaa! I can confirm that I managed to flash back to stock by flashing the blob to the staging partition. Like so many other, the first flash failed but the second time worked. I now have working 3G again!

0nyx7 said:
I have a WW TF300T and had no problem flashing a US version.. so its no SKU problem how long did you wait on the ASUS screen with the spinning circle? It took up to 5 mins for me! just wait a lil bit longer next time.. And there comes no "SUCCESS" on the tablet! only a blue bar that should be full after SUCCESS comes up in your Fastboot-COMMANDLINE.. the reboot with the fastboot reboot command from the first page..just give your tab a bit more time.. its like a babe. handle it with care :silly:
Click to expand...
Click to collapse
Thanks for the reply 0nyx7!
I had waited a while, maybe 10-20 minutes? But I don't remember entirely. I tried flashing the stock firmware a few times but eventually I just gave up. I didn't like the possibility that my tablet was bricked so I just aborted mission and decided to go back to cm10 where it was safe. I just looked up a post on how to flash Clockworkmod Recovery with fasboot and then flashed a cm10 nightly I already had on my internal storage. So all is good... Mostly.

N7 3G 32 Booting failed

I know there is many topic like this, but I need urgent help. We go to holiday on saturday and I have to decide what to do.
Today got I back my N7 from Brno/Czech from warranty repair. Than the device shut down and I couldn't power on, they replaced my charger and sent back the device. I sent on 26th in July with an RMA number.
When I got back the device I started by the courier and it booted into Android. About 10 minutes later it showed me an update to 4.3 and I allowed it. It restarted and when it was ready the device didn't powered on again. It remained on the Google logo. Now - when I tried to wipe/Hard reset - it only shows the Google logo in the middle and a Start sing on the upper right corner.
I can do:
- recovery
- ADB sees the device
- Nexus 7 toolkit sees too
- Nexus Root Tools sees too
- I can install recovery (TWRP-CWM-stock) it works
- bootloader lock/unlock
but
I cant install
- system/image
- boot
- bootloader
- radio
- etc...
It looks like the flash storage is injured. 20 minutes before I sent a command: flash radio now the device in fastboot and on the upper left corner there is a white text: "Booting downloaded image" It doesn't respond...
I need an advice how to forward, send it back or is there any sollution'

bigsee said:
I know there is many topic like this, but I need urgent help. We go to holiday on saturday and I have to decide what to do.
Today got I back my N7 from Brno/Czech from warranty repair. Than the device shut down and I couldn't power on, they replaced my charger and sent back the device. I sent on 26th in July with an RMA number.
When I got back the device I started by the courier and it booted into Android. About 10 minutes later it showed me an update to 4.3 and I allowed it. It restarted and when it was ready the device didn't powered on again. It remained on the Google logo. Now - when I tried to wipe/Hard reset - it only shows the Google logo in the middle and a Start sing on the upper right corner.
I can do:
- recovery
- ADB sees the device
- Nexus 7 toolkit sees too
- Nexus Root Tools sees too
- I can install recovery (TWRP-CWM-stock) it works
- bootloader lock/unlock
but
I cant install
- system/image
- boot
- bootloader
- radio
- etc...
It looks like the flash storage is injured. 20 minutes before I sent a command: flash radio now the device in fastboot and on the upper left corner there is a white text: "Booting downloaded image" It doesn't respond...
I need an advice how to forward, send it back or is there any sollution'
Click to expand...
Click to collapse
need not to worry man...its a common problem...i have xperienced more than 50 times than while doing fastboot it doesnot respond after a certain period of time and when u power off and start the defice it goes into fastboot mode
solution:
for device: enter in fastboot mode
chose power off then leave it for five minutes till then do the instructions for laptop or computer as mentioned below
for computer/laptop:
shutdown (do not restart, it should be shutdown)
then power on ur computer wait for it to finish booting
plug the usb cable in other port (other than the previous port u were trying)
then power on ur device let it go to fastboot
then plug the usb cable to it
wait for 2-3 minutes
then flash the stock factory image by clicking on flashall.bat
hopefully it will take 5-10 minutes to do the work
and if it exists more than 20 minutes...disconnect ur device and repeat the procedure...till u suceed...
sorry mate but this is the only solution to it...
i have tried it many times...
if u succeed...do reply and hit thx...or if u face another problem...just post the reply:good:

dr.sushant said:
need not to worry man...its a common problem...i have xperienced more than 50 times than while doing fastboot it doesnot respond after a certain period of time and when u power off and start the defice it goes into fastboot mode
solution:
for device: enter in fastboot mode
chose power off then leave it for five minutes till then do the instructions for laptop or computer as mentioned below
for computer/laptop:
shutdown (do not restart, it should be shutdown)
then power on ur computer wait for it to finish booting
plug the usb cable in other port (other than the previous port u were trying)
then power on ur device let it go to fastboot
then plug the usb cable to it
wait for 2-3 minutes
then flash the stock factory image by clicking on flashall.bat
hopefully it will take 5-10 minutes to do the work
and if it exists more than 20 minutes...disconnect ur device and repeat the procedure...till u suceed...
sorry mate but this is the only solution to it...
i have tried it many times...
if u succeed...do reply and hit thx...or if u face another problem...just post the reply:good:
Click to expand...
Click to collapse
Thank you for the answer! I'm trying-I'm trying and trying, but none...
I got two error messages, the first is when it sends the radio to the device:
sending 'radio' <16384KB>...
OKAY [2.078s]
writing 'radio'...
FAILED <remote: <BadParameter>>
finished. total time: 2.094s
the second at the end:
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
When I hit The Anykey (I didnt find it at first ) nothing happens... so I'm sad again...
What can I do yet?

bigsee said:
Thank you for the answer! I'm trying-I'm trying and trying, but none...
I got two error messages, the first is when it sends the radio to the device:
sending 'radio' <16384KB>...
OKAY [2.078s]
writing 'radio'...
FAILED <remote: <BadParameter>>
finished. total time: 2.094s
the second at the end:
checking version-baseband...
FAILED
Device version-baseband is 'N/A'.
Update requires '1231_0.17.0_1205'
When I hit The Anykey (I didnt find it at first ) nothing happens... so I'm sad again...
What can I do yet?
Click to expand...
Click to collapse
What factory image have you tried?
Update requires '1231_0.17.0_1205'
Click to expand...
Click to collapse
I think this one can be dodged by installing the 4.2.2 factory image (I remember that 4.2.2 had 1205 BB so this should install it) from here. Also have a look here for how to return to stock. It also worked for me upgrading to 4.3.
I hope it helps

al3x1393 said:
What factory image have you tried?
I think this one can be dodged by installing the 4.2.2 factory image (I remember that 4.2.2 had 1205 BB so this should install it) from here. Also have a look here for how to return to stock. It also worked for me upgrading to 4.3.
I hope it helps
Click to expand...
Click to collapse
Hy!
This image: nakasig-jdq39-factory-0798439d.img unzipped to the directory of fastboot in c:\
I tried this:
Code:
- unpacking the .zip file
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot format userdata
(optionally: fastboot flash userdata userdata.img)
from here:
http://forum.xda-developers.com/showthread.php?p=44317341#post44317341
And it was succes! The tablet booted in, I could set it up, but there is a minor (major?) problem: it has lost 75% os the storage capacity, the storage is 6.02 GB.. it is a 32 GB 3G version...
I dont dare to upgrade now
edit: oopppsss I forgot: I made the above commands in a machine: winXP32 - 768 MB RAM - and a Blackberry USB cable!!!

bigsee said:
Hy!
This image: nakasig-jdq39-factory-0798439d.img unzipped to the directory of fastboot in c:\
I tried this:
Code:
- unpacking the .zip file
fastboot format system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format cache
fastboot format userdata
(optionally: fastboot flash userdata userdata.img)
Click to expand...
Click to collapse
It sounds like one or more partitions are not mounted by android (either they are not formatted properly or i don't know, but android can't see it/them).
I think you can try erasing them at all...however when I upgraded it to 4.3 I used that flashall.bat (or something like that) you can find inside the archive downloaded from Google website. You can try that too, it's basically the same thing as typing them by yourself, but you know...just to be sure everything it's ok.
Also from what i see in your code, you don't flash the radio (baseband) image at all and because of that your baseband/radio problem will persist at a further update. You formatted user data so you don't care about your files, so you can perform a full wipe and erase everything just to get things done well.
However, if you want to do it by yourself try theese full wipe instructions (OF COURSE YOU HAVE TO CHANGE bootloader-tilapia-4.23.img AND radio-tilapia-1231_0.18.0_0409.img AND image-nakasig-jwr66v.zip WITH YOUR 4.2.2 ONES (THEESE ARE FOR 4.3)):
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66v.zip

al3x1393 said:
It sounds like one or more partitions are not mounted by android (either they are not formatted properly or i don't know, but android can't see it/them).
I think you can try erasing them at all...however when I upgraded it to 4.3 I used that flashall.bat (or something like that) you can find inside the archive downloaded from Google website. You can try that too, it's basically the same thing as typing them by yourself, but you know...just to be sure everything it's ok.
Also from what i see in your code, you don't flash the radio (baseband) image at all and because of that your baseband/radio problem will persist at a further update. You formatted user data so you don't care about your files, so you can perform a full wipe and erase everything just to get things done well.
Full wipe instructions (OF COURSE YOU HAVE TO CHANGE bootloader-tilapia-4.23.img AND radio-tilapia-1231_0.18.0_0409.img AND image-nakasig-jwr66v.zip WITH YOUR 4.2 ONES (THEESE ARE FOR 4.3)):
Code:
>fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-tilapia-4.23.img
> fastboot reboot-bootloader
> fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
> fastboot reboot-bootloader
> fastboot -w update image-nakasig-jwr66v.zip
Click to expand...
Click to collapse
Thanks! I store this method but I wait a little bit more because I started a new RMA by Asus. Now I'm waiting for their answer.

bigsee said:
Thanks! I store this method but I wait a little bit more because I started a new RMA by Asus. Now I'm waiting for their answer.
Click to expand...
Click to collapse
As you wish

At least it came back from repair - from Brno - with a JOP40D FW and a working 4.2.1.
After update - to 4.2.2. - it showed an error but it could boot into the former system ... 4.2.1...
I had to reflash to the JWR66Y FW without the correct recovery...
Currently my Nexus 7 is living with a working 4.3 but without a recovery

I played with N7 a little bit. I discovered that I can only be succes if I erase boot/recovery/system/userdata and than flash these img's individually anyway I get a "booting failed" message w/o working recovery and/or android. Nor the flash-all.bat nor the bootloader/radio/update doesn't work.
Q: Philos64 wrote a super howto (here: http://forum.xda-developers.com/showthread.php?t=2175086) to flash the stock and he says: "Reboot to your recovery for confirm the install - You will see the progress bar moving. When it's done, the tab will automatically reboot into normal mode[, if your Nexus doesn't reboot itself, reboot yourself!" I never do it because of the missing recovery... Should I/can I write only the BL or radio end at the end and step into recovery to finish or levye it on the present state?

Did you tried boot into stock recovery then via fastboot?

No I didnt. I enjoyed the working system...
Tapatalk 2-vel küldve az én Nexus 7-ről

[GUIDE] Unlock Bootloader, Install Custom Recovery, and Root the Pixel C (2/4/2016)

The instructions in this guide are outdated and way more complicated than necessary. Once the official release of Android 7.0 Nougat becomes available/rooted, I will update the procedures in this thread. In the meantime, I recommend referencing this post along with the original instructions.
A massive shout out to @cheep5k8 for all the hard work he did in getting root and recovery working on the Pixel C. Please donate to him if you can. He deserves it.
Disclaimer: This will wipe your device. Backup anything important before you start. I mostly made this guide for selfish reasons. cheep5k8 has done a great job but some of the instructions are a little vague. I like being spoon fed and I wanted a resource to refer to in the future. You know the drill. If it breaks, not my problem. Post in the forums or hop onto the XDA IRC channel.
There may be more efficient ways to do this, but this will get you where you need to be. If you find any problems or have any suggestions, feel free to reply (BE VERY SPECIFIC WITH STEPS) and I will do my best to update the instructions.
Prerequisites:
ADB/Fastboot - Minimal ADB and Fastboot
ADB/Fastboot Drivers - I recommend using Wugfresh's Nexus Root Toolkit and using the full driver installation guide. Alternatively, you can install them yourself using the official Google Drivers (no installer)
An easy way to access the ADB prompt is to navigate to the directory that ADB is installed in, hold shift and right click inside the directory. This will give you an expanded right click menu that includes an option to "Open command window here." Select this option and a command prompt will open that is already in the ADB directory, saving you from having to do a bunch of cd nonsense. You can check to see if your device is recognized in ADB by typing "adb devices." If ADB and the driver are all working correctly, it should come back with something like "5A20001071 device." You can also check to make sure your device is recognized in fastboot by booting to the bootloader and typing "fastboot devices." It will show something similar.
Necessary Files:
Pixel C Recovery - Cheap5k8's Recovery -- NYCHitman's Recovery (newer)
Pixel C Root files - Download the XCeeD kernel, su.img, and SuperUser.apk
Copy these files to your directory that contains the ADB and Fastboot executables.
Device Prep:
Enable developer mode
Go to Settings > About tablet
Tap on Build Number 7 times until it says "You are now a developer"
Enable OEM Unlocking
Go to Settings > Developer options
Enable OEM Unlocking
Tap on Enable when a disclaimer pops up
Enable USB Debugging (ADB)
Go to Settings > Developer options
Enable USB debugging
Tap on OK when prompted with a disclaimer
If the ADB USB driver has been installed, you will see a popup that says "The computer's RSA key fingerprint is: xx:xx:xx:xx(blah blah)"
Check the box next to "Always allow from this computer"
Tap on OK
Unlock Bootloader:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
Input the following to unlock the bootloader:
Code:
fastboot flashing unlock
You will be prompted on the tablet screen with a warning about unlocking the bootloader.
Press the power button to unlock the bootloader.
The device will reboot and say "Bootloader is unlocked and OS verification is OFF. Device will continue booting in 30 seconds." You will also hear an audible beep. You will then see the green android with some spinny stuff. This is the userdata being formatted.
When complete, the device will boot back into the bootloader and say
Code:
Waiting for fastboot command...
Boot back into Android by inputting:
Code:
fastboot reboot
Your Pixel C will be reset, so you will need to re-enable USB debugging. Connect to your wireless network and then skip past everything else in the initial setup, as all of this setup info will be wiped again later on. Refer to the "Enable USB Debugging (ADB)" steps above to re-enable USB debugging.
Install Custom Recovery:
Open ADB prompt (see prerequisites)
Input the following:
Code:
adb reboot-bootloader
The device will now boot into the bootloader and say
Code:
Waiting for fastboot command...
With the Pixel C in the Fastboot bootloader and the recovery file in your ADB directory, input the following:
Code:
fastboot flash recovery (replace with custom recovery filename).img
Example:
Code:
C:\>fastboot flash recovery twrp-2.8.7.0-dragon-ryu-01082016-2.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
(bootloader) erasing flash
OKAY [ 0.054s]
sending 'recovery' (13760 KB)...
OKAY [ 0.349s]
writing 'recovery'...
(bootloader) writing flash
OKAY [ 0.375s]
finished. total time: 0.783s
Reboot into Recovery using the physical buttons. If you reboot the device back into Android, it will write over the custom recovery with the stock one. This will be fixed in the future.
Code:
Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
Install Root:
In TWRP, navigate to Wipe > Format Data
Type "yes" in the warning prompt and wait for the userdata partition to format. Again, this will wipe your tablet.
Press the Home button at the bottom when the format is complete
Navigate to Reboot > Bootloader to boot back into Fastboot
In the ADB prompt, flash the new kernel:
Code:
fastboot flash boot (replace with xCeeD kernel filename).img
Example:
Code:
C:\>fastboot flash boot xceed-kernel-google-dragon-02-01-2016-RC1.img
target reported max download size of 268435456 bytes
erasing 'boot'...
(bootloader) erasing flash
OKAY [ 0.064s]
sending 'boot' (6220 KB)...
OKAY [ 0.161s]
writing 'boot'...
(bootloader) writing flash
OKAY [ 0.197s]
finished. total time: 0.426s
Reboot into Android. The device may boot twice.
Code:
fastboot reboot
Reboot back into Recovery. Power + Volume down until screen turns off, keep pressing volume down to boot into Coreboot Bootloader. Navigate to Reboot into Android Recovery with volume down and then press power to select.
In TWRP, navigate to Mount and check only Data
In the ADB prompt move su.img to /data:
Code:
adb push su.img /data
Example:
Code:
C:\>adb push su.img /data
5677 KB/s (33554432 bytes in 5.772s)
In TWRP, navigate to Mount and uncheck Data
In TWRP, navigate to Reboot > System
Perform initial device setup
Once you are at the home launcher, re-enable USB debugging (Refer to Device Prep)
In the ADB prompt, install superuser.apk:
Code:
adb install Superuser.apk
Example:
Code:
C:\>adb install Superuser.apk
8612 KB/s (6227998 bytes in 0.706s)
pkg: /data/local/tmp/Superuser.apk
Success
Install Busybox from the Play Store: link
Congrats. You are now rooted (not in the Australian sense).

Big big thanks
Amazing, great job.

P.S. One thing to add, for those who bought SuperSU Pro, you can install that too from the Play Store instead of installing the APK, but at the moment, it will say that the su binary is outdated (because the xCeeD kernel comes with 2.66, but SuperSU is already at 2.67). There needs to be a somewhat better solution but it's a bit hard to come up with it.
xCeeD v1-RC4 will have SuperSU updated to 2.67, and I'm thinking of how to make it possible to flash the normal SuperSU ZIP in TWRP. I will probably modify TWRP in some way to make that possible.

Very good step by step, guide, I went through the same process myself yesterday, although without the benefit of your guide!
Just one additional suggestion I would make, especially for people who have already got things set up nicely on their device.
Before doing anything you can make a backup of your device data using adb.
I used the guide at - http://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Although you cannot guarantee everything will restore perfectly (I recommend that for important apps that have the capability - backup the settings manually and remember to copy them off the device), it certainly saved me a heck of a lot of time in putting things back exactly as they were before - and it is a lot quicker than letting google backup restore things.

Does this void the warranty?
Great job,anyway
Enviado desde mi Pixel C mediante Tapatalk

Cool, but you don't mind make put the video or pictured for guides.
Keep it up!!

there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command

Scarfacez2007 said:
there no show up wipe/ fromat data when I into in reboot into android recovery look like said no command
Click to expand...
Click to collapse
Are you booting into TWRP recovery or the stock Android recovery?

I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command

Thank you for this in depth tutorial.. GREATLY appreciated..my C will be in tomorrow just in time for RC4! Hopefully all goes smooth with this. So no need to swipe fastboot fix in twrp??

Scarfacez2007 said:
I have unlocked and I was install install custom recovery that all
---------- Post added at 01:11 AM ---------- Previous post was at 12:21 AM ----------
I just installed trwp then I into on reboot into android recovery but still no command
Click to expand...
Click to collapse
I had that too after my first attempt, I reinstalled TWRP and it worked after the second flash.
There were no errors shown either time.

The same thing - no command, though the TWRP is installed. Re-installing doesn't help at all.
UPD Just managed to do this step by manually booting into recovery without booting the ui.

I updated the instructions saying to use the physical buttons to boot into recovery immediately after writing TWRP to flash. I believe this should mitigate the issue with the device overwriting the custom recovery before the kernel is flashed.

You don't mind guide put with the video or picture?

Scarfacez2007 said:
You don't mind guide put with the video or picture?
Click to expand...
Click to collapse
I have no plans to make a video or pictures.

Finally I got rooted about time!!!! thanks oRAirwolf!!!!

I just wondering I can download Xposed 6.0.1 on my pixel c?

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
I have no idea. I would probably start a new thread in the Q&A section.

Scarfacez2007 said:
I just wondering I can download Xposed 6.0.1 on my pixel c?
Click to expand...
Click to collapse
Yep xposed works fine

How did you get download xposed with arm64 for Google Pixel C? where get it? you don't mind can find for me on link?

Problem rooting Nexus 4 on Mac OS X

I am wanting to root my old Nexus 4 because you can apparently use a USB OTG cable with it once it's rooted? I can't seem to get the damn thing rooted though!
I've been following this tutorial, as the second video is specifically for Mac users.
I've managed to unlock my boot loader, and then try to flash CWM, but whenever i reset my phone, it doesn't boot into CWM, just the normal boot screen. I've followed the video step by step and tried it multiple times, with no success.
I've also tried using these one-click methods (the One-Click ClockworkMod Recovery Toolkit version), and I can boot into CWM recovery, but then whenever I restart my phone, I loose the CWM recovery,
Can anybody help me try to root my Nexus 4 on Mac OS X. I don't mind not rooting if there is another way USB OTG can be used with the Nexus 4?

Ysh232 said:
I am wanting to root my old Nexus 4 because you can apparently use a USB OTG cable with it once it's rooted? I can't seem to get the damn thing rooted though!
I've been following this tutorial, as the second video is specifically for Mac users.
I've managed to unlock my boot loader, and then try to flash CWM, but whenever i reset my phone, it doesn't boot into CWM, just the normal boot screen. I've followed the video step by step and tried it multiple times, with no success.
I've also tried using these one-click methods (the One-Click ClockworkMod Recovery Toolkit version), and I can boot into CWM recovery, but then whenever I restart my phone, I loose the CWM recovery,
Can anybody help me try to root my Nexus 4 on Mac OS X. I don't mind not rooting if there is another way USB OTG can be used with the Nexus 4?
Click to expand...
Click to collapse
Use TWRP 3.0.0, it's up to date and supported still. The flashing process is the same as CWM: ./fastboot flash recovery twrp-3.0.0-0-mako.img Also, to boot into recovery, power off your phone and hold Volume Down+Power and it will boot into the bootloader, then use the volume buttons to select recovery and power button to boot it into recovery. I use OS X so if you need any help just quote me and I'll try to help out
Edit
If you have ADB downloaded as well in the same directory of Fastboot, you can enable USB Debugging under developer options in Settings on your N4. Type /.adb reboot recovery in Terminal whenever you want to boot into recovery, without having to do the above process that I mentioned.

After flashing recovery, boot directly into recovery after flashing using the volume and power button. Do not reboot the phone before booting into the new recovery. Also, there is no need to power off the phone before booting the new recovery for the first time.

fireball0093 said:
Use TWRP it's up to date and supported still. The flashing process is the same as CWM: ./fastboot flash recovery twrp-3.0.0-0-mako.img Also, to boot into recovery, power off your phone and hold Volume Down+Power and it will boot into the bootloader, then use the volume buttons to select recovery and power button to boot it into recovery. I use OS X so if you need any help just quote me and I'll try to help out
Edit
If you have ADB downloaded as well in the same directory of Fastboot, you can enable USB Debugging under developer options in Settings on your N4. Type /.adb reboot recovery in Terminal whenever you want to boot into recovery, without having to do the above process that I mentioned.
Click to expand...
Click to collapse
Thanks for the advice. I downloaded TWRP and booted into recovery. I then entered the following into the terminal:
Code:
A-MacBook-Pro:RootNexus4 A$ ./fastboot-mac flash recovery twrp-3.0.0-0-mako.img
sending 'recovery' (9122 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.475s]
finished. total time: 0.767s
I then changed the setting on my N4 from 'Start', to 'Recovery Mode' and pressed the power button. It seems to have booted into TWRP correctly. I then chose to restart phone as normal and got the infinite boot sequence of coloured balls swooping in-between each other...
I'm confused whats going on here...

Ysh232 said:
Thanks for the advice. I downloaded TWRP and booted into recovery. I then entered the following into the terminal:
Code:
A-MacBook-Pro:RootNexus4 A$ ./fastboot-mac flash recovery twrp-3.0.0-0-mako.img
sending 'recovery' (9122 KB)...
OKAY [ 0.292s]
writing 'recovery'...
OKAY [ 0.475s]
finished. total time: 0.767s
I then changed the setting on my N4 from 'Start', to 'Recovery Mode' and pressed the power button. It seems to have booted into TWRP correctly. I then chose to restart phone as normal and got the infinite boot sequence of coloured balls swooping in-between each other...
I'm confused whats going on here...
Click to expand...
Click to collapse
I've now tried to Reboot (through TWRP, and clicked Bootloader, but TWRP says there is no OS installed. Thats probably why I get the infinite boot loop? How can I re-install the OS? I've downloaded the factory image from Google, but can't flash it...

You can manually flash each partition to the phone using fastboot commands. This will restore the phone back to stock.
Once the phone is able to boot the stock rom, reinstall twrp, boot into twrp, and flash supersu.

[GUIDE] [ROOT] LG K7 MS330 - Concise tutorial on rooting with: ADB, TWRP and SuperSU

***MOD EDIT: BE WARNED THAT WHEN PERFORMING THESE INSTRUCTIONS, THAT ALL DATA WILL BE WIPED (FACTORY RESET) FROM THE DEVICE - THIS INCLUDES THE INTERNAL DEVICE STORAGE (INTERNAL SDCARD). YOUR EXTERNAL SD FILES, HOWEVER, ARE SAFE AND WILL NOT BE MODIFIED.***​
Hello.
I will attempt to keep this tutorial as concise as humanly possible, without the expenditure of costly applicably valid information. There are many other persons (whom I do not know) to thank for the majority of this information (from XDA Developers and other sites around the world wide web). Without further adieu: Let's begin!
The base operating system that this tutorial references is a Windows distro (I am operating on: Windows 10 Home OEM).
Target phone specs (http://www.lg.com/us/cell-phones/lg-MS330-White-k7):
Carrier: MetroPCS®[*]
[*]Make: LG K7 ("HW" or "White")
[*]Model: LG MS330
[*]Build number: LMY47V
[*]Software version: MS33010m
[*]Android version: 5.1.1
[*]Android security patch level: 2017-04-01
[*]Kernel version: 3.10.49​
Prerequisites:
A USB cable (able to transfer data)
A functional copy of Windows
An internet connection (to download the software tools)
If you opt to not download and install the stock firmware ROM (*.kdz) and LG UP (used for many things):
You are taking a great risk in the event something catastrophic occurs (no backup; Corrupted partition(s); Broken hard-key reset; etc).
The LG UP tool combined with the ROM file enables you to fully slate the drive on the phone (effectively restoring it to a manufacturers state; No partitions, no data, nothing!).
It also acts as a major fail-safe as previously iterated.
You can also (if you take the time of day) use it to create your own customized 'factory style' bloatware free, customized filled state *.KDZ ROM! Although TWRP backups should be capable of emulating this type of behavior.
The ROM is ~1GB in file size from the server (capped at ~10MB/s download rate at the time of the writing of this post). Translation: It takes a while (~30min) to download. Fortunately for me: I had it and had to use it earlier today (TWRP backup failed).
Software tools (ADB, TWRP, SuperSU, LG UP, ROM):
ADB (Android Debug Bridge): https://developer.android.com/studio/releases/platform-tools.html
TWRP (Team Win Recovery Project) v3.2.1.0: https://twrp.me/lg/lgk7.html
SuperSU (SuperUser) v2.82: http://www.supersu.com/download
LG UP Lab v1.10: https://www.mylgphones.com/download-lg-up-software
Stock ROM (MS33010i -- *.kdz): https://mega.nz/#F!sdwRDLbZ!yPOiRPv5QJS_9I4hzL4ptQ!ddJHSBhR
This will be a step-by-step process; If you skip a step: Make sure you have a good reason!
I will be assuming you have followed the links above and both downloaded and installed the appropriate software (ADB, LG UP). Keeping everything organized is key.
For instance: Create a folder on your main drive ("C" drive is common traditionally). Name this folder "Rooty." Create a short-cut of "adb.exe" and place it there. Place the SuperSU *.zip and *.kdz ROM data files in the same directory as well.
Overview of procedures:
Enable "OEM unlock"
Enable "USB debugging"
Unlock OEM bootloader
Install ("flash") TWRP
Using LG UP (after TWRP is either installed or live loaded)
Install SuperSU
Step 1) Enable developer options
Enabling developer options -- Navigate to "Settings," then to "About phone," then to "Software info," then tap on "Build number" until the dialog states: "No need, you are already a developer."
Step 1.1) Enable OEM unlock option
Traverse two levels up; Tick off "Enable OEM unlock"; Scroll down 2 options and tick off "USB debugging."
Step 2) Unlocking the OEM bootloader
Insert your USB cable to connect your desktop/laptop to your cellphone; When the dialog comes up asking for permission to debug: Accept it (OPTIONAL: Tick off the 'always allow this device'). Ensure "Media device (MTP)" option is selected (it will automatically install the drivers from your phone to your computer if enabled).
Step 2.1) Unlocking the OEM bootloader (for the not-so-technically-inclined)
Create a textfile and name it whatever you'd like (I prefer the filename: "OEM_Unlock.bat").
Copy and paste this script and simply place it in the same directory ('folder') as ADB.
Code:
REM This will reboot the phone into "bootloader" mode
adb reboot bootloader
REM This will unlock the OEM bootloader (a message will display on the starting logo afterwards)
fastboot oem unlock
REM This is just to verify that it was successfully unlocked ("unlocked: yes")
fastboot getvar unlocked
Alternatively: You can manually input the commands one at a time by typing them yourself or copying and pasting.
Step 3) Installing TWRP
You can just use ADB to directly flash the recovery partition of the ROM on the phone:
Code:
fastboot erase recovery
fastboot flash recovery C:/Android/recovery.img
You can also simply 'live boot' into TWRP (less risk of a faulty TWRP):
Code:
fastboot boot C:/Android/recovery.img
Now TWRP is installed (unless you simply loaded the image file into the phone's RAM).
Using LG UP to flash the ROM ("WIPE" every partition of the phone with TWRP; EVERYTHING will be lost:
To use LG UP: You only need to power down the phone fully (ensure it is not yet connected to the computer).
Hold the "VOLUME UP" key (do not release); Insert the USB cable. The phone should (within moments) place itself into "DOWNLOAD MODE." At which point LG UP will recognize the phone. There will be two options: "Refurbished" and "Upgrade"; Tick off 'upgrade' every time! Below that is "3 dots" which enables you to navigate (GUI) to the directory of your desired *.tot or *.kdz file. Simply hit "start" and it'll flash the phone (it usually takes ~300s or ~5m).
Step 4) Installing SuperSU
Through TWRP: Click on "Advanced"; Then click on "ADB Sideload"; Tick both the "Wipe Dalvik cache" and "Wipe cache" (these will force all APKs to be reinstalled via root level). Then slide the bar across. Return your attention to Windows.
You can just use ADB to directly sideload SuperSu onto the phone.
Code:
adb sideload C:/Android/SuperSU.zip
The final page asks if you would like to install the "official TWRP app" and also if you'd like to install it under "system" privileges (one less than root).
The end! You now have root accessible privileges through the "SuperSu" application (which contains root privilege at this point).
Alternatively to manually inputing everything by hand into ADB: I've whipped up this simple batch script for Windows:
Code:
ECHO OFF
CD\
CLS
ECHO Waiting for the device to communicate (ensure you are not in 'recovery,' 'sideload,' or 'bootloader' state)
adb wait-for-device
REM Reboots to the bootloader
adb reboot bootloader
REM Unlocks the OEM bootloader
fastboot oem unlock
REM Quick check to see if it successfully unlocked
fastboot getvar unlocked
REM Flashes (deleting the stock ROM recovery program)
fastboot erase recovery
REM Flashes (copies the TWRP custom recovery program)
fastboot flash recovery C:/Android/recovery.img
REM Loads the TWRP custom recovery program into memory (a "live boot")
fastboot boot C:/Android/recovery.img
REM Pauses execution until the phone boots into "recovery" state
ECHO Wait until the phone enters a "recovery" state...
adb wait-for-recovery
CLS
ECHO Traverse to "Advanced" then to "ADB Sideload"
ECHO Check off clearing both the Dalvik cache and cache
ECHO Press any key *after* you swipe the bar across
ECHO(
PAUSE
REM Copies over the APK to the ROM (security exploit to gain root permissions)
adb sideload C:/Android/SuperSU.zip
adb reboot
How to use the batch script file to root your phone with ADB, TWRP and SuperSU:
Place: SuperSU.zip and TWRP.img in the same directory as the ABD/fastboot executables
Modify the absolute paths and file names to your system (EG: "C:/Android/" and "recovery.img")
I hate to post this, but I feel it to be utterly important to express my deepest gratitude to all those who have posted this information that was scattered about the internet. This is my first Android or PHONE for that matter to root! It was quite the under-taking (nearly a 48 hour scourge of research). I've learned quite a bit how the Android OS works internally as a result; as well as the tool-kits that are commonly used in conjunction with modding the Android (out of the scope of this thread).
I hope this very recently updated and compiled information will help ease the suffering of another's entrance into the world of rooting Android phones. I also hope it really deepens the understanding of what they're doing (EG: The commands being utilized with abd and fastboot).
Here is a helpful link in regards to adb/fastboot:
- Quick reference to abd commands (syntax and meaning): https://developer.android.com/studio/command-line/adb.html
- Alternatively: You can use "adb help" to see a print-out of the commands and arguments (same applies to fastboot).
Happy rooting, y'all!

Thanks for the write-up!
The attached SuperSU.zip worked perfect to gain root on my K7 m1 using the adb sideload in Twrp and PC.
My bootloader I had already unlocked. Twrp, I flashed before I accomplished that feat!
Was rooted with Kingroot but wasn't satisfied with that.
Factory reset, and followed your adb sideload instructions to gain root with SuperSU.zip ..
Thanks again my friend.
Custom Roms for the K7 seem to be scarce, unless I am looking in all the wrong places.
Would be much appreciated if anyone could help me on that front?? ... Please let me know.

Good Day
With very insignificant changes to syntax used above I found this works perfectly on OSX as well.
Thanks

hi, i cant seem to unlock the bootloader. i have already enabled oem unlock and usb debuggin from settings but it always fails
Code:
PS C:\adb> adb devices
List of devices attached
ZSTSS8DUSWZD9LCE unauthorized
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot devices
ZSTSS8DUSWZD9LCE fastboot
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
FAILED (remote:
Unlock operation is not allowed
)
finished. total time: 9.294s
I should note that kingrot also failed to root
i dont know whats wrong, imma gonna try factory reset and try again
UPDATE
It seems the allow oem unlock option got disabled by itself somehow, i re enabled, tried again and unlocked succesfully
UPDATE 2
Aaaaand Bootloop, dunno what went wrong, iv'e reached step 4, flashed twrp, then tried to reboot into twrp and now im stuck in bootloop
Code:
PS C:\adb> adb reboot bootloader
PS C:\adb> fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 8.981s]
finished. total time: 8.983s
PS C:\adb> fastboot getvar unlocked
unlocked: yes
finished. total time: 0.003s
PS C:\adb> fastbot erase recovery
fastbot : The term 'fastbot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastbot erase recovery
+ ~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastbot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\adb> fastboot erase recovery
erasing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.004s
PS C:\adb> fastboot flash recovery c:/adb/lg.img
target reported max download size of 134217728 bytes
sending 'recovery' (12010 KB)...
OKAY [ 0.394s]
writing 'recovery'...
OKAY [ 0.706s]
finished. total time: 1.103s
PS C:\adb> adb reboot recovery
error: device '(null)' not found