Develop Bugs

unable to reroot Sprint Galaxy S3 with a failed root.

I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...

christivson said:
I have an S3 from sprint. it has a faild root at this point (TrevE). My guess is that an update locked up my root.. I am tring to flash back to stock so I can reroot but SU blocks everything i do. I have tried to reroot but CW wont come up, just android recovery. Everything I have found on removeing SU requires you to be rooted first.... I even tried Root Browser and Uninstall master but SU just denies permission.... All i want to do is start from scratch. Please help...
Click to expand...
Click to collapse
Do you are able to get to download mode?

kevinrus123 said:
Do you are able to get to download mode?
Click to expand...
Click to collapse
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks

christivson said:
The problem was that i watched too many videos and went through too many how to guids. I kept working at it and finaly got it to work. i finaly found a video that told me not to let it reboot after odin was done. I turned "off" the auto reboot on Odin, which is the exact oposite of what every other video said to do, and manualy shut it down and put it straight into Recovery Mode. All of the videos I had seen said to leave Auto Reboot on so i had been doing that. after it would reboot I would shut it back down and try to go to recvery mode but got the android recvery insted of CWRecovery. I guess the reboot after Odin was enough to through it all out of wac. Manually shutting it down after Odin and then going into recovery right away got it. Unfortunatly thats the problem when there are 5,000 answers to the same question. Thanks
Click to expand...
Click to collapse
You may have watched some videos from before the last two official stock updates that were released several months ago - I don't recall which one, but one of those updates added a function that reinstalls the stock recovery every time the phone boots up. And since the custom recovery is the only way to flash a custom rom that doesn't revert your recovery to stock, you have to do that while the custom recovery is still installed, which means before the stock rom ever gets a chance to boot
In other words, nothing was thrown out of whack - it was all operating the way it was designed to, by developers who don't want us to be able to mess with their programming - we sure showed them, though, lol
Sent from my SPH-L710 using xda app-developers app

[Q] ATT SGH-I313 Note 2 bricked/soft brick issues

So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!

titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Download the latest kies from the samsung website.. and then open tools and then firmware update and initialization.. pull out the battery and type the model number and serial number kies asks.. follow the instructions.. your phone will be fine..
Sent from my GT-N7100

titostats said:
So I have an Att Note 2, which is bricked or soft bricked. I am a very rookie Android guy when it comes to modifying or hacking. I did root my Note 2 with Cyanogenmod. However, I missed S Note and the use of my S Pen so I researched a bit to get back to stock with the use of Odin and stock roms found on the net. I was successful, and actually amazed it worked. Long story short, a few days after that, an OTA update hit my phone, didn't even think about it and began the download. The phone downloaded the update, and rebooted to complete the install. The problem is, during reboot, the phone got stuck on the "Samsung Galaxy Note II" screen. I researched a bit online, and everyone said get to recovery mode and do a few things. Problem is, I can't get into recovery mode, I can only get the screen described above, and the download screen, THAT IS ALL. Looked a bit more online and attempted to flash various stock roms with Odin. Some were successful, Odin passed, and the phone would get stuck on the Note II screen again, and would not boot into recovery mode, same issue with only being able to access download mode. The unsuccessful flash attempts got me to screen informing me that Kies needs to be used to update my firmware. Kies showed a recovery code, which was downloaded, but unsuccessful. It would download all the way, but at the end of install, it would fail. Funny thing is it would work enough to get me back to the ability to get into download mode. I just want my Note 2 working again. Is there any way to wipe my phone completely clean, and start over? Or is there any way to even re-root it, or flash any sort of rom on there, just so I can use the damn thing? I need some help by you pros out there ! Please!
Click to expand...
Click to collapse
Try flashing a recovery for ur device with Odin, not a ROM, just flash twrp recovery with Odin, after u flash the recovery u will be able to access recovery and flash a stock ROM through twrp. I think what happened to u is when u flashed the update it tried to right over the unlocked bootloader which caused the soft brick, try flashing the recovery for ur device and if that doesn't work try the above posters way...
Sent from my Nexus 5 using XDA Premium 4 mobile app

Galaxy Note 2 Superbork

Where to start...
First, as a disclaimer, I may use language or terms that sound noobish. I have rooted and run custom ROMs on several devices in the past, however generally when I get a ROM I like I stick with it, so I'm not constantly tinkering. I've done my best to search and find solutions so please go easy on me.
17 days ago I was running stock 4.3 on my SGNII when the battery died. Upon charging I found I was stuck in bootloop and had a bad /efs mount. I searched and searched and spent around 15 hours trying this and that but to no avail. I finally threw my hands in the air and got ahold of Josh at mobiletechvideos and he was able to fix the efs mount issue. However, he left me in factory mode which required me to root to get out of, and once I did this I was unable to activate data on my carrier (Ting). I was so happy to have my phone "back" though that I used it like this for 4 or 5 days. I could get on wifi and I could call and send text messages. I had been off the grid so this felt like something I'd fix fully later.
Well I kept reading and found "fix" after "fix", flashed this and that and still no dice. FINALLY, last night, I found this thread: http://forum.xda-developers.com/show....php?t=2086769 which helped immensely. I was able to get TWRP flashed by unchecking the "auto-reboot" option in Odin and pulling the battery after the update took, and via TWRP I was able to install the ROM. I booted up, the device activated, I was running 4.1.2, I made and received some calls, the birds were chirping, the air was sweet...
I had struggled for so long and I had finally achieved success! Then, for seemingly no reason at all, I accepted an OTA update which bricked my Note2. Devastation.
The current state of things...
* Cannot get past the initial "Samsung Galaxy Note 2" screen
* Cannot boot into recovery
* I CAN get into dl mode,
* but, I CANNOT successfully flash anything. TWRP will flash like it took, but upon reboot I'm not able to boot into it. I'm also able to flash a ROM but it fails when it gets to sbin, and upon rebooting I'm greeted by the screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
When I try to use Kies it doesn't find the device. I've installed all of the most recent drivers and I'm running Kies as administrator. I select Tools > Emergency Firmware Recovery, THEN connect my device as instructed.
I'm at the apex of frustration. I beg thee to help!!

