Develop Bugs

[Help] Hard Brick

My Device Details :
Device : Lenovo P2a2
Bootloader : Unlocked
OS: Stock Android N 7.0
Recovery : TWRP
After Erasing modemst1 , modemst2 while flashing ROM, my device Baseband has been lost.. to recover baseband i have tried to flash everything in stock ROM files.. after flashing everything, my device is dead now (Hard Brick) there is no Recovery, no fastboot, only indicating RED LED while charging, is there any tool or any idea to recover my device? i have attached an log file to this thread & while connecting to pc there is a driver is installing ( Qualcomm HS-USB QDLoader 9008 ) . . it's screen shot also attached.

You can try put twrp or rom to external sd card and pray it works.
There is guides on google you can try. If all fail just take it to repair.

yea google 9008 + qfil and hope for the best

heatfire said:
yea google 9008 + qfil and hope for the best
Click to expand...
Click to collapse
all solutions are not related to Lenovo P2...

Kiryo24 said:
You can try put twrp or rom to external sd card and pray it works.
There is guides on google you can try. If all fail just take it to repair.
Click to expand...
Click to collapse
"You can try put twrp or rom to external sd card"
what do you mean by this?. if you mean Install recovery by copying in sdcard, how i can install it? because installing recovery via fastboot, to install it there is no other way, because there is no fastboot , Recovery...

Sangeeth Mk said:
"You can try put twrp or rom to external sd card"
what do you mean by this?. if you mean Install recovery by copying in sdcard, how i can install it? because installing recovery via fastboot, to install it there is no other way, because there is no fastboot , Recovery...
Click to expand...
Click to collapse
I just quickly read there is way to make sdcard bootable and i just speculate that maby phone reads and boots stock rom/recovery from ext sd card if booting from inner memory fails.

Kiryo24 said:
I just quickly read there is way to make sdcard bootable and i just speculate that maby phone reads and boots stock rom/recovery from ext sd card if booting from inner memory fails.
Click to expand...
Click to collapse
ok!

Thread cleaned up.
Please lets stay on topic. There is no need for trolls whatsoever.
If you can't answer the question asked by the OP, you can just move on to another thread. No need to be abusive whatsoever.
Thanks!
Regards
Vatsal,
Forum Moderator.

gl

Hi, I have exactly the same issue, has anybody managed to find a solution?

Try the below link for possible options in adb.
https://googleweblight.com/i?u=http...sue=267&page=6&type=1&grqid=VbDqgFEZ&hl=en-IN
Also please check out the video :
https://www.youtube.com/watch?v=sZXOJTGH8og
This was for ZUK1. But it should also work with P2. You just need to find the Raw stock firmware image.
The stock Firmware is also available here:
https://mega.nz/#!3hhhhRYC!bDbs1VGHA7s0n-uH-B30fVDsulFRVw-ZbYTvheS9m8I

QFIL did not work as it requires firehose file, which is unavailable for P2.
senseijtitus said:
Try the below link for possible options in adb.
https://googleweblight.com/i?u=http...sue=267&page=6&type=1&grqid=VbDqgFEZ&hl=en-IN
Also please check out the video :
https://www.youtube.com/watch?v=sZXOJTGH8og
This was for ZUK1. But it should also work with P2. You just need to find the Raw stock firmware image.
The stock Firmware is also available here:
https://mega.nz/#!3hhhhRYC!bDbs1VGHA7s0n-uH-B30fVDsulFRVw-ZbYTvheS9m8I
Click to expand...
Click to collapse

senseijtitus said:
Try the below link for possible options in adb.
https://googleweblight.com/i?u=http...sue=267&page=6&type=1&grqid=VbDqgFEZ&hl=en-IN
Also please check out the video :
This was for ZUK1. But it should also work with P2. You just need to find the Raw stock firmware image.
The stock Firmware is also available here:
https://mega.nz/#!3hhhhRYC!bDbs1VGHA7s0n-uH-B30fVDsulFRVw-ZbYTvheS9m8I
Click to expand...
Click to collapse
There is no adb & fastboot to try these above step, bro... ? only red light while charging..

