Database Develop

Every ROM install boot loops

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

Requesting some help :)

Hello Everyone!
I am new, my name is rohan and I have my eyes on the Xposed framework. I wanted to download some cool apps but i realized i needed Xposed framework. I own a Samsung Galaxy S5, Android 5.0, It has an ARM32 chip or something like that and i am a huge fan of Xposed now. So i didn't realize until now...I download TWRP, created a recovery and then i downloaded the .zip file for Xposed's framework to be installed. I was using TWRP and flashed the file via recovery but then my phone was starting, remained on the "samsung" (the blue dots like some fireworks) and never went beyond it. Could i get some help on this? Is this the BootLoop?...
Also, I don't know how to recover my phone too, it was also a rooted phone -- i forgot to do a backup for it...So any chances my phone will work again? Currently i have an S6 Edge - SM-G925F. But no plans to root the big boy yet.

Rohan114757 said:
Hello Everyone!
I am new, my name is rohan and I have my eyes on the Xposed framework. I wanted to download some cool apps but i realized i needed Xposed framework. I own a Samsung Galaxy S5, Android 5.0, It has an ARM32 chip or something like that and i am a huge fan of Xposed now. So i didn't realize until now...I download TWRP, created a recovery and then i downloaded the .zip file for Xposed's framework to be installed. I was using TWRP and flashed the file via recovery but then my phone was starting, remained on the "samsung" (the blue dots like some fireworks) and never went beyond it. Could i get some help on this? Is this the BootLoop?...
Also, I don't know how to recover my phone too, it was also a rooted phone -- i forgot to do a backup for it...So any chances my phone will work again? Currently i have an S6 Edge - SM-G925F. But no plans to root the big boy yet.
Click to expand...
Click to collapse
First of all: facepalm. A backup is mandatory if you flash any file through recovery. Always, no excuses.
Concerning your problem: you are encountering a bootloop... maybe. How long did you wait until you decide to abort the boot process? The first boot after flashing takes some time. If you have waited more than ten minutes, download the uninstaller.zip from the Xposed thread and place it on your SD card. Boot into recovery via key combo (use Google to find out about this). Then flash the uninstaller.zip and wipe cache&dalvik. Reboot and you might have your phone back running.
Another hint: after flashing the Xposed framework, it is recommended to wipe cache&dalvik.

orville87 said:
First of all: facepalm. A backup is mandatory if you flash any file through recovery. Always, no excuses.
Concerning your problem: you are encountering a bootloop... maybe. How long did you wait until you decide to abort the boot process? The first boot after flashing takes some time. If you have waited more than ten minutes, download the uninstaller.zip from the Xposed thread and place it on your SD card. Boot into recovery via key combo (use Google to find out about this). Then flash the uninstaller.zip and wipe cache&dalvik. Reboot and you might have your phone back running.
Another hint: after flashing the Xposed framework, it is recommended to wipe cache&dalvik.
Click to expand...
Click to collapse
Maybe i clearly did not explain it, after the flash success from TWRP 2.8.70 i used the re-boot option and then it got boot-looped from there i suppose. And you recovery mode, the recovery mode is still the odin download recovery mode, i ended up restoring the 4.4.2 firmware for now on my S5.
Plus, the issue is fixed - mod lockdown requested.

Closed at OP's request.

problem after uninstalling xposed

HI, I installed xposed on my s2 using twrp recovery, and every thing worked fine, untill I found a problem after updating my rom automatically it gets stucked in cm boot screen I tried updating using another recovery but didn't work so I restored my last cm12.1 build , I uninstalled xposed also using twrp recovery and wiped cash and dalvic but when the phone complete it's boot all the apps installed on sdcard are not shown even it was shown when the phone was saying ''optimizing system apps", the only fix is to do wipe data which is a thing I don't wanna do offcourse.
Any help.guys I realy need to update my rom.

muhammad mujahid said:
HI, I installed xposed on my s2 using twrp recovery, and every thing worked fine, untill I found a problem after updating my rom automatically it gets stucked in cm boot screen I tried updating using another recovery but didn't work so I restored my last cm12.1 build , I uninstalled xposed also using twrp recovery and wiped cash and dalvic but when the phone complete it's boot all the apps installed on sdcard are not shown even it was shown when the phone was saying ''optimizing system apps", the only fix is to do wipe data which is a thing I don't wanna do offcourse.
Any help.guys I realy need to update my rom.
Click to expand...
Click to collapse
Did you re-flash Xposed after you updated your ROM? Updating a ROM will overwrite files which are required for Xposed. So basically you should do the following:
update your ROM, boot into recovery, re-flash Xposed, wipe cache&dalvik, reboot.

orville87 said:
Did you re-flash Xposed after you updated your ROM? Updating a ROM will overwrite files which are required for Xposed. So basically you should do the following:
update your ROM, boot into recovery, re-flash Xposed, wipe cache&dalvik, reboot.
Click to expand...
Click to collapse
It doesn't even boot after updating.
It stuck in cm boot screen
You meen that I should flash xposed anyway even if it didn't reboot?

muhammad mujahid said:
It doesn't even boot after updating.
It stuck in cm boot screen
You meen that I should flash xposed anyway even if it didn't reboot?
Click to expand...
Click to collapse
Yes. Then wipe cache&dalvik and reboot.

orville87 said:
Did you re-flash Xposed after you updated your ROM? Updating a ROM will overwrite files which are required for Xposed. So basically you should do the following:
update your ROM, boot into recovery, re-flash Xposed, wipe cache&dalvik, reboot.
Click to expand...
Click to collapse
Yeah ?, thanks ovrille87 I fixed it using the way you explaind
1-updated the rom
2-booted into recovery and flashed xposed
3-wiped the cash and dalvik
Thanks man, you made my day.

