Develop Bugs

[Q] Bootloop (softbrick to hardbrick back to softbrick)

Long story short:
EDIT: I somehow magically (after 2 hours of trying) got into recovery, cleaned and wiped everything and booted into MIUI. Switched to CM 12.1, leaving this thread for anyone that experiences the same problem.
1. I was running CM11-R24, with an early version of the Xcelerate kernel. All was fine and well but today it restarted on its own a couple of times. It would enter a bootloop that I managed to get out of by going into recovery and rebooting from there.
2. Bootloop happened again, couldn't get into recovery.
3. Installed newest twrp recovery via fastboot. No change.
4. Managed to hardbrick my phone by installing a wrong .img of a global version.
5. Managed to revert back to a softbrick by installing the right (hopefully) global version of my mobile phone.
6. I did manage to read a logcat inbetween and I remember there being something about the kernel settings being nulled to default, because there was a failed boot 2 times in a row.
Links:
Hard-brick to soft-brick procedure I followed - http en.miui.c o m thread-54139-1-1.html
Used global version: Singapore 50? Going to try other versions
Settings in MiFlash tool (using 2014.11 version). - http postimg.o r g /image/hh122e54j
Current problems:
1. When powering up the phone, it will not go beyond the Mi logo.
2. When trying to enter recovery (volup+power) I enter another loop. It is normally 10-15 seconds of Mi logo, power down, 3-5 seconds of Mi logo, power down. Repeat. I do not stop holding the recovery combination while this happens.
3. I have installed via fastboot all of these recoveries - TWRP 2830, TWRP 2860, Philz latest recovery. After installing each of them, I can not enter recovery mode again. Flashing a new recovery doesn't seem to change that.
I have access to fastboot, currently I installed the stable fastboot rom version "armani_images_JHCCNBH45.0_4.3_cn_e7e373f319".
I can not get adb to recognize the device, only fastboot. Can't get a logcat because of it. If you think I might be doing it wrong, please walk me through the process.
How do I get it back to working condition? The phone was bought in Bulgaria from a retailer, but I don't know which country it was originally shipped from, only that it's a WCDMA version.

Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .

ford.sushil said:
Throw it away and get your self some reliable phone unlike redmi , it's a crap lots of issue ... I prefer Motorola .
Click to expand...
Click to collapse
Oh oh oh don't be rude everyone has his own priorities and financial limitations

Bootloop
Dude, I have the same problem, can you help plus?

[UNBRICK] Getting into recovery/unbricking V410

I'm posting this just because it might be helpful for others, as well as providing some warning for anyone else who might one day get into the same situation.
I was rooted and had installed TWRP on my new Gpad 7.0 V410 and everything was running just fine. I've been modding Android devices for years and thought I knew what I was doing. I didn't like the AT&T boot animation and thought I'd replace it. I found the stock animation in system/media, and replaced it (with a Nexus 7 ani) just like I'd done on previous devices.
When I rebooted, the animation started and ran. But then it hung, and rebooted. It was now stuck in a bootloop. Well, no problem, I thought, I'll just get back into recovery and restore the stock ani.
That was when I discovered how locked down the firmware is on this device. No fastboot. No standard Android bootloader. Not even, as far as I could tell, anyway of rebooting into recovery using the hardware buttons.
I could get to the factory reset screen and download mode, but neither have any way to get to recovery. ADB could not connect. The LG support tool found it, but did nothing but tell me the firmware was up to date. Lots of searching and reading turned up similar tales of woe. I began to worry that there was no way out.
Having no other ideas, I tried doing a factory reset. It ran, and lo and behold, kicked me into TWRP. From here, I confirmed that the device was wiped.
However! I had had the foresight to create a TWRP backup on my external sdcard, and that was still there. Restoring it got everything back in working order.
The moral: If you're up and running now, make an external backup. It could save your butt just as it did mine.

Amen
I'd just like to add that you can enable fastboot on this tablet for anyone who might read this thread. If you follow the method described here you'll lose download mode, but the tablet will fall back to fastboot when download mode fails. :good:
Without a kdz file released for the V410 the download mode isn't really good for anything, but fastboot gives you a fighting chance of being able to flash your way out of trouble if you brick your V410. Probably advisable to keep a backup of the laf partition just in case you need it someday.

Aha, thanks, I had seen that referenced several times, but wasn't sure where to go with it, and wanted to try less extreme methods before attempting something like that.
I've been spoiled by modding HTC and Nexus devices up to now, so this is a bit of a culture shock over here.
Edit: Decided to bite the bullet in case of future problems and nuked laf. Ah, sweet fastboot. :highfive:

SM-G925F Stuck at factory reset, unable to enter the recovery mode and flash firmware

Hello and sorry if this is the wrong category...
It's my first time making a thread on xda.
I've been looking for an answer for the past 2 hours, but I still have a bricked phone... As the title says, I can't enter the recovery mode anymore. I tried to do a factory reset (when I could enter the recovery mode) and the phone got stuck at erasing. Now I can't enter the recovery mode anymore. I downloaded a new firmware from sammobile for the SM-G925F. The firmware works since I used it on an other phone and everything worked just fine. The problem is, when I open Odin and add the .tar file to AP, it gets stuck at nand write and sometimes on boot.img. The phone isn't showing that it's downloading anything (it has no progress bar). At this point I have no idea what to do...
Some extra info that could be helpful:
The phone was bootlooping when I got to fix it;
I work in a kind of phone repair store where customers bring their phones for hardware and software repair. I do the software;
I've installed new firmwares on multiple phones and I never had something like this... Normally some time with google and xda could help me to find a working way to fix the problem, but as I said... I've been looking for 2 hours and the problem is still here;
I'm not a pro with Android and phones. I just like to learn new things and I'm still learning.
Could it be a hardware problem?

