Hello, I have RR Android 7.1.1, and I want to flash new GlobeRom, but Ive noticed that my recovery dont work(not even show me a splash screen) or twrp load very long and rebooted.
What's the matter? How can I fix this?
did you try to flash recovery zip again?
@covecove1 yea, the old one, and the new, based on marshmallow. Same result ;d
Related
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
i'd tried to manualy flash the boot with my current firms boot.img and still no go... the damn touchscreen update screen keeps showing on no matter what....
thanks for everything
i change the firmware and start logo changes too so booting it's changing why the hell the touchscreen update keeps appearing... grrrrr i even installed a chinese firmware and a equivalent screen appeared i'm pretty sure it says: "Touchscreen Firmware Update in Progress Please Wait" but in chinese XD really don't know what to do anymore...
some ideas please?
i just don't know what to do anymore... does anyone knows what makes the phone try to update the touchscreen firm? today i installed the CWM in boot not in recovery just to test if the damn thing would go to the touch updt screen again and it just boot to the CMW like it should (normal because i'd flashed the CMW in the boot place). now i flash a new firmware (that will flash the correct boot.img) and the thing keeps holding on the touch update... i'm really out of ideas now
one other thing it's that if i install the TWRP in boot it won't boot in TWRP like it shoul... it stucks on oppo logo.
well i managed to install the same firm i had and have no touchscreen update... but if i install any other firm the message appear...
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.
hello,
I downloaded Flashify and I install with it TWRP (image), but I think, I downloaded a bad version, because when I restart my phone, It can't load boot screen..
- in 4.4 android I get error message: "error: can not load invalid boot image"
- in 5.0 android I dont get any info, it stops in boot screen..
I tried to change ROM (with full wipe), but it doesn't works (5.0 --> 5.0 --> 4.4 --> 5.0, etc.)
So I cant use my phone... Have you any idea? How I solve this problem? :/
thanks!
(sorry for my bad english..)
When you get into recovery does it look stock with the android there or does it show twrp.
If its not twrp you could use fastboot to try flashing a new recovery and then boot recovery after.
Then you could just reflash the fw you have before.
That could mean that you might have flashed the recovery img under boot.
Because you only restarted your phone and it just came up like black screen.
But what confuses me is you have went to 5.0 to 4.4 somehow and the problem still exists. Im wondering how you did that exactly, is it from backups or fw files from Asus.
If its the asus fw and the problem persists It might be the recovery and you might want to flash a different one.
The 4.4fw to 5.0fw should have flashed stock recovery again and the problem would have been solved. Only if you have used the downgrade fw and bootloader gets relocked
Overall its a weird problem
You could also try to flash cm 12.1 or 13.0 using custom recovery too if the bootloader is unlocked. And it should work just fine then you could go back to stock. You just might want to back up the data partition on stock then restore it after you get back to stock
Hi, I am trying to install cynogenmod or mokee rom and the device always gets stuck at cyno/mokee logo. it never goes beyond that. tried to wait for half an hour(waited for one hour twice).
Here is what I am doing:
I used TWRP but it wasnt working so i installed CWM, in both the recoveries I was wiping everything except sd card storage as my zip files were in the card. after that i flashed zip files(ROM & GAPPS). after that i rebooted to system. Am I doing it wrong? I am currently on 4.4.4 stock rom. Need help.
Thank you.
No one to help?
How can TWRP not work on your device? Install again TWRP via adb.
Flash latest twrp 3.0.2 and try
rian_tama said:
How can TWRP not work on your device? Install again TWRP via adb.
Click to expand...
Click to collapse
Rajendran Rasa said:
Flash latest twrp 3.0.2 and try
Click to expand...
Click to collapse
The problem wasn't with the recovery and I wasn't doing anything wrong. It was really too bad to know that the rom version I was installing had a bootloop bug in it. So I had tried two previous versions but they too had the same bug. And unfortunately I tried CONTINUOUSLY for two long days to install those same bugged ROMS as if God has put me in frustration mode. Tech fooled me right, lol.
Grab the November 8 version of Cyanogemod. There are issues with the newer updates.
Recently I installed Project Elixir 1.9, for some reason I decided to go to stock rom again, but I couldnt, first my TWRP was reboting all the time, I managed to solve it by installed another version, the problem now is that I cant install any rom, I mean not stock not custom rom because it is stuck on patching system image unconditionally, no matter what ROM i try to pacth, it always get stuck there and reboots TWRP, I've tried with many TWRP, Orange fox and PBRP, different versions of android and I cant do anything...
I even tried to unbrick it with flash tool and with other tools with no luck, anyone has the same problem? Anyone knows how to solve it and get back to custom rom?
As I mention I have access to TWRP and to fastboot, my device is RMX2170
Thanks a lot.