Hi
I have bought a Galaxy Tab 2 10.1" to my wife for 2 months ago.
But The problem is, that it hangs alot and it freezes, i have tried to "factory reset" it and send it to "repair" but when finally i got it back from repair i was told, that they couldn't find any problem, and they are not responsible for the 3part apps.
And now i still got those problem?
The Tablet is not rooted its still like when i bought it.
Please help!
To those who suffer under same problems.
Solution found read below:
Is to delete cache evry 3-4 days depending on how much you use it.
----------------------
By izzo | From mobile
Have you tried flashing another copy of the stock rom and factory resetting after flashing it? Are you on the latest update (4.0.4 I believe) Lasly, if those don't work, you may want to flash Cyanogenmod 9.1 or Cyanogenmod 10 Jelly Bean (which is fast beyond belief)
Thanks, but have found the solution.
I can't root the tablet because it's not mine..
The solution is in post 2
----------------------
By izzo | From mobile
Hi guys,
I just bought a new Coby Kyros MID8127 tablet (A8, Android 2.3) for my friend.
Now, I want to flash a custom ROM with JB on it, but I just did not find any ROM, CWM or tutorial for that here at XDA (or elsewhere).
Is it possible, that there is no custom ROM for that tablet to have?
Thank you in advance.
Greetings,
sYCO
I have the same tablet and I bought a custom ROM from the people at KTZ, however, I could not install this ROM successfully, in order to install it I had to take the tablet to factory reset state and then delete a bunch of system applications to make room for the new ROM because the ROM does not allow you to install it from a formatted system partition (it's more like an upgrade). But when I finally installed the ROM it wuold not boot a second time; what that means is that, after installation the ROM boots normally but if I reboot it gets caught in a loop where I just see a blue disk spinning and it doesn't do anything else and the only way to get it out of that loop is to connect the USB cable and boot to recovery via adb and restore the backup that i did before flashing the new ROM. I tried to get help from the guy who makes these ROMs but he wasn't very helpful. I followed all his instructions and always got the same result.
I managed to install manually most of the components of this ROM through a long process of trial and error and left out the components that make the tablet misbehave and now I have a hybrid on my tablet which works pretty well with the exception of the wifi. The wifi works but at times is painfully slow.
I tried other ROMs from Android Tablet forums (check here). There is an ICS Rom there (or more than one, I don't remember) and also a JB ROM for the 8127 but I could not make them work on my tablet. The ICS ROM installed fine and runs very fast but it keeps freezing so I uninstalled. The Jelly Bean did not install properly and it was very hard to get the tablet to a working state after it bricked.
That was a while ago and I haven't checked lately if there is something else out there.
leunam12 said:
I have the same tablet and I bought a custom ROM from the people at KTZ, however, I could not install this ROM successfully, in order to install it I had to take the tablet to factory reset state and then delete a bunch of system applications to make room for the new ROM because the ROM does not allow you to install it from a formatted system partition (it's more like an upgrade). But when I finally installed the ROM it wuold not boot a second time; what that means is that, after installation the ROM boots normally but if I reboot it gets caught in a loop where I just see a blue disk spinning and it doesn't do anything else and the only way to get it out of that loop is to connect the USB cable and boot to recovery via adb and restore the backup that i did before flashing the new ROM. I tried to get help from the guy who makes these ROMs but he wasn't very helpful. I followed all his instructions and always got the same result.
I managed to install manually most of the components of this ROM through a long process of trial and error and left out the components that make the tablet misbehave and now I have a hybrid on my tablet which works pretty well with the exception of the wifi. The wifi works but at times is painfully slow.
I tried other ROMs from Android Tablet forums (check here). There is an ICS Rom there (or more than one, I don't remember) and also a JB ROM for the 8127 but I could not make them work on my tablet. The ICS ROM installed fine and runs very fast but it keeps freezing so I uninstalled. The Jelly Bean did not install properly and it was very hard to get the tablet to a working state after it bricked.
That was a while ago and I haven't checked lately if there is something else out there.
Click to expand...
Click to collapse
Hey Guys,
Just found this link. Maybe you can try it out and tell me if it works for you.
http://www.androidtablets.net/forum...lly-bean-stock-lite-mid8127-rooted-gapps.html
jpapadami said:
Hey Guys,
Just found this link. Maybe you can try it out and tell me if it works for you.
http://www.androidtablets.net/forum...lly-bean-stock-lite-mid8127-rooted-gapps.html
Click to expand...
Click to collapse
Sorry, I gave that tablet back and cannot test it anymore. I rather recommend to buy an Ainol Novo 7 Crystal. It is cheaper, better and ****ing fast with a nice custom ROM support like CM 10, CM 10.1, Paranoid 3.0, Crystal-Fuse, ...
Btw, KTZ sucks totally.
First of all, I'm a complete noob. I just joined the xda forum today after a year of following developments especially for custom roms and apps.
I have a pre-owned rooted Samsung Galaxy Note 2 (Android v4.1.1) which the "About Device" indicates is model n7105. I really wanted to "upgrade" its capabilities and features to a level close to Note 3 and/or KitKat goodness. So after reading a lot about how to flash custom ROMS, I tried Ditto Note 3 v5 (http://forum.xda-developers.com/show....php?t=2589715). Everything went well during the installation but after reboot it got stuck in the logo screen. After waiting for 10 minutes I flashed it AGAIN but with the same result. Finally after waiting for 20 minutes, I restored my phone to its backup. Now my phone can no longer detect my SIM card and my IMEI is null/unknown, even after factory reset. I made a big mistake! Then I remembered that that the original owner mentioned it's a converted E250 KOREAN version but I'm no longer able to contact her. This phone has been rooted and tweaked many times for over a year now, and having it serviced is no longer an option.
I definitely still want to flash DN3 (or any custom ROM compatible with E250) but I also need how to revert E250 to N7105 and fix my "Insert SIM card" problem. So where do I go from here? Any help/comments/suggestions on my specific case would be greatly appreciated! I am willing to learn whatever it takes to get this done and experiment.
Note: I didn't find clear answers to these in related forums and I'm also not yet able to post anything there. Hoping someone knowledgeable and helpful reads this.
103
I would begin with calming yourself down :]
There's always chance to flash proper rom so don't worry.
Pick up proper DN distribution suitable for Your device and flash again.
Remember to clean system for new rom, wipe data/factory reset and also wipe cache and dalvik cache, format system, and flash the thing again.
Remember that not always rom will boot from the first kick.. it often happens to me (freeze on first screen - not Samsung but the one with Note2 screen), it's as easy as taking the battery off the device and reconnecting it again for awhile and then power on again (sometimes it works in thrid attepmt so be patient, once it runs there should be no more further problems)
I hope You will solve Your problem.
Good luck!
Yep I totally agree with roozxx on that
Sent from my GT-N7100 using XDA Premium 4 mobile app
Hi Everyone,
I come to you for a bit of help. I have spent a long time trying to fix this and come for help from you guys.
So I got a little bored with standard Samsung Android on my Note 2 (GT-N7100). Having used Cyanogen before, I decided to try it on the note.
I rooted the device and installed CWM on it no problems. I then loaded CM from a micro usb.
On reboot it just gets what i'd call the "Spinning blue screen of death" where it just has the big blue circle going round until it runs out of battery. After some research I used CWM to clean out the caches etc but it still didn't appear to work. This was using the stable version for my Note 2. I then went on to try other versions and got the same issues. Alas, trying to do a restore didn't work either, as it didn't seem to have all the files.
At this point I am happy to go back to stock Android or indeed CM. I'd just like a phone that works!
My device details:
Model GT-N7100
SSN: -N7100GSMH
Network Provider Virgin UK
Any help appreciated.
Two days ago my Galaxy Note 10.1 gt-n8010 got stuck at the initial screen (Samsung Galaxy Note 10.1)
It was working normally, and it was last successfully upgraded to a custom rom and CWM 6.0.3.6 a month ago.
The custom rom was (to my best knowledge Android Revolution HD 11.2 - 4.1.2)
Booting into recovery and download modes works.
CWM recovery works partially. Erasing Cache en resetting to factory works, and sometimes results in getting to the second splash screen of the boot process where it again gets stuck (Samsung animation keeps glowing), but more it keeps getting stuck at he first boot screen.
Erasing Dalvic cache leads to immediate reboot.
CWM log files cant be opened / external sd card can't be reached/mounted.
So CWM is only working for a small part.
I've attached images of the CWM screens including a log-screen that shows that files and folders cannot be found.
Using ODIN, to flash a new CWM or custom/original ROM result in a FAIL message.
Tried different ODIN version, two original Samsung data cables and two computers. Alle the same result. FAIL.
I'm hesitant to continue now without some help. I might do more harm and destroy all chances there are to recover this tablet.
I've flashed all my phones and tablets before. I'm not an expert, but never had a mishap, because I triple read the instructions. The situation that arises now is not a result of a failed upgrade/flash, but suddenly appeared one morning.
On the last days i thought i had also broken my tablet and i had more or less the same problem. If i were you i would directly download an official 4.4.2 and flash it via odin. Then if you everything works i would try whatever you want to flash
Try changing recovery. Give TWRP a try. Had it happen with a phone and switching recoveries solved it.
Sent from my SM-N900T using XDA Free mobile app
Well I had the same problem due to toooo many consecutive reboots
I was on gnabo then wid twrp
then I reflashed 4.4.2 update via odin and everything was a breeze after that
and one more thing
be sure to change the recovery cause the same one might not work again
well at least it didn't do worth me
I use philz now
Can't flash anything
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Deadbeef said:
Tried everything I could find but nothing works. I'm using windows 7 and cannot flash anything using Odin.
Download mode and CWM recovery still boot.
Are there other ways to communicate and reprogram the galaxy note 10.1?
Click to expand...
Click to collapse
are you sure you do not have a bad cable
I've used two different original Samsung cables. Same result.
Brick?
Change a Odin version like odin 3.07 http://forum.xda-developers.com/showthread.php?t=1837605?
your odin shows your device is Samsung I9505 Galaxy S4
Where does Odin show the device is a i9505? It's a n8010.
reCAPTCHA
I am having similar issues (Galaxy Note 10.1 N8010 Gnabo ROM) - stuck on the samsung logo (never managed to get past it though) boots into recovery but can't mount sd card OR internal storage. Can't flash anything using Odin, always gets a Complete(Write) operation failed. Any suggestions ?
Looks like we're both in the same sinking boat.
Sorry for late reply
Deadbeef said:
Where does Odin show the device is a i9505? It's a n8010.
Click to expand...
Click to collapse
Sorry for late reply
Your Odin Screen Shot Say i9505 as your device
Deadbeef said:
Looks like we're both in the same sinking boat.
Click to expand...
Click to collapse
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
georgesmh said:
I join u guys as well....
also was on gnabo rom and suddenly stuck on Samsung screen... however what's different from you is that I have a N8000 and Odin flashing shows "PASS". But whatever I flash doesn't boot... I think I need to open a thread about it.
Click to expand...
Click to collapse
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Agyar said:
Same here with Ganbo v7 since ysterday....
Just get stuck on Samsung logo and nothing works, even reverting to older backup image
Click to expand...
Click to collapse
guys did any of you solve the problem??
georgesmh said:
guys did any of you solve the problem??
Click to expand...
Click to collapse
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Agyar said:
Nothing yet.... I've tried one old backup of v5 I've had and that won't boot now as well...
Really strange. I'm hoping to get it working somehow over the weekend latest, since I'll be on business trip next week and would like to have operating device on airplanes.
Click to expand...
Click to collapse
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
georgesmh said:
maybe it's a problem from Gnabo ROM itself??? What's really sad is nobody on the threads knows how to help us
Uni starts next week!
Click to expand...
Click to collapse
I've seen few other occurrences of this on different roms on various forums, so probably not Gnabo issue. also, nobody nowhere had a fix for it
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
dmarchant said:
I had similar problem last November with a stock 4.4.2 ROM. Fortunately it was still in warranty (2 years in the UK) and Samsung took it in and replaced both battery and main board. They did not explain what was wrong, only that they were seeing quite a few with this issue. Could it be flash failure?
Click to expand...
Click to collapse
I don't think it was flash failure, at least not in my case, since device worked without any issue for quite a while after last flashing... what was different now is that my battery was drained out for the first time i quite a while...