Hi. I hope this is the correct forum. My Samsung Galaxy Tab 2 (10.1) won't shut down after the latest firmware update. I believe I had 4.2.1 and now I have 4.2.2. My device name is is GT-P5113. I plugged the Tab into my computer and Kies opened automatically. It said there was an update for my device so I updated.
All seems to be ok, but now when I choose to "shut down" the tablet shuts down and then cycles back on as if I had just pressed the power button to turn it back on.
I guess it could be worse - it could be refusing to turn on.
Is there a fix for this? Anybody else had this problem?
It is not rooted and I don't really want to do so.
Thanks in advance for any help!
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
wipe cache
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
mymeatb18 said:
I think u could wipe cache in stock recovery I would do that and see if that fixes it. Hold down vol up and power at the same time till the device reboots into recovery. Dunno how it is on the bigger ones but on the 7" I have to keeo holding the buttons for a second longer after the samsung gtab2 logo comes on to boot in to recovery.
Remember u dont want to factory reset just wipe cache
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
beezerhale said:
Thank you for the reply. I tried that and got an "error". I was able to get to recovery mode and choose "wipe cache". It begins and I get an error message.
Click to expand...
Click to collapse
What type of error?? :cyclops:
error
It just read "error" and a image of the little android on it's back.
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
beezerhale said:
It just read "error" and a image of the little android on it's back.
Click to expand...
Click to collapse
can you take a picture of it ??
mythi said:
What type of error?? :cyclops:
Click to expand...
Click to collapse
mythi said:
can you take a picture of it ??
Click to expand...
Click to collapse
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
beezerhale said:
I just uploaded 4 pics to a section of a website that I already have running.
Here is the link:
http://6thgraderocks.wix.com/galazyerror
The images show the end process of updating through Kies (I screen captured), the current tab info, the recovery screen and the error I get when I try to erase cache. Keep in mind, I am able to reboot and my tablet comes on like normal - no issues except when I try to turn it off - it comes right back on.
Click to expand...
Click to collapse
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
This tab is not rooted or tampered with at all. I have no desire to do so.
mythi said:
Did you try flashing pit?? did you flash jb bootloader ?? did your device be rooted before flash ?? were you on cm/aokp/pac/slim/etc ??? if yes whic h build did you flash black hawk next kernel ?? <--- may be it what caused it ---> did you try to downgrade to 4.0.3/4.0.4/4.1.2 if yes what happened what did you flash before going to stock rom like mod and etc ???? hope you answer these questions !!
also try this
enable usb debugging
turn off your tab fully
connect tab to pc pull a logcat dsmg ksmg and post them as txt or pastbin
does your tab stuck in recovery loop like rebooting always to recovery sometimes until you compeletly shut down the tab?
if it is under warranty return it to SAMMY TO FIX IT IT IS THEIR FAULT !!
i think it is not hard ware related don't worry !!
Click to expand...
Click to collapse
I have the exact same problem with BOTH my Galaxy Tab 2 10.1 (Wi-Fi only) It's a software problem for sure...
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
I know I could probably do that (flash back) myself, but I just don't want to. I have bricked a Kindle Fire before while trying to make it do what I wanted it to. I don't want to mess with this Galaxy - it does exactly what I want it to --- surf the web, Netflix/Hulu, and comic books - I'm not too complicated!
I spoke with Samsung yesterday and they said to try a hard reset. That did not work. I spoke with another rep this morning and they are going to repair or replace it for me. He sent a shipping label to my email. This was a gift and I have no receipt. I am VERY pleased with the service from Samsung.
SebasC said:
Also flashing back to 4.1.1 or lower will eliminate the problem
Sent from my GT-P5113 using xda app-developers app
Click to expand...
Click to collapse
So you're going to replace a perfectly good product with a software mistake? I've two tablets, unrooted, 4.2.2 with the same problem... Your better off waiting for a fix..
Why shoukd he feel burdened for something he had no control over. Samsung sent the update, iys not his fault its not doing what it should. If he wants to return it cuz it doesnt turn off as it should he has every right to do so. At least he didnt brick it and is expecting samsung to pay for it.
Sent from my GT-P3113 using xda app-developers app
I had the same problem
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Similar "Reboot after turn off" issue
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
d86 said:
Hello,
I registered here to just answer your question since I've been searching around on the internet as well for this problem. I have a Samsung Galaxy Tab 2 10.1 with version 4.2.1. I updated to version 4.2.2 and all hell broke loose. Before I get into it, I had a perfectly working tablet that never had any problems. I installed all updates through OTA or Samsung Kies. It's not rooted.
Anyway, after the update to 4.2.2 my tablet wouldn't turn on. I had to plug it into the wall outlet and then it finally turned on. After playing around with it, some of the widgets didn't work so I thought maybe I should turn it off and reboot it. When I chose "power off" it wouldn't turn off. Instead it would automatically restart. After trying several attempts it still wouldn't turn off so I contacted Samsung. They made me clear the cache and then wipe out the whole system and install a fresh copy of the software. The tablet then went black and now all that was shown on the screen was the little android bot with the error message like how yours is now. It wouldn't boot up to the main screen anymore.
So I had to return the tablet back to Samsung yesterday and they are going to attempt to fix it. It's still under warranty but I'll be pissed if I won't be able to install the new software on my tablet since I like the new updates they did for it.
Anyway, sorry for my long response but I hope this helps you out even though nothing was resolved. I'll post what happens once I get back my tablet.
Click to expand...
Click to collapse
Reboot issues
avm1 said:
I have the same "can't turn off" issue on my stock Tab 2 10.1 updated to 4.2.2 via Kies. After turning off and confirming on the screen, the tablet simply turns back on. This typically happens several times in a row before something happens and it stays off. I emailed Samsung to request support.
Click to expand...
Click to collapse
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
update #1
Just wanted to give an update. Samsung sent me an email yesterday stating they "fixed" my tablet. I should be getting back my tablet by the end of this week or early next week. The receipt said that it was a "software problem" and they reinstalled new software with the latest update. I'm just wondering if it's 4.1.2(that worked fine with my tablet) or 4.2.2(which messed up my tablet)
I'll give another update once I get it in my possession.
---------- Post added at 05:33 PM ---------- Previous post was at 05:28 PM ----------
SamsungTab2User said:
I had a live chat with Samsung just now. It is interesting that the tech I communicated with did not know of any issue with the rebooting and there was no mention in their system that a problem even existed (so I sent a link to this page to him).
Anyway, the end result was that it I wanted to fix the problem, I would have to restore Android through KIES:
samsung.com/us/support/faq/FAQ00052690/61266/GT-P3113GRSXAR
This will delete all data and get back to Android 4.2.1
Since I have already have seen issues with KIES, I wonder if it wouldn't be easier to just use ODIN? Any suggestions from those who might have tried both?
Click to expand...
Click to collapse
I tried this when I chatted with Samsung and it messed up my tablet completely where as when I rebooted my tablet it would show an android robot with "error"
Plus, I don't know about you but I don't want to have 4.2.1. I want to have the 4.2.2 update on my tablet. It's a much more sleeker interface. Just the only problem is that it wouldn't shut off. I will see what happens once I have it. If 4.2.1 is on my tablet I will try again updating the software to 4.2.2.
There are some problems like boot fail or can't poweroff I've seen at some posts, they do the same things:
1.flash a 4.2.2 stock rom
2.have some problems: boot fail or can't poweroff eg..
3.boot to recovery and want to wipe the cache
4.get a error with the robot logo lie down
I found a post mentions that he've fixed this problem by using odin 3.07 flash the 4.2.2 stock rom with a matched kernel boot file.
The post is here, it's in chinese:
http://b.it168.com/thread-4690107-1-1.html
His solution is get to this site to find the 4.2.2 stock rom and matched kernel file of your device and use odin 3.07 flash them:
http://samsung-updates.com/
do it at your own risk maybe solve your problem.
Update #2
So I got my tablet today and I turned it on to see that it had android software 4.1.1. Then the software update icon popped up and I updated to 4.2.2. Then the same problem happened again like the last time. The tablet wouldn't turn off and it would automatically restart. I contacted Samsung Support again and they had me do a factory reset which then fried my tablet again. It doesn't turn on. So now I have to send it back again for a 2nd time. This time they said they may have to replace the tablet either with the same tablet or a different model tablet. But I stressed to them to make sure to update the tablet this time to 4.2.2 so they can see the problem I'm facing. We shall see next week I guess what happens.
Related
i have one Samsung Galaxy Tap GT-P6200 hang in logo.Please tell me how to flash this phone with Odin or show me the produce.thanks
jimmymobile said:
i have one Samsung Galaxy Tap GT-P6200 hang in logo.Please tell me how to flash this phone with Odin or show me the produce.thanks
Click to expand...
Click to collapse
Wrong section.
Please re-explain what you mean. Are you bricked? Use better English please.
Thread moved to General.
I also have this problem. My tab got drained so when I got home, I plugged in the charger to the tab. Then I pressed the power button. So the tab opened but it hangs when the SAMSUNG logo is on the screen. I tried to wait it out for around 10mins but nothing happened, it remained in the SAMSUNG logo. So I tried holding the power button for 15secs to reboot but when it rebooted, the tab still hangs in the SAMSUNG logo.
Please help. I just bought this tab 3days ago. It is not rooted and so far I have installed only around 10 apps and games all from the market. Im not sure what caused this problem.
check in the development section under official firmwares post. there are official firmwares and instructions for odin. try to charge up battery as much as possible. a failed Odin flash could be a perma-brick. If you have Kies , I think there is an emergency software recovery option as well.
chrisrotolo said:
check in the development section under official firmwares post. there are official firmwares and instructions for odin. try to charge up battery as much as possible. a failed Odin flash could be a perma-brick. If you have Kies , I think there is an emergency software recovery option as well.
Click to expand...
Click to collapse
thanks for the reply dude. so im gonna have to flash this tab. i checked the instructions and all is good except for the ROM to use. there are 2 ROMs posted for the P6200. Im not sure which one i should use. I bought my tab here in Manila. All i know is that its a P6200 3g tab. Could i just pick anyone from the two?
The KK5 is the original firmware that the p-6200 came with . If you install that, as soon as you run it, it should be giving you the notification that an update is available . There will be 2 incremental upgrades and you will end up with KL1.
Or you can directly download the KL1 .
P_
pakalrtb said:
The KK5 is the original firmware that the p-6200 came with . If you install that, as soon as you run it, it should be giving you the notification that an update is available . There will be 2 incremental upgrades and you will end up with KL1.
Or you can directly download the KL1 .
P_
Click to expand...
Click to collapse
thanks dude! anyway im still thinking if i should flash this now or just bring it to Samsung for service. im afraid that if i flashed this, Samsung might say that ive been tinkering with it.
Before venturing yourself into flashing the stock rom why don't you try a factory reset from the recovery menu :
Turn off the tablet
Press at the same time the power button and the volume up button
As soon as you see the galaxy logo release the power button but keep the volume up pressed until the recovery menu pop up
Select the factory reset option using the volume button and confirm with the power button
I am pretty sure that it will fix your problem
Let me know how it goes
P_
pakalrtb said:
Before venturing yourself into flashing the stock rom why don't you try a factory reset from the recovery menu :
Turn off the tablet
Press at the same time the power button and the volume up button
As soon as you see the galaxy logo release the power button but keep the volume up pressed until the recovery menu pop up
Select the factory reset option using the volume button and confirm with the power button
I am pretty sure that it will fix your problem
Let me know how it goes
P_
Click to expand...
Click to collapse
thanks dude!! the problem was fixed after the factory reset.
im still wondering though what caused the problem. ill probably try draining the battery again to see if this problem reoccurs.
thanks again!!!
successfully done p 6200
Hi all. I've had the same problem last month. My P6200's battery got drained and was kind of in a boot loop. I didn't know how to do a factory reset then so I looked online for a Samsung Service Center here in the Philippines. I was advised that my device was not covered by International Warranty as I bought it outside of the Philippines (I got mine in India) as only Samsung cameras have have international coverage. The guy still tried to flash it, however, it did not fix the problem. Now it just boot loops to the Samsung Galaxy Tab 7.0 Plus and does not reach the Samsung logo that it used to go to after that.
I'm trying to reset my tab but pressing and holding the power and volume up buttons don't work. Please advise what I can do. I don't want this device to go to waste.
Many Thanks!
ive also had the same problem duno wut to do anymore
Had bootloop problem too
Download Odin and the appropriate firmware for your region then flash it via Odin(turn off tab,press volum down and power until you go in download mode then connect the tab to pc,click pda on Odin,click start,wait to flash)
Good luck
i had the same problem before, when i restart my tab, it was stuck at samsung logo, i wait for 15m but still the same and then i connect to my laptop.
amazingly, kies can detect my tab, so i did backup, suddenly samsung logo disappeared and enter homescreen. maybe around 15m more after i connect to my laptop.
my suspect was the ADW laucher because there's no problem before i installed adw launcher and set it as default launcher.
Try clearing dalvik cache from recovery ....worked for me....please keep it as a personal opinion....search threads for better solutions....try this if nothing works...
Sent from my GT-P6200 using Tapatalk 2
gudbud said:
Try clearing dalvik cache from recovery ....worked for me....please keep it as a personal opinion....search threads for better solutions....try this if nothing works...
Sent from my GT-P6200 using Tapatalk 2
Click to expand...
Click to collapse
Not sure if trolling or not reading dates... The last post in this thread is from May...
Sent from my myTouch 4g via Tapatalk
i tried factory reset so many time but still stuck..my problem now is it keep rebooting after flashing 3.2 HC..anybody please
Same
jerung16 said:
i tried factory reset so many time but still stuck..my problem now is it keep rebooting after flashing 3.2 HC..anybody please
Click to expand...
Click to collapse
SAME!!!
CLink08 said:
SAME!!!
Click to expand...
Click to collapse
New here? If you are on HC.. enter recovery then wipe cache and partition.. you're welcome
Sent from my GT-P6200 using XDA Premium HD app
All,
Hopefully this is an easy one. I looked through the board and did not see anything I haven't similar but i can be wrong. Quick background, I rebooted the phone it looked normal on shutdown but it never came back up.. What I have tried is tremove the battery and left it for day and tried to turn on with no luck. A couple of times it showed the battery indicator but would go black screen if i tried to turn it on. I have reloaded the stock rom using ODIN still no luck. The only thing I can make it do is go to the download screen, that's it. This is a stock ATT Skyrocket no mods or anything. It seems to be a software issue but I do not know how to fix it. Any Ideas Thanks
oops!
l33t_killa said:
I'm in the same boat. Root was a confirmed success after the OTA update, but now I can't get pass the download screen while booting up the phone. When I was trying to boot into recovery mode after I did a few quick restarts in a row after rooting phone, to install a debloater .zip, it came to this screen only (see screenshot), the Samsung logo comes up before this and it's all that it does now. Thinking it's a soft brick as this screen is the only thing that keeps coming up after Samsung Logo with no unlock/lock symbol, when I try to reboot the phone in various ways. I know I can't use Odin to reflash back to stock MDL after the June OTA update, as I tried with no luck came up failed like I knew it would. Plug in via usb to computer, PC doesn't recognize it, so I can't check / access anything on the phone. Pulling straws here. PLEASE HELP.......
US ATT SGH-1337 Jelly Bean 4.2.2
(Last night) Stock Firm: I337UCUAMDL
(This morning) OTA Firm: I337UCUAMF3
Click to expand...
Click to collapse
Wrong forum bro
Sent from my GT-P5113 using Tapatalk 4
xcrazydx said:
Wrong forum bro
Sent from my GT-P5113 using Tapatalk 4
Click to expand...
Click to collapse
Didn't notice that....
l33t_killa said:
Didn't notice that....
Click to expand...
Click to collapse
Glad I caught it before you bricked using our files. Good luck!
Sent from my GT-P5113 using Tapatalk 4
OK here goes.....
Turned my phone on and got "Process com.android.phone stopped unexpectedly. Try again." Clicked Force Stop as I couldn't get past it otherwise. Then got to the "Touch the android to begin". So touched the android and ...... nothing!! It just stayed on that screen. I can't get to any apps or settings and can only use the keypad to dial emergency numbers.
I searched the internet, as one does these days, and tried the touching all 4 corners of the screen to get around the android, and still nothing.
I've tried doing the reset and hard factory reset, taking the battery out and waiting, then putting it back and trying the reset again, but each time the phone reboots I get the "Process com ......" or "Touch the android...."
I'm not that au fait with Android and am finding it hard to understand much of what's being said on these forums (so much jargon and so many acronyms, it seems like you all were born knowing this stuff!!! ) that I'm sure the more things I'm trying the worse I'm making it!!
I can still get into Recovery and Download so I don't think I've messed up completely, but I'm so p!$$ed off with it now I just want to throw the phone down the toilet!!! So, pleeeeeze somebody, can you explain in absolute idiots language what I should do.
The phone is:
Samsung Galaxy Y Duos GT S6102 and it is rooted.
Any help would be appreciated.
What rom are you trying to flash?
Sent from my GT-S6102 using xda app-developers app
Aakashtitli said:
What rom are you trying to flash?
Sent from my GT-S6102 using xda app-developers app
Click to expand...
Click to collapse
I'm not trying to flash any ROM. I just want to use my phone.
It was Gingerbread but I don't know which version or which version of Android.
As I said above, I just turned it on yesterday morning and I got the message about Process blah blah......! I wasn't trying to do anything else except turn it on as usual.
deleted
ckr1986 said:
This worked for me:
Clear data for the phone app and contacts , force stop and try again. (back up your contacts before clearing data cuz it wil be erased)
Click to expand...
Click to collapse
I'm sorry but I don't know what you mean.
are you able to reach the homescreen of your device?
http://forum.xda-developers.com/showthread.php?t=1990997
You can ask here if you dont understand something. I believe that your firmware in your phone got corrupted or the internal SD is bad/corrupted.
If its the former, good you can fix that with the above link. If not, then your phone is bust. Its not going to get fixed.
Lower end smatphones do have these types of issues, so if you do change your phone to something else, just visit alot of forums and make up your mind, at least you wont get suprised when you see others report problems. I hope that this could help.
ckr1986 said:
deleted
Click to expand...
Click to collapse
ckr1986 said:
are you able to reach the homescreen of your device?
Click to expand...
Click to collapse
I turn on the phone and the Samsung icon comes up with the jingle. After the vibrate, it goes to the black screen with the android with a message saying "Touch the android to begin". Below that are 2 options - Emergency call and change language.
After a few seconds a window comes saying "Process com.android.phone stopped unexpectedly. Try again". And below that is a button "Force Stop". If I press Force Stop, I get back to the first screen with the android and the message "Touch the android ..........". If I leave it at "Process com..............................." that's how it stays.
So to clarify - the only screen I get is the "Touch the android to begin". I cannot get any further.
I have tried the touching the 4 corners of the screen to bypass the android but nothing happens.
Alright ...guess the best bet for you is to reflash your stock rom (the software thats currently in your phone). You could check out the link that shadowcore posted above.
Sent from my SM-N9005 using Tapatalk
ckr1986 said:
Alright ...guess the best bet for you is to reflash your stock rom (the software thats currently in your phone). You could check out the link that shadowcore posted above.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
OK, so couldn't understand how to flash the rom suggested by shadowcore! Told you I needed an idiots guide!!!!
Anyway I downloaded stock firmware XXMA3 from samMobile. Opened it up in Odin 3, let it do its thing until Odin said PASS. But phone looped at reboot so I had to wipe data in Recovery thinking I would have to start all over again but.....voila!!!!
All sorted!!!!!
Thanks for your help anyways.
Glad to hear it all worked out !
Sent from my SM-N9005 using Tapatalk
Hi thanks for reading, I will tell you as quick as I can
Basically I got this Allwinner A31 Tablet Q102 and wanted to root it and flash it when I got it, so I got it only a week ago, week ago from tommorow.
I managed to root it with VRoot and then attempted to install CWM because ROM Manager would say that it isnt supported. So after tons of research I took the method of rooting an Onda tablet which was to use the ADB. I got the Recovery.tar extracted the files inside it and then did the
adb push /data/recovery.img
And stuff like that
After I did all that it told me to hold the VOL+/POWER to enter CWM, I held it for like 1 minute until CWM showed and it was working. CWM version was 6.0.2.7 I think. So I was like oh ok its working now. So then I rebooted the system using the first option CWM gave me. After it turned off it didnt turn back on. So I turned it on manually and all I see is a blank BLACK screen. Thats it. It hangs and does nothing. Cant enter Recovery, safe mode, the USB is not recognized. Infact it doesnt even connect anymore.
If I hold the power button, it turns off then once I let go it turns back on doing the same thing.
Please help me as I only just got the Tablet and can't afford to lose it. Theres too many files I need to keep, only some were moved to the SD card.
4.4.2 KitKat
addy187a said:
Hi thanks for reading, I will tell you as quick as I can
Basically I got this Allwinner A31 Tablet Q102 and wanted to root it and flash it when I got it, so I got it only a week ago, week ago from tommorow.
I managed to root it with VRoot and then attempted to install CWM because ROM Manager would say that it isnt supported. So after tons of research I took the method of rooting an Onda tablet which was to use the ADB. I got the Recovery.tar extracted the files inside it and then did the
adb push /data/recovery.img
And stuff like that
After I did all that it told me to hold the VOL+/POWER to enter CWM, I held it for like 1 minute until CWM showed and it was working. CWM version was 6.0.2.7 I think. So I was like oh ok its working now. So then I rebooted the system using the first option CWM gave me. After it turned off it didnt turn back on. So I turned it on manually and all I see is a blank BLACK screen. Thats it. It hangs and does nothing. Cant enter Recovery, safe mode, the USB is not recognized. Infact it doesnt even connect anymore.
If I hold the power button, it turns off then once I let go it turns back on doing the same thing.
Please help me as I only just got the Tablet and can't afford to lose it. Theres too many files I need to keep, only some were moved to the SD card.
4.4.2 KitKat
Click to expand...
Click to collapse
So,Wrong discussion area...Anyway
You're still under warranty,why dont you just RMA it?
just dont tell them you're rooted or anything mess with softwares.
androidvillage said:
So,Wrong discussion area...Anyway
You're still under warranty,why dont you just RMA it?
just dont tell them you're rooted or anything mess with softwares.
Click to expand...
Click to collapse
Hi, thanks for the replay, the business wouldnt replace it but they offered to have a look, I know its bricked so there is no point sending it there. I hear you can fix it in Phoenix Suite but I cant find the firmware for it.
Btw what should it be in, I had trouble sorting it lol
addy187a said:
Hi, thanks for the replay, the business wouldnt replace it but they offered to have a look, I know its bricked so there is no point sending it there. I hear you can fix it in Phoenix Suite but I cant find the firmware for it.
Btw what should it be in, I had trouble sorting it lol
Click to expand...
Click to collapse
Ok but....what is the actual model of this thing?
androidvillage said:
Ok but....what is the actual model of this thing?
Click to expand...
Click to collapse
Took ages to find out, but its called an Allwinner Q102 something with YBC, Ive heard of a similar one called Allwinner A31s Yonestoptech and was also a Q102
Hey,
What's up with your tablet? I own the same model and was thinking about installing cyanogenmod, but I have no idea yet. Have you managed to figure something out, or found any way to repair it?
Cheers!
flash ??
Try to flash the stock ROM.......
Nah man, I can't do anything with it. Turn it on just a black screen. Holding the volume down button then pressing Tue power button a couple of times makes my computer detect the tablet. But nothing else.
I cannot enter CWM, after I flashed CWM it said Can't mount boot.IMG can't Mount this and that and then I restarted it and it happened.
SO DONT FLASH ANY CWM OR ROMS ON IT.
I really want the tablet fixed man. What the hell do I do?
Sent from my HTC One using XDA Free mobile app
Try this mate
slatedroid.com/topic/40623-aml-flash-tool-aka-imageburntool/
Sent from my GT-P5210 using XDA Free mobile app
@addy187a - Did you get it done?
I have the same problem.... - I installed successfully twrp, did a backup, wiped and tried to install another rom - failed. Now I am not able to boot into recovery - it is black, not recognized by the system (so I can't use imageburntool).
It starts, is black illuminated, nothing happens, only power is possible
my device: Fusion5 F5CS 32GB, Q102, 32GB
..no idea what to do...
Hey, I know I'm 1 year late to reply but I only just logged in to XDA since ages! I know right? Anyway, the way I fixed it was to download the firmware for the tablet which I found out by keeping a note about tablet model number (Settings> About device> Model) and spent a couple minutes searching for the firmware for it. Then I used Phoenix suite or just Phoenix can't remember what it was called to flash the tablet. There are plenty of YouTube videos and instructions on the web of how to use it, I can't remember how I did it as this was over a year and a half ago! It's as simple as that and words cannot describe how relieved I felt after reviving it. If an admin sees this, please close the thread. I'm still finding out how to use this site.
HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
Good point cindy if its an internal hardware issue verizon will replace it at no charge
From my Wicked S3 running MIUI
how is this even possible?
gorilla29 said:
HELP!!!
About 1 month ago, my Galaxy S3 running 4.4.2 (Completely stock: no root, rom, or custom firmware), suddenly got into a boot loop about 3 weeks after receiving the 4.4.2 update. At first, it would boot up completely into the OS, then shut down before I even had time to enter PIN. Sometimes, after shutting down, it would restart by itself, but only on some occasions. I was able to enter and constantly use recovery and download mode with no shutdowns, so it wasn't a battery problem, instead a software/firmware one. I found that if the phone was plugged in while booting, I was able to use the phone with no problem, but it shut off as soon as the charger was removed. I then factory reset it, wiped the cache and such, but the problem still persisted. After about not touching it for a week, the phone wouldn't even make it past the first Samsung boot animation and jingle without turning off. However, the plugging in method would make it go further into the boot sequence, but it still wouldn't boot into the OS. After leaving it alone for one more week, I then LOST RECOVERY ACCESS! It would boot up to the android figure, but shut off immediately. I was able to access download mode, and therefore, tried to flash an earlier firmware with ODIN.
The phone was recognized by ODIN, but the flashing process failed. I first tried to root the stock ROM, but ODIN couldn't find the recovery. I then tried to downgrade my firmware to 4.1.2. I got a FAIL message on my PC and an error message on the phone (in ODIN mode) saying, " SW REV CHECK FAIL: FUSED 2 BINARY 0" Now every time I try to turn on the phone, it goes straight into ODIN mode, and it shows the message, : Firmware upgrade encountered an issue, Please use Software Repair Assistant & try again" with an image of a phone and PC linked together, but being interrupted by a yellow triangle with an exclamation mark in it.
HELP ME PLEASE. I LOVE THIS PHONE AND I STILL HAVE A WHILE UNTIL I CAN GET A NEW ONE!!!!
Click to expand...
Click to collapse
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
cyberkeeper1 said:
I would love to help, but please help me first. how do you claim to have 4.4 kitkat when for the i535 there is confirmed to only be 4.3 for a stock OS? this will make a big difference in the outcome of who can help you. Google and android both confirm that 4.3 is the last update for this phone coming from verizon. How can you have 4.4 stock with touchwiz and everything? unless you have AOSP, which is another things entirely. this phone does poorly for 4.4 in AOSP because we don't have a proper kernel or baseband for it. it wasn't officially released.
anyway, that is my question to you.
Click to expand...
Click to collapse
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
I wish it was.
cindylike24 said:
Is your phone still under warranty with your wireless carrier? If it is, you may want to contact the customer support department. You may be able to get a new phone as a warranty replacement.
Cindy
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
Click to expand...
Click to collapse
No, Cindy, it isn't under warranty anymore. It has been more than one year. I wish it was though!
Thanks, but...
JudgeFutta said:
4.4.2 is the latest and probably the last update for the i535. This should fix your problem OP. http://forum.xda-developers.com/showthread.php?t=2791801
Click to expand...
Click to collapse
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
gorilla29 said:
Thank you so much for your help. I flashed the file, and I got recovery back. However, the phone has just returned to the state that this problem begun with. It still goes further into the boot sequence (still won't start) when plugged in, but it will shut off before it finishes and as soon as it's unplugged. It won't even start the sequence without the charger.
Any other suggestions?
Click to expand...
Click to collapse
Try flashing the .tar file from the second post. Also make sure you have odin setup correctly like cyberkeeper1 said.
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
SlimSnoopOS said:
VRUDNE1 4.4.2 has been available for roughly two months.
Verizon PDF (laziness, Verizon did not change the software name to VRUDNE1): http://www.verizonwireless.com/support/system_update/galaxys3.html
Samsung PDF (click first question under FAQ): http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW?
Quick online search: http://www.droid-life.com/2014/06/19/verizons-samsung-galaxy-s3-galaxy-s4-mini-kit-kat/
Click to expand...
Click to collapse
Many thanks, Slim.
Should be made a sticky. This is important stuff for this phone.
Sent from my SCH-I535 using XDA Free mobile app
cyberkeeper1 said:
Is that so? I had no idea. I was told by Verizon the 4.3 is the last one. I certainly will investigate. On ODIN, make SURE you check the bootloader update option, F. Reset Time, and auto reboot. Otherwise, the bootloader will not allow you to boot.
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
Would the file go under PDA (AP) or BL?
gorilla29 said:
Would the file go under PDA (AP) or BL?
Click to expand...
Click to collapse
PDA (AP)
JudgeFutta said:
PDA (AP)
Click to expand...
Click to collapse
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
gorilla29 said:
I tried everything you suggested. I am able to boot into the OS, but only while connected to power. Definitely helped, but didn't solve.
Any suggestions?
Click to expand...
Click to collapse
However, the phone will still shut down once booted, despite it being connected to power.
gorilla29 said:
However, the phone will still shut down once booted, despite it being connected to power.
Click to expand...
Click to collapse
It may be the battery or the phone just went out.
JudgeFutta said:
It may be the battery or the phone just went out.
Click to expand...
Click to collapse
Maybe, but the phone never shuts off during recovery. I bet the phone is just done. Lol