[Fixed] Accidentally installed Tab 1 recovery onto Tab 2 - Galaxy Tab 2 Q&A, Help & Troubleshooting

I was following this the Cyanogen install directions for the p5110. When I to the section on downloading the recovery image, I headed to Clockworkmod but didn't scroll down far enough. The end result, I've installed the recovery for the Samsung Galaxy Tab _1_ 10.1 (wifi) onto my Galaxy Tab _2_ 10.1 (GT-P5100).
It's now stuck in a boot loop. Holding down power reboots to the Tab 2 10.1 screen, but holding the volume down/up buttons in various timings with the power button doesn't get me back into Download mode, it just comes back to the same Tab 2 10.1 screen over and over. I cannot get the device to power off completely, it just boots to the 10.1 screen again.
Is there any way to recover my device or have I bricked it?

After trying repeatedly to get back into download mode, I gave up for a few hours and came back once the battery had died.
After charging the battery for a while on a wall plug I tried to boot into download mode. This caused the same problem as before.
I thought I'd check to see if the USB was even visible within Linux on a PC so attached the USB cable and powered on. Magically, after a few iterations, it booted to the OS.

Related

Cannot boot into recovery

i have a Galaxy Tab 2 7.0 p3113.
i used heimdall to flash CWM into the tablet.
after what seemed like a succesful flash, my tablet rebooted. but for some reason, it would only go as far as showing the galaxy tab logo. it seems stuck there. i could not turn the unit off. i would hold the power button to force shutdown, but it always starts right back up. it seemed like i could only shut it down if it was connected to my mac while holding down the power button. i can however, boot into download mode.
after consulting google, it seems like the appropriate step was to restore the unit to stock. problem is, i can't seem to boot into recovery. i'm being told by the internet that to boot into recovery, i need to hold [power] and [volume down] until it turns on and then release [power] but keep on holding [volume down] and CWM will load. but nothing happens.
i know this is a total noob post, but i've been scouring the web for two days. i'm at my wits end. any help would be greatly appreciated.
I think recovery mode accessed via volume up+power if you could not so use download mode to flash stock or so to return to normal operation
Sent from my GT-I9100 using xda app-developers app
I press the power and UP ( button next to the power button) I normally hold BOTH buttons down at once and let the boot cycle process twice just to make sure i am going into recovery .....so i see the white samsung text twice i mean. It may take around 10 seconds to complete the process. Then release BOTH keys at once.
The battery needs a good charge for it to work.. Try charging over night before you try it via the mains supply.
Holding the power button and down will bring you into download mode and thats what you use for an odin/heimdall flash.
Hope that works for you
Let us know how you get on .....
Thanks. The battery of the gtab2 drained overnight, so i've got it charging back up now. Will definitely post my results when i have something.
Thank you guys. I'm able to boot into recovery now.
But unfortunately, i still need a little guidance on my original problem. And that problem being that my gtab2 will not startup. After rebooting, it gets stuck on the logo screen. It also plays a startup audio clip. But after that, it just displays the startup logo screen. It does not go into the animation screen and start.
I should also mention that when i plug my gtab2 into my computer, no drives show up.
My question now is, if i were to select [wipe data/factory reset] in CWM, would this restore my gtab2 to it's original factory state? Or would I need to flash a ROM for this? And if i need to flash a ROM, could i place a ROM on a microsd card and flash from there?
*********UPDATE*************
Everything is fine (so far).
I went poking around CWM and realized that I had put a cyanogenmod 9 update.zip in the root of the internal sd card before all this happened. So i went back to cyanogenmods wiki on how to install it on my gtab2 and followed the rest of the instructions on flashing it and VOILA!! I have my gtab2 back.
you should use ODIN instead CWM.
CWM is not designed specifically for Gtab2.

[Q] Tab not booting(P6200)

I have galaxy tab p6200. I had flashed the 4.4 omni rom available on XDA forums for p6200. It worked fine for about a month. Then one fine day, my tab did not boot up. I pressed the power button for about 60 sec, but still refuses to switch ON. I tried going to recovery and also to download mode, but the tab doesnt boot in either of these options.
But when I plugged the tab to my charger it showes the charging symbol and then when i go into recovery mode it boots up. But screen flicers and dies.
PLS Help me.....

[Q] gt-p5113 bricked

Gt-p5113 bricked stock rom-Canadian updated through kies the charge animation locked up and pad restarts, shows samasung galaxy tab 2 10.1 then goes to a black screen never seems to shut off.
No recovery mode only odin, after stock flash never shows andriod doll.
Tried power and volume down just resets back to samsung galaxy tab 2 10.1, power and volume up goes into odin mode.
Downloaded odin 1.85 and firmware Galaxy Tab 2 10.1 (WiFi) P5113UECLK7 region XAC flashed stock rom no errors and no change still boots to samsung galaxy tab 2 10.1 screen then goes blank.
Have tried to kill battery with tape the power button down for a few days then charge for 10 hours tried again no luck.
If tablet is plugged in to computer in device manager OMAP4430 shows corrupted bootloader maybe not sure how to fix this.

Galaxy Tab 7 sph-p100 boot looped after root attempt

Galaxy tab 7 sph-p100 stuck in a boot loop after root attempt, using odin3 v1.70 and CF-Root-TAB7_XX_OXA_JQ1-v3.3-CWM3RFS.tar and this tutorial off youtube "How to ROOT Galaxy TAB P1000 [Gingerbread]" ,Im not a developer , I wanted to gain root access to upgrade to jelly bean 4.4. I downloaded drivers for the tablet onto my pc based machine, downloaded the linked files, ran odin, selected PDA, selected the CF-Root-Tab7.tar, I want to note that In the tutorial the tabs stock version was 2.3.6 while mine WAS 2.3.4. With my tablet off I connected my usb cable, odin detected my device, with my device connected , odin displayed it as com-4 while in the tutorial the device connected read com-3, I hit start on odin, Odin's messages displayed 1 succeed/ 0 failure, my tab reboots and reads samsung then displays a faint white line on the right side of the screen and just keeps doing that. I hold power till it goes completely off , the I try holding power + Vol up keys when the samsung logo is displayed let off the vol and keep holding the power key till it goes Into recovery mode? which it wont...... I don't really know how to proceed at this point , Im pretty much stuck with this device until its figured out. Any help is much appreciated.
Wrong Tab sir.

Bricked Galaxy Tab 2 P3100

Hello XDA !
I have a Tab 2 P3100, bricked with Odin. I was using a flash file that I've used many times before on the same laptop, with the same cable, and the same tablet.
Something went wrong and Odin displayed an error saying there's no PIT partition .
I've tried to use different PCs and cables, still not working.
I'm stuck now at the emergency recovery page, and when connected to Kies it just hangs on "Connecting...". The device does charge alright but I cannot turn it off (it reboots instead of shutting down when I long press the power button).
I think it might be going into download mode when I hold power button + vol down, but I'm not sure as it gives me a blank black screen and gets a bit hot on the left upper corner.
Any Ideas ?
Thanks in advance!
UPDATE: I managed to find "loose" solder points on the USB port and replaced the whole port altogether, What I'm facing now is that after I flash the device with official stock ROM, Odin3 seems to finish the work and flash the whole ROM to the device, but when I try to reboot the device it's still stuck on emergency recovery screen.

Categories

Resources