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?

Bricked Redmi 1s - what is left to try?

Hello XDA, it's my first post here, and I'm looking for your help. I wanted to upgrade my father's Redmi 1s from MIUI 5 to MIUI 7. During the process of upgrading through Updater on phone it got stuck on 98%. After some googling, it turned out to be a pretty common problem. I tried to follow this ...thread-126225-1-1..(on en.miui). And after step 8, when it should boot me to TWRP I guess, I get booted to normal recovery from where I can't do anything.
Next I tried to flash MIUI 7 through fastboot ...a-234... (on en.miui). Following this I get error in MiFlash "unspecified error 0xffffff01". I think it's because I haven't enabled USB debugging prior to trying the flashing.
I have no idea what to try next, since this is my first time trying something similiar and I have already failed heheh..

You can fix yo device by 2 ways.
First is flash TWRP and flash the recovery rom for redmi 1s
second is flash fastboot zip in fastboot by cmd or MIFlash.
First method will not delete your data and second method will wipe.
Try searching in these forums you will get the steps for both the methods.
Thank You
-TechExhibeo

I have tried both ways. I posted part of links (because I don't have 10 posts yet) for guides I tried to follow.

5arg said:
I have tried both ways. I posted part of links (because I don't have 10 posts yet) for guides I tried to follow.
Click to expand...
Click to collapse
It seems that you haven't flashed twrp recovery. Try flashing it again through fastboot and install the miui recovery rom.

Nexus 7 stuck on Google logo and unable to access TWRP

I am new to XDA. I flashed my Nexus 7 with Lineage OS 16 using TWRP. It was working perfectly. Since I didn't require it for my daily use, I didn't use it for about 4 months. I took it out two days ago and started it up. It started fine but its touch was not responding. It is not the first time that this has happened and usually the touch starts working after a few hours or a day. But this time it was taking too long. So I decided to factory reset it (from Lineage settings). But after restarting, it is stuck on the Google logo.
I cannot even access TWRP recovery. Using the key combination (Power+VolumeUp+VolumeDown) just restarts the device.
Any ideas?

C Karthik said:
I am new to XDA. I flashed my Nexus 7 with Lineage OS 16 using TWRP. It was working perfectly. Since I didn't require it for my daily use, I didn't use it for about 4 months. I took it out two days ago and started it up. It started fine but its touch was not responding. It is not the first time that this has happened and usually the touch starts working after a few hours or a day. But this time it was taking too long. So I decided to factory reset it (from Lineage settings). But after restarting, it is stuck on the Google logo.
I cannot even access TWRP recovery. Using the key combination (Power+VolumeUp+VolumeDown) just restarts the device.
Any ideas?
Click to expand...
Click to collapse
Yes:
#1 to enter TWRP recovery use Power+VolumeUp, not Power+VolumeUp+VolumeDown
-- alternatively do Power+VolumeDown and then select "Recovery"
#2 to fix touch issues check this post
#3 for any other issue do a more complete factory reset with RESTOCK first
:fingers-crossed:

k23m said:
Yes:
#1 to enter TWRP recovery use Power+VolumeUp, not Power+VolumeUp+VolumeDown
-- alternatively do Power+VolumeDown and then select "Recovery"
#2 to fix touch issues check this post
#3 for any other issue do a more complete factory reset with RESTOCK first
:fingers-crossed:
Click to expand...
Click to collapse
Well I have tried all key combinations ,it just restarts.

My tab is nexus 7 2013 flo. Recently I tried to flash new custom rom., I am using Havoc A11 and wish to change LOS 18.1 official. I tried to flashTwrp 3.5.1. I have done using fastboot boot twrp 3.5.1.img. Process was normal. After flashing I tried to get into recovery. The tablet landed in google logo. I tried all possibl ways to see whether tablet to reboot to bootloader but failed dall my attempts. I am unable to recover my tablet. I seek the help, direction and suggetion of forum to solve this problem.

Raja M Reddy said:
The tablet landed in google logo. I tried all possibl ways to see whether tablet to reboot to bootloader but failed
Click to expand...
Click to collapse
Now the screen is blank, device appears dead and you can not boot in fastboot mode anymore - correct?
If no, boot in fastboot mode and flash an older version of TWRP, eg 3.5.0 or 3.3.1
If yes, connect it to PC and check for a new USB device. If you see Qualcomm HS-USB 9008 - VID_05C6&PID_9008, try Nexus 7 2013 Unbricking Guide

NERVOUS about flashing Lineage 18 :-(

HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler

Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom

Tsuragi said:
Something similar happened to me, it turns out that from android 10 stock you have to first:
fastboot flash recovery xxxx.img
you will get an error in the cmd, that's good, now
fasboot boot xxxx.img
.
this was mentioned a long time ago but was never mentioned more in other threads
if you get stuck you can use ost la. also remember the slot A B when you flash the rom
Click to expand...
Click to collapse
Thanks Tsuragi,
Forgot about that - it was me who posted that solution some time ago duh!
Pootler

pootler said:
HI,
I am not new to flashing phones and tablets, but I am a bit confused about the new partition format.
I have a nokia 6.1.
I want to flash the official lineage 18 ROM on it.
I downloaded the latest version , and also the latest lineage recovery.
I followed the install instructions on the website . I believe, exactly.
But after I have executed this command '' fastboot flash boot xxxxx.img"" to temporarily boot recovery, the phone stays in download mode and does nothing.
I then thought maybe I need to reboot?, and power down, because the next thing on the lineage install instructions is to start the phone having powered down.
Anyways, when it boots up, it hangs and stays on the android one screen.
Power/Volume up does nothing.
Whats worse is, it is no longer recognised in ADB.
I was really worried. I let the battery die overnight, and then tried to get some response, but no - still stuck.
Finally, after more fiddling, I got it into download mode, and was able to flash stock using OST.
I tried again - same thing, and once again luckily managed after an hour or so to get it into download mode.
So I have reflashed stock, and wondering if somebody a lot brighter than me can give some advice??
Currently on stock android 10, but would much prefer lineage 18 , as I have no need for google services.
Can only think something is going wrong with whichever partition I am temporarily booting to recovery?
Many Thanks ( with a relieved sigh for escaping a brick )
pootler
Click to expand...
Click to collapse
Hey bro same experience, thats why im stock in android 10 with unlock bootloader. but i successfully flashed lineage with unofficial twrp but the problem is i cant flashed gapps thats why i cant install pre apps and cant use the default message and call. please help me

[Solved]Requesting Help Regarding Mi A2 Lite (Stuck in Unlocked Boot loop, No OS installed)

Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
Your browser is not able to display this video.
Any form of response and acknowledgements will be much appreciated )

@hachi_eight
Please read the guidances that are stuck on top of every forum prior to your next posting like
Note: Questions go in Q&A Forum
If you are posting a Question Thread post it in the Q&A forum. Technical discussion of Android development and hacking. No noobs, please. Device-specific releases should go under the appropriate device forum...
forum.xda-developers.com
I've moved the thread to Q&A.
Regards
Oswald Boelcke
Senior Moderator

hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Hey brother, I had the same situation a few months ago. My device - Redmi 6 (Cereus).
So, I was trying to install TWRP in Redmi 6 and then after trying many times TWRP successfully got installed. But when I tried to boot the device, It stuck in bootloop (Going to fastboot and again booting...). So, the answer is that you first boot into fastboot mode of your device and then download the fastboot Rom of your device, (link of fastboot rom of your device - https://xiaomifirmware.com/download/18010/ ) . Then go to your PC and then extrac
the fastboot file, then connect your phone to pc and go to fastboot mode then open the extracted folder and then click on flash-all (The batch file) and then a new command window will open automatically and flashing process will start. After it's done your phone will reboot automatically. For reference, go ahead. Best of luck!

hachi_eight said:
Just this day, November 23, 2021, I have been trying to flash a custom rom named Syberia OS for daisy(Mi A2 Lite variant). As I have done booting up the device to fastboot(thru cmd command since my power button is jammed), I installed the twrp after booting the image to the device, making it as my recovery.
Now I am set and excited to install the rom, so I went to fastboot again and tried to flash the rom, but it always errors and not installing the rom. It is said "to flash multiple zips, reboot recovery before..." (correct me if I'm wrong), so I rebooted to recovery thru the twrp (since its in fastboot). Now, I did the same, I installed the rom again and experienced the same error so I dont know what to do, I did wiped system, data, dalvik and internal storage (a lot of times and tried to install the rom again), but I get the same error.
Then since I cant install the rom, I went to reboot to system thru twrp, and then I forgot, that I have no OS installed.
So now I'm stuck with the "Your device software can't be checked for corruption. Please lock the bootloader. Please visit this link..." plus arriving to the AndroidOne logo, and it turns off and turns on again with the message and logo, repeats until the battery is completely empty.
Is there anything I could do to go to fastboot again for a clean install of the stock rom? (I promise to not unlock the bootloader and experiment on custom roms again)
(I am sorry if you find it hard to understand, I am willing to edit this thread for better understanding if there are things you dont understand.)
This is what I see after all that happened...:
View attachment 5466081
Any form of response and acknowledgements will be much appreciated )
Click to expand...
Click to collapse
Check in the guides section for mi a2 lite. Do a little search before asking. This one

user-001 said:
Check in the guides section for mi a2 lite. Do a little search before asking. This one
Click to expand...
Click to collapse
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!

hachi_eight said:
i fixed it, i opened the back of the phone and managed to fix the power button, and used the combo to get to fastboot mode, and reinstalled the stock OS. so, now I fixed it!
Click to expand...
Click to collapse
I am having same issue. What did you do fix the power button?