I had RNE-L21C185 with Stock Oreo updated
Then flashed Mofruz latest rom working fine, but then I tried to install Stock recovery, I was not able to do so
as it would show error with partition etc. Then tried to install the same TWRP from Morfuz ROM back again.
In fastboot mode I already have PHONE Unlocked and FRP Unlocked messages
So either Morfuz ROM TWRP or any other TWRP recovery, show properly completion of flash command
But when tried to boot into recovery it goes in a loop (the loop shows phenom image, then shows the default
screen that is shown before launching of recovery), then restarts again, and it goes on loop.
So I dont know why I cannot get to load into any of TWRP I have.
The ROM is working fine, if I properly shutdown mobile and start it again, it boots to the phone and
I can use my phone as normal.
Any help guys ?
try to flash stock rom via hisuite
http://huawei-firmware.com/rom/huawei-mate-10-lite/rnel21/8437
or try one of these twrp
https://mega.nz/#!GxsAUQaS!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
https://drive.google.com/file/d/1_dfpSOCD23Oz_LexYMn1JNRVfrlvKU-x/view
https://mega.nz/#!OzQ3GCJK!ofjiXcb7VRpGkhrd1vwXrVeSAO2vF1BVYLYRX2fExn4
.
Thanks problem solved by:
Tried to use fastboot command to flash official stock Kernal and ramdisk (Oreo version) phone got no OS after it as
it will go on bootloop, now even the forced download (dload folder) method wont work, factory data reset wont work
(both of above will show EMUI circle with no processing or text whatsoever)
At this stage, flashed Catuva recovery from Morfuz ROM again, and it worked
Related
Hello @xda
I ran into some ussues lately with TWRP and M5 kernel made by @Myself5
Until last week I have been using M5-kernel with Validus ROM, and it has all been running smooth. I have been able to open TWRP during boot with volume keys and all was joy. Then I decided to try MultiROM and I got that working with the app.
This monday I decided to get rid of it and cleaned my phone.
Then the issues started. I replaced MultiROM TWRP with TWRP and flashed boot.img from validus zip. No problems entering recovery and I successfully flashed the zip and gapps for it. I used his latest version with M5 included. Booting into the ROM was not a issue and it all worked fine until I was trying to get into TWRP.
As I always do before I backup my phone, I shut it down. Then I booted it and tried to enter recovery, the purple light came on, but nothing happened when pressing any keys...
To enter the recovery i had to boot the ROM and reboot to recovery, witch I did not have to do before. I tried all possible solutions, in the end I decided to try with the kernel from a earlier Validus version, and guess what, it opened TWRP.
Is there someone that can tell me WTH I'm doing wrong??
I always do a
<fastboot flash recovery twrp.img and <fastboot flash boot boot.img
I was running the 8/3 update of Cyanogenmod 13 just fine on my L24. I downloaded the 8/13 nightly from the CM website and tried to flash it, but for some reason it returned error 7, which shouldn't happen because I already updated to EMUI4/MM firmware two weeks ago (as evidenced by me running the 8/3 version with no problems). However, when I then tried to boot back into system, the phone instead booted back into TWRP. Trying to boot into system in any way (from TWRP menu, through bootloader --> fastboot reboot, et cetera) just reboots the phone right into TWRP again. -_-
Now, I can access only TWRP and bootloader, but whenever I try to flash a .zip in TWRP it immediately reboots back into TWRP. I've tried reflashing TWRP (newest version and older versions), flashing the Cyanogenmod recovery for kiwi, factory resetting, and even reflashing the stock recovery and trying to return to stock EMUI. None of these have worked. (And yes, of course I've tried clearing cache/dalvik.)
At this point I'm just looking to actually boot into system...If anyone has any idea how I might be able to fix this, it would be great.
EDIT: to clarify, when I try to flash the ROM in TWRP, I get the following:
updating partition details
full selinux support is present
MTP enabled
and then an immediate reboot. This is very fast - I had to take a video of it and then freeze the frame to see what the message was.
Boot in fastboot and install your crap? Turn phone off connect to your PC hold Power and volume down until it boots.
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
radiobacter said:
Thanks for responding!
Could you explain what you mean? I can easily get into fastboot, but I'm not sure what I should be installing. Trying to install the ROM gives me the android-info.txt/android-product.txt missing error, which makes sense because it's not a fastboot ROM. What file should I be installing through fastboot?
Click to expand...
Click to collapse
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
clsA said:
fastboot flash recovery twrp.img
reboot with power + volume up and down
from TWRP
Install / yourRom.zip
Install / gapps.zip (if needed for cm13 based roms)
reboot / system
enjoy
Click to expand...
Click to collapse
Again, the issue is that I can't install any ROM through TWRP, because trying to instantly reboots the phone and brings me back into TWRP. I've tried reflashing TWRP, but it doesn't do anything.
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
radiobacter said:
Update: I fixed it! For some reason TWRP was recognizing my SD card up until I started flashing. I just put the ROM in my internal storage instead of the SD card, and then the ROM was flashed with no problems. Thanks to those who tried to help me out!
Click to expand...
Click to collapse
The phone is known to be finicky about sd cards. Try formatting it with TWRP
Sent from my SM-N920T using Tapatalk
Trying to install TWRP to flash a custom ROM, but still without success.
After trying the first few times, holding Vol Up + Power either booted the stock recovery or just booted android.
Then I tried to boot recovery directly through adb commands, and since then recovery is in a bootloop even if I flash TWRP again.
Is there any sollution? I also tried installinh through the TWRP app, but cant flash because it requires root and in order to get rooted I need TWRP...
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
-FliP- said:
Fixed the bootloop, apparently the twrp version in a guide was wrong, so I used the version that the twrp app downloaded.
However, fastboot boot recovery.img successfully flashes twrp, but boots into android instead
EDIT:
Got TWRP to run, but it is not recognizing any storage. Therefore, useless again. Figured that the latest version of TWRP for Le Max 2 does not run at all, the oldest version as well as the lowest 3.1 version do run, but do not recognize storage
EDIT2: fastboot boot recovery.img does work and twrp now recognizes the storage for a safe backup. Hope this helps others with the same problem
Click to expand...
Click to collapse
Interesting. Have you tried Androbench?
So which version are You running right now?
Ricky_Karmator said:
So which version are You running right now?
Click to expand...
Click to collapse
I dont even remember to be honest. I think I used the base 3.1 version and got it to detect storage by starting it with the boot adb command. If I run twrp by holding power and vol up, it never detected storage.
I got the same problem with my device X820 6/64 with 19S rom, any TWRP is able to read/write on the internal storage I install TWRP from 3.0 till 3.1.1.1 . What can i do?
Thx
Aj
So my phone doesn't boot to Android anymore.
(Huawei Y560-L01)
A while back I tried flashing a custom ROM but it failed and I couldn't get past recovery mode anymore.
Today I tried to get back to Android but no succes.
What I tried:
- Flashing a ROM (Stock/Recovery) using adb/fastboot.
- Downloading a "update.app" file of the stock firmware and flash it from the recovery (with an sd-card).
- Hard reset / wipe everything and reboot.
adb isn't able to detect my device because USB-Debugging is disabled and there is no way (as far as I know) to get it back into debugging/OEM-unlock mode. (Can't boot past recovery mode and bootloader is locked)
The update.app file I found doesn't work.
I'd love to get my old phone to work again. Any solutions to my problem?
Thanks in advance.
P.S. Is Android still installed or is the OS wiped, I'm not sure?
My phone has screen issue its stuck on logo. I can't flash combination because of the new security Samsung created. I get the message please get approval to use factory binary(PIT)
I have unlocked bootloader and twrp installed, Is there a way to extract the files from the combination rom and create flashable zip to flash that via TWRP?
My Phone is Samsung Galaxy M31S running latest U3 stock rom. Twrp can be installed easily but after the system is booted and If I restart it shut it down I get only official binary are allowed to be flashed. Screen works and is not stuck in twrp but when it boots to system its stuck at first logo/unlocked bootloader screen.
Thanks!
Hello! I have the same problem and the same question.