Hello Forum,
I recently purchased my Gtablet and the first week with T.n.T rom was amazing, but one day I came home and a majority of my apps started force closing. I Nvflashed to return gtablet to stock after noticing the gtablet would not boot. After flashing it back to stock rom the force closures continued to happen, soon after I did the security-data wipe. This did not help. The tablet will not boot. I have tried many different recommendations on this site, but note: the tablet will go into APK mode, but will not go into recovery mode with power + Plus volume. I have been reading through the threads for 3 days and spent several hours trying to fix this problem. I have read of one other person with my problem, but he didn't seem to solve it either.
Can some one help?
Solved
Ok This is how I solved the issue...
First wipe all apps from your device besides stock apps (this can be a lengthy process).
2nd, Data wipe.
3rd download all new NVFLASH box files and ensure they are extracted correctly.
4th NVflash your tablet.
5th up date tablet.
My tablet was soft bricked, no boot except for nvflash, no vol + plus recovery option, and mass force closures... Now everything is working.
The problem you had is actually a lot more common than you might think. It just takes quite a while before some folks figure out that they're in APX mode.
Great job.
Had the same thing happen to me. NVFlashed back to stock, installed update and it rebooted fine. Installed 3558 update ota and it rebooted but stayed in APX mode after reboot. How do you keep it from staying in APX mode after reboot?
Install clockworkmod through nvflash, reboot into recovery, repartition 2048 and 0. Then nvflash again. This should correct all issues and give you a good baseline. There is a chance that it will not work. I'm researching that for a number of other users.
Related
My father brought home the G Tablet yesterday after getting it at Office Depot because it was on sale and was the last one left.
I didn't want to open it because I've had my eye on the ADAM tablet and was going to wait for it to come out and compare the two. However, he convinced me to mod the G Tablet to run TNT 2.0.
It worked fine for a while today. I got it up and running, fixed the Market, and was able to download apps and games. Then, I woke it out of sleep mode and the Market started coming up with errors. I figured that I'd just need to turn it off and boot it back up again.
The problem that I'm having is that the thing doesn't want to boot back up. It goes to the ViewSonic screen, then to the G Tablet logo, pauses for a second, then goes back to the ViewSonic screen.
I attempted to do a recovery and see if I could reinstall TNT; it refused. It will see that there is a kernel, but when it goes to install it, I get an exclamation point flashed on screen and then it goes back to the ViewSonic screen (I'm getting really sick of looking at those birds).
Is there any way to fix this, or did I have the shoddy luck to have one with bad hardware?
I didn't use Clockwork to install the firmware. I realize that that might have not been the best choice now.
I haven't had that, probably I'm still stock, but there are threads about getting out of the problem. Use forum search, in this forum. Search titles only, for 'loop'.
Jim
Thanks.
I tried flashing it again with clockwork installed to no avail. I also tried to set it back to the manufacture default, but encountered the same loop.
Looks like it's going back to Office Depot!
Kaizykat said:
Thanks.
I tried flashing it again with clockwork installed to no avail. I also tried to set it back to the manufacture default, but encountered the same loop.
Looks like it's going back to Office Depot!
Click to expand...
Click to collapse
If you have clockwork installed then go to advanced and partition the sdcard. I use 2gb, and 0 for swap. Do a wipe data/factory reset, and a wipe cache partition from clockwork also. Problem will likely go away after that. Partitioning the sdcard will remove any data but that's the way it goes sometimes.
Then I would reflash from clockwork something like TnTLite 2.4, or the VegaN Beta 3 rom. You can do that from clockwork also.
Sprdtyf350 said:
If you have clockwork installed then go to advanced and partition the sdcard. I use 2gb, and 0 for swap. Do a wipe data/factory reset, and a wipe cache partition from clockwork also. Problem will likely go away after that. Partitioning the sdcard will remove any data but that's the way it goes sometimes.
Then I would reflash from clockwork something like TnTLite 2.4, or the VegaN Beta 3 rom. You can do that from clockwork also.
Click to expand...
Click to collapse
x2 on the sd re-partition, it will most likely fix the issue. Many users have reported similar issues.
Here's the problem -- this is very common and exchanging it probably won't help as you might eventually have the problem again. You already have cm on the device, so you are 90% there already.
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
m_hawkmoon said:
Hello everyone,
I searched the forums for awhile but could not find a satifying answer for my question. So i am hoping you guys will have an answer for me.
First of all i would like to point out that i am not looking for an answer for how to unbrick the phone. There are several guides and hopefully when i get home i will be able to fix the problem. *Fingers crossed*
I did not have my Galaxy S for long. After getting it and installing KIES and updating my firmware the battery life what terrible so I rooted the phone and then installed Gingerbread 2.3.6 JVU. it worked like a charm.
Yesterday when I was playing with the CWM application, I decided that i was going to back up the phone and backed it up using the application. This morning one of my programs was acting weird and I decided to restore the backup I have done yesterday.
Upon going into applications and CWM, I chose the restore option and started the process. Everything was going smoothly, the phone was plugged in to the charger as well.
When the phone rebooted after the initial process I am stuck at logo screen. i can go into download mode (That is why I am hoping that I will be able to unbrick it) however that is as far as the phone goes. When I try to go into CWM Recovery mode, I am once again welcomed by the phone getting stuck at logo screen.
Does anyone have any idea as to why this might have happened? To avoid future problems is there any extra steps I should have taken before using the CWM restore function?
Thanks for the help.
Click to expand...
Click to collapse
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Theonew said:
Maybe your backup was corrupted somehow. You could have tried wiping the dalvik cache after restoring your backup (before rebooting), but its too late now. Since you can get into download mode, you can easily fix the problem (your device is just soft bricked - nothing to worry too much about).
Click to expand...
Click to collapse
The phone rebooted automatically. Did not give me the chance to do anything beforehand.
As you said the phone was soft bricked so when i got home that day i just fixed it. No problem. However I am really really into getting to find out how a 1 day old back up can get corrupted.
so today i went to unlock and flash CM 10.1 on my tablet.
unlocking went smoothly
installing clockwork recovery went fine
installing cm10.1 and gapps went fine
once i booted into cm successfully, i checked the internal storage to see if it was clear. it wasn't, so i went to settings, backup and reset, and done a factory reset. now i'm stuck on this one screen and i dont know what it is.
i've held the power button and volume down until the tablet restarts and that results in the same thing.
i've tried power and volume up. that seems to start the tablet but the screen stays blank. i connected it to the computer and my computer installed an APX or APTX or something like that driver.
i've tried holding power, volume up and down, and that does the same as the power and volume up.
i'm very new to installing custom recoveries and roms. can anyone give me an idea on whats happened
Once you have a custom recovery installed you should NEVER wipe from the system settings or the bootloader menu. You wipe from your recovery.
If you do that, the bootloader seems to write a command to the misc partition to reboot into recovery.
And that is the loop you seem to be stuck in.
You can try _that's method to clear the misc partition from here: http://forum.xda-developers.com/showthread.php?t=2528313
Read the whole thread, salvation may be found in post 7.
If that does not work, you could try this:
http://forum.xda-developers.com/showthread.php?t=2399698
buster99's method may be another way to enable you to boot into the bootloader and flash a working recovery.
Good luck!
Thanks for the tip. I'll remember to do that next time. As of now it is fixed. I found a post on the cyanogen forum of someone who done the same thing. And he said he had to wait a painful 6+ hours of that screen I posted. Lucky for me it was only a ~45 minute wait. So all is good. Cyanogen is running. Recovery is working. All the stress is gone.
Hey everyone, I'm using a GT-P5100 (3G + Wifi) O2 UK rooted tablet and for the last month it has been broken. It started rebooting itself randomly every now and then, and then suddenly it wouldn't even boot up for 15 seconds before it would restart itself again.
I am able to get into safe mode and I can get into the boot options, but when I factory reset it does nothing, I've tried from the boot menu, from safe-mode options and even from the dial up code.
I tried to connect my tablet to my PC as a media device and format it but that didn't work either; I can't connect it as a disk then format it that way because they took out 'mass storage mode' on this firmware.
I then tried to flash a stock ROM in Odin but every time I tried it would fail until I used Odin.v1.3, but guess what, it rebooted itself and my entire tablet is still exactly the same.
(the option was on AP ram in v1.3 not AP nand I don't know if that makes a difference.)
If anyone can point me in the right direction I would appreciate it so much. I have been trying for weeks to fix this and I just don't know what to do anymore, I tried on another forum but nobody answered me.
Everyone else gets replies and I get zilch; amazing. I don't know what it is that is preventing my tablet from wiping itself but it refuses to clear the current data no matter what way I try (ROM, factory reset, computer format). If someone could just tell me what that is and what I have to do about it that would be grand.
You mention "rooted " but you don't mention what current rom or past roms that you may have flashed, you could have some sort of rom cluster [email protected]$k going on in your tab but NO one else will ever be able to help because of lack of INFO or history.
Pp.
I standard rooted it from Odin. This is my first ROM I am trying to flash. I just need to know what would prevent a tablet from rebooting itself properly. Factory reset, format and flash is not working so I must assume that rebooting is the issue here.
If you are running stock rooted rom and having issues like this the only way out is reflashing the stock firmware complete (not just a rom) and see if that fixes it before you try any other roms.
If you can get into download mode thats the fix.
Pp.
To flash it completely do I need more than an MD5 file? (I also have the partition file for my model). Another question, if the tablet is having issues with the reboot after a flash, will updating from a microSD with a zip help? Thanks for the advice.
Hi! So, my father's old Samsung Galaxy Tab 2 10.1 P5110 (bought 5 years ago) has gotten into a bootloop. It's an odd case. Basically, it's like the device is completely read-only.
To describe the symptoms:
It boots into the OS, but after 30 seconds or so it suddenly restarts. The device cannot be turned off (it just reboots and reboots and reboots...), so it empties the battery if left unplugged.
I can enter download mode and recovery mode, where the device is stable.
The device is not rooted.
I tried to flash it with TWRP recovery (it worked on my mother's tablet; exact same model, but no problem like this), but the recovery mode is always unchanged. I've flashed with Odin 1.8*, Odin 3.0*, and latest Heimdall; it always completes, but nothing changes. I've learned about having to boot to recovery after flashing due to a script replacing custom recovery, but even when I go directly to recovery mode, it's the same old stock recovery.
I decided to try another approach, by uninstalling apps during those short 30 second intervals of functioning OS; I got to uninstall one app (AVG anti-virus software), but after the reboot, the app was installed again.
I tried to go into recovery mode to do "wipe data/factory reset" and "wipe cache partition", but even that did nothing! Everything is where it was.
I can use ADB in recovery mode, so I tried to see if I could do some damage there, but the tablet is unrooted, and no rooting works either. (Tried rooting with Odin and "apply update from external storage" in stock recovery.) Couldn't find a writable directory to upload a su executable into either.
Just now I finished a 90 minute flashing of some Chilean stock firmware -- although I'm Swedish -- to see if that made things "rewritable", but guess what? All the old apps and files and settings were still there, in Swedish.
At this point I'm starting to suspect that I could hit it with a sledgehammer and it would just return to normal after a minute.
My father is not poor (just a bit cheap!), so buying a new tablet isn't a big deal, but I'm ostensibly a computer engineer...ing student, so it feels like a surrender to leave it unsolved. What might be the problem? Can memory in these devices become read-only due to some hardware fault?
Risky suggestions are welcome. If it's bricked, that's no problem.
EDIT: Whoops! My father ordered a new tablet; I was still going to experiment on the old one, maybe get it working again, but it seems that he went and tried the sledgehammer mode on it. But what happened is still an open question.