Database Develop

Stuck in fastboot, LG L90 D405N

Hello,
I made a mistake of using a .bat file created by someone to unlock my bootloader. After going through the .bat file, I see that it nulled my boot.img file on the phone, so now I'm stuck in fastboot mode (previously nulled LAF to get access). The irony here is that I do have a backup of the boot.img file on both my PC and on the phone's internal memory, but there's no way (atleast I haven't found one) to actually flash it back so it would work. So my question here would be - do you guys have any ideas how should I proceed? I tried using fastboot flash, but all I get in turn is an error:
"FAILED (remote: unknown command)"
Device is not unlocked (as I was trying to get it unlocked). I have no access to anything else other than fastboot.
getvar all outputs this:
(bootloader) display-panel:
(bootloader) charger-screen-enabled: 0
(bootloader) max-download-size: 0x20000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:cache: 0x38400000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:userdata: 0xfbd80000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:system: 0x80000000
(bootloader) unlocked: no
(bootloader) secure-boot: no
(bootloader) version-hardware: rev_10
(bootloader) variant: w7n_global_com Samsung 8GB
(bootloader) serialno: LGD405aa16eaa7
(bootloader) kernel: lk
(bootloader) product: W7N_GLOBAL_COM
all:
finished. total time: 0.041s
Any input to this thread is appreciated!

i need help R1 HD

I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all

This is photo of recovery may help you to help me get it back

KARIM9377 said:
I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all
Click to expand...
Click to collapse
only thing you can do with stock recovery is factory reset.
Was phone bootloader unlocked before the ota.
If so bootloop is normal after OTA, except usually it will not open recovery only fastboot.
did you try "fastboot OEM unlock" like you put above or
"fastboot oem unlock" like it supposed to be?

mrmazak said:
only thing you can do with stock recovery is factory reset.
Was phone bootloader unlocked before the ota.
If so bootloop is normal after OTA, except usually it will not open recovery only fastboot.
did you try "fastboot OEM unlock" like you put above or
"fastboot oem unlock" like it supposed to be?
Click to expand...
Click to collapse
Thanks for reply no I think it was not unlocked bootloader before OTA
I try factory reset from stock recovery but not fix bootloop
"Fastboot OEM unlock" not working when pres V up to confirm unlock on phone its say fail back to fastboot 3se
I think if I can get full OTA update zip file for R0030UU can I update with stock recovery
When use flash tool I get this error
S_BROM_DOWNLOAD_DA_FAIL (0x7D4)

KARIM9377 said:
Thanks for reply no I think it was not unlocked bootloader before OTA
I try factory reset from stock recovery but not fix bootloop
"Fastboot OEM unlock" not working when pres V up to confirm unlock on phone its say fail back to fastboot 3se
I think if I can get full OTA update zip file for R0030UU can I update with stock recovery
Click to expand...
Click to collapse
the updates are incremental, and it checks md5sum of every file on /system before doing the install, so if ota was stopped halfway you might be "borked"
also will need to know the version it was on , in order to get correct update.
here is link for the v17 to v21 update
http://hwfotadown.mayitek.com/ota/r...RIC_6.0_20170505-17451495815395129/update.zip

mrmazak said:
the updates are incremental, and it checks md5sum of every file on /system before doing the install, so if ota was stopped halfway you might be "borked"
also will need to know the version it was on , in order to get correct update.
Here is link for the v17 to v21 update
http://hwfotadown.mayitek.com/ota/r...ric_6.0_20170505-17451495815395129/update.zip
Click to expand...
Click to collapse
r0011uu is it working on r0030uu ?

KARIM9377 said:
r0011uu is it working on r0030uu ?
Click to expand...
Click to collapse
not sure. All my links are for either r0011uu or r0010uu.
r0011uu= non prime 16gb version
and
r0010uu= prime 16 gb version
Be AWRAE all the updates flash a new preloader that intentionaly blocks spft. and gives the error you have
so any update takes flash tool away

still no fix
mrmazak said:
not sure. All my links are for either r0011uu or r0010uu.
r0011uu= non prime 16gb version
and
r0010uu= prime 16 gb version
Be AWRAE all the updates flash a new preloader that intentionaly blocks spft. and gives the error you have
so any update takes flash tool away
Click to expand...
Click to collapse
still no fix try with all OTA file but not work and i cant find OTA or firmware for R0030UU 16GB 2G RAM I think i have v6.6 on it because not accept flash with SPFT
THIS is my getvar all
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x800000
(bootloader) partition-size:flashinfo: 1
(bootloader) partition-type:flashinfo: r
(bootloader) partition-size:userdata: 32
(bootloader) partition-type:userdata: ex
(bootloader) partition-size:cache: 19000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a700
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 25
(bootloader) partition-type:metadata: ra
(bootloader) partition-size:nvdata: 2000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw dat
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw da
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw da
(bootloader) partition-size:keystore: 80
(bootloader) partition-type:keystore: ra
(bootloader) partition-size:secro: 60000
(bootloader) partition-type:secro: raw d
(bootloader) partition-sizeemkeystore:
(bootloader) partition-typeemkeystore:
(bootloader) partition-size:seccfg: 8000
(bootloader) partition-type:seccfg: raw
(bootloader) partition-size:expdb: a0000
(bootloader) partition-type:expdb: raw d
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw da
(bootloader) partition-size:recovery: 10
(bootloader) partition-type:recovery: ra
(bootloader) partition-size:boot: 100000
(bootloader) partition-type:boot: raw da
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw da
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a0
(bootloader) partition-typerotect2: ex
(bootloader) partition-sizerotect1: a0
(bootloader) partition-typerotect1: ex
(bootloader) partition-size:nvram: 50000
(bootloader) partition-type:nvram: raw d
(bootloader) partition-sizeroinfo: 300
(bootloader) partition-typeroinfo: raw
(bootloader) partition-sizereloader: 4
(bootloader) partition-typereloader: r
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.078s

