Database Users

Edited /system? Here's how to get the OTA to apply.

http://android.modaco.com/content/t...ng-to-stock-1-19-before-applying-the-new-ota/
P

Seriously, did a mod edit my topic name to put a [Q] in front? (I removed it now).
Just because there's a question mark in the topic doesn't make the topic a question. IYSWIM.
P

do u HAVE to revert to the stock rom to apply the update?

Only if you've deleted stuff on /system.
P

after doing the flash paul, my phone is sitting at the black htc screen with the green indication bar full

'fastboot reboot'
P

thanks, this is my first droid flash. i prolly have flashed windows mobile over a thousand times

Hey paul anyway on doing your method without wiping? Don't wanna lose my launcher pro homescreen setup I got going on took me a while to do lol.
[G2/HTC Vision]

Hey paul did u update. I'm holding off on the update cuz I don't wanna risk never being able to get root

I did yeah.
P

How long should it take to flash?
Its been sitting on a black screen with HTC logo for 20 min
terminal shows:
./fastboot-mac flash zip PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
sending 'zip' (126272 KB)...

http://www.mediafire.com/?s9ld7vag3fdm39g alternate link for shipping rom

mcp2009 said:
http://www.mediafire.com/?s9ld7vag3fdm39g alternate link for shipping rom
Click to expand...
Click to collapse
Oh YES! I was pulling my hair out waiting for the other to download. thank you

ikarma said:
How long should it take to flash?
Its been sitting on a black screen with HTC logo for 20 min
terminal shows:
./fastboot-mac flash zip PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09b_26.02.01.15_M2_release_149459_signed.zip
sending 'zip' (126272 KB)...
Click to expand...
Click to collapse
If it's still on 'sending', you can pull the battery and try again.
P

When I try to extract the fastboot zip it errors me out. Downloading from my device. Not pc
Edit: guessing I'm suppose to use fastboot thru my pc? How does this work?
[G2/HTC Vision]

mine is sitting on htc screen with green progress bar which looks to be full.. is it okay to pull battery and try the update?

Fastboot
When I run fastboot-windows.exe on my computer I just get a quick flash of a black screen and then nothing.
Nevermind kinda went a different route and put the orginal rom on the root of the sdcard and named it to pc10img.zip and the booted into fastboot and then bootloader. It then flashed the zip, took a few min. Than put OTA on root of sd and named it to update.zip and entered into recovery and selected apply sdcard : update.zip. All went well. Actually is now booting for the first time havent even played with new system yet. Thanks for all the hard work that you devs do though. You make these phones bada$$.

Helpful Hint
If you have trouble getting it to "see" the device while in fastboot, just go to control panel, devices, install driver, and pick the one from sdk folder.

This was my first time using fastboot, so I had to do some digging around to figure it out.
Flashing via Fastboot (done within Windows, not the phone):
1.Download ROM and fastboot.zip from OP
2.Leave the ROM alone, and extract the contents of fastboot.zip into the same folder as the ROM
3.Start phone in fastboot mode; when phone is off, hold trackpad button and press power
4.The phone should go into the proper mode, now connect it to USB
5.Open up the command prompt in Windows (Start>run>cmd)
EDIT:6. I forgot to add this: you have to set the directory in cmd to the folder in which the ROM and fastboot files reside. The easiest way to do so is make a folder on the desktop itself, and type "cd desktop/[foldername]" into the command prompt, without the quotes.
7.Follow the last three bullets as listed in Paul's post
I already had the USB drivers for the phone when messing with adb. I don't know if that will affect fastboot; if it does, you'll need to boot the phone normally and connect via USB, download PdaNet onto your computer, and let it install the necessary drivers. Once done, then you may follow the remaining steps.
EDIT: See #6 for updated instructions; it is crucial to avoid the invalid command error.

EfemaN said:
This was my first time using fastboot, so I had to do some digging around to figure it out.
Flashing via Fastboot (done within Windows, not the phone):
1.Download ROM and fastboot.zip from OP
2.Leave the ROM alone, and extract the contents of fastboot.zip into the same folder as the ROM
3.Start phone in fastboot mode; when phone is off, hold trackpad button and press power
4.The phone should go into the proper mode, now connect it to USB
5.Open up the command prompt in Windows (Start>run>cmd)
6.Follow the last three bullets as listed in Paul's post
I already had the USB drivers for the phone when messing with adb. I don't know if that will affect fastboot; if it does, you'll need to boot the phone normally and connect via USB, download PdaNet onto your computer, and let it install the necessary drivers. Once done, then you may follow the remaining steps.
Click to expand...
Click to collapse
LOL! I had sat around and realized even though I used abd and shell... I had no drivers in fastboot. also after flushing type "fastboot reboot" or pull battery to finish.

[Beginners Guide] Unlock & Custom ROM your TF300

