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...
Related
please forgive me if this has been asked before. i've tried searching but can't seem to find any fix. my phone was working great but i wanted to try a new rom since i was getting bored. my mistake.. anyway i have CWM recovery on my atrix and it worked good. i've flashed roms before.i was flashing between Neutrino ROM V2.9 and V3 trying to see if i could get the CMsettings to work on V3 without crashing. anyway after a while i gave up and decided to full wipe and just flash V2.9. after the ROM flash i reboot the phone but got a boot loop so i pulled the batter and tried to boot into recovery to wipe and flash again but when i select Android Recovery it just hangs at a black screen. what happened? can it be fixed quickly because my battery before the final flash was about 30%
BTW.. i've tried to reflash the recovery through fastboot and my compute the way i did it when i fist unlocked my phone and flashed the recovery but still no luck... still hang at blank screen after selection Android Recovery
never mind i fixed the problem.... had to flashed a different recovery (in this case TWRP) and then flash back to CWM recovery. idk the reason why but it worked and now my phone is back on and just in time with only 5% battery life left after all the trial and error flashing..
ok i figured out what caused my recovery to crash in the first place. its the gapp addon. when i flash that zip and reboot i get a boot loop and my recovery is gone. first i though it was the zip file that was damaged so i re-downloaded the gapp addon from Neutrino ROM V2.9 fourm but now chrome says the zip is infected so ok i went and download the full gapp addon for CM7 rom and that flashes without crashing my recovery but when the phone restarts i can't access half the gapp like market and gmail and a few others. they show that they are installed in Manage Applications but they don't show up in the app drawer.. whats the problem now? i've never had this problem before
Hi everyone
My sister updated her MEGA OTA last month. She cant remember which version she was on. I am assuming it was 4.3. shes doesnt know much,
Her phone got stuck in bootloop.
Initially a got a hard time even getting into restore mode. however after a lot of goggling and trials and errors here is where i am today :
1- I can install TWRP and/or Philz recovery and boot into them.
2- I can enter download mode
3- I have tried installing many ROMS and different versions. I was only partially successful with 4.4 versions because I get a passed message in Odin however upon restart the phone enters boot loop again.
4- I have tried multiple wipe data/dalvik cache/cache and restoring factory settings but i still get the same results.
5- Only in Philz recovery i can mount the external SD card and copy zip files. I was able to root the phone that was (but im not sure if it still is). However all ROMs zip files I tried to install (both from PC and from extSD card) wouldnt open in recovery mode.
Because I get a passed message when I install a ROM from Odin , I dont know what the issue could be. But there is something wrong that happens as soon as this phone boots up.
I seriously do not know what to do anymore. I just need this phone to be working again. At this point I dont care about warranties/ROM versions/stock or custom...
Please help and sorry for my bad English
It sounds like you need to download the stock rom and flash it in Odin (you gotta put the phone in download mode to flash in Odin). The stock rom can be found on the sammobile website in the firmware section. That should get you back to square one (stock rom, stock recovery, no root). Then you start over from scratch.
Sent from my SGH-M819N using XDA Free mobile app
Thanks
I did and I still get the same problem.
In fact after installing stock rom, i could not enter "stock" so I installed philz recovery, logged in philz and wiped cache a couple of time, did a factory reset.
and yet when i restart , the phone is stuck in bootloop.
Maybe she has a Galaxy Mega with a repaired screen. Starting with 4.4 Samsung only supports a digitizer with Synaptics brand chip. It's a big mess and there are countless screens and digitizers made worthless. I think unofficial 4.4 by Cyanogen and others might work, but not official Samsung. With some Galaxy Megas you get a bootloop. With others it boots however the digitizer and touch functions no longer work. I don't know how to go back after you are on official 4.4 because last I saw, there was no root for it. If I'm wrong, someone else please clarify and continue to help.
IMHO only one way out from such situation is try to flash MegaFire MJ2 which is derived from stock 4.2. It's only one 4.2 ROM which can be safely flashed onto KK.
Iformation about MegaFire you can find HERE
I workerd some days before and i dont know what happend.
I unlocked my bootloader and did pretty much everything. Ive installed cm12 and everything worked perfectly. Only thing that annoys me was the Cyanogenrecovery that forced me to flash twrp manually after every update.
The TWRP App says i got 2.8.4.0 installed. But i cant boot into it. The Led blinks pink and then it goes off and cm starts booting like nothing happend. I tried to reflash the recovery but it did not work.
Please help, i just want to update cm and install xposed
xan_asmodi said:
To gain a persistent recovery, one needs to flash a recovery to the fota partition as explained here: cant post twrp sirius link here bc xda spam prevent...
I figured that it was an error with Infected's CM12 nightlies. I flashed the latest boot.img and I was sorted.
Click to expand...
Click to collapse
this fixed it for me ^^
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 everyone,
I own a samsung galaxy s2 gt-i9100 I've been using it for a long time. A few days ago i installed cynogenmod 13 marshmallow on it but faced some severe issues like dialler problems,battery drain,google play services not working. So, i switched it back to my previous rom i.e. cm 12.1 lollipop but my old twrp recovery got replaced by cynogenmod default recovery. Now some people who may have used it know that its very basic and does not has backup,restore, has bugs,does not flashes some zips or files that i wanted so i tried to replace it with twrp/cwm through rashr,flashify,rom manager,etc. But none of it worked, whenever I'd boot after flashing the twrp/cwm recovery it'll go back to the default cynogenmod recovery. Now, me not knowing what im doing stupidly downloaded mobile odin lite app then i downloaded the cwm kernel recovery kitkat compatible and installed via mobile odin lite. After that it got screwed, it won't just startup it'll just start and go into recovery i mean continuously! It was annoying, then i read an article on a forum to download any cm nightly or stable mod and flash it but i did a little bit of tweak of removing the recovery boot img file with twrp to get preinstalled twrp recovery but i gotta admit it was the last mistake possible. Now i sit here, with a bricked phone in my hand which is looping continuously only on the samsung logo. If anyone out there can assist me correctly it'll be a life saver for me. Thanks for reading this and please reply with a solution asap. Please! Im in danger!
can you get into download mode?
if yes you can download a stock firmware and flash but you will have to hope it will work, otherwise you will get stuck on nand write start which means the nand is stuffed/corrupted and then basically only a motherboard replacement will do the job, or you can try using another computer, reinstall usb drivers..
can you get into recovery mode?
if you can, you can flash a rom
The 'nand stuffed' assumption is a last resort, tried everything and nothing works assumption. There is *plenty* to try before assuming that the nand is 'stuffed'......
It sounds like (from your description) that you may have rendered recovery useless and inaccessible.
I've a feeling what you need to do is to go into download mode and Odin flash a firmware.
Even if it doesn't boot, you should have a recovery that you can flash PhilZ recovery from and then use that to flash a custom rom. Initially, I'd stay away from the MM builds and instead flash something KK or LP based as they're less 'volatile' and have a higher degree of stability than the MM roms.
http://i.imgur.com/rVnFwJM.jpg