Hi guys
My mido vibration stopped working a week back abruptly. I didn't flash anything new back then.
Tried diagnosing it with change of vibration motor (with a technician) as well but the new one didn't work either. He did attempt a temporary replacement of its underlying chip as well but again it didn't resolve the issue.
Attempted clean reflash RR. Then clean reflashed Havoc 2.9 build as well.
After reflash in both the builds, didn't install Magisk (just to be sure some version could have been conflicting with the motor may be)...No solution
Attempted firmware upgrade to notably stable versions 10.2.3 and then downgraded to 9.6.3 as well. No solution still....
Could anyone advise what I could attempt next..?
Current environment: Havoc 2.9
No magisk installed as of now.
Nothing works.
Magisk 20.1 was installed but removed now... Still doesn't work...
Please help.
@Walden0 brother could you help may be?
Naagraj said:
@Walden0 brother could you help may be?
Click to expand...
Click to collapse
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Walden0 said:
I don't really know what might be the issue , but I can suggest you to flash stock miui rom to see if it works there.
Don't forget to backup modem and efs partitions in case anything goes wrong with IMEI numbers. I hope that solves it.
Click to expand...
Click to collapse
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Naagraj said:
That could be a little tricky for me since I haven't attempted to go back to MIUI again. Could you point me to a guide or so?
Click to expand...
Click to collapse
First take a backup of EFS Am& modem partitions from recovery.
Wipe data, cache, dalvik & system. Flash miui rom, format data and flash orange fox recovery again. Boot into system.
That's it.
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Naagraj said:
Is orange fox recovery necessary? I don't know.
I an currently using twrp 3.3.1.0
Will that work?
Click to expand...
Click to collapse
Should work, orangefox has aggressive stock recovery deactivation which isn't available in twrp I guess.
btw quote or mention me as I can't get any notification if you don't.
Naagraj said:
Furthermore just to tell
Vibration doesn't work even in twrp (which actually is very strong in twrp navigation generally)
Could this hint a hardware malfunction?
Also, i did see the efs partition but not modem one....
Click to expand...
Click to collapse
Have already told you pal, try flashing miui and see if it works.
Modem partition should be in orangefox. I can't confirm as I don't have the device anymore.
Brother I am having same problem right now in 2020. did you find any solution to it? Any response will be greatly appreciated
I'm having this same problem in 2021. Any fix guys?
Related
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
phonester said:
After factory resetting/reinstalling [Resurrection_Remix][Android 6.0.1, r_52][Kenzo], the "Unfortunately Setting Has Stopped" has started appearing whenever I try to access the Privacy setting to change the password/pin/pattern option. I also noticed that the Fingerprint scanner is no longer in the Privacy setting.
Under TWRP I have also tried wiping Dalvik / ART Cache, Data, Internal Storage, and Cache when reinstalling any other Custom ROMs and Gaap. The other custom ROMS I've installed are causing the Setting->Privacy option to crash also. All the searches I've made doesn't seem to fix the issue, particularly the searches in the Redmi section. Any suggestion would be helpful, thanks.
Click to expand...
Click to collapse
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
khan_pegasus said:
Flash radio.zip fix.and dont forget to flash gapps after flashing roms.
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
It worked, thanks.
link to download radio.zip?
This situation happens when you switch to an OFFICIAL Rom from an UNOFFICIAL one like Mokee or RR from Siddhesh or Santosh. This is because these ROMs lock the bootloader and cause other problems too.
Radio.zip may not always fix the problem. If you are really stuck, there is a lengthy process that is guaranteed to work.
1. Flash one of the MiUI Fastboot ROM (global or chinese stable works fine) for RN3SD with Mi Flash tool. Use Flash All in the options at the bottom.
2. If you had an officially unlocked bootloader, use the Mi Unlocker tool to unlock your bootloader. Otherwise, you need to follow the unofficial unlock guide.
3. Flash official TWRP or a variant if you now what you are doing. Refer to this thread if you are not sure which TWRP will work.
3a. Download and copy this file to internal storage - LazyFlasher. I have verified this file to work with MiUI7 and MiUI8 global.
3b Reboot the phone in fastboot mode. On your PC, copy the TWRP img file to the adb directory and open command window there. Rename it to recovery.img. Use this command
Code:
fastboot flash recovery recovery.img
3c Boot into recovery (using ADB or Vol-pwr button shortcut). DO NOT BOOT into the phone before you do this. Flash the Lazyflasher zip with TWRP. You could probably flash this using fastboot too, I just never tried it.
Dhanajay made a guide video here. The video is a little outdated, and the updated instructions are in the description and comments.
You phone is now rooted and you have TWRP. Happy flashing.
This method will soon be outdated as a graphical UI for ADB is already in progress. Others have done it before, but this one shows real promise. Check here for details.
It has been a few months now since the RN3SD launch and the time has come when unofficial ROMs are no longer the best option around. Most Official ROMs, including the ones from RR and XOSP among others work great now and are incredbilby smooth and efficient. The war for the best kernel is now starting, and custom kernels will be responsible for the next round of reasons for bricked phones. Be VERY careful when you are flashing a ROM with a custom kernel. Be prepared to do some legwork if things go wrong.
Joswin said:
link to download radio.zip?
Click to expand...
Click to collapse
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
talkaboom said:
http://builder.balika011.me/official-cm13/cm-13.0-RADIOS.zip
I would also recommend anyone having this issue to read this post.
Click to expand...
Click to collapse
Link isn't working...
Can you mirror it?
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
Seems to be down. Normally works. Give it some time.
But if you are moving from an unofficial ROM, flashing radios alone is unlikely to work. Radio zip fix is for undetected SIM and IMIE errors. Check your IMIE number in About Phone. If you are showing an IMIE number instead of '0', flashing radio may be pointless.
Joswin said:
Link isn't working...
Can you mirror it?
Click to expand...
Click to collapse
New Link available.
https://mega.nz/#!9hlljJKD!QmjwPqMOH...gOqWkEJ0QasGE4
talkaboom said:
New Link available.
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
virtualgates said:
This link needs a decryption key not provided. Why even post this?
Click to expand...
Click to collapse
Link is from August 8th. That **** has mirrored a hundred times by now.
Also, the problem is now tackled in a different way. If you're facing a similar issue, ask in the rom thread you are trying to flash.
If you are facing this problem now, just flash the correct CM firmware.
P.S. On XDA, please do not question why someone posted a link or method that did not work for you. Do your research. No one is obligated to solve your problems.
Flashed radio. Zip. Worked for me.
Sent from my Redmi Note 3 using Tapatalk
Hello talkaboom!
the link is not working anymore. Any chance to upload it again please? Thanks a lot!
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
Hello everyone, let me just go ahead and say that I'm a total noob in the android customization thing but I somehow manage to install Lineage OS on my L03 and at the time I thought it was done and I didn't messed anything up but somehow that backfire on me.
So right now my HAM 2 is on a boot-loop, it kept staying the Lineage OS loading screen and once it was done and show the device setup screen for like 3 seconds it goes black and load again.
I've tried everything to fix it, from reinstalling an older version of Lineage, install CM13, wipe all data cache and dalvik ( and yes I have install gapps everytime I install any custom ROM, and finally after looks around the web I thought It might be the power button that making it acts weird but when after cleans it with rubbing alcohol (70%) It's still happening.
Now I have 2 options, first is to downgrade the firmware ( I'm not sure if it safe and how to do it) and seconds is to downgrade or delete TWRP ( newest version on HAM2).
Please, if anyone knows how to fix this. Help me. I got this device from amazon and it'll be a hassle trying to claim warranty on it since I have unlock it's boot-loader and install a custom ROM.
Thanks in advance.
Im not trying to be an asshole but does no one know how I can fix this?.
Bl4ckAir said:
Im not trying to be an asshole but does no one know how I can fix this?.
Click to expand...
Click to collapse
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
divhandyman said:
Are you using MDMower's latest version of TWRP for the Mate 2 (3.1.N0-0) ?
Click to expand...
Click to collapse
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Bl4ckAir said:
I'm using the offical Teamwin TWRP 3.1.1.0 for mt2l03.
Click to expand...
Click to collapse
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
divhandyman said:
That one never works for me. Flash this version of TWRP and flash the latest version of Lineage OS 20170903.
https://www.androidfilehost.com/?a=show&w=files&flid=40887
Click to expand...
Click to collapse
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Bl4ckAir said:
Could you elaborate on how to do that? Can I flash it in the old TWRP or ADB on desktop? Thanks.
Click to expand...
Click to collapse
Yes use ADB.
https://www.youtube.com/watch?v=OwY-K6-pmJU&feature=youtu.be
Bl4ckAir said:
Please, if anyone knows how to fix this.
Click to expand...
Click to collapse
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
hola
have you managed to solve it?
I have the same problem!!!
please help
Douglas_27 said:
have you managed to solve it?
I have the same problem!!!
please help
Click to expand...
Click to collapse
Hi, Douglas I have managed to solved it. Please tell me the step you have taken and I'll maybe able to help you.
Does it work for L01 the latest TWRP
EndlessFall said:
Well, it seems that you missed all of the fun & games last week in the following thread:
https://forum.xda-developers.com/ascend-mate2/help/candy7-cm13-rom-restarting-loop-issue-t3661885
"divhandyman" gets right to the point by correctly recommending MDMower's repo @ AndroidFileHost. My discussions on the topic are slightly more wordy (we all have our faults, yes?), but MDMower's TWRP & LineageOS 09/03 (or newer) is all that you need because the boot loop fix is baked-in.
As a side note, my original instructions assumed a degree of basic knowledge and did not include guides to installing TWRP, making backups, moving files, using ADB/fastboot, etc... These tools and procedures are well documented, ad nauseam, elsewhere.
Click to expand...
Click to collapse
I tried the latest TWRP from MDMower but got stuck in a boot loop after I flashed it and went to turn off the phone to go into recovery mode.
i mistakingly delete a file on my huawei mt2-l02 and since then when i power on it will stuck on startup anyone with solution
Hello everyone
Yesterday while restoring a backup of my rom, I also restored the firmware (didn't know I wasn't suppose to do that :/) and lost my IMEI etc.
I fixed that by flashing a stock rom suggested on another thread.
That fixed the IMEI and everything.
I restored my rom (correctly this time) and got everything back (I'm on Cardinal)
But now my gyroscope and accelerometer are acting weird.
I used an app to test and saw it was really erratic, jumping from side to side etc.
Now I have no idea where to go from here.
Any help would be great
Thanks
Danish78 said:
Hello everyone
Yesterday while restoring a backup of my rom, I also restored the firmware (didn't know I wasn't suppose to do that :/) and lost my IMEI etc.
I fixed that by flashing a stock rom suggested on another thread.
That fixed the IMEI and everything.
I restored my rom (correctly this time) and got everything back (I'm on Cardinal)
But now my gyroscope and accelerometer are acting weird.
I used an app to test and saw it was really erratic, jumping from side to side etc.
Now I have no idea where to go from here.
Any help would be great
Thanks
Click to expand...
Click to collapse
You can always flash the firmware file, if you want.
Do that, it should fix (most probably)
MyNameIsRage said:
You can always flash the firmware file, if you want.
Do that, it should fix (most probably)
Click to expand...
Click to collapse
The stock firmware? (the one with MIUI)
How do I go about doing that?
Through TWRP?
Danish78 said:
The stock firmware? (the one with MIUI)
How do I go about doing that?
Through TWRP?
Click to expand...
Click to collapse
If the rom you restored is aosp based then the firmware which you have for aosp roms, but if you have miui then installing miui again will fix it.
MyNameIsRage said:
If the rom you restored is aosp based then the firmware which you have for aosp roms, but if you have miui then installing miui again will fix it.
Click to expand...
Click to collapse
I restored a backup of a Lineage based rom, that's what cause the problem with the IMEI vanishing in the first place.
And I've read that the persist.img is what can fix the accelerometer... So confusing.
Danish78 said:
I restored a backup of a Lineage based rom, that's what cause the problem with the IMEI vanishing in the first place.
And I've read that the persist.img is what can fix the accelerometer... So confusing.
Click to expand...
Click to collapse
Try this,
I made this flashable zip, comtaining the persist backup of my phone, which i made using redwolf recovery. (Sorry i can't switch to regular twrp :crying
Ok so flash this and then try to restore.
https://drive.google.com/file/d/1aLwU_IuqzDrVwPC9SXsegTeZbUhfvREQ/view?usp=drivesdk
MyNameIsRage said:
Try this,
I made this flashable zip, comtaining the persist backup of my phone, which i made using redwolf recovery. (Sorry i can't switch to regular twrp :crying
Ok so flash this and then try to restore.
https://drive.google.com/file/d/1aLwU_IuqzDrVwPC9SXsegTeZbUhfvREQ/view?usp=drivesdk
Click to expand...
Click to collapse
Oh man this totally fixed the issue.
Thanks a lot.
I thought I'd have to flash an official firmware and start from scratch.
You saved me a lot of time.
Thank you very much
I'm left clueless here. I just can't get it to boot, no matter what ROM/Kernel i'd flash. It was originally running OOS 2.3.1 but flashing it now won't work anymore. It worked briefly for 1 hour with that AOSP 8.1 but then after trying to flash gapps it stuck again in a bootloop. Sometimes it also freezes and reboots while i am flashing sometimes. I really have no idea what should i do next, hope you can help me.
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Kéno40 said:
You need to give more information on which TWRP you have.
Did you upgrade the bootloader at one point ?
OOS 2 is the old one.
You should have upgraded to MM bootloader and the use a TWRP compatible.
If not, you'll have to follow the Mega Unbrick Guide...
Click to expand...
Click to collapse
I updated the bootloader like over a year ago or so. I also tried 2 different versions of TWRP, now i am using the latest one.
ALSO, very sorry it actually is OOS 3.1.4, not 2.3.1, i just typed briefly what i could remember, i haven't been using this phone for months now but i would like to give it to a relative so there's that. Hope you can help me out, i have no clue why is it acting up like that.
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Try to flash official ROM after having wiped everything
Kéno40 said:
Try to flash official ROM after having wiped everything
Click to expand...
Click to collapse
That's what i first tried, mentioned it in the main post.
yayakuya said:
Have you ever think that could be the emmc problem that need to get replaced?
Our phone is old enough...
(just my thoughts btw)
Click to expand...
Click to collapse
I don't know what to make of this, thought maybe anyone else encountered this problem and has a clue.
gabytzu338 said:
That's what i first tried, mentioned it in the main post.
Click to expand...
Click to collapse
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Kéno40 said:
You didn't mentionned you wiped everything : System, data, cache, Internal...
Then usb mount to pussh OOS 3 and flash
Click to expand...
Click to collapse
I don't really understand what you are trying to say. I did wipe everything and the only way to flash anything is through adb sideload anyway since the device is not recognized as storage while in TWRP. I think I am gonna give up on it, I was gonna sell it but I can't risk having it act up days/weeks after i sold it.