Database Users

Need help fixing my bricked phone

Hey Guys,
I have a redmi 3s prime and i tried to install lineage os on it, during the process i accidentaly flashed twrp over both the recovery and the boot. Now i cannot get into the recovery (and fastboot) unless i flash it over boot before rebooting my phone. After that i AM able to flash an new rom but it seems to always have wifi issues.
atm i am trying to flash the xiaomi developers global rom to see if it makes any difference. My main goal is to flash TWRP and a curstom rom (linage or resurrectionremix).
Can anyone help me?
Thanks alot!
Update #1
The flashing of the global developer rom worked and the wifi seems to work aswell, i will try to boot into fastboot and recovery.
Update #2
Its seems i am able to boot into fastboot and recovery again
Update #3
Following a tutorial for flashing TWRP and a custom rom but cant se2 anyone help me here?:
Code:
>>> Check then next step to root :
- launch minimal adb tool (previously installed)
- type : adb devices (to list phone connected) it will appear "unauthorized"
- on the phone : accept the computer
- re type : adb devices
it has changed in "authorized"
- type : adb reboot bootloader
it will go in fastboot mode (the same that power + vol down)
- type : fastboot devices
your phone will appear as in adb mode (unless the bad signed driver is choosen in win10 ; i won't repeat it again)
- type (optional) : fastboot oem device-info (to verify if bootloader is locked or unlocked)
now, we go to root
- type : fastboot boot twrp.img (if it is your renamed twrp copied in the minimal adb folder)
link for TWRP guide at the end if needed
!!! it will boot temporary in this recovery but it will keep your original recovery !!!
> allow to modify system (don't keep the "read only" if you want to root or flash recovery later)
go to settings to set date, hours, language, set custom options...
My optional advices :
- save your EFS & persist partitions or all whole partitions (except cache) to make a backup
- export this backup in computer or SD card in case of future problem
(EFS, persist are usefull to save and restore your IMEI in particular)
- you can flash directly TWRP with fastboot command : fastboot flash recovery twrp.img
>>> Root :
Now flash DM-verity patch, then superSU.zip to root and accept to wipe dalvik/cache after, finally reboot !
Device is rooted ! and you have kept the original recovery.
the reboot is quite long like rom update (because of cache rebuild)
sometimes, parts of theme are lost after rooting : just restore your theme
some devices don't need DM-verity patch as explained upper
superSU app shows "systemless root" from android 6+, it is normal, read below
>>> Change the Recovery by TWRP (optional) :
Now you are rooted, you have 2 methods :
- Install one TWRP app with googleplay and flash recovery through app on rooted device.
New official app in development (flash/backup .img & .tar)
- OR reboot in fastboot mode (with TWRP app method or power+vol- method or adb reboot recovery method)
in fastboot mode, and type commands :
fastboot devices
fastboot flash recovery twrp.img
(be sure your twrp.img is unlocked and correctly copied/renamed in minimal adb folder)
Now, long press power to turn OFF phone
power + vol+ (release power at vibration) to enter in TWRP or by TWRP app or Updater app or under Windows with minimal adb reboot recovery command
Note for devices with DM-verity : flashing TWRP needs to have patched system with DM-verity patch before because you will modify system most of time - generally, you don't need to patch again because you have ever done it in previous steps - in case of bootloop : go to fastboot mode, boot in TWRP with command and patch it.
Chainfire has recently modified superSU for android 6+ devices with DM-verity to install root without modify the system : it's called "systemless root". When you flash superSU.zip, it detects automatically android version, cleans old files and installs with appropriate method. Maybe no need to patch boot in this case with DM patch.

Hard Bricked!

Hi,
My devices is stuck on Mi logo, it was not Bootloop, it cant reboot to EDL, sometimes my devices can go to Fasboot mode but sometimes cant, while in fastboot mode I check in the Device drivers section theres no Qualcomm blablabla but the only available is Android Bootloader Interface and when I try to flash my phone via Mi Flash Tool I cant because my devices is not detected, What should I do? :crying:
1. My device is already unlocked
2. Before this I was flashing RR, and it was just fine, then I try to boot to my TWRp but it seems I cant, then I install TWRP and it just works fine, then I want to flash new rom, then I qipe dalvik cache, cache, system, and data then it shows error "partitions blablabla" then I try to factory reset in TWRP, its done its job, then I try to flash the new rom but when I pick "sdcard" (internal storage) it was blank! then I check "sdcard1" (external memory) it was blank too! then I just reboot (it says no OS installed, I just swipe then it stuck on MI Logo).
3. I have tried some tricks to recover it but It cant! (I still didn't tries deep flash cable or either test point method because I don't know how to do that)
4. My devices Is Detected when I typed "fastboot devices" in cmd but not detected in MiFlash Tool.
Please how do I fix this problem?? please help me as soon as possible!!
Thanks.

Help me!
Please someone answers me! :crying:

Since your device is showing in fastboot, flash TWRP again from fastboot. Copy ROM and GApps to external SD card and boot into TWRP. Wipe dalvik, cache, data, system, and internal storage. Flash new ROM, GApps reboot.
If you get any errors while wiping partitions then format the partitions to f2fs or anything then again back to ext4.
Hope this helps!!!
Cheers ?

Chris828 said:
Hi,
My devices is stuck on Mi logo, it was not Bootloop, it cant reboot to EDL, sometimes my devices can go to Fasboot mode but sometimes cant, while in fastboot mode I check in the Device drivers section theres no Qualcomm blablabla but the only available is Android Bootloader Interface and when I try to flash my phone via Mi Flash Tool I cant because my devices is not detected, What should I do? :crying:
1. My device is already unlocked
2. Before this I was flashing RR, and it was just fine, then I try to boot to my TWRp but it seems I cant, then I install TWRP and it just works fine, then I want to flash new rom, then I qipe dalvik cache, cache, system, and data then it shows error "partitions blablabla" then I try to factory reset in TWRP, its done its job, then I try to flash the new rom but when I pick "sdcard" (internal storage) it was blank! then I check "sdcard1" (external memory) it was blank too! then I just reboot (it says no OS installed, I just swipe then it stuck on MI Logo).
3. I have tried some tricks to recover it but It cant! (I still didn't tries deep flash cable or either test point method because I don't know how to do that)
4. My devices Is Detected when I typed "fastboot devices" in cmd but not detected in MiFlash Tool.
Please how do I fix this problem?? please help me as soon as possible!!
Thanks.
Click to expand...
Click to collapse
Yeah. This is not a hard brick. You can also reflash miui from fastboot. Extract that tgz file of miui and click on one of the batch files.

Help!!! My Axon 7 is dead (Boot into fastboot and EDL only)

My phone was working fine, until it suddenly freeze and reboot. After that, it runs into bootloop at zte logo.
I had miflash the phone with stock rom. Flash successful, but the phone still bootloop at zte logo (can't enter system).
I can enter fastboot only (recovery + system => reboot);
try:
0. boot to system => definitely failed
1. hold volumn up + power button => failed
2. fastboot boot recovery => failed
3. fastboot boot twrp.img => failed
4. axon7tool -w recovery = successful , but failed when boot recovery
5. axon7toolkit : flash twrp = successful, but failed when boot recovery
6. miflash A2017 rom = successful, but failed when boot system + recovery
7. miflash A2017 rom = successful, but failed when boot system + recovery
:crying: I am desperate here.
Any help would be appreciate!! Thank you!

Try going into your recovery and formating as ext4. If you were using f2fs, edl won't work.

My edl is working, and miflash successful but then the device cant boot system (and cant boot recovery also)

tamahouse02 said:
My edl is working, and miflash successful but then the device cant boot system (and cant boot recovery also)
Click to expand...
Click to collapse
First of all, redownload the stock EDL file. If you already have it, just check that it's not corrupted or anything. I'd advise redownloading it, which the files can be found from this thread.
Flash the stock EDL, then before booting, go into stock recovery (Hold volume up button whilst powering on). Do a factory reset, and also wipe cache. Now try booting. It should boot, and if it doesn't, then the only thing I can think of is either a corrupted EDL file or physical damage inside the phone to the memory chip.

I had miflash two different edl roms (china and us). And facing the same issue. It may be the hardware problem.

tamahouse02 said:
I had miflash two different edl roms (china and us). And facing the same issue. It may be the hardware problem.
Click to expand...
Click to collapse
Everyone is telling you that you have to format your data partition, but you're not answering that: did you or did you not? If you have Fastboot, enter it and issue
fastboot format userdata
and hit enter

Choose an username... said:
Everyone is telling you that you have to format your data partition, but you're not answering that: did you or did you not? If you have Fastboot, enter it and issue
fastboot format userdata
and hit enter
Click to expand...
Click to collapse
I did. The phone enters system for 1 minute then keep reboot itseft again

[ZE550KL] Unbrick Experience, QCN recovered, working from 9006/9008

First of all, thanks for all the people here provide very useful message.
Acutally I encouter a lot of similar issues across the posts.
Please refer to the posts here:
Unbrick guide Z00l Ze550kl
Need QCN file for ZE550KL/Z00L (2GB Ram) Please.
[Solved]Stuck on logo when booting into custom ROM( Zenfone 2 laser ZE550KL Z00LD)
My model is ZE550KL 2GB/16GB version.
What need to be prepared (please look around from google)
1. CSCImage for recovery
2. QPST 2.7
3. Workable QCN, if you have no backup please make one from the other post. (you will need imei coverter and HxD)
4. Retail image WW_ZE550KL_1.17.40.1234-rel-user-20160304185904-secured-releaseAFT_QC
5. Offical latest image
6. TWRP
7. Minitool Partition Manager (I tried diskpart but not working, so please use this one)
8. Qualcomm Driver
Here are the procedures for reference (I do this for over 10 times and 3 nights)
Please make sure you have working QCN...otherwise you cannot recover the calling feature.
1. Erase aboot
fastboot_8916 erase aboot
use above command to erase the partition
you can unplug the battery and cable and replug them.
or simply use fastboot reboot command.
Result: Device enter into 9006 mode
2. Open Minitool Partition manager
Right click and Delete all partition.
Create one single partition using ext4 format
Once done, remove the battery and cable, replug them.
Result: Device enter into 9008 mode
3. If you installed QPST, you should have a program called QFIL
Please use it and extract the firmware from CSCImage, it should have all the items except emmc MBN, just copy it from the root folder.
If you do this correct (follow other post for more detail)
Replug the device will give you a fastboot screen
Result: Device with workable fastboot
4. Now you have a clean bootloader, but no other thing
Go to CSCImage and click flashall
Once it is done, all the partitions will be ok (sometimes I got /factory not mount, let's fix this later)
Result: you will have a engineering OS and bootloader unlocked, diag mode natively enabled.
5. Open Software Downloader from QPST, and recover the QCN, it will reboot the phone.
If you are not doing this correctly (and many issues here), you will get bootloop.
And you have to start over again.
My suggestion is do not touch any of the bootloader setting. (so do not try to use unofficial bootloader unlock guide)
Even you give a command like "fastboot oem adb_enable" it will cause a bootloop and have to start over.
So my suggestion is not touch any bootloader setting
Result: The phone calling and data should be recovered. You can test by making some call.
6. If you want to keep your bootloader unlocked, the retail image flashall you can search there is a "oem lock"
change to unlock and run it in fastboot mode.
Result: You will have a bootloader unlocked phone, with WW firmware.
You can start from here to do TWRP.
to fix /factory partition. you can install busybox and in adb shell, use mkfs.vfat for the partition.

What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)

christian.arvin said:
What is CSCImage, I tried your method but got stuck on missing partitions. (Boot, Recovery, System, etc..)
Click to expand...
Click to collapse
This means you didn't unlock your bootloader.
bootloader needs to be unlocked to flash the partition file, and then the partition will be recovered without data.

My bootloader was unlock.
I digged deeper in your method. And this is what i understand and let it be an information for those who will try.
Back up all partition before you delete all partitions. (Your serial and other sensitive data are stored in some of this partition)
Your method only restore 5 partition table that is inside the main0 gpt mbn.
Note: the whole partition table is listed in the both0 gpt mbn.
In my stupidity I renamed the both0 gpt to main0 gpt thinking that it would work. Instead I run into an unstoppable bootloader bootloop.
In an ending note my ZF2 Laser's only hope is a full eMMC reflash that requires external methods. Or let the official professionals handle it.

[SOLVED] Bricked ALE-L21 | Damaged fastboot partition

So, I've had an issue with fastboot mode for some time, it reacted to everything with a "remote: command not allowed". I tried an sdcard upgrade to stock which did nothing, ran the oem unlock again and that said unlocked succesfully (it was aleady unlocked but ok) then tried to relock, tried to flash every stock image from B896 I knew the partition of - everything returned "remote: command not allowed", also did a fastboot reboot - which worked, if I remember correctly, enabled usb debugging and saved my computers key just to be sure - still no difference.
Later on, I tried reinstalling the fastboot image from the phone itself using dd - that was pretty stupid, I know - especially since there were two files named fastboot and fastboot1 but only one fastboot partition (I don't even, just had to try) and after a reboot it shows no logo, doesn't vibrate, only thing it does is blink the led red-green-green for a minute and power off again. I have a raw backup of the original partition but no way to restore it.
Does anyone know how to repair a diskdestroyer'd fastboot partition? I'm willing to try any risky methods, including disassembly and reflashing of the memory chip. Does someone have a model number for the built in flash storage?
Any help is much appreciated.