Apparently destroyed my phone with Xposed. S7(G930V) - Xposed General

I want to start this off by acknowledging that this is my fault. I didn't heed the warning I was given when installing Xposed.
I installed Xposed, and when my phone restarted it just got stuck in the loading screen for Verizon.
I've tried putting a "factory" ROM on my device with no luck, multiple error codes, went through all the steps I could find online to try to resolve those.
I'm really lost here. There are a lot of important verification apps on my phone, and I really need this resolved. If anyone could please help bail me out of my stupidity it would be greatly appreciated.

Blueroad12 said:
I want to start this off by acknowledging that this is my fault. I didn't heed the warning I was given when installing Xposed.
I installed Xposed, and when my phone restarted it just got stuck in the loading screen for Verizon.
I've tried putting a "factory" ROM on my device with no luck, multiple error codes, went through all the steps I could find online to try to resolve those.
I'm really lost here. There are a lot of important verification apps on my phone, and I really need this resolved. If anyone could please help bail me out of my stupidity it would be greatly appreciated.
Click to expand...
Click to collapse
Maybe have a look at the S7 Verizon subforum. Someone over there might be able to help you. Good luck.
https://forum.xda-developers.com/verizon-galaxy-s7

Portgas D. Ace said:
Maybe have a look at the S7 Verizon subforum. Someone over there might be able to help you. Good luck.
https://forum.xda-developers.com/verizon-galaxy-s7
Click to expand...
Click to collapse
Will do, thanks.

For what I recall there was (don't know if it's still there) an "emergency way" to boot the phone preventing xposed to kick in. It saved my *ss many times, but you should see if and how this can be achieved with actual version of xposed. Good luck mate.
Sent from my Samsung G935F with Tapatalk 6

Blueroad12 said:
I want to start this off by acknowledging that this is my fault. I didn't heed the warning I was given when installing Xposed.
I installed Xposed, and when my phone restarted it just got stuck in the loading screen for Verizon.
I've tried putting a "factory" ROM on my device with no luck, multiple error codes, went through all the steps I could find online to try to resolve those.
I'm really lost here. There are a lot of important verification apps on my phone, and I really need this resolved. If anyone could please help bail me out of my stupidity it would be greatly appreciated.
Click to expand...
Click to collapse
You tried flashing stock rom with Odin on PC? Flashing Xposed uninstaller?
Verizon S7 is this with locked bootloader?
Sent from my S7.

FlemishDroid said:
You tried flashing stock rom with Odin on PC? Flashing Xposed uninstaller?
Verizon S7 is this with locked bootloader?
Sent from my S7.
Click to expand...
Click to collapse
I'm an idiot and didn't do my research.
I tried flashing a stock rom and got errors every time with odin.

Okay, I got it fixed by flashing a fresh ROM off of sammobile.

Related

[Q] Need Help! Tried rooting my Note 3 for the first time and now very inoperable

To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
baileynapier said:
To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
Click to expand...
Click to collapse
Have you performed a factory data reset since the last attempt?
440bro said:
Have you performed a factory data reset since the last attempt?
Click to expand...
Click to collapse
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
baileynapier said:
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
Click to expand...
Click to collapse
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
28248965 286a
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That was the method that originally got me into this situation and i just tried it again step by step and i am still having the issue.
One thing that has caught my eye is that this was my devices information before ever trying any rooting process or anything:
MODEL NUMBER: SAMSUNG-SN-N900A
ANDROID VERSION: 4.3 (Jelly Bean)
BASEBAND VERSION: N900AUCUBNB4
KERNEL INFO -
3.4.0-1625098
se.i[email protected] #1
Mon Feb 10 21:13:28 KST 2014
BUILD NUMBER: JSS15J.N900AUCUBNB4
SELINUX STATUS: Enforcing
Is there any possible way to get it back to being a BNB4 device like the information above?
graydiggy said:
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
the2rrell said:
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
Click to expand...
Click to collapse
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
Click to expand...
Click to collapse
use kingo 1.1.8 it is a lot easier
baileynapier said:
ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc.
Click to expand...
Click to collapse
How did you NOT find Kingo right away?
What kind of research did you do for 3 weeks? lol
Well, I'm glad you're good to go now. The devs on this site are exceptional and you are lucky to have them. (me too).
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
Click to expand...
Click to collapse
So how did you get it back functioning properly? I am at the same point. I bricked my N3 screwing around with getting Face Unlock to work. So I followed the steps of Restore for MJ5 post, and immediately upon the final boot into setup, the Direct Pen Input error started, and makes the device useless. What fixed yours?
Re-download all the files and retry. Also, verify the size. I think you may have a corrupt file somewhere.
And factory reset after installing a ROM, even if it's the same ROM you had. Any ROM, on any phone, not just this one. Different ROMs store data in different locations, and if a ROM picks up the data from a previous ROM, that may bot be the data it wants, so it causes things to crash.
Ok thanks for the replies. I actually tried a factory reset after seeing the error, but it didn't help at all. And I did run a checksum on the only file that displayed a number, when I originally downloaded the files. But as would be expected, after all simple efforts to fix the issue failed, I started fresh on a whole different PC, downloaded all of the files again, used a different USB cable, and installed everything all over again. And low and behold, the second time was a total success. I can't explain what made the difference, and the checksum result showed an accurate download both times. But this is the nature of the beast isn't it?
Thanks,

