Database Info

[Tutorial] FNF Ifive Mini 4s bootloop fix

So you probably did something wrong trying to get a custom recovery or root on your FNF Ifive Mini 4s. Well I did too, that's why I'm writing this
WARNING: This will remove ALL files from your tablet.
Just follow these steps and your tablet should be back on track soon!
So first you have to download FNF Ifive's official upgrade tool which can be found here
Press on the latest one, which as of April 2 is called ifive_mini_4S_US_1.0.6_20170330 Upgrade Tool&Firmware.
Now download both files in the onedrive folder. One is the recovery tool and the other is the latest firmware.
Extract both to a folder of your choosing.
Enter the folder called Driver and run Driverinstall.exe as admin.
Press uninstall driver, press ok and press install driver.
Go back to the main folder and run FactoryTool.exe as admin.
Turn off your tablet.
Enter loadermode on your tablet by connecting it to your computer with the included cable and pressing the powerbutton and Vol-.
Click on "Firmware" in the FactoryTool.
Locate the .img file you downloaded and extracted.
Check the box called "Restore".
Click on "Run" and wait for it to say success.
After it says success you should disconnect the tablet from your computer and just wait for it to boot. This will take a few minutes.
Success! You have now fixed your bootloop and updated to the latest firmware if you did not have it already!
If you had any problems I will be happy to help you

Error
Thanks for your help.
I tried it but it never end with "success". It says: "Wait for loader fail".
I don't know what I don't have to do.

TkMelter said:
Thanks for your help.
I tried it but it never end with "success". It says: "Wait for loader fail".
I don't know what I don't have to do.
Click to expand...
Click to collapse
That is probably because you are doing something wrong when entering loadermode or because you forgot to first uninstall the driver and then install it. When entering loadermode you must make sure the tablet is connected to the pc with the application open and running. Then you turn it off, and enter loadermode by pressing the power button and volume down simultaneously.
Hope this helps

Worked!!
Many thanks.
I manage to get the tablet working. I tried many times and I finally get it to work.
Sry for my bad English.

TkMelter said:
Many thanks.
I manage to get the tablet working. I tried many times and I finally get it to work.
Sry for my bad English.
Click to expand...
Click to collapse
I'm happy it worked

Hello.
And for mac users? How can we do it?

version 1.06, when I update play serviices and reboot, boot loop begins. how can i fix?

gabrielpardal said:
Hello.
And for mac users? How can we do it?
Click to expand...
Click to collapse
The tool only works for windows.

JOAOFRS said:
version 1.06, when I update play serviices and reboot, boot loop begins. how can i fix?
Click to expand...
Click to collapse
By using this tutorial.

Hi,
I successfully upgraded the firmware, it says Build Number ifive_mini_4S_1.0.8-W in my settings but my device still doesn't work properly. The message "Unfortunately Google Play Store/services has stopped" pops up frequently and the boot screen sometimes shows up out off nowhere closing all my apps and locking the device. I also can't open the Play Store at all. I always get the "Unfortunately Google Play Store has stopped" message.
Once I rebooted the device I got a bootloop but it stopped after a while and now my Wi-Fi does not work anymore. I can turn it on but it doesn't find any networks and turns itself off after a few seconds.
I read that some models are just straight up broken. The serial number of my device is P1QRMW1HAR. I bought it a year ago or so and I had problems with bootloops all the time so I barely used the device and hoped for a firmware upgrade that would fix everything. Now my patience is about to run out and I really hope that someone knows how to fix this stupid China device...

ifve mini 4s not loading , FVF logo not booting
hii...i did the upgrade from 1.1.6c to 1.1.7c but is still have same problem ,the upgrade tool showed the upgrade is success my tablet restart three times but was unable to boot and getting the logo FNF,and when i turn off for many houres and turn it on iam getting this message.
E:failed yo mount. /mnt/external_sd (no such device )
E:failed yo mount. /mnt/external_sd (no such device )
Supported API : 3
--wiping data...
Formatting /data...
:silly: it was more text but it disappeared quickly.
pls some help

