hi guys i have a problem with the mi9t
After a long time I bought a new phone but unfortunately for me things have changed for modding my phone is in bootloop and when I try to install a rom it installs me but on rebooting and as if it were not there
and then notice the following errors
unable to decrypt FBE device
to then start the installation by completing it but on restart it goes into bootloop and finally into recovery
https://imgur.com/a/s9zOpZE
Hard to help without knowing which steps you did.
Did you format data (not wipe, format) before rebooting after installing the ROM?
maybe ask the guys in the Pixel Experience thread?
who knows, it seems to be an issue with the rom .. wrong base (china fw) who knows
Related
my english is very poor ,my problem is the same with this , so i copy this from another one's question.
Help me, please!
Yesterday, I wanted to make a clean install for the latest Quarx's CM 10.1 nightly (I've been flashing Quarx's builds for almost a year now, he's The Best), but I think I made a terrible mistake.
When I wanted to make a factory reset, I've got this error because the sd-ext, I understand, that happened because TWRP's structure with almost all devices running Android 4.2.2 have a virtual-sd and a sd-ext, so I decided to make an Advance wipe and I every damn box, even wipe system and wipe sd card.
Finally when I rebooted my phone, TWRP asked to install SU, I pressed yes.
Then when my phone was rebooting, I've got this error:
Bootloader
09.10
if someone can help me ,can you teach me step by step ,because i really not familiar with english~~~ think every one any way
Hello,
I may have bricked my phone but I'm open to suggestions of possible solutions.
I upgraded to lollipop and everything was working great, I decided to try out the encryption functionality and now it doesn't boot...
It gives me an error screen saying that encryption failed, perform a factory reset. I have done so and it still won't turn on...
Since I have done a ADB push rom.zip to it and that didn't work.
Tried both TWRP and CWM to factory reset...
Do you guys have any other ideas?
Thanks
Anthony
Solved
I did end up finding a solution, thought it would be nice to share just in case someone else has the same problem.
Flashing to CM12 actually worked and got me through but I wasn't happy being limited to CM12 because when I flashed back to the rom it had the same issue.
I flashed to a standard rom from Samsung and used it's factory recovery menu to do the reset and that worked
First of all I'm not a very techy girl so please give me step by step instructions to recover my Yureka (Phone Details are given below). Few days ago (as usual) I restarted my phone and suddenly noticed a weird thing, It was stuck at YU-bootscreen/Logo for many minutes but suddenly started getting booted but I ignored it. I never knew it's going to be a big mess soon. After few days I again rebooted my phone but this time it refused to boot, the same situation. It was stuck at YU Logo. I waited for a long time but no gain. Screen was constantly on and it was literally scaring me. finally I ejected/removed the battery forcefully and reinserted it and restarted the phone and again after getting stuck at YU Logo/bootscreen for a while it got booted and it was a relief of sign. Here comes the main problem. Again after few days Yureka started hanging as usual and I again rebooted it but this time it was dead-end for me. It's again stuck at YU Logo Screen. I tried restarting/removing the battery many times but no luck. It's stuck at the screen forever. I am trying/restarting/reinserting-the-battery again and again but seems it's stuck forever at the bootscreen. It's been few days but no luck. I am totally frustrated and don't know what to do! I have important data in the phone especially App Data like Hike/WhatsApp and some GamesData/SMSes/Contacts etc. Please guys help me. How to revive my Yureka without damaging the precious data?
Things I tried to solve the problem:
1) I removed the battery many times. I did reboots many times.
2) I tried "Wipe cache partition" option in the recovery menu (Power+Volume Up+Volume Down) multiple times. But no gain.
What could be the reason of this problem? Is this faulty internal memory? Because my phone is behaving weird since the day I purchased it. Random App crashes happen multiple times regularly. This service stopped that service stopped blah blah. It's so annoying and counter-productive. It Started hanging and lagging a lot too. And finally bricked. I think this bricking problem only happens when you fiddle with your OS or try to root or install any unsupported custom ROM, But I am on stock ROM then why did it happen with me? Hardware defect? Did I get a faulty phone? I always ignored App crashes/Google services crashed /Random auto-reboots because I though Cyanogen OS is prone to bugs. But this is insanely odd! So many bugs are too much. Stock ROM has to be stable. I think YU gave me a faulty device! Please help me. What to do now to turn on my device without losing the data? I didn't try the Wipe data/factory reset OR Wipe media because it will remove all of my data which is very important to me.
P.S. Please note that my phone is stuck at YU Logo (NON-Animated logo) NOT on Cyanogen Logo.
One Another Indication of the problem:
When I tried to charge my phone by turning it off completely and then connected the charger with it the same YU logo came up and screen never went blank/off (screen with YU logo was constantly ON) and the Red LED light (charging indicator) didn't turn on, It means I can't even charge my battery because I think it's not getting charged cuz it's stuck on the same screen and never shows battery indicator while soft-pressing power button curiously just to check I removed the battery and tried connecting the charger without battery in the phone and the Red LED turned on normally.
Phone Details:
Phone Model: simple YU Yureka A05510 (NOT YU Yureka plus)
Cyanogen 11.0-XNPH05Q (Android KitKat 4.4.4) (NEVER updated Yureka)
NEVER rooted
Stock Cyanogen ROM
Stock Cyanogen Recovery
Are you sure it's still on KitKat?
Please confirm once again then I'll give you flashing guide.
saurav007 said:
Are you sure it's still on KitKat?
Please confirm once again then I'll give you flashing guide.
Click to expand...
Click to collapse
Yes it's KitKat 4.4.4
Download CM11 fastboot.zip and follow the flashing instructions from here.
This will erase everything from your device. If you don't want to lose data then download CM11 signed zip and flash it manually from stock recovery.
saurav007 said:
Download CM11 fastboot.zip and follow the flashing instructions from here.
This will erase everything from your device. If you don't want to lose data then download CM11 signed zip and flash it manually from stock recovery.
Click to expand...
Click to collapse
Hi! When the problem occurred I was thinking about the same solution, I mean flashing the ROM by putting it on a SD card. But I've two confusions on my mind
1. Should I directly flash CM 11.0 (the same ROM which I have currently) or the upgraded CM 12.0 (Lollipop)? I am confused
2. When this catastrophe happened, free space on internal memory was very low (I don't remember exactly but may be 100MB or 200MB or 300MB but very low). Will the ROM flashing process complete successfully?
Sarika CoolGirl said:
Hi! When the problem occurred I was thinking about the same solution, I mean flashing the ROM by putting it on a SD card. But I've two confusions on my mind
1. Should I directly flash CM 11.0 (the same ROM which I have currently) or the upgraded CM 12.0 (Lollipop)? I am confused
2. When this catastrophe happened, free space on internal memory was very low (I don't remember exactly but may be 100MB or 200MB or 300MB but very low). Will the ROM flashing process complete successfully?
Click to expand...
Click to collapse
1. COS12.1 Signed zip can be used to flash directly over COS11, but since there is lots of things happening in your phone, I'd suggest you to flash COS11 first.
2. 300MB is very low. Use external SD card because the size of signed zip is 500 MB.
Solution
Guyss plz plzz help me out, even my yureka has started behaving like this, im really fed up i tried many things but no use i tried the following things
1.installed stock rom using fastboot
2.flashed cm11 signed zip using recovery
3.clearing cache in storage
4.wiping dalvik and normal cache
Currently now i am using cm11 signed zip version
Hello all
I am having a little bit of trouble with my TWRP recovery after flashing an updated version of a custom ROM, i have been using for a while.
I am using the latest version of the Pure Nexus ROM, and am currently un-rooted. I earlier want to try and clear my davlik cache as i was having a few little issues with some things, and wiping this has previously fixed the issue, i rebooted into the TWRP, and was asked for a password, which i thought would have been the PIN i use to unlock my phone. This then failed, and it proceeded to try and decrypt the partition. I left it doing this for about 20 mins, but nothing happened.
After reading up a little more, and trying a few different potential passwords to no avail, i read up that the password that TWRP was asking me for was related to the fact i had my phone set to ask for password on boot.
I removed this, and tried again. This time, TWRP just got stuck on the splash screen when trying to boot. Nothing happened for a good 10 minutes.
After putting the PIN settings back on, it goes back to asking for a password, that it wont take.
Whats my next option here, im kinda stuck. I really dont want to have to wipe the phone as i have just spent the best part of a week after flashing my new ROM getting it all back to how it was after flashing the new custom ROM i am using..
All help, much appreciated, thanks in advance
What version of TWRP are you using ?
No issues on TWRP 3.2.0.3
Sent from my Nexus 6P using Tapatalk
I'm on version 30.20
Hey everybody, I need help. I have a J320P that is stuck in a boot loop, when it was found like this by my friend they came to me and asked if I could help. I have no information on how this happened other than they took a shower and when they came back it was like this. I have tried installing stock firmware 3 times to no luck. I might have an sd card somewhere with the backup for this phone but finding it would take some time so in the mean time I am turning to the forums. If anyone could help that would be amazing. I will provide more information and answer questions as they come.
Steps I have taken:
1. dirty flash of stock latest firmware
1. wiping the phone completely
2. Installing latest stock firmware
3. Still bootlooped
Not solved
So after triple wiping through TWRP and installing the stock firmware again it was still looping so i left to run to the store quickly and when I returned I tried powering it on and it loaded normally and I am still setting it back up.
Leaving the original comment. After coming home from work my friend said it had started doing it again, and it is. This time there was no root and no system anything messed with, does this mean there is a hardware problem?