Database Users

SBF fails, factory restore fails, flashing new ROM fails, rooting fails.. WTF!?!?!

I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!

lwright84 said:
I literally cant do a damn thing with my Droid 2. This all started when I started noticing an increasing number of Force Close popups. I hadn't installed anything new recently so I just rebooted and dealt with it. At this point, it was a completely stock Droid 2 with only market-approved apps installed.
So, I decided to do a factory restore and... it didnt work. It sat at the recovery screen and did nothing. I pressed search and selected wipe data\cache and it said something to the effect of "Cant open E:\recovery\something" but the Wipe data\cache completed successfully. Needless to say, my issue remained.
So I found the stock recovery SBF and went to flash it... it got to 98% on the final step and then said FAIL. Error message: Failed flashing process. Error verifying Code Group 31 checksums. File 0x4BAF (0x4007031); phone connected. The phone still show SW Update when this occurs, and then eventually "completes", reboots, and boots back up as if nothing ever happened.
So then I tried the root process so I could install rom manager and try EUnleashed or something. The rooting steps all took, and I tried to open the Superuser app it just stuck on a blank screen. So I rebooted, and wtf.. it disappeared.
So then I went to Applications and uninstalled every single application except for Maps, rebooted, and WTF THEY ALL CAME BACK AGAIN. I did this 3 times and each time every single app was reinstalled and working after a reboot. Only now I cant complete the root process again, and Rom Manager doesnt work.
So, to recap... I cant do a factory restore. I cant flash the stock SBF. I cant root. I cant do f*$&#*$ ANYTHING!
If I cant fix this today I will be giving this junk phone to my 2 year old because that's about the only thing this POS is good for. I never had any of these issues on my Droid, Droid X, or Samsung Captivate. How Motorola could fail so hard while simultaneously succeeding so well with other devices is mind-boggling.
HELP!
Click to expand...
Click to collapse
I think you might be overreacting here.
First, I haven't flashed the SBF yet but I do remember seeing the fail screen on original Droid SBF flashes and it was something you could ignore. You booted back into Android, right? That means it worked.
Second, the Superuser app is supposed to show a blank screen because the purpose of it to manage apps to which you have granted to superuser permissions. If you just installed it, there would be nothing listed.
Third, Froyo restores apps if you have "back up my data" checked under Privacy settings.
Fourth, you never mentioned the Droid 2 bootstrapper. I wouldn't expect ROM Manager to work properly without it.

First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.

lwright84 said:
First, no that doesnt mean it worked. I boot back into my exact same Android install as before. Same settings, same notifications, same alarm, same problems, same everything. If it was successful, it would be like a factory restore (Which I cant even do).
Second, ok that makes sense. But after rebooting it disappeared and RomManager wouldn't recognize that it was rooted. Now the rooting process wont work at all when I try and redo it.
Third, I dont think this is the same thing. It's not restoring apps... the apps are there as if they were never removed. Same customizations, settings, etc.
Its like my D2 is stuck with a certain "image" on it, and it wont let me edit, delete, format, reinstall, or reimage. It's infuriating.
Also, ROM Manager works without bootstrapper as long as you have Superuser. Ive used it fine on my Captivate.
Click to expand...
Click to collapse
Captivate is not a Droid 2. I'd be surprised if it works without the bootstrapper, since that's the only way to flash anything on a Droid 2.
My suggestion is to keep trying the SBF. Once you get it to work, get the SW update and then root. From there, I wouldn't go messing with anything in ROM Manager until you confirm the files are 100% legit for the Droid 2. As far as I know, only a few themes are working without issue on the Droid 2 - the ROMs all have bugs.

The same thing happened to me. I am assuming we were using the same instructions to flash the .sbf. Here is a link to instructions I followed.
http://forum.xda-developers.com/showthread.php?p=8245826#post8245826
I did not heed the red flag I got when I unzipped the .jpg file. I saw some error message and ignored it, and went ahead with the procedure to end up as many others with "fail".
Long story short, I deleated the .jpg file and downloaded it again.
When I used 7 Zip to extract the files, this time I had no error msg and everything went smoothly.

[Q] "Unfortunately, settings has stopped working" after factory reset