Can you show me your phone's download mode image to see where could be the problem?
Also, make sure you are flashing latest firmware, if you are downgrading it - than you will get such boot errors.

*Update*
I found out what was wrong. The eMMC chip was broken.

Question Soft brick no backup

Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope

check the link
BootLoop not letting me access fastboot
Okay so when I flashed Magisk boot image my device activated boot problems. And when I tried to access recovery mode via adb (from Android Studio), my phone entered a bootloop from which I cannot exit. Vol down + power buttons does not work...
forum.xda-developers.com

I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.

historypm said:
I'm in the same exact boat as you...That guide was absolute trash and I can't find anything.
Click to expand...
Click to collapse
Hold tight, I'm very close to fixing it!
Got everything working except mobile network. As soon as I figure that out, I'll post a fix here

RadixMalum said:
Hi all!
Long story short, I beefed it...
I tried flashing the unofficial twrp and accidentally did format all on spflashtool.
I'm two months in and for the life of me I can't fix my phone... I've even tried to learn how to write a custom OS myself to fix it but I'm definitely not smart enough.
So, here's where I'm at right now:
When I flash the engineering ROM, the phone boots normally and all that seems to work, but flashing the official MIUI causes a bootloop to the stock recovery.
In there, there's the message "NV data is corrupted".
I'm 2 months in now, so I've seen almost all google pages, so yes, I've tried flashing using the official tool, flashed vbmeta with --disable-verity and --disable-verification.
It's my phone and I have the box here, so I have both IMEI numbers which I managed to flash in the engineering ROM, but flashing the normal MIUI somehow deletes the IMEI numbers again.
I can get into fastboot so the bootloader is unlocked, but I can't boot into the system so I can't enable dev options.
please, if you can help I'm more than happy to answer any other questions and being called an idiot :')
help me, XDA, you're my only hope
Click to expand...
Click to collapse
Good evening, sorry for my bad English, but I have the same problem when this happened, I had miui V13.0.7.0 there, I got bootlop, I loaded V12.5.2.0 there and the phone worked everything except the network, try and let me know

You have to download the firmware and paste it into the platform tools folder and click flash all.bat

I have hit a wall

Hello everyone, Merry Christmas!
Although I say that, I bring not so merry news. My OnePlus 7T is bricked and after trying everything I don't know where to go from here. Currently I am stuck at the:
The current image (boot/recovery) has been destroyed​phase of things and all I can do is boot into fastboot, that is it.
How did this all start? All I did was just update the phone to Android 12 with the official OTA update from OnePlus, big mistake. Worst update ever; my adaptive brightness went haywire, the brightness gets stuck at max, I couldn't receive calls, data was completely unresponsive, and the list goes on. So before the obvious downgrade method, I try a few things first:
Cycle airplane mode on/off
Reset network settings
Reset ANR
These worked for a minute on my data then right back to the same issue.
Wipe cache partition... Oh wait I had to find out the hard way Android 12 removed this option....
Wipe the phone
That fixed nothing.
Ok time to downgrade, but this is where things got tricky and I realized that maybe all my issues stemmed from me getting the wrong update from OnePlus? Although I found this out too late.
See my phone model is HD1907 which I already knew at the back of my head, but when it mattered to remember the most, I didn't catch what happened. After my update to A12, my model number changed to HD1901 which is the Indian version, and when I saw it didn't think anything of it at the time but then after all my problems it came back to me, my phone has always HD1907 so maybe this is a compatibility issue.
Anyway since I was going to downgrade anyway I thought to myself, 'since I already wiped everything, maybe I can use this opportunity to try out a ROM for A12 and see if it is just this ****ty OOS causing all these issues,' and so I did. First thing I did was unlock the bootloader, and try get TWRP on my phone. That all went fine, I booted into TWRP, flashed my zip for TWRP, then proceeded to try to boot into the OS... and the rest is history because that is as far as I got. Apparently my boot.img is destroyed and I can't boot back into TWRP anymore either, all I can do is get to fastboot.
So then I tried MSM, it won't detect my phone.... So then I tried flashing my Stock ROM through fastboot, apparently I'm missing a partition and it won't write to a critical partition either....
So where do I go from here...?

Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!

Canbeit said:
Hello I was in the exact same boat as you today same phone, same update issues, same no recovery mode, no os to boot into only greeted with fastboot mode. I have resolved it and I'm back on oos 11 good as new. I did use the msm tool it is tricky for sure at first. A critical step is installing the qualcomm drivers and then rebooting your pc. Get them here
https://androiddatahost.com/nbyn6. Be sure to reboot. It's late and I just got this thing back into working shape so I don't want to write a lot a right now. It's been a few days since this post so... If you are still stuck I will be glad to help out let me know. There is hope!
Click to expand...
Click to collapse
I too had all the symptoms after an update to OOS12, including progressively losing any semblance of booting. not even recovery and the drivers found elsewhere didn't work, and had a different name when installed and would never get detected in the MsmDownloadTool. After installing this one and rebooting, it finally detects it and installs the image of EDL mode.