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

Installing rooted ROM on a phone that's not rooted

Hello guys! I have Xperia T 9.2.A.0.295.
I've tried a couple of methods of rooting my phone and all failed:
- rooting via flashtool, when "make it ra1n" appears, phone just restarts
- rooting via first method listed in this subforum, when running .bat file it gets stuck @ *daemon started successfully*
- rootin via towelroot, when I try to install it, it simply says "App not installed".
My idea was following, but I'm afraid to execute it without you guys having my back or I know it will be broken (back or phone or both hehe)
I wanted to try to push CWM via fastboot (already got drivers installed and all options defined correctly, unknown sources, debugging etc.)
I wanted to follow this tutorial with this CWM: http://forum.xda-developers.com/showthread.php?t=1918966
1. So, if I install rooted ROM, is my phone going to be rooted or not? Or is installation going to fail? (some people were mentioning it's very likely phone is gonna end up bricked...)
2. If I install this CWM (since it's from 2012) am I going to have problems installing ROMs developed in 2015 (eg. 4.4.4 or 5.x?)
3. Is there a way I could back my current software up just in case something goes wrong so I could restore it in case of a fail?
Thanks guys!
If anyone has FB and maybe would like to add me just so I could contact him if things go south, feel free to send it to my PM, I'll add you

OK, I found older firmware on XperiFirm (9.2.A.1.199) from the vendor I bought the phone from. Later the phone was unlocked, I sure hope it doesn't lock again or something.....Since I moved to another vendor.
I'm downloading now, but I'm thinking about sleeping through the night 'till someone answers because I'm having a feeling I'm gonna wreck something...

Did you tried THIS ?
It works for me

Sorry for replying so late, didn't work for me, but I'm working on it with Olivier, he helped me

Unable to enter Custom Recovery, Galaxy Pro 10.1 SM-T520 .Help Please, dead Robot

Hi all,
I have been hammering away at this one, and putting it on the back-burner, but now, it is really getting to me. Samsung Galaxy Tab Pro 10.1 SM-T520
It has been rooted with ODIN, and shows no problem, (things seem much easier now, as I have re-jigged lots of my old phones using so many more tools, I am not an expert, but can read and search without too much problems) I was very careful to choose the correct file, CF-Auto-Root-picassowifi-picassowifixx-smt520.zip, I have rechecked this step several times, as most of the instructions I found ODIN device ID:COM box should become yellow, when on newer versions it is blue I think, I wondered if I was going mad,
Root Checker Root access granted, all fine. I have Root access. n.
Installed CWM ,latest recovery for a Pro 10.1 wifi, recovery 6.0.3.1 Titanium backup-ed, all ready to go and Reboot and flash a new ROM.. No joy. .. Installed TWRP , same.
When it re-starts it ,shows the galaxy logo, flashes off, then back on, and then fails. Android dead with a red warning , standard recovery KOT49H.T520XXUANAE, all I can do is the usual options:apply update. The only thing I haven't tried is to just wipe all the data. I have a backup of my apps with Titanium Backup on the SD card,I am not that bothered really about much other data if its a pain. I just want control of my device and to try a new ,cleaner ROM(SMT520_GraveD_V3.0)
This has been bothering me for ages, I have read so many posts so am now getting really frustrated I have bought triangle away app. today although I think I sorted that issue early on anyway , but just in case...
Super SU seemed to have vanished so that is back installed
I think I searched and found the Mount/system issue and looked into an issue that lead me to the .system folder, but it is hidden, so I could not find the file it related to. I dont have the specifics to hand as I checked it out at work. I wondered if it is because I have ES file manager, not ASTRO as it said in some of the posts I found.but sure this is a red herring.
I have tried everything..I have a Mac at home and PC at work, I have tried ADB and can see &restart the device etc... so I am connected, first I got the error that it didn't recognise the sideload command. Read up on ADB , looked at the help etc. sideload isn't there as a command, very confusing. But I think I got there one I figured out paths, as of course they are different on a Mac, and possibly more so as I have 2 drives in it, which often confuses me ..grr.
I can of course get into the bootloader, with ON+VOL -, it tells me so far the system is : Official and Knox Warranty Void: 1 which I think is fine, but a chap at work suspected this, but after lots of threads I gather this is normal..
Sorry if long, just thought I should be as clear as possible. I have not really come across such an awkward issue as this , my HTC One was a breeze:crying:
*edit* Just worked out through trial and error, that to use the sideboot command I had to select send via ADB and now with the path /Desktop/SMT520_GraveD_V3.0.zip I was able to send the file but with the following messgae : E:footer is wrong and E:signature verification failed, twice.. So some progress
Thanks !

Just to say after being up waay too long on this, I discovered there is a newer firmware T520XXUANI1_T520BTUANI1_BTU which I may aswell upgrade to first, but of course I cannot do this OTA now As it recognises the device is 'tampered with' *sigh* so gun and games with Odin for Mac tonight, or JODIN3 , just to get the firmware upgrade(which seems to be a jungle of fake download links). before a Rom without bloatware..
I am also not completely clear why, as from another thread about KNOX, as I am basically running stock , without custom recovery.. According to this thread , but I am getting a bit confused now
http://forum.xda-developers.com/gal...neral/knox-warranty-void1-otas-t2996067/page2
Click to expand...
Click to collapse
however this is another story from the ROM install. Apologies

Well. No replies, but I did eventually solve this. Hopefully this can help someone. I am a tinkerer, but I really nearly gave up on this..But this was a cheap second hand tablet ( my first) and I want to see what it can do before I test drive one on my mother who is having nightmares with every Windows laptop I give her!
Once I got to a PC , I had access to Odin3, although it is not available online (apparently to Mac) I could not get it to work due to Java issues (JOdin3 online - brilliant idea but no joy for me so far)
I had the Rom I wanted ( GraveDigger- SMT520_GraveD_V3.0.zip ), the firmware update (T520XXUAOD2_T520BTUAOB1_BTU.zip(i think)) and the unlock file (CF-Auto-Root-picassowifi-picassowifixx-smt520.zip) , non of which I could install in any way , due to being locked out of using a custom Rom bootloader!
At this point I factory reset and cleared the cache( as that is the only options in the basic bootloader!) I also has ADB on the PC so attempted to install the files this way (after messing about using some software to produce the .tar and .md5 files needed for Odin. I tried everything to get this into proper 'bootloader mode' all from scrach again, including trying the adb oem unlockbootloader command, which I would never get to work as I could not get there!
With Odin, I was also again able to flash the firmware update, eventually, and of course had to unlock again. I was curious if I could now use the OTA update, and could not. At some point, in repeating this process( as I think it hung up several times and needed a hard reboot) I had at this point fully wiped the device as I know that is another reason to have glitches and an unstable ROM later.
I think I then tried to check and although T520XXUAOD2 seems to still be the firmware, at some point I managed to get online ( I think some superuser app which I have had to try several may have notified me that KNOX was reset:laugh:When I go to About>Software update it said I had the latest update! Good news!
At this point I had installed both CWM and TWRP again , and thought I would try TWRP.I had tried CWM and the same problem, like a double flash of the Samsung Logo , so I know it had reset !!
THIS TIME I used TWRP ( I thought of trying CWM touch, but its either paid, or I would have to find and ABD the file over I guess) , I managed to re-apply the Root file, Root checker confirmed this , as it had throughout this ordeal!, although apart from ACCESS GRANTED I dont really know what the rest means..Anyway although picassowifi , was still in Device name on TWRP I chose an earlier recovery version to install.- twp-2.7.0.0-picassowifi.img. When I re-booted, I was able to get the TWRP recover image, and install the ROM, I cannot remember if I re-rooted as I was so elated.
I had a few , freezing moments, reinstalling most of my apps through Titanium Backup, I think I just tried to reinstall everything which of was unnecessary, after a hard reset, all seems fine. I checked and the TWRP recovery seems to have stuck. I am not entirely sure how to check about the firmware , but for now I feel this is progress.
Good Luck if anyone found this any use.
Just to add, when you search this ( and probably many other models) you seem to get so many sites, offering exactly the same unlock information, in exactly the same way, many of the downloads seem to take you to many weird and wonderful places. So I tended to look here for downloads if possible. But I had to join SamMobile (which seems a useful site for the firmware upgrade) and trawl all over and assume similarities between other Samsung devices to fully check I was not being an idiot. But this was very odd and I could not find any posts or other workarounds that I did not try. But this new ROM feels lovely and smooth so far, and I now want to look into this tablet further

Doogee X5 Pro [Xposed Framework Help]

Right. I have been doing a fair amount of research on how to install the Xposed Framwork. I am running Lolipop 5.1 and I am pretty sure all Doogee X5 Pro's run it. I haven't changed anything to do with the rom and my android is rooted using KingRoot. I only did that because it was easy to do and I didn't want to go through the bother of flashing a nand or anything. I got the installer thinking that would work[This was before I did any research about Xposed] I heard that it allowed you to use a lot of modules and improve the device so I thought.. Why not. this isn't my first time screwing around with nands and stuff with devices.
Anyhow. On to the problem at hand, To start with I think I am on a stock ROM and a lot of people are saying that I am going to need to get a custom ROM. I am not entirely sure what to do there and I am aware that most android devices are different so looking at a tutorial from someone not using the same device as me causes some issues.
I don't know which SDK to get for the framework but after doing a fair amount of looking and finding that I need armv8-a helped out a little but then I got slightly confused with the table that they made on the Xposed Framework Thread. It stated that if I was not on a TW ROM then I would need to check if the /system/lib64/ folder exists and then that would tell me what ROM to get.. I found that all a bit confusing and not very well explained so I didn't proceed because I didn't want to end up bricking my phone [So much as you can fix a soft brick. I thought I would come here first and save my self some hassle]
Model Number : x5pro
Android Version : 5.1
http :// prntscr.com / bzu2he
EDIT: I just booted into recovery mode and then I got the "No Command" problem so I had to take the battery out to get it to reboot into normal mode..
EDIT: Well that was silly. Found a way around it. Now I can get into Recovery Mode.
Link to the spec's of Doogee X5 Pro
Kindest Regards XeNitro

6.0.1 and Viper4Android....

Ok.. Background.
I have rooted and installed ROMS on several devices over 10 years. I'm no developer, but I'm pretty darn proficient.
I used this last process to root after the update:
http://forum.xda-developers.com/tmo...tmb-g920tuvu4epf1-20160627114318-zip-t3408162
I have read so many threads on this topic, and tried every single process. Here are the two main ones.
http://forum.xda-developers.com/gal...-edge-root-t3072183/post66048178#post66048178 - Original post AND #414 (updated for 6.0.1)
http://forum.xda-developers.com/google-nexus-5/themes-apps/discussion-viper4android-t2543796 - This was the final attempt
I ended up in the final attempt flashing the zip in the last thread, getting everything "working" drivers wise, but NO sound was coming from the device. UGH.
The kicker here I think is the SELinux mode, and although the workaround seems to be the kicker for some, I never got it working.
At this point I am fresh wiping and installing 6.0.1 again until someone with a T-Mobile S6 can give me the steps that worked for them.
Anyone???

Potential Solution
Try flashing the zip from the link provided after you install the viper driver.
It worked for me, but sometimes it won't work when you want it to, but this
is always fixed with a reboot, then it will work until you close the viper app.
Not the best solution but worth it.
(XDA wont let me post links because this is a new account, add ".com" after google and delete all the spaces)
drive.google /file/d/0B4wY0nl4hWhQZWVydUhiVDVEUVE/view?usp=sharing