Hello folks,
The SGH-i337 is my first android device and I've had it only for a few days now. I rooted the phone using the "1 click root and debloat" files in the development section of this forum. Everything worked great after that. Today I installed an unofficial apk on my phone but I wasn't comfortable with it at all. So I did a factory reset (are you not supposed to do that?)
After the factory reset, the phone boots up and gives me the usual settings menu. At the end of the settings however, it lags for a few seconds before it says "Unfortunately, settings has stopped working". This brings me back to the "choose a device name" menu in settings. If I fill it out again and go through settings, it crashes again. I can't get into anything else on the phone since it keeps going through the initial setup.
I've tried booting into recovery mode and deleting the cache. I doubt that this clears it since the phone gives me an error and reboots. I tried selecting factory reset through the recovery mode but that also gave me the same issue (said error and rebooted).
After some searching I've found that flashing a stock rom with odin might be the best way to go. Is that correct or is there a better way? On the odin download page, it only lists the 9505 version for Galaxy S4. Could I use that for my SGH-i337?
I think the phone is still rooted because it says Samsung Custom before booting up. Thanks for the help!

Had same exact issue as well.
I booted in to download mode and flashed it with factory rom, then installed CWM.
This is what i used. http://forum.xda-developers.com/showthread.php?t=2297033

KGB7 said:
Had same exact issue as well.
I booted in to download mode and flashed it with factory rom, then installed CWM.
This is what i used. http://forum.xda-developers.com/showthread.php?t=2297033
Click to expand...
Click to collapse
Oh man, you're a life saver. I'm downloading the file and I'll give it a shot. So just to confirm, I put the phone into download mode and run Run_Me.bat and that should fix the issue?
Also for future reference, are you not supposed to do a factory reset after rooting your phone? Thanks!

Fixed it
The issue arose because the settings program was supposed to follow up with at&t locker setup. But since I had deleted the at&t files with the debloat tool, it kept crashing. So the solution was to reset the phone to stock firmware. I used Odin 3.07 to flash the factory ROM onto the phone and now everything is back to normal.
I guess this also answers my previous question, if I'd probably have the same problem again if I do a factory reset.

aleatoric said:
The issue arose because the settings program was supposed to follow up with at&t locker setup. But since I had deleted the at&t files with the debloat tool, it kept crashing. So the solution was to reset the phone to stock firmware. I used Odin 3.07 to flash the factory ROM onto the phone and now everything is back to normal.
I guess this also answers my previous question, if I'd probably have the same problem again if I do a factory reset.
Click to expand...
Click to collapse
Just dont use all in one tool as you did before. Just use the chooper rooting process in the link I provided.
Then manually remove the apps you dont with titanium backup.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Help with Root and Recovery please!

Hello.
My Galaxy S4 was dying so T-Mobile just replaced it with an S5. It came with:
LMY47X.G900TUVS1FOJ4
I clicked on Software updates in About device and it did whatever updates, but the version stayed the same. Then I went to autoroot [dot] chainfire [dot] eu and downloaded the correct file to root. I unzipped the file and ran Odin 3.10.6 that came with it. I was able to root the device no problem.
What seemed like a problem afterward was that I couldn't find SuperSU in the Application list. I know the phone was rooted though because I could launch Titanium Backup to restore all my stuff from the S4. I went to the Play Store to download SuperSU. It kept complaining that I needed a new binary, but it would fail every time to update. I even tried downloading the latest SuperSU zip to install in the recovery mode, but that failed too. I really wasn't too worried about this.
While looking up how to root the S5, I saw some posts where people mentioned their root access stopped after 24 hours. I just experienced this when I launched Titanium Backup to begin uninstalling bloatware. I was informed that I didn't have root access anymore.
I figured I'd try to reflash the auto-root through Odin. According to Odin, everything passed, but looking at the device, it said it's already patched and the restore failed, so it aborted.
Now the device is stuck in an infinite reboot loop. I can access both the download and recovery modes, but that's it.
I'd really really like to not have to do a factory wipe as it was a pain to get everything copied over from the S4.
Can I flash it with something else?
Once I can get back in the device, how do I keep the device rooted? Do I have to flash TWRP or CWM?
The only root program I use is Titanium Backup and would really really like to keep using it to makr regular backups.
Thanks a lot.

