Hi All, Xoom MZ601, EOS4 ver 132, CWM 4.0.0.4. The tab often needs soft boot (vol+ and power) to start. Can unlock tab, but lots of FC's clock, google etc. Nothing is working properly. Can't open google play and won't register google account.
Have tried CWM factory reset, to reload new rom and gapps......nothing changed, apps and problems remained the same
Have tried fastboot lock oem/unlock oem; tried to flash boot.img and different recovery .......same result.
have tried RDS lite and SBF file.......like all the other options I have tried, it seemed to work.....but once I booted back into the tab...nothing changed.
It has AVG that seems to be running, I thought it might be a virus?
Nothing I do seems to change the data on the tab or the CWM or the ROM, I was wondering if I should either try to use nvflash (cant find any info about how to use this) or open up the tab and disconnect the battery to try and reset the tab?
By the way I am a noob and I am lost about how to fix my xoom.
Just something else that might help..i did getvar and the tab is listed as a mz602 and not as a mz601, could this be the cause of the problems?
thanks for any advise.
Related
My friend has a Captivate. He lost all his google apps, android market, gmail, etc. He flashed gapps.zip from his recovery and now his phone is not working right. When he flashed a new rom to his phone, and it brought up the welcome screen it shows it for about 2 seconds and then reboots. He is also almost unable to access the recovery becuase of this, but even when he finally was able to access it and wipe everything, dalvik, cache, data/system, it still has issues. Nothing is fixing the issues from the gapps.zip. He was wondering if there is a way to wipe his entire phone from a update.zip file. Any help would be appreciated. Thank you in advance.
Please note that even when he wipes everything in recovery and flashes a new ROM, it still reboot on the welcome screen and he is unable to resolve this issue.
Ok, so he has now wiped all cache and system files, now instead of showing teh galaxy S logo with the cyanogen logo underneath, it shows just the AT&T screen, but it will not go any furhter, it just sits there. He says that because he is now unable toget into android he cannot access the recovery and the volume up/down is not responding. Is his phone Bricked?
Have you used Odin 1-click to revert back to stock?
had my friend use the Odin 1 click and he said it still did not work. He cannot get the volume up/down trick to work, when before all this it worked just fine. I am going to guess that the only thing he could try is the jig method. He swaers that Odin3 is not doing anything
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
AusomBabs said:
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
Click to expand...
Click to collapse
Good Job if You Could Explain For Latest Problem Solved. I Think this is the problem from cwm or maybe the latest rom of cwm snapshot, need to investigate for problem occured. before this update we never have this problem. "When Reset Factory Default within Setting than it will always bootlop". My a701 have this problem too. looks like @Flupkes Problem too, the different is i Reset it From Snapshot M7 this my old thread and could make the adb working because the usb slot problem.
Alright, so yesterday I tried to root my tablet (Samsung Galaxy Tab 3 10.1 Wifi) yesterday by installing TWRP and then loading the Superuser zip found in their link in the play store. It worked fine--I had root access and all was going fairly well. I then tried to make a small tweak to the build.prop file by changing ro.build.version.codename from REL to L.
When I rebooted to apply that change, I could not start up, so I did a factory reset (not a big deal, no essential files on there). It then booted fine, but when I reinstalled/updated all my apps, the Google services were crashing like mad. So I reverted the build.prop file back to REL and again it would reboot, so I did another factory reset and all was good; the Google apps were fine.
Well I was still rooted and I wanted to take advantage of all that time I spent doing it, so I downloaded the bootanimation zip found on this thread and replaced my bootanimation.zip that was already on there. I restarted to see the animation, and this is when the real nightmare started happening. I could not boot now at all.
I did another factory reset, and still it wouldn't boot. I then used TWRP to do a full reset, and still nothing. I did an advanced reset and somehow managed to delete the operating system files (I have no idea how), causing TWRP to say that no operating system was installed. I still couldn't boot, of course.
Finally, I decided I had had enough of this rooting ****. I searched all over the internet looking for a North American version of my stock ROM, and finally found one posted on this forum post. I wouldn't normally trust any random file, but I was getting desperate here. I used Odin to flash that ROM, and there were no errors. Now when I go into recovery, it gives me stock and not TWRP, so I know that was probably successful.
However, I still cannot boot. I get stuck on the screen that says Samsung Galaxy Tab 3, which sometimes goes away and then comes back. I can't send it in for warranty, because it still says "custom" in the recovery mode. How can I fix this? any ideas?
I really want my tablet back :crying:
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.
Hey guys hope someone can point me to the right direction or knows this problem:
Galaxy Tab 10.1 Wifi (P5110).
Device will only boot recovery no matter what. (both with stock or custom recovery AND stock or custom rom installed - tried all combinations already)
Stock rom has been installed with odin and pit-repartition has also been tried.
When I turn on the tablet it boots straight to recovery. On stock recovery it says something about update, then "no command" and when I then choose reboot system, it says error and powers the device off.
Please help.
nobody an idea?
I had this kind of behaviour on another device before - dont exactly remember if also was samsung - but the solution was to clear out a stuck OTA update which was stored in a special partition which would normally not get wiped of flashed over. (by reformating or writing it full with /dev/zero)
Thinking back I dont think it was a samsung device though - but the "error picture" is the same.
But in this case I'm unsure where ota updates would get stored other than cache partition. Already tried clearing out some partitions on this thing - since its a wifi only model - can I clear EFS or use "reformat all" (dunno how exactly that option is called in odin) without totally bricking it? (never had to do this but since I'm out of ideas... )
Please anyone.. =)
zroice said:
Hey guys hope someone can point me to the right direction or knows this problem:
Galaxy Tab 10.1 Wifi (P5110).
Device will only boot recovery no matter what. (both with stock or custom recovery AND stock or custom rom installed - tried all combinations already)
Stock rom has been installed with odin and pit-repartition has also been tried.
When I turn on the tablet it boots straight to recovery. On stock recovery it says something about update, then "no command" and when I then choose reboot system, it says error and powers the device off.
Please help.
Click to expand...
Click to collapse
Try rebooting while power is plugged in.
LāvLab / HostileSlothRecords
LavLab said:
Try rebooting while power is plugged in.
LāvLab / HostileSlothRecords
Click to expand...
Click to collapse
definitely tried that. But no longer have the device, so cant try it out again unfortunately. But thanks for your reply!