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.
Related
i rooted my milestone a few months ago (g.o.t.) and recently i tried to install the shadowsmod gingerbread rom onto it. when i restart the phone it stuck at the Motorola boot logo (M). i can enter recovery mode and do a factory reset but the problem still remains. maybe i just have to flash the stock sbf to fix the issue but the problem is that my battery is almost deplete and that the phone wont charge itself so if i enter the bootloader it'll say: battery Low cannot Program. please help me, i searched hours long for solutions but nothing worked.
Thanks in advance
Srinath
Have you done a nandroid backup? If so, you must be able to nandroid restore the Milestone, if you still have some batery left. It is usually pretty quick the restore. And if done correctly, your "stone" will be back. Next time flash the phone only when you have a fully charged battery. That would be what I would do.
Hope it helps.
YESS thank you ! i am so stupid : i DID do a nandroid backup but for some reason i forgot it! it works it really works! thanks alot your a lifesaver
Glad I could help . But you went lucky. As soon as I send the reply I though to myself, if the flash is done through .sbfs it must erase the open recovery partition. So, no nandroid restore option. But I guess you where trying to flash the roms from within the open recovery itself. So that way i believe the open recovery partition still remais untoutched. Not shure though.
Anyway, it still worked. And that´s the most important thing.
See you around.
normally if you have this problem after install a new rom, you just need to clear the cache / dalvik cache and it'll fix it
i have the same problem but i installed a rom with Droid 2 recovery bootstrap. before flashing i maked a nandroid backup but i cant get acces to restore. anyone can help me?
just reflash stock firmware. i have Droid2 Global and haved same problem but, reflashed stock firmware, root and after install bootstrap recovery, worked for me. may be helped you?
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
divibyzero said:
Sometimes when you flash new Recovery (usually when replacing stock recovery with modified recovery for the first time) you get stuck at bootloop. It means /boot partition was damaged. After flashing TWRP did you restart your phone and it booted correctly, or did you install everything (TWRP, got backup, wipe and install new ROM) at once?
There is a guide for i9001 bootloops
http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Boot-loop
Click to expand...
Click to collapse
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Got the rom working with a fresh backup after fixing the bootloop. Thanks again for the link divibyzero, the troubleshooting steps solved the problem, whatever it was, and now its running ICS
These Samsungs S+'s seem to be a little more finiky than my HTC.
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Dapper SRB said:
I am still stuck in CWM Recovery mod ! When I start Download mode, I dont have ODIN option ..only Download mod start screen! Can anybody help me?
Click to expand...
Click to collapse
What do you mean by "don't have ODIN option"?
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
alireza7991 said:
Is bootloader.tar which used to repair bootloop problem usable on ICS roms for SGS+??
Click to expand...
Click to collapse
yup, you can use bootloader or http://forum.xda-developers.com/showpost.php?p=32655216&postcount=17 CWM with AriesVe.ops
evan8683 said:
Hi folks,
I tried updating my S plus to ICS today by following the instructions listed here:
theandroidsoul.com/galaxy-s-plus-i9001-ice-cream-sandwich-update-install-cyanogenmod-9-cm9-pretty-good-and-working-rom
I read through the instructions and it looked pretty simple. I successfully installed Team Win recovery, performed a backup, wiped, and then installed the CM9 rom.
After the installation, the phone just boots back into Team Win recovery. I tried reverting to the backup, but it still just boots to recovery every time.
Now that I'm stuck in TeamWin recovery, I'm at a loss on what to try next .
Does anyone have any insight on how I can fix the problem?
Thanks,
Evan
Click to expand...
Click to collapse
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
krisslake said:
Hello guys,
I think have the same problem, this morning I installed the Team Win recovery and after a reboot my phone come into recovery mode and even after a furthr reboot I'm blocked in a bootloop that leads me always on Team Win recovery.
I tried to wipe cache, dalvik cache, factory reset and even a wipe of the system but nothing happen.
I reinstalled rom but without success.
There is a way to fix this through adb?
Advanced thanks for help
Max.
Click to expand...
Click to collapse
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Marshian said:
You didn't specify, so I'll assume you have an i9001, if this is not the case, you probably shouldn't follow these instructions
Just reflash the bootloader as explained here (http://forum.xda-developers.com/showpost.php?p=24831012&postcount=1330) and you'll be fine. I had the exact same problem when I had installed CWM on my own device. It's not with adb, but it's not like you have to do a lot of effort to get Odin or anything and it will fix your device.
Click to expand...
Click to collapse
Luckily I found a windows system
Istructions you report was perfect for my case...seem I solved my problem...thanks again.
There is some i need to do for report I solved my problem ?
Bye Max.
[Boot-Loop] Can I use dd to flash bootloader?
Guys, has anyone tried to use dd to flash bootloader partition?
I assume dd if=boot.img of=/dev/block/mmcblk0p8 bs=512 should work
Can somebody attach boot.img taken with dd so I could test?
error - can t acces system csc/cnx/system
hello. I have a problem. I had installed on the phone cm10. Now I switched to cm 9 but since we locked in botloader and I returned with odin. recowery mode now you did not have the option install from sd / card only update. My problem is that now go phone but I can not install gapps. ie install it says the installation is complete, restart give when I see me many times with yellow writing including my error appears so: can t access system csc / CNX / system. and after I start the application from google. to say you've tried many variations and if you try recovery-clockwork-5.5.0.4-phone crashes every time. Please help ... (I tried many variations of gapps). thanks in advance.back with another caveat: any clockwork I try to install say installation aborted. and in the recovery mode screen down to write I / / / status = 0 / / /
evan8683 said:
So is reflashing in Odin what you are suggesting? Sorry if I'm misunderstanding.
And yes, after I flashed TWRP it booted fine, the 2nd time I went into recovery, performed the backup, wiped, then flashed the rom. I've tried wiping both the cache's with no success. I've also tried reflashing the rom, wiping the cache's, restoring with the backup, wiping cache's again... nothing seems to be working
What would be different if I had installed everything (TWRP, backup, wipe, rom) at the same time?
*Edit* Reflashed through Odin and it worked great! Thanks for the help, I'm a little scared to start messing with the phone again, but ICS is tempting...
Click to expand...
Click to collapse
Hi Evan which release of Odin did you use I am also facing the same problem for the past 28 hours and not been able to resolve it. The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer.
Please help.
sunbaj said:
The problem is thay the Com Port does not pop up basically the phone is not being recognised by the computer. Please help.
Click to expand...
Click to collapse
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
tetakpatak said:
You must properly install Samsung mobile drivers on your PC, kill Samsung Kies process (or even better: uninstall Kies) and enable USB debugging on your phone. Then it will work.
Click to expand...
Click to collapse
The problem was that I was using Windows 8. I was able to resolve the issue after doing it on Windows XP.
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
bruce2662 said:
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But even the latest version it cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
Click to expand...
Click to collapse
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Snah001 said:
Since it seems that cwm works did you make nandroid backup before you started fiddling with the Rom? ( basic rule nr.1)
When not go to the boot loader screen and do a factory reset there (third icon from left).
But maybe you can do that also from within cwm but I do not know if it is in there.
The official update zip you must unzip that first and then put the new zip on the sdcard, can't do that from cwm.
Let it reboot and it must start flashing.
Click to expand...
Click to collapse
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
bruce2662 said:
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
sorry for my bad english
Click to expand...
Click to collapse
Wipe data is like factory reset.
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Snah001 said:
Wipe data is like factory reset.
Click to expand...
Click to collapse
Sorry to disagree..
I would NOT wipe from the bootloader with a custom recovery installed! People have hard bricked their tablets that way!
Unzip the firmware package and put the zip on your microSD. Then reboot and let it flash.
This way you get all a clean fresh install
Click to expand...
Click to collapse
That works only with the stock recovery, not with a custom recovery. But you should be able to flash the once unzipped firmware in CWM. That would flash you back to stock, including the stock recovery.
Next time you install CWM your first action should be to make a nandroid.
If it doesn't work please explain why and what. Just "doesn't work" is not helpful - do you get error messages?
Explain - in detail - your steps.
Since you said you flashed CWM you do have fastboot access?
Forgot that you aren't on stock recovery.
When you still get into the recovery did you unzip the factory firmware zip before you tried to flash it?
First give that a try.
Volume-up + power pressed normally would get you into apx mode but since we have no Nvflash files available you can't do anything with that.
So unpack and put the factory firmware zip on you sdcard and flash from custom (think you have cwm installed) recovery (choose install and choose the file you put on your microSdcard).
Del msg
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
ToneyEricsson said:
Hi I got an issue today with my TF701T can anyone help.
I got a prompt for installing an update, downloaded it, installed and on reboot the TF701T is stuck on the ASUS Splash screen.
How do you reset this device? I'm new to this TF701T
Click to expand...
Click to collapse
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
berndblb said:
There are a number of users with the same issue. Asus seems to have pushed an incompatible update to WW users (Man! They are really scre*** the release of this device! Unbelievable...)
Head over to the General section, there are a couple of threads dealing with this issue. The fix seems to be to wipe data and manually re-install the 10.26.1.7. (and ignore the update notifications you'll get again!)
But read the threads before you do so...
Click to expand...
Click to collapse
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
ToneyEricsson said:
Sure buddy I will be reading xda before installing any updates from now on!!! Thats really bad ASUS pushed this update out that gets owners of the TF701T stuck on the Splash Screen after updating.
Click to expand...
Click to collapse
Haha funny :cyclops:, same problem for the UK devices too (i see you´re from London?)? OMG!
I´m a german user and a bunch of peopole here also had this kind of issue after they did the last update from 4.3 to any newer release, since 27th dezember 2013 there´s no valid reply from ASUS and (for my understanding) the invalid software update is still on the servers and get sent to the EU users (...).
@ XDA: do you know, where i could find out the local storage where on my device the *.zip (or what ever) is saved, so that i could manually delete it? To make sure i´ll receive a newer one in future? Or did this (incorrect 250,8MB file) will be replaced by the newer one?
Regards
Silver
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
where can i delete this file
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Snah001 said:
Try the root of your internal sdcard or in the download folder.
Sent from my Asus Infinity TF700 with Dock
Click to expand...
Click to collapse
xistentz said:
Hi guys,
i've got the same issue, sent the device to the service and replaced a part of it, but because they've went over the 15 days period where they should have send it back ( fixed or not) I got a new one.
i updated to 4.3 and this time again i got prompted to install the crap update, but i didn't. Now i want to delete this file but i can't find it. if my kid or someone else will accidentally say OK to the update i'm back to older version ( at the best) .
so will be highly appreciated if anybody will provide a solution to remove this file.
thx
Click to expand...
Click to collapse
It'll be on the cache partition, which you can only access from the stock recovery - you'll need to boot to nthe boot loader, choose rck and mess around with power and volume up / down until the menu appears. Then choose wipe cache. But it will come back when you next check for an update......
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
re: bootloops
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
You need to ODIN flash the stock original official COG2
firmware & odin flash cf-autoroot and the twrp recovery
before flashing the zip file rom.
Once that's done you can flash any N910T zip file rom in
twrp recovery without any issues.
Make sure to do a full wipe in twrp before you flash any
zip file rom to avoid bootloops and or getting stuck on
the samsung boot logo screen and be sure to do a full
and complete wipe which includes:
"System, Data, Cache, Dalvik Cache and last but not
least do a factory reset.
Good luck,
Have a great day!
Tharkys said:
So I've been attempting to install a rom, ANY rom on my phone and the results always seem to be the same. I boot into TWRP, wipe then install the rom. On reboot, the phone loads up the initial (black) samsung screen. Then buzzes twice and reboots. It will do this infinitely. It happens with any rom I've tried flashing. It has to be something I am missing or doing wrong. Does anyone have an idea what it is? I've even gone as far as completely wiping, odin in a stock image and then adding TWRP again. I just can't seem to figure it out.
Click to expand...
Click to collapse
i dont know if we are having the same problem but try installing the original firmware via odin and see if that works. if it does not then we have the same problem and i dont know how to fix it, now i am stuck with my S4 wait for help from someone to help me fix my note 4
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.