Database Info

Xiaomi Mi4c stuck at MI.com screen

Hi all,
I've received my Xiaomi Mi4c today and tried to install CM 12.1 from here :
http://www.teamsuperluminal.org/mi4c-cyanogenmod-12-1/
I think I've bricked my device, because when I tried to install the new ROM it failed, with an error that there is no OS install, are you sure you want to reboot and now I've got a device that doesn't boot or start...
I think it can connect to the PC but I don't have drivers for it... even if I have is there a way I can restore it to MIUI default ROM?
Please help..
Edit: I've deleted the ROM I had on the SD, so I ahve access to TW Recovery but I don't have anything on the phone... is there a way I can copy a file over and flash it again?

In twrp, go to mount tab and then mount your storage while connected to your PC and transfer the ROM over

Hi ermacwins,
Thx for helping!
I couldn't mount my external SD card, however I've sideloaded a stock MIUI ROM on the device. When I try to flash it I receive the following error:
zip signature verification failed 1
When I untick the zip verification it just fails.
Any ideas what I'm doing wrong?

GeorgiUzunov1990 said:
Hi ermacwins,
Thx for helping!
I couldn't mount my external SD card, however I've sideloaded a stock MIUI ROM on the device. When I try to flash it I receive the following error:
zip signature verification failed 1
When I untick the zip verification it just fails.
Any ideas what I'm doing wrong?
Click to expand...
Click to collapse
You have the following possibilties:
Download a fastboot rom and flash it with MiFlash tool through your PC.
Or download a Rom from Xiaomi.eu or sMIUI (you can also use CM12.1 or MoKee). Put it in your phones storage and flash it in TWRP. But before you flash it, wipe cache, dalvik, data and system. Then flash it. If you get an error, just reboot again to TWRP and flash it a second time, but this time without wipes.
You see, you can easily recover your phone

please help me. it's stuck in mi logo i tried both the recovery mode (pc doesn't recognise it) and the miflash that says an error: the system can not find the file specified. what im i gonna do ??

alexvv said:
please help me. it's stuck in mi logo i tried both the recovery mode (pc doesn't recognise it) and the miflash that says an error: the system can not find the file specified. what im i gonna do ??
Click to expand...
Click to collapse
Press volume down + power for 4-5 seconds it will force reboot to fastboot mode then u can flash chinese stable rom and try again you must have kept the fastboot package by side so that if anything goes wrong you can get back to working stock rom

alexvv said:
please help me. it's stuck in mi logo i tried both the recovery mode (pc doesn't recognise it) and the miflash that says an error: the system can not find the file specified. what im i gonna do ??
Click to expand...
Click to collapse
Power off your device, then press POWER + VOLUME DOWN button together until you see the fastboot logo
Connect the device to a pc with (fastboot/adb drivers installed)
Download a TWRP recovery for the device and boot it with the following command:
Code:
fastboot boot mi4c_recovery.img
Then you will be able to wipe/flash new roms using the recovery.

well after many hours, i found the only working solution to be by adb sideload (thanks god i had twrp recovery, otherwise my phone would be completely dead). i flashed a smiui rom and all is fine. thanks for the help anyway. btw miphone tool is useless, couldn't get it to work.

can you say step by step with the adb sideload? my phone is enter in fastboot mod but not in recovery, when i keep volum up and power is starting to flash mi.com over and over again. I tried to flash Version: 6.2.25 (MIUI7) please help

SM-G930x Retail Phone Secure Check Fail : (PIT), help please?

So I got a hold of a retail G930x and was successfully able to install TWRP and factory reset with a stock image, only problem was that I never turned off the FRP lock, and when the phone was restarted while updating SuperSU my recovery was blocked. OK, no problem, just flash a stock ROM through Odin mode right? Well for some reason G930AATT1APB5, and G930FXXU1APB4, do not seem to work. At one point I was able to partialy boot into the stock recovery, but at another flash attempt my computer blue screened and I received the error message "An error has occured while updating the device software. Use Emergency recovery function in the smart switch PC software", but Smart Switch returns an error message of "Device Not Supported". I can still boot into Download mode and attempt flashes, but I can't seem to find a working ROM for this phone or a solution to the stock Recovery issue (which is most likely corrupted by now). Any help would be greatly appreciated, thank you.