[Q] Can you help me get my Recovery Menu back and possibly Stock FW

Okay so to start I followed this Tutorial http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 all the way through and my phone was rooted and I was happy. One day I tried to install TWRP since this is what I used on my Galaxy s3 before this phone. It got stuck on on a boot loop. I eventually tried flashing every stock ROM which did not fix the problem because ODIN would fail when trying to flash. Eventually I tried flashing the "G900A_ND3_Stock_Kernel" supplied in the tutorial. My phone magically booted up and all my APPS and stuff was the same as I left it and it was still rooted. I decided not to mess with it anymore. This happened about a month ago.
Today, my phone had a notification saying that there was an update and I tapped remind me later. Eventually, I installed Titanium Back up to force closed the AT&T Software Update app the phone came with. Then. it automatically updated and eventually got stuck into the boot loop again. No problem, I fixed this before. What I noticed from the first time was that I had a screen that said "Secure Fail: Recovery. System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help" Once I flashed the stock kernel from the tutorial I never checked to see if the recover menu was there.
So right now I have my phone working and its rooted. I installed the "Phone Info" app and it says Bootloader Version:G900AUCU2ANG3. Eventually, my phone will try to update itself again and it will fail causing it to boot loop. I am not sure on what to do. Is there a way for me to have my recovery menu back? I just want to have the option in the future to revert everything back to normal in case I sell it or feel like having the newest OS. Also it would be cool to have a recovery menu on my phone again.
I know this was long but I needed to solve this problem before it gets out of hand in the future. Also I am pretty sure others have followed the tutorial and might have had the idea to update the OS or something else and had a problem similar to mine.
Thank You Very Much.
xtremegamer13 said:
Okay so to start I followed this Tutorial http://forum.xda-developers.com/att-galaxy-s5/general/how-to-root-g900aucu2aoa1-4-4-4-2-3-2015-t3021120 all the way through and my phone was rooted and I was happy. One day I tried to install TWRP since this is what I used on my Galaxy s3 before this phone. It got stuck on on a boot loop. I eventually tried flashing every stock ROM which did not fix the problem because ODIN would fail when trying to flash. Eventually I tried flashing the "G900A_ND3_Stock_Kernel" supplied in the tutorial. My phone magically booted up and all my APPS and stuff was the same as I left it and it was still rooted. I decided not to mess with it anymore. This happened about a month ago.
Today, my phone had a notification saying that there was an update and I tapped remind me later. Eventually, I installed Titanium Back up to force closed the AT&T Software Update app the phone came with. Then. it automatically updated and eventually got stuck into the boot loop again. No problem, I fixed this before. What I noticed from the first time was that I had a screen that said "Secure Fail: Recovery. System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nearest AT&T store for help" Once I flashed the stock kernel from the tutorial I never checked to see if the recover menu was there.
So right now I have my phone working and its rooted. I installed the "Phone Info" app and it says Bootloader Version:G900AUCU2ANG3. Eventually, my phone will try to update itself again and it will fail causing it to boot loop. I am not sure on what to do. Is there a way for me to have my recovery menu back? I just want to have the option in the future to revert everything back to normal in case I sell it or feel like having the newest OS. Also it would be cool to have a recovery menu on my phone again.
I know this was long but I needed to solve this problem before it gets out of hand in the future. Also I am pretty sure others have followed the tutorial and might have had the idea to update the OS or something else and had a problem similar to mine.
Thank You Very Much.
Click to expand...
Click to collapse
So you're still rooted?
And if so using titanium backup just freeze the ATT update app I forget what it's called exactly but you'll know it when you see it and that'll stop your device from trying to automatically trying to update
OPOfreak said:
So you're still rooted?
And if so using titanium backup just freeze the ATT update app I forget what it's called exactly but you'll know it when you see it and that'll stop your device from trying to automatically trying to update
Click to expand...
Click to collapse
Yeah I'm still rooted and I found out about the freeze app option but do you know about the problem where I don't even have a recovery menu?
xtremegamer13 said:
Yeah I'm still rooted and I found out about the freeze app option but do you know about the problem where I don't even have a recovery menu?
Click to expand...
Click to collapse
You need to download the safe strap recovery menu. That is for rooted phones with locked bootloaders.
dirtydodge said:
You need to download the safe strap recovery menu. That is for rooted phones with locked bootloaders.
Click to expand...
Click to collapse
Thank You very much I was able to install the Safe strap Recovery and am now backing it up. Hopefully my last question Is there a way to update in the future for example if I wanted to have the OTA firmwares from AT&T without root in case I were to sell the phone?
Thank you guys for the answers.
xtremegamer13 said:
Thank You very much I was able to install the Safe strap Recovery and am now backing it up. Hopefully my last question Is there a way to update in the future for example if I wanted to have the OTA firmwares from AT&T without root in case I were to sell the phone?
Thank you guys for the answers.
Click to expand...
Click to collapse
Odin back to stock
OPOfreak said:
Odin back to stock
Click to expand...
Click to collapse
I've tried this in the past when my phone was stuck in bootloop, But it always failed since I have a different baseband or boatloader. Would you know which stock ROM I have to use because I tried many and had no luck in the past?
xtremegamer13 said:
I've tried this in the past when my phone was stuck in bootloop, But it always failed since I have a different baseband or boatloader. Would you know which stock ROM I have to use because I tried many and had no luck in the past?
Click to expand...
Click to collapse
Read here links are still working
http://forum.xda-developers.com/showthread.php?t=2868776
OPOfreak said:
Read here links are still working
http://forum.xda-developers.com/showthread.php?t=2868776
Click to expand...
Click to collapse
Wait, the thread is for Galaxy s5 Active. Will the G870AUCU1ANE4_Full_Odin.tar file work on my Galaxy s5 AT&T? Just making sure.
xtremegamer13 said:
Wait, the thread is for Galaxy s5 Active. Will the G870AUCU1ANE4_Full_Odin.tar file work on my Galaxy s5 AT&T? Just making sure.
Click to expand...
Click to collapse
No my bad
Here
http://forum.xda-developers.com/showthread.php?t=2862299

