Database Develop

Help! Note 4 softbricked!!

I rooted my Note 4 (sm-n910t) and installed wanam xposed and it started acting slow so when i removed the module my phone froze and i rebooted it and now im bootlooped at the tmobile splashscreen and it keeps rebooting no matter what. I need help guys please any help is appreciated. Trying to find firmware files to flash in odin but so far i cant find any working ones.

That was fast.... ?? Try this, third post.
http://forum.xda-developers.com/showthread.php?t=2903733

Damn I love wanam exposed

Before flashing the firmware try this. It says only compatible with Sony and LG roms but it wouldn't hurt to try.
This is Xposed version 2.5 (final). The main new features and fixes in this version are:
* Rewritten framework installation/uninstallation
* Uses interactive su (via libsuperuser) to provide improved compatibility with different Superuser apps
* Better feedback when root access fails (doesn't freeze the app anymore)
* Offers installation via custom recovery (CWM/TWRP), either flashing the file automatically or manually
Safemode to disable Xposed with hardware keys to get out of (most) bootloops
Compatibility with Sony/LG ROMs (4.3 and 4.4), Meizu ROMs (4.4)
Debug setting to disable resource hooking as a temporary workaround for incompatibilities with some theming engines (not all modules can be used in this mode)
There are also other improvements and fixes, especially many translations updates.
In case you get a message "Segmentation fault" during installation, you can now download an additional app which provides statically compiled versions of BusyBox (a lot bigger, but should work with every ROM). It's not needed otherwise.
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.

Go into the development section, download the stock rom file and flash via Odin/download mode.

techcomputergeek said:
I rooted my Note 4 (sm-n910t) and installed wanam xposed and it started acting slow so when i removed the module my phone froze and i rebooted it and now im bootlooped at the tmobile splashscreen and it keeps rebooting no matter what. I need help guys please any help is appreciated. Trying to find firmware files to flash in odin but so far i cant find any working ones.
Click to expand...
Click to collapse
Not that you don't know this by now but you need to wait for a approved version for our phones to come out.
NOTE 4

techcomputergeek said:
I rooted my Note 4 (sm-n910t) and installed wanam xposed and it started acting slow so when i removed the module my phone froze and i rebooted it and now im bootlooped at the tmobile splashscreen and it keeps rebooting no matter what. I need help guys please any help is appreciated. Trying to find firmware files to flash in odin but so far i cant find any working ones.
Click to expand...
Click to collapse
Free thanks. You need to disable xposed your not even soft bricked this is the perils of messing with phones before things are sorted out. Grab the Odin flushable image and flash from pm.. Fyi more or less the only way to brick a samsung phone is to smash it with a brick. Or flash the wrong image......

deeznutz1977 said:
Free thanks. You need to disable xposed your not even soft bricked this is the perils of messing with phones before things are sorted out. Grab the Odin flushable image and flash from pm.. Fyi more or less the only way to brick a samsung phone is to smash it with a brick. Or flash the wrong image......
Click to expand...
Click to collapse
best advice right here..
ESPECIALLY for N00bs; you better learn to be patient, because you will bring alot of misery on yourself if you just start flashing stuff that you aren't really familiar with.

Man i was about to rush & install it also..i need minminguard

deeznutz1977 said:
Grab the Odin flushable image
Click to expand...
Click to collapse
Do I need a Samsung toilet to flush it?

How do you brick a device that have been out for less than 24 hours....patient is virtue my friend. When it come to xpose always look at last it was updated, if got nothing to do with the time you received your phone i usually stay clear...especially with wanam...if last update is not with in your device age, best to stay clear.
It may have been xpose acting up as well, next time reboot the device and as it does keep pressing one hardware key repeatidly (forgot how how many press) but just go nut, it will disable and get pass the boot loop

You aren't alone, when I loaded xposed after rooting the phone became very very laggy. When I removed all parts of it from the phone it went back to normal which was just weird but for right now I am leaving it off my phone till I figure out why it did that. Which sucks, I miss my darktube.

Thanks Everyone
Thanks everyone....the problem for me was finding the firmware since the device is so new and i did find it and took 16 hours to download on rapidgator which sucked, but it got me running again. Hopefully wanam xposed and xposed framework it self gets updated sometime soon. I'm a root junkie so I may be using my 3 until support for the 4. My friends were right and I should have waited for nexus 6 lol.

siraltus said:
Do I need a Samsung toilet to flush it?
Click to expand...
Click to collapse
Lol too funny

Thinking about lollipop upgrade

im pretty happy with kk, but i do want to be on 5.0, so i just wanted to make a few thing clear first.
1. if anything goes wrong with flashing a captured ota, how to restore my kk as it is now? will simply restoring a twrp backup do the trick on any stock rom?
2. where can i find the stock rom? the motorola site links arent working for me.
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
5. are there any bugs that seriously affect most users?
i am planning to root immediately so root only mods are fine.
im on a rooted unlocked bootloader xt1063,
thanks for your time,!

1. Just flash the stock ROM via fastboot.
2. I guess are some links on the Development section.
3. in 5.0, unfortunately not.
4. I guess no :/
5. Only a bootloop that happens with the newest versions of SuperSU (the only versions that works with 5.0), no major bugs..
Sent from my XT1063 using XDA Free mobile app

thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?

Kobro said:
thanks for your fast response
is there a fix for said bootloop yet? can you show me a link?
Click to expand...
Click to collapse
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.

pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.

Kobro said:
lol im no noob to flashing roms and updates, i am new to lollipop
thanks so much for your info, it is very helpful.
Click to expand...
Click to collapse
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.

Kobro said:
3. the quicksettings panel. is there a way/mod/app/ that will let me pull down quicksettings with one swipe like on cm and with gravitybox?
4.i really like to be able to customize the quicksettings, is that possible?
Click to expand...
Click to collapse
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!

Flash custom rom and enjoy lollipop

pastorbob62 said:
I wasn't implying you were a noob, just sharing my experience with you since you asked the question. Every device has its own quirks and idiosyncrasies. And I have seen posts from people with apparent considerable experience that displays much impatience.
Click to expand...
Click to collapse
your right for stating everything clearly, my bad

anomalyconcept said:
Try pulling down with two fingers instead of one- I've heard that this is the shortcut for the quick settings. (I don't have a device w/ 5 to try.) I think Google has also made the tiles in the quick settings dynamic and "smart" based on what you use most often. I tend to prefer having a static view and knowing exactly which ones are present (and in the same place!), but I won't know until I actually use it more.
I have the US GSM variant (XT1064) which came preloaded with 21.11.23. The OTA I've found only applies to 21.11.17 (the original release), and I've not had any luck downgrading. Good luck in your Lollipop quest!
Click to expand...
Click to collapse
yes that works, and has been since 4.3, on my custom rom devices it just is not so comfortable on a 5" device i was thinking more of something like pull down from right.