KARIM9377 said:
still no fix try with all OTA file but not work and i cant find OTA or firmware for R0030UU 16GB 2G RAM I think i have v6.6 on it because not accept flash with SPFT
THIS is my getvar all
C:\adb>fastboot getvar all
(bootloader) max-download-size: 0x800000
(bootloader) partition-size:flashinfo: 1
(bootloader) partition-type:flashinfo: r
(bootloader) partition-size:userdata: 32
(bootloader) partition-type:userdata: ex
(bootloader) partition-size:cache: 19000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a700
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 25
(bootloader) partition-type:metadata: ra
(bootloader) partition-size:nvdata: 2000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw dat
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw da
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw da
(bootloader) partition-size:keystore: 80
(bootloader) partition-type:keystore: ra
(bootloader) partition-size:secro: 60000
(bootloader) partition-type:secro: raw d
(bootloader) partition-sizeemkeystore:
(bootloader) partition-typeemkeystore:
(bootloader) partition-size:seccfg: 8000
(bootloader) partition-type:seccfg: raw
(bootloader) partition-size:expdb: a0000
(bootloader) partition-type:expdb: raw d
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw da
(bootloader) partition-size:recovery: 10
(bootloader) partition-type:recovery: ra
(bootloader) partition-size:boot: 100000
(bootloader) partition-type:boot: raw da
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw da
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a0
(bootloader) partition-typerotect2: ex
(bootloader) partition-sizerotect1: a0
(bootloader) partition-typerotect1: ex
(bootloader) partition-size:nvram: 50000
(bootloader) partition-type:nvram: raw d
(bootloader) partition-sizeroinfo: 300
(bootloader) partition-typeroinfo: raw
(bootloader) partition-sizereloader: 4
(bootloader) partition-typereloader: r
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
finished. total time: 0.078s
Click to expand...
Click to collapse
dont think there is anything you can do.
Contact "Blu" customer service, maybe they will send you a repair file or let you send it in for repair. The phones have 1 year warrenty

BLU R1 HD won't turn on
KARIM9377 said:
I have R1 HD R0030UU
its friends phone he get OTA when installed OTA the phone get bootloop and can get recovery and fastboot but I can't use SPFT to flash the phone its restart before when the red line finish on SPFT I tryed to unlock bootloader with fastboot OEM unlock but its failed is there any way to get back with the stock recovery or fastboot command
I have all drive NEEDS on my PC if there any way to use SDCARD to flash
Thanks all
Click to expand...
Click to collapse
Hey guys, my BLU HD has stopped working and it is just stuck whit white screen blu logo, I tried hard reset from recovery mode and unlock bootloader with fastboot but nothing has changed. Can somebody help me, please?

Recovering Bricked BLU R1 HD

Hi guys, my first androind in a few years
A cousing of mine just handed me his bricked R1 HD "as a gift". My goal is to unbrick it, if possible, and hand it to my little nice to replace her broken phone..
Cousing says, it got bricked while doing an OTA update, he tried reseting it and.. nothing..
Here is scoop, when i turn on the phone it boots, and i get the error message: "Unfortunately, GBA SErvices has stopped" over and over again.
Can i load a custom rom and even a stock rom to it and make it work again?
Thanks!

Found a stock backup rom with SP flash tool, cant seem to get it to load.
Let see if i can upload images..
Enviado desde mi iPhone utilizando Tapatalk

https://drive.google.com/file/d/1cj9A3y_BKtD0hQLtqtaOli6eNhT1IdCj/view?usp=sharing
{
"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"
}
I have access to the phone via windows explorer yet get a communication error..
Any ideas?
Enviado desde mi iPhone utilizando Tapatalk

luistf76 said:
I have access to the phone via windows explorer yet get a communication error..
Any ideas?
Enviado desde mi iPhone utilizando Tapatalk
Click to expand...
Click to collapse
Can it load I to recovery?
Did you try factory reset if it loads recovery?
That should fix it . If his story about it stopped working solely because if an OTA update.
Google search tells me that error is possibly related to messaging somehow.
https://www.google.com/amp/s/amp.re.../unfortunately_gba_services_has_stopped_help/