[Q] FlashFire: Current Binary

Hi, thank you very much for reading!
I've been playing around with my new Verizon Edge 6. I had no problems obtaining root, though I'm not an Android expert whatsoever. More of a good at following clear instructions kind of guy, I guess.
Anyway, I haven't been able to flash it much else than the stock rom. Whatever else I try flashing does end up booting, but the phone won't recognize my SIM Card at all no matter what I try (I know I could likely try some more stuff, but I have no idea). When I flash the stock one back in, it behaves flawlessly again.
My guess is that this has something to do with my Current Binary Status in FlashFire being "Unknown" when it should read "Official". And my question is if you know how what the easiest way to get it that way and if you could pretty please point me out where I can get the files I'll need.
Thank you VERY much in advance!
Frannyman said:
Hi, thank you very much for reading!
I've been playing around with my new Verizon Edge 6. I had no problems obtaining root, though I'm not an Android expert whatsoever. More of a good at following clear instructions kind of guy, I guess.
Anyway, I haven't been able to flash it much else than the stock rom. Whatever else I try flashing does end up booting, but the phone won't recognize my SIM Card at all no matter what I try (I know I could likely try some more stuff, but I have no idea). When I flash the stock one back in, it behaves flawlessly again.
My guess is that this has something to do with my Current Binary Status in FlashFire being "Unknown" when it should read "Official". And my question is if you know how what the easiest way to get it that way and if you could pretty please point me out where I can get the files I'll need.
Thank you VERY much in advance!
Click to expand...
Click to collapse
Binary status in Flashfire will read unknown for all Verizon S6/edge variants, due to the bootloader being protected.
I am not sure where your problem comes from exactly. Are you on OC3 firmware, and trying to flash an OE2 rom/package? If not, could you be more specific on what your flashing in FF, and what firmware your on?
Sent from my SM-G925V
My apologies por taking so long to reply. I had no trouble installing the Firmware I wanted right after reading your post. It was in fact trying to flash an OC2 on a OC3 Firmware. I was too embarrassed to admit I had in fact no idea what I was talking about. I humbly recognize now my ignorance, stupidity and stubborness. Thank you very much for your prompt help!
Frannyman said:
My apologies por taking so long to reply. I had no trouble installing the Firmware I wanted right after reading your post. It was in fact trying to flash an OC2 on a OC3 Firmware. I was too embarrassed to admit I had in fact no idea what I was talking about. I humbly recognize now my ignorance, stupidity and stubborness. Thank you very much for your prompt help!
Click to expand...
Click to collapse
No problem with trying to help, and thank you for replying. And don't feel bad or worry about it, we all start somewhere! I certainly am no expert, but try and help where I can.
Sent from my SM-G925V
My S4 i9500 International version is shown as UNKNOWN, too in Flashfire. Why?

