Database Users

[Q] Formatted Nexus 10

So I had the latest version of Paranoid Android on my rooted nexus 10. The keyboard was messing up so i wanted to run a factory reset and go all the way back to stock 4.2.1. In the process I accidentally wiped both the Rom and stock from my nexus 10 leaving it with no OS and nothing but the boot-loader. If i try and go to recovery mode all i get is the android laying down with an exclamation mark in a red triangle in it's stomach or the word Google with and unlocked padlock underneath it.
Any advice/help would be amazing! Thanks!

Download the factory image from Google: https://dl.google.com/dl/android/aosp/mantaray-jop40c-factory-0d641789.tgz
If you don't have fastboot already you need that too: http://downloadandroidrom.com/file/tools/fastboot.zip
Unzip the factory image tgz I linked to with 7zip/winrar etc
Unzip the fastboot.zip contents into the folder you just extracted
open a command prompt in the folder you just unzipped (mantaray-jop40c)
Boot your device into the bootloader by holding down BOTH volume keys and the power button
Connect your Nexus 10 to your PC
At the command prompt type
fastboot flash bootloader bootloader-manta-mantalj12.img
fastboot reboot-bootloader [wait for the device to reboot back to the bootloader]
fastboot -w update image-mantaray-jop40c.zip
This will wipe, repartition and install 4.2 straight from Google back to your device.. You will be prompted to update by Google to install the 4.2.1 update shortly after you boot up.
If you didn't have Fastboot already and had to download the zip I linked to, it's highly suggested to download and install the Android SDK so you have it and more native tools at your disposal. You can do that after the fact though and optional but highly suggested if you plan on learning your device more.

Will this work even if my device WAS Android 4.2.1 JOP40D?

Jamocobi said:
Will this work even if my device WAS Android 4.2.1 JOP40D?
Click to expand...
Click to collapse
Yep.

styckx said:
Yep.
Click to expand...
Click to collapse
Awesome thanks, I'll give it a shot once the files downloaded!

You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock

styckx said:
You're welcome. You should be fine.. This will start you right back at square one w/ an unlocked bootloader. You won't have a custom recovery or anything like that but you'll be back at a good starting point if you ever want to go that route again.
If you want to lock your bootloader again. After the device boots into Android reboot back to the bootloader one more time and type
fastboot oem lock
Click to expand...
Click to collapse
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?

Jamocobi said:
Awesome. Thanks so much! Unfortunately the command prompt is just stuck on "sending 'bootloader' <1280KB>..."
It's been over 4 minutes now which doesn't seem right, any ideas?
Click to expand...
Click to collapse
How did you unlock and root this device in the first place?

styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
With the WugFresh Nexus Root Toolkit (Sorry, Can't post a link yet)

styckx said:
How did you unlock and root this device in the first place?
Click to expand...
Click to collapse
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!

Jamocobi said:
Okay so after messing around with restarting bootloader i redid the script in command prompt and it is now back to factory settings, thank you so much!
Click to expand...
Click to collapse
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...

styckx said:
Figures. I had a long post written up to help you out. ha ha.. Good on ya for figuring it out..
I'm aware of the toolkit and situations like this is why I hate them. Users press a few buttons and `magic happens'.. When that user gets in trouble they now have no idea how to reverse what they did because there is no "Undo the magic" button and they learned nothing from the initial unlocking process because some toolkit did it for them.. Nexus devices can be unlocked and flashed with Google provided tools. Now that you manually did it you probably have a better overall idea of the actual process that is taking place. The more you do it manually, the more it becomes second nature. It's not even all that complicated. It's just a different way of copying files and erasing data.
One thing.. You NEVER.. EVER.. EVER... EVER... want to do is type this
fastboot erase bootloader
^ That is the quickest and easiest way to permanently brick your device.. If anyone ever suggests you do that.. Don't...
Click to expand...
Click to collapse
Sorry about that, i was hoping you'd see it in time! You're definitely right about that, i was just worried i would totally mess it up if i did it myself but i can do that anyway with a toolkit so next time ill give it a shot without one.
Okay thanks, I'll take note of that one for sure! Really appreciate the help, thought i was doomed! haha!

You're welcome man.. It's no fault of your own for using the toolkit. To new users they're attractive and promise quick results.
Side note. It's extremely, insanely, stupidly hard to permanently screw up a Nexus device by flashing. There is always a way back from `the grave'.
Take care

Possible way to save any bricked Nexus device!

Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!

That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N

So is this usable in all situations? If yes then should download it & store it safely

Interesting thing, can this update bypass factory reset protection?

iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.

This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.

This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/

flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you

Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:

mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?

holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).

mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.

holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.

TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .

atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face

TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939

just want to ask would this method work if the phone has not been authorized to a specific PC ?

iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...

LG aristo 2 (K8 2018)

Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well

I just got this phone. Let me know how what happens please.

tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.

I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool

attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.

tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?

Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2

Hmm and you flashed the twrp that was for the aristo right?

Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?

you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?

The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.

I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.

Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.

We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.

The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?

@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App

brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.

brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?

t510 please help im pulling my hair out

ok long story short i have a sm t510 32gb, i reflashed it with stock rom and its now showing as a 16gb, i have tried several pit files but all seem to be 16gb. i have tried several roms all seem to be 16gb, i have ticked and unticked format partition in odin but always 16gb after restore, i have tried to clear cache, factory reset etc etc, i even loaded the pit file into pit magic but was at a loss after this as none of it made any sense, i dont want to install twrp if i can help it.
strange thing is they dont even sell 16gb version of this tablet they only sell 32,64,128 so really any of the firmwares should be ok but sadly not in this case.
anyone know what im doing wrong?

lukeeyboy7 said:
ok long story short i have a sm t510 32gb, i reflashed it with stock rom and its now showing as a 16gb, i have tried several pit files but all seem to be 16gb. i have tried several roms all seem to be 16gb, i have ticked and unticked format partition in odin but always 16gb after restore, i have tried to clear cache, factory reset etc etc, i even loaded the pit file into pit magic but was at a loss after this as none of it made any sense, i dont want to install twrp if i can help it.
strange thing is they dont even sell 16gb version of this tablet they only sell 32,64,128 so really any of the firmwares should be ok but sadly not in this case.
anyone know what im doing wrong?
Click to expand...
Click to collapse
They do MAKE a 16gb tablet. Mine is 16gb. But it does say "Not for Sale" on the back. They were intended to be used as store demo tablets.

lewmur said:
They do MAKE a 16gb tablet. Mine is 16gb. But it does say "Not for Sale" on the back. They were intended to be used as store demo tablets.
Click to expand...
Click to collapse
thanks for the response, thats exactly what these ones i have here, not for resale, they have demo mode on and i dont know the password to exit it. so i reflashing them with stock firmwares from sammobile. but before i wipe them PLUS also on the labels on the boxes they are 32gb, but once restored they are coming up as 16gb
i have tried several different roms from different locations around the web but all restore to 16gb.
does anyone know what i change in the pit file to make the 16gb partition 32gb?

lukeeyboy7 said:
thanks for the response, thats exactly what these ones i have here, not for resale, they have demo mode on and i dont know the password to exit it. so i reflashing them with stock firmwares from sammobile. but before i wipe them PLUS also on the labels on the boxes they are 32gb, but once restored they are coming up as 16gb
i have tried several different roms from different locations around the web but all restore to 16gb.
does anyone know what i change in the pit file to make the 16gb partition 32gb?
Click to expand...
Click to collapse
It isn't a matter of partitioning. The "Not for Sale" model only has a 16gb chip. I'm assuming that Samsung came up with the idea of making a "Not for Sale" model to use up their inventory of 16gb chips that people would no longer buy in retail tablets.
As to "demo" mode, I don't recall even having it on mine. But in any case, installing any custom ROM should get rid of it. There is no "demo mode" in custom ROMs.

I also have one of these demo units, same model. I cannot use Odin to flash any firmware to it; I get a '0 success / 1 failed' message at the end. I am also using a firmware from SamMobile. How can I flash it? Also, OP, you were probably provided with a display box to store the tablet in, which almost certainly isn't the box for the demo device you have. My tablet has never been flashed, and it says 16GB as well.
Edit: Also, mine is SM-T510X. In other words, it's European.