Fresh MM install

Before MM I was already having issues with my LP install. Lockups, crashes, etc.. I had planned on performing a fresh install of my LP ROM yesterday but was excited to see that MM was released. I was hoping that installing MM over LP would fix the issue that I was experiencing. No dice.
So, is it possible to go into TWRP, perform a factory reset (including erasing Internal Storage) and then booting into Download Mode so I can install MM fresh using Odin? Is there anything that I need to know of or missing before performing this procedure? I can then reinstall TWRP and root afterwards. I just want a fresh install and can't wait two or three days for a Flashable Zip. My system is just too unstable in its current form.
Thanks.
JC

For The Record
This is exactly what I just did. It works perfectly and now my phone is back to operating normally. And with a clean install of 6.0.1 to boot!
Now....time for TWRP and Root........

What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.

Wipe
Mister_E105 said:
What is safe to wipe in TWRP? I did an install of MM for the 910T stock rom and unfortunately tried the encryption. I thought it would give me the option to decrypt, but that is not the case.
Click to expand...
Click to collapse
I wiped EVERYTHING in TWRP. Powered off the phone and then booted to Download Mode. From there I pushed out a fresh copy of MM using Odin. It flashes a new stock recovery. After the phone boots up go back into Download Mode and flash TWRP using Odin. Then you can flash Beta SuperSU in TWRP for root.

But.....I wanted to follow up on this post. My Note 4 started experiencing issues last week. I was hoping a fresh OS install would fix things. Unfortunately for me during a power off to go into recovery to flash SuperSU I received the dreaded mmc_read failed error. The phone is nearly two years old and I have never seen the bug on my device. I had thought that I was one of the lucky early purchasers. I was wrong.
The device got worse and worse. To the point that now it rarely boots at all. It just sits at the "Samsung Note 4" screen. I can't even get into TWRP reliably. And the mmc screen is popping up more frequently now as well.
I had no choice but to stop by T-Mobile yesterday and (reluctantly) buy a S7 Edge. I say reluctantly for two reasons. 1. The Note 7 comes out in barely over a month 2. There is no known root for S7 (and Note 7 will probably be the same)
I have 30 days to decide if this phone is for me or not. Not having root is something that I never thought I'd have to live with. Barring some unforeseen circumstance I thought I'd have the Note 4 for a couple more years. And I didn't have the time to look for a used one as I needed a phone immediately.
Fingers crossed they get this thing roooted because it really is a pretty sexy device!

I found that the only way to clear the encryption was to load the stock recovery, it had the power to wipe the partitions and allow a clean install.

[Deodex] for 32.3.A.0.376 + Superuser Mod

I created a Deodex patch tested it too, so far no fc's if you encounter something let me know.
Requirements: you need to be on stock 32.3.A.0.376
Create A Backup Before Flashing
Download removed Im gonna test it further and release it again when everything works fine
Update : Superuser Mod included as a download
Thanks to @venkat kamesh for his tutorial for the Superuser Mod
Waiting on feedback I may have found a problem // Update : all good false alarm

Does it have DRM fix ? or only stock kernel ?

emosis said:
Does it have DRM fix ? or only stock kernel ?
Click to expand...
Click to collapse
Its based on stock I extracted the files direct from the ftf I patched my kernel with drm fix so its only stock nothing added just deodex
And its just a patch to deodex it not a whole rom forgot to add

Hi Bro! How did you do? Thanks!

Thx.. I ll dowbload and try it soon..

wiped dalvik data cache..
Flashed the ROM
Rebooted
Sony logo waited and didnt booted..
restarted waited a black screen.. restarted Sony logo again..

emosis said:
wiped dalvik data cache..
Flashed the ROM
Rebooted
Sony logo waited and didnt booted..
restarted waited a black screen.. restarted Sony logo again..
Click to expand...
Click to collapse
Hmmm weird it works for me are you on 376?

Before installing deodex need a clean, just put the firmware activated a Google account and update all the app through playmarket.
Z5C 32.3.A.0.376 deodex.zip

i`m on MM right now, can i flash this firmware after a clean wipe ? or i must have 376 already ? did anyone try exposed on this firmware? what xposed works? thanks

adryanodej said:
i`m on MM right now, can i flash this firmware after a clean wipe ? or i must have 376 already ? did anyone try exposed on this firmware? what xposed works? thanks
Click to expand...
Click to collapse
You need to be on 376 and as far as i know there is no xposed for nougat

Arter flashing 376 i flashed zachs kernel because it has twrp then flashed your rom it rebooted when turned on to first setup screen..

emosis said:
Arter flashing 376 i flashed zachs kernel because it has twrp then flashed your rom it rebooted when turned on to first setup screen..
Click to expand...
Click to collapse
I will look into it im gonna clean install 376 and test it again, weird tho everything works fine on my end

Hello.
I have also tried to install this.
1. Fresh 376 install (Australia CU).
2. Flash just TWRP 3.0.2 recovery.
3. Flash you deodex.
4. Clear Dalvik Cache
5. Reboot
6. Sony logo
7. Black screen
8. Sony logo (stuck)

This might not be related... but I think I found the cause of the stuck logo screen.
It seems for some reason at some point, the OS is no longer found.
This occurs after I go to TWRP. The phone boots completely fine all the time with no issues. It seems the OS is lost after booting into TWRP. I'm not entirely sure where is the best place to address this, the TWRP section?