I guess you need to wait till firehose for P2a2 is leaked. I am also having same issue as you. Just waiting.
Or else you can try custom solutions like infinity box. will cost you money

Sangeeth Mk said:
My Device Details :
Device : Lenovo P2a2
Bootloader : Unlocked
OS: Stock Android N 7.0
Recovery : TWRP
After Erasing modemst1 , modemst2 while flashing ROM, my device Baseband has been lost.. to recover baseband i have tried to flash everything in stock ROM files.. after flashing everything, my device is dead now (Hard Brick) there is no Recovery, no fastboot, only indicating RED LED while charging, is there any tool or any idea to recover my device? i have attached an log file to this thread & while connecting to pc there is a driver is installing ( Qualcomm HS-USB QDLoader 9008 ) . . it's screen shot also attached.
Click to expand...
Click to collapse
Yes exactly same happen to me unable to access recovery and fastboot, but you can restore your phone as long as in state Qualcomm HS-USB QLoader 9008, not by qfil or miflash tool it will make even worse if you flash by another firmware, but only by original p2 firmaware, your phone cannot boot because bootloader file corrupt

hendibudi said:
Yes exactly same happen to me unable to access recovery and fastboot, but you can restore your phone as long as in state Qualcomm HS-USB QLoader 9008, not by qfil or miflash tool it will make even worse if you flash by another firmware, but only by original p2 firmaware, your phone cannot boot because bootloader file corrupt
Click to expand...
Click to collapse
Without fastboot mode I don't think he can flash the firmware/bootloader.

abhayruparel said:
Without fastboot mode I don't think he can flash the firmware/bootloader.
Click to expand...
Click to collapse
Hacker from poland cant restore his p2 from hardbrick, while he can't access to fastboot and recovery, i can restore also after 3 months my phone got hardbrick

hendibudi said:
Hacker from poland cant restore his p2 from hardbrick, while he can't access to fastboot and recovery, i can restore also after 3 months my phone got hardbrick
Click to expand...
Click to collapse
I'm aksing how did you restore.

abhayruparel said:
I'm aksing how did you restore.
Click to expand...
Click to collapse
your phone should in state Qualcomm HS-USB QLoader 9008

hendibudi said:
your phone should in state Qualcomm HS-USB QLoader 9008
Click to expand...
Click to collapse
What after that?

OnePlus 5t - Bricked, No OS, Can't Flash OS

I recently rooted my OnePlus 5t. I found out that the root was unnecessary for what I needed, so I decided to undo the process. Somewhere during that process, I messed up big time. Currently, it has no OS and has the stock recovery, but I am unable to flash anything to it. It does not show up in file explorer anymore, but it does show up when I used "adb devices" command. When I did try to flash the OnePlus stock OS, I got a "compatibility.zip error". When I removed the "compatibility.zip" from the OS file, it then gave me an "update-binary" error. Now, I have no clue what to do. Any help?

wwkings said:
I recently rooted my OnePlus 5t. I found out that the root was unnecessary for what I needed, so I decided to undo the process. Somewhere during that process, I messed up big time. Currently, it has no OS and has the stock recovery, but I am unable to flash anything to it. It does not show up in file explorer anymore, but it does show up when I used "adb devices" command. When I did try to flash the OnePlus stock OS, I got a "compatibility.zip error". When I removed the "compatibility.zip" from the OS file, it then gave me an "update-binary" error. Now, I have no clue what to do. Any help?
Click to expand...
Click to collapse
There are fixes for this, you can use unbrick tool or just format data and flash oos if it gives you compatibility error you must use 'mixplorer' file manager to delete compitibility.zip :good:

intoxicated.mad said:
There are fixes for this, you can use unbrick tool or just format data and flash oos if it gives you compatibility error you must use 'mixplorer' file manager to delete compitibility.zip :good:
Click to expand...
Click to collapse
The unbrick tool does not work because I cannot get my device to be recognized as a SnapDragon device. I also cannot use mixplorer, because the device has no OS. I did manage to get TWRP back on it, but I am still unable to to flash any ROMs.