UnknownDK said:
ifive_mini_4S_US_1.0.6_20170330
Click to expand...
Click to collapse
Hello,I find "ifive_mini_4S_US_1.0.6_20170330" for a long time,can you share it with me？my email:[email protected],THANKS!

[HELP] Bricked Oneplus 6 - Qualcomm CrashDump - already tried everything

Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.

Did you try msm download tool? If not, nead that thread and good luck

whizeguy said:
Did you try msm download tool? If not, nead that thread and good luck
Click to expand...
Click to collapse
Hi!
Thanks for your reply, but I think you do not read my entire post
As I said, i've already tried at least 8 different versions of msmDownloadTool.
If you have any other suggestion, I'll appreciate.

so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot

EarthquakeXS said:
so you can't boot into fastbootmode anymore?
Had the same problem once before and solved it by flashing the correct twrp by fastboot
Click to expand...
Click to collapse
Yes, I am unable to enter into Fastboot Mode.
When I try, the logo saying "fastboot" appears, but after 4 seconds, the systems stucks on CrashDump error screen again.
That way my PC cannot find my phone with ADB or FASTBOOT commands.
The only tool that works is msmDownloadTool, but even with a success run with that tool, my system does not start and stills under CrashDump error.
I was thinking if exists some version of msmDownloadTool that justs restore the fastboot and unlock bootloader with brute force.
Thats my last hope

hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!

sanaulla jauhar said:
hello. heres what u need to do. download miracle kraked version. hold volume+ and - key simultaneously.
go to device manager in pc. look for port expand it and u should see qualcomm Qloader.
now use miracle under qualcomm tab select patch and flash!!
Click to expand...
Click to collapse
Hi!
Can you please provide some link to this tool?
Thanks for your help!

