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!
Related
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
corrosivefrost said:
So I had a problem where I had issues getting a ROM onto my phone after entirely formatting it.
Some kind members helped me to get the phone running again and then getting TWRP 2.6.3.1 on it with the 4.1.2 build.
This was flashed to the phone using Odin after using E-Z Unlock 1.2 to unlock the bootloader and install TWRP 2.6.0.0.
I saw some random issues when I would reboot or power off and on with it locking on the Samsung Galaxy S III logo... but the phone rebooted eventually and I was able to continue use.
Fast forward to today -- for the first time in awhile, my battery fully discharged. When I got home, I plugged in and tried to power on my phone. Locked at the Samsung Galaxy S III logo... EVERY. TIME.
So I go into recovery... I find that the first thing that greets me is a message asking me for a password. This is odd, since I never put a password on anything... I try to mount the system/cache/external partitions. I try to factory reset to try a different rom. I'm told it works but there's a failure message because of E: cannot decrypt data. I try to flash a different rom anyway. It says it was successful. I flash the gapps, more success messages. I try to reboot and again I'm locked at the Samsung Galaxy S III logo.
Random side note -- sometimes my Samsung Galaxy S III logo has a blue android cat of some sort on it... not sure where that came from (one of the CMR flashes when I was trying to fix the phone, methinks).
It's so strange -- because I was obviously able to load a custom ROM with the current bootloader and recovery -- and now after my phone's battery drained, I'm back to being dead in the water... I really need to get to the bottom of having my phone boot into a ROM reliably.
Previous ROM was Gummy Nightly 01-06-14.
New flashed ROM is CyanFox 2.0.2.
Please help. I need my phone up and working as soon as possible here, I'm expecting important calls in the morning, so this is horrible timing.
Click to expand...
Click to collapse
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
buhohitr said:
At this point I would take the phone back to factory stock, are you able to boot into Odin mode?
Click to expand...
Click to collapse
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
corrosivefrost said:
Yeah -- I can boot everywhere, pretty much.
I ended up formatting everything... I tried CyanFox again, but after install, it was throwing errors all over the place (not sure why).
I then formatted everything again and loaded up Gummy... it seems to be working relatively well.
I'm not sure what caused TWRP to think it was encrypted, but I'm guessing that had something to do with the issue?
Is there anything I can do to try to prevent this type of issue from happening in the future?
Click to expand...
Click to collapse
I know for a fact that there has been issues with the flashing of 4.4 and encryption. The best bet is to turn encryption on then off again. Now you said you never encrypted it but the Turn it on then off again approch might work here. I also know for a while TWRP had issues flashing 4.4 so it might be worth it to run CWM.
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 all, I recently got a second hand Samsung galaxy S4 (GT-I9505) as a gift from a friend. I realized it had a problem that every time I went on certain applications especially settings I'd get a warning saying 'Unfortunately,'said app(settings)' has stopped.' I decided to factory reset my phone using the 'volume up, home button and power key' and I also wiped cache and even rebooted it, yet the problem still persists. Now when I try to turn on my phone and I get onto the set-up page when I try to press next it says 'Unfortunately settings has stopped' and takes me back to the start which I believe is called a boot-loop, I'm not sure though. I'm not to sure how my friend managed to get the phone to this state before he gave it to me and I think it may have either been that he downloaded a faulty application or that he tried to update the phone and then this problem occurred. Now I'm not too experienced when it comes to Custom Roms and things but I heard there is a solution which requires you to press the volume down and power key in order to download a Custom Rom but I'm not sure how I'll download one without the help of my phone(which remains in the boot-loop). And I'm also 100% sure that no Roms have been downloaded on the phone ever.
Any help is appreciated. Thanks in advance
kwesi101 said:
Hi all, I recently got a second hand Samsung galaxy S4 (GT-I9505) as a gift from a friend. I realized it had a problem that every time I went on certain applications especially settings I'd get a warning saying 'Unfortunately,'said app(settings)' has stopped.' I decided to factory reset my phone using the 'volume up, home button and power key' and I also wiped cache and even rebooted it, yet the problem still persists. Now when I try to turn on my phone and I get onto the set-up page when I try to press next it says 'Unfortunately settings has stopped' and takes me back to the start which I believe is called a boot-loop, I'm not sure though. I'm not to sure how my friend managed to get the phone to this state before he gave it to me and I think it may have either been that he downloaded a faulty application or that he tried to update the phone and then this problem occurred. Now I'm not too experienced when it comes to Custom Roms and things but I heard there is a solution which requires you to press the volume down and power key in order to download a Custom Rom but I'm not sure how I'll download one without the help of my phone(which remains in the boot-loop). And I'm also 100% sure that no Roms have been downloaded on the phone ever.
Any help is appreciated. Thanks in advance
Click to expand...
Click to collapse
serach for flashing stock s4 ROMs via odin ....that should help for sure ....you can flash a factory ROM with this method and think your problem will be solved
Download factory ROM and download custom recovery(like philz touch or twrp), flash custom recovery via Odin...if its flashed successfully, goto recovery mode ( by pressimg buttons..sorry I don't know much about Samsung but I know to flash ROMs) if u entered recovery mode first wipe cache, wipe dalvik cache, wipe to install new ROM, then goto the option "install from SD" select the factory ROM package and wait until its finished fully....after flashing reboot your phone...and then ur phone is fully fixed..hope u will get ur problem solved soon....(thanx me if its helped am new to xda and I need some fame for helping more no. Of PPL and solving their problems) thank you....
devwaseem said:
Download factory ROM and download custom recovery(like philz touch or twrp), flash custom recovery via Odin...if its flashed successfully, goto recovery mode ( by pressimg buttons..sorry I don't know much about Samsung but I know to flash ROMs) if u entered recovery mode first wipe cache, wipe dalvik cache, wipe to install new ROM, then goto the option "install from SD" select the factory ROM package and wait until its finished fully....after flashing reboot your phone...and then ur phone is fully fixed..hope u will get ur problem solved soon....(thanx me if its helped am new to xda and I need some fame for helping more no. Of PPL and solving their problems) thank you....
Click to expand...
Click to collapse
I think downloading and flashing the rom from a computer would be easier. Just download the correct files from sammobile and flash them via Odin. Also you will need Samsung drivers, you can get them by installing kies or if you search here in the forums im pretty sure you'll find them too.
Sent from my GT-I9505G using XDA Free mobile app
Hi All.
So I'm not new to rooting / ROMs (nor am I an expert, as you'll see), but somehow have totally screwed up my tab. I've now honestly done so many things to try to recover, that I couldn't begin to summarize how I got into this mess, but I'll try.
Model is GT-P5113. Most recent working ROM was SlimLP 5.1
I went to flash CM12.1 (using CWM) and God only knows what happened. After it flashed, I tried to reboot and it would only go to CWM recovery. If I chose to reboot device, it would only shutdown, not reboot (This was actually one of the issues I was having with SlimLP as well, so I don't think the flashing had anything to do with that???)
After many attempts at reinstalling CM and SlimLP (I used the same Zip that had worked previously with SlimLP, and the flashing would say installed) it would still only boot to recovery. I finally said, screw it, I'll just start completely over
So attempted to go back to stock 4.2.2 using Odin3.09. Got the stock ROM off SamMobile site. ODIN seemed to flash,but again when it would go to reboot, it would just power down and a charging battery would show up. So I would unplug from the computer, push power button. When it powered up, it would say Installing system update, then after the status bar moved a bit, it would say Error and shut down. When I restart, it very briefly says installing system update, then show the dead android with a red triangle and No Command, and it would boot to the stock android system recovery (I assume CWM was taken off in the process). In yellow, under the stock recovery it says
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : XAR
Successfully applied multi-CSC.
I've tried installing the other ROMs again, this time with TWRP, but only for it to boot to recovery after the Samsung Tab 10. 1 logo.
I have no clue where to go from here. No clue if I'm still rooted (doubt it). At this point I don't care. I just want a functioning tab. I've spent hours searching, but nothing works. I'm open to any / all ideas.
Thanks
Aw, show me a little love, bros. Someone' gotta know something. I'm not above begging / pleading.
I can give more info, less info, post somewere else. Just let me know,and help me resuscitate my tab.
thanks again!
Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying: