Hello,
I'm facing a bit of a weird situation with my K20 Pro. I just went to update it after a long time ( unlocked bootloader, TWRP and custom rom Revolution X). At the moment of installing, it was usually going to TWRP and rebooting and all good, this time, no. Just black screen. And since then, it's stuck in bootloop, and whenever i try to access recovery mode it just crashes. I tried to reinstall twrp trough fastboot but the same is hapenning.
I tried to flash the OEM OS too trough miflash but after 0s is says '' success '' but as you could guess it : nothing.
I already had others soft bricks on other phones but nothing like this, if anyone has a guess ?
Update : Could access TWRP for the first time after trying again to flash the official rom
+ now says that no OS is installed (
Related
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?
Hi !
Before tonight, i was on a lineageOS 7.1 and i tried to flash the stock Oreo android that i downloaded on google websites. My bootloader was unlocked, so i just used fastboot and flashed all. I had TWRP installed.
It worked. Then i had the stock 8.0.0 with no TWRP anymore ( and i forgot to re-flash it ). Then, i dunno what passed in my head, after the first reboot, i decided to **lock my bootloader**.
And now i'm in a bootloop on the vendor image ("Google"), with a LOCKED bootloader ( so no fastboot anymore ) and i cant do anything. I forgot to go to paramters and allow the bootloader to be unlocked before rebooting...
The only access i got is via adb in the stock recovery mode, but i'm not enough aware of wath i could do with that. I tried abd sideload with the same .zip, but it didnt worked. I get stuck on the same Error when the phone tries to verify the conformity of the flash.
So :
1° Cant use fastboot to take me out of here because bootloader's locked.
2° No TWRP anymore, only the stock android recovery.
3° Bootloop so i cant launch the device.
4° My only in is adb fastboot.
5° My build number is OPR6.170623.013
What do you think i could / should do to take me out of here ? I'm taking anything that allows me to boot the phone.... For what i saw, i'm kinda thinking it's bricked, but i still got hope. I'm comming to you because i'm desperate
Thanks for your advices.
useful threads
that nobody ever bother checking out
Very usefull post. Thank you very much. I'm still stuck but i've posted there so i'll hope someone will come.
This post can be closed
Long story short, I ended up with a classic bootloop (shows boot animation continuously) from messing around with Magisk modules, so I did a wipe from recovery, still bootloop, so I tried reverting completely to stock with the OEM downloads. I tried flash_all_except_storage.bat, and flash_all.bat, but this time it was a different bootloop. The phone shows the Android One logo, the screen flickers like it's going to the boot animation, but then it just goes back to the Unlocked Bootloader Warning Screen, then the Android One logo, and loops like that. I dumbly thought locking the bootloader, reflashing everything, and starting over like it were a new phone would fix the issue, so I did flash_all_lock.bat, but now I'm just stuck with this weird bootloop and a locked bootloader. Trying to unlock the bootloader with fastboot just gives me "oem unlock is not allowed", so I'm at a loss here.
Does anyone know of anything else I could do, or is this a hard brick?
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
thorin0815 said:
With a locked bootloader EDL flash probably is your last chance.
Maybe this thread helps:
https://forum.xda-developers.com/mi-a2-lite/help/hard-bricked-mi-a2-lite-help-to-enter-t3862648
Click to expand...
Click to collapse
I got stuck with a similar problem and that was the only option, to boot into EDL mode you will need to partially dissasemble your device and flash the image via fastboot or via MiFlash (download the latest version as I had problems with an older one). Since that incident I kept the bootloader unlocked just in case something happens.
I had the phone booted into EDL mode and attempted to flash the stock ROM (10.0.3.0) with MiFlash, but it errored out with an ERROR_UNSUPPORTED_TYPE. I tried with the previous version, 10.0.2.0 and it worked for some reason. That fixed it though, so thanks! I've been lightly tinkering with rooting android phones a few years now, but until encountering this issue, I'd never heard of EDL mode. You learn something new every day? ?
I have the same issue with my nephew 's mi a2 lite which has the bootloader locked.
It only shows the android one logo.
I cannot go to recovery mode, but I can go in fastboot.
Changing from "a" to "b" doesn't solve anything and being the bootloader locked is not possible to flash anything from fastboot.
So I've opened the device and I've short circuited the edl pinpoint to be able to flash with MiTool (I've used an old version since more recent ones gave errors when flashing).
I was able to flash both the latest official ROM and the oldest one which I've found ( daisy_global_images_V11.0.14.0.QDLMIXM_10.0 and daisy_global_images_V9.6.4.0.ODLMIFF_8.1 respectively).
In both cases the device still is "frozen" with the android one logo when I've tried to turn it on after the flashing procedures gave me a successful status.
What else can I do?
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
I have a weird situation going on with my phone
My phone is Chinese Pack and I had Xiaomi Eu MIUI 12 previously
I tried flashing MIUI 11 Stable China rom on it using TWRP
when I installed the rom, TWRP didn't get deleted and my phone started to bootloop, so I flashed magisk and the bootloop was gone and I could boot my device after flashing magisk.
Now I want to sell my phone and I'm trying to flash everything back to normal, get rid off TWRP and Magisk and lock the bootloader as well using MiFlash
the phone is running on V11.0.5.0.PCACNXM and I'm trying to flash the same rom using MiFlash and lock bootloader, but at first, it says device mismatch
and when I delete the first 2 lines of flash_all_lock.bat which causes this problem, something else happen
check the attached image
when I press the flash button, this screen comes up and nothing changes except the timer that goes up, and when I remove the phone cable, the phone boots normally without any problem, practically, MiFlash doesn't change a thing
any solution that can help me unlock Bootloader, remove Twrp and Magisk?
Already tried different versions of MiFlash and an app called XiaomiADBFastbootTools.jar, nothing again
P.S: while flashing with XiaomiADBFastbootTools.jar, I get the same message but after removing the cable, the error changes to "current device anti-rollback version is greater than this package", which is nonsense because I have the same ROM on phone already.