wwkings said:
The unbrick tool does not work because I cannot get my device to be recognized as a SnapDragon device. I also cannot use mixplorer, because the device has no OS. I did manage to get TWRP back on it, but I am still unable to to flash any ROMs.
Click to expand...
Click to collapse
UPDATE: I found out that in order for the unbrick tool to work, the phone needed to be put into EDL mode. I did this using "adb reboot edl". This allowed the device to show up correctly in order for the unbrick tool to find it properly.

need complete flashing guide with working/activated flashing tool

I have bricked my realme x2 (rmx1991) and trying to flash it. But the flashing tools are not working (msm tool needs username and password), (download tool shows "oppo unauthorized and cannot download"). So please give us a complete flashing guide with required rom and flash tool which is working/activated. Please.

hridoy501 said:
I have bricked my realme x2 (rmx1991) and trying to flash the .img. But the flashing tools are not working (msm tool needs username and password), (download tool shows "oppo unauthorized and cannot download"). So please give us a complete flashing guide with required rom and flash tool which is working/activated. Please.
Click to expand...
Click to collapse
Download the stock recovery from this guide extract it and flash it while your phone is on fastboot.
Before you flash stock ROM, you need to have the rom zip file either in phone storage or the sd card. You can use adb push commands to transfer the rom file to phone storage folder. ROM OTA can be downloaded from the realme official website.
Once you have the file, just select install from phone storage / install from sd card and it will flash the stock rom.
This is how I recovered my phone when it was bricked.

My device is bricked, cannot boot into flastboot or recovery. so need flash tool flashing method

hridoy501 said:
My device is bricked, cannot boot into flastboot or recovery. so need flash tool flashing method
Click to expand...
Click to collapse
You bricked the boot so lusten to me clearly u are gonna to flash your phone online with servets its costs you 15 dollars i cany put the website because the xda admin warned me before to put link so u gonna to download the full tom not ozip file the rom file has tool needs password so there is some websites buying the password so u can write me in private cuz i cant put any link

Hey
hridoy501 said:
I have bricked my realme x2 (rmx1991) and trying to flash it. But the flashing tools are not working (msm tool needs username and password), (download tool shows "oppo unauthorized and cannot download"). So please give us a complete flashing guide with required rom and flash tool which is working/activated. Please.
Click to expand...
Click to collapse
I did the same and now same thing happend.
Can you fix your device?

Question Poco F3 - How to restore FastBoot and use unencrypted TWRP

Hi there,
though i'm not a newbie, i'm not an expert either. I usually go by trial and error.
And so I have done with my Poco F3: I've succeeded (with trial and error) to get a recent MIUI 13.eu rom on it and it runs real smooth. But the TWRP I am using, is not able to decrypt anymore with the password I've always used. And I think my fastboot-option is corrupt, since when I boot to this option my pc does not recognize my phone as a device anymore.
I am looking therefore for instructions / a tutorial on how to repair the fastboot option and how to go about with the encyption if I don't know what te password is. I would like to be able to upgadre to the latest .eu rom, but for this my twrp needs to decrypt and I can't get that to function anymore. So in present TWRP, i can not acces any rom-files, also not through the SD-storage function
Ofcourse there will probably by an option for clean install of everything, but where is it and how does this find the nescessary rom-file (as the file explorer had only acces to internal files and even then not to encrypted part).
Hope I explain it clearly enough?
Any help / tips / suggestions will be appreciated!!
Thanks in advance!

* download mi unlock tool and open its settings (at the top right corner)
* install phone drivers (connect your phone in fastboot mode)
also make sure you connect the phone on a usb 2.0 or 3.0 port
as for twrp, use the following twrp:
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.3_A12/%5BBOOT%5D3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.3_A12-alioth-skkk_a616ae6b.zip