edit:
edit: so I flashed a recovery image file from ROM.G93xF.XXU1DQFM-v18.0.by.ambasadii.zip and was able to get to the stock recover screen. Unfortunately i get an error message saying "Failed to mount E: /system (Invalid Argument)
Update from external storage is disabled.

Nexus 5 bootloop bricked - CAN'T FASTBOOT/SIDELOAD FLASH - Need QCom TESTPOINT

I had a Nexus5 that was stock, and working.
I unlocked the bootloader and flashed to 31E, using the factory image.
It was OK afterwards. I used
After a week it one day randomly rebooted, and hasn't booted since.
After power on, there is Google screen for ~50sec, and then colour animation for 30+min.
THE PROBLEM - FASTBOOT FAST WRITE FAILURE
I can boot into fastboot. It says its unlocked. I can erase and flash laf, boot .. but Most of them, like recovery, cache, it says
FAILED (remote: flash write failure)
Obviously, if you run the flash-all or anything similar you will get the same thing.
RECOVERY IMAGES - FAIL
It says it can't mount /cache. Mounting system, and then wiping cache spits out 20 mount errors. Factory reset/wiping - same.
fastboot boot with 4 different TWRP boots after 5min to TWRP logo screen, and shows up in adb. I found a CWM recovery that booted,
but had lots of mount errors.
I played around with parted, and make4fs, trying to recreate partitions - no dice.
they are there under block./mmcblk0 - 29 of them. I get errors that journal is outstanding when trying to e2fsck. And trying different superblock didn't work either.
SIDELOADING - FAIL
I tried sideloading from ADB. Doesn't work. Complains about mount points. 0%.
LG DOWNLOAD MODE - NOT EXIST??
I cannot boot into "LG" Download mode. 2 other LG phones boot immediately into download , so I'm 99% sure the cable or PC, or "static" is not the issue.
QDLOADER - NO EFFECT
Finally, Qualcomm USB QDLoader - I got it working in Win10 x64.
To boot device into QDLoader, it has to be booting up normally to Google screen, and you are holding all buttons for 8+ sec, until you see it in Device Manager.
I tried both the 16GB and extracted TOT flash, and they completed, but phone is the same. Still cannot flash factory image.
I tried running RAM test. Success. EMCC read and erase test are OK, but "rwrite" test fails immediately (write protected???)
So, I tried flashing the system, cache, misc, persist, modem and recovery from BoardDiag. They completed, taking 30min for system and 20min for cache.
Still fails.
QFIL - WHERE FILES?
Where do I get the files for QFIL? Is it worth even trying?

FYI, for reference, I basically gave up and bought a new phone.
This error message basically means your eMMC is "fried":
FAILED (remote: flash write failure)
The failing eMMC BoardDiag test confirms it.
I dont believe so many people would have Sandisk eMMC (the one in Nexus5) which would suddenly become completely broken.
I'm quite sure some internal project engineer out there knows of some "fuse" or "write-block" that's causing this...
But, in meantime, I've decided its better to be enjoying the phones I express ordered from Hong Kong...

Installing system update fail after Odin flash. Boot into recovery mode.

Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
E:failed to clear BCB message: failed to fin /misc partition
Click to expand...
Click to collapse
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!

normsrayn said:
Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!
Click to expand...
Click to collapse
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Just download the latest version of the file (6.0)
Now wait until rom boots
-----------------------------------------------------------------------------------
Please donate and like if you think i deserved it,
If it didnt work you don't have to do it
Happy flashing and good luck
Dont forget to update me after following the steps

I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!

normsrayn said:
I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!
Click to expand...
Click to collapse
Flash the stock firmware again but from download the firmware from Samfirm application. Please use the HOME_CSC too or your device is wiped. If you need the firmware just post modelnumber or name idk and CSC code and i can post a link with the firmware for you. TWRP can't mount /data and you will need to format your phone with means you lose everything.

getting dark error in galaxy j4 smj400F after system update failing
Picklewickle said:
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
but i have done factory reset so how to enable oem /unlock bootloader to flash via odin
HELP
-----------------------------------------------------------------------------------
Click to expand...
Click to collapse

Same issue
I have the same issue. I cant boot into download mode at all to even attempt to flash anything

Lenovo Tab2 A10-30 (tb2-x103f), I have messed it up.