these responses motorola about the model xt1068
Catherine: Hi, my name is Catherine. How may I help you?
ENRICO: good morning
are to hold model xt1068, I wanted to know when will the update to Android 5
Catherine: Hi, at the moment we do not have a release date for Lollipop in Europe. It is currently going through testing before release but we are working hard to get it out as soon as possible. You can find the latest information at http://www.motorola.com/updates
ENRICO: thanks
Catherine: No problem, is there anything else that I can help you with?
ENRICO: no thanks
Catherine: Ok, have a nice day!
ENRICO:

pastorbob62 said:
When I ran into that problem I just hard reset (hold power button until it reboots) then let it run the course. After another reboot it came up to the lock screen and all was well. I have not had any issues since.
That said, I suspect if I had just left it for a few minutes without the hard reset it would have been fine. My tendency (as is the case with most people in these forums) is to be impatient, and jump the gun before things are completed.
The first reboot after installing Lollipop takes a while so don't get impatient.
I am using an XT1063.
Click to expand...
Click to collapse
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.

Kobro said:
just wanted to let you know, i have successfully flashed lollipop, rooted with twrp, run into the bootloop, found a solution in the general forum, (wipe cache and dalvik) and voila rooted 5.0
thanks for all your input.
Click to expand...
Click to collapse
Don't need it now, but good to know should I have to reflash in the future. Thanks for the info. :good:

root on English 546?

So I just got my Z3C and have been happily loading my apps when I read that rooting wipes the device and I might be wasting my time. Is it still the case that you need to use the exploit to root?

I had to pretty much re-root and do the whole shibang shibang again. Not only that, but I've also been struggling to get xposed to work on 5.1.1. Didn't have any trouble getting it to work on 5.0.2. So far, it seems like most people are getting xposed to work by using an older zip, which has been annoying to track down. It's a v67 version of xposed, but it's a specific one. Also, had to flash an additional zip just to get the notification bar to align correctly, and there's some additional new bloat.
Won't lie. Was pretty happy with 5.0.2., and it's taking me quite some time to get my phone back to how customized I had it in 5.1.1

mnguyen127 said:
I had to pretty much re-root and do the whole shibang shibang again. Not only that, but I've also been struggling to get xposed to work on 5.1.1. Didn't have any trouble getting it to work on 5.0.2. So far, it seems like most people are getting xposed to work by using an older zip, which has been annoying to track down. It's a v67 version of xposed, but it's a specific one. Also, had to flash an additional zip just to get the notification bar to align correctly, and there's some additional new bloat.
Won't lie. Was pretty happy with 5.0.2., and it's taking me quite some time to get my phone back to how customized I had it in 5.1.1
Click to expand...
Click to collapse
This is your best bet to find out exactly what Xposed version you need for your Rom and for your phone. You will have 5.1.1 working better than ever in a couple steps. Hope it helps.
http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118

flamand said:
So I just got my Z3C and have been happily loading my apps when I read that rooting wipes the device and I might be wasting my time. Is it still the case that you need to use the exploit to root?
Click to expand...
Click to collapse
To answer your question - you only TRULY have to wipe your device when changing from KK to LP or vice-versa; however, everything just works better when you wipe. During the rooting process, I believe you'll have to downgrade to an old KK firmware, then once you've obtained root, you'll have to install a pre-rooted 5.1.1 LP firmware. At that point, you can choose to either wipe or not.

Nexus 6 shows 4,000% battery life after root?

I got my Nexus 6P for Christmas, and I decided to root my Motorola Nexus 6 from last year. I've been waiting to do this for a few months, and was excited to finally enable several of the options I couldn't otherwise enable (such as double tap to wake and auto rotate on the lock screen and Google Now launcher). About an hour ago I got around to rooting and done so with little issues. It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. I rooted following the steps in a YouTube video by DroidModderX and the device is running perfectly fine. The device hasn't died yet, and I'll be interested to see when it will die. The battery life seems to fluctuate between 4,001% and 4,204% (Those two figures being the highest and lowest figures respectively). Rebooting does not fix this error.
I know it's not a massive problem, but I'd like to know what's causing this issue and how to resolve it. I haven't flashed any custom OS's on my phone, I'm still running stock Android 6.0.1 Marshmallow with the latest December security patches. The device is carrier unlocked also. How can I fix this?
Thanks,
Eamonn.

sonic2kk said:
It's been a little under an hour since I rooted, and I just now noticed that the battery life is being displayed as having over 4,000% charge. being the highest and lowest figures respectively). Rebooting does not fix this error.
Click to expand...
Click to collapse
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.

sansnil said:
You need to use updated root files. The battery issue arises when you're on 6.0.1 but aren't using the right file version. Easily fixed not to worry, just re-root with updated files and it will resolve with no lasting harm.
Click to expand...
Click to collapse
Ah, thank goodness. I'll re-root tomorrow and post back if I have any problems. Thanks!

Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.

Why did you need root for the Google now launcher?

mikeprius said:
Why did you need root for the Google now launcher?
Click to expand...
Click to collapse
What do you mean? I can run the Google Now launcher perfectly fine. Root works fine as well. The problem isn't with the Google Now launcher but with the warning on boot. I didn't need to root, I chose to. Am I misunderstanding?

Your original post made it seem like you need root for double tap to wake and Google now launcher.

