General :: Galaxy Tab GT P1000 - Stuck After Factory Reboot?
Oct 7, 2013Samsung tab GT-P1000 is stuck, I tried the factory reboot, wipe data and reboot, nothing is working, is it a brick now?
View 3 RepliesSamsung tab GT-P1000 is stuck, I tried the factory reboot, wipe data and reboot, nothing is working, is it a brick now?
View 3 RepliesI am using HTC Explorer A310e. I rooted my cellphone yesterday. After rooting my cellphone, I had WhatsApp install and uninstalled couple of times, which led to some corruption as well. Thought of clearing the space by "Factory Reset" option with an intention of retrieving the built in apps.But after I did this, runs a process of resetting and when it restart it stuck at the main screen where HTC comes out on the display. My cell phone is not running beyond this screen. Cellphone screen is still on and displaying the "htc" only.
View 6 Replies View RelatedIm using a galaxt tab GT-p1000 3g froyo 2.2 which is bought from dubai . there were few issues since last few weeks where i could not boot the device. I have done the factory reset few times also. After that i rooted the device using oneclick(SuperOneClickv1.9.5-superoneclickdownload.com) it was completed and rooted where i got the superuser too.now the device is not getting booted again. it shows the samsung logo and getting dragd.i tried reset and reboot through the recover mode that also dosnt work.
View 1 Replies View Relatedmy samsung galaxy tab GT - P1000 is always hanging & restarting especially if i m connected to the internet, what do i do ?
View 1 Replies View RelatedI have flashed the GT-P1000 tab with clockworkmod version 6 (i am not sure the exact version) using Odin.Now after flashing the recovery, I have successfully installed Cyanogenmod 11 (nightly build) and everything was successful and everything is great.
A friend of mine borrowed the tab and he put a pattern to lock the phone, instead of asking him what is the pattern I just decided to wipe the tab again to make a clean install. So what I did was I went to recovery and selected "format /system" which I shouldn't have, then after rebooting it is not booting up to Cyanogen anymore, so what i did was I just wiped everything (format /data, cache and factory reset)
Now this is the weird part, the devices has kept on booting up to clockwork recovery and it says the device is not yet rooted, it is asking me if it is ok to root it, I always selected yes
After another boot up, the clockwork recovery is now version 3.0.0.5??? it is really weird? I never installed any clockwork mod with a lower version... How did that happen?
Now whenever I try to install from sd card or restore it or mount it nothing happens, it just says:
E:Can't mount
E:unknown volume
E:unable process volume! skipping
I tried to flash the recovery again using Odin many times but still the clockwork mod is stuck in version 3.0.0.5.
Right now, I am not sure if my understanding of the entire system is correct:
1. Should I install a new recovery, if yes, how and why is it whenever I am installing it again it is not being installed, it gets stuck to version 3.0.0.5?
2. Are there any other recovery I should use and how should I install it? is it the same as using the Odin?
3. Is there a way to install the original recovery of this tab and then from there I will start over again.
I pressed hime, down key, and power to boot into the recovery console on my virgin mobile Optimus V. Looked around and told the phone to reboot when I didn't see what I was looking for. Phone was rooted previously using Gingerbreak.APK v1.20 After reboot phone was no longer rooted? Also programs and such were deleted, but super user app remained. Downloaded and installed gingerbreak again. Fire it up and I get a big, fat, steamy pile of "Could Not Extract Assets!" error message. Tried a couple of fixes I saw on the developers site, but nothing seems to be working for me. How to get my phone rooted again. I have Terminal Emulator on my phone, or I can do it through my computer's cmd window. Either way works for me. I've been sifting through and trying all kinds of stuff for the last 5 days.
View 2 Replies View Relatedhave a problem with my acer iconia b1-710 16gb. I tried to install custom fonts with rom tool box and when it asked me to reboot my device I got stuck on acer logo.
View 4 Replies View RelatedI am stuck in the recovery mode "FACTORY MODE" in my phone. I've enter in the recovery menu (power + volume up down) then I enter Factory Mode, then Item Test. And in this item test I don't have an option to return to previous menu tree, my phone only have UP, DOWN and POWER buttons, and none of them goes back to initial menu. Also the battery is non user replaceable, so I'm completely stuck in this screen. It's a motorola razr D3 XT920. I'm going nut's.
View 2 Replies View RelatedI'm using Xolo q800. recently when i took it out from my pocket, it was turned off. so i turned it on,
the logo appeared but it directly goes to factory mode.
i can go up and down in factory mode but im not able to select anything.
Now im stuck in this factory mode and im not able to enter into user mode.
Basically its bricked now and not able to use my phone.
Tried taking out battery and re inserting it ! but no luck. Phone is stuck in Factory mode.
i think i deleted the wrong files and now my phone won't go back the "HTC ONE" screen. I've done the process of a recovery and then allow the red triangle to come up, from there i know i should hold power + Up, and that should take me to a black screen with blue letters, and i should select something about "partition" but this black and blue screen, i remember seeing it as a thumbnail in a folder i deleted. I thought it was an ad photo saved onto my phone as spam (as the folder was named adSOMETHING) and so i deleted it and now, i feel i have have screwed myself over. I have no way of getting another phone right now. How can i get my laptop to read my phones connection and allow me to copy and paste the files needed to get it running again?
View 1 Replies View RelatedI'm an Android developer who is working with the upcoming Samsung P1000 tablet. I have to say that I haven't worked with Samsung Android devices so far. This is a developer/Engineer sample but I have real rough time to get a contact person at Samsung to help me solve this in a fast way, so I'm asking to the community :-)
The thing is I was trying my application while developing and every certain time I found the phone memory almost full (I think the tablet is saving all of its logs in a very verbose way in /data/logs where I haven't permission to access, and also it hasn't a micro sd inserted). The first time this happened I just did a factory reset from the OS itself.
The second time has been today and the phone was so full of data it didn't start at all. I was viewing the logs with adb logcat and Android was unable to start. He was trying and trying again (like in a loop) but only the Android logo was shown. I found the lack of memory to be the reason for this:
W/BatteryStats( 2949): Error writing battery statistics
W/BatteryStats( 2949): java.io.IOException: No space left on device
W/BatteryStats( 2949): at org.apache.harmony.luni.platform.OSFileSystem.writ eImpl(Native Method)
W/BatteryStats( 2949): at org.apache.harmony.luni.platform.OSFileSystem.writ e(OSFileSystem.java:129)
W/BatteryStats( 2949): at java.io.FileOutputStream.write(FileOutputStream.ja va:297)
W/BatteryStats( 2949): at java.io.FileOutputStream.write(FileOutputStream.ja va:253)
W/BatteryStats( 2949): at com.android.internal.os.BatteryStatsImpl.writeLock ed(BatteryStatsImpl.java:3080)
W/BatteryStats( 2949): at com.android.server.am.ActivityManagerService.<init >(ActivityManagerService.java:1430)
W/BatteryStats( 2949): at com.android.server.am.ActivityManagerService.<init >(ActivityManagerService.java:129)
W/BatteryStats( 2949): at com.android.server.am.ActivityManagerService$AThre ad.run(ActivityManagerService.java:1338)
The tablet can't write anything on the system, so it fails at booting and tries again, and again...
I did a factory reset via ADB with adb reboot recovery. Then the phone shows the recovery menu but no matter what option I choose (reboot, factory reset, update.zip or wipe cache) because the device doesn't seem to be doing anything but keeping the screen in black. If I turn off the device then it goes again to the recovery menu.
So I was stuck with the Android logo screen, and now I'm stuck in the recovery screen.
I thought flashing the phone would help so I turn it on in upload mode pressing the 2 volume buttons together (Power reset or unknown upload mode it says). This way the phone is recognized by Odin Multidownloader. I just grab a leaked firmware for this upcoming tablet from this Web The rar file only contains a SS_DL.dll and a OXA.tar. The tar contains some files: modem.bin, zImage, param.lfs, cache.rfs, dbdata.rfs and factory.rfs.
I've never used Odin nor flashed an android samsung phone so probably I'm doing something wrong. I tried to load the tar as the phone image it gives me an error, I also tried to load it as a single package but also failed.
So at this point I'd be most than grateful if anyone can share his ideas on this almost bricked tablet :-P
Edit: That "upload mode" was a fault of me, probably volume down was released while booting. I have the device in download mode but Odin keep me saying check image files, Any idea??
I woke today to find my Galaxy Nexus in a reboot loop. I went to bed last night and it was working fine but now it just constantly rebooting. Maybe some app auto-updated over night?
I have 4.0.2 ICL53F currently loaded, updated it about two months ago.I recently loaded CWM recovery.
My rooted Evo keeps hanging up after I try to reboot into recovery. When I rooted my Evo I had used a bat file from my desktop to get into recovery after original root. My question is will I have to run this file again from my desktop with my Evo connected to get into recovery mode again to flash fresh Rom. Will there be any issues with running this recovery file again. Or Am I missing a step to get into recovery. Power off hold volume down while power on volume scroll down to recovery press power button.
View 1 Replies View RelatedAs I remember the issue got started from my fault about wipping my battery state. my battery never charged to 100%.I tought I can solve this by wiping when it's fully charged(99%).so I charge my phone to 99% and wipped.but after that my charge percentage got wrong.for example it shows 50%,but it gets off bcoz of low battery.or I plug my charger when it's at 30%.it jumps to 90%rapidly.I have changed my rom.but no results.I tought maybe it's from relation of hardware(battery)and software(ROM) data.so I decide to try my idea.
My idea was:wipe and format all things at recovery.draining battery to 0%(by entering the downloading mode and remaining to it untill phone gets off)then pluging it to charger and let it fully charged.and then odin and installing a ROM.but I have wiped and formated all ghings.but when I plug the charger now a battery icon appears on the screen,but it doesn't get green as it is charging.
GT-I9000
i just buy my new galaxy ace plus and when i want to root it from recovery.. i cant reboot into recovery..how to reboot recovery on this phone?.. or maybe this ace+ doesnt have a stock recovery?
View 9 Replies View RelatedI rooted and installed this Atomod for s7500, [URL] ....
It was awesome. It was also running good. Not a single application crashed.
But when i rebooted my android, it won't start. It won't go past the Samsung logo. Nor is it entering into CM recovery mode nor into Download mode.
so i just find a new way to reboot to stock recovery on samsung galaxy ace plus GT-S7500 without flashing another custom recoveru like cwm or something like that
many people say that we cant access the stock recovery on galaxy ace plus because it have some bugs or something else.. now i found the way how to do that
just follow the simple guide how to do that :
1. reboot it using volume + and volume - ~> home button ~> power button
2. click and hold both volume button then the home button then the power button..
3. if the phone gets turned on so u need to keep hold that button until the recovery showed up (when it showed up and its get turned off again so u need to hold all the button again until it get rebooted to recovery)
4.if u get rebooted all time its not a big problem again .. all u need is just hold all that button until the phone gets turned on and release the power off button and hold it again until u boot it on recovery mode.. and done u booted up on recovery mode (im not responsible if ur phone gets bootloop or something else)
This afternoon, while scanning the forums. I had my Incredible charging off the AC adapter. and in airplane mode for shits and giggles. After doing some research on the ATK killers. I decided to uninstall mine and just allow the phone to manage itself. After the phone was finished with the uninstall I gave it a quick reboot just to allow the core apps to come back up. and upon doing so, I found myself in an endless reboot cycle. I would get the HTC " quietly brilliant " screen, followed by two verizon wireless screens and then loop back to the HTC screen. I let it loop about 10 times before pulling the battey to stop it.
It's rather odd. After pulling the battery and disconnecting it from the charger, I let it sit for a few minutes, replaced the battery and attempted the restart again. Once again I found myself in the same loop. After 5-6 loops i was finally brought to the OS and everything loaded as normal. Anyone have opinions on what may have caused this?
1. Uninstall of ATK
2. Rebooting while on charge
3. Airplane mode + charge + reset=boom
4. Because I touch myself at night
I've rooted 6 or so different android phones mainly using cf-autoroot, including an i9300, and never had any issues. But I have had a few issues rooting my 9503 using the cf-autoroot method (method #1 in this post). It aooeared to work, but SuperSU subsequently fell over, and Knox complained but after reading other posts I rectified that, but obviously not quite correctly:
After using cf-autoroot, SuperSU DID NOT appear in the apps list, but Google Play said it was installed but only presented the option to open it (not update or remove).
So I then tried flashing twrp (as per method #2 in this post) which all appeared to go successfully according to Odin. I was expecting to install superSU updater, as per step 3, but recovery mode appeared unchanged/stock so of course I couldnt flash anything as there was no option to do so. Yet there were no errors reported by Odin?
So I then got hold of the app file for SuperSU 1.93 and installed it (via Airdroid). It ran. It found knox. It removed it, and root was installed successfully (as verified by root checkers, titanium backup, droid wall and the like). So I concluded I had successfully rooted my 9305.But when I reboot SuperSU falls over again on boot up, and the version I added via Airdroid has disappeared, and of course there is no root mode.
But I can then restore root access after a reboot simply by following the same process, namley installing the supersu apk via Airdroid.And why is the later version of SuperSU disappearing on reboot?
My dinc just automatically rebooted and got stuck in the initial white droid incredible screen (before the green htc logo)....vibrate...black...white droid incredible screen. happened for first time two nights ago...finally got it out of this and wiped phone to factory. just today happened again. i was able to uninstal it in between the 5 minutes of working phone i had (kept going into reboot cycle....and as soon as i uninstalled it..this nonesense stopped!
View 1 Replies View RelatedI have a non-rooted EVO with all the latest updates and lately it will randomly go into a reboot loop. The only way I've been able to stop this loop is immediately put it in airplane mode, that is when it gets as far as the main screen. Usually it doesn't even get to the 4G animation before crashing again. Is there a fix for this? Or is this a hardware issue? I have not done a hard reset yet or anything.
View 7 Replies View Relatedmy fascinate is rooted and i attempted (foolishly) to replace the default device fonts. however, after following directions and "successfully" completing the steps, my phone rebooted and is now stuck on the samsung reboot screen. i've tried wiping all data, removing cache, removal of sd card, and rebooting and i'm still stuck on the samsung main reboot screen.is there anyway to fix this issue or at least restore my phone using terminal on a mac or command on windows? and if this is possible, would debugging have to be checked because i unchecked debugging after i rooted my phone.
View 1 Replies View RelatedI have a samsung galaxy tab 2 GTP3100. today it suddenly started to restart in every few minutes.
I tried to uninstall lastly installed app, but the device restarted every time I tried to do something with it. Then i tried to reset it from the settings>>backup & Restore. but no gain. the device was as it was before.
then i tried with system recovery mode. it opened with an error message
did not match sized 'system/csc/common/system/csc/default_workplace.xml' (No data found)
despite tht I performed "wipe data/factory reset" and "wipe cache partition"
it said to have completed the above operation, no further error message. I rebooted the system... but no gain.. same as before.. not a single change. and the "restarting problem" was ther.
I recently bought a new spacious SD card for my new phone and decided to move all my files there. I was having trouble with the apps so I found out FolderMount could be useful. I rooted my device without any problems and checked it too before using FolderMount. However when I opened FolderMount it said it needed to patch/repair something so I hit OK. After that it said You can reboot your device now. so I did. After that my device starts and stands still after the samsung logo is shown. I wouldn't call it freeze because I can see it's still working (the background of the samsung logo gets a blue gradient every second) but I'm beginning to worry about it since it has been in that state for like more than an hour. Rebooting wont work.
View 4 Replies View RelatedI rooted my phone Friday and it is now Tuesday(Got my phone in August). I installed some apps that are rooted only. Tethering, Overclock Widget, Titanium Backup, ROM manager.When I tried to install a new ROM I was getting download errors. I saw something about ADW.Launcher so I downloaded that and got a theme for it. Today when I reinstalled the Cyanogen 6.0.0. Stable release and rebooted my phone I would get to the Motorola Symbol. After that I got to my custom boot image(Dancing Droids). The image got half way doing its animation it restarted from the begging this continued until I took out the battery. Went into recovery mod and the Cyanogen boot image appeared and did the same as my Dancing Droid but completed 1 1/2 circles with the blue flame. When I got home I plugged in my phone flashed a 2.2 FRG22D.sbf file. I then used RSD lite and connected my phone. Had some trouble flashing the file but eventually got it. When I went back to the boot loader screen and cleared my cache/data(thought it would help) I restarted my phone. Watched and Motorola symbol appear and posted this 1 hour later. Can someone please tell me what I did wrong or what to do?
View 13 Replies View RelatedI was messing with my Samsung Galaxy S the other day and came across the Pattern Lock. I thought it was pretty cool so I decided to use it. So I came up with a pattern immediately and, without any thought, I accepted the design I made (It was a complicated one) and forgot what it was right after. I know at some point after failing to enter the correct pattern you get to a "Username" and "Password" box for your Gmail and/or Google account, but, Since my device runs strictly off WiFi and WiFi is turned off I can't sign in. I also tried force resetting my device but it doesn't work like all the videos on YouTube show.
Extra Info
Name of Device: Samsung Galaxy S Media Player 3.6"
Order from Amazon
Internal Memory: 8GB
Micro SD Card: 16GB (Kingston)
Model: N/A
1. During the Google Login screen, I can't access my notification bar, therefore, I can't turn WiFi or anything else on.
2. I tried the different variations of: Turning off device. Holding Volume up+Home Button+Power Button. The "Samsung" logo pops up, vibrates once, and the screen turns pitch black all while still holding buttons and nothing just happens to happen after. When I release the buttons, the device boots up normally but I end up back at the Google login screen.
3. I tried taking the battery out and putting it back, doesn't really affect anything.
4. I tried plugging my device into my computer, but since I'm trapped at the Google lock screen, I don't have the option of connecting "Mass Storage Device" to my computer.
5. I tried adb shell (or whatever the command is) into Command Prompt and it doesn't detect my device. I have all the drivers installed for the device but because I don't have the option of tapping "Connect Mass Storage to Computer" it doesn't sync in with my computer. It just charges my device as if it were a wall charger.
My last resort option was coming to Android Central. Otherwise I'll just go to Radioshack or various other stores and see what they can do if anything at all at least.
I have an AT&T Galaxy S4 I337 that I have been running Cyanogenmod on for quite a while now. Well, after getting bored and wanting to revert to the original firmware, I went through the process of a factory reset to stock through Odin. Everything went smoothly, all that's left is to update to 4.4.2 Kitkat and to root my phone once again. I went into settings and began the OTA update thinking it would install 4.4.2. After about 20 minutes of updating and downloading, my phone finally finished rebooting, but when I checked to see what version of android I was running, it was still 4.2.2. Kies also says that I'm running the latest firmware. Why won't my phone or Kies pick up the new Kitkat update? Does it have something to do with the fact that I flashed a custom ROM before?
View 1 Replies View RelatedI deleted a file(logo) and my phone galaxy music duos wouldn't reboot.
View 2 Replies View RelatedI've been rooted for quite some time to it. Not exactly an old pro, but I know my way around at this point.At any rate, I decided to give the BatteryLeft widget a try today since I went to Fab's xTheme and it didn't have a battery percentage in the notification bar. The dev recommends that you let your phone completely discharge a few times so that it can accurately predict the remaining percentage and the time until the battery dies.So I let the battery completely discharge and I connected it to my home wall charger to begin recharging. The problem I have been having is that my phone will not stay powered off and continually tries to boot up. I tried charging via car charger, USB and in the media dock and I had the same result.
The problem is that the phone won't charge long enough to stay powered on and continue to charge. The process of rebooting seems to prevent the phone from charging appropriately and uses up the small bit of the charge the battery gets for the 2-3 seconds before rebooting.I tried rebooting into CWR and letting it sit to gather enough charge to stay up, but that doesn't seem to have worked either.I'm at a loss for what to do. I can't get the phone to stay on to do anything, I can't get it to stay off to charge.
I have JT's Voodo (v.2 Ext 4 installed) on my samsung fascinate, and I tried deactivating it using the voodoo toggle app so that I could flash his super clean rom. Things appeared to go ok, but now i'm stuck on the reboot screen (have the droid peeing on apple) for an hour now. I know JT said wait it out, but I havent read about anybody having it in reboot for over an hour.I dont know what to do?
View 7 Replies View Related