my Mi Note is dead. - Xiaomi Mi Note 2 Questions & Answers

Hi everybody.
Dis morning I woke up and I realized that my phone was gone. I used AOSP Extendend ROM when it happens. At first, the rom completely froze. I thought it was a bug, so I rebooted the phone, but after did dis, the phone kept on rebooting and froze on first screen and I couldn't do anything. Touch didn't respond, nothing worked.
So I tried to go on recovety, but nothing.
At the end, I gave up about take back my data and try to install the stock ROM through MiFlash. I tried different stock ROM, but at the first they works, but during the installation guide they froze again and reboot. I can't even finish the setup!
So I tried again, unlock bootloader, flash TWRP, but still there:
- only TWRP v2.0 works, other versions won't start
- even with TWRP v2.0, after did wipe everything and format, when I tried to install a custom ROM, even TWRP froze and reboot the phone
- TWRP is pretty useless, it keeps on froze and when I boot recovery again, TWRP is locked and I have to format everything again, but still don't work.
Someone could tell me what happened to my phone? Any suggestions about what I could to to install something on my phone?
Pls help me, I am completely lost and disperate

You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.

cobben said:
You may in deed have a serious hardware problem.
What you can do without opening it up is to try charging it overnight, and see how it works tomorrow.
You have tried everything else you can think of, I assume, like wiping & formatting everything you can in TWRP, and possibly "repairing file system" if there is such an option.
The next thing I would try is opening it up and disconnecting the battery for a while, then connecting it again to see what happens.
Click to expand...
Click to collapse
Ok, I will listen your tip. Yeah, I have tried everything but nothing. Technically, I bought this phone last december, so it's still covered by warranty, but I have to send it to China, I would avoid that if I can.
I hoped there would be something that I didn't but...nothing.
Thanks anyway dude

Related

