I have my rog 2 stuck in a bootloop. I don't really know why in the first place, because I don't like to change and mess around with custom roms. So i've never done that.
The case was that I was watching a video on YouTube and suddenly the touch screen stopped responding, the phone kept responding to other inputs such as the power button and the volume rocker. So I decided to restart the phone. And then it didn't turn on again. Got stuck in a boot loop.
I've been trying to fix it for a long time. But I just can't do it. Nor am I able to see what is happening with the phone. I have used this guide.
EVERYTHING works perfectly, it doesn't give me any errors during flashing or anything like that. Even the program tells me that the rom has been flashed correctly, and even the rog logo during boot, changes (I suppose because it is a version of the rom prior to the one I had.). The fact is that even with that the phone is still stuck in the bootloop. I have tried more things but this is the one that has taken me the furthest. I don't know what else to try. If anyone has any ideas, please tell me.
P.D. Sorry if my English is a bit rusty.
go back to stock and try other rom.
atoyu said:
go back to stock and try other rom.
Click to expand...
Click to collapse
Any suggestions which rom I can use? I have tried the rom of the guide and the ones that Asus has on their website. None of them have bailed me out.
@Arnau17 Any Updates? I am facing the same issue. Mine reaches till boot logo and then freezes and reboots again. Tried flashing stock ROM as well but no Luck
I am in the same situation, tried several raw rom files, still in bootloop
USB plug correctly on side USB port? can you enter recovery or fastboot mode?
i have same problems before, if fixed after flash RAW rom, hope this help.
is there a guide to fix AVB VERIFY FAIL on Rog Phone 2
Related
Alright, here's the story. I needed to unlock my phone, so I looked up a few guides. I found one that I like and was checking to see if the ROM I had installed would allow me to enter in my unlock code after I got it, unfortunately it wouldn't. So I decided to flash the stock ROM for my phone. Odin did it's job, and everything seemed to go alright, but after Odin finished up, the phone still remained in the boot screen. I let it sit for a while, and it continued on for about half an hour. I restarted it, went to go do some things. I came back hoping that my problem would be solved, but nope, still a looping boot animation. Has anyone else had this problem, or have some idea on how I might work around this?
TLR; Phone is stuck on boot animation after flashing Stock ROM.
skribel said:
Alright, here's the story. I needed to unlock my phone, so I looked up a few guides. I found one that I like and was checking to see if the ROM I had installed would allow me to enter in my unlock code after I got it, unfortunately it wouldn't. So I decided to flash the stock ROM for my phone. Odin did it's job, and everything seemed to go alright, but after Odin finished up, the phone still remained in the boot screen. I let it sit for a while, and it continued on for about half an hour. I restarted it, went to go do some things. I came back hoping that my problem would be solved, but nope, still a looping boot animation. Has anyone else had this problem, or have some idea on how I might work around this?
TLR; Phone is stuck on boot animation after flashing Stock ROM.
Click to expand...
Click to collapse
Enter recovery and wipe data
Sent from my Sony Tablet S using xda app-developers app
[B]thats the hardest brick man[/B]
happened to me while doing something stupid to my kernel... believe me it is impossible to fix.
i took it to my ISP they said its liquid damage but it wasnt i knew... they said BER(beyond economic repair)
so i took it to samsung and collected it after 10-15 days. from the looks of things they changed my motherboard.
you can return it even if warranty is void(they cannot tell if its void or not)
mine only blinked when i tried recovery,download or charge and showed logo when i turn on only.
Hi There,
You will need to enter the Recovery Mode and Have a Factory Reset and Wipe Dalvik cache. If the device doesnt enter recovery you can force it to do so using JIGG or Heidmall. After wiping if still no progress. You should check whether you have flashed the correct stock rom according to your Country.
Droid 4 running Stock Jb 4.1.2, Safestrap 3.11, Liquid smooth 2.9, CM (last stable)
Everything working fine for a number of months, installed Liquid smooth via -> delete romslot 3, create romslot 3, install Liquid 2.8.
It ran for a number of days no problems. Restarted fine, all features worked great, even the annoying random restart from 2.4 went away.
6 - 10 days in, im surfin' the news sites at work, put it down, screen goes black, i pick it up. Hit the power button cause i realize its off and it just boot loops... so bad i had to vol-/+ pwr, go to flash mode and THEN turn it off b/c it just kept trying to restart, hang on logo.
I got home and decided to AP flash the latest:
9.8.2O-72_VZW-18-2
Blur_Version.98.72.182.XT894.Verizon.en.US for the maserati.
Boot looped a few times, i was able to get it to go into recovery mode, after that it loaded up the stock JB system. First boot it crashed and restarted, second boot it loaded but only the keyboard worked, not the touch screen. Went to the in OS option of factory reset mode + delete storage.
Rebooted, worked. Checked it a few boots, everything is fine. I use Druid 4 Utility Xt894 JB version and apply the root. Works great. Install safestrap, Create new partition, install liquid smooth 2.9. Works for an afternoon... at work today the touch screen stops responding, i restart it a few times. I try to enter recovery mode. Now im in boot loop again...
I've tried re flashing it again, a few times. I tried even going down to the previous release of JB for the phone. STILL 4.1.2!!!! But nothing.... it just boot loops... what did i do wrong? It was running great. No tweaks or anything done to it prior to it having its melt down.
Help please.. ive provided as much information as possible and though i only joined XDA now to post for help, i have read it for a long time as my main source for my phone and have donated to both CM and Liquidsmooth teams previously..
help!!!
I can't see where you are doing anything wrong. You have obviously done your research and have a good idea of what you are doing. I see, after you fastbooted, you went back to Liquid. I think I would try running CM10.1 or even stock for a few days and see if you have the issue there as well. If you do than it sounds to me like it might be a hardware issue. If not, maybe try re-downloading Liquid. Perhaps your zip got corrupted somehow.
I would love too. In fact i would be willing to run it on the stock crappy 4.1.2 if i could get it out of boot loop this time...
It just keeps boot looping on the logo. AP Fashboot flash and BP flash work but recovery and normal boot/reboot mode just goes into M logo boot loop.
I've re downloaded the 4.1.2 jb SBFs from 2 different sources to ensure its not a corrupt file, tried 18_1 and 18_2 software versions...
Is there a way to use the abd shell to get into the filesystem and check whats going on? Is the SBF the last call? or is there another route to see whats going on or just flash EVERYTHING? Like completely back to stock?
I can find my way around a PC file system but im not familiar with linux. Please help me understand, Is it like having CMOS and BIOS settings or equivalent to damaged CMOS firmware? What am i not replacing/reverting by SBF and HOW can i replace/revert BEYOND the basic sbf...
If ya point me in a direction or to someone who can help me out i can do all the foot work just point me in the right direction?
Is this applicable? I found a site talking about using CWM in a ADB shell file push to possibly get access to more features?
The article also goes into reading the busybox / ADB command screen? (sorry for not proper jargin) and see what its doing during the boot loop before it restarts?
Id add the link but i need more posts....
Update: Flashed 18_2 again with a "factory cable" i made, let it boot loop a series of times before it started up into the stock system again.
At first, again the touch screen wouldn't work, random lockups and restarts, etc. Since i just got it into the main system again and i had to leave for the weekend for a trip(no wifi or network), i couldn't mess with it all weekend but i left it on the whole time and kept checking its functionality... gradually its come back to full function. Touch screen works and is accurate, no more lockups, no more restarting, even stopped boot looping when i restart and enter recovery..
Im not sure and i couldn't find any forum converstations or write ups to support to idea but i think after a major crash and you flash new or reflash your SBF, it seems the phone needs time to recalibrate and index? Not sure, but just an FYI. Gonna try loading SS and liquid again.
Hi, i'm kinda new to all of this, so literally any help is appreciated.
I recently rooted my S6, and managed to get it stuck in a boot loop on the Samsung screen, with the logo in the centre, slowly fading from light to dark repeatedly.
This happened when i accidentally logged out of my snapchat, causing it to detect my device was rooted and wouldn't let me log back in. I got around this by updating my superSU and disabling it as i logged into my snapchat. Once i was back into my snapchat i went to re enable superSU, but it failed the reinstall and prompted me to reboot, so i did, then ended up getting stuck at the boot screen for the past 3 hours.
I don't know if what i tried was right, or even helped or made the problem worse.
I have tried reinstalling the custom kernel, re flashing the superSU through recovery, using ODIN to flash the original OS but each time i tried it failed, i might be using the wrong firmware, not sure, but i have a SG920F and installed the firmware for that, but it failed when doing so. I also never had the chance to create a back up as my phone didn't have enough storage to do so... It's at the point where im happy to factory reset im just not sure what to do.
I'm genuinely sad that i messed this up, and managed to brick my phone already. If anyone can help please reply to this...
Thanks.
theBoyAnt said:
Hi, i'm kinda new to all of this, so literally any help is appreciated.
I recently rooted my S6, and managed to get it stuck in a boot loop on the Samsung screen, with the logo in the centre, slowly fading from light to dark repeatedly.
This happened when i accidentally logged out of my snapchat, causing it to detect my device was rooted and wouldn't let me log back in. I got around this by updating my superSU and disabling it as i logged into my snapchat. Once i was back into my snapchat i went to re enable superSU, but it failed the reinstall and prompted me to reboot, so i did, then ended up getting stuck at the boot screen for the past 3 hours.
I don't know if what i tried was right, or even helped or made the problem worse.
I have tried reinstalling the custom kernel, re flashing the superSU through recovery, using ODIN to flash the original OS but each time i tried it failed, i might be using the wrong firmware, not sure, but i have a SG920F and installed the firmware for that, but it failed when doing so. I also never had the chance to create a back up as my phone didn't have enough storage to do so... It's at the point where im happy to factory reset im just not sure what to do.
I'm genuinely sad that i messed this up, and managed to brick my phone already. If anyone can help please reply to this...
Thanks.
Click to expand...
Click to collapse
I think it should be fixable. Firmware should be available at sammobile.com
RealWelder said:
I think it should be fixable. Firmware should be available at sammobile.com
Click to expand...
Click to collapse
Ah! Didn't know this! Thanks, will download it now and use odin to get it back on my phone, will update here if it works or not!
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
your phone partition got messed up you have to put TWRP back and then go in wipe and then you have to do file repairwhen you fix file then ran back the stock firmware which will fix bootloader
then go back install twrp and install custom rom with root
---------- Post added at 04:03 PM ---------- Previous post was at 04:02 PM ----------
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
once you fix file then do the format within twrp
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
there is the list of stock firmware try them see which one works with twrp, you have to install twrp first so you can fix the problem using repair files in twrp
https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/
also read this for installing twrp on 910t
https://forum.xda-developers.com/no...nt/tool-utility-twrp-2-8-1-0-teamwin-t2915588
rayhawk said:
Hello everyone. I have encountered something I don't understand. My note suddenly turned off and wouldn't restart. I thought maybe my battery was low so I plugged it in and it started. I decided to get a new battery and charged it up same thing was going on sometimes it would restart and be fine I was running stock rooted rom twrp recovery never dropped it never messed with it. Then since i was having trouble I took it to a cell repair shop. I could boot to download and twrp but when i tried to back up the rom it would get to about 2 percent and shutdown. The only way the phone stayed on is if i am in download or twrp but i couldn't do anything repair shop couldn't help either. I was desperately trying to save some data off the phone when i gave up I said ok i will reflash it all goes well in odin it reboots then says applying update but never gets past the boot farthest i have got is the tmobile screen. then it shuts down and keeps vibration and trying to restart only to shut down and do it all over again. so I am now stuck in a boot loop it seems not sure if that is accurate. I have no idea how to fix this any ideas anyone i have reflashed the latest rom twice and everything should be fine but it isnt. I am wondering what to do next I tried to flash twrp but it didnt take and also tried cf oneclick root didnt take either but odin says success and pass. I am at the end of my idea list and out of google searches no idea what to try next. So I have come to the one place i may find some help XDA. Thanks in advance
Click to expand...
Click to collapse
Befour flashing twrp make sure you uncheck Auto reboot....when it's done flashing pull your battery, put it back in the phone but don't power on....you want to boot right into recovery......then twrp will stick
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Matsilagi said:
Hey!
I was using my phone as normal, and installed an update for PixelPlusUI, it was working fine and all, until earlier today, i tried going into recovery to fix an app issue. After that, the phone just bootlooped. I figured that going into Fastboot would fix that, but the problem is, i can't reach any of those modes. It just goes to the Redmi logo, reboots, and repeats that infinitely.
I heard about EDL mode, but that seems atleast so far, unreacheable.
Is there any way for me to reach it? Maybe by letting the battery dry out and then plug the powered off phone with Volume -, or am i out of luck here? Im pretty sure this is caused by the stupid VBMeta checks XIAOMI phones has.
Click to expand...
Click to collapse
Vbmeta means Android Verified Boot.
Vbmeta is default for all android devices and it was made by Google.
It is not specific made by Xiaomi.
Android Verified Boot 2.0
https://source.android.com/security/verifiedboot/avb
What changes did you do when you fixed the app issue?
Couldn't do any, just tried to boot into recovery, then got into that bootlooop cycle, couldn't reach anything.
Managed to get into EDL and SP Flash Tool mode, however, im a bit confused on what i need to flash to get it back to life with stock MIUI or atleast boot to main system to use ADB.
My IMEI is fixed on the phone stickers so i can reasily recover that aswell, any help is appreciated.
EDIT: Now i just need help flashing as it seems, what do i need to do to properly re-flash / re-boot the phone without losing IMEI and that sorta stuff? I plan on switching back to Pixel Plus UI again so, it isn't an issue.
EDIT2: Completely fixed, followed VD's guide on EDL/Mediatek Bypass method and flashed a normal GLOBAL rom, all was fixed, no IMEI lost.