Database Users

Help an idiot flash a factory image

So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??

You can't use adb commands in fastboot. You should use fastboot commands and flash the factory image
Sent from my Nexus 5

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
Well, I had a serious issue with something similar, after trying to update (not flash the factory image) to KitKat it produced an error and now it's bootlooping and, worse, my computer won't recognize the device, so I can't flash the factory image whatsoever. Your problem is much more light, as your computer is actually recognizing the device. What I'd suggest is using the Nexus Root Toolkit by WugFresh. Yes, I know, a lot of people here don't like using it but it's extremely useful when you have drivers issues.
It's actually a pretty straight forward procedure, you install the toolkit and it will ask you for your device model, android version, etc., then take you through the process of updates and stuff. Then, on the main window, you have this wizard "Full Driver Installation Guide" that will give you 4 ways to get your device working. You can find the Toolkit here: http://www.wugfresh.com/nrt/. Good luck!

I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
It's also difficult when trying to assist somebody... they're using the vocabulary of toolkits (which I'm not familiar with)... and I'm going on about fastboot... which they don't understand. It's like there are now two different languages... TOOLKIT and FASTBOOT.
Makes it very difficult to assist people.
Maybe I should have a tinker with Wugfresh... if for no other reason than to at least get an insight into how these things work.
Rgrds,
Ged.

The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5

Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.

GedBlake said:
So an edit box where you could be prompted to type in things like fastboot flash recovery recovery.img... interesting idea... sort of walks you through the process, but doesn't obsessively hold your hand, where you don't learn anything.
I suspect most people just have problems with drivers, because, let's face it, fastboot and ADB aren't exactly difficult to use... unless people have difficulty understanding command lines in these GUI driven days, where everything is a simple menu or button click away... kind of sad really.
Rgrds,
Ged.
Click to expand...
Click to collapse
Basically yeah.
I have a feeling a good portion of the hesitation comes from the command line being scary to most people.
Sent from my Nexus 5

In the tgz file you download there is a 'flash-all.bat' file that does everything for you. If you open it in notepad, you see exactly what it does and in what order.
Yes, drivers are probably the issue, they were for me at least. I ended up using NRT (wugs toolkit) to install drivers (and root later, but that's a new topic)
Code:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
This is a Google way to flash the factory image.
---------- Post added at 10:02 PM ---------- Previous post was at 09:59 PM ----------
Pirateghost said:
The concept of the toolkit is great. It's the implementation and use of it that is horrible.
I think a toolkit should walk you through the actual steps and force you to type in the commands. You select an option of what you want it to do, it tells you what to type step by step to achieve said goal, and checks that you don't type in the wrong thing for the option you selected.
Unfortunately I don't think there is a market for that when you can get everything 'one clicked' for you.
Sent from my Nexus 5
Click to expand...
Click to collapse
The idea is great, try writing it
I'm sure it'll be greeted with appreciation.

Tones1971 said:
So i decided a few days ago to try and flash a factory image for kitkat on my N7. But i downloaded the image for the wrong device. the script has wiped recovery and system etc. The N7 now just boots to bootloader.
i got the proper factory image to flash, but i cannot get the device recognized on the pc running Windows 7 now. its showing as Other Devices / Android. I did install the drivers from the SDK and it now appears as Android ADB Interface. However ADB is still not recognizing it. I have done adb devices but nothing is found.
Any help, it is fixable isnt it??
Click to expand...
Click to collapse
As long as you can still boot into bootloader mode, it is still fixable. Try reinstalling fastboot drivers.

Pirateghost said:
I vote we ban all talk of toolkits. 99.9% of the help threads around here start with, "I was using/used x toolkit and now my device won't boot."
What happened to people learning about their devices?
How about learning how to fix your problems, rather than compound them by not understanding what you are doing? How about if you don't have the capacity to learn it, you leave it the F alone?
Sent from my Nexus 5
Click to expand...
Click to collapse
Yeah, because that was really helpful to him. I didn't tell him to use the toolkit to flash, root, unlock, or anything of the sort. For drivers issues, I do recommend (and will continue to do so) using the toolkit when official drivers don't work, because it has helped me a lot in the past, but I haven't used it to flash anything.

Download the image for your device and extract it into a folder
Download the zip below and move the files into the folder you created above
http://forum.xda-developers.com/showthread.php?t=1484407
Switch device off. Hold volume down and turn it back on, so it's in fastboot mode
Plug device into computer
Run "flash-all.bat" in the system image folder you extracted first

Want to thank everybody for their replies. Have had a family emergency so havent had a chance to try any suggestions, but didnt want to just ignore the thread i started.

Nexus 10 (Manta) Help Thread - Ask Your Questions Here!

Samsung/Google Nexus 10 Help Thread!
mantaray​
Welcome to the Nexus 10 help thread! You can ask all questions here without the need of background knowledge. This thread is dedicated to solve users problems, so if you don't want to start a new thread for your question, ask it here. Members ready to help will be monitoring this thread and provide answers as soon as possible. For a list of supporters, see here:
Current List of Supporters@demkantor - All Things Nexus - adb & fastboot expert!
@lj50036 - GitHub Expert and All Around Android Guy!
@rirozizo - Battery Guru and Android Know It All!
@XxLordxX - The Unbricker!​
Click to expand...
Click to collapse
Supporters: If you want to be put on or off the list, just send me a PM!
To those seeking help: Please don't bombard the supporters with PMs asking for help. Instead, ask your question here in the thread so others can benefit from the solution to your problem as well. If you want to be sure someone particular gets notified of your question, put his / her username directly after an @ like above. Also, if you have ROM related questions, post in the relevant ROM Q&A thread (if there is one) or directly in the ROM development thread. If you are not eligible for posting there, you may post here. And Please Read The 2nd & 3rd Post Of This Thread Before Posting! Thank you!
ROM developers: Please read this. Consider if you want to have a ROM specific help thread or not, if not, most likely questions about your ROM will be asked here if the users aren't eligible for posting in development section.
To all of you: Remember the Rules and the Forum Etiquette

Knowledge is Power!
This section is not meant to offend but rather inform XDA members, please read, understand and abide by what is said in this post... you will never be called a n00b if you do!
First Read This:
~~~~This alone will save you - thanks Tony Stark~~~~
How to post your problem or question
This isn't really complicated but the more you know the more likely you can find your own answer.
But we are here to help! So the more information you give us, the better/faster we may help you!
Step One
Have you searched for the answer to your problem/question?
If not do this first, both the search button in the XDA forums and Google work wonders.
At least attempt to show you did a little research before you scream help or this ROM is garbage, Not searching or just simply complaining will get you ignored EVEN IF YOU WRITE IN ALL CAPS
All questions belong in Q&A Forum All General Phone discussion in General NEVER post random problems in Developers section
Step Two
So you have searched for your answer and can't find it, that's okay, it happens to all of us. But before you create a new thread seek out a similar one (in the proper forum for you device) and ask there - or here.
You may think a new thread is better but in truth people look at the old ones just as much, and keeping all similar questions in one thread helps to elevate congestion and makes the next guys search a ton easier.
Step Three
Know what to post. This means explain your problem as best you can (dont write a book, just not "help my phone is possessed by demons" this is not helpful)
So this means explain all about your phone, boot into your bootloader and write down all from that screen within your post. Are you rooted? Explain where your troubles began and what you have tried to do to fix it.
Give details as much as possible, this often will include a logcat. Which there are many ways to get, learn how to before you have a problem.
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg ; adb logcat -b system -b radio -b events -b main
Code:
cat /proc/last_kmsg
Also read THIS or maybe try THIS
Use pastebin or codewraps around your logcat ( # sign from above)
Obviously every problem and question will require different information, but the more you give the better chance someone can help you.
Step Four
Wait for your answer, do not post the same question in ten threads, one will do. While you are waiting keep searching for your own answer.
When someone gives you help say thank you (with the thanks button preferably - don't make a post that just says thanks... nope, never)
Even if you don't like the answer be grateful someone took time from their day to try and help, If you think it's bad advice maybe reiterate your question and politely ask for a clearer or better explanation to the solution.
Once you have an answer
Edit first post to add the fix. If there was no fix maybe explain why there is no fix in first post.
This will help others searching for a similar problem later. Make sure your helper was thanked as well.
*Remember ROMs, Kernels, etc, may be posted in the developer section, basic questions shouldn't be in those threads. If you must add something, like a bug report, be sure to add a logcat or you man not be helped.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Again, please understand that no one here is paid, we are here to learn and we help for fun. so please be respectful...

Quick Tips!
Okay, so if you look through the Q&A thread here the number one issue that keeps popping up is "Help Bootloop!" and "Help I Think it's Bricked!"
So here is a quick guide that will most often fix these issue (90% of the time anyway)
First things first.... Drivers
Now many of you have these installed, so if you can connect your device to PC through USB and are able to communicate with adb and fastboot just skip this.
If however you can not, then you need to download appropriate drivers for Windows.
You can get these through the Adroid SDK if you already have this
Or direct from the OEM following the link HERE
Or some say having the Naked Drivers works best, so try HERE or HERE or HERE
If you need help installing these then see the next chunk on adb/fastboot or feel free to ask here as well!
*Linux users just need the android rules set up, see fastboot link for how to...
Click to expand...
Click to collapse
Click to expand...
Click to collapse
So after drivers are up... Fastboot!
Well here is many's big fear, but fear not as the terminal is not that scary!
For an in depth explanation on how to use fastboot, I highly suggest reading through THIS
It will have all you need to know and if there are any further question please feel free to ask here or in the fastboot thread.
If you have any issues running fastboot (or adb) commands, please copy and paste all input/output from terminal/cmd here so one of your helpers can assist better.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can connect to PC and you know the commands.. but what to flash?
For the most part we want to use the stock firmware found here (some OTAs HERE for another use)
Download the latest for mantaray (currently 4.4.2-(KOT49H)
Now check MD5sum or sha1 for a match (Linux use terminal, windows use THIS)
If all is good lets extract the contents (I prefer 7zip but whatever)
So if all of your prep work is a success then when you type
Code:
fastboot devices
Into a terminal/CMD you will see your serial number
If not be sure you are in bootloader mode (power on while holding volume +)
Also have a high quality USB cable if not the one that came with your device
*Still have issue, ask in this thread!
If you have a locked bootloader it may be wise to
Code:
fastboot oem unlock
Then follow the below info, if you don't want to unlock your tablet just run the flash-all.bat to get similar results
And now you have a bunch of images, lets erase and flash so we will be oh so clean!
*have everything backed up first! this will erase your tablet!
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
now after we cleaned things up, lets flash back to stock!
Code:
fastboot flash bootloader nameofbootloader.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
(Everything should be named accordingly except for bootloader, so change this command)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Congrats! You can reboot to a functioning tablet!
Some quick notes:
If you want a custom recovery, fell free to instead flash latest TWRP or CWM or whatever.
You do not need to use stock recovery for the above to work, but you will need your custom recovery in a .img
Similarly if you want a custom ROM instead of stock you can do this, but only if your dev supplies you with the system.img, if not just boot to recovery, make a nandroid, wipe all, flash custom ROM and gapps through adb sideload.
If you still have a bootloop or a "brick" then ask us here and someone will be glad to give you personal assistance.
Or for real time help you can see if anyone is at ##Manta_Help_IRC on freenode
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Anything I missed feel free to ask in this thread!
Happy Flashing!

Tech Specs and More!
Want To Know More About Your Tablet
GENERAL INFO
GSM ARENA
Factory Images "mantaray" for Nexus 10
AOSP
Click to expand...
Click to collapse

Quick Linux/Unix Rooting Guide
First of all, you need to have Fastboot and ADB. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now follow the instructions on your tablet screen. As soon as your bootloader is unlocked the device will reboot, so you'll now download the recovery and the Superuser.
Get the TWRP from here (download the .img file): http://www.teamw.in/project/twrp2/128
Get the SuperSU from here: http://download.chainfire.eu/396/SuperSU/UPDATE-SuperSU-v1.94.zip
Click to expand...
Click to collapse
Copy SuperSU to your device internal memory (that's probably empty now) and rename the .img file of TWRP to recovery.img. Now enable USB debugging again (it's explained above lol) and replug the tablet on your PC. Time for typing again! (Please, open the terminal in the folder where the recovery.img is located).
Code:
adb reboot bootloader
Wait for it to reboot, and then type:
Code:
sudo fastboot boot recovery.img
(If you want to install the recovery permanently in the device, type 'sudo fastboot flash recovery recovery.img' before issuing the command above).
Now you probably see a screen like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click in Install and select the SuperSU zip that you copied to your tablet internal memory earlier. When the flash is complete, reboot the tablet and congratulations! You're rooted :victory:.
Hope this helps anyone who may need it!
Click to expand...
Click to collapse
Quick Linux/Unix Restoring to Stock Guide
So you've decided that you don't want root anymore or you did something and want to restore to stock? That's not a hard thing to do! Just follow these steps and you'll be fine.
First you need to have adb and Fastboot ready. To do as such open your command line and type:
Code:
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/fastboot
wget http://www.undergroundandroid.com/developers/xLordAIOx/bin/adb
Now that you have both files, you need to setup them to be able to use. As you're an Unix user you'll probably get what I'll do here, you can do it slightly different, but this way was the easiest IMO, also it makes the procedure for next times using adb and fastboot easier. Type the following:
Code:
sudo mv fastboot /usr/bin/fastboot
sudo mv adb /usr/bin/adb
sudo chmod 755 /usr/bin/fastboot
sudo chmod 755 /usr/bin/adb
Now that you have adb and fastboot set up it's time to start the real thing. First of all, make sure to backup your device, as everything will be lost in this procedure! First you need to unlock your device bootloader (if it is already unlocked, skip this part). Please, go to settings, "About Device" and click multiple times "Build Number", a new tab will appear in settings, called "Developer Options", go there and enable USB Debugging. Now plug your Nexus 10 on your PC and type this to check if your device was recognized:
Code:
adb devices
If something came up it was successfully recognized and you can follow up :victory:, but it nothing appeared you may need to check this:
http://rootzwiki.com/topic/258-udev-rules-for-any-device-no-more-starting-adb-with-sudo/
When you get your device recognized do the following:
Code:
adb reboot bootloader
Wait for the device to reboot, when it turns on again, you'll type the following:
Code:
sudo fastboot oem unlock
Now you'll follow the instructions on screen. When your device is unlocked, you'll have to download the stock firmware you want from one of those links:
Android 4.2.2. - https://dl.google.com/dl/android/aosp/mantaray-jdq39-factory-d79f489e.tgz
Android 4.3 - https://dl.google.com/dl/android/aosp/mantaray-jwr66y-factory-3d8252dd.tgz
Android 4.4 - https://dl.google.com/dl/android/aosp/mantaray-krt16s-factory-94413961.tgz
Android 4.4.2 - https://dl.google.com/dl/android/aosp/occam-kot49h-factory-02e344de.tgz[/CODE]
Click to expand...
Click to collapse
Now that you're done with your download, you'll extract the .tgz package the way you prefer. Now, open a command line in the folder where the extracted files are and (with your device plugged on fastboot mode) just type:
Code:
chmod 755 flash-all.sh
sudo ./flash-all.sh
The procedure will now begin. It can take some time to finish. When it ends, it's recommended that you lock back your booloader, which is as easy as unlock. Type (tablet plugged in fastboot):
Code:
sudo fastboot oem lock
Hope this helps!
Click to expand...
Click to collapse
~Lord

XxLordxX said:
If you want I can do the Linux walkthrough and script . I'll be more than glad to assist in this.
~Lord
"This Story Ends Where It Began"
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
Yes a Linux walk-through is what I was going to do... I can also do a windows one it will just take me a bit longer... Thx lj

i want in! "all-round-android-guy"
Sent from my Nexus 4

Nexus 10
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110

kerriganinks said:
I've followed the instructions, unlocked the bootloader all the commands executed with "okay" but then on reboot the tablet is exactly like it's been from the get go, still showing user info and still showing all downloaded apps and updates, nothing works correctly. Thought maybe was a half installed update or virus. Nothing I've tried resets this to Factory. It's the Gtp 8110
Click to expand...
Click to collapse
What is your PC's OS.....:good:

OS
lj50036 said:
What is your PC's OS.....:good:
Click to expand...
Click to collapse
Windows 7 64 bit. on several machines. I tried 3 diff systems same results, even tried the hated toolkits, but the bootloader locks on any reboot at all. Negating any changes, the fastboot at least didn't reboot so it said all commands were completed, but nothing actually changed. I'm having issues reading those verifications on the page to post, is there a way around that. I got the phone number to call this in to Samsung for service, something has it locked and I've wasted way too much of my life toward trying to work on someone else's tablet. I've used the flash method on several phones and tablets in the past, so not a complete novice, just know it's not giving the same results as for others because something's wrong with the tablet.

This indeed is a strange issue, it seems others have had the same challenge
http://forum.xda-developers.com/showthread.php?t=2638227
Can you try the fastboot method of restoring stock again and this time copy and paste all input/output here
Also can you write down all info on bootloader screen
Sent from my Nexus 4 using XDA Premium 4 mobile app

Nexus 10 Boot behavior
Hello forum gurus!
I have a question regarding the boot behavior of the Nexus 10 that you'll probably know something about.
I need to have the device boot straight to the android desktop after it's been plugged in while in an off state. Usually, most devices boot into a battery-charging screen when you apply power while they're off, then they top up the battery and go to sleep, waiting for you to press the power button.
I'm hoping there is a way to alter this behavior and get the device to boot into android's desktop straight up. I've seen this setting being changed between different ROMs and I'd like to hear your opinion how to get the change done.
This is for a project of mine, the way I see it, i'll be using a few of these tablets for an installation.
Thank you for your feedback in advance!
Best,
Stef

Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app

Thanks a lot, also for the quick response.
I'll wait for your reply, so we don't end up pestering the same people twice for the same thing.
BR,W
demkantor said:
Hi wheezardth
Unfortunately I can't answer your question directly as I have never attempted this. The boot sequence is controlled by the bootloader but I have often seen android devices with a custom recovery boot directly to recovery when being off and then plugging in. So this would mean that the bootloader must look to the kernel (which a recovery is a kernel) for some direction at this point.
It more than likely is possible to alter either the kernel partition or possibly the recovery to do exactly what you are after but how you implement this I can't say off hand. But I will say it is unwise to attempt to alter the bootloader itself so look to kernel ninjas for help on this one.
I'll talk with some people who may have an answer on this and get back to you and if you know any (they don't have to own a n10) ask them and see if they may have an answer
Best of luck and I'll let you know what I find
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Please Help
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me

unitnerd said:
Main issue: Unable to write to internal storage
Symptoms: Cannot write to external storage,
Google Play FC
Opening Gallery shows "no external storage available"
Opening camera shows "insert an SD card before using the camera"
Trying to open internal sd from ES file explorer storage/emulator/0 not found.
I installed Omni Rom. Then i changed to other roms which were already in the storage.I noticed I could not write to internal storage but i could read.I tried 3 roms then i switched to stock 4.4.2 and locked my bootloader. I heard installing a custom kernel may help so I tried flashing one but didnt help. I can install APK's through ADB but not otherwise.I cannot download anything also.
Currently im in stock 4.4.2 rooted bootloader unlocked.
My problem is different as i can install apk's that means the emmc is not corrupted? (Not sure)
Storage shows: 26.75 GB available Total : 27.30
Please help me
Click to expand...
Click to collapse
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1

XxLordxX said:
Hi,
Did you try formatting your storage? I know that relocking the bootloader will format, but maybe you need to reformat with a PC or something... Make sure you didn't select a bad partition .
Sorry, but this issue is a little weird... And I can't help you too much, I'll think a little more, but hope this helps a little.
~Lord
"All I Ever Needed Was A Little Piece of Hope" - World of Fantasy (Helloween)
Sent from my monstrous Xperia Z1
Click to expand...
Click to collapse
How do i reformat with pc?

hi, i am very new to android (i still use a flip phone)
i have unlocked my nexus 10 (4.4.2), and have stopped there.
after the final steps in post #3
>fastboot erase system -w
>fastboot erase boot
>fastboot erase recovery
>fastboot flash bootloader nameofbootloader.img
>fastboot flash system system.img
>fastboot flash userdata userdata.img
>fastboot flash cache cache.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>Congrats! You can reboot to a functioning tablet!
after the reboot, would the device be rooted?
thanks in advance.

Not if using the factory image, you would still need to boot into recovery and flash superuser, then it would be rooted. Or boot to recovery and flash one of the many custom ROMs, all of which are prerooted
Really the only thing you need to do is unlock the bootloader, flash a custom recovery, then either flash a custom ROM or su
Sent from my Nexus 4 using XDA Premium 4 mobile app

thanks for the reply,
it looks like a 'catch 22' , but im sure its just that, i am seriously confused.
after reading several links, that link, to yet another linked guide.
i thought that i would use team win recovery project but it requires root. so thats a no go.
i checked a few others but same situation, require root to use.
could you/someone recomend a stable recovery or whatever i need.
...my head hurts, ill revisit this tomorrow.

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?

{Noob Guide} Unlock Bootloader n Root with Magisk With Easy OTA Support ! {No Twrp}

* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty could be void if you tamper with any part of your device / software.
* Same statement for XDA.
Click to expand...
Click to collapse
This is my first time posting here on xda if i miss some rules please let me know
Installing drivers & Preparing PC (Thanks to balazs312)
- Download this file and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it
NOW Unlock Bootloader (It will wipe ur data! so backup before doing it)
-Open the Settings app on ur phone
-Go to System.
-Tap on About phone.
-Scroll down and tap on Build number 7 times until it says you’re now a developer.
-Go back one page you should see “Developer options.” click it
-then you should see an “OEM unlocking” option. Enable it.
-Scroll down a bit until you see “USB debugging.” Enable it.
-Disable automatic updates
-now turn off your phone
-now turn on ur phone in fastboot mode by pressing volume down + power key in will boot in fastboot mode
- Download zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
Code:
fastboot flashing unlock
fastboot flashing unlock_critical
done now pop up will show on your phone select unlock bootloader with volume key n power
it will reboot set up ur phone again
2. Installing Magisk
To Install Magisk you need patched boot image you can have one from here
{always use img that matches exactly to ur build no}
OR
{OPTIONAL}
you can make own boot img
download fastboot rom and get boot.img from there
or download untouched img from here
so now ur phone is unlocked download magisk manager and install it from HERE
copy that untouched boot image from ur pc to phone
open magisk manager >install >patch boot image select ur boot img u just transferred
magisk manager will create a patch image in same directory or download folder
Fastboot patch img
Now if u have created ur own patch img transfer it to pc from ur phone n put it in adb folder
or if u have simply downloaded the patch image copy it to adb folder
Open a fastboot command prompt on your pc.
Type "fastboot boot {patched boot image name}.img"
Your phone will reboot
Install the magisk apk.
Now open Magisk Manager app
Click Install, direct install. Wait for the process
And click reboot.
HOW TO APPLY OTA UPDATES
IMPORTANT: it will only work if you do not alter system yourself like build.prop (try altering system just using magisk modules)
{if u created ur own patch img}
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images"
{if u have not created ur own img put untouched downloaded build.img in magisk folder then}
When you know that a new OTA update is available and you want to install it, open Magisk Manager, and tap on "Uninstall" > "Restore Images"
Close Magisk Manager and go to "Settings" > "About Phone" > "System update" and install the OTA update. Dont Reboot
Open Magisk Manager again and tap on "Install" > "Install" > "Install to Inactive Slot" and after that you can tap on "Reboot".
alternatively
Magisk could alert you that it cannot restore the original boot.img when you trying to uninstall
To fix this, you can flash directly the untouched boot.img through fastboot
Code:
fastboot getvar current-slot
then you will get ur active slot it might be a or b
if its a then use
Code:
fastboot flash boot_a boot.img
If its b then use
Code:
fastboot flash boot_b boot.img
Now We Have Mi A2 Telegram Group get in if u want to help or need some help
OffTopic Group HERE
Development Group HERE

-reserved-

i have just created this account to reply here it
i used to read here alot but i dont reply here
as i found this thread has no reply but the best method i was searching for on internet for my mi a2
i just got my mi a2 was highly confused how to root because of a/b partition and no official twrp
i found this method among the best no confusion straight on point
and seriously a noob guide
thank you for the this !

geekh said:
i have just created this account to reply here it
i used to read here alot but i dont reply here
as i found this thread has no reply but the best method i was searching for on internet for my mi a2
i just got my mi a2 was highly confused how to root because of a/b partition and no official twrp
i found this method among the best no confusion straight on point
and seriously a noob guide
thank you for the this !
Click to expand...
Click to collapse
I personally think that there are at times some confusion. but it remains a more reliable method. (in terms of ease this method (https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/) is by far the fatest, try it after your next ota)

Atlas/ML said:
I personally think that there are at times some confusion. but it remains a reliable method. in terms of ease this method (https://forum.xda-developers.com/mi-a2/how-to/guide-2-minutes-magisk-installation-t3856980/amp/) is by far the easiest, try it after your next ota
Click to expand...
Click to collapse
I have just checked your linked thread first of all its wrong to promote your own thread like this
u are fishing people to come to your thread thats completely wrong and unprofessional you are on xda maintain some professionalism !
if someone wants to use your thread he/she will use it by themselves ,its visible to all !
and about your method i didnt wanted to use ur method i have looked into it you are using temp twrp method using unoffical twrp which i dont want to use thats personal preference i will wait for official twrp before flashing !
this method is best for me(noob here might be not as good as you but i know basic stuff) i can easily flash twrp permanenlty as soon as it is released without any further steps
Not everyone wants to use that temp twrp method
It is not fair to @Adinid who has taken so much time writing this great noob friendly thread
coming to his thread and telling people that ur thread is best or easiest is isnt good my friend !

in OTA part，"put untouched downloaded build.img in magisk folder"，This is invalid，I test it on V9.6.13，It always prompts that the backup image was not found.

geekh said:
I have just checked your linked thread first of all its wrong to promote your own thread like this
u are fishing people to come to your thread thats completely wrong and unprofessional you are on xda maintain some professionalism !
if someone wants to use your thread he/she will use it by themselves ,its visible to all !
and about your method i didnt wanted to use ur method i have looked into it you are using temp twrp method using unoffical twrp which i dont want to use thats personal preference i will wait for official twrp before flashing !
this method is best for me(noob here might be not as good as you but i know basic stuff) i can easily flash twrp permanenlty as soon as it is released without any further steps
Not everyone wants to use that temp twrp method
It is not fair to @Adinid who has taken so much time writing this great noob friendly thread
coming to his thread and telling people that ur thread is best or easiest is isnt good my friend !
Click to expand...
Click to collapse
I personally think that official twrp will never support boot, because At first glance the beta does'nt support it. So my method will be the simplest for a while.
As for the sharing of MY guide, it is a simpler and faster method. And it will allow more people to root their phone without following 50,000 steps and without fear of brick their phone ...
If @@Adinidhas a problem with sharing my guide, he can tell me privately on Telgram, and I'll delete it.
Have nice day,
Matteo

I don't really care which method people use to do one thing or another. It's up to them, whatever they feel most comfortable doing.
But, I do care when someone misuses the 'code' functionality box. It's not used for 'further description'... it's used for CODE... ie, actual code:
like: fastboot boot bootloader
like: adb shell setprop persist (etc)
It's meant to be something someone can copy and paste it to the command line, to avoid typing errors, not for 'further descriptions...'

Atlas/ML said:
I personally think that official twrp will never support boot, because At first glance the beta does'nt support it. So my method will be the simplest for a while.
As for the sharing of MY guide, it is a simpler and faster method. And it will allow more people to root their phone without following 50,000 steps and without fear of brick their phone ...
If @@Adinidhas a problem with sharing my guide, he can tell me privately on Telgram, and I'll delete it.
Have nice day,
Matteo
Click to expand...
Click to collapse
Your Reply shows your arrogance and unprofessionalism nothing else
you think the method you have is best u dont want to even think that someone can have other method n others might prefer it
you are just boasting about your method as best n what not lol !
instead of accepting that you did wrong by sharing your thread here , you are trying pull down op thread by shamelessly telling people that op method might brick phone n needs 50k steps(that is completely NOT true ) when ur method CAN also brick it !
you both have given options to users its their pick which one they want to use !
I dont want to waste my time here to educate you about how to behave in public forum !
Just want to say calm down put ur arrogance on side,show some maturity and even please try to change ur attitude
you might be good but try to learn as it doesnt matter how good you are there is always someone who is better than you n others might prefer it more !
different people have diff use cases preferences always remember that
peace !

AsItLies said:
I don't really care which method people use to do one thing or another. It's up to them, whatever they feel most comfortable doing.
But, I do care when someone misuses the 'code' functionality box. It's not used for 'further description'... it's used for CODE... ie, actual code:
like: fastboot boot bootloader
like: adb shell setprop persist (etc)
It's meant to be something someone can copy and paste it to the command line, to avoid typing errors, not for 'further descriptions...'
Click to expand...
Click to collapse
Thank you for your feedback sir, i have just started posting here as i wrote it in my initial post
my apologies will try to format it properly

tianma163 said:
in OTA part，"put untouched downloaded build.img in magisk folder"，This is invalid，I test it on V9.6.13，It always prompts that the backup image was not found.
Click to expand...
Click to collapse
looking into it
till then i just added alternate method use that !

geekh said:
Your Reply shows your arrogance and unprofessionalism nothing else
you think the method you have is best u dont want to even think that someone can have other method n others might prefer it
you are just boasting about your method as best n what not lol !
instead of accepting that you did wrong by sharing your thread here , you are trying pull down op thread by shamelessly telling people that op method might brick phone n needs 50k steps(that is completely NOT true ) when ur method CAN also brick it !
you both have given options to users its their pick which one they want to use !
I dont want to waste my time here to educate you about how to behave in public forum !
Just want to say calm down put ur arrogance on side,show some maturity and even please try to change ur attitude
you might be good but try to learn as it doesnt matter how good you are there is always someone who is better than you n others might prefer it more !
different people have diff use cases preferences always remember that
peace !
Click to expand...
Click to collapse
That's why i add a warranty part lmao, and for brick not possible, because magisk support A/B, and Twrp is BOOT only. So after reboot it's gone.
I just say that my method is the simplest, not the better. As for the arrogance I only share my link for you to win time if needs after any ota, if you do not want to use it. You say that I lower his method, etc. I have already done one with these same methods, and I will soon hold a repo. You're totally wrong. No luck You judge me without knowing me and give me orders and I'm arrogant. OwO
As for the answers, personally I do not have anything to do with it, it makes go up this thread in the list, hoping that it has more visibility.
Matteo

If i enable camera2api does it count as altering system for ota?

Ajakazema said:
If i enable camera2api does it count as altering system for ota?
Click to expand...
Click to collapse
it depends on how you activated it. if you activate it using a magisk module it will be fine, if you activate it using an adb command it's a system modification. so it should alter the ota.

Ajakazema said:
If i enable camera2api does it count as altering system for ota?
Click to expand...
Click to collapse
if u do that by build.prop edit it will count for altering system
but if u use magisk module to do that it will not
let me know if u have any more confusion
happy to help !

I'm currently in august security patch, with an unlocked device + root (magisk) and i've altered the build.prop to enable cameraapi2. How can I update safely to the new october patch?
Thanks in advance

hugopg said:
I'm currently in august security patch, with an unlocked device + root (magisk) and i've altered the build.prop to enable cameraapi2. How can I update safely to the new october patch?
Thanks in advance
Click to expand...
Click to collapse
if u want everything clean u can flash fastboot rom
after uninstalling magisk through magisk manager
or just uninstall magisk then fastboot flash boot img
u can check it in my how to get ota part in my initial post (alternative method)
then apply ota
root again if u want
adinid

Adinid said:
if u want everything clean u can flash fastboot rom
after uninstalling magisk through magisk manager
or just uninstall magisk then fastboot flash boot img
u can check it in my how to get ota part in my initial post (alternative method)
then apply ota
root again if u want
adinid
Click to expand...
Click to collapse
Hey, thanks for your fast reply!
In your post you said that the OTA can be done if I didn't altered the system.prop, but I did! So I would need to restore boot.img (through magisk, to remove root) and also flash system.img (to restore the prop)? Is that it?
Thanks

Atlas/ML said:
it depends on how you activated it. if you activate it using a magisk module it will be fine, if you activate it using an adb command it's a system modification. so it should alter the ota.
Click to expand...
Click to collapse
This is COMPLETELY inaccurate information! YOU are setting a very bad precedent.
Magisk is a SYSTEMLESS root, which means what it does with system is HIDDEN (very hard to detect), but that does NOT mean it doesn't modify system!!
The ADB command to set the cam2api is a setprop persist command WHICH DOES NOT MODIFY SYSTEM! EVER!
PLEASE DO NOT SPREAD COMPLETELY INACCURATE INFORMATION!! YOU WILL BE MISLEADING POTENTIAL FUTURE OWNERS OF THIS DEVICE!!

AsItLies said:
This is COMPLETELY inaccurate information! YOU are setting a very bad precedent.
Magisk is a SYSTEMLESS root, which means what it does with system is HIDDEN (very hard to detect), but that does NOT mean it doesn't modify system!!
The ADB command to set the cam2api is a setprop persist command WHICH DOES NOT MODIFY SYSTEM! EVER!
PLEASE DO NOT SPREAD COMPLETELY INACCURATE INFORMATION!! YOU WILL BE MISLEADING POTENTIAL FUTURE OWNERS OF THIS DEVICE!!
Click to expand...
Click to collapse
So, first shut a up.
Next i never say that magisk doesn't modify system, i just say that if use magisk for enable it it's fine.
For the second information, my bad , i try but with the adb command ota failed so i'm not totally false.
Have a bad day,
Matteo

[How To] Enable Cam2API - simply, and keep OTA - NOT working with stable PIE

********** 11/17/18 sorry to say folks, this method of enabling cam2api does not, for some reason, work with stable PIE. Looks like root is the only option now ********
**** please note, the next comment, after this guide, has some 'condensed problem solving' tips from the 10 pages of comments - if you run into problems doing the following, look at the next comment for possible solutions *****
While this might sound similar to other 'guides', it's not the same. In this guide we'll enable Cam2API, not flash anything, and not install root then later uninstall it.
And we won't do it with a 'tool', that you have no idea what it's doing behind the scenes (they have their place, but not really needed for this imho).
Also, it's not my intention to knock Magisk. It's a great rooting app, and it has a lot of additional features besides root. But when deciding to use Magisk or not, if all you want to do is enable cam2API, and use none of it's other great features, it seems like overkill to me.
Prerequisites:
1) Your version of fastboot needs to be one that recognizes 'dual slot' phones (look at the version docs if yer not sure).
2) Your device needs to be bootloader unlocked, and adb debug enabled (research that if you don't know what it means).
3) You need the latest version of Tingyichen's TWRP, which currently is twrp-3.2.3-jasmine-20181020.img
https://forum.xda-developers.com/mi-a2/development/recovery-unofficial-twrp-recovery-mi-a2-t3825146
1) Connect the device with adb, and verify it's working with 'adb devices'. Assuming it works type:
Code:
adb reboot bootloader
2) Once in fastboot (the bootloader), find out which slot is current with:
Code:
fastboot getvar current-slot
Make a note of which slot is current.
3) If the current slot is NOT 'a', then we have to set it to 'a'. Do the following to accomplish that;
Code:
fastboot set_active a
4) With the current slot set to a, do the following command:
Code:
fastboot boot twrp.img
(or the actual name of your twrp.img if you didn't rename it to twrp.img - you don't *have* to rename it, seems most people do though.)
At this point, let the device start and go into twrp. You will have to use your 'pattern' if you have one set on the phone. Also, you do NOT have to hold vol up to boot into twrp.
5) Now we'll do the 2 (or 3 if u have Pie) commands to set cam2 enabled.
Code:
adb shell
Code:
setprop persist.camera.HAL3.enabled 1
note: only do the following command for Pie or newer versions.
Code:
setprop persist.vendor.camera.HAL3.enabled 1
Code:
exit
6) Our cam2 will be enabled the next time we reboot. So lets type this:
Code:
adb reboot bootloader
7) Now, if our original active partition was b, we have to set it back to b:
Code:
fastboot set_active b
8) Lastly, we simply reboot with:
Code:
fastboot reboot
That's it, boom, done.
Side Notes:
So why does this work? After so many have indicated TWRP didn't work for them? But it did for others? Wha Up? Simple, it seems twrp isn't very dual slot smart (and why should it be? it was originally written for single slot devices - it DOES give you an option to set the other slot active when you exit it, but all that's doing is running 'set active', nothing to do with installing it).
So I just verified this morning, even though I have cam2 working. My active slot is b, and 'fastboot boot twrp' would fail (even though others said Tingy's new version worked!). So what's different? Only thing I could think of was which slot was active. The active slot changes for ea device with updates, and thus we don't all have the same active slot!
But setting it to a, then doing boot twrp, works like a champ. setprop persist commands of course work also (I verified, even though mine are set). And simply going back to fastboot and doing reboot should avoid any trace of twrp having been used (we didn't 'flash' it, only booted it).
If anyone decides to try 'fastboot boot boot_a twrp.img', that *might* work, I didn't think to try it.
Cheers

updated 11/9/18
Some people have run into issues with twrp working as needed. The following are some of the solutions that have been found:
1) Some have used PBRP instead of TWRP, **BUT** it seems the most recent version of pbrp does NOT work.
2) Some have found that booting TWRP works okay but doing the 'setprop persist' commands didn't result in cam2api being enabled.
2 a) to fix the above, they went into the 'mount' section of TWRP and disabled the MTP option. They indicated they also enabled 'persist', but it's uncertain if that made a difference. (Special thanks to @lept_2014 for that!)
For most, it seems to work just by following the guide. I'd recommend this; ea and every time you go to fastboot, or to the device with adb, always be sure that fastboot and adb can see the device before proceeding. That narrows down the problems significantly.
If 'adb devices' does not show your device in the response, the problem is your PC and usb / adb drivers.
if 'fastboot devices' does not show your device in the response, the problem is with your PC and usb / fastboot drivers.
Thanks to all of the contributors. That's a big help to everyone.