Recovery: power and volume up?
I tried that, (i think he did that too) it does the same.. boots up, to that welcome screen, as soon i scroll up to unlock i get that error msg “gba service has stopped”, i press on and the error msg re-appears... only way to get away from that loop is to reboot or turn off.
Enviado desde mi iPhone utilizando Tapatalk

Being reading some since last night,
Went to Recovery mode,
Did a wipe data/factory reset AND wipe cache partition
Still have same error pop-op once i scroll up to unlock it:
1. Unfortunatelly, GBA Services has stopped. (OK)
-- once i hit (OK) i get another error message that only last a fraction of a sec, had to use slow-motion video to eve see what it says.
2. Unfortunatelly, the process androind.process.acorenas stopped.
then back to error one, and the loop starts.
edit: just noticed, a "fota provider has stopped" message pop-up for a minute then went back to error #1.
this phone is wacked!
--------
Installed the fastboot and got phone info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
------------------------
The error message i keep getting with SP Flash: S_BROM_DOWNLOAD_DA_FAIL (0x7D4)
i have two set of bins, one stock amazon from rootJunky and an OEM from here. (I´ll use the OEM, but just had to try)
As for drivers, im using CDC MediaTek SP Drivers v2.0 signed.
i think i got the tools i need but the SP flash is not communicating with the phone.
what im i missing?

luistf76 said:
Being reading some since last night,
Went to Recovery mode,
Did a wipe data/factory reset AND wipe cache partition
Still have same error pop-op once i scroll up to unlock it:
1. Unfortunatelly, GBA Services has stopped. (OK)
-- once i hit (OK) i get another error message that only last a fraction of a sec, had to use slow-motion video to eve see what it says.
2. Unfortunatelly, the process androind.process.acorenas stopped.
then back to error one, and the loop starts.
edit: just noticed, a "fota provider has stopped" message pop-up for a minute then went back to error #1.
this phone is wacked!
--------
Installed the fastboot and got phone info:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) max-download-size: 0x8000000
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 19000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: a7000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:metadata: 2500000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:nvdata: 2000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:tee2: 500000
(bootloader) partition-type:tee2: raw data
(bootloader) partition-size:tee1: 500000
(bootloader) partition-type:tee1: raw data
(bootloader) partition-size:keystore: 800000
(bootloader) partition-type:keystore: raw data
(bootloader) partition-size:secro: 600000
(bootloader) partition-type:secro: raw data
(bootloader) partition-sizeemkeystore: 200000
(bootloader) partition-typeemkeystore: raw data
(bootloader) partition-size:seccfg: 80000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:logo: 800000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:lk: 80000
(bootloader) partition-type:lk: raw data
(bootloader) partition-sizerotect2: a00000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: a00000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-sizereloader: 40000
(bootloader) partition-typereloader: raw data
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) kernel: lk
(bootloader) product: P6601
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
all: Done!!
------------------------
The error message i keep getting with SP Flash: S_BROM_DOWNLOAD_DA_FAIL (0x7D4)
i have two set of bins, one stock amazon from rootJunky and an OEM from here. (I´ll use the OEM, but just had to try)
As for drivers, im using CDC MediaTek SP Drivers v2.0 signed.
i think i got the tools i need but the SP flash is not communicating with the phone.
what im i missing?
Click to expand...
Click to collapse
Ever since the second OTA update (6.6) . Spft has been blocked by the new preloader that the update installed.
And after the 8.x update to the kernel has been patched to block dirty-cow exploit, so those were the two methods we had to root. And unfortunately I think root is needed to fix your problem.
Sounds like you might be in a no win situation.
There is some talk in the general thread about a risky method to force phone to take an spft connection. Maybe you could be an exterminator and see if you get success.
A chance it will make things worse though.

Dirty-cow exploit?? Haven’t tried that.. will look into it
How do u force a phone to take spft connection? Water board it? ?
Enviado desde mi iPhone utilizando Tapatalk

luistf76 said:
Dirty-cow exploit?? Haven’t tried that.. will look into it
How do u force a phone to take spft connection? Water board it? ?
Enviado desde mi iPhone utilizando Tapatalk
Click to expand...
Click to collapse
lol
sort-of
it involves soldering jumper wire between test points on mother board.
Not done for every board, thats why it is experimental.

Yeah.. at this point it seems like a paperweight..
can u point me to that thread about soldering?
Enviado desde mi iPhone utilizando Tapatalk

luistf76 said:
Yeah.. at this point it seems like a paperweight..
can u point me to that thread about soldering?
Enviado desde mi iPhone utilizando Tapatalk
Click to expand...
Click to collapse
here is the thread here on R1HD thread where the method is mentioned. Method is on Hovatech.com
https://forum.xda-developers.com/showpost.php?p=74811964&postcount=1891

