So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
TribalPaint said:
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
Click to expand...
Click to collapse
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
bogarty said:
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
TribalPaint said:
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
Click to expand...
Click to collapse
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
TribalPaint said:
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
Click to expand...
Click to collapse
Update:
I fixed my phone, and here's what I did, so if anyone is new here with the same issue I had, I hope this can help you. So first of all as I said I kept booting to TWRP, later I tried reflashing TWRP, but I remembered that I missed something in ODIN, so I just pulled the cord and my screen after rebooting just said something along the lines of "An unexpected error occurred while updating software, please recover using Samsung Smart Switch." after that, I tried Samsung Smart Switch, but it was no luck for me, so then I used the last resort. I went on sammobile.com, I searched stock firmware for the exact model I had and then I checked the stock firmware that was available. Since I'm from Latvia, I picked the Baltic region, then I downloaded the latest stock firmware. After a long time, I downloaded the file, and I checked the instructions on how to flash it, I flashed the stock firmware, and then my problem was fixed, my phone was working again and now I have Android 7.1.1 as I used to have Android 6.0.1 and I had ZERO file loss However as you flash the stock firmware, TWRP get "flashed" out and same with root if you have it, and in that case if you want TWRP and root again, I highly suggest Meziani's YoutTube channel, because he gives simple and working tutorials on how to do it I'm glad if this helped anyone.
Related
Hello,
I flashed CM11 yesterday and everything went alright. This morning I noticed I had an update for it and proceed to do it.
After the instalation and optimizing all apps it asked me for my simcard PIN and after I unlocked the phone it just went back to the cyanogenmod logo over and over.
I tried to reboot phone but it didn't help.
I've tried to search for similar threads but since i'm a newbie (first time I ever flashed anything) to this I decided to create this thread.
What should I do?
Thank you!
try to use flashtool. google it on how to use flashtool or check other threads.
So I guess i have to flash a stock ROM with flashtool and do it all over again right?
And btw, any reason you guys might think It got stuck in bootloop after I updated CM11? I came from a fresh stock rom. I'm kinda scared it might happen again after the reinstall.
Can't you enter recovery to flash a nandroid backup? (If you have one)
If not, you have two options to choose from.
Fastboot or flash a kernel with CWM or TWRP.
ADB push a zip file of a ROM and flash that.
Flash an FTF file using flashtool and start all over again.
There are many reasons why you're stuck in bootloop at the moment.
With the info you provided, there's no way of telling what caused it for you.
Well, i flashed stock ROM with flashtool, installed CM11 and I had no problems.
Went to settings and OTA update was available. Downloaded it and installed it, stuck in loopboot again. I just can't figure out what's wrong. My phone has bootload unlocked.
Might just do it all over and not update, is that a problem?
Don't use OTA, just download and flash updates manually using recovery.
In the future, for your ease, if this happens again just wipe the phone very clean (cache, /system, /data etc except /boot) and then re-flash the CM zip that you have.
It is a good practise if you make a nandroid backup before flashing a newer version of zip, in case of breaks. Or, you can have Titanium Backup to backup your apps automatically (pro version) everyday, so that you can be ready if there will be something bad happen.
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked
Edit: The flashable zip seemed to be a good workaround and got everything done in one go. Fingers crossed from here on in.
Hi guys, this is my first post here, so please go easy on me.
So recently my phone screen cracked and I had to send it off for recovery.
The company wiped and upgraded my firmware, but I did my data backup as a nandroid backup, so I have to get a recovery installed to restore it.
I have managed to unlock the bootloader and flash this version of the firmware : - D5803_23.4.A.1.264
I am simply trying to root the phone so I can get SuperSU onto it and the method I used last time uses CWM. However, when I try to install CWM I can access CWM, but otherwise, it goes into a boot loop and I have to reflash that firmware to restore it, which deletes the CWM. The CWM version I can flash does not seem to be able to restore nandroid, so it's fairly useless.
i have tried downgrading but then the phone crashes on startup. I noticed when I restored to the current firmware above, the phone had kept all my settings, so I don't know if there's extra I need to wipe, or if I'm not flashing correctly.
Now I have used PRF tool to create a flashable zip, that I thought might be able to do the job for me if I can get something to install it. It has the working firmware, SuperSU and dualrecovery in it.
I have done this all before without issues, but the new firmware version is making things more difficult.
So questions are;
1. Am I flashing incorrectly when downgrading? Or is there some other factor at play preventing me from doing so?
2. Is there a way I keep the CWM and flash the working firmware? Like it would go into boot-loop but then I could get the normal systems operating again and have the phone rooted, continuing the work. I figured there might be an option in flashtool, but I didn't want to press anything without confirmation from someone.
3. Is there an easier way to froot this? Last time I was able to use giefroot, but now it says my kernel isn't supported.
Any help would be greatly appreciated. I'm not new to modding my phones, but I'm not advanced either. Let me know if there are other details I can give that might help.
Thanks.
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
slifer225 said:
So the case was I reset my device, and later after i flashed a ROM into my device, it does not boot. Instead, it goes into TWRP recovery. And it goes to TWRP every time i boot my device.
I have done this for so many times and I cannot even know what is going wrong this time. I am quite frustrated and I did googled a lot but it did not solve my problem. So, I want to know if anyone else encounter similar problem and solution towards it.
I tried:
1. Wipe the dalvik cache.
2. Remove the battery for half an hour
3. Reflash the twrp
Any efforts and reply is much appreciated.
Thank you.
Click to expand...
Click to collapse
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
slifer225 said:
Well i have took the ultimate solution. Back to stock firmware fix everything. Well, i guess not much to mention on stock firmware=)
I think you should do the same thing too. Good luck.
Click to expand...
Click to collapse
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Yes, i flashed custom recovery and ROM afterward. Even several attempt on wipe and flash the new ROM. So i guess it should be fixed
Thank you.
andydgg said:
Mine's exactly the same, I factory reset so I could pass the phone on; and now it will not install custom roms, I've tried about 7 or 8, and it will only boot into twrp 3.0.2-5. Soft brick, but I'm unable to find any solution.
Here's hoping someone will come and help.
I think I'll have to reinstall twrp by connecting the phone to the computer, but I've no idea how to do this.
Click to expand...
Click to collapse
As slifer225 mentioned you can downgrade to stock firmware by installing the stock MM rom s433 version using spftools.
Download and Install stock MM rom using spftools.
Here is the link- https://cloud.mail.ru/public/Cco5/JYk3ytrW1
For further info follow this post- https://forum.xda-developers.com/k3-...3#post71749243
Follow this step by step guide to go back to unrooted stock rom. If you want to root after that then try installing custom recovery(twrp) again using spftools and flash supersu.zip using recovery. Do take a backup though before rooting your device.
---------- Post added at 10:11 AM ---------- Previous post was at 10:04 AM ----------
justwondering said:
That is good to know, I shall attempt to do the same, did you later install a custom rom and everything was fine afterwards?
Click to expand...
Click to collapse
Everything is working perfectly as I myself had gone through the same issue and did everything to fix the problem until I downgraded back to stock. Did root on my device again and installed lineage 7.1.1 and it works like a charm. One thing I love about this rom is the efficient ram management, lag free but battery management is not upto the mark but I guess we can work it out.
Whatever you do never forget taking a backup of functional rom.
Yes, I can confirm the solution worked for me, I left it with stock rom for my friend, I tried lineage 14.1 and did a factory reset, but ended once again with softbrick , lineage will install and work perfectly, but as soon as you do a factory reset, soft brick
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Wondering...
justwondering said:
Exactly the same issue here too, installed lineage 14.1, was working great, I was selling to a friend, did a factory reset, now stuck at twrp, roms install etc, but after a reset, every time straight back to TWRP.
Looks like I might need to flash back to stock somehow.
But I did find this, but not yet tried.
https://www.reddit.com/r/LineageOS/comments/5riech/how_fix_twrp_recovery_boot_loop_after_lineageos/
Click to expand...
Click to collapse
I think that solution only works on Snapdragons. It didn't for me. Is there a solution for MTK devices?
the solution for this(FIX)
all we need to do is reinstall a stock recovery and the again reinstall the TWRP
https://forum.xda-developers.com/k3-note/general/ufficial-thread-lenovo-k3-note-t3102997
follow this link..my phone just got fixed
My phone TWRP-looped many times. The solution is actually easy.
1. Reflash using SPFlashtool ONLY the stock recovery
2. boot into stock recovery
3. choose english > press reboot phone
4. phone will reboot into rom without problemos
5. reflash TWRP
cheers
or
1. Copy stock recovery.img into sdcard
2. In twrp, select Install and navigate to where you put stock recovery.img
3. Press install image. Then, Select recovery.img. Slide to install
4. boot into stock recovery
5. choose english > press reboot phone
6. phone will reboot into rom without problemos
7. reflash TWRP
DONE
Infinity loop recovery
andydgg said:
Now I've hard bricked it. I loaded up a 'looprecovery' when it rebooted there's nothing, no charge light no vibrations PC doesn't see it, land fill?
Click to expand...
Click to collapse
hI MY FRIEND , you have been able to fix your K3 note, I have the same problem, I made twrp flash and went into infinite loop. Can you help? thank you
I smashed it and put it in the bin. I think once you can't get a charge light after tyring for a couple of week, it's dead.
Not working for Lenovo K3 Note.
My K3 note stuck in the twrp recovery after factory reset from the RR. I tried this solution but it didn't work.
Please help.
Hi guys
Hope you are well, just wanted to find out, i rooted my phone using the patching method (Magisk). Thereafter i installed TWRP (Placing TWRP / VBMETA file in one archive) Flashed it, and it worked, i was able to log into recovery, i then formatted data, rebooted and wiped Dalvik etc etc. (Note i did not install the Multidisabler (The instructions i followed did not mention anything about it) I then installed LOS with GAPPS,
I know would like to try and either install Beyond ROM, or if need be back to complete stock (CTF3) as im missing DEX.
Can i just log back into TWRP - WIPE and installed Beyond ROM? (As we used to do in the old days - jumping between ROMS) Or should reflash MAGISK TWRP process everytime? If this is the case i would want to rather move back to stock...
Can i just flash back in ODIN and all will be good? Or is there any risks? (Ie in bricking the device etc)
Have you checked out this thread?
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
StoneyJSG said:
Have you checked out this thread?
https://forum.xda-developers.com/galaxy-s10/how-to/proper-to-root-s10-device-twrp-s10-10e-t4015813
Click to expand...
Click to collapse
Hi there! Thank you very much, this is a fantastic guide. Exactly what i was looking for