Maq47 said:
I also have one of these demo units, same model. I cannot use Odin to flash any firmware to it; I get a '0 success / 1 failed' message at the end. I am also using a firmware from SamMobile. How can I flash it? Also, OP, you were probably provided with a display box to store the tablet in, which almost certainly isn't the box for the demo device you have. My tablet has never been flashed, and it says 16GB as well.
Edit: Also, mine is SM-T510X. In other words, it's European.
Click to expand...
Click to collapse
Mine is also an SM-T510X. As far as I know, the X only means it is the "Not for Resale" model. I've flashed several XAR stock versions on it with no problems. I think it is much more likely that you are doing something wrong rather a problem with the tablet. I've also flashed the BTU version for the UK when Samsung hadn't rolled out the version I wanted for the U.S.
Please tell my what you've succeeded in doing so far. Is the bootloader unlocked? Have you turned on Dev Mode and enabled OEM? What version of the stock ROM do you currently have?

lewmur said:
Mine is also an SM-T510X. As far as I know, the X only means it is the "Not for Resale" model. I've flashed several XAR stock versions on it with no problems. I think it is much more likely that you are doing something wrong rather a problem with the tablet. I've also flashed the BTU version for the UK when Samsung hadn't rolled out the version I wanted for the U.S.
Please tell my what you've succeeded in doing so far. Is the bootloader unlocked? Have you turned on Dev Mode and enabled OEM? What version of the stock ROM do you currently have?
Click to expand...
Click to collapse
It is OEM locked, and there is no option under Developer Options for it, nor any option when I power on holding Volume Up. The currently installed ROM is T510XXXU1ASCC, and I'm trying to install the only firmware available for it on SamMobile, T510XXU2ASH2. I also cannot run fastboot, and Odin mode (plug up to PC while holding volume buttons) gives an error when trying to flash a custom recovery (blocked by OEM lock). The bootloader cannot be accessed at all, and attempting to load it puts the tablet in a non-Odin download mode. When trying to flash a firmware in this mode, I get "Please get the approval to use factory binaries (pit)".

Maq47 said:
It is OEM locked, and there is no option under Developer Options for it, nor any option when I power on holding Volume Up. The currently installed ROM is T510XXXU1ASCC, and I'm trying to install the only firmware available for it on SamMobile, T510XXU2ASH2. I also cannot run fastboot, and Odin mode (plug up to PC while holding volume buttons) gives an error when trying to flash a custom recovery (blocked by OEM lock). The bootloader cannot be accessed at all, and attempting to load it puts the tablet in a non-Odin download mode. When trying to flash a firmware in this mode, I get "Please get the approval to use factory binaries (pit)".
Click to expand...
Click to collapse

no i have about 40 of them and all boxed in store demo white box and serial numbers match boxes so they are 100% 32gb. even says so when goto setting in store mode but once reset they 16gb.
has to be the rom.
sammobile has many roms depending on location.
as for yours not taking a flash you have to have usb connected to odin. then hold power plus vol up and vol down until unit resets{black screen} then release only power until download mode shows then press vol up to continue then reflash.
also all these are t510x so yeah i also believe the x stands for retail mode.
i also believe the pit file located is CSC[if memory is serving me correctly} is responsible for structuring the partition and hence the problem im having with the incorrect storage problem

lukeeyboy7 said:
no i have about 40 of them and all boxed in store demo white box and serial numbers match boxes so they are 100% 32gb. even says so when goto setting in store mode but once reset they 16gb.
has to be the rom.
sammobile has many roms depending on location.
as for yours not taking a flash you have to have usb connected to odin. then hold power plus vol up and vol down until unit resets{black screen} then release only power until download mode shows then press vol up to continue then reflash.
also all these are t510x so yeah i also believe the x stands for retail mode.
i also believe the pit file located is CSC[if memory is serving me correctly} is responsible for structuring the partition and hence the problem im having with the incorrect storage problem
Click to expand...
Click to collapse
I get the same error with this method - "Please get the approval to use factory binaries (pit)".