sonic2kk said:
Thanks, that fixed the issue. I re-rooted and everything is working fine. I flashed the ElementalX kernel. However on boot I now get a warning with a red triangle saying "Your device is corrupt. It cannot be trusted and may not work properly". This warning goes away, and the phone proceeds to boot up successfully. Everything on the device works perfectly fine with no issues. I am successfully rooted running Android Marshmallow 6.0.1, but this screen scares me somewhat. I rooted my Galaxy SII and I have a yellow triangle on boot but only on the Samsung splash screen. Is this something new in Android M or something unique to Nexus devices? I researched this a bit and found one post on Reddit that said this happened in the M previews, and that it was nothing to be concerned about. Is there a way to remove this screen, or is it just like the yellow triangle on the SII? Should I even be concerned with this, or is it something to just dismiss? Is my device at risk any more than normal when rooting, and have I done something wrong? I'm a bit of a newbie at the rooting stuff, but I intend to use my Nexus 6 and SII to learn more about it (and my 6P way into the future, once I get a new phone).
Thanks in advance.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24269982087021512 gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: https://www.androidfilehost.com/?fid=24340319927534323 (flash this also after you flash the bootstack).

HueyT said:
(removed url) gives you 6.0.1 bootstack for Nexus 6 (shamu). Flash this in TWRP. This should fix your corrupted boot splash screen. It's new in Android M when you've installed custom kernel and/or roms. It does not hurt anything except Android Pay is unlikely to work once rooted.
EDIT: I forgot to included mmb29k, non-encrypt boot.img made by GerardF: (removed url) (flash this also after you flash the bootstack).
Click to expand...
Click to collapse
Worked perfect. That got rid of the corrupt message. One last question: (This is the last one, I swear! ) Are you saying that Android Pay won't work at all after rooting or that it wouldn't have worked if that screen had have appeared on boot? I hope to use the service if and when it comes to the UK.
mikeprius said:
Your original post made it seem like you need root for double tap to wake and Google now launcher.
Click to expand...
Click to collapse
Ah, sorry for the confusion my friend ?

I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...

orangekid said:
I would have kept it at 4,000% - that's like 2 weeks of battery life with no charge...
Click to expand...
Click to collapse
Haha if it wasn't a display error I might have (Though it would have only been like 3 days on the Nexus 6 )

Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6

Dalek Caan said:
Stupid question but where do I get updated files. I followed the method on root junky for the Nexus 6
Click to expand...
Click to collapse
Sorry, I don't remember where I got the updated files now. I do remember sticking to looking on XDA and not just searching randomly online, maybe you could try searching the forums?

is it possible to root with chainfire root files. I did a clean install of the January security update, then flashed the latest boot.img from chainfire then flashed SuperSU 2.66.zip through TWRP, but im still getting this. I received this same issue with the last patch. Im at the point where it isnt worth rooting. Any help would be appreciated.

Stuck at Verizon bootup screen

Samsung Galaxy S7 EDGE
Android Marshmellow
I used 3.11 APK
Anyway, I followed the installer and flashed the phone, however once it restarted it continues to get stuck at the Verizon screen. Do I need to factory reset the phone? I just rooted my phone today, so I'm still learning. Maybe I didn't use the right version to install? I did a decent amount of research, but apparently I missed something.
Any help would be appreciated, thank you!

jmiller13 said:
Samsung Galaxy S7 EDGE
Android Marshmellow
I used 3.11 APK
Anyway, I followed the installer and flashed the phone, however once it restarted it continues to get stuck at the Verizon screen. Do I need to factory reset the phone? I just rooted my phone today, so I'm still learning. Maybe I didn't use the right version to install? I did a decent amount of research, but apparently I missed something.
Any help would be appreciated, thank you!
Click to expand...
Click to collapse
Yup... You missed something.
Check out the official Lollipop/Marshmallow thread and look for the red text: https://forum.xda-developers.com/showthread.php?t=3034811
And when you've done that look up wanams Xposed.

Oh, well I'm an idiot. Is the version of Xposed you mentioned specifically for S7 Edge's?

Alright, well I found this:
repo.xposed.info/module/ma.wanam.xposed
It says discontinued, but I'm assuming that's the one I use?

https://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960

You need the unofficial wanam xposed for Samsung devices. The thread is in the main page.