Try booting into recovery and wiping the CACHES
If it still won't boot, grab a stock ROM from sammobile .com for your model S5 (G900T by the looks of the ROM name) and flash it with ODIN from download mode
That won't wipe your data or anything you've restored, as long as you don't reset
If it still won't boot, you might have to suck it up and factory reset after flashing stock
Was the TiBu backup you restored, rooted? Maybe restoring the backup restored an old version of SuperSU and broke the CF AR version
Might need to go down the TWRP and SuperSU from TWRP recovery route to get it rooted properly if CF AR isn't woprking 100%, which it doesn't for a fair few people

I tried clearing the cache, but that didn't work.
Is there a way to download the stock ROM without having to create an account on the download site?
The Titanium Backup I restored was rooted. Everything was totally fine, until I went back to TB and it suddenly told me I wasn't rooted anymore.
I did try TWRP after I made the original post. I think messed up the device, but I can get in now. I flashed the latest version and booted into Recovery Mode. I clicked on Fix Permissions and possibly one other thing. It let booted farther before the infinite bootloop. It'd show my lock screen and give me 1-2 seconds before rebooting. If I swiped quickly, I could see the home screen with most of my icons gone. Clicked on Apps shows most of the apps are gone. When I removed the SIM card, I stopped getting the infinite bootloop. Here are the list of important programs I have left:
Contacts (all cleared out), Gallery (all present), Messages (all present), My Files (shows files from previously installed programs that I can no longer access), Phone (works when I put the SIM card back in), Settings
Unfortunately, TB and the Play Store are both gone. I might be able to install stuff using adb or by copying files over. I haven't tried, but it doesn't look good. I tried reflashing the CF ROM. It didn't change anything. I suspect I may be looking at a factory reset at this point. I'm happy to try any other suggestions.
Thank you.

whynoteel said:
Is there a way to download the stock ROM without having to create an account on the download site?
Click to expand...
Click to collapse
Wut? lol, just make one, it's free...
XDA does not spoon feed

I created an account and downloaded the stock ROM. I flashed the device and got most of the programs to appear again though the Play Store was still missing. I decided to cut my losses and just do a factory reset. I rooted again and put everything back in place. Now I'm experiencing the problem where I lost root after a day or so of use. I'll start a new thread.
Thanks for your help.

Issues After Root - Rotation and Encryption

Howdy,
I got a new Note 4 from Bell Mobility about a month ago...
I updated the software, rooted it and installed the Wanam modified Xposed framework.
I have lost the automatic rotation, except for the built in camera software. Nothing else will auto-rotate. Checked the gyroscope and checked a few 'leveler' applications - all tests pass. Oddly I noticed the camera software still auto-rotates, no idea why it is special.
I tried the Wanam Xposed module to 'Enable all rotation angles' it has made no difference. With screen rotation software, currently have "Rotation - Orientation Manager by Pranav Pandey" installed. Auto-Rotate On and Forced Auto-Rotate neither option will rotate the screen when I turn my phone. If I choose Forced Landscape, it will go into Landscape mode. The only way to return to Portrait though is to use one of the Force Portrait options though.
My other issue is with turning on Device Encryption... Using SuperSU Pro for su..
If I just go through the prompts without changing anything, it reboots but doesn't encrypt.
First I tried installing as a system app so I could use the Disable function in the Android Application Manager, as I did with my Note 2, SuperSU tells me "Not (currently) available in system-less root mode".
If I turn off "Enable Superuser" in SuperSU, encryption enables properly, but I am unable to turn the "Enable Superuser" again, it says it has to update, but the fails. Suggests a reboot and try again. Sadly, this did not help.
I had success with one of the exploit root methods, KingRoot. While this worked when my phone was encrypted, it wasn't stable and kept popping up stuff. I tried to replace it with SuperSU, there are a few guides written to do just that, but they all indicate that it is very hard to get rid of, regardless, none of the guides worked for me. I ended up resetting the phone and starting over...
I tried the CLI command to start the device encryption from a # prompt..
vdc cryptfs enablecrypto inplace password 1234567890abcdef
The phone rebooted a couple times, but took a very long time (hour plus) to come back to the Android Lock-Screen.. But still a non-encrypted device. If I intrupted the process because I thought it had crashed, it started up and immediately told me something when wrong with the encryption and I need to use Recovery to reset the device..
As for root methods, I was using the CF-Auto-Root at first, trying to look for solutions to both issues, I tried a few ways of getting SuperSU installed.. The last time I reset I tried the "SkipSoft Unified Android Toolkit" method. 'Grasping at straws' to get SuperSU installed into /system so can use the Applicaiton Manager to disable and enable it...
My mobile's specifics, if it matters..
Samsung Galaxy Note 4
Model number - SM-N910W8
Android Version 5.1.1
Baseband version - N910W8VLU1COK3
Build number - LMY47X.N910W8VLU1COK3
Currently have the Team Win Recovery Project v2.8.7.0 recovery software installed.
I am looking for suggestions for both issues, but really want to avoid resetting the phone if I can at all possible... Yes, I have Titanium Backup Pro installed, but have never actually gotten a restore to properly restore all my applications and data... I rely on it now just for the Uninstall and Freeze features.