3zozHashim said:
* download mi unlock tool and open its settings (at the top right corner)
* install phone drivers (connect your phone in fastboot mode)
also make sure you connect the phone on a usb 2.0 or 3.0 port
as for twrp, use the following twrp:
https://dl.akr-developers.com/?file=skkk/TWRP/A12/v6.3_A12/%5BBOOT%5D3.6.2_12-RedmiK40-POCOF3-Mi11X_v6.3_A12-alioth-skkk_a616ae6b.zip
Click to expand...
Click to collapse
Great tip on the correct installation of phone drivers, thank you. After re-installing them through the mi unlock tool, it looks like the device is recognised again.
As for the TWRP, I am using the official TWRP 3.7.0 for A12 now... wil downgrading to the 3.6.3 skk version be a step forward for the decryption problem?
Thanks very much for helping me out!

mnstr said:
Great tip on the correct installation of phone drivers, thank you. After re-installing them through the mi unlock tool, it looks like the device is recognised again.
As for the TWRP, I am using the official TWRP 3.7.0 for A12 now... wil downgrading to the 3.6.3 skk version be a step forward for the decryption problem?
Thanks very much for helping me out!
Click to expand...
Click to collapse
skkk twrp is pretty much the go to twrp for poco f3

Thanks for the help, but alas the problem isn't solved.... After reinstalling the USB drivers, my the driver-utility reports it sees a device after I connect my Poco F3. In ADB (through powershell with administrator rights) however, on the command ADB devices it shows no connected devices. And also the fastboot flash recovery command does not work... it looks like it is uploading the twrp-file, but notihing really happens.
I'm guessing the fastboot that the official TWRP 3.7.0 brought me, does not function well... But now I have no idea on how to get the correct TWP img version on to the device, since I cannot seem to get an ADB session, and since the present TWRP 3.7.0 does not recognise the normal filesystem, I also cannot load it through the TWRP interface.
Any ideas on how to get out of this mess are very welcome, I would very much like to be able to have a properly updateable Poco F3 once again, appearantly I messed up by installing the official TWRP 3.7.0...
Thank you for helping me out, any idea is appreciated!

Luckily this problem is solved now. Problem was that I was using the wrong TWRP, appearantly the proper one for alioth is the TWRP from skk. And after booting into that one (not flashing it yet), I could get in the new TWRP recovery, which did recognise my folders and file system, including my USB drive. So I was able to install the latest EU rom from that booted TWRP and before rebooting, I also opted in the new TWRP to have this new TWRP flashed into recovery.
After rebooting, all is well. I have the latest stable EU rom installed and my installed recovery is the latest skk one. Thanks for all the help, I am glad I called on the community!

Question Tough technical problem - First hardbrick then softbrick

Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...

Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com

NOSS8 said:
Try to use Miflash with the oldest Fastboot rom.
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
MIFLASH[GUIDE]⚙ USE XIAOMI FLASH TOOL
FOR ALL XIAOMI BOOTLOADER MUST BE UNLOCKED https://new.c.mi.com/global/post/101245 https://en.miui.com/unlock/index.html ----------------------------------------------------------------------------------------------------------- All your data...
forum.xda-developers.com
Click to expand...
Click to collapse
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?

stercorarius said:
Thank you for your input, yes we have thought of that and downloaded the oldest global rom but haven't tried to flash it yet because of another hardbrick possibility. We are trying to fix it with terminal within twrp (we can flash twrp now) attempting to fix the partitions.
Any other ideas?
Click to expand...
Click to collapse
Not sure that the Twrp for this device is 100% functional, especially since this device has A/B partitions and A13 has write restrictions.
You can try a Xiaomi Eu rom and flash the rom in fastboot mode with the first install.bat script included in the extracted folder.(xiaomi.eu_multi_MI11LE_XM11Lite5GNE_V14.0.6.0.TKOCNXM_v14-1)
Xiaomi.eu Multilang MIUI ROMs - Browse /xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv14 at SourceForge.net
OFFICIAL mirror of MIUI Multilang ROM by https://xiaomi.eu/
sourceforge.net
Format data, erase your data and create a new partition if necessary (Twrp format data type yes, Miflash and Xiaomi Eu rom do it too).
The recovery roms do not contain all the system imgs unlike the Fastboot rom and Xiaomi Eu rom.
Could also be a HW problem.

