Hi! I've got a Galaxy Tab P100 CDMA tablet with interesting problem: after any reboot or power off my device goes back to initial state just as after data wipe. I can work with it almost fine, sometimes different apps are crashing, but just till reboot.
I tried to flash different roms, stock and custom, kernels etc... Nothing helps...
Also after data wipe or reboot system automatically sets up some weird google account [email protected] and I cannot delete it. I think it is all the probem. And also I think, I need to flash stock csc files, but I can't find it...
Can anyone help me, please?
Related
Hi
I got a rooted Samsung galaxy plus 9001.
I installed font changer and busy box.
With the font changer i chose a ttf font from the internal memory card, and after applying it, i got the pop up menu reboot now.
After clicking on reboot now my phone stuck in reboot loop.
I can access android recovery menu, i treid wipe all user data but still stuck in reboot loop.
Please help me guys.
You'll have to reinstall the rom you were using... that should get you out of bootloop. If that doesn't work, do factory defaults (you'll lose all apps and settings!) and install the original rom again (or for instance XXKPS).
One more tip: always make a (cwm/feamod) backup before changing system defaults
Regards,
Nika.
Thank you.. Thanks alot
nikagl said:
You'll have to reinstall the rom you were using... that should get you out of bootloop. If that doesn't work, do factory defaults (you'll lose all apps and settings!) and install the original rom again (or for instance XXKPS).
One more tip: always make a (cwm/feamod) backup before changing system defaults
Regards,
Nika.
Click to expand...
Click to collapse
any link to step by step instructions on how to do this available anywhere?
i have similar boot loop problem.
I doubt anyone has created that. How did you get into the loop?
Sent from my GT-I9001 using xda premium
Boot Loop
When you are stuck in the boot loop:
1. Take out the battery and re-insert it.
2. Put the phone in download mode (using 3-button combo - down+home+power)
3. Open Odin, and reinstall the stock firmware (using all 3 md5 files: PDA, CSC and PHONE); you will be able to find the files in the stock firmware 2.3.5 from the post in XDA-stock gingerbread roms for i9000.
4. After you have done this, root your phone, install custom kernel, and then install custom firmware through custom recovery menu.
Thats the way i did it....i dunno if there is a short cut to it.
Hope it helps!
I also find bootloop can be resolved by going into download as stated by puneetgandhi and flash a VOODOO KERNEL using ODIN (it goes on PDA).
Then booting to recovery and turning off all lags.
Link to the stock firmware page i was referring to:
Link to the stock firmware page i was referring to:
http://forum.xda-developers.com/showthread.php?t=846913
nikagl said:
I doubt anyone has created that. How did you get into the loop?
Click to expand...
Click to collapse
No idea, it has been going in and out of boot loops a few times already for last few months works fine for ages. All of a sudden it would starts lagging on an app or when texting and reboots into a loop
although i never had the problem on froyo only in gingerbread (a few week or so after i got my phone back from repair shop, they upgraded it to gingerbread without my notification, but since i had voodoo on before on froyo i don't know, maybe they updated it wrongly ).
First time i fixed it with a fix on here about transferring a system file through odin.
second time it fixed itself after i left it for a day as i didn't have time to fix it .
this time i finally fixed it with a factory reset for the 4th or 5th time in a row, after wiping cache and so on, didn't work first few times.
So not sure whats causing it, could be a failing internal memory card i suppose or overheating corrupting the memory, hoping its a software issue that the factory reset will permanently fix (but doubt it).
If you were on Froyo, please look or create another thread for I9000 Samsung Galaxy S. This thread is about Samsung Galaxy S plus I9001... That's the device I own, and stuff like Voodoo and Froyo do not exist on SGS+ (and I have no experience with - probably other with an I9000/SGS do).
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
I recently updated my gt-p1000 to cm10, by following a youtube tutorial. After Two days of use , i encountered a bootloop.
i tried factory reset and wiped dalvk cache, cache but it still ddnt work. i then put ICS, (CM9) but still ddnt work.It still keeps restarting.
then i tried to install the latest kernel, but after i did this im stuck on the cyanogenmod logo, it just keeps rotating. I then used odin and down graded to the stock rom, and im suprised that the restarting still ddnt stop. It just keeps restrating every 20-30mins or sumtimes just after u turn it on, (10sec). Pls help Me, i've dont everything told on the internet ( wiped cache, dalvk cache, factory reset, formated sys) EVERYTHING!
Hi,
It sounds a lot like a stuck power button issue to me. Especially if it behaves the same after returning to stock.
But for other opinions and ideas, I will have your thread moved to your device section.
Good luck!
ted my galaxy tab p1000 2.2 froyo with z4mod.
Then initially I installed cwm with ROM manager for galaxy tab T because there wasn't any specific model of cwm for p1000.
But but when I switched off and booted recovery, stock recovery always came......I could access cwm only through the ROM manager ("boot into recovery")....and that too if i choose any function it starts to load and when I press home twice it says "replacing stock with cwm" and that goes on forever...
So I installed cwm with Odin as I couldn't access functions like "install" in cwm without going into the loading phase.....but as the process in Odin finished, my tab started to boot and at "galaxy", the sceen got all pixalated and it went till " samsung " and the whole process looped........ Help!
I actually was trying to install lollipop 5.0.2...
OK, using my phone normally rooted. I sometimes get random reboots and it bootloops. I have to force reboot a few times by holding power, bixby, volume down etc etc and it boots up normally.
This time, it did the same thing and force rebooting got me to the lockscreen but kept rebooting at that screen. I plugged in to the computer and forced reboot and it worked fine but for some reason but it made me start the whole setup process again as if I factory reset the phone but everything was still there except settings were reset.
Brightness wasn't working, so I tried to reboot to see if it would fix the problem but it started to bootlooping again and NOW I can't get past the lockscreen without it rebooting.
What do I do. I tried wiping cache in recovery but no dice. Can I reflash the firmware in odin? I don't want to lose any data. I know about flashing home csc instead but I'm rooted and I don't have the modified ap file from magisk, so wouldn't it just wipe my phone?
From my experience with the Galaxy S3 and S4, you will need to flash the firmware with Odin which will wipe everything. Use Samsung smart switch or TWRP to make a back-up of your data.
StoneyJSG said:
From my experience with the Galaxy S3 and S4, you will need to flash the firmware with Odin which will wipe everything. Use Samsung smart switch or TWRP to make a back-up of your data.
Click to expand...
Click to collapse
things have significantly changed since those days, but youre half right. In the new firmwares, there are 5 files. 3 of them have to be flashes as normal, but the last 2 are the CSC and HOME_CSC, you can shoose whichever of the 2 you want to flash depending on whether or not youll end up factory resetting. HOME_CSC doesnt wipe whereas CSC does.
OP, flash the HOME_CSC and the other 3 files as normal in Odin and you should retain your data and fix whatever part of the firmware is having a seizure. If the problem persists, then youre stuck with alternate methods of data recovery, including but not limited to ADB'ing into it while in the bootloader screen so long that you have ADB enabled in dev settings and then flashing the CSC to reset it. If THAT doesnt fix it, then youre prolly boned. Prolly a hardware issue at that point.
Where do you get HOME_CSC files from? Been looking for it for my AT&T firmware.
My Tab S2 T719Y has started acting really weird recently. For some reason, it would stall trying to run any ROM that I flash to it.
I'm not certain if it's a LineageOS problem or something is dead in the tablet.
I can flash (the few available still maintained) ROMs offered on the forums for my specific model.
The flash would go fine and everything seems to boot fine. I can install GApps and all. Not a single error mesage.
Then it gets to the new device setup wizard and then it stalls with a black screen. Or in the case of having GApps installed, I can choose a language and press Start at the start of the setup wizard, but I end up in a "Just a min.." bootloop and the tablet is unable to do anything except go back to the language select startup page.
The tablet seems to be running fine beneath. The touch buttons light up and haptic feedback still works. By double tapping the Back button I can get the system UI to show that it's switching between apps, but leads to another blank screen. By pulling down from the top, I can even pull open the notifications bar and quick settings. And I'm able to switch them on an off fine.
I've even tried flashing old ROMs that I know for a fact would run fine, but those end up in the same dead screen.
I've tried wiping and formatting everything in the tablet: Dalvik, System, Data, Storage, Cache ... all to no avail.
What is going on here? I'm reading in some Reddit threads that there might be some data access problem?
How do I resolve this?
Restore the stock ROM using odin and 4-file firmware and check again. If it is OK, go ahead
Thank you! That miraculously revived the tablet back from the dead.
Game-R said:
Thank you! That miraculously revived the tablet back from the dead.
Click to expand...
Click to collapse
Where can I find 4-file firmware.? I tried using Odin to go back to stock 7.0, but the tablet after reboot stops at the Samsung logo. Tried flashing several times and same thing. Help!