lukeeyboy7 said:
no i have about 40 of them and all boxed in store demo white box and serial numbers match boxes so they are 100% 32gb. even says so when goto setting in store mode but once reset they 16gb.
has to be the rom.
sammobile has many roms depending on location.
as for yours not taking a flash you have to have usb connected to odin. then hold power plus vol up and vol down until unit resets{black screen} then release only power until download mode shows then press vol up to continue then reflash.
also all these are t510x so yeah i also believe the x stands for retail mode.
i also believe the pit file located is CSC[if memory is serving me correctly} is responsible for structuring the partition and hence the problem im having with the incorrect storage problem
Click to expand...
Click to collapse
All I know is that on the two 510X tablets I bought, both came with stock ROMs that were not "demo mode" and they both had only 16gb. Could it be that the "demo" ROM only reports 32gb because that is what the tablets the store is selling have? IOW, the ROM is faking having 32gb when, in reality, they only have 16gb? If you have 40 of them, try taking a new one that is still "reporting" 32gb and see if you can actually load data that exceeds 16gb.
BTW, I notice that you haven't said if you have unlocked the bootloader on the tablets you are trying to flash. Take note that that is NOT the same thing as enabling OEM. Older Samsung tablets did not have locked bootloaders but the current models do., If the bootloader is unlocked, you get an extra nag screen when you turn on the tablet, warning that your tablet is "unsafe".

lewmur said:
BTW, I notice that you haven't said if you have unlocked the bootloader on the tablets you are trying to flash. Take note that that is NOT the same thing as enabling OEM. Older Samsung tablets did not have locked bootloaders but the current models do., If the bootloader is unlocked, you get an extra nag screen when you turn on the tablet, warning that your tablet is "unsafe".
Click to expand...
Click to collapse
If you're talking to me, I cannot unlock the bootloader without OEM unlocking. I want to know how to OEM unlock.
Edit: None of the things posted here worked for me, likely because it's a demo unit: https://forum.xda-developers.com/t/guide-unlock-t510-bootloader.3929459/

Maq47 said:
If you're talking to me, I cannot unlock the bootloader without OEM unlocking. I want to know how to OEM unlock.
Edit: None of the things posted here worked for me, likely because it's a demo unit: https://forum.xda-developers.com/t/guide-unlock-t510-bootloader.3929459/
Click to expand...
Click to collapse
The bootloader CAN be unlock without OEM enabled. All emabling OEM (and it is "enabling" and not unlocking OEM) does is prevent the FRP lock from engaging. So long as you know the Google Account login and password, the FRP lock is meaningless. But you DO have to have Dev mode enabled. And if you mean that your tablet is a "Not for Sale" model, then so are my two and I've succeeded in unlocking both.
BTW, telling us "nothing" works, is meaningless. Instead, tell us what EXACTLY have you attempted and what were the results. Also, have you setup the tablet with a Google Account?

lewmur said:
The bootloader CAN be unlock without OEM enabled. All emabling OEM (and it is "enabling" and not unlocking OEM) does is prevent the FRP lock from engaging. So long as you know the Google Account login and password, the FRP lock is meaningless. But you DO have to have Dev mode enabled. And if you mean that your tablet is a "Not for Sale" model, then so are my two and I've succeeded in unlocking both.
BTW, telling us "nothing" works, is meaningless. Instead, tell us what EXACTLY have you attempted and what were the results. Also, have you setup the tablet with a Google Account?
Click to expand...
Click to collapse
But I cannot flash a custom recovery without OEM unlocking it.
Maq47 said:
It is OEM locked, and there is no option under Developer Options for it, nor any option when I power on holding Volume Up. The currently installed ROM is T510XXXU1ASCC, and I'm trying to install the only firmware available for it on SamMobile, T510XXU2ASH2. I also cannot run fastboot, and Odin mode (plug up to PC while holding volume buttons) gives an error when trying to flash a custom recovery (blocked by OEM lock). The bootloader cannot be accessed at all, and attempting to load it puts the tablet in a non-Odin download mode. When trying to flash a firmware in this mode, I get "Please get the approval to use factory binaries (pit)".
Click to expand...
Click to collapse
I want to flash TWRP to it in order backup the system partitton in order to extract the pit file, which is required for my device in order to flash a stock ROM.
Maq47 said:
It is OEM locked, and there is no option under Developer Options for it, nor any option when I power on holding Volume Up. The currently installed ROM is T510XXXU1ASCC, and I'm trying to install the only firmware available for it on SamMobile, T510XXU2ASH2. I also cannot run fastboot, and Odin mode (plug up to PC while holding volume buttons) gives an error when trying to flash a custom recovery (blocked by OEM lock). The bootloader cannot be accessed at all, and attempting to load it puts the tablet in a non-Odin download mode. When trying to flash a firmware in this mode, I get "Please get the approval to use factory binaries (pit)".
Click to expand...
Click to collapse
lukeeyboy7 said:
no i have about 40 of them and all boxed in store demo white box and serial numbers match boxes so they are 100% 32gb. even says so when goto setting in store mode but once reset they 16gb.
has to be the rom.
sammobile has many roms depending on location.
as for yours not taking a flash you have to have usb connected to odin. then hold power plus vol up and vol down until unit resets{black screen} then release only power until download mode shows then press vol up to continue then reflash.
also all these are t510x so yeah i also believe the x stands for retail mode.
i also believe the pit file located is CSC[if memory is serving me correctly} is responsible for structuring the partition and hence the problem im having with the incorrect storage problem
Click to expand...
Click to collapse
Maq47 said:
I get the same error with this method - "Please get the approval to use factory binaries (pit)".
Click to expand...
Click to collapse
I have gone through everything you have suggested, basically. I cannot flash any ROM without the pit file, I cannot get the pit file without dumping the system partition, I cannot dump the system partition without a custom recovery, I cannot flash a custom recovery without OEM unlock (nor can I run fastboot commands without unlocking the bootloader, and the unlock bootloader option won't appear without OEM unlock; I have looked into this already), and I cannot OEM unlock the usual way due to it being a demo unit (the instructions for OEM unlocking on this model say it is in Developer Options, and it isn't, even after doing the 'trick' here: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/ )
It appears that I can ONLY do any other step AFTER I disable OEM lock. THERE IS NO OTHER WAY. I want instructions to OEM unlock this demo tablet that work on demo units specifically.

