Hello guys...
I need a help. First, I will not gonna blame anyone for spreading the beta/alpha ROM links here.
I believe that many of Mi3w users are very exciting to hear that their device will get an upgrade. And I, one of them who want to be the first to taste Android M on Mi3, officially with MIUI.
The problem is, when updating from 6.1.12 to 6.1.21, suddenly my Mi3w experiencing short bootloop. Normally, boot process will display android text below MI.com, this short bootloop only display MI.com for about 2 seconds and after that, my device turn off, and on again with the same symptom. This process will drain battery very-very fast.
I tried several times to flash fastboot (yes, I still can access the fastboot via vol down + power), at the end of the process, the bootloop happens again and again.
If I kind of lucky, I can access recovery. I tried also to wipe all data, after I reboot, the bootloop happens again and again.
I have search the MIUI forum and found that many, not only me, experiencing the same. Is it possible that this is an error, a weakness, faulty the Mi3 devices have? If so, it was so shameful since Mi3 is one of their flagship.
Oh, anyway... Is there anybody here who can help me fix this problem?
Same for me. Flashed twrp via fastboot and installed ivans 6.0 for now because of the new partition table. Waiting for fix.
Related
Hi, this is my first post. I have tried to search and look through the question threads, but nothing seems to be close to the problem I have here, hoping someone can help me.
I have this Xperia TX, recently given by my friend, it can boot up ->sony->ribbon-> entering system->shutting down, it's not like a sudden blackout but more like a command sent telling the phone to shut down, it has the window saying shutting down and vibration at the end, but the shutting down is instant, can't operate yet. I made several approaches trying to fix it, these are what I have been done with it.
-Flashing different stock ROMs using flashtool, the flashing went perfectly without errors, and phone will boot and install new system until the setup wizard (languages, time etc) comes out on screen, and it shuts down right away.
-I used flashtool to unlock BL, succeeded.
-I flashed TWRP, it can boot into TWRP without any problems and working fine.
-I formatted the phone partitions using TWRP, working fine.
-I flashed cm-12.1-20151010, and same thing happened as soon as the system launcher comes out.
-And I flashed stock ROM again, the problem remains.
The phone won't charge the battery, so I tried using a separate charger avoiding 0 battery situation (I do see the battery icon showing 50%+ when it shutting down), and I also tried another lt18i battery (don't want to buy a new one yet in case the phone is dying), and there is no different.
I don't understand the problem, all the operations work fine but can't boot in system, doesn't seem like a hardware thing but what else can it be? I am not hoping to fix it any more at this point, but can anyone tell me what could possibly cause this? Can I read a boot up log somewhere so that I know what happens during booting?
I hope I didn't break any routine or do anything wrong here, if I did, apologies in advance, thank you.
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
try to flash official twrp recovery via fastboot
Rahuljs said:
try to flash official twrp recovery via fastboot
Click to expand...
Click to collapse
How to flash it ?? Method pls...
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Try flashing the phone via MIUI flashing tool as you were able to access fastboot mode
http://en.miui.com/a-234.html
xypherize said:
Hello everyone. Well, as per the title, after I flashed a new custom ROM (Ivan's AOSP to be specific), my Mi3 refused to boot properly and get stuck in the bootloop at the Mi logo and it would bootloop again and again and again....
Now, if I tried to enter twrp recovery by holding power button + volume up, it would refuse to boot into recovery and just bootloop again. But, I was able to access fastboot mode (don't know why but I could easily boot into fastboot mode)
I downloaded stock ROM for Mi3 and tried to flash it via MiFlash and it succeeded but the device would still bootloop. I also attempted to flash twrp recovery via flashboot and it succeeded, again, but my phone would refuse to at least boot into twrp recovery mode, again. Naturally my phone still had the bootloop at the Mi logo, sigh.
I don't know what to do anymore, aside from sending my phone to repair center that might charge a fortune. Please help!
Click to expand...
Click to collapse
Here is the link for tutorial for flashing recovery via fastboot mode. All commands are same just download the twrp recovery image from here. DON'T FORGET TO RENAME THE IMAGE FILE, BECAUSE ADB DOESN'T RECOGNISE ANY SPECIAL CHARACTER.
what did you do ? I'm stuck in the same situation word by word.
did you solve this issue ?
yohaneseko said:
Many users confirmed the same symptoms. Is it possible that the damage caused by "software" since some people of India have visited the service center and asked to replace the motherboard of which cost $150?
Click to expand...
Click to collapse
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
rxl.noir said:
Seems like the problem is caused either because of this, or your battery's PCB simply fried because of unknown reason, maybe because faulty charger/cable or wrong charge voltage setting by the kernel? Also, seems like most of the similiar case stems from MM roms, including MIUI's own chinese developer ROM.
Some people with the exact same case stated that after replacing the battery, the device worked again, like this guy on iFixit: https://www.ifixit.com/Guide/Xiaomi+Mi+3+Battery+Replacement/50785
I haven't tested it yet on my bricked device (just ordered the battery today), but I really hope it was just the battery. I think fried mobo is kinda unthinkable, since if the mobo got fried, you probably can't even flash anything since the eMMC would probably also inaccessible.
Click to expand...
Click to collapse
yohaneseko said:
Hi @rxl.noir, urang Bandung?
How much does it cost for battery replacement? I have sent my Mi3 to the seller because it's not even one year already.
Click to expand...
Click to collapse
Heyaa~
For the battery, you could easily found it on Tokopedia started from 110k, although most of them are shipped from Jakarta. The replacement process is quite easy, you might only need #0 Phillips or any small plus screwdriver, a plastic card (for spudge replacement), and some guts :q. The details and steps are on my prev. post.
I haven't tried to sent it to the seller/distributor, since it might take a long time to get it done.
Just a little update;
I replaced my battery on my Mi3 that have the same exact case as yours, and it finally works. No more short bootloop, no more stuck in fastboot.
hi
my mi3 was on miui 8.1 stable last day the phone switched off and it short bootloops on the Mi logo.
it only goes into fastboot mode and i tried to flash roms via that and it dosent work.
it goes back to bootloop again.
i even tried shortcircuting the motherboard and trying to flash ROM because i thought it was hard bricked and had no success
can anyone tell me what to do or replace ?
ive heard its either eMMC or battery
thanks
https://forum.xda-developers.com/xiaomi-mi-3/help/mi3-bootloop-stays-fastboot-modus-t3656560
kingnikpic said:
hi
my mi3 was on miui 8.1 stable last day the phone switched off and it short bootloops on the Mi logo.
it only goes into fastboot mode and i tried to flash roms via that and it dosent work.
it goes back to bootloop again.
i even tried shortcircuting the motherboard and trying to flash ROM because i thought it was hard bricked and had no success
can anyone tell me what to do or replace ?
ive heard its either eMMC or battery
thanks
Click to expand...
Click to collapse
Persistant and continuous bootloops is normally a result of the battery being at the end of it's life - I would seriously recommend replacing the battery. Fortunately batteries for this device are fairly inexpensive, and like always, when troubleshooting issues - always start with replacing the least expensive components that are likely the cause to your issue.
I too had to replace the battery in my Xiaomi Mi 3W due to continous boot loops, they would only occur when attempting to do anything CPU intensive, and likewise, my device would remain on in recovery and fastboot without a problem. Anyhow, replacing the battery cleared my symptoms instantly.
Don't waste your time/money with eBay batteries. The best battery I've found, that is much alike the original is the Nohon Battery... This can be purchased at aliexpress for a good price: https://www.aliexpress.com/item/Ori...32677903782.html?spm=a2g0s.9042311.0.0.YHewuy
Best Regards,
Stickman89
ok so i used this toolkit for the MI A2 from this thread:
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585][Tool]
to unlock the bootloader, root the phone and enable camera2 API. And i had a little bit of issues with that as well but i got it working.
Now that was a few weeks ago and last night i accidentally slept in while watching videos on the phone without the phone plugged to the wall. So it drained and as i woke up i plugged it in and tried to turn it on but it was stuck on the boot screen (NOT bootloop, just stuck at android one screen) so i tried to fix the phone with the toolkit but then i suddenly got in bootloop (that problem i had the last time) so i tried to fix it the same time as last time. Said "last time problem" was that while trying to go into TWRP i got stuck on partition B (in my case normally the empty one) which resulted in a bootloop and i also couldn't access fastboot. It would always bootloop, so i tried to let it drain and then plug it in and immediately go into fastboot which seem to work and there i could change the partition back to A.
This time i thought it may be a similar problem and tried to solve it but i failed now i cant flash any partition (will add screenshot with prompt from toolkit), both of the partitions are bootlooping, i can still enter fastboot (now anytime i want to) and with the toolkit i can still access TWRP where i also tried to wipe cache (didnt't help) restore the phone (same) or wipe all the data and all resulted in failure. now im kind of lost at this prompt of the toolkit and my amateur guess is that my last resort may be the EDL mode but i dont know much about it and therefore i seek out for help
Best Regards
NicoLogics
https://imgur.com/a/IKsvM4F
NEVERMIND, the phone started now as factory restored BUT i can't do anything really because i always get the prompt "Google-Framework-Services repeatedly stopps working" (my phone is in an other language so i translated it roughly). what should i do next? i dont want to mess this up more.
Edit:
Also i am currently on slot/partition B
You're probably trying to install a downgraded version, I highly doubt Mi A2 toolkit has been updated with the latest stock rom, you're better off downloading the stock rom from here and using the flash_all.bat file to do it.
Yepi69 said:
You're probably trying to install a downgraded version, I highly doubt Mi A2 toolkit has been updated with the latest stock rom, you're better off downloading the stock rom from here and using the flash_all.bat file to do it.
Click to expand...
Click to collapse
how would i have to do that? im not fimiliar with the flash_all.bat
would this explain the toolkit prompt?
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.