HI Everyone, I am having this issue with my Note 3.
About six months ago I flashed the Lollipop software.
I backed up my S note files and could not recover them till I worked out this week they were in a zip file on my Google Drive.
Today I tried to get them back by downloading the Titanium file and restoring once I got Titanium working again.
I had to change my SuperSU too allow grant always and block Knox to allow Titanium to have root access.
Anyway, I tried restoring the file and it sat for about half an hour just saying it was restoring.
Then the phone shut off and restarted again.
Now I am constantly getting the Sorry S Note has crashed notification at 1 second intervals. I can see the phone is loading software in the background, but I cannot turn the notification off long enough to press anything else. It wont stop looping.
I have tried booting into recovery and wiping the cache and partition and factory reset. When the phone rebooted, it showed me the first setup page you see when you first start your phone for the first time, so I know the factory reset worked, but immediately the error started popping up again.
I tried booting into safe mode, and it still flashed up.
When you press ok, the notification immediately comes back again, so you have no time to do anything else.
You cannot go into settings, or press any other buttons, another notification shows up right away.
I am currently downloading a new firmware because I think this will be the only solution, has anyone else had this issue, if so how did you fix it, or will the new firmware be the only way?
Can you add screenshots pls?
*COUNCIL: S-Note use 2 folders that have to be in your internal memory: S Note Export (empty) and SnoteData (where you put your .spd files).
Related
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.
After i tried
http://download.chainfire.eu/397/CF-Root/CF-Auto-Root/CF-Auto-Root-klte-kltexx-smg900f.zip
on lollipop on vodafone uk, i got this error message on boot, i press ok and after reboot i got no root
Then i install superuser through twrp that i previously had and keep getting this error message on boot.
The thing is i cant get past it, its covering the whole screen no operating system ui just that in a white box and a press ok, which doesnt work until after 2 minutes.
EDIT: its just constantly saying programs has stopped responding in a loop and cant get into android system. How do i fix this, i tried fixing permission in recovery but that didnt work.
So what i can do without losing all my work on my phone.
I hope you made a backup before flashing root files
Boot into recovery, clear CACHES, reboot - see how you get on with that
If you flashed CF Auto Root, there was no need to flash SuperSU, as it comes part of CF Auto root, someone else just did that and ended up in a boot loop, had to wipe the phone and flash a stock ROM
Thats the thing i didnt, i watched a video saying it wouldnt delete your files rooting and decided not to backup.
I was stuck on samsung logo half the time and other times stick with "unfortunately MTP application has stopped." in a big white box blocking me getting into android.
I tried fix permission, clear cache and delvin cache and nothing worked.
I just system wiped and got in but lost all my work.
Fortunately Google backed up most of my photos and videos and contacts but no sms messages.
Now i gotta get all my apps back on my device and get it back to how it was and hopefully i did not mess any important texts.
Note to self: Always backup.
EDIT: i just had gaaps not working and giving server error, after trying out ways to fix that i tried all the normal stop app and clear cache, and then did fix permission in twrp, and after doing "also fix SELinux contexts" it messed me over and got me back to that white box.
so another note to self not to use "Fix SELinux contexts" as that messed up my system after getting 30 apps back installed.
Hi guys,
I have a problem as I post a thread. I have recently owned a note 4. Before changing phone, I decided to configure all the note 4 settings and apps, root, install twrp and SD fix. All worked fine. So i did a nandroid backup with the app "online nandroid backup". After that, I transfered my sim from my xiaomi Redmi 1 to the note 4, and I continued doing other things :
- 15th july: I put the sim to the note 4.
- 16th july: I messed up my phone because i accidentaly deleted the google framework odex file. So i wanted to restore the nandroid backup done by the app "online nandroid backup" when I finished configuring my note 4 but it failed. So I re flashed stock rom, re rooted and restored backup from titanium backup.
- 17th july: I installed an apk of nova launcher and configured it. Trust me, it is not the prime version I pay the developer me! I installed the apk from internet instead of the app itself from the play store because I never download from play store.
- 18th july: I found that because I also restored the system data with titanium backup, the private mode didn't work, so I factory reset my phone with twrp and I restored only user app and data backup. I did a nandroid backup after that.
- 19th july: I messed up (again) with tasker and so I hadn't notification sound. I decided to re flash the stock rom but didn't work. After that, I left my home without my phone for 2h and when I came back, I sSAW THE FIRST RANDOM REBOOT.
- 20th july: To solve the sound problem, I decided to restore the nandroid backup. It works: the sound came back! But I saw again a random reboot.
The random reboots appear only two or three times per week: indeed, I remembered the other random reboots appeared on the 25th of July and on the 27th July.
The random reboots are special I think because they appear at any time: it appeared when I use the phone or when I don't use it. Moreover we can see the Samsung logo at the minimum brightness and it is infinite: I need to remove the battery to make it restart.
To solve the problem, I first thought that it was a problem from restoring any backup from titanium backup. So I factory reseted the phone using twrp to keep root and internal storage. Then I reinstalled the apps with the official Google backup and restore tool. But as I can see, the random reboots are still here because on the 27th July, as I said, a random reboot appeared.
- 28th July (so today): I removed nova launcher, then shutdown my phone and pull out the battery. When I reinsert it, the phone takes a long time to switch on. Finally, it said system is not responding and reboot and the message re appeared, and reboot... I must remove the battery and reinsert it to restart the phone correctly: the message doesn't appeared. I tried removing the battery one more time to see if the message apprear when I pull out the battery but it didn't appear. However, there are no reboot since, but I think it is because it appeared tomorrow (27th july), and I have to wait to see if the reboots are still here, but I think yes because of this strange message. Or it may be a pure coincidence?
Please help me with all this strange events! I said all I know!
Finally I solved it by deleting nova launcher. And the pop up is only a simple coincidence!
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.
Hello all, I my phone started turning itself off and back in about a week ago and today whenever I hold the home button down to bring up the task manager, this error message pops up. I've tried wiping the cache from r the recovery menu, and doing a delete data/factory reset. The reset seemed to work until my phone started updating and I imported my contacts from SD card. Now, once again the error message comes up whenever I hold down the home button. Could it be an update causing this, or did the virus come back when I imported my contacts? Any thoughts or suggestions would be appreciated. I should mention that I'm using the straight talk version of the S4.
The new google app update is causing this problem. Either turn it off via app manager or unistall the update
My husband and i both have the galaxy S4. We also noticed this issue around the same day you posted this! Have you figured anything out? Or fixed the problem?