Bricked? Solutions? - Redmi Note 8 Questions & Answers

Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.

Maybe try flashing a custom rom

With what tools if I may ask? Any advice you can give me?
Fastboot doesn't stay on like it should, the screen just flashes the fastboot picture and it restarts again. Recovery does the same.

Try following bliss rom guide with installation of twrp

Trying to do anything with ADB tools just gives me a "< waiting for any device >".

I'm sure there's other ways of flashing twrp

VirusWar said:
Hello.
Tried flashing older stock rom via TWRP.
TWRP installed fine, worked fine, flashed vbmeta, still everything worked.
Downloaded ROM, put it into the sd card, went into twrp, formatted data, rebooted into twrp again, wiped Dalvik/ART cache, cache, system, vendor and internal memory, tried flashing, gave error 7, with "mkdir folder file not existing or whatever". In twrp i went into terminal, made a directory /cache/recovery, tried flashing, worked. Wiped dalvik and when i tried to reboot, the backlight turns on for a split moment and then it turns off.
Recovery does the same, and fastboot lights up the screen with the image of fastboot but it turns off. Plugging it with the usb makes it so it repeatedly turn on backlight and off again.
What does this mean? Device dead? Any help?
Thank you.
Click to expand...
Click to collapse
i think it's dead
-when the twrp gave you the error you should log it
-you should format data after flashing a rom ,not before (and only few roms require it)
your only option is flash VBMETA then TWRP again and see if it work
use the unofficial twrp : (3.3.10)
https://forum.xda-developers.com/re...ecovery-unofficial-twrp-xiaomi-redmi-t3997267

You should have formatted data partition after flashing the rom(not manually create those folders). You would be okay.

Any solution?

Related

recovery loop problem

I now cannot get into an operating system. The device loads FFF 1.4a says "booting" goes blank for a little while then comes back to the 1.4a screen and says "booting" again and loads up TWRP. This is how I got to this point:
I recently decided to go from an older CM7 rom to a new jb one.
Because I had an older version of FFF and had a CWM recovery, I downloaded the new version of FFF (1.4a) and the newest version of TWRP (2.2.0) (flashable zip file) as well as the new jellybean rom and jb gapps. I checked all md5s prior to doing anything.
I booted into recovery and created a backup in CWM. I then cleared cache and Davlic cache and installed FFF 1.4a. I then rebooted to CM7. After loading CM7, I rebooted into recovery, cleared cache and davlic cache and installed TWRP 2.2.0. I then rebooted into CM7, rebooted into recovery. I then cleared cache, davlic cache, factory reset, and wiped system. I then installed CM10 and jb gapps and attempted to reboot to system, but have not ever been able to get there.
I have tried installing the CM7 rom I had before, no difference, CM9 rom, no difference. I tried to use a recovery file I had, still no good.
Adb does not seem to behaving properly as well. I can't seem to be able to get the device into fastboot mode for one. In TWRP I can see the device as the following:
4B8E000600000001 recovery
when I try to change the bootmode, this is how it behaves:
adb shell
~ # <-[6n idme bootmode 4002
/sbin/sh: idme: not found
KFU also seems to not be much help at changing the bootmode. I have tried older version as sited elsewhere (0.9, 0.3), but these fair no better.
Also, In my haste and desire to get this working I thought,"maybe there is some conflict with the sd card", so I wiped that only to realize while wiping that I never backed up my recovery files, "doh!".
Also, I have full battery.
I am a noob, so I could have done anything wrong. Any help would be appreciated.
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Thanks
Thepooch said:
When you get to the bootloader screen select boot normal in the boot menu by quickly depressing your power button a few times if it does not boot normal then flash the bootloader again in recovery http://forum.xda-developers.com/showthread.php?t=1632375 also you will have to mount your sdcard in twrp to do so make sure there are no checks in the boxes of system and data then mount transfer 1.4a bootloader a new ROM and gapps then unmount flash bootloader reboot it get back to twrp wipe factory reset wipe cache wipe dalvik wipe system flash ROM flash gapps select reboot if prompted select system see where your at after that
Click to expand...
Click to collapse
Thanks, I will try this when I get a chance.
Thanks
kinfauns said:
http://forum.xda-developers.com/showpost.php?p=29186989&postcount=157
Click to expand...
Click to collapse
Thanks for this as well, did not see this information anywhere else.
fixed
Yep, it was a bad FFF flash. All good now. Thanks for the help.