Maq47 said:
But I cannot flash a custom recovery without OEM unlocking it.
I want to flash TWRP to it in order backup the system partitton in order to extract the pit file, which is required for my device in order to flash a stock ROM.
I have gone through everything you have suggested, basically. I cannot flash any ROM without the pit file, I cannot get the pit file without dumping the system partition, I cannot dump the system partition without a custom recovery, I cannot flash a custom recovery without OEM unlock (nor can I run fastboot commands without unlocking the bootloader, and the unlock bootloader option won't appear without OEM unlock; I have looked into this already), and I cannot OEM unlock the usual way due to it being a demo unit (the instructions for OEM unlocking on this model say it is in Developer Options, and it isn't, even after doing the 'trick' here: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/ )
It appears that I can ONLY do any other step AFTER I disable OEM lock. THERE IS NO OTHER WAY. I want instructions to OEM unlock this demo tablet that work on demo units specifically.
Click to expand...
Click to collapse
WILL YOU PLEASE READ WHAT I WROTE. FORGET ABOUT OEM!!! Do you have a Google Account setup?? What happens when you go to /Settings/About and tap Build Number 7 times?

Maq47 said:
But I cannot flash a custom recovery without OEM unlocking it.
I want to flash TWRP to it in order backup the system partitton in order to extract the pit file, which is required for my device in order to flash a stock ROM.
I have gone through everything you have suggested, basically. I cannot flash any ROM without the pit file, I cannot get the pit file without dumping the system partition, I cannot dump the system partition without a custom recovery, I cannot flash a custom recovery without OEM unlock (nor can I run fastboot commands without unlocking the bootloader, and the unlock bootloader option won't appear without OEM unlock; I have looked into this already), and I cannot OEM unlock the usual way due to it being a demo unit (the instructions for OEM unlocking on this model say it is in Developer Options, and it isn't, even after doing the 'trick' here: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/ )
It appears that I can ONLY do any other step AFTER I disable OEM lock. THERE IS NO OTHER WAY. I want instructions to OEM unlock this demo tablet that work on demo units specifically.
Click to expand...
Click to collapse
The instructions ALWAYS say that the first thing you SHOULD do is "enable OEM". What the instructions DON'T say is that enabling Developer Mode, which you need to do in order to enable OEM, is what's really important. As I said, not enabling OEM will only require you to enter the Google Account login and password after a "Factory Reset".
edit: Where did you get the idea that you need the pit file? If you think that will give you 32gb, then I give up. You're asking the impossible.

Maq47 said:
But I cannot flash a custom recovery without OEM unlocking it.
I want to flash TWRP to it in order backup the system partitton in order to extract the pit file, which is required for my device in order to flash
Click to expand...
Click to collapse
You do NOT need a pit file. You are getting that message because you are attempting to flash without having unlocked the boot loader. NOBODY has EVER been required to have a pit file in order to flash this tablet via Odin. But you don't appear to want to accept that other people might know what they are talking about.

