Scared myself - Xiaomi Mi CC9 / Mi 9 Lite Questions & Answers

I got myself stuck in fastboot. When i hold down the power button on the device it goes right back into fastboot. I cannot get the device to show up via adb devices to do a recovery flash. I'm not sure what to do next. The only thing i think im able to do at this point is to use miflash and use the stock fastboot image. Unfortunately, i am having a really hard time finding any download sources for it with a decent download speed. Meanwhile my phone is sitting at the fastboot screen and i cant seem to turn the device off so i am worried about the battery dying. i dunno if it charges on that screen. If someone has a faster mirror to the stock fastboot image, i would be grateful. I swear it seems like the official server has it out for me as the download speed seems to continually go down.. currently at 10 hour wait
Finally got the file and was able to flash it with miflash and im back to normal.. whew. why cant i delete my own post

Related

bootloader screen flahes when powering on

ok i have run into this weird issue with my G1. it was working perfectly fine yesterday. i turned it off and charged it until it was fully charged like i usually do, but when i turned it on the boot loader screen flashed and the phone turned off! this happens whenever i try to turn the phone on. i cant get into recovery becuase the bootloader screen just flashes. when i try to get to the bootloader screen, it starts up fine but then looks for an image and turns off again. this started happening a few days after flashing haykuros spl if that helps. am i bricked or is there a way to fix this? thanks in advanced
edit: i am also usin the latest experimental build from cyanogen although i dont think this is the problem.
edit2: i managed to get my phone to start up, but im afarid to switch it off just incase it starts happening again so im still looking for a solution to this problem.
edit3: ok back to square one, my phone froze after fully booting up, restarted itself and now the problem is back! wow this is annoying.
it sounds like your camera button could be stuck. if you want to test this type reboot recovery into the recovery console and see if it boots into recovery or bootloader.
check and see if your camera button is stuck or partially stuck since you were able to boot it up once at least
Do you have fastboot working? if so, you can grab your nandroid backups from your SD card and flash them.
or go to cyanogens thread, download the recovery and flash the recovery using the fastboot command to install. i believe its
fastboot flash recovery recovery.img
but plz confirm before you do that
EDIT: david means use adb since you cant get into recovery
adb shell reboot recovery
B-man007 said:
Do you have fastboot working? if so, you can grab your nandroid backups from your SD card and flash them.
or go to cyanogens thread, download the recovery and flash the recovery using the fastboot command to install. i believe its
fastboot flash recovery recovery.img
but plz confirm before you do that
EDIT: david means use adb since you cant get into recovery
adb shell reboot recovery
Click to expand...
Click to collapse
he said he got the phone up and running i meant if he wanted to see if it was a software problem he could type reboot recovery into the terminal emulator and see if he got the bootloader screen or the recovery screen.
also i believe the fastboot commands you posted are correct.
ok thanks for the help guys. before reading your posts a left the phone for a few wins powered it on and now mt phone has booted up and it is working. i will try your solutions still though. i am not sure if i have fast boot working. when the bootloader screen flashed i do remeber it saying fastboot so does that mean i have it running?
edit: camera button seems to be fine although i havent tried the rebbot recovery yet though lol because i need my phone an im not sure if i can get it working again.
do you have adb set up
david1171 said:
do you have adb set up
Click to expand...
Click to collapse
yeah, although im using the 1.5 sdk and not the latest 1.6 does that matter?
if you have adb you will need to have the fastboot.exe (which i think is in the tools folder of the sdk) so cd to the sdk tools folder then use
fastboot flash recovery recovery.img
(also have the recovery.img in the tools folder for this)
ok thanks my phone froze so i had to turn it off and now i am back to square 1 again is there anything besides the camera button that could be casuing this?
djosiah said:
ok thanks my phone froze so i had to turn it off and now i am back to square 1 again is there anything besides the camera button that could be casuing this?
Click to expand...
Click to collapse
have you tried the fastboot flash recovery recovery.img command?
david1171 said:
have you tried the fastboot flash recovery recovery.img command?
Click to expand...
Click to collapse
i cant get into fast boot...the screen with 3 androids on skateboards flashes once really quickly and thats it :/
can anyone help me? the camera button seems to be fine and not stuck. is there another factor that could be causing this? i think i might try unrooting then going through all the steps to root it again. or flashing back to the hardspl and see what happens.
update: i managed to get the phone to boot up again so i went into terminal and typed reboot recovery and i got to the recovery screen ok, but when i pressed home + back to restart the phone the bootloader screen flashed again really quickly :/ it also seems like if i leave the phone off for a few hours it will power up fine but when it is turned off i have to wait another few hours til i can switch it back on.
djosiah said:
can anyone help me? the camera button seems to be fine and not stuck. is there another factor that could be causing this? i think i might try unrooting then going through all the steps to root it again. or flashing back to the hardspl and see what happens.
update: i managed to get the phone to boot up again so i went into terminal and typed reboot recovery and i got to the recovery screen ok, but when i pressed home + back to restart the phone the bootloader screen flashed again really quickly :/ it also seems like if i leave the phone off for a few hours it will power up fine but when it is turned off i have to wait another few hours til i can switch it back on.
Click to expand...
Click to collapse
this sounds like a hardware problem instead of a software problem since there is still a recovery screen, if your phone is still under warranty call your provider and see if there is anything they can do about it, and if they send you another one, just unroot the one you have
my phone isnt under warranty so looks like i will either have to put up with or buy myself a new one. thanks for the help.
If your sure your camera button isn't stuck, check your back button. If not, maybe some sweat or water got into it. some type of hardware dmg possibly. If your the do it yourself type of person, theres always this handy dandy notebook, I mean service manual
http://forum.xda-developers.com/showthread.php?t=468673
wilnotdie said:
If your sure your camera button isn't stuck, check your back button. If not, maybe some sweat or water got into it. some type of hardware dmg possibly. If your the do it yourself type of person, theres always this handy dandy notebook, I mean service manual
http://forum.xda-developers.com/showthread.php?t=468673
Click to expand...
Click to collapse
ahh yes that would make sense seeing as the bootloader screen says fastboot so it must be a problem with the back button. never thought of that. thanks for the help.
ok assuming that the back button is the problem, if i were to flash back to the hard spl would this problem go away seeing as fastobot mode only works with the 'special' spl?

