[Q] Xposed question (Bootloop) :( - Galaxy Note 4 Q&A, Help & Troubleshooting

Just installed it with a bunch of new modules and rebooted. Is it normal to take longer than 10 minutes to update everything? Its running on TekXodus rom
EDIT: its been 20 mins so i pulled the battery and went back into twrp and wiped all the cache. Still in bootloop
I had to do a complete restore to my original state. It would not go out of bootloop after using Xposed. I only installed the modules that were compatible from this list:
http://forum.xda-developers.com/showpost.php?p=59955968&postcount=2
Ill try again tomorrow but looks like im not going to be using Xposed for a while. Are you supposed to reboot after installing each module?

equlizer said:
Just installed it with a bunch of new modules and rebooted. Is it normal to take longer than 10 minutes to update everything? Its running on TekXodus rom
EDIT: its been 20 mins so i pulled the battery and went back into twrp and wiped all the cache. Still in bootloop
I had to do a complete restore to my original state. It would not go out of bootloop after using Xposed. I only installed the modules that were compatible from this list:
http://forum.xda-developers.com/showpost.php?p=59955968&postcount=2
Ill try again tomorrow but looks like im not going to be using Xposed for a while. Are you supposed to reboot after installing each module?
Click to expand...
Click to collapse
you need boot into recovery, do a factory reset and then flash rom in odin

That was no help at all man. I did say im back to stock using recovery.

What run time was your phone on?

Related

[Q] Doesn't boot

Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
ricomana said:
Hello,
I've got a problem with my gt-i9505.
I've managed to root the phone and install TWRP.
So i decided to install CM10.2 (21-08) and the right gapps for it.
Everything worked very good and I couldn't be happier.
All my apps were back and it was ready to use it!
I turned off the phone and went to sleep.
The next day i turned it on and it got stuck on the bootscreen (not the CM bootscreen, but the SAMSUNG GALAXY S4 bootscreen).
So I tried to do factory reset and install rom again, gapps again, afterwards again wipe dalvik and cache.
But i keep having the same problem. Right now after flashing the rom it doesn't even boot up the first time.
I also tried going back to 10.1, but same problem.
I don't know what to do, i just got my s4. Really hope i can fix it.
Luckily i can enter the recovery. But i didn't do a backup or anything.
Does anyone have any tips on how to get it working again?
Click to expand...
Click to collapse
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
malybru said:
Hi,
Look HERE
Put everything back to stock then, try again.
I found some 10.2 ROMS do not like rebooting,and just hang.
Remove the battery and try again normally worked.
Click to expand...
Click to collapse
Thanks for replying
I followed the instructions and succesfully installed the official stock rom for my device and region.
But it's still stuck at the samsung boot screen.
And now i can't boot into TWRP anymore either, is that correct?
After that I flashed with the .pit file. But still stuck on bootscreen.
Is there any other way to solve this problem?
idgaf about custom roms or CM10.2 anymore, i just want my phone to work.
Wether it's with custom or with stock firmware.
Really hope I didn't break my phone. :crying:
EDIT:
I wiped cache after flashing, but no data wipe/factory reset. That did the trick.
God i can't be happier my phone finally works again. Now i'm scared to flash a custom rom again. I think i need to install TWRP or CWM again too I'll just wait for now.

Phone randomly reboots and boot loops

Hey,
I am using the AllianceRom with safestrap, AllianceRom installed on stock rom slot. Recently, my phone would suddenly reboot while I am using it, making a call etc, then get stuck in a boot loop until I pulled out the battery, then sometimes it would start up well or get back in a loop.
What I have tried,
- Installing ROM to romslot1.
- Flashing stock verizon rom, phone worked normally for a while, I tried to get back to AllianceRom or RootDeOdex_NCG rom, but no reboots started again after like 2 happy hours.
Leaving phone alone for like 2 hours powered off, then when i turn it on, it works, for like a few hours, then bootloops...
Ideas?
fixticks said:
Hey,
I am using the AllianceRom with safestrap, AllianceRom installed on stock rom slot. Recently, my phone would suddenly reboot while I am using it, making a call etc, then get stuck in a boot loop until I pulled out the battery, then sometimes it would start up well or get back in a loop.
What I have tried,
- Installing ROM to romslot1.
- Flashing stock verizon rom, phone worked normally for a while, I tried to get back to AllianceRom or RootDeOdex_NCG rom, but no reboots started again after like 2 happy hours.
Leaving phone alone for like 2 hours powered off, then when i turn it on, it works, for like a few hours, then bootloops...
Ideas?
Click to expand...
Click to collapse
Are you using WIFI? I had bootloops after updating to NI2 whenever I would connect to WIFI. Wiped caches didn't work, had to revert back to a backup ROM
ldeveraux said:
Are you using WIFI? I had bootloops after updating to NI2 whenever I would connect to WIFI. Wiped caches didn't work, had to revert back to a backup ROM
Click to expand...
Click to collapse
Well yeah, I'd use WIFI after installing the rom to install my apps, and everything would go well, I'd even install apps and use the phone for a while. Then sudden boot loops.
Update: Just installed stock rom, and even re-partitioned using the
Code:
http://forum.xda-developers.com/showpost.php?p=53447942&postcount=1
PIT file. It boot looped afterwards, then like 2 minutes later, it run, phone is working, holding breath.
ldeveraux said:
Are you using WIFI? I had bootloops after updating to NI2 whenever I would connect to WIFI. Wiped caches didn't work, had to revert back to a backup ROM
Click to expand...
Click to collapse
well if you updated to ni2 firmware on alliance rom thatd b your problem lol.. alliance rom is on ne9 still
Sent from my SM-G900V using XDA Free mobile app
elliwigy said:
well if you updated to ni2 firmware on alliance rom thatd b your problem lol.. alliance rom is on ne9 still
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
No I'm on stock ROM, just noting that I had the same problem and how I fixed it
So far:
only had one surprise reboot. Which I'm thinking is not so bad.
I am on stock verizon still, can't do a wireless hotspot. feel caged! Noticed I cannot send sms unless I use a third party SMS application, might be due to the fact that i'm not on verizon but I'm using Hello SMS (it rocks) so eff it.
- I rooted so I could get rid of the annoying "Sim card from unknown source" message, by uninstalling Setup Wizard. and restored some of my apps with Titanium.
Waiting till Sunday, if all goes well, I will install safestrap and it's back to customRom goodness...
Thanks guys for the help.

Soft brick - Need some guidance

It's been awhile since I changed anything on this phone, I've been running CM11 with no issues. The wife was playing with my phone which is on cm12 and wanted me to upgrade it. Great, I hate having to touch her phone but ok.
1. Did a straight upgrade to CM12 nightly (couple nights ago build) with gapps from CM site. After the install everything crashes on the initial load, it's like the baseband is jacked and doesn't know how to handle the new google play services because everything crashes.
2. Went back and wiped internal everything this time, re installed nightly and gapps. No change.
3. Tried step 2 a couple more times and different gapps from PA and other random sites (micro, light, stock versions) and then TWRP just died on me. It's asking for a password when I first go in so now I'm stuck there. Tried to use ODIN to install the latest TWRP after converting it with another script found here (i'll find the link).
so, I'm probably going to have to use ODIN to restore some stock version of S4 ATT but I really don't know which one is stock that would work with CM12. I don't want to get caught in the safestrap crap of dual boot and whatever else. Any help is greatly appreciated.
You'll need to Odin the mdl firmware in Odin. Be careful as it will want to update itself after you flash it. See sammobile.com for the firmware.
Sent from my Nexus 9 using XDA Free mobile app
Awesome, thanks!
Flashed the stock, towelroot, twrp from google play and cm12 nightly. Perfect and back where I left off. Thanks!!
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
kronikwisdom said:
Ok.. I did a bad thing I guess. after working for a couple weeks I tried to reset the phone while cm12.1 was installed. All it did was keep restarting TWRP and was stuck there. So I figured there was an issue with the twrp install or something whatever, I went to flash back to stock mdl in odin. Instead of selecting PDA I selected Phone and it failed on the first attempt. Then I selected PDA and it installed correctly (Said passed). Now I'm stuck on the AT&T logo on boot. I tried to reinstall the stock rom again and the same results. Where do I go from here??!?
Click to expand...
Click to collapse
Boot into the stock recovery and do a factory reset
Sent from my Nexus 9 using XDA Free mobile app
Ok, factory reset worked on the second try. Sent it in to a boot loop on the first go around, odd. Thanks!

[Q] Nexus 4 - booting - takes a very long time

My Nexus 4 was running on Android 5.0(Stock,Rooted). I installed the Xposed framework for Lollipop and few other modules for it. Initially things were working fine, but after installing few additional modules, the boot process started taking a long time than usual(30 mins to even 1 hr). The very first time it happened, I thought that my phone went into boot loop, but after some 20-30 mins it booted into the Android runtime. But from then on, every reboot has been such a pain the ass.
When the Factory Image for the 5.1.1 was released, I flashed it using the steps mentioned in http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
But still I'm facing the same problem(the boot process is taking a very long time). So, I think it doesn't have anything to do with the Xposed Framework/Modules.
Has some one else faced similar problem? If so can you please provide some pointers on how I should go about solving this problem?
Try installing a custom recovery again, like TWRP, and then going in and manually doing a factory reset, along with wiping your Dalvik cache, and formatting the system partition on your phone. Then, try installing 5.1.1 again or install a custom ROM. It's possible some of the Xposed framework stuff got left on there.

Phone will not stop boot loop after flashing ROM

This morning while at work i decided to try another ROM while I had some time. I have been running VRtoxin with no issues as of this morning. I downloaded the latest pure nexus and proceeded to advance wipe everything but storage. I flashed the rom and dynamic gapps. The phone booted up and seemed to be fine until i tried to open a few of the apps i use on a regular basis. When i went to open facebook, hangouts, google plus and some others i would get a notification that unfortunately the app was stopped. I tried rebooting and reinstalling pure nexus and kept getting the same messages. I finally got sick of it and decided to flash my back up i made this morning of VRtoxin. That's when the boot loops started. I have since then mounted system, advance wiped all but storage and tried to flash both VR and pure nexus. Neither will get past boot loop. I have waited 15+ minutes for each.
Thank you in advance.
nvanells said:
This morning while at work i decided to try another ROM while I had some time. I have been running VRtoxin with no issues as of this morning. I downloaded the latest pure nexus and proceeded to advance wipe everything but storage. I flashed the rom and dynamic gapps. The phone booted up and seemed to be fine until i tried to open a few of the apps i use on a regular basis. When i went to open facebook, hangouts, google plus and some others i would get a notification that unfortunately the app was stopped. I tried rebooting and reinstalling pure nexus and kept getting the same messages. I finally got sick of it and decided to flash my back up i made this morning of VRtoxin. That's when the boot loops started. I have since then mounted system, advance wiped all but storage and tried to flash both VR and pure nexus. Neither will get past boot loop. I have waited 15+ minutes for each.
Thank you in advance.
Click to expand...
Click to collapse
Try manually flashing each stock IMG
Boot, system, vendor, recovery. Then re flash twrp then try restoring your backup.
Yup. That's exactly what I would do. I would do. Report back and let us know!
Thank you for the advice. Before the response i just started over completely. Reflashed back to stock, flashed twrp and rooted. I'm back on VRToxin now with no problems.
I'm a ROM flashing junky, what do i have to do differently now on the 6p? I've never had this problem on my N6. On my N6 i would advance wipe everything but storage and then flash a new ROM with Gapps and never had this happen.

Categories

Resources