stercorarius said:
Hello all,
I've been having the hardest week, all my personal business at the halt (cant use bank apps, email etc.). One morning my phone suddenly entered a bootloop, then since then I was in a bit of hurry, I tried a stock rom recovery update from twrp, that made the phone enter a hardbrick status.
Then since we don't have a firehose for the 'lisa' I had to pay a guy to take it out. That solved the hardbrick but the softbrick remained. Since I am not an android expert just have mediocre knowledge I asked a kind persons help. They've been trying to help me for days but we still couldn't solve the issue and I thought other opinions would be nothing but helpful.
The details you should know:
1. Only hardware operation made on the device is changing a resistor. (Can explain it better, if requested). But the phone was working just fine after it for months.
2. We have identified the partitions are all messed up and and flashing stock rom doesn't solve it, tried Eu, global and Chinese roms.
3. The system was missing on the twrp advance wipe and there were:
dalvik
metadata
data
ınt storage
sdcard1
usb otg
4. I didn't understand all the things he/she tried but tried to fix the partitions mainly using these sources ( it could give you a better idea ):
How to create System partition in Android? Which is accidentally deleted when tried to increase size.
Tools needed can be downloaded from forum.xda-developers Section 3. parted_gdisk_fdisk_mkfs.ext4-AARCH64.zip - [Click for QR Code] ...
illitrateman.blogspot.com
How to fix "Partition does not start on physical sector boundary" warning?
I have one HDD on my laptop, with two partitions (one ext3 with Ubuntu 12.04 installed and one swap). fdisk is giving me the following warning: Partition 1 does not start on physical sector boundary
askubuntu.com
5. We tried 3 different custom roms but no avail.
6. At the moment the phone can enter in fastboot but giving trouble flashing twrp or orangefox.
I'm confident my expert angel has a solution for that but I think in general any thoughts, ideas, suggestions would be highly appreciated.
Thank you in advance...
Click to expand...
Click to collapse
Which twrp version were you using and which version of MIUI did you try to flash when you hard bricked?
There's no system partition nowadays, it is now included in the "super" partition (system, system_ext, product and vendor) and developer removed the option to wipe it because you are not intended to wipe it.
My recomendation is to flash any fastboot rom, I've flashed 7 roms with fastboot and it always worked flawlessly.

Hi, I'm the person that has been helping.
Of course we flashed miui (in fastboot). Global and chinese. We haven't tried eu yet.
I think I've found the source of the problem, but I'm not sure if solving it will fix the bootloop. A partition that's called switch is corruped. It reports as 16EiB (yes that is correct, 16 exabytes, 18446744073709551607 sectors, reported by gptfdisk, full report). It could just be a program issue. The switch partition in located in /dev/block/sda1 and /dev/block/dm-5. I also found that a dummy.img file is being flashed to that partition.
I also got this error from trying to open the switch partition from a newer version of gptfdisk.
I'm not sure if that's the reason for the bootloop, but I think it can be.
These reports have been from /dev/block/sda1. From /dev/block/dm-5 it's like this.
If someone wants to look at the tools I found, they're here.
If someone has any suggestions or possible answers for us, please reply.

What is the error generated by Mi Flash?
Miflash log folder

NOSS8 said:
What is the error generated by Mi Flash?
Miflash log folder
Click to expand...
Click to collapse
Hi, there was is no error in miflash.
You can take a look here if you want to.

Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.

NOSS8 said:
Indeed, no error.
Could be a boot sector problem but with dynamic+A/B partitions+A13 , it gets tricky.
Click to expand...
Click to collapse
Can we somehow repair the sector?

Sucharek 233 said:
Can we somehow repair the sector?
Click to expand...
Click to collapse
I saw that you changed a transistor, maybe there is a problem elsewhere that is causing this to happen.
Changing the motherboard with the flex cable might be preferable.
I doubt that what you are trying to do is possible due to the complexity of the current system and especially for boot sectors which are not likely to be accessible with current tools.
Especially since the problem has not been identified with precision.

A little update:
We tried flashing EU rom and the oldest rom, but still no luck. Phone is still bootlooping and switch partition is still broken.