Uh-Oh...I NEEED HELP Please :[

so basically, my phone will not turn on anymore...and i have nooo idea what happened!! It was working fine this morning..
not battery issues, didnt drop it on ground or in water, oh and when i plug it in it doesnt even seem to have any reaction of charging whatsoever..
ive been running cyanogenmod 4.2.2
theme: xxmonsterx+plastic (soo sexxy :b)
recovery: cm-recovery 1.4.
anyone have any ideas or suggestions?? anything is appreciated..
or am i DOOOMED. :[
If you can boot into either recovery or SPL, you're not bricked. If you can get into SPL, I'm assuming you have the SDK (or at least Fastboot) configured on your comp.
fastboot flash system system.img
fastboot flash userdata data.img
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
If you're using Linux, make sure you add the "./" in front of "fastboot" on each line.
^ he/she has 2 posts, try this:
Home + Power... do you get your recovery image like usual?
Do you have Cyans ROM still on the root of your SD card, if so, just flash it and reboot.
If you do not have his ROM still on the root, but can get your recovery, d/load the ROM to your computer, connect your SD card to your computer with adapter, move the file to the root, put back in your powered off phone, HOME+POWER and flash the ROM, reboot.
You might need a new battery...or a new phone Also, check the contacts on the phone miniUSB outlet for gunky buildup and the plug on your charger, see if that is gunked up too. may be a bad connection causing your phone to not charge.
So I'm sure this isn't the problem or he/she would have already reported back that they had figured it out. But...
Sometimes while tethered and running heavy traffic while charging if I forget to turn the screen off the battery will run so dead while the phone's still working that it'll die and I get nothing.. no led, no attempt to boot, nothing. I have to let it sit there and charge for about 10 miniutes then it'll boot up just fine, then.. the charging led begins to work again. I know bizzar but it happens.
Edit: I don't know exactly why it does it. The other reason could be that the processor gets too hot and the phone shuts down as a failsafe.
blackknightavalon said:
If you can boot into either recovery or SPL, you're not bricked. If you can get into SPL, I'm assuming you have the SDK (or at least Fastboot) configured on your comp.
If you're using Linux, make sure you add the "./" in front of "fastboot" on each line.
Click to expand...
Click to collapse
no sadly it wont even get up to the the tmobile G1 screeen it just stays black...and the keys dont even try to light up like usuaully..no reaction. :/
sonikamd said:
So I'm sure this isn't the problem or he/she would have already reported back that they had figured it out. But...
Sometimes while tethered and running heavy traffic while charging if I forget to turn the screen off the battery will run so dead while the phone's still working that it'll die and I get nothing.. no led, no attempt to boot, nothing. I have to let it sit there and charge for about 10 miniutes then it'll boot up just fine, then.. the charging led begins to work again. I know bizzar but it happens.
Edit: I don't know exactly why it does it. The other reason could be that the processor gets too hot and the phone shuts down as a failsafe.
Click to expand...
Click to collapse
really good idea thanks but i tried and left it on the charger for almost an hr now and still nothing...
i guess its been officially bricked? :/
This problem happened to be before too. My phone started up and you could only see the backlight. the screen would still stay black. I found out the Problem was the Black flex cable that connets the Mainboard to the LCD. I replaced it and it started working again. Hope that helps your problem..

[Q] RSDlite - can I cancel halfway to fastboot myself?

I'm tring to use RSDlite from a virtualbox vm, but its going really, really slow. I'm some 40 minutes in and its only on step 6 - I don't think it will complete before the battery goes dead.
If I cancel it now and do all the fastboot flashing by hand through my host os, will I screw anything up?
vonwhoopass said:
I'm tring to use RSDlite from a virtualbox vm, but its going really, really slow. I'm some 40 minutes in and its only on step 6 - I don't think it will complete before the battery goes dead.
If I cancel it now and do all the fastboot flashing by hand through my host os, will I screw anything up?
Click to expand...
Click to collapse
its never safe to stop a flashing process. Depending on when you stop it you could royally screw your phone up. Certain files can get corrupted that won't allow you to enter fastboot mode anymore (im not aware of exactly which those are but i think there are many). It shouldn't take that long to flash your phone so im not sure what the problem is. If it has been stuck on the same step forever then maybe it has failed or something. You def don't want your phone battery to go dead because there may be no way to charge it again if there is no bootable rom on there. I believe fastboot may still allow your phone to charge but Im not sure if thats true. I know it didn't used to be able to but i think it may now. Personally, i would stop the rsdlite process before i let the phone battery drain. Then hopefully your phone will fully boot from there and i would charge it to 100% before trying to flash it again.
If my memory is correct then step 6 is the system.img file - the main OS of the phone. It is the big file that will not only take the longest but it is also the one that will fail the easiest as it is so big. On an older XP machine it takes 5 minutes or so to transfer/flash that file.
I have had the process hang during the transfer of the system.img file before. One time I had to reboot my computer and I rebooted the phone. This will leave the phone unable to boot but with enough key presses you can get into fastboot still - I don't recommend this!
When it happened a second time I only rebooted the computer, and not the phone. You can start the flashing process again without restarting the phone unless it has crashed. You should be able to manually flash with fastboot starting with the step that that failed.
I did some googling - it looks like VirtualBox has some problems with USB speed in Windows XP as a guest.
I ended up killing the RSD flash, and doing it by hand, which went way, way faster. I was able to flash the whole thing in the time it took to send the first 2 files, which only adds up to 1.7 meg.
For what its worth, I killed the flash during step 6, which is system, you are correct. I think this may have actually saved me since it had the boot and recovery images already.
edit: and it appears the phones do charge in fastboot. I had more charge when it rebooted after the successful flash than I started with.
Good to hear you got it working. And yes, the phone should (slowly) charge when in fastboot.

Bootloop & empty battery

Hi.
I've been searching for a solution on how to fix my phone for already almost a year now. I didn't even do anything to it, no custom recoveries or OS (wanted to get CM, but at the time it wasn't available on it, not sure if now is).
The problem - the phone is stuck in a bootloop with an empty battery. The battery wasn't empty at the beginning, but it died in the process of trying to make it work, since the only thing I can boot is "fastboot&rescue" mode, in which the phone doesn't charge - how sweet. Now, I've read just about every thread here on how to flash custom (and original) recoveries, all the DLOAD folder versions and everything, and somewhere in between all that I found that it's impossible to flash anything if the battery is low (or totally empty).
The question - how do I charge the battery if it doesn't boot in anything other than fastboot, and when I plug it in the wall it just loops and loops and loops, and doesn't even charge? It's also impossible to turn it off while it's plugged in the charger. WTF, Huawei, really?
Any help appreciated. Cheers,
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
l3Nni said:
Can you Boot into recovery through pressing power + volume+?
You may have to remove the back of your phone and buy a new battery. The disassambling process is pretty simple, but of course you will loose any guarantee..
Click to expand...
Click to collapse
No, can't boot into recovery, only fastboot. If I could, I guess I would've already fixed it, heh.
I actually got it to charge, at least that's what I think. There was a *.bat script somewhere here that was repeatedly doing these two things:
1) fastboot getvar battery-voltage
2) fastboot reboot-bootloader
So, I ran that (while the phone was plugged in my computer and running fastboot mode), and it began looping and looping and looping. Left it like that for the night. Now, in the morning, when I unplugged it and tried to do someting, the red "battery low" LED wasn't glowing/blinking anymore! Since "fastboot getvar battery-voltage" returned an error all the time (remote: command not allowed), I don't exactly know how much power I have in it, but I'll just leave it like that for a day or two now, and then try some of the methods I've already tried before. Got any new ones I could try?
I already removed the back and removed the battery - wanted to see if I can charge it externally, but has a very small connector to connect it to the mother board, and I can't just put it in any external charger - I actually didn't find any external chargers that can charge the battery of this phone, really strange.
About the warranty - don't even care anymore. Somehow I managed to get a small crack on the glass on the back of the phone just a few days after getting it. Screen is not damaged, just the back cover. And, you don't know Latvia, but this is how it goes here. I took it to a repair shop - the one I needed to take my device for warranty repair. However, in Latvia that means it's just an another small repair shop, which just happens to have a contract with the company who sold me the phone (mobile phone operator). So, they take my phone, say they'll do a diagnostic and get back to me. Three weeks pass, and they call me telling that the only thing they can do is replace the motherboard, which is gonna cost me about 250 euros. That, or nothing. I don't agree. That means, if I don't agree to their suggested method of repairing, I have to pay for the diagnostic (about 20 euros).
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Just flashed TWRP 2.8.1.0, it's already getting better. Now when I tried turning it on in recovery mode, it's not just simply bootlooping all the time, but is stuck on the Huawei logo. At least I hope that's better If I try to turn it on normally it just bootloops again. Omg omg omg.
l3Nni said:
Well, good idea, looks like you will get your phone running..
To unbrick your device you need to flash a recovery that matches with the firmware you had been on. So, if you had a B1xx Rom running try flashing TWRP 2.8.1.0 and MyRom 1.2. After that flash the stock emui 2.3 recovery and B133 through dload. If you were on a B6xx Ron flash TWRP 2.8.7.0 and MyRom 3.3, then emui 3.0 Recovery and B621.
When you didn't try this way until now, do it. It should work if the device isn't hardbricked.. I wish you the best.
Click to expand...
Click to collapse
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
edzjins said:
Well, tried everything again. Flashing all those recoveries, nothing, can't get a recovery. Put a dload folder with update.app in it, magic 3 button combo just gives me some more of that good old bootloop. Extracted everything from the update.app, flashed recovery, system and boot with fastboot - all showed success. I got the most excited when it got to flashing system - it was quite big and took quite long, and returned success, so I really hoped that really did something - but no. Downloaded P7 kernel. Tried "fastboot flash:raw boot P7_kernel" ("P7_kernel" is the name of the file). It created a boot image (544985088 bytes), sending 'boot' returned "OKAY [20.622s]", then "writing boot" returned "FAILED (remote: flash write failure)". Is this the thing that's really broken? The boot flash partition? If so - what can I do, if anything?
God I hate this phone. The best is that I only used it for 3 months, and I still have to pay for it for more than a year. It's been in this condition for 7-8 months already. FML.
Click to expand...
Click to collapse
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
SiulGKT said:
Hi, is your bootloader unlocked??? I think you cant write the boot partition if tour p7 is not unlocked, hace you tried flashing stock recovery? Try the b135
Click to expand...
Click to collapse
Hi. Yes, bootloader unlocked, 100% sure. Have tried flashing the stock recovery, no changes. Tried to find the b135 now - I actually failed to find a real, valid download link! All I found were some russian ****up sites, which downloaded some russian ****ing malware! WTF? I'm about to give up on this phone. Just destroy it with all my hate for it. **** this ****ing piece of **** to hell. There is no hope, and **** my life. Whatever.
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Ziolek67 said:
Be patient. I'll give you link soon but give me answers for this questions.
What was yours last valid ROM ?
Dude you can't flash any recovery you want.... It's not simply working between different ROMs.
Second question. Do you unplaged usb cable before flashing ROM by force update (3 buttons) ?
PS
I am not sure but battery isn't charging even fastboot mode or if totally device is off ?
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
edzjins said:
My last valid ROM is the only one I ever had - EMUI, whichever was the latest about a year ago.
After flashing recovery in fastboot mode, I unplugged the cable and pressed the power button and helt it until it turned off. Waited for a minute to see if it doesn't turn on, to make sure it's completely off - just what the instructions say. Then I tried the force update with 3 buttons, cable unplugged. With stock ROM it was still bootlooping, no changes at all, but with TWRP 2.8.1.0 it got stuck at Huawei logo - but no bootloop. Just Huawei logo, nothing else.
Battery is not charging in fastboot mode because that's how it is on all phones. But it's also not charging when it's totally off, because when I plug it in the charger, it automatically tries to turn on, and starts bootlooping. It's impossible to charge it then. However, with the .bat script I guess I have solved the charging problem - at least the red LED doesn't light/flash anymore.
Click to expand...
Click to collapse
Than you probably have EMUI 2.3 ROM version.
Try flashing B135 recovery from here.
Next try to install B135 ROM from this link.
l3Nni said:
Emui 3.0 beta release was at the end of 2014, official B609 in January 2015. It's important what rom you have been on. Trying different ones is just a waste of time..
You may try to extract and flash Bxxx part for part (depends on what rom you were) and then TWRP 2.8.1.0/2.8.7.0.I have no other idea, unfortunately.
It's a stupid question, but did you, when trying to boot into recovery, press volume+ for a longer time?
Click to expand...
Click to collapse
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
edzjins said:
No, it broke down before EMUI 3 came out, then. I guess I had the ROM which was just before EMUI 3.
Usually when trying to boot into recovery I press the volume+, hold it for about 10 seconds, and then press and hold the power button until it starts turning on. Then I hold both of them for some time, then release the power button but keep the volume button pressed. I've tried doing it differently - holding both buttons for longer time, releasing both as soon as it starts turning on, nothing I've tried works.
Click to expand...
Click to collapse
B135 recovery
http://forum.xda-developers.com/ascend-p7/general/trying-to-update-rom-1-2-t3222485
I uploaded it couple days ago...
OK, I left it "charging" for 2 days straight, hoping maybe battery was too low to flash partitions or whatever. Just wanted to make sure the battery is charged enough. I can't check the voltage or the percentage, because "fastboot getvar battery-voltage" always says that it's forbidden, no permissions, whatever.
So, I left it to charge for 2 days, and now I tested all the things you guys have posted here. Carefully, one by one. Every fastboot flash command returned success, but in the end nothing changed. Doesn't matter which recovery and/or boot I flash, it's just stupidly bootlooping all the time. Nada.
Finally, you can buy a defect P7 (with a broken screen or anything like this) for pretty low money on eBay and change the motherboard.
But I could also understand it well if you just throw it out of the window.. You had really bad luck.
Probably i have the same problem..... You solve yours problem with this ?
Nop, didn't solve the bootloop. I managed to get a donor phone for 55eur though, which had a bent body and wasn't functioning well because of that, and the screen was a bit cracked too. So I did a motherboard swap. Worked perfectly, but the battery connector protecting case screw doesn't hold in anymore, so sometimes it just turns off because it loses connection, or something. I tried to fasten it with some duct tape, hoped it'd help, and put a hard case on it - got better, but still fails sometimes.
I try give it back on warranty, i hope thei repair it.
I am in the EXACT same boat as edzjins. I have wasted 4 days of my precocious life trying to flash stuff on a phone with a completely dead battery.
I just doesn't work, period!
The only possible fix is to buy a new battery, replace the old one, and after the new battery is installed, have all of the flashing software ready to go and fired up before the new battery dies, too!
Its a time game.
Just like edzjins, there was a brief period of time when I thought I could stop the bootloop via TWRP recovery, but was unable to and the battery completely died.
Be wary of trying to flash "EdXposed" framework with TWRP. Instead, flash it only through Magisk.
I have learned the hard way : (

EMERGANCY Issue with flashing a new ROM

Hallo, yesterday my phone kinda got laggy so i thought to my self hmm why not flash a new firmware. Aftewards i said to my self, why not go even further and flash lingeageos 16 and thats when it starts going down. The phone would crash or black screen (volume and power key still work and show their UI on the screen) while the rest of the screen was black. I panicked and quickly wiped everything system,internal storage and all that via TWRP recovery. Now i face a even bigger problem. I cant flash anything onto my phone. The Flashtool requires some drives which i installed as the program instructed but with no great result. I put the device in flash mode by holding volume up key and putting the usb cable into the phone and still nothing i can do. I tried various tools to convert the FTF firmware into zip so i can flash it with TWRP that luckily still works. If i try to flash anything i get the error: 7 or bootloop/stock on loading screen. What should i do?
UPDATE: I flashed a stock rom via newflasher, so for anyone in situation like me, where they phone is a very essential part of they everyday life and everyday responsibilties. Then i recoomend this guid for you, it says everything you need to know when you are in a situation where nothing works: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/

Categories

Resources