Database Develop

[Q] Restore from Fastboot or other method?

So basically Im stuck.
After goofing around with this thing I wanted to restore to stock. I didnt back up any bloat software and attempted this.
Now im stuck where it wants you to add accounts, upon hitting next it asks for my location permissions, then it crashes because of myaccount.apk, then that loops.
After playing around im totally botched...
Booting normally leads me to a "AP Fastboot Flash Mode (Last Flash Failed)" screen. I can kill that and get to the "Boot Mode Selection Menu" as well. Selecting recovery from that menu will erboot to the typical dual core boot screen, then back to "invalid flash mode"
Long story short - is there a file or method that will get me back to factory from here?

You can use psouza4s tools to restore your /system/app.
Sent from my DROID3 using xda premium

From what boot mode though? I cant get IN to android so I cant connect via ADB.
Boot Menu results:
Normal Mode: Invalid Flash Mode
Recovery Mode: Invalid Flash Mode
AP Fastboot: ALL GOOD
BP SBF Flash: ALL GOOD
BP Only: Sits at the M Dual Core Screen - But device is detected
AP BP USB Bypass: Sits at the M Dual Core Screen - But device is detected
BP Tools: Invalid Flash Mode
My guess is I need to flash a recovery file somehow to get to a proper recovery, then some kind of update.zip or such I can flash.

edru said:
From what boot mode though? I cant get IN to android so I cant connect via ADB.
Boot Menu results:
Normal Mode: Invalid Flash Mode
Recovery Mode: Invalid Flash Mode
AP Fastboot: ALL GOOD
BP SBF Flash: ALL GOOD
BP Only: Sits at the M Dual Core Screen - But device is detected
AP BP USB Bypass: Sits at the M Dual Core Screen - But device is detected
BP Tools: Invalid Flash Mode
My guess is I need to flash a recovery file somehow to get to a proper recovery, then some kind of update.zip or such I can flash.
Click to expand...
Click to collapse
First of all . . . don't wipe. Second of all, have you tried the booting into bp tools method with your terminal/power shell set to:
Code:
adb wait-for-device shell

rynosaur said:
First of all . . . don't wipe. Second of all, have you tried the booting into bp tools method with your terminal/power shell set to:
Code:
adb wait-for-device shell
Click to expand...
Click to collapse
Too late. Wiping is how I ended up in this position :/ - And Im unable to do the adb wait command because BPTools gives me invalid flash mode.

if there was a way to get a backup in a recovery update.zip form place on a sd card and use the recovery menu

Again here is what happens when selecting different boot modes.
Boot Menu results:
Normal Mode: Invalid Flash Mode
Recovery Mode: Invalid Flash Mode
AP Fastboot: ALL GOOD
BP SBF Flash: ALL GOOD
BP Only: Sits at the M Dual Core Screen - But device is detected
AP BP USB Bypass: Sits at the M Dual Core Screen - But device is detected
BP Tools: Invalid Flash Mode
So recovery is not an option as you can see.

Boot to where your phone is detectable use psouza4s tools get the system restore apps he provides his tools will install them ... all bloatware will be back..

Anyone who has a bricked DROID 3 phone (Verizon only), I may have a solution for you.
Requirements:
Windows platform
7-zip installed (and know how to extract files)
ability to follow all instructions exactly
willingness to factory reset/lose data on their phone
This unbrick method is NOT guaranteed to work, but it's very hopeful for most situations where other methods aren't working. If you are in desperate need of a fix, send me a PM and I'll link you some files to try.
Lastly: I will not be walking through anyone step by step on how to run this procedure -- the included instructions should be more than enough for most people. If you read the instructions and are thoroughly confused, then this fix isn't for you.

Bricked razr i Hellp

