Database Develop

[Q] Milestone 1 - can't boot after the installation

Hi guys, I'll try to explain my problem:
My Milestone has been running the rom "cm-7.2.4e-umts_sholes" since two years without issues... until a few days ago: aleatory restarts and freezes. Yesterday, I turned it on and was stuck on "M" logo. Several restarts later, it shows the "2ndBoot - Kernel Restart in progress" logo and nothing else.
I tried to reflash the rom and encountered some issues:
Bootloader 90.73, I flashed the vulnerable recovery "vulnerable_recovery_only_RAMDLD90_78.sbf" and enter in recovery stock. When I tried to run the "OpenRecovery_2ndbootOR_v1_2" the OR doesn't start at all. Black screen, restarts and recovery stock again. Only the "OpenRecovery_v1_46_SHOLS_inkl_ext_mmcfix_parted_update" does the trick and starts the OR with red letters. After all the obligatory wipes, applied update from "cm-7.2.4e-umts_sholes" and then reboot system. And the same "M" stuck or "2ndboot" stuck screen. I tried wipes again, but no results.
So, I tried to go back to an earlier version and installed "SHLA_U2_02.02.0_USASHLSPERARLA017.0R_USASHLSPERARLAT_P037_A015_HWp2a_1FF" with RDSLite. It boots up Android BUT the touchscreen not works at all, even with several reboots. Tried to reflash Cyanogenmod from here, but the same issues above listed appears.
I really going crazy with this... Did I make some mistake at any point? Must I reflash the bootloader 90.73 if I found it? (besides all the webs containing all the .sbf's and bootloaders appears to be offline by now).
Any solution/advice you can give me please?
Thanks in advance and sorry my english, isn't my first language.

Custom Recovery issue (XT1068) (Solved)

Hi everyone, I'm having a weird issue since this morning and could not solve it yet, maybe someone can help me.
Basically I tried to dirty flash the new nightly of CM12.1 using TWRP 2.8.6.0 and it got stuck. After rebooting the device I could not get to twrp anymore (strangely) and then I tried to reflash it (two different versions) with no success.
With my device being in this state (without booting into OS and with no recovery access) I had to download the stock 5.0.2 for the XT1068 and flash it using fastboot. It can now boot up normally into stock ROM and restored the stock recovery, but now any custom recovery I flash it does not work. I had two different results on two versions of twrp:
2.8.5.0 - After flashing it and trying to access it the device shows the "unlocked bootloader" screen and then reboots itself and goes to the ROM without even getting into TWRP.
2.8.6.0 - After flashing it and trying to access it the device goes to the "unlocked bootloader" screen and freezes there. I have then to hold the power button for a long time (about 1,5 min) and then the device boots the stock ROM.
Anyone can give any idea of what I can do? I even tried to lock and unlock the bootloader again, flash CWM, flash TWRP and nothing. At least the device is booting, so it is not a urgency, but any help is appreciated!
----------------------------
I got it, a stupid reason for all issues I was having. The issue was with my router, that was set to use a internal firewall which was screwing up a lot of my downloads, and the ROM and TWRP files just got into this issue.
After reconfiguring my router everything worked out, which make me fell stupid for not thinking about this before hahaha, but at least it is fixed
Thanks for everyone who took a time to read this and sorry for any inconvenience!

Encrypted Z3 Compact ignoring boot to recovery/anything but the system rom

Hi all ,
I have a Sony Xperia Z3 Compact with Slimm Rom 1.2 installed. I encrypted my device some time ago and have now a working root and TWRP 3.0.2 installed.
Now I want to flash the new rom version and have to recognize, that my device is ignoring the boot options completely. Meaning easyboot, TWRP Manager boot to recovery / flash something and holding power down or power up during boot are ignored by my phone now (while they worked before)! The device shortly rumbles and shows a green LED, which should go purple for recovery as I remember? After ~2 seconds the green LED disappears and the phone starts to boot into the encryption interface asking me for the password. After entering it boots into Android.
I googled and did not find a solution for my problem. How can I force my Z3 Compact to boot into recovery instead of Encryption Overlay?
It feels like the device gets the 'boot into something special' options, then simply drops them and goes for default
I would hate to wipe everything again just because of this...
Thanks for your time
S3bish

I have the same problem and a workaround for flashing stuff is an app - FlashFire

Flashfire is a working workaround - thank you!!
To fix the resistan android boot you have to completely factory reset and reinstall twrp..
Can be closed

[Q] Possible partition corruption?

Here's the deal, I have a sprout8 device (the Indonesian Nexian Journey One) running stock 6.0 with some xposed mods installed on it. Suddenly the device shuts down and when I try to boot it up it only goes halfway through the bootanimation when it shuts down again. I wasn't too worried as I thought it was just a conflicting system issue and I also thought it was time to re-flash fresh stock 6.0 to freshen up my phone anyway. So I went ahead and did it.
Here's where the problems start to show up, I had a hard time booting to recovery through the power + volume up combination. The phone suddenly shuts down on its own as it boots up. I tried it a few times and finally got to recovery. After that, as I flashed stock 6.0 the phone shut down again. I thought it was an issue with my recovery so I tried wiping everything through fastboot and re-flashed recovery through fastboot aswell. From there I tried again to flash stock 6.0 through recovery and again, the phone shut down. I tried a different ROM thinking it was a ROM issue but still got the same results.
After hours of trying to flash a ROM through recovery (retrying over and over as it suddenly shut down while flashing), I finally got a ROM installed. Then I rebooted my phone, but again it freezes halfway through the bootanimation (literally freezing the bootanimation) and refused to do anything. I took off the battery and booted up the phone countless tries trying to get it to boot up. When it finally booted up, I filled in all the Google startup credentials and finally got started on a fresh stock 6.0. However, I tried to restore my previous application data through Android's application recovery on startup but everytime the device installs a new application it would freeze up and shut down. This happened countless times. Then the phone, once again, shut down and could not start the ROM. It would freeze up on the bootanimation.
Then things started to get weird, when the phone turns on it should show the "Nexian" logo in all its glory before going to bootanimation. But here the screen gets all distorted and shows these weird horizontal (and sometimes vertical) lines. Nothing's wrong with my phone screen so I assume it is a system error. From here on, the phone refused to boot. It just shows the Nexian logo and restarts over and over. The same thing happens even after I re-flashed both my recovery and ROM. I even tried using SP Flash Tool to re-flash stock but still the same results.
Now, the device wouldn't even turn on. But when I connect it using USB to a Windows computer, it still gets detected through device manager as an ordinary MediaTek device.
I'm assuming now that it may be a problem with the /system parition where we install our ROMs in. The partition may be (partially) corrupt. Seeing as the device could still boot the ROM a few hours ago but freezing upon updates to the stated partition.
If you guys have any other ideas/solutions I'm all ears.

Mi5 in mysterious bootloop (unlocked)

Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?

Hi..
I don't know exactly what's wrong with your mi5..coz you're already told that you almost tried everything..but as long the problems just softbrick i think there's nothing wrong to try this way that might be you don't try it before..
What twrp version you're using it currently..?, is it official or zcx twrp..?, if official..just try switch to zcx version first..you can find and download it from here.
After that with zcx twrp tried check and see that your partition system, data and cache are still as Ext4 file system not F2fs or you can try formatting the data partition (caution!!..this will deleting all your internal storage) to make sure everything is clear, then put it again the rom.zip then flash it again the rom but this time just try it using xiaomi.eu rom, you can try this rom
And anyway..what version XiaomiFlash tool you're using it while flashing official fastboot rom..?

Xiaomi eu dont support f2fs,i have tried it myself,the last thing to do if you already haven't do in is to flash the firmware in edl mode(i prefer to try Chinese devolep first),i think that way the phone is fully wiped and than flashed just like it came out of factory,other than good luck

wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Hey guys, I will try your suggestions. In the meantime, I attached the dmesg log - it shows the kernel booting. Maybe you see something. It would be cool, if you can upload a dmesg log as well so I can compare or check if you can see anything.

Further information:
- I am using MiFlash 2016.08.30.0
- Tried it with the alternative ZCX version AND the xiaomi.eu ROM
- Formatted the data partition as well (I could create a backup of it with TWRP)
- still same situation...
- Is there a way to reset partitions or kind of "deep flash" the device?

wolkenjaeger said:
Further information:
- I am using MiFlash 2016.08.30.0
- Tried it with the alternative ZCX version AND the xiaomi.eu ROM
- Formatted the data partition as well (I could create a backup of it with TWRP)
- still same situation...
- Is there a way to reset partitions or kind of "deep flash" the device?
Click to expand...
Click to collapse
Did you try to flash in EDL mode ?

vlatko98 said:
Did you try to flash in EDL mode ?
Click to expand...
Click to collapse
Yes. No luck either. Then I tried to flash (via normal fastboot mode) an old STABLE China MIUI ROM: miui_MI5_V7.3.2.0.MAACNDD_905c2c8100_6.0.zip -> resulted in boot -> black screen. Now I can go into either fastboot nor recovery

wolkenjaeger said:
Yes. No luck either. Then I tried to flash (via normal fastboot mode) an old STABLE China MIUI ROM: miui_MI5_V7.3.2.0.MAACNDD_905c2c8100_6.0.zip -> resulted in boot -> black screen. Now I can go into either fastboot nor recovery
Click to expand...
Click to collapse
Idk what to tell you else than to search miui forum and hope for the best

wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Have you got it fix yet ?

Nope. Next step is to try EDL again.
Gesendet von meinem MI 5s mit Tapatalk

wolkenjaeger said:
Nope. Next step is to try EDL again.
Gesendet von meinem MI 5s mit Tapatalk
Click to expand...
Click to collapse
Hav you got it fixed ??? Even i am facing the same issue.
please do let us know if you have fixed it.
Im using mi5 64gb

Exactly the same problem: " (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...)"
But this has happened after serious damage (car rolled over the phone) and I replaced the screen with new one. So I guess some hardware might be damaged. Flashing ROM's didn't help.
I couldn't find any solution so far

After screen replace , you got it working ?
I can't get into recovery also.
I tried many twrp versions , i can see the twrp screen but then it get stuck and phone restarts to go back to that mi logo bootloop.
I did flashed many Chinese and global ROMs via flashboot and miflash tool but all the same.
I'm so doomed...
My phone has no history of any fall or anything ..
I wonder what happened all of a sudden.
Thanks for the reply

wolkenjaeger said:
Hello everyone,
I don't know what I should do further. My Mi5 is in a bootloop and I almost tried everything. Here is the story:
On a normal day, I took the phone out of my pockets and it was black. So I though, maybe the battery is dead. So back at home I charged the phone and tried to turn it on, however it directly went into a bootloop (Mi logo for a few seconds - black screen - Mi logo - black screen - and so on...). Okay, nothing bad I though, maybe just the firmware got some strange damage. I then tried almost everything:
successfully flashed the Global ROM -> bootloop (tried both, beta and stable)
succesfully flashed the Chinese ROM -> bootloop (tried both, beta and stable)
flashed TWRP recovery and was able to access it and everything on the phone. Restart -> Bootloop
flashed LineageOS via TWRP -> NO BOOTLOOP, but guess what: EDL MODE?!
flashed again the official MIUI (different versions) -> BOOTLOOP
flashed the Chinese MIUI Stable with the LOCK command -> BOOLOOP (but with locked bootloader)
unlocked the phone again with MiUnlock
flashed TWRP recovery again -> tried various things, but unsuccessful.
Now, I found the possibility to download the log from the phone. Attached here.
(I tried various combinations of firmwares and process, but all ended with the same outcome: no startup into Android)
Do you guys have any idea what could be wrong?
Click to expand...
Click to collapse
Okay, have you tried Mi Flash with deep flash cable ? Flash it again with deep flash cable or go to any reseller shop. They have deep flash cable. Ask them to flash it again. It'd cost you upto $10.

I retried yesterday - no success.
I flashed both stable versions: Global and Chinese, but after flashing, I again had the same problem: bootloop. I stop wasting time, until someone knows the problem. I personally think it's a problem with the hardware, as when you see the log, which I posted above (kernel log of TWRP), there are quite a lot of "errors" in it.
Any other idea?

I asked an android expert who worked in mi about it ...
He was almost sure that either battery or the motherboard is faulty.
He thinks the motherboard is of more chance for the issue.

Bummer..... then I have to wait until I get back to Hong Kong to repair (bought it there). Thanks for the update @bilalsmu.

wolkenjaeger said:
Bummer..... then I have to wait until I get back to Hong Kong to repair (bought it there). Thanks for the update @bilalsmu.
Click to expand...
Click to collapse
Your welcome...
Can you just try flashing with mi flash tool with the option 'clean all and lock'
I just tried mine, and now android is loading *fingers crossed*
Will update if it did complete..

Okay, can you tell me which MiFlash version you have been using (and which ROM?)

I am sorry brother.
Android booted up,I could log into my accounts and I left the phone for charge while it was syncing the accounts ..
When I am back after half an hour , bootloop had already started
I used miflashtool 2016 and miui 8.2.1 official global rom