Took the latest OTA. How can I downgrade and install TWRP and CFW?

The title explains it all. I got this phone knowing I could root and install CFW, but wanted to just "use" it for a few days in stock. I don't mind stock, I would jsut prefer a custom firmware. I'm having trouble figuring out what I need to do to downgrade to Lollipop so I can flash TWRP and begin using CFW. A simple set of instructions would be very appreciated. Thanks to anyone who can help!
but2002 said:
The title explains it all. I got this phone knowing I could root and install CFW, but wanted to just "use" it for a few days in stock. I don't mind stock, I would jsut prefer a custom firmware. I'm having trouble figuring out what I need to do to downgrade to Lollipop so I can flash TWRP and begin using CFW. A simple set of instructions would be very appreciated. Thanks to anyone who can help!
Click to expand...
Click to collapse
There appear to be guides here for doing those things with 6.0 installed, such as MicroMod777's guides.
After a few more hours of digging, I figured it out. I may draw up a cleanly laid out guide referencing the posts that helped me for people in the position I was.
Thank you!
No, you don't need to downgrade, just go ahead and install TWRP & CFW.
Careful with downgrading, becuz H811 has Q-Fuse enabled, if you mess up you'll end up with a 9008 hard brick
im having a similar issue im trying to root/unlock 20p and its not finding any device in fastboot it just sits there saying locating any device and never locates anything adb see's the phone just fine anyone know anything about that? thanks for the help in advance
Rooting stock G4H811 already on 20p?
but2002 said:
After a few more hours of digging, I figured it out. I may draw up a cleanly laid out guide referencing the posts that helped me for people in the position I was.
Thank you!
Click to expand...
Click to collapse
Yea, I'm trying to root my new updated G4 that's on 20p. I have one that's soft bricked already that I'm trying to fix and don't wish to brick another.
Can someone point me in the right direction?
Thanks
Im in the same boat. No devices found after fastboot. Any advice?

Downgrade S2 T813 to MM?

Howdy, folks. I just picked up an S2 and though it was supposed to ship with MM, either it's a refurb and the store is selling it as new, or the factory upgraded the ROM and the ad copy didn't match with the software version.
I specifically want MM so I can run Xposed and Xprivacy.
Can anyone point me to a way to get ahold of the OEM Samsung equivalent of an RUU so I can get back to MM on this device?
Thanks in advance!
Wow. I figured you Sammy guys would be all over this.
I'm looking for the factory stock MM ROM for a T813NZKSXAR. Can someone point the way? Sorry, but I'm new to Samsung devices, so I'm not up to speed on all the resources and I'm not finding anything that seems right either here at XDA or on a web search.
Could really use some help, here...
Thanks!
BillTheCat said:
Wow. I figured you Sammy guys would be all over this.
I'm looking for the factory stock MM ROM for a T813NZKSXAR. Can someone point the way? Sorry, but I'm new to Samsung devices, so I'm not up to speed on all the resources and I'm not finding anything that seems right either here at XDA or on a web search.
Could really use some help, here...
Thanks!
Click to expand...
Click to collapse
Head over to updato.com
Thanks for that. I'm still getting my head around all of this.
So, I actually did download that file, but wasn't sure if it was safe. I went ahead and flashed the MM firmware with Odin3.12.3, but I seem to be having some trouble applying TWRP.
I'm using twrp-3.2.0-0-gts210vewifi.img, but when done flashing in Odin, I can't seem to figure out the sequence to catch the machine before it boots back into the OS. Either that, or I have the wrong TWRP image, or something. I just can't seem to catch it right.
Any help would be appreciated.
Ok, got it sorted. Managed to get TWRP installed, but having trouble flashing Xposed. I'm using xposed-v88.2-sdk23-arm64 but as it flashes, there's an error saying that it can't write to the data partition, and on reboot, the Samsung name just keeps pulsing and the machine never gets to the OS. At least, not for about ten or fifteen minutes, which is the longest I waited.
Thanks again in advance for your help!

Categories

Resources