i9505 black screen after reboot

Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Same problem on same phone
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
I was using a CM10.1 nightly build for my i9505 and attempted to install the AVAST Anti-Theft feature using the root install method. On the first attempt at installation there was a free-space error, in which the amount of free space shown in the /system partition had overflowed and showed negative free space. To work around that error I filled up my /system partition until there was only 100mb free and then the install worked. All went well until I did a reboot; the phone hung at the i9505 screen.
I tried rebooting the phone and removing the battery for a short while, but nothing worked - the phone still hung at the i9505 screen. However, all other functions worked, so I just reflashed CM10.1 after wiping /cache, /data (but not /data/media), /system, and the Dalvik-cache (though that is in /cache AFAIK so pretty redundant). All was fine after that reflash, other than the annoyance of having to set everything up again (didn't make a backup recently).
Obviously the Anti-Theft wasn't very secure if it could be removed by a simple reflash. But to be fair, I highly doubt any software can protect itself from a format!
Anyway, just letting people know that I can confirm this this problem exists, and how I fixed it on my phone.
ingvarr_zaag said:
Hello,
I have a problem with my i9505. The phone had been rooted with stock ROM. I've installed Avast Antivirus and decided to install Anti Theft feature. Installing it requires reboot. After confirming rebooting the phone beeped twice and rebooted. And this is where my problem begins.
After reboot the screen is black. It shows nothing. The phone boots, LED shows charging, connecting and disconnecting charger makes phone beep, but with few seconds delay. Connecting to PC shows content of phone memory.
I have managed to get to recovery. Odin had seen the phone so I've flashed official Samsung ROM. It didn't help.
Surprisingly after few hours with battery removed the phone started to work normally... until the next reboot.
And now it works until the reboot. After reboot the screen is black. After about 30 minutes without battery it works again.
The phone never got dropped or damaged in any way.
Before I get my phone to the service (hoping that they'll fix it under warranty) I'd like to ask you, if somebody had similar problem and knows how to fix it.
Thanks in advance.
Click to expand...
Click to collapse
Flash stock firmware using odin
Go to stock recovery there factory reset and wipe
Reboot
Note all data will be lost take backup b4
.
sheomualjy said:
Hi,
I too had this problem, and fixing it wasn't difficult, however I used the TWRP recovery which @ingvarr_zaag probably doesn't have installed (seeing as they had stock firmware). Nevertheless I can confirm this identical problem on my own i9505.
Click to expand...
Click to collapse
I had Clockwork Recovery installed but I couldn't use it, because after reboot the screen was black. I managed to get to android recovery and flashed stock Samsung ROM by Odin. It didn't help.
After 2 weeks in service it's possible that today I get my phone back. Finally, because two weeks with Samsung Galaxy Advance were miserable.
Actual status on service's page says, that they replaced main board in my phone.
BTW: no Avast Anti Theft ever again.

Nexus 4 turning off when unplugged from charger

Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
Planterz said:
The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.
If it's not the battery giving you woes, I don't know what it could be.
Click to expand...
Click to collapse
How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.
Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %
After all , all this hardware mess up can be the consequence of a bad cm flash ?
the whole "optimizing app" thing is the OS rebuilding the cache.
Click to expand...
Click to collapse
I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
By any chance did you have your phone charging while flashing and booting up your ROM?
ChainFires Son said:
By any chance did you have your phone charging while flashing and booting up your ROM?
Click to expand...
Click to collapse
May be? But not the the first time
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.
I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.
But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).
But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.
Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?
Please, Thanks
EDIT
Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
Click to expand...
Click to collapse
Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
Nezam said:
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...
Click to expand...
Click to collapse
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
shazR00t said:
I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.
Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.
Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.
Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.
This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
Click to expand...
Click to collapse
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
I have the same thing for several month now.
Always thought it is the dying battery.
theminikiller said:
Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
Click to expand...
Click to collapse
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
shazR00t said:
Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems
Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Click to expand...
Click to collapse
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
theminikiller said:
When you flashed the factory image did you do it via fastboot or by flashing a zip file. If you used the zip file I would suggest you do it with fastboot.
Click to expand...
Click to collapse
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the image files. If you did that then u don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
---------- Post added at 20:42 ---------- Previous post was at 20:41 ----------
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Yeah, I meant flashing each of the images. If you did that then I don't have any other suggestions.
Sent from my Nexus 4 using Tapatalk
I m too facing the similar issues. Phone is getting turned off suddenly when not charging, on charging it is working fine. i have done factory reset and also done factory image reset to 5.1.0. i m still facing the same issues. I don't think so it is related to battery. if anyone have the solution then please let me know.
shazR00t said:
By "flashing zip" you mean using "fastboot update" command? ...If so, nope I didnt. I extracted all compressed files and then flashed each of the img's using fastboot. Flashed a total of 6 img files.
Click to expand...
Click to collapse
Try the very basic flash technique by double clicking the flash-all.bat. It's not the same as flashing the imgs one by one.
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
gautam.is.sharma said:
Battery is the issue. Get it changed. I also faced same problem, and visited LG service center and they changed the battery. Phone working fine now.
Click to expand...
Click to collapse
Ok so Battery was the problem!! Got it changed, phone working fine now. Thanx all!
Ok guys i confirm that this is a battery issue. I took it to the service center and the guy temporarily replaced battery to show me issue solved... But... there i saw another issue due to which i did not buy the battery. I saw half the touchscreen not working (including the navigation buttons ). The guy at the center told its a h/w issue and i would have to spend 7K on it so i left my phone dead for now. The Question is ... can this be a s/w issue.. or result of bad flash which can solve on reflashing ??
same problem with my nexus ,but one thing i noticed that the phone does not power off while in recovery...Any idea??

When WiFi is turned off I get 'Unfortunately System UI has stopped'

This is on two standard Galaxy S5's, with standard ROM, etc - not rooted, or anything else.
Every time I turn off WiFi, or enable Mobile Hotspot, I get 'Unfortunately System UI has stopped'.
To fix I have to Power off/on the phone.
(Turning on WiFi is no problem, just turning it off.)
I have gone into 'Safe Mode', and same issue, so it looks to not be a bad App.
I have also uninstalled 'Google' updates, and again no change...
Any thoughts?
All of a sudden my S5 showed the exact same error message for no aparent reason... I didn't do anything, and now I can't use my phone at all because of that bug. It happens on every boot so I can't even unlock my phone. Tried reinstalling everything, ROM, recovery, kernel, with/without root = still same, what just happened here??
EDIT: Same thing if I'm in Safe Mode -_-
Seeing noone knows a solution here's what I did yesterday.
1. Backed up all my stuff from internal storage to the sd card
2. Did factory reset in TWRP recovery
3. Flashed completely stock official firmware from Samsung
4. Waited for it to boot up and try to restore some of my settings (it restored all folders on their places, made same amount of home screens as I had before the reinstall and downloaded all of my previously installed apps from the Play Store, ofcourse without the cracked ones, and it also restored most apps' data as well so it's not as bad as you may think to factory reset and reinstall everything)
5. Started rooting, flashing TWRP again, installing Dolby Audio, Xposed and everything I had before, took me one full day to set it up as it was before.
Now when I set it up I always make a nandroid backup from when things are working fine, in case it goes crazy for no reason again... Good luck!
when the wifi radio is acting weird, a dirty flash of your current ROM susually fixes is as its probably a radio issue. Id do that before doing anything drastic like the boot-n-nuke Odin flash and starting from scratch (which will fix that issue)
I don't think I have a ROM issue, as I have two S5's, and both have the same issue... and both are standard ROMs.
I will do a factory re-set on one at some point, but this looks to be a 'simpler' issue.
I have tried a full Cache delete, as well as other 'clean' processes.
Nothing works.
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
koragg97 said:
I tried to re-flash my stock ROM as @youdoofus said but still had that annoying popup. Try everything you can think of, if all else fails, reset.
Click to expand...
Click to collapse
well, you can wipe cache, and dalvik 3x each (not kidding about the 3x each), then dirty flash the rom, pray to the gods of android, reboot. If failure occurs, its Odin Nuke time unless you want to try to flash an individual radio file by itself (not recommended)

Freezing and rebooting

Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
raz_il_dio said:
Hmm i will give you an advice so you dont have to wait for your battery to drain...just press volume down and power button for like 5 secs and phone will force boot. Anyway back to your problem...did you tried flashing latest stock samsung firmware?
Click to expand...
Click to collapse
This advice doesn't work with my phone even with holding the buttons for 30 secs and more. For rebooting I can only wait until the battery is completely drained. With little hope for another way shortening time to the next reboot any help is appreciated.
Same here...experiencing the same prob...
Same problem.
Sent from my Redmi Note 4 using Tapatalk
smallcapsicum said:
Classic "my phone keeps freezing and rebooting". I am quite in the know about flashing roms and such.
It started on the stock firmware 6.1.1 (i think it was). I dd factory resets, cache wipes the lot. It would still randomly reboot.
So i flashed Telstra version of 7.0. Still froze every now and then. Did the same things as above.
Flashed TWRP and wiped everything, flashed Renovate Rom and the bootloader for it, Still did it. Numerus factory resets and wipes of everything. It would freeze at any point from startup, to having setup the phone and making phone calls or on facebook or whatever. It would even freeze in twrp, or loading twrp.
I found that the data partition was corrupt so i re partitioned to ext4. Still nothing. I reformatted every partition so the phone was a complete brick with nothing on it and after flashing clean again it would still do it.
Whats the issue that I'm missing, or is there a way to log so i can find where it keeps getting stuck? It gets hot and blue light flashes and i have to hard reset it or sometimes i have to let the battery drain so i can turn it back on again.
pls help?
Click to expand...
Click to collapse
Sounds like you need your motherboard replaced i had the same issues on marshmallow thought the nougat update would fix it but realized it was a hardware fault not software..left it in store to get fixed and on repair sheet it said faulty motherboard..
Sent from my SM-G935F using XDA-Developers Legacy app
As i know some S7 have motherboard hardware problem, mine has too, what help? warranty and they replaced motherboard. But if you root, you can say good bye to warranty, they look at knox first with this problem.

Encryption Failed... Tried formatting, wiping, installing new ROM but no use

I have a I9505 and it was working fine (samsung ROM), when I decided to 'encrypt' my device! It was fully charged and connected to a charger.
After starting, it stayed connected for 5-6 hours, but nothing was seemingly happening.. After 6 hours I switched it off. Then back on again.
The device after starting (just the system) didnt let me do anything else, and told me that since encryption failed, I need to format the device. So I restarted, formatted. Still same msg
Wiped the device completely. Still same issue. Tried changing file system from ext4 to ext2.. still same problem! I installed a couple of roms, they seemingly installed ok, but after starting, the same msg!
Please help me!
My bootloader is TWRP by teammate I think
Did you attempt to flash the stock ROM via Odin?
find a place that can do a JTAG
I had this issue last week.
1. Flash Stock rom with Odin
2. Boot into stock recovery (Must be stock)
3. Choose factory reset
Fixed.
SOLVED
Thank you guys! Flashing with ODIN worked fine! Not sure why I didnt think of that earlier!!
hdaackda said:
I have a I9505 and it was working fine (samsung ROM), when I decided to 'encrypt' my device! It was fully charged and connected to a charger.
After starting, it stayed connected for 5-6 hours, but nothing was seemingly happening.. After 6 hours I switched it off. Then back on again.
The device after starting (just the system) didnt let me do anything else, and told me that since encryption failed, I need to format the device. So I restarted, formatted. Still same msg
Wiped the device completely. Still same issue. Tried changing file system from ext4 to ext2.. still same problem! I installed a couple of roms, they seemingly installed ok, but after starting, the same msg!
Please help me!
My bootloader is TWRP by teammate I think
Click to expand...
Click to collapse
Dude did you try to use an aosp rom

Categories

Resources