For an update,
I also noticed that rotation works on the Lock Screen and in the camera applicaiton.
If I rotate my screen on the Lock Screen, the red handset picture and camera icons rotate.
If I rotate in the camera application, nothing changes position, but all the icons rotate as well.
I'm still completely stuck though, open to suggestions...

For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.

uchihakurtz said:
For rotation, it is likely caused because you removed the com.thingy.facebook system app. I tried removing it because I thought is was bloatware but read somewhere that messing around with it cause the auto rotate and pedometer to fail. I fixed it by reflashing the rom without data wipe then never removed it again. Page Manager is safe to remove though.
Click to expand...
Click to collapse
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.

kevinds said:
Thank you,
I had it frozen for a while, completely uninstalled it, trying to see if lack of space was why I couldnt' get SuperSu to become a System App..
I will try to put the facebook app back to see if that helps. Hoping I don't need to do a ROM reset, but if that is what it takes.
Click to expand...
Click to collapse
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.

kevinds said:
Thank you http://forum.xda-developers.com/member.php?u=5047956
I tried installing FaceBook from the PlayStore, no change.. So I uninstalled it again.
Took a backup in Titanium Backup and in TWRP.
From the stock image, I extracted system.img.ext4 and used SkipSoft's application to make just this file Odin flashable..
Flashed it.. When I got back to Android, my phone hadn't reset (what I was going for ), rotation is working, SuperSU still giving root access
I went back into Titanium Backup, the freshly installed apps were listed on top, because there was no backup of them.
Froze each, one at a time and checked the rotation after each.. Froze all the apps with no backups, and rotation stayed working, which I thought was odd for what fixed it.
So.. The Facebook applications are all frozen, as they were before I erased them the first time, and rotation still works. Hurray..
Now for the device encryption, I will keep messing with it.. Trying FlashFire to mount System as RW and to write the newest version of SuperSU, hopefully it will install to System this time.
Thank you again.
Click to expand...
Click to collapse
This is amazing, can you please post the odin flashable file? I am having this exact problem right now because I removed it in TB. Is it just the facebook file that are flashed? Thanks so much in advance, you're saving my life here

My rooted smt-350 crashed (kind of)

I rooted my smt-350about a month ago using chainfire and odin for my brother. Yesterday, suddenly many of the system apps started crashing, including the default launcher. I restarted the tab, but in vain. It stooped detecting the SD card. Third party apps are working fine but they are also not sensing the SD card. The tab worked fine before this happened. The tab doesn't have custom recovery or ROM.It has SuperSU. I am not an experienced rooter so please explain your solution. Thanks in advance.

Sounds Like you deleted Something you shouldn't have. Think of root as removing the protection that keeps you from screwing up you device. When you rooted unlocked the device and made read only files now read and write files. Did you install any apps from unknown sources(Not Google Play Store)? May have installed a bad app or just accidentally deleted something you were not suppose to. Easy to fix if you can stil get to download mode and find your stock firmware. Then flash it with Odin. Then reroot and be more careful this time and also make a back up with Titanium Backup from the play store(Needs root). Let me know if you need help with this I can walk you though it...