Cannot load image fastboot

I've recently tried to update my radio and bootloader to the latest versions, i was on a custom rom (7.1.1), I've updated the bootloader and radio via fastboot and wiped the cache then rebooted then my phone was stuck in a never ending boot and all is saw was the boot animation, i decided to reboot the phone so i held the power button until it restarted and to avail, the same thing happened. I rebooted to twrp and tried to wipe the cache and dalvik/ART cache and i got an error that it cannot be mounted and the partition size was at 0mb and twrp could not repair it either, and it could not format any of my partitions, so i tried to return to stock and i tried to flash the images from the stock .zip provided by google and it said that it could not load any images. I can access download mode and twrp, any solutions? (someone said to flash the vendor image after flashing both the radio and bootloader images? could that have cause my problem because it did not flash it?
i was on the latest vendor already)
thanks.
EDIT: after continuously trying to wipe the cache & dalvik/ART cache in twrp it worked and it recognized the partitions and it wiped and my device was able to boot, i'm not sure what caused the problem but it boots properly now, although i'm not sure if i can flash in fastboot again, otherwise it works.

TWRP Can't Mount /System - OP3 Bricks When Trying to Flash New ROM??

I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.

Redmi note 8 (ginkgo) When booting LineageOS reboots to recovery

Hello all.
The phone had an older unofficial LOS build installed (lineage-17.1-20200808-UNOFFICIAL-ginkgo.zip) but Bluetooth wasn't working.
I tried to install "lineage-17.1-20210927-nightly-ginkgo-signed.zip" via TWRP: I formatted DATA, then did a standard wipe, then installed via zip file on physical 64GB SD Card. But after rebooting I see the LOS animation for about 3.5 minutes then the phone reboots back to TWRP.
I installed official MUI (miui_GINKGOGlobal_V12.0.6.0.QCOMIXM_cfcf7038bd_10.0.zip) just to see if it will work and it booted without problems (and BT is working).
I tried LOS again, still doesn't work. I tried wiping EVERYTHING, including system, still the same. I tried with the LineageOS recovery - still the same but this time when it gets me back to recovery I get a message saying it failed and asking to try format DATA. I agree and let it do the format but still the same result.
I don't know what else to do and I need a phone because mine is broken!
Any advice?
C4lculated said:
Hello all.
The phone had an older unofficial LOS build installed (lineage-17.1-20200808-UNOFFICIAL-ginkgo.zip) but Bluetooth wasn't working.
I tried to install "lineage-17.1-20210927-nightly-ginkgo-signed.zip" via TWRP: I formatted DATA, then did a standard wipe, then installed via zip file on physical 64GB SD Card. But after rebooting I see the LOS animation for about 3.5 minutes then the phone reboots back to TWRP.
I installed official MUI (miui_GINKGOGlobal_V12.0.6.0.QCOMIXM_cfcf7038bd_10.0.zip) just to see if it will work and it booted without problems (and BT is working).
I tried LOS again, still doesn't work. I tried wiping EVERYTHING, including system, still the same. I tried with the LineageOS recovery - still the same but this time when it gets me back to recovery I get a message saying it failed and asking to try format DATA. I agree and let it do the format but still the same result.
I don't know what else to do and I need a phone because mine is broken!
Any advice?
Click to expand...
Click to collapse
do a clean flash and don't forget DFE

Categories

Resources