Hi all,
When installing TWRP on my daughters tablet I have accidentally flashed boot instead of the recovery with the TWRP image on the tablet using fastboot.
After I realised the error I have flashed TWRP to the recovery partition and rebooted the tablet to access TWRP.
When I was in TWRP I have wiped the data partition and flashed the lineage os rom for this tablet.
First error I noticed was E: legacy property environment did not init successfully, properties may not be detected.
Installation appeared to run properly but in the end I got a lot of E:Unable to stat '/data/.........' messages.
When rebooting TWRP asks to install SuperSu which also shows the same kind of error messages.
At startup I get the Lenovo logo and afterwards only a black screen which is turned on (in the dark you can see that it is active)
I am currently unable to access the fastboot environment, when rebooting using power and volume down it looks like the tablet is in fastboot mode, but when connected to the laptop it shows up as MTP device.
Fastboot or adb itself does not show any connected devices.
When rebooting after the Format data option in TWRP and installing an image I get the following errors :
E:Unable to find partition size for '/recovery,
E:Mount: Unable to find partition for path '/emmc'
E:UnMount: Unable to find partition for path '/emmc'
E:Mount: Unable to find partition for path '/emmc'
I have tried to flash the tablet back to stock rom with the Lenovo/Qualcomm downloader tool but that tool hangs at the Sahara stage and does not proceed after detecting the tablet.
Does anyone have an idea I can try or is the tablet bricked ?
TWRP version is 2.8.7.0 and I am able to access the recovery.
ROM's tried are lineage-14.1-20170520-UNOFFICIAL-x103f.zip and RR-N-v5.8.5-20171113-x103f-Unofficial.zip
USB debugging and bootloader were unlocked in the developer options on the tablet.
I ave rebooted to the bootloader from TWRP after trying another flash, still having a black screen.
In device manager I am now showing Lenovo-HS-USB Diagnostics (COM20), Lenovo HS-USB NMEA (COM21) and Lenovo HS-USB Modem Phone.
Still no luck with adb or fastboot.
Hope someone can help,
Kind regards,
Klaas-Jan

To revert to Stock
You could try the method indicated in this post. Please read the post thoroughly before proceeding.
Note that in step 4 you should be looking for the model number of YOUR tablet.
I have not tried this method myself yet, so I don't know if it works. As always you do this at your own risk, but as your tablet is not working, you may wish to give it a try.
Good luck.

Baldyiskaal said:
Hi all,
When installing TWRP on my daughters tablet I have accidentally flashed boot instead of the recovery with the TWRP image on the tablet using fastboot.
After I realised the error I have flashed TWRP to the recovery partition and rebooted the tablet to access TWRP.
When I was in TWRP I have wiped the data partition and flashed the lineage os rom for this tablet.
First error I noticed was E: legacy property environment did not init successfully, properties may not be detected.
Installation appeared to run properly but in the end I got a lot of E:Unable to stat '/data/.........' messages.
When rebooting TWRP asks to install SuperSu which also shows the same kind of error messages.
At startup I get the Lenovo logo and afterwards only a black screen which is turned on (in the dark you can see that it is active)
I am currently unable to access the fastboot environment, when rebooting using power and volume down it looks like the tablet is in fastboot mode, but when connected to the laptop it shows up as MTP device.
Fastboot or adb itself does not show any connected devices.
When rebooting after the Format data option in TWRP and installing an image I get the following errors :
E:Unable to find partition size for '/recovery,
E:Mount: Unable to find partition for path '/emmc'
E:UnMount: Unable to find partition for path '/emmc'
E:Mount: Unable to find partition for path '/emmc'
I have tried to flash the tablet back to stock rom with the Lenovo/Qualcomm downloader tool but that tool hangs at the Sahara stage and does not proceed after detecting the tablet.
Does anyone have an idea I can try or is the tablet bricked ?
TWRP version is 2.8.7.0 and I am able to access the recovery.
ROM's tried are lineage-14.1-20170520-UNOFFICIAL-x103f.zip and RR-N-v5.8.5-20171113-x103f-Unofficial.zip
USB debugging and bootloader were unlocked in the developer options on the tablet.
I ave rebooted to the bootloader from TWRP after trying another flash, still having a black screen.
In device manager I am now showing Lenovo-HS-USB Diagnostics (COM20), Lenovo HS-USB NMEA (COM21) and Lenovo HS-USB Modem Phone.
Still no luck with adb or fastboot.
Hope someone can help,
Kind regards,
Klaas-Jan
Click to expand...
Click to collapse
The errors look like the ones I got when I installed the TWRP posted here. There's something better available. Have a look on my post