Hello, perfect for me, like a charm.
My slot: A
Thanks a lot, best regards!!
PS: I use CMD. Problems in PowerShell with "fastboot flashing unlock_critical" command.

TingyiChens latest twrp from 20181020 works on my phone in both slots a and b. It just boots twrp into the active slot. I am running the October stock 9615 rom. Currently my active slot is b after the last ota.

When the hell would xiaomi enable cam 2 api by default

kishd said:
TingyiChens latest twrp from 20181020 works on my phone in both slots a and b. It just boots twrp into the active slot. I am running the October stock 9615 rom. Currently my active slot is b after the last ota.
Click to expand...
Click to collapse
Good to know. It's confusing why some of us get 'failed'. But it does work! As you point out also. I guess we can say that if you get a failed message, try setting the other slot active. It absolutely will work.
Yes, why don't they set cam2 by default sharingan, I wish I knew. But using twrp is pretty painless, so at least we have that.
Cheers

Can some pls make video tutorial for this...pls

setprop persist.camera.eis.enable 1 there is no need to knock

Is slot a and b contains same data inside by stock?
Edit: this is my first system ab phone so be gentle please

bojan1974 said:
setprop persist.camera.eis.enable 1 there is no need to knock
Click to expand...
Click to collapse
knock what? not making sense to me, sorry