I have been asked to port my "Beginners Guide" from the TF700 forum for the TF300. Since both tablets are very similar, that was not too hard to do
If I have missed to update a link specific for the TF300, do let me know please.
And the standard disclaimer: I am not responsible if you misunderstand instructions I give here, if my instructions are wrong, if you forget to charge the battery and the tablet dies halfway through a flash or if your house goes up in flames. YOU DO THIS AT YOUR OWN RISK
These instructions assume that you are on the latest Asus bootloader: 10.6.1.27.5
To determine which bootloader you currently have:
From an "Off" state, boot the tablet with Volume Down and Power into the bootloader menu. Read the small script in the upper left. You'll see
US_epad-10.6.1.27.5-20130801" or similar.
US or WW, JP, CN is your SKU or region
10.6.1.27.5 is your bootloader version
20130801 is the build date (and immaterial in most cases).
First things first:
Backup everything on your tablet you care about to an external microSD or your PC. Don't worry about your apps. You can always install them from the Play Store.
This is just common sense. It is not inherently risky to flash custom ROMs. But something can wrong at any time and you have to be careful. If you are, this is a safe procedure.
Basically the process of flashing a custom ROM on the TF300 involves three steps:
1) Unlock the bootloader using Asus' Unlock tool
2) Install a custom recovery on the tablet
3) Flash a custom ROM of your choice using said custom recovery​
Unlocking the bootloader
Your tablet should be fully charged at this point!
Make sure "USB debugging" is checked in Settings > Developer Options (if you don't see it, go to About Tablet and tap 7 times on Build Number)
Go to Asus website: https://www.asus.com/support/Download/28/1/0/9/8BmzkQ4yoz5WzBrW/32/
Choose "Android" for OS and look for the "Utilities" on the resulting page.
Download the Asus Unlock Tool v7 (not v8! It says v7 is for ICS but it'll work fine on JB - see below)
The tool downloads as a .rar file which is an archive you have to decompress. 7zip is a free and very good Windows tool that will do it for you
On your tablet, in Settings > Security check "Unknown Sources"
Copy the .apk you extracted from the .rar archive to your tablet.
Find the apk in your tablet's file browser, tap it and let it install
Open the app and follow the instructions. You will loose your warranty as soon as you click "I agree".
Update 2/15: Google added another wrinkle: It now checks even sideloaded apps and refuses to install them if they are considered not secure. The Unlock tool seems to fail their test. v8 does not install at all anymore. v7 will install if you allow "less secure apps" in your Google account settings. On the web - not your Google account on the tablet
July 2015: And another wrinkel... It seems to be pretty consistent now that the Unlock Tool hangs on the Google account password step. I suspect something changed on the Google side. It probably doesn't allow the tool to check/compare the password anymore. There have been quite a few security changes lately and the unlock tool never gets updated so I suspect that Google now is blocking access by the tool to it's servers.
The work-around is easy enough: Delete the Google account from the tablet (Settings > Accounts), then run the tool again. If that doesn't do it, do a factory reset from Settings, reboot and during the initial setup establish a WiFi connection but skip the google account setup, then run the tool
Click to expand...
Click to collapse
This can be a 5 Minute operation that goes without a hitch or a very frustrating experience with lots of error messages. There is no definite rhyme or reason for this. For some people it works like a charm, for others it works after 15, 25 or 55 attempts, for some never.... This problem is widely discussed on several forums. Google it if you hit that roadblock.
To check if you are unlocked, boot the tablet and read the tiny script. It should say:
The device is unlocked.
Installing a custom recovery on your tablet
I highly recommend you choose TWRP as your custom recovery. If you want CWM, you are on your own.
To push TWRP to your tablet you need to set up "Fastboot" between your tablet and your PC. Fastboot is a protocol that enables you low level access to your tablet.
Practice/Background
Power down your tablet and disconnect it from the dock
Push and hold the Volume Down key (left side of the rocker) and the Power key until you feel the tablet vibrate twice. Let go when you see the tiny script. Read it and it tells you that your tablet is now in fastboot mode and you will see three icons (I assume again you are on a JB 4.2 bootloader. In older bootloaders you had 4 icons and had to select the USB icon to get into fastboot mode):
RCK - (which should be flashing) is your recovery (the stock recovery at this point, but once TWRP is installed this is one way to get into it)
Android - is your system, selecting it boots you back to into your ROM.
Wipe Data - stay away! Especially with custom software installed never, ever use this option!
To toggle between the three icons use Volume Down, to select one use Volume Up. Try it but do not push Volume Up when the 'Wipe data' icon is flashing!​
Installing ADB and fastboot plus the necessary drivers
For a working ADB/fastboot connection from PC to tablet you need:
a) Asus device drivers – if you connect the tablet to your PC and it's recognized as a portable device you should be ok. If not, download the Asus Sync Utility from their support/downloads site and install it to get the drivers, then uninstall the program from your PC if you don't want it. The drivers will stay.
b) Fastboot and ADB drivers which will be installed if you run the tool below.
Windows Vista, 7, 8, 10:
Download and run this cool little tool [TOOL] [WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.1 - xda-developers (don't forget to hit the Thanks button)
The tool installs the adb and fastboot.exe to a folder on your C:\ drive (look for adb) and the corresponding drivers. Takes about 15 seconds.
On Windows 8 and 10 you need to turn off the driver verification feature. Here's a great video on how to do it:
https://www.youtube.com/watch?v=afrvSGiMAtk
Or - even better - here's a quick command line toggle to achieve the same (thank you @Jack_Hardin):
Jack_Hardin said:
If you're running W10, you can disable Device Driver Signing without following the procedure in the linked video, but by (more simply) right-clicking on the Start button, selecting Command Prompt (Admin) and then typing:
Code:
BCDEDIT /set nointegritychecks ON
Doing the same with OFF at the end of the string, as easy to guess as it looks, will reenable them.
Click to expand...
Click to collapse
Jack_Hardin said:
Win XP (and all other Win versions if the above does not work for some reason)
I recommend the "ADB Install Tool" mentioned above or the 'Minimal ADB Fastboot Tool': [TOOL]Minimal ADB and Fastboot [7-18-13] - xda-developers
Either works fine.
If you need the drivers, get them here and install manually in Device Manager:[ADB/FB/APX Driver] Universal Naked Driver 0.72 (We dont need no stinking HTC Sync) - xda-developers
Win7 and Win8 users seem to have the best luck wth the drivers sbdags provided here: http://forum.xda-developers.com/showthread.php?t=2646279
It's fine if you want to use his Recovery Install Tool from that thread. But I highly recommend you familiarize yourself with basic fastboot commands! There are lots of tuturials all over the web.
Linux:Check out this site https://code.google.com/p/adb-fastboot-install/
iOS:[GUIDE] Set up ADB and Fastboot on a Mac easily (With Screenshots!) - xda-developers or:
http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
The fun begins
Fastboot does not play well with USB 3.0, so use a USB 2.0 port for this. And no hubs and such....
Boot the tablet into fastboot mode and connect it to your computer via the original USB cable
In Windows Explorer navigate to the folder that contains your adb.exe and fastboot.exe
Win 7/8: Shift + right click and select "Open command window here".
For Win XP click here
select 'Run' from the Start menu, type
Code:
cmd
and hit Enter. In the resulting command prompt type
Code:
cd C:\adb\ [I](or whatever the path to your fastboot folder is..)[/I]
In the command window on your PC type:
Code:
fastboot devices
If that command returns a string of numbers and letters, you are good as gold.
Click me: View attachment 3070087
If it returns: "No devices found", fastboot is not working - yet - and you have to troubleshoot.
Getting the correct drivers working can be the hardest part of this exercise. If your computer does not "see" the tablet in fastboot, try to uninstall the existing driver (if any) in Device Manager and manually install the drivers I linked to above. And if Windows does not cooperate at all, PM me and I can hook you up with a Puppy Linux live CD with fastboot/adb set up already.
Let's assume everything is good:
On your computer go here: https://dl.twrp.me/tf300t/
Download the latest version of TWRP.
FYI ONLY: If, for whatever reason, you want to format your data partition:
Formatting /data starting with TWRP 2.7.x and later takes a lot longer than in previous versions (up to 90 minutes). LET IT FINISH. DO NOT INTERRUPT THE FORMATTING.
Rename the file to twrp.blob and place it into the same directory as your fastboot.exe. Note: More recent versions of TWRP download with an .img extension. Leave the extensions as is, rename the first part to watever is easy to type
Again check the connection with
Code:
fastboot devices
If you get the connection, in the command window type:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
or
Code:
fastboot -i 0x0B05 flash recovery twrp.img
This will flash the recovery to the recovery partition
If it is successful type:
Code:
fastboot reboot
and let the tablet boot up normally.
You may get a dialog in TWRP offering to root the stock rom. You can accept or cancel it - doesn't matter. I assume you are going to install a custom rom and they are rooted anyway.
Create a nandroid
Your almost there! You are now on the stock ROM with a custom recovery installed.
Power the tablet down and boot into the bootloader menu with Volume Down and Power buttons.
With RCK flashing, push Volume Up and you should boot into TWRP. Familiarize yourself with the many options of the touch based interface without executing anything yet. TWRP is very user friendly. You basically cannot do anything of consequence "by accident", so don't be shy.
To create your Nandroid (a full system backup) touch "Backup", leave the default selection as they are and swipe the button to create a nandroid of your current system.
This is a very healthy habit to develop: You always want to have a nandroid of your last working system squared away so that you can do a simple restore if you flash something that does not work, or something goes wrong during a flash. With a working recovery and a good nandroid you are minutes away from a working system if you soft brick your tablet.
Hint:
It's a good idea to have at least one good nandroid on external media. Sooner or later you will format your data partition and if you're like me, you may forget to backup your nandroids in the heat of the moment..
Installing a custom ROM
From here on out it's as easy as downloading the installation file of your custom ROM, booting into TWRP, choosing "Install" and navigating to the zip of the ROM you want to flash.
If you see a "signed" in the zip file name (best_rom_ever_signed.zip), make sure you check "verify zip signature" under the "Install" menu. Some devs sign their ROM zips - a better way to ensure file integrity than md5 sum.
Whatever you decide to flash: READ THE OP of the corresponding thread and make sure you have the correct bootloader and the required recovery installed! I can't stress this enough! If you are not sure, DO NOT FLASH!
Look for the ROMs in the Development section of the XDA forum for this tablet: http://forum.xda-developers.com/transformer-tf300t/development
It is mandatory to do a Factory Wipe in TWRP before installing a custom ROM or going from one ROM base to another (a so called clean install).
If you choose 'Wipe' in TWRP, all you have to do is swipe the button - 'Factory Wipe' is the default selection under the 'Wipe' menu. You will loose your apps, but it will not wipe your /data/media/ folder where your files, pictures, etc live.
If you do this right before flashing the custom ROM, make sure you have the zip file of your custom ROM on your microSD - not on your internal SD where it may get wiped....
Once you installed a custom recovery NEVER EVER UNDER ANY CIRCUMSTANCES - AND I REPEAT: NEVER! - use the 'Wipe Data' option from the bootloader menu or the "Factory Reset" option in Settings > Backup&Restore.
In your custom recovery you have the option to wipe, backup and restore every partition on your tablet selectively or collectively. Any wiping, any backup and any restore of the system, data, recovery or boot partitions MUST be done in your recovery (or in fastboot)!
You can safely use Titanium Backup or Asus Backup for apps and settings, but that's it. For everything else use your recovery.
FREE ADVICE
There are alternative methods to flash a recovery to your device using apps like GooManager (currently not supported anyway), TWRP Manager or Flashify from the Play Store which do it right from your tablet. These apps "save you the trouble" of getting ADB and fastboot set up and working on your PC. These methods still exist and they do work - mostly - and if you have root. But I would not recommend them.
If you are not willing to invest the time to learn the basics about ADB and fastboot (google "adb fastboot xda tutorial") and install the necessary drivers on your PC, you should not be flashing anything to your tablet!
GET ADB AND FASTBOOT WORKING!
Sooner or later you will do something stupid (I have done it and so will you) and ADB/fastboot may save your bacon IF you had it working when you didn't really need it.
Hit the 'Thanks' button and rate the thread 5 stars if this helped you
Click to expand...
Click to collapse

Save it for later

Mine

sbdags said:
@stamatis could we sticky this please.
Brilliant post Bernd :good:
Click to expand...
Click to collapse
Can we make that happen here to @stamatis
Thx Josh

Nice one Bernd! :good::good:

boot sequence
Hi,
Is normal to see three TUX and some phrases at the power on ?
Can I hide it ?
tnkx
Nicola

You mean the penguins?
That's normal I'd you're running a Rom that uses _that's preinit scripts. You can't hide them - why would you?

thank you SO much
I love you!
Wow, I've never had so much trouble rooting a device before! And days ago, I rooted my T700 without any problems. So, I guess I should have expected the hubby's TF300T to be problematic! Recoveries didn't work, I tried multiple ones. Eventually, I had a recovery that didn't recognize any partitions. I used fastboot to erase them all and put the stock ROM back on--wouldn't boot up. This thread was an immense help! I've moved the other recoveries and ROMs into my non-working folder!
Thanks again!
Lynne

Awesome
What a well written guide! I have a decent understanding of fastboot and adb (although minimal experience), and I perfectly understood every step.
My advice to all newbies like me.... Read stuff ALL of the way through (and understand it), BEFORE stepping off in it.

ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris

scuzzo said:
ok im a bit lost... i have rooted both Nexus 7s, nook hd and hd+, a tf101, and a few tv boxes.. so im not sure why this is hanging up... im trying to root and install the TWRP recovery on a tf300... followed the instructions and even have the char string that means... every thing should be good to go.... have checked that the twrp is in the dir of adb... but when i try to push the twrp.blob to the tf300, it just give me.. this error..
c:\adb>fastboot devices
015d14febf64041b fastboot
c:\adb>fastboot -i 0x0B05 flash recovery twrp.blob
sending 'recovery' (6800 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.002s
so.. at this point i not sure what else to trouble shoot... the tablet is in fastboot mode.. adb sees the tablet.. at least that is what the char string confirms.... so any help would be very much appreciated.. just a bit lost on this...
chris
Click to expand...
Click to collapse
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh

lj50036 said:
The bootloader is unlocked yes ?
What is your bootloader version ?
Try a different USB port ?
Thx Josh
Click to expand...
Click to collapse
hello,
bootloader is unlocked or at least it says it is at the boot screen.. "your device is unlocked"..
real time... just swapped ports... its says it pushed the recovery.... so... will continue along this path.... and see how it goes.... i think its good to go... just as you suggested... port swap... cool... i bought this just so i could root it and put the kit kat kis rom on it.... thanks for your help and big ups to OP.... great guide ...
thanks again.!

Nice guide!
I've been wanting to put a custom rom on my transformer for a long time. This guide worked like a charm.
The only problem I had was when I tried to flash TWRP recovery, but switching USB port fixed that problem.
I flashed the latest CM12.1 nightly and it works fine.
Many thanks!

Help please, I'm stuck!
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks

You won't see anything on the tablet screen, but what does the command window say?
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk

berndblb said:
You won't see anything on the tablet screen, but what does the command window say?
The command window didn't say anything, just blinking cursor after my command line
Go back, read the guide again, it's all in there....
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
Mishka79 said:
I'm trying to flash recovery,
after typing:
fastboot -i 0x0B05 flash recovery twrp.blob
I got this on tablet screen:
"Starting Fastboot USB download protocol"
for about 25-30 already and nothing happens, any ideas?
thanks
Click to expand...
Click to collapse
Thanks,
After writing the question, I've restarted my tablet and did all the steps again.
The second time everything worked as it should. :good:
thanks for your great guide

Really great guide
Amazing guide thanks for the help

Thank you for this good tutorial but I have one question.
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!

ANDROIDYER said:
I'm a newbie here, here is my dilemma: I've flashed CM android 5.1.1 successfully from stock 4.2. (Thanks for this detailed tutorial), but I lost my root privileges, now I can't use my root apps. How do I apply root to this ROM? My device is an ASUS TF300T. I've tried Kingo Root and King Root but no success.
I would really appreciate your help and inputs.
Cheers!
Click to expand...
Click to collapse
I have not used CM in quite a while but I think you have to enable root in Developer Options. I think it is not enabled by default.
If hat does not work you can go to Chainfire's website and download the flashable SuperSU and just flash it in recovery

Thanks and a couple of notes on TF300T
Thanks so much for the great guide. My 300TF was nearly bricked due to slowness and freeze-ups. I'd stopped using it. The process worked and am now running KatKiss. Couple of problems and their solutions for anyone who may have the 300TF:
-When trying to "Unlock Bootloader" I kept getting to "enter Google password" but when I did so (correctly) it was not accepted. The solution was to do another factory reset and NOT install google services. Didn't ask for password after that.
-Used fastboot command line to install "twrp.blob" but nothing happened and it timed out. I had to take out other usb connect programs first (in my case "easy-tether" and my LG phone connect app.) After that everything went as per your guide.
Thanks again
Geneg

Need some help with flashing Oreo B3

Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx

I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.

q13017 said:
Hi.
I was having trouble when I try to follow the method on essential's site.
Here's what adb told me:
"opening 'ota_file.zip'...
connecting...
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information."
Did some research on google. But sadly still don't know how this happened. Plz, help me, if you know what to do. thx
Click to expand...
Click to collapse
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download

jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
I just wait until the bts is available. I've had bad luck sideload in.
Sent from my PH-1 using XDA Labs

avd said:
I just wait until the bts is available. I've had bad luck sideload in.
Click to expand...
Click to collapse
I have gotten the essential today and the first thing I did is flash Android O and everything seems flawless

avd said:
I just wait until the bts is available. I've had bad luck sideload ing.
Click to expand...
Click to collapse
And if your bootloader is locked you can't fallback to other methods of your system goes wonky even if we have an a/b system.
Sent from my PH-1 using XDA Labs

Airwolf79 said:
I suggest trying to flash the stock dump OB3 from here:
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
I assume you already unlocked the bootloader.
You will need to unlock critical as well, but if you got ADB up and running already, should be easy.
Download and unzip the OB3 dump.
Unzip and place all files where fasboot is placed, should be platform-tools.
fastboot flashing unlock_critical (will wipe entire phone)
Then run the flash-all.bat in terminal (you can just drag and drop the flash-all file into terminal)
If successful, run fastboot -w to format data just for good measure.
If unsuccessful, open the flash-all in a text editor and copy paste the commands one at a time in terminal, enter after each one.
If not able to get either to work, DO NOT REBOOT. ask for more help.
Click to expand...
Click to collapse
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.

jamesst20 said:
Normally you should be able to adb sideload with a locked bootloader and the original recovery.
Try another computer or USB-C cable, and yes USB-C cable quality does make a big difference.
Double check these
1. Bad drivers (i.e dont use Leca driver, but Google usb driver)
2. Bad USB Cable
3. Too outdated adb version
4. Bad flashable zip download
Click to expand...
Click to collapse
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...

q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail

q13017 said:
Thx for the help,
1. I used the one provided on the official website.
2. The one comes with the phone. (My motherboard do support Type-c Male to Male )
3. I'm pretty sure it is the newest version.
4. Maybe...
Click to expand...
Click to collapse
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs

avd said:
The one that change with the phone is not for flashing
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
Yeah, don't use the charging cable for flashing. Essential has confirmed that some phones have been bricked using their included cable.
Sent from my PH-1 using Tapatalk

jamesst20 said:
It only works with fastboot factory images. These are recovery flashable zip as far as I know.
Also, you need unlocked bootloader to flash factory images and in case you are already unlocked, you could just push the zip into your phone and use twrp to flash it.
You could try booting your phone with usb debugging enabled and see if the command "adb push file.zip /sdcard/Download"
If this command fail aswell, it's probably driver related or cable. I don't think an invalid zip would make it fail
Click to expand...
Click to collapse
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!

q13017 said:
Anyway, fastboot flash method works for me. There's a guy post the dumped image files above. Thx for your help!
Click to expand...
Click to collapse
No problem! Then you had an unlocked bootloader

q13017 said:
Just wondering if I can delete -w to save user data? LIke the old day nexus devices.
Click to expand...
Click to collapse
Doesn't matter. If you use the fastboot method, you need to unlock the bootloader AND unlock critical, which will wipe user data anyway, unless you had already done that previously. You can try the sideload method with stock recovery, but if you're not able to get that to work, you don't have a choice but to unlock and try the fastboot method.

I'm trying to install Beta 3 (I'm coming from stock NMJ51B), but the sideload will end at 94% and I get the Message:
Unable to open sysfs usb node (no such file or directory) Trying configfs failed to set driver control: No such device
Install from ADB complete
The PH-1 will then boot just fine and everything seems to work.
Any ideas?

power-on+volume-up ..bootloader running?
Was problem solved?,I wanted looking for solved of same things.Just I found it's lost my process of running fastboot.

Root & TWRP!

Note: I am no expert at this. I used this to get TWRP and root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download Magisk's installer zip on your phone from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (Google Pay only works with Magisk v19.0+)
Download arter97's kernel .img to your PC. This kernel currently is the only reliable way to get TWRP. https://forum.xda-developers.com/razer-phone-2/development/arter97-kernel-razer-phone-2-t3914996
Reboot your phone into bootloader mode (Turn off then back on while holding vol down).
Make sure your phone is recognized by Windows before proceeding. Follow this guide to setup the proper drivers and fastboot.
Flash arter97's kernel by running
Code:
fastboot flash boot arter97-kernel-*.img
If you run into any issues, then you will probably need to specify the slot to flash. Reboot back into your system.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a arter97-kernel-*.img
if _b use
Code:
fastboot flash boot_b arter97-kernel-*.img
Reboot to recovery (either through bootloader mode or hold vol up while rebooting).
Install the Magisk .zip from TWRP.
Be amazed by the possibilities.
Old instructions (Should always work to get root):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer when in bootloader mode so I had to install the Google adb drivers and manually set the driver used to Google Bootloader Interface (or something like that)

I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.

figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3

Twiggy000b said:
figured itd be as easy as that. this will be my first up to date device in years, att sending it to me in the mail. should get it by the 6th . but glad to see theres root! hopefully lineage to follow <3
Click to expand...
Click to collapse
I know the feeling, my last device was the Nexus 5

my last "decent" device was the essential phone. then i went to the xperia xa2 ultra, then the iphone 6 then.... zte quest. -.-

CurtisMJ said:
I found you needed to specify boot_a or boot_b specifically as the bootloader tended to mess up the suffix(it tried "bootb_b"????). So I had to first run "fastboot getvar all" to check the current slot.
I also found the commands are executed much more reliably if you enter the command first and press enter so fastboot goes into the "waiting for device" state and then boot into the bootloader and afterwards plug in the cable so fastboot executes the command as soon as it connects.
Click to expand...
Click to collapse
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot

CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down and run `fastboot flash boot patched_boot.img`.
Reboot, and open up magisk manager to confirm everything is working.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?

CalebQ42 said:
Lol, bootb_b:laugh:. For me at least it worked fine without specifying the slot, though I may change the instructions to specify the slot
Click to expand...
Click to collapse
Interesting. The bootloader isn't exactly what I'd call a masterpiece of coding (weird cause I still maintain the ROM is excellent) so it might have just been a momentary glitch.
---------- Post added at 10:54 PM ---------- Previous post was at 10:53 PM ----------
ctakah27 said:
Does this destroy all data? Do I need to unlock bootloader? Does it matter where I place the boot.img on my device?
Click to expand...
Click to collapse
Yes, yes and not really (you get a file chooser so you just need to locate it)

I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!

CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
Good luck it's a easier process compare to years ago. I would do it but I have no need for root or custom recovery. If you fail on the TWRP I will do it in time for people.

Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.

CalebQ42 said:
I updated the post a bit with instructions on how to flash to a specific slot.
Tonight I'm going to try compiling TWRP for the first time ever (unless someone beats me to in). Wish me luck!
Click to expand...
Click to collapse
jonchance_84 said:
Is this working on the AT&T version of this phone? Or would you need to flash the global firmware in order for this to work? Looking to upgrade to this phone and I want to be sure I can get root. The rest looks to be coming fairly quickly.
Click to expand...
Click to collapse
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE

Warrior1988 said:
They have the image for AT&T
EAIaIQobChMIwYzbk7j_3gIVRZRpCh0RMwdoEAEYASAAEgLPifD_BwE
Click to expand...
Click to collapse
I see the separate firmware. I'm only asking because of past shadyness from AT&T trying to tell manufacturers what to do. Years ago on my Xperia x10, if on AT&T firmware, you needed to flash the global generic firmware to get around their crap.

CalebQ42 said:
With the release of the factory images we can achieve root via Magisk boot image patching. Note: I am no expert at this. I used this to achieve root, but it there is no guarentee it won't brick your phone. Only do this if you know what your doing. Before you start you must have an unlocked bootloader, which will delete all your data. Here's the instructions (If you need help, feel free to post a comment):
Download the factory image from here: https://developer.razer.com/razer-phone-dev-tools/
Extract and copy the boot.img file to your device
Download and install Magisk Manager. If you have an SD card make sure it's installed on your internal storage, not the SD card.
Tap install, select Patch Boot Image File, and select the boot.img (If using the default file manager click the overflow menu and show internal storage)
Copy the patched_boot.img back over to your PC
Flash the patched_boot.img to your device via fastboot (Turn off then back on while holding vol down) and run
Code:
fastboot flash boot patched_boot.img
.
If you run into any issues, then you will need to specify the slot to flash.
Turn on Android Debugging and run
Code:
adb shell getprop ro.boot.slot_suffix
and make note if the output is _a or _b
Reboot back into bootloader
If _a use
Code:
fastboot flash boot_a patched_boot.img
if _b use
Code:
fastboot flash boot_b patched_boot.img
Reboot, and open up magisk manager to confirm everything is working. After an OTA update you may have to re-apply due to it using a different slot.
Note: the phone wasn't properly recognized by my computer so I had to install the Google adb drivers and manually set the driver to Google Bootloader interface (or something like that)
I also tried to install some Android Pie GSIs, but none of them worked.
Click to expand...
Click to collapse
Would this procedure be the same as far as mac/win?

I understand all of that, I am simply asking if someone has tried this with the AT&T variant yet. I want to know before I go order this phone.

I love a rooted phone, but as far as I know, if you unlock the bootloader, Netflix will no longer work in HD mode. To me, this is a deal-breaker. If anyone knows about a work-around, I'd love to know.

Razer phone 2 root
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen

andy1011 said:
so im kinda new to rooting this type of phone and to the android boot scheme in general. i have a razer phone 2 and have attempted (febaly) to root it using this meathod. after installing the google adb drivers i was unable to see the device from my pc when it was in fastboot and unable to send commands, after installing the drivers again with windows update it ran even though no device was detected with this message
">fastboot flash boot patched_boot.img
Sending 'boot_b' (19268 KB) OKAY [ 0.523s]
Writing 'boot_b' OKAY [ 0.179s]
Finished. Total time: 0.718s"
it then blackscreened, i then tried a factory reset from recovery, and it is now in a bootloop... any advice?
update: no longer in boot loop but now is full blackscreen after a glitchy install screen
Click to expand...
Click to collapse
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next

CurtisMJ said:
Since it's already wiped the easiest way to fix it is to probably flash the full factory image. Did you happen to update to the MR2 update prior to following this guide? Doing this on MR2 will soft brick. Not entirely sure in what way, but I assume it would be similar to what you experienced. If you were still on MR0 you can actually just fastboot flash the original kernel image to fix it. I just finished rooting MR2 so I'll post that next
Click to expand...
Click to collapse
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.

andy1011 said:
this is what im trying to do. however i have no way of flashing to the device as adb is unable to see the device.
Click to expand...
Click to collapse
Adb and fastboot are separate things. You should only need download mode and fastboot. What are you trying to use ADB for? If in doubt, the guide on Razer's website should be quite sufficient
EDIT: You can get to download mode by holding Vol Down and Power Button while the device is off. You can force reboot by holding down power for approx 15s as well

[How to] Fix 'sensors and camera not working', restore IMEI, etc. (Stock Pie)

At some moment when playing with Magisk modules, I've got Android crash, after which sensors (Accelerometer, Gravity, etc.) and Camera stopped working.
Obviously, somehow persist partition data got corrupted and must be reflashed. I believe, that flashing persist via fastboot is not supported, so I reflashed it via ADB, and got everything working.
What we'll need to flash persist partition:
1. Mi A2 with unlocked bootloader and critical partitions, on stock Pie 10.0.2.0 to 10.0.7.0, connected to an USB 2.0 port in PC MB; USB debugging and MTP file transfer enabled;
2. Working copy of ADB / Fastboot installation
3. image of persist partition, can be found in each stock fastboot image
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
4. twrp-3.3.1-5-jasmine_sprout-unofficial.img, copied to ADB / Fastboot installation directory
https://forum.xda-developers.com/mi-a2/development/recovery-mi-a2-jasminesprout-t3941096
Note: even if TWRP boots with black screen, this method should work as we'll not control process on Mi A2, instead we'll use ADB commandsthis TWRP is reported to work with all variants of MiA2 screen panels.
5. Attached command file "flash_persist.cmd", unZIPped to ADB / Fastboot installation directory.
Instruction:
Run "flash_persist.cmd" from CMD shell or Explorer (probably admin rights needed?).
Command file execution will be paused several times, waiting for ADB and fastboot commands execution.
Please read CMD window output, check that phone is being switched to needed mode and/or ADB/Fastboot commands succeed.
In case something goes wrong, press Ctrl^C and terminate batch job.
After 1st reboot from TWRP, reboot once more by standard means.
Update:
- attached f"lash_persist_V2.zip" using "twrp-3.3.1-5-jasmine_sprout-unofficial"

my mi a2 is in ARB4, I can only use MIUI, could you tell me how do I get the persist file, could also explain where TWRP comes in since the command is made by ADB?

Aerobatic said:
At some moment when playing with Magisk modules, I've got Android crash, after which sensors (Accelerometer, Gravity, etc.) and Camera stopped working.
Obviously, somehow persist partition data got corrupted and must be reflashed. I believe, that flashing persist via fastboot is not supported, so I reflashed it via ADB, and got everything working.
What we'll need to flash persist partition:
1. Mi A2 with unlocked bootloader and critical partitions, on stock Pie 10.0.2.0 to 10.0.7.0, connected to an USB 2.0 port in PC MB; USB debugging and MTP file transfer enabled;
2. Working copy of ADB / Fastboot installation
3. image of persist partition, can be found in stock fastboot image
http://en.miui.com/download-353.html
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
4. twrp-3.2.3-0-jasmine_sprout.img, copied to ADB / Fastboot installation directory
https://dl.twrp.me/jasmine_sprout/
Note: even if TWRP boots with black screen, this method should work as we'll not control process on Mi A2, instead we'll use ADB commands.
5. Attached command file "flash_persist.cmd", unZIPped to ADB / Fastboot installation directory.
Instruction:
Run "flash_persist.cmd" from CMD shell or Explorer (probably admin rights needed?).
Command file execution will be paused several times, waiting for ADB and fastboot commands execution.
In case something goes wrong, press Ctrl^C and terminate batch job.
After 1st reboot from TWRP, reboot once more by standard means.
Click to expand...
Click to collapse
I don't understand either why is twrp involved. I'm at stock 10.0.12 ROM, with unlocked bootloader and usb depuration turned on. Should I get the persist.img from the Fastboot image of 10.0.12? I only see the link to an unofficial one which I don't know in which way is different to the official one...

marcushg said:
I don't understand either why is twrp involved..
Click to expand...
Click to collapse
ADB.exe is sending requests to phone. Usual ROM cannot evaluate these requests, while TWRP is specially developed to perform actions specified by ADB requests.

Thanks for the reply. Now what I'm not sure is if flashing persist.img will delete my original IMEI and Bluetooth and WiFi Mac address. I don't want to lose them.

[/COLOR]
marcushg said:
Thanks for the reply. Now what I'm not sure is if flashing persist.img will delete my original IMEI and Bluetooth and WiFi Mac address. I don't want to lose them.
Click to expand...
Click to collapse
This happens to me, camera and sensors are not working. the solution for this is to flash persist.img from original and official rom. you can get that on miui official website. there you can get the persist.img and flash it on TWRP in Mi6X version not the jasmin_sprout. I have try and tested and sensors and camera on my Mi A2 is working now. Blaming myself by deleting the persist! and persist_back up at the twrp. Not to worry by lost imei and etc. mine is all working fine.

how can i do this on android 10? I say that because twrp is not available for android 10. I have problem with frond camera. it return at secondary back camera. please help me

tnt-4- said:
how can i do this on android 10? I say that because twrp is not available for android 10. I have problem with frond camera. it return at secondary back camera. please help me
Click to expand...
Click to collapse
TWRP_4pda_verison works for me in 9 and 10 stock crypted. See link in item 4 of OP instruction.

Aerobatic said:
TWRP_4pda_verison works for me in 9 and 10 stock crypted. See link in item 4 of OP instruction.
Click to expand...
Click to collapse
sorry i am noob. please give me the link

tnt-4- said:
sorry i am noob. please give me the link
Click to expand...
Click to collapse
'OP' in these forums is mostly used in 2 meanings:
- 'OP' refers to the person who Originally Posted this thread;
- 'OP' refers to the Opening Post in this thread.
So, " See link in item 4 of OP instruction" means:
- scroll page up to the beginning (or go to the beginning of 1st page of a thread, here we still have 1 page);
- then read it carefully;
- find item 4:
4. twrp-3.3.1-5-jasmine_sprout-unofficial.img, copied to ADB / Fastboot installation directory
https://forum.xda-developers.com/mi-...prout-t3941096
Click to expand...
Click to collapse
Do I need to go through alphabet or google search course also? no offence, cheer up!

Aerobatic said:
'OP' in these forums is mostly used in 2 meanings:
- 'OP' refers to the person who Originally Posted this thread;
- 'OP' refers to the Opening Post in this thread.
So, " See link in item 4 of OP instruction" means:
- scroll page up to the beginning (or go to the beginning of 1st page of a thread, here we still have 1 page);
- then read it carefully;
- find item 4:
Do I need to go through alphabet or google search course also? no offence, cheer up!
Click to expand...
Click to collapse
thanks for all. i will try to do it beacause the front camera is very usefull.

Persist.img flash via flashed_persist.cmd or flash with twrp??

tnt-4- said:
Persist.img flash via flashed_persist.cmd or flash with twrp??
Click to expand...
Click to collapse
Read OP carefully and try to Google about ADB, TWRP, etc. to understand the process. Why should we do your homework instead of you?
In brief, again and again:
1. TWRP is needed to be booted into phone, as it is the only valid means to perform ADB requests from PC.
2. TWRP has no options to reflash /persist partition from its UI
3. /persist partition image is flashed into phone from PC using ADB commands, so:
3.1. PC is to be prepared (drivers installed, latest platform-tools with ADB unpacked and tested to work, persist.img unpacked and copied into platform-tools directory)
3.2. phone is to be prepared (successfully connected via USB and then booted into TWRP with command from "flash_persist.cmd").
4. "flash_persist.cmd" is just Windows::CMD command file, helping to make ADB / fastboot / ADB requests from PC to phone/TWRP in correct order, and with intermediate checks of successful connection / mode switching: rebooting into bootloader (ADB command), booting into TWRP (fastboot command), and then reflashing /persist (ADB command)
You can read it, e.g. in Notepad, and try to understand what it should make, Googling for Windows::CMD commands and ADB commands descriptions.

Aerobatic said:
Read OP carefully and try to Google about ADB, TWRP, etc. to understand the process. Why should we do your homework instead of you?
In brief, again and again:
1. TWRP is needed to be booted into phone, as it is the only valid means to perform ADB requests from PC.
2. TWRP has no options to reflash /persist partition from its UI
3. /persist partition image is flashed into phone from PC using ADB commands, so:
3.1. PC is to be prepared (drivers installed, latest platform-tools with ADB unpacked and tested to work, persist.img unpacked and copied into platform-tools directory)
3.2. phone is to be prepared (successfully connected via USB and then booted into TWRP with command from "flash_persist.cmd").
4. "flash_persist.cmd" is just Windows::CMD command file, helping to make ADB / fastboot / ADB requests from PC to phone/TWRP in correct order, and with intermediate checks of successful connection / mode switching: rebooting into bootloader (ADB command), booting into TWRP (fastboot command), and then reflashing /persist (ADB command)
You can read it, e.g. in Notepad, and try to understand what it should make, Googling for Windows::CMD commands and ADB commands descriptions.
Click to expand...
Click to collapse
I understand that. I have unlock bootloader and criticals. Then i need run twrp.img on cmd to boot twrp. Then?? Sorry for my questions i am afraid for my phone. I dont want to destroy it with any fault step

tnt-4- said:
I understand that. I have unlock bootloader and criticals. Then i need run twrp.img on cmd to boot twrp. Then?? Sorry for my questions i am afraid for my phone. I dont want to destroy it with any fault step
Click to expand...
Click to collapse
Then read everything I wrote and understand what you are going to do.
Again: read text in "flash_persist.cmd" and make sure you understand each line in it.
At this I stop helping you, I'm to make my work, I'm really busy.

Aerobatic said:
Then read everything I wrote and understand what you are going to do.
Again: read text in "flash_persist.cmd" and make sure you understand each line in it.
At this I stop helping you, I'm to make my work, I'm really busy.
Click to expand...
Click to collapse
i've done it but my front camera still not working. when return it returned at secondary. :crying:
Then i disassembly my phone and disconnect my camera. I open my phone again and did the same thing. Finally i reconnect the camera and it works!! Thanks fo all Aerobatic

Would this work on a V11.0.6.0.QDIMIXM?
Also, where can I find the persist files for it?

valp88 said:
Would this work on a V11.0.6.0.QDIMIXM? Also, where can I find the persist files for it?
Click to expand...
Click to collapse
Yes, it should, if this is really /persist corruption issue, and not HW problem. Diagnostics can be made running tests in engineering mode or with 3rd-party apps like AIDA64: if most or at least several sensors are misbehaving or disfunctional, this is the direct prompt to reflash /persist.
As for your question, It is always recommended to read the OP:
Aerobatic said:
3. image of persist partition, can be found in each stock fastboot image
https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849
as "jasmine_global_images_V10.0.2.0.PDIMIFJ_9.0\images\persist.img"; must be copied to ADB / Fastboot installation directory.
Click to expand...
Click to collapse
Latest variant of persist.img for A10 can be found in unofficial repack of 11.0.8.0 OTA, link was published in https://forum.xda-developers.com/showpost.php?p=82370929&postcount=42.
Funny fact, but someone wrote in these forums that he solved his problem with corrupted /persist (being on Pie?) using image from the 1st official fastboot image for Oreo (V9.6.9.0.ODIMIFE, link in the thread pointed to in OP and above.)

Will it work with WIfi problems in MIUI for Mi A2
I'm using Custom Rom named as Derpfest and i had also flashed MIUI 11 but my wifi doesn't works in MIUI while it works perfectly for Derpfest.

steps please?
tnt-4- said:
i've done it but my front camera still not working. when return it returned at secondary. :crying:
Then i disassembly my phone and disconnect my camera. I open my phone again and did the same thing. Finally i reconnect the camera and it works!! Thanks fo all Aerobatic
Click to expand...
Click to collapse
Can you describes the steps... yo disassembly and disconnect the camera module, and then? you power it on?