I have a rooted Gt-P1000 it crashed and now right from factory reset it keeps saying process android.process.acore has stopped unexpectedly. I can get onto the internet through going back through the initial set up screen after reset. I can also download something to get a download failed to get to my files. All system files fail to restore.
I have no working menu settings and process android fault constantly appears. I also get process.com.android.setupwizard has unexpectedly stopped. I have searched the internet and found no answers.
I went and bought a new pad only to find z4root does not work any more. And oneclick is an unopenable file!
Hence i have an unrooted pad that is as much use as a chocolate fireguard and a rooted one that is corrupt. The unrooted one is crap as i work in saudi and need to run market enabler, which wont run here unless routed. Please can someone give me an UPTODATE METHOD OF ROOTING, TELL ME HOW TO FIX FAULT, THANX!
Do a hard reset: switch off the tab and boot into recovery by holding volume up and power button. choose factory reset.
NOOB rooting guide: http://forum.xda-developers.com/showthread.php?t=812367
Already done loads of resets, as above - after reset i still have all the above problems!
Related
I think that this problem has already been discussed before, but I could not find an answer. My skill level is too low...
My TAB is a Hong Kong Retail version, which is unlocked.
After successfully rooting my TAB using Z4root, I installed BootStrap for EURO TAB and then I could successfully install Paul’s Modaco R1 version. I did not experience any problems. Then I installed Richard Trip’s Kernel, and I am not sure if something went wrong (or was already wrong), but somehow I could not get access to the Market anymore.
So I decided to reinstall Paul’s ROM using ODIN, but somehow after a successful start, there was a red FAIL. I guess i probably used the wrong setting and fell into the protected boot trap? I tried to get into the boot mode again, but could not get in.
After many tries to get into the boot mode, I now have:
If connected to an adapter: there will be a phone+triangle+PC error message. Sometimes this message will stay on as long as the TAB is connected to the power adapter.
Sometime the phone+triangle+PC error message will get flash slowly.
I tried to leave it overnight and then charge it and get into Boot mode, but no success.
If I try to attach the TAB to a PC or Notebook, nothing will happen. Nothing will happen even after several hours.
So … what is the best way to solve this problem? Please help.
hi,
read these two threads, maybe it can solve your problem.
thread and thread
good luck.
regards,
mike
I did a hard reset and it worked...
Samsung Galaxy Tab: Steps For Hard Reset
by Mitch under Android, Hardware
A hard reset will reset the Samsung Galaxy Tab back to factory default settings. You would perform these steps if you want the device prepared to sell or return to the store, but you may also want to perform a hard reset if there are problems with the device that you can’t seem to solve using any other method.
Note: These steps clear data from the device. SD card data like your photos and music are not erased unless you choose to format the SD card.
1. With the device off, press and hold Volume Up and Power.
2. Release the Power button when you see the Samsung logo, but continue to hold Volume Up until the recovery screen appears.
3. Use the Volume buttons to navigate the menu and select wipe data / factory reset. Press Home to choose the selection.
4. Press Volume Up continue.
The Galaxy Tab should then go through the hard reset process.
If you have access to the OS, you can also perform a hard reset in Settings.
1. Open the Settings app.
2. Select Privacy.
3. Choose Factory data reset.
Hard reset probably won't work as it sounds like a bad flash... Any OS you flash will replace your stock OS which is why people say to backup EVERYTHING...
Right. A hard reset (if it works) removes user installed apps and their data. It won't restore anything, but it should return any user-made settings to the default.
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
Hello everyone,
I've been literally 12 hours searching for possible answers on how to repair my Galaxy Note N7000 which from what I've concluded, has a problem that can be easily repaired but I've found nothing but limitations when I have a go at it. It doesn't seem to be bricked as I can still access recovery mode, download mode and it effectively boots, it's only giving me errors.
Here's what happened:
1) I tried rooting it using UnlockRoot PRO. Paid the PRO version, detected the device. Later I find it says the N7000 with 4.1.2 is not compatible so the rooting process was never completed, so I rooted it using Root_SuperSU.0.95.Only-signed and it worked just fine.
2) Everything worked fine, downloaded Andromizer to customize the phone.
3) Changed the DPI size to test it, then went to Developer Options and changed the Animation scales to 0.5 to make it all run faster.
4) Rebooted the device. Once I did, I got nothing but "SystemUI has stopped working" together with "TouchWiz home has stopped working errors".
I checked around the web and so far, what I've found (and tried) is this:
1) There seems to be a bug related to TouchWiz and the Animation Scale option (or perhaps the DPI size option in Andromizer). So I tried to do a wipe data / factory reset through recovery mode.
2) When trying the wipe data / factory reset through recovery mode, I rebooted the phone, only to find the SAME errors after I registered everything.
3) First option that came to mind was to wipe everything and immediatly reinstall the Official JellyBean 4.1.2 firmware (at this point I want to pretty much unroot the device as I didn't know it was going to give me so much trouble). When I tried that, I realized that SUDDENLY, Odin (nor Heimdall) are NOT detecting the phone in download mode. I'm guessing it's because USB Debugging is turned off but, I can't access the phone settings. It's my only logical conclusion, although it should be turned on given I could install PhilZ Custom Recovery later.
4) I search around the web and it says it's a driver problem. So I uninstall everything, run CCleaner, USBDeview to uninstall everything related to the Samsung Galaxy. Reboot. Install drivers again. Reboot. Plug booted phone and let Windows detect the device, installed successfully. Reboot in download mode. Let windows detect the device, installed successfully. Run Odin: DEVICE NOT DETECTED. (It does detect it while it's booted though, only it doesn't work for **** obviously).
I've literally tried everything. I've tried checking for a way to install the firmware via Recovery Mode instead of Download Mode. I've tried checking for a way to remotely access the device and mod the settings from there using ADB, and I get the same problem in ADB, doesn't detect the device.
Also tried to reset settings to normal via PhilZ Custom Recovery which I managed to install later.
Isn't there just a way to reset all settings to normal? Shouldn't a factory reset do this? How can I get SOMETHING to work and try to recover the phone? Any Aroma Recovery Script? Any way to mess with the system folder and modify settings manually via notepad or something since due to the SystemUI / TouchWiz home errors I can't access the phone settings?
I'm barely awake at this point. Can't believe I've stressed myself this much. Please help. This is beyond retarded.
Thank you,
Z
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
I read the post but it seems you have done a lot of things and nothing worked. So what is the situation right now? You can boot as normal but cannot get any icons or settings as sysUI and TW crashes?
Try installing GB ROM then wipe/cache first. If good, root GB ROM then do full wipe. Then test ROM for crashing.
If good then install JB rom and test. Let us know.
unable to enter phone setting ？ then just simply look for a secsetting.apk for ur version then replace it n set the permission rw-r--r--
You could use adb to modify your build.prop
Sent from my SGNote
Makrilli said:
You could use adb to modify your build.prop
Sent from my SGNote
Click to expand...
Click to collapse
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
nice to hear that you had this one fixed
Glad to hear its working now.
n7000 touchwiz home stopped
Zardonic said:
Bwahahah, now I see why you guys enjoy calling newcomers "noobs".
It was a computer problem. I just reinstalled JB 4.1.2 from my netbook and it worked.
Weird as hell though, given that I updated my GT-N7000 to JB 4.1.2 through Odin in this computer and it never gave me any problems.
I AM going to learn some ADB / Android SDK though. I'd rather learn everything before something like this happens to me again.
I appreciate everyone's concern, and thank you all for it.
Click to expand...
Click to collapse
hi.... im having the same problem as yours. i dont know what to do
lulu2050 said:
i had the same exact problem just few hours ago.....first of all you should boot into recovery mood by pressing vol up+ home button+lock button until samsung logo shows and then wipe all data/factory reset and wipe all cache partitions..........if that didnt fix it you should try rerooting it againg after re wiping
Click to expand...
Click to collapse
I have tried to upgrade my touchwiz to the new one, but got the danger message, would clearing the cache help?
Sent from my SM-N910C using Tapatalk
Hello,
I've been rooted for a few months now and have never had any problems. I wanted to use that Milk Music app from Samsung so I followed the instructions and was able to get it working on my phone and have been for awhile. I recently decided it would be a good idea to change the build.prop file back to its original state, so I copied and pasted it in using Root Browser. (I had made a backup file stored elsewhere). Once I did that I rebooted my phone for the changes to take effect. After I did that I cannot get my phone to turn back on. It displays the LG animated logo screen and then goes completely black. The light on top of the phone radiates blue/green. I've read through several forums about this issue and have tried everything in order to get it to work and for some reason, using my computer and ADB always gives me an error: device not found. I have installed the drivers and everything. Anyone else run in to this problem before? I would really appreciate it.
If you are on stock rom, just rooted. I would think you should be able to factory reset through stock recovery.
Confirm the process but i think you power completely off. Then hold volume down and power at the same time when you see the lg logo release both buttons then press both buttons and hold them.
Should take you to factory reset.
Not 100% certain but this will probably be your next step if you can't get a computer to see it.
Good luck
2111
The factory data reset didn't really change anything. For some reason I cannot boot into recovery mode either. I can put it in download mode though, but my computer still has a problem recognizing it.
brody_low said:
The factory data reset didn't really change anything. For some reason I cannot boot into recovery mode either. I can put it in download mode though, but my computer still has a problem recognizing it.
Click to expand...
Click to collapse
If you can get into dl mode then you should be able to return it to stock which should reset everything. Returning to stock has its own downside but at least you'll be up and running again.
So I've had success rooting the SM-T377V thanks to electronhacker post on the forums.
I thought I would give my experience because anyone else doing this will most likely run into the same problems I did. I still have a few problems I am running into. I hope someone can help me out.
electronhacker had said to downgrade to stock firmware LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop, from firmware MMB29K.T377VVRS1BPL1 (6.0.1) Marshmallow using Odin.
I ran into problems finding LMY47X.T377VVRU1AOL7 but I eventually did find it on samsung-firmware.org Thank you moonsh0t!
It did actually work and passed with Odin, however it got stuck in a bootloop. I thought there was nothing that could be done but after looking into the bootloop matter more I figured out how to get out of it and start it up.
1.) Wait for the device to turn off while it's bootlooping.
2.) Then hold down the power button and the volume up buttons to enter recovery mode.
3.) Restore factory defaults. "I think this actually gave me an error but clearing the cache got it to work."
4.) Clear the cache.
5.) Reboot the device.
There you have it now you're out of your bootloop, the device will start up now.
Now that we have downgraded electronhacker had said to run a program called Kingoroot using the Windows application.
I ran Kingoroot and it got stuck at 44% and my screen went black and would not come on or turn off. I am pretty sure you call this a soft brick, but maybe it's called hard brick as there was nothing that could be done.
So this is what I did to Unbrick the tablet:
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
I tried to use Kingoroot again. This time it got stuck at 51% and my screen on the tablet got stuck. Nothing was responding, not the power buttons, the volume buttons, home button, nor the screen. This is because Google Application had showed up on the tablet while I was in the middle of rooting. The Google Application said "Do you want to enable Google Security?".
Again;
1.) Hold the power button and the volume down button for 15 to 30 seconds.
2.) The screen should come back on.
3.) Scroll through settings to reboot device normally.
The device booted normally and I tried Kingoroot again. I wasn't going to give up. This time it worked, 100% Root Successful. I couldn't believe it the SM-T377V was rooted. I checked and verified with Root Checker.
Now this is where I need help!
#1.) The device only stays rooted until you restart it. Then you have to Re-Root it with Kingoroot every time you restart. I found out if you run SuperSu and go into setting you can stop this from happening. I'm not exactly sure what you do yet because I can NOT get into SuperSu. It tried to install the binaries but gets interrupted by Knox. It says disable Knox on SuperSu but this does NOT work. This tablet does NOT have a way to open Knox in order to disable it. So I need to figure out how to delete it that way I can run SuperSu and stop the never ending root process. So if someone could help me figure out how to do that I would very much appreciate it.
So far I've figured out that you can run an application called Titanium Backup to freeze the Knox files and then remove them followed by a Re-Boot to get rid of Knox. I looked further into my SuperSu problems and found out that you can manually download a SuperSu.apk file that should bypass Knox and actually disable it.
Here is my new problem, installed Titanium Backup from Google Play Store only to find out that I can't freeze the Knox settings unless I pay the $5.99 for Titanium Backup Pro. So I removed Titanium Backup and downloaded Titanium Backup Pro.apk which I found for free on the internet. I can NOT install it though, because I have a new error that says "APP not installed".
This happens with the SuperSu.apk that I found on the internet too. I've tried a lot of things but can't get them to install. Google Play Store gives me error (-504) I've tried clearing cache and data for Google Play Store and Google Play Services but no luck. I even tried downloading APK Installer but it doesn't even work. Please help I don't know what to do.
02-09-2017
<UPDATE>
I'm at a loss, so I decided to do a factory reset from settings and that did not get the applications to install. So then I tried to clear the cache but again no suck luck. Then I decided to enter recovery mode and factory reset, but then got stuck on "Your tablet is getting ready for you". or something along the lines of that and wouldn't get past that on start up. (This is because I disabled setup with another application, and is my fault.) Not being able to get past that I realized I had no choice but to Re-Flash the System Update LMY47X.T377VVRU1AOL7 (5.1.1) Lollipop with Odin and that was successful, thank God. Now I have to Re-Root and before installing the wrong applications, which are Google Play Store SuperSu and Titanium Backup. Reason being that once you install these once and uninstall them you can't install them again without getting error (-504) in Google Play Store or even outside the Google Play Store such as manually downloaded .APK files or you will get the error "APP not installed".
Here is my idea, and I haven't done it yet. Re-Flash, Re-Root, Install for the FIRST time the right SuperSu.apk and Titanium Backup Pro.apk in order to disable Knox and stop the never ending Re-Root every time the tablet it restarted.
02-10-2017
<UPDATE>
I have been running Kingoroot with my PC using USB. This gives me temporary Root access until Re-Boot. So I installed Kingoroot.apk and tried using to mobile application but this one works, but I get stuck in bootloop on restart of tablet. Then have to Re-Flash with Odin to get out of bootloop. I'm not having any luck.
#2.) Even with my temporary root I can not seem to install Xposed because of SDK 22 not supported. I was wondering if anyone knows a way to get it to work on SDK 22 so I can run IMEI Changer. Unless there is another way to change the IMEI without Xposed.
Thank you to electronhacker for your post I found on this forum which has made me a lot of progress, and thank you moonsh0t for your help redirecting me to find that firmware. :good:
I just got a SM-T377V this weekend and have been trying o root it as well. Wow seems like nobody has had any luck getting a reliable root on it. Please update me as you keep at it! Brent your attempts at this are amazing!! Keep at it!
I'm trying to get this thing rooted too, so please keep me updated if you find a
Way!! Thanks for your help!
Yep
Ok
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Alright, so your goal is to run an IMEI changer, but why?
Also my luck was to get it temped root and try and use chainfire's supersu to take over.
from there I tried unlocking the bootloader with samdunk. The issue though, is the CID was deleted from the tablet, so when I restarted, never ending bootloops.
I just Odin'd it back to the AOL firmware today, will look more into samdunk later.
Treyday645 said:
Same issues here. I never have trouble rooting with the APK, but its super annoying having to reroot all the time. also the superuser app is absolute cancer so learning to replace that would be dope.
Click to expand...
Click to collapse
If you use Odin to flash android 5.1.1 via package T377VVRU1AOL7, you can use the kingroot or kingoroot app (desktop or android) to temporarily root the device. From there, if you delete the kingroot or kingoroot app from the device you can use SuperSu to take the binary over. From there you can use any flashing apps you'd like.
The issue is at this point, the second the device turns off, when it comes back it will no longer have root. (note so far in my attempts I've found that Kingroot, will reboot rootless, whereas kingoroot will bootloop.)
Kingoroot will bootloop because it modifies the boot file in some way, which causes the bootlooping. The work around to this is just flashing over the previous android. However, if you flash with Odin, you lose root, but keep your files.
Going back to flashing, when you attempt to use Odin to flash other packages, they are denied, due to the locked bootloader, however, you can use Flashfire to flash these firmwares. I attempted to flash the T-377P firmware and bootloader. Obviously the locked bootloader stayed locked, the recovery partition got errored out, but the android system itself actually started. Just sans root.
It's worth noting I've also attempted using SamDunk, the S5 bootloader unlocking tool, and so far all I've noticed is it deletes the CID file and doesn't finish. So I'm of the impression that the temp root, isn't a full root either.