Hello everyone, I hope you can help me in this huge problem, I do not deny being completely scared...
I'm not an expert in modding, actually I'm new in this discipline, I'm a holder of Xiaomi Redmi Note 4 Qualcom 3/32.
Today I wanted to follow a video on youtube that explained how to improve my device, making these changes:
ROM Pixel Experience: https://forum.xda-developers.com/re...her-development/rom-pixel-experience-t3723382
TWRP for Redmi Note 4 (mido): https://dl.twrp.me/mido/
All versions of the Google Camera: https://www.celsoazevedo.com/files/android/google-camera/
Direct link to the version for Xiaomi Redmi Note 4 (requires modified ROM, does not work on MIUI): https://www.celsoazevedo.com/files/android/google-camera/f/scrubber_GCam_5.1.018_24.apk
Kernel: https://forum.xda-developers.com/re...-development/kernel-stormguard-11-08-t3702031
So I convinced myself to take the appropriate online guides to get the same benefits described in that video.
- I managed to unlock the bootloader after three days from the request to Xiaomi.
- I followed the guide to install TWRP, the first attempt was successful, but entering the recovery I did not find the TWRP but the recovery of Xiaomi.
I realized that I should avoid starting Android first, as the system is as if it were self-protected by TWRP, replacing it with the original version.
- I made a second attempt, this time I managed to get into the TWRP screen first, but here I had to choose the "overwrite" option instead of "go into read-only mode".
Now if I restart the phone to get back to the system I am stuck with the Xiaomi logo and can no longer access the operating system.
- I have access to fastboot.
- I have access to TWRP.
- I do not have access to Android.
- I have unlocked bootloader.
- my phone is not rooted!
Panicked, I found on the internet guides that suggested to format "DALVIK" and "Data" and "Cache" via TWRP, so I did, but this did not solve the problem, I can not yet enter the operating system.
How can I recover access to my device?
What could have happened precisely?
Thank you so much ... I hope you do not have to throw the phone ...
Pleppo said:
... How can I recover access to my device?
What could have happened precisely?
Thank you so much ... I hope you do not have to throw the phone ...
Click to expand...
Click to collapse
If your ROM is miui, then you need to install lazyflasher. Search the forum for this.
DarthJabba9 said:
If your ROM is miui, then you need to install lazyflasher. Search the forum for this.
Click to expand...
Click to collapse
Thank you very... very much for your answer!
Yes, I bought my phone with MIUI international inside... I'm going to search it on the forum, can you please provide me a link you too?
My fear is that the phone won't turn on anymore following the guide of "lazyflasher"... how can "lazyflasher" help me? thank you
Pleppo said:
Thank you very... very much for your answer!
Yes, I bought my phone with MIUI international inside... I'm going to search it on the forum, can you please provide me a link you too?
My fear is that the phone won't turn on anymore following the guide of "lazyflasher"... how can "lazyflasher" help me? thank you
Click to expand...
Click to collapse
https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
DarthJabba9 said:
https://forum.xda-developers.com/re...er-development/recovery-twrp-3-0-2-0-t3550061
Click to expand...
Click to collapse
Thank you, that thread will explain how to "recover" the system by using "twrp + Lazyflasher" right?
I will follow this instructions, even if I already installed TWRP, is it right?
Download recovery*.img and Lazyflasher
Copy lazyflasher In your internal Phone memory
Run "fastboot flash recovery recovery-mido.img in command line
Boot into recovery and flash Lazy flasher (Important for miui, else you can't boot into system)
Reboot and enjoy it
Click to expand...
Click to collapse
Why do you think my phone has got breaked?
Thank you! (i'm sorry for my bad English)
Pleppo said:
Thank you, that thread will explain how to "recover" the system by using "twrp + Lazyflasher" right?
I will follow this instructions, even if I already installed TWRP, is it right?
Why do you think my phone has got breaked?
Thank you! (i'm sorry for my bad English)
Click to expand...
Click to collapse
You already have TWRP. Just boot into TWRP and install lazyflasher via TWRP. You should be able to reboot into your miui after that. As has been explained, miui will not boot after installing TWRP if you don't install lazyflasher.
DarthJabba9 said:
You already have TWRP. Just boot into TWRP and install lazyflasher via TWRP. You should be able to reboot into your miui after that. As has been explained, miui will not boot after installing TWRP if you don't install lazyflasher.
Click to expand...
Click to collapse
Thank you so much, then tell me if I understood correctly, I do not need to panic, because the "brick" is not a real "brick" but it's just a known side effect that happens when someone decides to install TWRP on their device Xiaomi, am I right?
Since my goal is to install the Google Experience ROM on my Xiaomi, in your opinion, can I proceed with the flash of the external rom? I mean, this kind of "soft brick" is part of the normal practice for installing a custom rom? How come no guide I read talked about it? "lazyflasher" is useful to solve a damage that I created, or just to return to MIUI?
The following instructions and the current situation of this "soft brick" may have damaged something in the phone, so I have to stop moving forward with the intention to flash the Google Experience?
format "DALVIK" and "Data" and "Cache" via "advanced wipe" from TWRP
Click to expand...
Click to collapse
Pleppo said:
Thank you so much, then tell me if I understood correctly, I do not need to panic, because the "brick" is not a real "brick" but it's just a known side effect that happens when someone decides to install TWRP on their device Xiaomi, am I right?
Since my goal is to install the Google Experience ROM on my Xiaomi, in your opinion, can I proceed with the flash of the external rom? I mean, this kind of "soft brick" is part of the normal practice for installing a custom rom? How come no guide I read talked about it? "lazyflasher" is useful to solve a damage that I created, or just to return to MIUI?
The following instructions and the current situation of this "soft brick" may have damaged something in the phone, so I have to stop moving forward with the intention to flash the Google Experience?
Click to expand...
Click to collapse
Installing TWRP damages nothing. Wiping cache and dalvik damages nothing. If that is all that you did, then nothing is damaged. If you can boot into TWRP, then almost anything can be fixed. And, yes, you should be able to install Pixel Experience or any other ROM (just make sure you follow all the instructions).
To be honest, if you are asking these questions, then you really should stay with your miui until you have secured deeper understanding of things. There are many pitfalls with regard to flashing custom ROMs, even for experienced people. Just install lazyflasher, boot into miui, and lurk round these forums for about a month, before trying anything else.
DarthJabba9 said:
Installing TWRP damages nothing. Wiping cache and dalvik damages nothing. If that is all that you did, then nothing is damaged. If you can boot into TWRP, then almost anything can be fixed. And, yes, you should be able to install Pixel Experience or any other ROM (just make sure you follow all the instructions).
To be honest, if you are asking these questions, then you really should stay with your miui until you have secured deeper understanding of things. There are many pitfalls with regard to flashing custom ROMs, even for experienced people. Just install lazyflasher, boot into miui, and lurk round these forums for about a month, before trying anything else.
Click to expand...
Click to collapse
Thank you very much, I managed to enter the MIUI 9, although I noticed that everything has been restored as factory, I wonder, which of the instructions I listed before applied the restoration, precisely?
In addition, about updates to the system coming from Xiaomi, nothing has really been changed, apart from the restore of the phone?
Pleppo said:
Thank you very much, I managed to enter the MIUI 9, although I noticed that everything has been restored as factory, I wonder, which of the instructions I listed before applied the restoration, precisely?
In addition, about updates to the system coming from Xiaomi, nothing has really been changed, apart from the restore of the phone?
Click to expand...
Click to collapse
Lazyflasher allowed you to boot into what was there before TWRP was installed (which still remained there, but was inaccessible under lazyflasher was installed). Wiping the data partition will reset the phone to factory.
Pleppo said:
Thank you very much, I managed to enter the MIUI 9, although I noticed that everything has been restored as factory, I wonder, which of the instructions I listed before applied the restoration, precisely?
In addition, about updates to the system coming from Xiaomi, nothing has really been changed, apart from the restore of the phone?
Click to expand...
Click to collapse
is you device fixed now?
MyNameIsRage said:
is you device fixed now?
Click to expand...
Click to collapse
Yes! Thanks to DarthJabba9! :laugh::laugh::victory:
Pleppo said:
Yes! Thanks to DarthJabba9! :laugh::laugh::victory:
Click to expand...
Click to collapse
cool ? also please add [Resolved] in the title so that any one else having same problem can find the soulution here :fingers-crossed:
Related
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)
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
video_dewd said:
Hi all,
I recently got a new Axon 7 (A2017U) and wanted to root it just like my old G3. I tried following DrakenFX's instructions (Here: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204), but I got lost. I ended up with a password being requested at the android startup screen. In a panic, I clicked Format Data when I got back into TWRP, that made it worse and I went into EDL to see if that might help. Eventually I got back into TWRP and that's where I am now, desperately trying to get my new phone working again. All the threads I read only add another layer of confusion. Would someone be willing to walk me through the steps of fixing my phone? I really don't want to RMA/have $400 to go down the drain. I'd own you a big one.
-RG
Click to expand...
Click to collapse
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
mugel2110 said:
Hi,
so you have access to the TWRP. Thats good. Do you have access to a stock ROM from your manufacturer? In case yes, you could simply flash the stock.
For this, the rom has to be on a SD card or on the internal memory of the phone.
In TWRP go to "Install", than navigate to the file and swipe to install (it comes a zip file).
Click to expand...
Click to collapse
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
video_dewd said:
I'm looking for one. Some threads pointed to an OTA update that ZTE has on their site. However, when I try to install things on TWRP, I get an error about "dev/block/sde14" being read-only. (It sometimes says "sde13" too.)
Click to expand...
Click to collapse
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
mugel2110 said:
Dis you go on Advanced
Wipe dalvik-chace
Wipe /cache
Do you have access to fastboot?
Click to expand...
Click to collapse
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
video_dewd said:
Yes and I'm not sure. I can boot to system, recovery, and bootloader.
Click to expand...
Click to collapse
I am far from being a pro. I once had the problem that I was caught in bootloop and could not install a new rom. But I was able to re-flash TWRP (via Minimal adb and fastboot) and than everything was fine.
Maybe someone else can comment on that. On your own risk...
Just a tip. Never panic and press any button
mugel2110 said:
Just a tip. Never panic and press any button
Click to expand...
Click to collapse
I figured haha
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
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.
I tried flashing twrp vince in note 5 but it asks password i tried my phone pin password but still it didn't work even i tried formata data but still it ask for password again and again to decrypt and it also shows internal memory zero
I also tried redwolf recovery but it also have same issues i.e unable to mount
internal memory zero
I don't know whats wrong
Is it due to miui 10 developer rom or something else
Please anyone could help me with this problem
harsh818 said:
I tried flashing twrp vince in note 5 but it asks password i tried my phone pin password but still it didn't work even i tried formata data but still it ask for password again and again to decrypt and it also shows internal memory zero
I also tried redwolf recovery but it also have same issues i.e unable to mount
internal memory zero
I don't know whats wrong
Is it due to miui 10 developer rom or something else
Please anyone could help me with this problem
Click to expand...
Click to collapse
Search the forum, this has been explained time and time again.
Morecs said:
Search the forum, this has been explained time and time again.
Click to expand...
Click to collapse
Sorry i couldn't find can u give me the link of that thread please!
harsh818 said:
Sorry i couldn't find can u give me the link of that thread please!
Click to expand...
Click to collapse
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
DarthJabba9 said:
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
Click to expand...
Click to collapse
This is not what OP asked for. It's not even TWRP. Why do you keep linking this thread as an answer to unrelated questions?
raneso said:
This is not what OP asked for. It's not even TWRP. Why do you keep linking this thread as an answer to unrelated questions?
Click to expand...
Click to collapse
Because orangefox recovery works well with encrypted data partition. Twrp can't handle encrypted data partition.
raneso said:
This is not what OP asked for. It's not even TWRP. Why do you keep linking this thread as an answer to unrelated questions?
Click to expand...
Click to collapse
If you think this is not relevant, you clearly do not understand his problem. And, may I ask, what is your personal contribution to helping him with his problem?
DarthJabba9 said:
https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479
Click to expand...
Click to collapse
Use this ( orange recovery )
---------- Post added at 02:44 PM ---------- Previous post was at 02:43 PM ----------
raneso said:
This is not what OP asked for. It's not even TWRP. Why do you keep linking this thread as an answer to unrelated questions?
Click to expand...
Click to collapse
Twrp encrypts data every time when u boot into recovery , for this use Orange Recovery ( above guy DarthJabba9 is correct)
DarthJabba9 said:
If you think this is not relevant, you clearly do not understand his problem. And, may I ask, what is your personal contribution to helping him with his problem?
Click to expand...
Click to collapse
I know what orangefox recovery is, no need to act condescending. I see you in every other thread plugging your own thing without a word of explanation and I don't think it's helpful. Regardless, we're getting off-topic here...
raneso said:
I know what orangefox recovery is, no need to act condescending. I see you in every other thread plugging your own thing without a word of explanation and I don't think it's helpful. Regardless, we're getting off-topic here...
Click to expand...
Click to collapse
What is your personal contribution to solving this guy's problem?
jes0411 said:
Because orangefox recovery works well with encrypted data partition. Twrp can't handle encrypted data partition.
Click to expand...
Click to collapse
i tried to flash this recovery, but sadly system has been destroyed bricked , (but now device is back in normal i flashed miui again) , i flashed with twrp recovry but it bricked my device, i think i might have flashed wrong or wrong img not compatible for this device
what should i do now ?
harsh818 said:
i tried to flash this recovery, but sadly system has been destroyed bricked , (but now device is back in normal i flashed miui again) , i flashed with twrp recovry but it bricked my device, i think i might have flashed wrong or wrong img not compatible for this device
what should i do now ?
Click to expand...
Click to collapse
I flashed miui several times with orangefox without problem. IDK what's wrong with yours...
harsh818 said:
i tried to flash this recovery, but sadly system has been destroyed bricked , (but now device is back in normal i flashed miui again) , i flashed with twrp recovry but it bricked my device, i think i might have flashed wrong or wrong img not compatible for this device
what should i do now ?
Click to expand...
Click to collapse
That's a new one! I can assure you that installing OrangeFox cannot possibly "destroy" anything. In fact, I do not see how installing any recovery (if you have installed the correct recovery for your device) can destroy anything.
What exactly did you do, and what exactly was the outcome? By the way, you might want to take this discussion to the OrangeFox forum: https://forum.xda-developers.com/re.../official-orangefox-recovery-project-t3807479