I have roughly the same situation. Was rooted and on an MK4 rom, battery ran down super fast yesterday and when charged, only get splash screen and slowly flashing blue light. I can get into Philz recovery but no matter what I try, no dice. Also can get into DL mode, but haven't been able to get anywhere. What the heck happened?

Well i bought another phone because of this problem of unknown baseband and 0 for everything in settings which didnt allow me to connect to sprint. Now when that happen it put me in safe mode . and i couldn't find a fix for months i ended up getting a lg g2 and let my note 2 collect dust. Well I'm using my note 2 and its up in running . my partition was messed up . if you have this issue which it sound like i can help. My phone was running fine then rebooted on its own and rebooted on safe mode with no signal
Sent from my SGH-M919 using XDA Premium 4 mobile app

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app

title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.

Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app

Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.

Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

Rooted with Magisk. Working fine but now stuck on Bootloader. HELP!

I rooted my galaxy note 10+ with Magisk the other day. everything was fine until i gave an app root access to uninstall another app that i had converted to a system app....as soon as it was uninstalled a message popped up saying it had to reboot and did so automatically only to get stuck in Bootloader.
I can access recovery mode and downloader mode, i have tried wipe/reset, wipe cache, flashing original firmware back on etc and it just ends up back at the bootloader. someone please give me some advice.
i tried using ADB but only some commands work and mostly all the useful ones say error or closed.
I unfortunately do not have a custom Recovery either as this is my first rhodeo for Rooting and in hind sight i should have done more research. I have attempted to flash TWRP Recovery onto my phone via Odin but it either does nothing or takes me to the same boot screen but with errors and locks me out of base recovery mode.
I have been at this for hours now losing my marbles!:crying:
CAN SOMEONE PLEASE GIVE SOME ADVICE/INSIGHT...I HAVE SPENT ALL NIGHT TRYING MULTIPLE THINGS AND GOOGLING TO NO AVAIL.

BuBz1990 said:
I rooted my galaxy note 10+ with Magisk the other day. everything was fine until i gave an app root access to uninstall another app that i had converted to a system app....as soon as it was uninstalled a message popped up saying it had to reboot and did so automatically only to get stuck in Bootloader.
I can access recovery mode and downloader mode, i have tried wipe/reset, wipe cache, flashing original firmware back on etc and it just ends up back at the bootloader. someone please give me some advice.
i tried using ADB but only some commands work and mostly all the useful ones say error or closed.
I unfortunately do not have a custom Recovery either as this is my first rhodeo for Rooting and in hind sight i should have done more research. I have attempted to flash TWRP Recovery onto my phone via Odin but it either does nothing or takes me to the same boot screen but with errors and locks me out of base recovery mode.
I have been at this for hours now losing my marbles!:crying:
CAN SOMEONE PLEASE GIVE SOME ADVICE/INSIGHT...I HAVE SPENT ALL NIGHT TRYING MULTIPLE THINGS AND GOOGLING TO NO AVAIL.
Click to expand...
Click to collapse
If anything, you'd probably have to do a full wipe and restore back to stock.

BuBz1990 said:
I rooted my galaxy note 10+ with Magisk the other day. everything was fine until i gave an app root access to uninstall another app that i had converted to a system app....as soon as it was uninstalled a message popped up saying it had to reboot and did so automatically only to get stuck in Bootloader.
I can access recovery mode and downloader mode, i have tried wipe/reset, wipe cache, flashing original firmware back on etc and it just ends up back at the bootloader. someone please give me some advice.
i tried using ADB but only some commands work and mostly all the useful ones say error or closed.
I unfortunately do not have a custom Recovery either as this is my first rhodeo for Rooting and in hind sight i should have done more research. I have attempted to flash TWRP Recovery onto my phone via Odin but it either does nothing or takes me to the same boot screen but with errors and locks me out of base recovery mode.
I have been at this for hours now losing my marbles!:crying:
CAN SOMEONE PLEASE GIVE SOME ADVICE/INSIGHT...I HAVE SPENT ALL NIGHT TRYING MULTIPLE THINGS AND GOOGLING TO NO AVAIL.
Click to expand...
Click to collapse
Could yo solve the problem?