(Before, sorry for my bad english, I'm Poland..)
I've receive my Razr i xt890 yesterday and today I have unlock the bootloader. i root.exe
Everything happen very good, my bootloader is unlock but when my phone reboot it'll go to fastboot over and over again.
In fastboot, I can see :
"AP fastboot flash moide (secure boot)
20.00 (sha - bdfb943)
IFWI info 42.21
eMMC info
battery (okay) 4.18v
connect USB data Cable
ROM-key : motorola -key
Boot mode selection menu:
- normale powerup FAILURE crashes
- recovery FAILURE crashes
- factory FAILURE crashes
- BP tools FAILURE crashes
- switch console [default: null] work
- power of " work
And, it's written in yellow :
dismatched partition entry array crc32
" fastboot reason : sticky bit fastboot
fastboot : max download size: 100MB
In addition, the vol down button work for scroll, but the vol up button work, so, I can't select boot mode selection.. crashes
Rsd lite USED to flash CFC_signed_customer_8.7.1I-110_IFW-DE-31_RTEU.xml
There is an error ---- fAILED FLASHING PROCESS . 3/11 FLASH MOTOBOOT "MOTOBOOT" - PHONE RETURNED FAIL
And, it's written in yellow ITS FHONE:
Getvar max-download -size
downloading...
Flashing gpt ...
OEM fb_mode_set
Getvar max-download -size
downloading...
E: Downgarded security version for logo
fastboot command failed
Is there a solution please?
Help me please!!!!!

Why have you copy this post?! : http://forum.xda-developers.com/showthread.php?t=1945176
Your phone isn't brick if you can go into fastboot mode.
To repair your phone you have to flash a homemade fastboot with a command on cmd, like that: fastboot flash boot "name of your boot".img
Go on the link and read the thread , all is explain.
Good luck and don't worry your phone isn't dead

PELLET Nolwenn said:
Why have you copy this post?! : http://forum.xda-developers.com/showthread.php?t=1945176
Your phone isn't brick if you can go into fastboot mode.
To repair your phone you have to flash a homemade fastboot with a command on cmd, like that: fastboot flash boot "name of your boot".img
Go on the link and read the thread , all is explain.
Good luck and don't worry your phone isn't dead
Click to expand...
Click to collapse
Do not look at this post I copied my description of a test in different ways. Compare that everything is copied.
FOR IN cmd fastboot me wondering. And nothing helps.

rymaz said:
Do not look at this post I copied my description of a test in different ways. Compare that everything is copied.
FOR IN cmd fastboot me wondering. And nothing helps.
Click to expand...
Click to collapse
if you still need help pm me. i speak polish

Mi3w failed booting into system

Hello,
Problem - Device keep on rebooting showing Mi logo (every 2 sec), Does not boot into system
What I did?
exteneded system partition to 1.2 gb - success
flash Marshmellow custom rom - success
misinstalled system ui of theme - system ui stopped
reinstalled clean rom from custom recovery - success
then it does not boot into system - keep on rebooting at mi logo (every 2 sec)
tried fastboot rom - failed (remote size too large)
rebooted into recovery
flash stock partition via adb - success
fastboot flash (with flash all) - success (says miflash - operation compeleted successfully)
Still it does boot into system - keep on rebooting at mi logo (every 2 sec)
Help?

if you can access recovery now then go to recovery and take a backup of current rom. The wipe everything except internal storage and then restore the backup.
maybe it'll fix it because thats what happened to me too after flashing the MM custom rom. Every time i was rebooting the phone kept bootlooping at Mi Logo.

Hmm i ll try but i have to install twrp from adb for backup.
Cwm backup not promising.
You think there ll be problem in hardwere?

No problem in hardware.
and yes do it twrp only. never try cwm.

the thing is i am not able to enter into recovery mode at all.

No recovery and fastboot accessible.
Then connect it to PC and tell me what name the device manager shows for the device.

fastboot is accessible.
i've flashed fastboot rom from miui. successfully completed. but it won't boot.
yesterday it booted into system so i was charging the phone, as soon as i removed charger it went the same boot looping.
now,
clicking flash_all_except_storage from fastboot command
it shows one line in every process - 'target reported max size 80909989 '
process goes on and success.
but does not boot into system. same bootloop.

one strange thing is,
when i connect to pc, - just by pressing vol down button i'm entering to fastboot. (even without holding power button)
does this mean there's something wrong with power button which causing cont. reboot? i mean it cont. forcing system to on and off? :s

Nothing is wrong with the hardware. In this situation the phone boots into fastboot by pressing vol when plugged in.
You didn't answer my question. What does it show in device manager on PC.

sorry for late reply , net connection loss
device manager
1st one is android booloader interface
other devices - bluetooth peripheral devices

Did you use miflash tool to flash fastboot rom

yes,
flashed successfully says miflash.

While flashing using miflash did you select all files in advanced menu properly.
Like all the bat, mbn and xml files.

i didnt try all the file separatly.
trying now.

Then go to advance and choose all the respective files properly.
1st one - flash_all_except_storage.xml
2nd one - nvflash_all.bat (leave it as it is)
3rd one - MPRG8974.mbn
4th one - 8974_msimage.mbn
5th one - rawprogram0.xml
6th one - patch0.xml

i found
flash_all.bat
could not find nvboot script
flash programmer
boot image
could not find kernelflinger image
could not find UFS provision image
RAW xml file
patch xml file
should i go with files?

Which MiFlash tool are you using.
I used the 2014.05.09.0 version
Try this one.
And extract the fastboot ROM twice till you get the images folder inside the "cancro_images_V7.0.****" folder. There you'll fill all the files.
Then in miflash click browse and select that images folder.
And in advanced options select the respective files which are there outside the images folder.

2015.10.28 version
i ll leave the navboot as it is.
giving it a try.
appreciate your help brother.

If it doesn't work then try my version.
It has proper names of files. To avoid confusion.
And all files are there in fastboot ROM except nvboot

i checked on miui
no halos.bin
tz.bin
these all files?
p.s.
operation completed successfully but same boot loop.
trying your version now.

Mi A2 Can't flash anything via fastboot (bootloader unlocked, oem critical too)

When I flash TWRP
It shows me this
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
PS C:\adb>
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
Code:
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
PS C:\adb>
I try to use another way
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot getvar current-slot
getvar:current-slot FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
PS C:\adb>
But without fastboot devices
Code:
PS C:\adb> fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
PS C:\adb> fastboot flash boot_b recovery.img
sending 'boot_b' (41314 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
-------------------------------------------------------------
UPDATE!!
I just use a USB2.0 Port (USB HUB)
and I got the problem solved!!!!

You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......

bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(

same problem here , please help anyone

cs853120 said:
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(
Click to expand...
Click to collapse
reset your phone once then try........also try to unlock your boot loader & see if you can flash the stock rom from the official website......make sure that the entire rom file is in a folder on your desktop.......for some reason MI flash does not like long system paths.....

cs853120 said:
When I flash TWRP
It shows me this
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
I try to use another way
But without fastboot devices
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
Click to expand...
Click to collapse
Hi there.
I have the same problem. Can't do anything with my phone on any USB 3.0/3.1-Port on my Ryzen desktop (works neither on Win10 nor Linux Mint). I have to use my old Win8.1 Intel laptop and there everything works flawlessly but only on the USB 2.0 port. I used the same tools/commands/Mi-drivers but it only works on the laptop. Tried different drivers for MB/USB-host controller and different cables but to no avail... Connecting the phone and mtp works but no adb/fastboot.
I read on different threads that other people have the same problem with other hardware setups but most of them were able to fix it with MB drivers from the manufacturer instead of the Windows ones. Maybe that could work for you.
For now I keep the laptop around for flashing my A2....

whenever you get "press any key to shutdown" on fastboot it's because of the usb port, use usb 2.0

I have the same problem , and change to 2.0 USB Ports works! Thanks!

Did you found a solution?

Please help. Facing exact same issue. Tried all USB ports on my PC. Switched between Ubuntu and Win10. All to no avail.

It's a USB 3 problem. I had it too in my laptop. You gotta find a USB 2 port, maybe in another PC. Good luck.
Sent from my Mi A2 using XDA Labs

i was also fasing same problem so what is did is
fastboot flashing unlock_critical
then
fastboot oem edl
and flashed stock

Mi A2 Boot loop
The first thing you'll want to do here is extract the factory images archive that you downloaded from your manufacturer's website. For that part, I'd recommend using 7-Zip, as it's free and works with most archive formats , move all of the contents of the archive to the platform-tools folder inside of your ADB installation directory, then open an ADB Shell window in this folder.
Flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders.
there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
//
fastboot flash boot <boot image file name>.img
//
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
//
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
//
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
//
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
//
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
//
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
//
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot
/
Thanks to Android gadget hacks .
P.S : Including today , it was 22nd time that i rooted , enabled camera2api .. but i think till know its useless .

After dealing with this issue for a long time I found that using a USB hub solved it for me.
This is the one I'm using: https://es.aliexpress.com/item/USB-...342.html?spm=a2g0s.9042311.0.0.1d6e63c04tJJe6
Hope this helped!

the same problem
have tried all USB port, unfortunately, no success

Hi everyone,
Today I have a big problem
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks

HELP
bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
Can you help me with my thread?? Thank you!

Same error.

Download TWRP and TWRP installer
DONT CONNECT YOUR PHONE!!
Put your phone in Fastboot
in cmd type
fastboot boot twrp.img (twrp name instead of twrp.img)
Then when you see <Waiting for Device> connect your phone !
Check if it's working.
This was fix for me, when I was unable to even boot into recovery.
Once you boot into recovery, wipe everything, flash twrp zip, and error should be gone

Hey guys,
same issue here but i don't have any usb2.0 port on my laptop now. Any workaround? Totally sure that i used fastboot + usb3.0 on Sony, LG, Samsung ROMs with no hassles whatsoever. Is this only happening with Xiaomi?
Cheers

Is my phone has brick?

My smartphone was running on Android 9 pie. I am saying "was running" beacuse i am in a trouble now... I flashed a custom recovery(TWRP) and I installed a custom rom (LingeaOS) without wipping storage... from that time TWRP shows that "No os installed" .. It restart again and again but without starting android..Whenever I tried to restore my backuped stock rom It shows an error message"Failed to mount /system".. then I flashed another custom recovery(CWM).. And now it restart again and again I've tried to rebboot it in custom recovery mood but I 've failed... Is my Smartphone is bricked?? Is there any way to solve this problem??

This is how to fix it
Naim178 said:
My smartphone was running on Android 9 pie. I am saying "was running" beacuse i am in a trouble now... I flashed a custom recovery(TWRP) and I installed a custom rom (LingeaOS) without wipping storage... from that time TWRP shows that "No os installed" .. It restart again and again but without starting android..Whenever I tried to restore my backuped stock rom It shows an error message"Failed to mount /system".. then I flashed another custom recovery(CWM).. And now it restart again and again I've tried to rebboot it in custom recovery mood but I 've failed... Is my Smartphone is bricked?? Is there any way to solve this problem??
Click to expand...
Click to collapse
Yes, this is called a soft brick.
You can solve the problem by doing the following:
-Your bootloader should be unlocked, and I think you've already unlocked it since you were trying to flash a custom ROM.
-You need to have a STOCK ROM of your exact phone model, this is different from TWRP backup, search google for your phone model's stock rom and download.
-You should have Fastboot and ADB installed on your pc.
-boot to fastboot mode (volume up+power, then navigate to fastboot mode).
-connect your phone to pc with USB cable
-open the folder where you have downloaded the minimal adb and fastboot, and open cmd window there with right lick or click cmd-here.exe
-now type fastboot devices, and there should be an alphanumeric code. This means your device is connected. If it is not showing up, try downloading 'minimal adb and fastboot tool' and clicking cmd-here.exe.
-In the stock rom file, there will be a file called 'firmware', and inside it there should be these files: 'system.img' 'recovery.img' 'cache.img' 'userdata.img' 'boot.img'
-Copy all 5 of these, then go to the folder where you have adb and fastboot, go inside that folder( to the place where you have all the adb and fastboot files like adbWinApi.dll). Now paste the 5 files here.
-open cmd window again, and type the following:
1) fastboot erase boot
2) fastboot flash boot boot.img
3)fastboot erase system
4)fastboot flash system system.img
5)fastboot erase recovery
6)fastboot flash recovery recovery.img
7)fastboot erase cache
8)fastboot flash cache cache.img
9)fastboot erase userdata (this may be called data, if fastboot shows an error message, type data instead)
10)fastboot flash userdata userdata.img
and you are done, this should enable you to restore your phone.
If you are unable to access your bootloader, try flashing your stock ROM with SP Flash tool (if you have a mediatek device). You have to have your stock ROM downloaded on your pc. Connect phone to pc via usb, open SP Flash tool, select your firmware file in the topmost box, and in the box beneath that, select the file ending in scatter.txt from your firmware file. Uncheck 'preloader' if it shows up on your screen, then click 'download'. Do not disconnect your phone during the process. When it is finished, there will be a green tick, and you should be able to restart your device.