mikesmarcos said:
Hi everyone!
Well guys, sorry to bring this subject on thread again (because this forum has a lot of guides to solve this problem).
But I'm without hope with my phone at this moment.
Let me tell you guys my sad story...
I have an Oneplus 6 since december 2018, and never, NEVER, tried to use any modification on my phone.
I am from Brazil (so sorry for my bad english =] ), and here we CANNOT use Oneplus Support services (I've tried but only received the response "sorry I cannot help you on your country"), so because of this, I've decided to never apply any modification to avoid problems.
This week after a simple reboot my OP6 started with "Qualcomm CrashDump" error and my despair begins.
I'm not able to enter on Fastboot Mode. When I try, the systems attempt to boot (the fastboot mode logo appears) and fall down into crash again.
I'm not able to enter on Recovery Mode either. This method shows nothing, only black screen and after some time the crash screen comes again.
I do not have Bootloader unlocked too.
Any suggestion to use TWRP via fastboot.exe or ADB are useless, because I cant make the connection. At least I think that is impossible because the 'adb devices' command does not find the device.
I followed a lot of guides from XDA to solve my problem, including the Mega Unbrick Thread.
I already downloaded at least 8 different versions of msmdownloadtool in consecutive attempts of unbrick my phone. Nothing really helps.
The most weird situation is that msmDownlodTool can finish the proccess with success. The driver installation is working... everything seens OK using the tool but my phone does not revive
Someone have a suggestion for me?
Any suggestion, tool or alternative method is welcome in my actual situation.
Sorry if I posted at wrong local, just tell me and I can fix if necessary.
Thanks in advance to all of you guys.
Click to expand...
Click to collapse
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?

Hi dude are u here ? i will help u

Try this
Rhach1d237 said:
Hi there ! I am experiencing a similar issue on the same device. Did you manage to fix it ?
Click to expand...
Click to collapse
Source is a videotutorial. google oneplus 6 hardbrick and click the video of Max Lee
(it worked for me)
the download takes an awful lot of time
first get your phone into qualcomm download mode by holding down volume up + power button and plug your device in your PC.
(first unzip the hardbrick zip folder) then the oneplus 6 folder and than the .exe file and click 'start' if it detects your phone.
That is flashing every chip and Hydrogen OS 5.whatever.3 but that is not important. Your phone should boot and than you can install Oxygen OS with android 10(thats the other zip folder) using the local upgrade feature.
(make sure to enable google play services after upgrade from hydrogen OS)
Hope it will work for you too if you haven't tried it already.

failed root fastboot only help please

I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you

marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659

blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?

These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view

not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.

Blackview Tab 8 unlocked Bootloader, but how to magisk?

Hi,
so with this Tutorial i was able to unlock the bootloader of the Blackview tab 8.
but i just could not find any way to flash magisk.
- "fastboot boot patched_img.img" and "fastboot flash boot patched_img.img" gave me "fastboot: error: Couldn't parse partition size '0x'"
- "fastboot flash:raw boot boot.img" was able to flash the patched_boot.img (a twrp i tried to port as well), but then i was stuck at blackview logo (SOFTBRICK)
- SPD Research Tool R24.0.0003 was able to flash patched_boot.img, but same stuck at logo (SOFTBRICK)
The only way i was able to unbrick it, involved opening back cover and disconnecting the battery and reconnecting it again.
then put research tool to download mode and flash stock img
I'm hoping for some advices, what i could try to get magisk flashed
- Tab8 Firmware (DK_SC9863A_P30_5G_10.0_Tab8_EEA_20201022_V1.0)
- SPD Research Tool R24 (there are 2 other tools but afaik research tool is the only one, where i can choose which partitions to flash)
best regards
Oxo

Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards

I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?

nr0000000 said:
Hi,
I've got a tab8 too (eu) and I have the boot_patched.img generated by magisk manager but I can't unlock the bootloader. I used the tuto you gave (your first link) too.
Could you explain what you did to successfully unlock your bootloader please?
Thanx
Bests regards
Click to expand...
Click to collapse
I did it like described in the tutorial i linked. did you use linux? maybe in a VM or so, to use the .sh script. AFAIK it doesnt work with windows
also dont forget to activate "OEM unlocking" in dev options
StormChaser1337 said:
I was trying to backup the stock ROM of this same tablet, however i must have incorrectly installed SPD drivers or somehow had uninstalled them, Research Download said "failed user cancel", then boom when i tried to switch it on it was not turning on nor charging. I have been trying to charge it for about 4 days, no dice, it does not charge still, nor turning on.
I must have soft bricked it, because it gets detected by the PC as "SPRD U2S Diag (COM5)", but when i try to flash Stock ROM i downloaded it either says " failed user cancel" or gets stuck at "checking baudrate".
I don't know what to do, would opening it and test point it make a difference? Because some guy on Youtube was able to flash his SPD phone after test pointing it, as it was facing "failed user cancel"
Another question, which key combinations did you use when flashing your Tab 8? Vol - and Power or?
Click to expand...
Click to collapse
i dont know about test point actually. you can open it pretty easily and just disconnect battery. then connect again, use sdp tool and start the flash process, then press vol- and hold it while pluging in usb cable. thats what i do, if im stuck and cant do anything else.
regarding button combination, i'm not sure. usually i use adb reboot bootloader.
Also for the Blackview Tab 8 you need to extract keys from your vbmeta.img and sign it differently, also every other .img you wanna flash, like patched magisk boot.img. i successfully rooted mine some time ago, but i flashed some magisk modules and something went wrong and i ended up bootlooping. now im trying to root again.
somehow i cant flash the vbmeta.img. i dont remember if i did anything different last time.
all the stuff i did to get it rooted, i have taken from that hovatek forum.
edit: uploaded Stock Rom Images and stuff like for example a magsik patched boot image, which got repacked with android image kitchen then signed and repacked again with avbtool here
PS: dont have time to invest to this atm, also i just read that there was a update sometime this year which i didnt get, so maybe that changed some stuff.

I was considering buying this Blackview tablet and before I ordered it I got in touch with the Blackview home people in Hong Kong. They were extremely UNHELPFUL AND EVEN RUDE (not unusual for the chinese). As far as I am concerned this mob does not deserve to be supported and having a product that is so difficult to do any tinkering with precludes it from my list for sure. It is so time for consumers to DEMAND that any product that does not give explicit instructions as to unlocking and flashing is not supported. Why is it not possible in this day and age for this to happen. OK I know why but you get my meaning.

Oneplus 8T stuck in Qualcomm CrashDump mode

After trying to restore stock OOS and rebooting fastboot my phone is now stuck in Qualcomm Crashdump mode. I have MSMDownloadTool installed but it won't open, it just opens a windows saying "Program has been started" after executing it.
I also can't reboot to the bootloader, the phone just turns on or off.
What to do?

From my rather long post in https://forum.xda-developers.com/t/...your-device-to-oxygenos.4180837/post-86563159 :
"connect the phone to the PC whilst it's still in CrashDump mode and then press Pwr + Vol Up until the phone buzzes and then hold Vol Up + Vol Dn and MSM will then connect."

Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.

petrolblue said:
Thank you, that worked. I have another question if you don't mind:
I tried to restore OxygenOS with https://forum.xda-developers.com/t/...xygenos-fastboot-roms-for-oneplus-8t.4348023/ but it cant find the create-logical device and delete-logical-device commands, also when I try to flash some of the image files fastboot complains about not being able to flash system critical files. I tried running fastboot flashing unlock_critical but that didn't change anything. Is there any other way to restore Oxygen OS with fastboot or is there any fix to my issues? I've been looking on the web for a few hours now, to no result.
Click to expand...
Click to collapse
The delete/create logical commands are in the thread OP, but you have to tap on "click to show" button.
Note that fastbootd is not the same as fastboot. And you need to be in that mode to avoid the "critical" warning and to be able to do the logical partitions stuff.

So, after massively failing to update my 8T I am stuck in a bootloop with a bit of Crash dump [dm-verity device corrupted force dump].
I am still able to access fastboot but that is it. I can't get adb working, when I attempt to enter recovery mode all I get is a black screen, MSM is not able to find my phone/I can't get my phone to enter EDL (been trying for about 5 hours now).
I feel so defeated by this can anyone help me?

Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/

BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.

Angilias37 said:
Whenever I connect my phone to the pc it just auto-boots. In my devices the driver does show up. But I don't think I have been able to access EDL.
I did reinstall the driver as well, no change. I tried installing the drivers and MSM stuff on a 2nd pc, still unable to get it going.
I did come across this method and my phone/fastboot keeps erroring whenever I try to use cmd for anything beyond Reboot fast boot. It's weird.
Click to expand...
Click to collapse
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see the option to update the driver.
PS: you may need to flash boot, DTBO, and recovery in fastboot first before you can use fastbootd to flash the other partitions for the fastboot method.

BillGoss said:
I see that your PC sees the phone (Qualcomm...) but has an ! against it. If you open that you should see l the option to update the driver.
Click to expand...
Click to collapse
Right but where's the update? From everything that I can find it is the most updated version

Angilias37 said:
Right but where's the update? From everything that I can find it is the most updated version
Click to expand...
Click to collapse
I use the driver (Qualcomm HS-USB QDLoader 9008) from https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008

OK
BillGoss said:
Did you read my post (#2)?
Does your PC make a sound when you connect your phone to it in EDL mode? If so, try reinstalling the Qualcomm driver (though I've never needed to do that).
If you can get into bootloader, then you can try using the method in https://forum.xda-developers.com/t/guide-unbrick-or-restore-to-oos-using-only-fastboot.4289013/
Click to expand...
Click to collapse
Ok I take back what I said! That link with the CMDs worked!
I really don't know what I did differently, probably skipped a step or something, but I was able to reset my phone!
Still unsure what is going on with the drivers but the crisis has been averted!
Thank you BillGoss! You are incredibly helpful!