@luistf76
Have you removed the SIM card and tried factory reset.
A deeper search showed me the error message is more related to the the SIM card "pairing secret" with the service provider.

The phone haven’t had a sim in months.
When time allows, ill try the ‘harsh’ method. Its allready bricked so no biggie.
Enviado desde mi iPhone utilizando Tapatalk

Help please!!!
Hello!!! How could I find or make the "update.zip" file from the "bim blu r1 R0010UU.rar", "MTK6735_1902151154.bin" or "SP_Flash_Tool_BLU_R0010UU_V6.4_Firmware.zip" that I've already downloaded for my BLU R1 HD??? I've tried with SP Flash Tool and Miracle Thunder, but there's something missing with the USB Port, cable or PC, so I would like to do it trough Recovery Mode with "apply update from sd card"... Thanks a lot for your help!!!

Question Please help recover photos from boot looping Xiaomi Redmi Note 10S

Hi
I have a Xiaomi Redmi Note 10S that randomly rebooted during normal use and then got stuck in a boot loop, it loads the 'powered by android' screen then reboots on a loop to this screen. There was no notification of update or suchlike, however I am aware there has been a recent update sent out, however I don't know if it had been sent to this phone and automatically rebooted itself.
I would be eternally grateful for any advice or guidance in trying to recover photos and data, or at least being able to boot the phone to enable this in the usual manner. I have very limited knowledge of this and have read several posts here and elsewhere over last 24hrs, but would appreciate some clarification of some points below in 'questions'. Phone is 3 months old, Xiaomi can't help. they wipe it on receipt, can't find local phone shop to help.
The phone is stock as new from the factory.
Situation:
-Boot loops as above
-Can access MIUI recovery 5.0 by pressing volume and power buttons, only options are 'reboot' (just loops again), 'wipe' (not an option as need to retrieve photos) and 'connect mi assistant' (can connect by ADB sideloader in this mode)
- Can access fastboot by pressing volume and power button and fastboot devices sees it connected
Main objective:
Retrieve photos and whatsapp messages
Attempted solutions:
-reboot through recovery menu on MIUI recovery 5.0, loops still
- tried to connect to Xiaomi PC suite, phone not seen as connected (is seen through command line ADB/fastboot devices, i think perhaps the phone isn't supported by PC suite)
- I tried a suggested solution of fastboot continue when in fast boot mode, but i get the error FAILED (remote: not support on security), what does this mean?
Questions:
- As I understand it as the bootloader is locked and it is a stock ROM I cannot retrieve the data through ADB/fastboot, is this correct?
- I considered wiping the cache partition in the hope this may fix the bootloop (there is no option to do this in MIUI recovery just a full wipe) so was going to do it through fastboot but I read it deletes the hole partition I.E. not just the data within, is this the case?
Open to suggestions but from what I gather from limited research is my only options would be appear to be :
A: flash a system.img (I do not know how I obtain this or how to load it, nor do I know what version of MIUI / Android the phone was on before this fault)
B: sideload a .zip file having edited the .bat file to remove the overwrite of the user data and remove the wipe command. Will this leave the photos/app data intact? (again i do not know how i identify the right official ROM to download and whether it is recovery or fastboot)
C: load a boot.img, again same challenges as above
Thank you for any advice or help you can offer

shw2021 said:
Hi
I have a Xiaomi Redmi Note 10S that randomly rebooted during normal use and then got stuck in a boot loop, it loads the 'powered by android' screen then reboots on a loop to this screen. There was no notification of update or suchlike, however I am aware there has been a recent update sent out, however I don't know if it had been sent to this phone and automatically rebooted itself.
I would be eternally grateful for any advice or guidance in trying to recover photos and data, or at least being able to boot the phone to enable this in the usual manner. I have very limited knowledge of this and have read several posts here and elsewhere over last 24hrs, but would appreciate some clarification of some points below in 'questions'. Phone is 3 months old, Xiaomi can't help. they wipe it on receipt, can't find local phone shop to help.
The phone is stock as new from the factory.
Situation:
-Boot loops as above
-Can access MIUI recovery 5.0 by pressing volume and power buttons, only options are 'reboot' (just loops again), 'wipe' (not an option as need to retrieve photos) and 'connect mi assistant' (can connect by ADB sideloader in this mode)
- Can access fastboot by pressing volume and power button and fastboot devices sees it connected
Main objective:
Retrieve photos and whatsapp messages
Attempted solutions:
-reboot through recovery menu on MIUI recovery 5.0, loops still
- tried to connect to Xiaomi PC suite, phone not seen as connected (is seen through command line ADB/fastboot devices, i think perhaps the phone isn't supported by PC suite)
- I tried a suggested solution of fastboot continue when in fast boot mode, but i get the error FAILED (remote: not support on security), what does this mean?
Questions:
- As I understand it as the bootloader is locked and it is a stock ROM I cannot retrieve the data through ADB/fastboot, is this correct?
- I considered wiping the cache partition in the hope this may fix the bootloop (there is no option to do this in MIUI recovery just a full wipe) so was going to do it through fastboot but I read it deletes the hole partition I.E. not just the data within, is this the case?
Open to suggestions but from what I gather from limited research is my only options would be appear to be :
A: flash a system.img (I do not know how I obtain this or how to load it, nor do I know what version of MIUI / Android the phone was on before this fault)
B: sideload a .zip file having edited the .bat file to remove the overwrite of the user data and remove the wipe command. Will this leave the photos/app data intact? (again i do not know how i identify the right official ROM to download and whether it is recovery or fastboot)
Thank you for any advice or help you can offer
Click to expand...
Click to collapse
If you have Whatsapp backup stored on google account that can be used it to restore again. Regarding your photos, were they stored on Google account?

mvikrant97 said:
If you have Whatsapp backup stored on google account that can be used it to restore again. Regarding your photos, were they stored on Google account?
Click to expand...
Click to collapse
Thank you, no remote backups unfortunately

mvikrant97 said:
If you have Whatsapp backup stored on google account that can be used it to restore again. Regarding your photos, were they stored on Google account?
Click to expand...
Click to collapse
Flashing phone without user data data partition may also help.

Below added in case anyone can interpret this to ID correct files to download, thank you
(bootloader) max-download-size: 0x8000000
(bootloader) fuse: yes
(bootloader) cpuid: fb3095cc17db56aed6aa8522f88647336c21ce04fddab3339f15
(bootloader) variant:
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x0
(bootloader) hw-revision: ca00
(bootloader) battery-soc-ok: yes
(bootloader) battery-voltage: 4244mV
(bootloader) partition-size:sgpt: 8000
(bootloader) partition-type:sgpt: raw data
(bootloader) partition-size:flashinfo: 1000000
(bootloader) partition-type:flashinfo: raw data
(bootloader) partition-size:userdata: 1b13bf8000
(bootloader) partition-type:userdata: f2fs
(bootloader) partition-size:super: 220000000
(bootloader) partition-type:super: raw data
(bootloader) partition-size:tee_b: 500000
(bootloader) partition-type:tee_b: raw data
(bootloader) partition-size:dtbo_b: 800000
(bootloader) partition-type:dtbo_b: raw data
(bootloader) partition-size:vendor_boot_b: 4000000
(bootloader) partition-type:vendor_boot_b: raw data
(bootloader) partition-size:boot_b: 4000000
(bootloader) partition-type:boot_b: raw data
(bootloader) partition-size:lk_b: 400000
(bootloader) partition-type:lk_b: raw data
(bootloader) partition-size:gz_b: 2000000
(bootloader) partition-type:gz_b: raw data
(bootloader) partition-size:cam_vpu3_b: f00000
(bootloader) partition-type:cam_vpu3_b: raw data
(bootloader) partition-size:cam_vpu2_b: f00000
(bootloader) partition-type:cam_vpu2_b: raw data
(bootloader) partition-size:cam_vpu1_b: f00000
(bootloader) partition-type:cam_vpu1_b: raw data
(bootloader) partition-size:sspm_b: 100000
(bootloader) partition-type:sspm_b: raw data
(bootloader) partition-size:scp_b: 600000
(bootloader) partition-type:scp_b: raw data
(bootloader) partition-size:audio_dsp_b: 400000
(bootloader) partition-type:audio_dsp_b: raw data
(bootloader) partition-size:spmfw_b: 100000
(bootloader) partition-type:spmfw_b: raw data
(bootloader) partition-size:md1img_b: 9600000
(bootloader) partition-type:md1img_b: raw data
(bootloader) partition-size:logo: 880000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:boot_para: 1a00000
(bootloader) partition-type:boot_para: raw data
(bootloader) partition-size:nvram: 4000000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-size:efuse: 80000
(bootloader) partition-type:efuse: raw data
(bootloader) partition-sizeroinfo: 300000
(bootloader) partition-typeroinfo: raw data
(bootloader) partition-size:sec1: 200000
(bootloader) partition-type:sec1: raw data
(bootloader) partition-size:tee_a: 500000
(bootloader) partition-type:tee_a: raw data
(bootloader) partition-size:dtbo_a: 800000
(bootloader) partition-type:dtbo_a: raw data
(bootloader) partition-size:vendor_boot_a: 4000000
(bootloader) partition-type:vendor_boot_a: raw data
(bootloader) partition-size:boot_a: 4000000
(bootloader) partition-type:boot_a: raw data
(bootloader) partition-size:lk_a: 400000
(bootloader) partition-type:lk_a: raw data
(bootloader) partition-size:gz_a: 2000000
(bootloader) partition-type:gz_a: raw data
(bootloader) partition-size:cam_vpu3_a: f00000
(bootloader) partition-type:cam_vpu3_a: raw data
(bootloader) partition-size:cam_vpu2_a: f00000
(bootloader) partition-type:cam_vpu2_a: raw data
(bootloader) partition-size:cam_vpu1_a: f00000
(bootloader) partition-type:cam_vpu1_a: raw data
(bootloader) partition-size:sspm_a: 100000
(bootloader) partition-type:sspm_a: raw data
(bootloader) partition-size:scp_a: 600000
(bootloader) partition-type:scp_a: raw data
(bootloader) partition-size:audio_dsp_a: 400000
(bootloader) partition-type:audio_dsp_a: raw data
(bootloader) partition-size:spmfw_a: 100000
(bootloader) partition-type:spmfw_a: raw data
(bootloader) partition-size:md1img_a: 9600000
(bootloader) partition-type:md1img_a: raw data
(bootloader) partition-sizetp: 3000000
(bootloader) partition-typetp: raw data
(bootloader) partition-size:seccfg: 800000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect2: 800000
(bootloader) partition-typerotect2: ext4
(bootloader) partition-sizerotect1: 800000
(bootloader) partition-typerotect1: ext4
(bootloader) partition-sizeersist: 315e000
(bootloader) partition-typeersist: ext4
(bootloader) partition-size:metadata: 2000000
(bootloader) partition-type:metadata: raw data
(bootloader) partition-size:md_udc: 169a000
(bootloader) partition-type:md_udc: raw data
(bootloader) partition-size:vbmeta_vendor_b: 800000
(bootloader) partition-type:vbmeta_vendor_b: raw data
(bootloader) partition-size:vbmeta_system_b: 800000
(bootloader) partition-type:vbmeta_system_b: raw data
(bootloader) partition-size:vbmeta_b: 800000
(bootloader) partition-type:vbmeta_b: raw data
(bootloader) partition-size:vbmeta_vendor_a: 800000
(bootloader) partition-type:vbmeta_vendor_a: raw data
(bootloader) partition-size:vbmeta_system_a: 800000
(bootloader) partition-type:vbmeta_system_a: raw data
(bootloader) partition-size:vbmeta_a: 800000
(bootloader) partition-type:vbmeta_a: raw data
(bootloader) partition-size:nvdata: 4000000
(bootloader) partition-type:nvdata: ext4
(bootloader) partition-size:nvcfg: 2000000
(bootloader) partition-type:nvcfg: ext4
(bootloader) partition-size:frp: 100000
(bootloader) partition-type:frp: raw data
(bootloader) partition-size:rescue: 8000000
(bootloader) partition-type:rescue: raw data
(bootloader) partition-size:blk1: 800000
(bootloader) partition-type:blk1: raw data
(bootloader) partition-size:cust: 40000000
(bootloader) partition-type:cust: raw data
(bootloader) partition-size:ffu: 800000
(bootloader) partition-type:ffu: raw data
(bootloader) partition-size:gsort: 1000000
(bootloader) partition-type:gsort: raw data
(bootloader) partition-size:expdb: 1400000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-sizeara: 80000
(bootloader) partition-typeara: raw data
(bootloader) partition-size:countrycode: 200000
(bootloader) partition-type:countrycode: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-sizegpt: 8000
(bootloader) partition-typegpt: raw data
(bootloader) partition-sizereloader_b: 400000
(bootloader) partition-typereloader_b: raw data
(bootloader) partition-sizereloader_a: 400000
(bootloader) partition-typereloader_a: raw data
(bootloader) partition-sizereloader: 400000
(bootloader) partition-typereloader: raw data
(bootloader) serialno: [redacted by OP if required please advise]
(bootloader) off-mode-charge: 1
(bootloader) warranty: yes
(bootloader) unlocked: no
(bootloader) secure: yes
(bootloader) tokenversion: 2
(bootloader) crc: 1
(bootloader) kernel: lk
(bootloader) product: rosemary
(bootloader) is-userspace: no
(bootloader) slot-retry-count:b: 1
(bootloader) slot-retry-count:a: 1
(bootloader) slot-unbootable:b: no
(bootloader) slot-unbootable:a: no
(bootloader) slot-successful:b: yes
(bootloader) slot-successful:a: yes
(bootloader) slot-count: 2
(bootloader) current-slot: a
(bootloader) has-slot:sgpt: no
(bootloader) has-slot:flashinfo: no
(bootloader) has-slot:userdata: no
(bootloader) has-slot:super: no
(bootloader) has-slot:logo: no
(bootloader) has-slot:boot_para: no
(bootloader) has-slot:nvram: no
(bootloader) has-slot:efuse: no
(bootloader) has-slotroinfo: no
(bootloader) has-slot:sec1: no
(bootloader) has-slot:tee: yes
(bootloader) has-slot:dtbo: yes
(bootloader) has-slot:vendor_boot: yes
(bootloader) has-slot:boot: yes
(bootloader) has-slot:lk: yes
(bootloader) has-slot:gz: yes
(bootloader) has-slot:cam_vpu3: yes
(bootloader) has-slot:cam_vpu2: yes
(bootloader) has-slot:cam_vpu1: yes
(bootloader) has-slot:sspm: yes
(bootloader) has-slot:scp: yes
(bootloader) has-slot:audio_dsp: yes
(bootloader) has-slot:spmfw: yes
(bootloader) has-slot:md1img: yes
(bootloader) has-slottp: no
(bootloader) has-slot:seccfg: no
(bootloader) has-slotrotect2: no
(bootloader) has-slotrotect1: no
(bootloader) has-slotersist: no
(bootloader) has-slot:metadata: no
(bootloader) has-slot:md_udc: no
(bootloader) has-slot:vbmeta_vendor: yes
(bootloader) has-slot:vbmeta_system: yes
(bootloader) has-slot:vbmeta: yes
(bootloader) has-slot:nvdata: no
(bootloader) has-slot:nvcfg: no
(bootloader) has-slot:frp: no
(bootloader) has-slot:rescue: no
(bootloader) has-slot:blk1: no
(bootloader) has-slot:cust: no
(bootloader) has-slot:ffu: no
(bootloader) has-slot:gsort: no
(bootloader) has-slot:expdb: no
(bootloader) has-slotara: no
(bootloader) has-slot:countrycode: no
(bootloader) has-slot:misc: no
(bootloader) has-slotgpt: no
(bootloader) has-slotreloader: yes
(bootloader) version-baseband: MOLY.LR13.R1.MP.V89.5.P47
(bootloader) version-bootloader: k85v1_64-879e20af-20210531104000-202108
(bootloader) version-preloader:
(bootloader) anti: 1
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.814s

@shw2021
Take note that in the moment you unlock phone's bootloader - what is required to sucessfully run most of the FASTBOOT commands and/or flash a Custom ROM - all user-data automatically get wiped.
Take note that ADB won't work on a bootlooping device because a stable USB-connection isn't given.

Try to get it to boot in safe mode.
Sometimes when boot looping they will go into safe mode automatically after a few cycles... depending on the degree of damage.
If you get into safe mode, don't reboot, grab the data then.
Try clearing system cache.
If you reflash all bets are off... in the future always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Edit, OP got me with the quickness...

blackhawk said:
Try to get it to boot in safe mode.
Sometimes when boot looping they will go into safe mode automatically after a few cycles... depending on the degree of damage.
If you get into safe mode, don't reboot, grab the data then.
Try clearing system cache.
If you reflash all bets are off... in the future always redundantly backup critical data to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Edit, OP got me with the quickness...
Click to expand...
Click to collapse
Thank you for quick reply, I don't know how i get it to boot in safe mode, it has been left overnight and continues looping until it beeps and turns off, I can get it to the 'fastboot' screen or the MIUI recovery screen. How can i grab the data? From what I read, as it is locked pulling data from sdcard won't work? Grateful for pointers though. How do I clear system cache please, there is no option for this in MIUI recovery menu? Indeed I am kicking myself, never had a phone do this before, I will definitely take on board the double back up point you made.
jwoegerbauer said:
@shw2021
Take note that in the moment you unlock phone's bootloader - what is required to sucessfully run most of the FASTBOOT commands and/or flash a Custom ROM - all user-data automatically get wiped.
Take note that ADB won't work on a bootlooping device because a stable USB-connection isn't given.
Click to expand...
Click to collapse
Thank you for quick reply, I wasn't intending to unlock the bootloader, again this is only what I have read, that if loading a stock ROM or .img then the bootloader does not need to be unlocked. Is it the case that I cannot boot a boot.img or flash a system.img?
I seem to get a stable ADB connection by booting phone into MIUI recovery menu and selecting 'connect miassistant', i then get ADB sideloader and phone shows on devices

This tutorial covers how to flash the Redmi notes 10S and here are the flash file links.
I would recommend you not to flash the userdata and cache partition to prevent data loss.

shw2021 said:
I seem to get a stable ADB connection by booting phone into MIUI recovery menu and selecting 'connect miassistant', i then get ADB sideloader and phone shows on devices
Click to expand...
Click to collapse
Then try to sideload phone's Stock ROM via ADB Sideload method as offered in recovery menu - but this may overwrite already existing user-data, because the /data partition, where user-data are stored, is part of Stock ROM.

.

Keep trying to boot it up, it may take. Try at at dozen times... play with it.

You can recover data from formated or lost partition via data recovery software .

HeiloWorid said:
You can recover data from formated or lost partition via data recovery software .
Click to expand...
Click to collapse
Without rooting the device it is not possible to recover that data and the partition once overwritten while flashing will wipe all data.

I recovered data successful (pictures) on my friend's phone who was with wipe data and factory reset.

HeiloWorid said:
I recovered data successful (pictures) on my friend's phone who was with wipe data and factory reset.
Click to expand...
Click to collapse
Do you have specifics please? Program used, method employed? thank you

jwoegerbauer said:
Then try to sideload phone's Stock ROM via ADB Sideload method as offered in recovery menu - but this may overwrite already existing user-data, because the /data partition, where user-data are stored, is part of Stock ROM.
Click to expand...
Click to collapse
From what I gather from @mvikrant97 and elsewhere, editing the flashall.bat file possibly offers the opportunity to not overwrite the user data.
However MIUI recovery menu doesn't have the option to initiate the load of an ADB sideloaded file, if i sideload the stock ROM will the phone load it upon reboot, or do you need to have an option within the recovery menu on the phone to make it load it? thank you

blackhawk said:
Keep trying to boot it up, it may take. Try at at dozen times... play with it.
Click to expand...
Click to collapse
No luck with this unfortunately, thank you for the suggestion though was definitely worth a shot

HeiloWorid said:
I recovered data successful (pictures) on my friend's phone who was with wipe data and factory reset.
Click to expand...
Click to collapse
Which software did you used?

I use software from Hiren’s BootCD PE
Hard Disk Tools/Data Recovery:Lazesoft Data Recovery ,Puran Data Recovery ,Puran File Recovery ,Recuva .I've tryed with all of them and they have different percent success more than 90% recovered of all pictures.

[Solved] A7600-F: How to flash TWRP when recovery partition doesn't support flashing

Hey there,
Spoiler: Edits
- I just hit in "fastboot reboot" and the device rebootet. So the fastboot might not be broken.
- used "fastboot flash recovery twrp.img", it returns me "Partition "recovery" not support flash"
- Added a Spoiler with returns of fastboot
- Added the try "fastboot boot twrp.img"
- added the solution
Spoiler: erased because of edits
if I turn my device into the fastboot mode, it seems to stuck while loading. First my steps and the Interface that I can see.
1. Starting the device while holding Vol+ and Power
2. Selecting fastboot
3. See "FASTBOOT mode..."
First Question: Do I get any other interface, when fastboot mode is started? In general there is a different image shown.
My overall aim is to intall twrp (and lineage os). So I installed a driver set for this device and the latest adb-toolset. Starting the fastboot mode, I'll try to turn over some fastboot commands, like "fastboot oem device-status", but there is no response.
If I use "fastboot devices" my device is shown in the list. My (windows 10-)hardware manager doesnt return any devices with driver errors. But, the tab is shown as a device by tp-link.
Could someone help me to get twrp installed?
I've rooted the tablet by kingoroot. (I know about) There are no sensible dates on and I'm ok with unrooting as well as reinstalling all stock-roms before installing lineage. Just wanted to be sure, that the environment is open for all activities to get twrp running.
My question turns into "how to flash twrp, when the recovery doesn't support flashing"?
When I use "fastboot flash recovery twrp.img", it returns me "Partition 'recovery' not support flash"
Thank you for your time and help
Edit:
Spoiler: return of fastboot getvar all
(bootloader) partition-size:userdata: 32000000
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 10000000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:system: 4c800000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:expdb: a00000
(bootloader) partition-type:expdb: raw data
(bootloader) partition-size:flex: 2800000
(bootloader) partition-type:flex: ext4
(bootloader) partition-size:resv: 80000
(bootloader) partition-type:resv: raw data
(bootloader) partition-size:ebr2: 80000
(bootloader) partition-type:ebr2: raw data
(bootloader) partition-size:logo: 300000
(bootloader) partition-type:logo: raw data
(bootloader) partition-size:misc: 80000
(bootloader) partition-type:misc: raw data
(bootloader) partition-size:sec_ro: 600000
(bootloader) partition-type:sec_ro: ext4
(bootloader) partition-size:recovery: 1000000
(bootloader) partition-type:recovery: raw data
(bootloader) partition-size:boot: 1000000
(bootloader) partition-type:boot: raw data
(bootloader) partition-size:uboot: 60000
(bootloader) partition-type:uboot: raw data
(bootloader) partition-size:seccfg: 20000
(bootloader) partition-type:seccfg: raw data
(bootloader) partition-sizerotect_s: a00000
(bootloader) partition-typerotect_s: ext4
(bootloader) partition-sizerotect_f: a00000
(bootloader) partition-typerotect_f: ext4
(bootloader) partition-size:nvram: 500000
(bootloader) partition-type:nvram: raw data
(bootloader) partition-sizero_info: 300000
(bootloader) partition-typero_info: raw data
(bootloader) partition-size:ebr1: 80000
(bootloader) partition-type:ebr1: raw data
(bootloader) partition-size:mbr: 80000
(bootloader) partition-type:mbr: raw data
(bootloader) partition-sizereloader: 1400000
(bootloader) partition-typereloader: raw data
(bootloader) kernel: lk
(bootloader) product: LVP9_ROW_WIFIONLY
(bootloader) version: 0.5
all: Done!!
Finished. Total time: 0.109s
If I try to temporarly boot from the twrp-image, this is happening:
"fastboot boot twrp.img" (imagine the image is called twrp)
Sending ... ok:
Booting ........ (nothing happens, neither on the tablet, nor the command line)
Edit:
Found a solution. Following this steps will help: https://forum.xda-developers.com/t/...-lenovo-a7600-f-mt6582.3895322/#post-78799763