lewmur said:
WILL YOU PLEASE READ WHAT I WROTE. FORGET ABOUT OEM!!! Do you have a Google Account setup?? What happens when you go to /Settings/About and tap Build Number 7 times?
Click to expand...
Click to collapse
Yes, I do have a Google account linked, and YES, I have been into Developer Options - I even referenced them TWICE in my quoted posts. And NO, there is no 'OEM unlock' option in Developer Options, and YES, I have USB debugging enabled, with my PC set as allowed, and NO, fastboot is disabled, so I cannot send commands. Is that enough information?

Maq47 said:
Yes, I do have a Google account linked, and YES, I have been into Developer Options - I even referenced them TWICE in my quoted posts. And NO, there is no 'OEM unlock' option in Developer Options, and YES, I have USB debugging enabled, with my PC set as allowed, and NO, fastboot is disabled, so I cannot send commands. Is that enough information?
Click to expand...
Click to collapse
It's a start. I didn't go back and read all of your previous post. I just answered your last one, so that's all the info I had.
So, you now have two options. First, make sure wifi is connected and Dev mode is still enabled. If there is no OEM enable option, then just reset the tablet. That should get you out of demo mode. Or, go directly to unlocking the bootloader. Either should work because unlocking the bootloader will trigger a factory reset.

lewmur said:
It's a start. I didn't go back and read all of your previous post. I just answered your last one, so that's all the info I had.
So, you now have two options. First, make sure wifi is connected and Dev mode is still enabled. If there is no OEM enable option, then just reset the tablet. That should get you out of demo mode. Or, go directly to unlocking the bootloader. Either should work.
Click to expand...
Click to collapse
I don't want out of demo mode, I want to flash a stock ROM. Seriously, please read all of my posts. I have explained everything you can possibly think of.

[HELP] Unlock bootloader.

Asus' unlock tool for M1 is dead (network error, guess they just cut the line for older models). Attached one I had in my backup from who knows how long ago, since I couldn't find any working links anymore.
Trying unlock tool for newer devices throws "Device model is not supported".
Dev. menu option for OEM Unlock is not available in neither of "official" images.
Max Pro's unlock doesn't work for this device.
So am I really stuck with Android 10 Beta release? I guess it is kind of "win" considering this release isn't completely bloated by Asus, but it would still be nice to get TWRP and Lineage on it. Not to mention I really wanted to give the Postmarket try on this device.
I'm more than willing to be lab rat if anyone wants to try.. stuff.. on my device, at this point I wouldn't even mind if it got bricked in progress.

Alright I have not given up on this, yet. I've stumbled upon post from one of the Asus' moderators on their forums:
For ZB555KL, there will no longer be any system updates and maintenance (including server).
Sorry for any inconvenience it may cause.
Click to expand...
Click to collapse
What this means is there is no official way to unlock this phone anymore, as their unlock app has nothing to communicate with.
In the same thread, another user posted this:
I dont know if you are still looking for this but after working on it for hours what you are looking for is:
in fastboot mode type:
fastboot oem enable-unlock-once
will unlock the bootloader for you until the phone is reset. Just have to do it everytime you reboot back into fastboot.
Also if you're flashing recovery, these other 2 commands may prove useful:
fastboot oem reboot-recovery
fastboot oem reboot-recovery-wipe
Cheers!
Click to expand...
Click to collapse
Indeed using this, I was able to flash recovery. Multiple actually: TWRP, stock from step 3 of the post, OrangeFox, stock again.
Why? Well, booting into any recovery leaves me hanging on black screen.
I've tried TWRP, OrangeFox. Nothing. I have found stock recovery image as well, which I have flashed. Got black screen again. BUT. Thanks to the stock recovery image I've figured out it was actually working, since after pressing some buttons randomly (kind of stupid, I know, but I though its bricked at that point anyway) I've managed to wipe data and was presented with fresh startup. I'm thinking both TWRP and OrangeFox worked as well, its the screen that doesn't want to show things for some reason while in recovery.
So if any of you got any ideas why would any recovery present me with blank screen and how should I deal with it, I'm all ears. Or eyes..