nhmanas said:
Is slot a and b contains same data inside by stock?
Edit: this is my first system ab phone so be gentle please
Click to expand...
Click to collapse
Probably the 1st A/B phone for a lot of us.
But no, they don't have the same 'data inside by stock' (I'm not sure what you mean by that).
They use different partitions for many things such as; boot, system, vendor (the most important ones). But they do use the same one for data (is that what you meant?). The data one is where our apps, media files, etc are kept, and that doesn't change with an OTA update.
Another important difference is there is no longer a 'recovery' partition, which is what twrp use to be installed in. Now, with A/B, the 2 boot partitions and the rest of the 2 partitions are the old 'recovery'.
So what does the 'other' boot partition have in it? Well the old version of the OS before the OTA update. That doesn't change with an update. The other slot is updated and then made active. Then when a new update happens, the current one becomes the old one (again). And on and on.
the reason this works is because the setprop persist commands only change the data partition, not system. And since twrp mounts data (of course it does, it's a recovery tool), it can execute the setprop commands no problems.
good luck

When i boot twrp i get error: device '(null)' not found.

Ajakazema said:
When i boot twrp i get error: device '(null)' not found.
Click to expand...
Click to collapse
What is the exact command you are entering? What happens if you do 'fastboot devices' ? Does that command see your device?

AsItLies said:
What is the exact command you are entering? What happens if you do 'fastboot devices' ? Does that command see your device?
Click to expand...
Click to collapse
adb shell, but no i don't think it can see the device when it goes into twrp. I think it's a driver issue but i can't figure out why, tried it on 2 PCs and i get the same problem.
Edit: when i type fastboot devices it just says list of devices attached

Ajakazema said:
adb shell, but no i don't think it can see the device when it goes into twrp. I think it's a driver issue but i can't figure out why, tried it on 2 PCs and i get the same problem.
Click to expand...
Click to collapse
yes it may be a driver issue. did you just unlock the bootloader? if yes, you have to reboot the device and enable adb debugging in dev options?

AsItLies said:
yes it may be a driver issue. did you just unlock the bootloader? if yes, you have to reboot the device and enable adb debugging in dev options?
Click to expand...
Click to collapse
Did both of those things.

Ajakazema said:
Did both of those things.
Click to expand...
Click to collapse
Another thing it might be is the pin / pattern security being set. Twrp won't let you touch the device if you haven't entered the pin / pattern.
It might be a good idea to just disable them temporarily and then try again.

AsItLies said:
Another thing it might be is the pin / pattern security being set. Twrp won't let you touch the device if you haven't entered the pin / pattern.
It might be a good idea to just disable them temporarily and then try again.
Click to expand...
Click to collapse
Yea i tried that too, no luck.

Ajakazema said:
Yea i tried that too, no luck.
Click to expand...
Click to collapse
Are you using the version of twrp I mentioned in the first post? They aren't all the same, the one mentioned is specifically for this phone - Jasmine.
hard to imagine what else it could be...

AsItLies said:
Are you using the version of twrp I mentioned in the first post? They aren't all the same, the one mentioned is specifically for this phone - Jasmine.
hard to imagine what else it could be...
Click to expand...
Click to collapse
Yea. No idea what the problem is.