How to fix my tab? Help, I have bricked it, I have video - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Alright, I have some weird things going on in my galaxy tab. I think its bricked, but if it is, its definitely only soft bricked.
Figured I'd post a video showing stuff as I cant really explain it. It shows up in my windows, so i can access inside it, but i have no idea what to do, it shows up in Kies, too
I'm wanting to hopefully make it usable, and if not usable AT LEAST get rid of clockwork mod recovery so I can return it!
So how do i fix my tab?
(note i was following the samsunggalaxytabhacks unrooting guide when I did this, I cant link b/c new
7510, btw

did you flash anything prior to this happening? I ask as I used the wrong kernel one time, one that wasn't for TW and when I rebooted it did the exact same thing... Did you make a backup?
Try to d/l one of the custom roms, since kies can see it, place the zip on sdcard and follow the OP to install it.

yeah im pretty sure i used the 3g model/non touchwiz kernal and this happened! i cleared m device, thinking it would fix it i guess i lost my backup!

go to roms section on 10.1 android development, and look for the correct kernel, transfer to sdcard via kies and go to recovery and reflash kernel for the TW. Or just d/l Tasks/Phantoms rom Paris and do the same, follow the OP to a T, that should fix it.

which one would be the right one?

I would use
http://forum.xda-developers.com/showthread.php?t=1284355

reload
There is a very good walkthough on putting your 7510 back to stock (first step I would suggest). This walk through gives you all the files you need. I have tested this (files include tested pit files, rom files, etc..)
Hope this helps...
http://p7510.teamovercome.net/?page_id=18

Related

[Q] just fu** up my tab trying to get ICS!

Tried getting a cyagen 9 ICS rom on my 3g wifi 10.1 tab, forgot to install the clockwork stuff, and now it wont work no more. Think i managed to delete everything on it!? Did manage to install clockwork after via odin but now it find no files on sd and nothing else will work. The sd card will not appear via usb on my pc so i cant put new files in!?
Is there any hope for it or is the garbage can next stop?
Magnar, Norway
Apparently you can see the device with odin - I'd recommend doing a full restock, you can follow the guide at the overcome experience: http://www.teamovercome.net/p7500/?page_id=5
Scroll down on that page until you see the "Re-“Stocking” Yer System…" part and follow the instructions there.
Once you do that your tab should be back in working condition and you'll be able to install CWM and a custom ROM with it. And another piece of advice - always (seriously, ALWAYS) do a nandroid backup of your system before flashing ROMs, especially if you aren't 100% sure what you need to do. This way, if something goes wrong, you can always just restore the backup and you're good to go.
Best of luck!
Why don't you just mount your tablet to you PC through - mounts and storage in CWM recovery? It should work. If not, do what the guy above me said.
jippi
Tried mounting usb but it did not work just got error. Tried the full restock and that did the trick. THANKS
That's why reading helps, It clearly says "Flash the zip using CWM" because modified files cannot be flashed by the stock recovery due to Googles restriction's to avoid breaking their EULA, so the work around would be using a personal made CWM. Problem is stock one is only meant to flash update.zip, to specific folder's, when you install a ROM via stock, it just dumps and replaces everything in one place, It's like getting all your 3 Science subject notes mixed in 1 notebook, you have no idea what is what.

[Q] I hope I didn't brick my 10.1 Wifi Tab... HELP

So I am not sure what happened. I started with a stock rom (and what I thought was) a rooted tab. I wanted to try the new ICS nightly so I downloaded the ROM and attempted to install it from ROM Manager (install from SD Card option). That didn't seem to do anything so I booted into recovery and tried to install it from there. That's what it all went wrong. After rebooting, my tab stays at the screen that says "Samsung Galaxy Tab 10.1" (picture). I've rebooted several times but it still comes back to this screen. I've left it for over 30 minutes just to be sure it wasn't stuck building the cache or something (I did try deleting the cache).
I am able to get into Download mode and connect with ODIN and have tried flashing several stock ROMs and others. The load successfully but after rebooting, it still gets stuck at this screen.
Any suggestions?
Well, simple enough, when you flash a stock ROM, you boot into the recovery, and do a factory reset, I know it sounds silly but there are some files that are in the tablet, since the tablet has no SD card slot, it will try to read the sectors that were replaced and not replaced. If the nightly build files are in the system, it ends up reading that since some files don't get replaced as they have roman's name on it, (You can confirm this by checking in Titanium Backup )
You can however flash with a PIT file if you feel lazy to do that and would want to start without the hassle of booting into several options, just flash the file to completely wipe and repartition the thing, that would be your best bet. Should be on the Overcome thread to grab the pit file. That should do the trick
Thanks for giving me hope! I just did some reading and I am afraid to download and attempt the wrong .pit file. Any chance you can give me a link to the correct .pit file for my tab (GT-P7510UWYB)?
Thanks again for the help!
Thanks again Misledz! I found this thread over on the Overcome site (link) that had all the files and very detailed instructions. Ran the PIT to bring it back to stock and it looks like it worked! You saved another tab!
! Yeah I don't really keep track of the websites But I do know where most of the files are, and Overcome thread seems to be doing a good job of hosting the files required to save every man, woman and child's tab
It's all good, Don't mention it , Glad it's alive

SD card required?

Hey, im new here, and completely new to the whole "custom rom flashing" thing.
I would like to get into rooting my phone and then installing a custom rom like resurrection for example, but I have a couple of questions.
1. Do I need an SD card in my phone, to be able to root my phone/install custom roms? or can I just use the phones internal 16gb memory?
2. Would someone be kind enough to point me to a guide to rooting/installing custom roms for complete newbies like myself? I have searched the forums, but theres so many threads about different stuff, like clockworkmod/odin/cyanogenmod etc, my head is completely boggled. I just don't know where to begin with any of it.
Cheers.
1) No.
2) Everything you need to know is in the Stickies.
MistahBungle said:
1) No.
2) Everything you need to know is in the Stickies.
Click to expand...
Click to collapse
1. No you cant root without an SD card? or No you don't need an SD card? elaborate please.
2. Nothing in that thread helps someone like me who is totally new. I don't know what any of it means. Surely there is a simple guide that explains exactly how to root your phone, without linking you to 7 other threads in the process? That's all I've found up until now.
This requires sdcard
http://forum.xda-developers.com/showthread.php?t=1501719
This doesn't
http://forum.xda-developers.com/showthread.php?t=1103399
Thanks, thats what I was looking for.
One more thing, just so I dont make a mistake, could you tell me which kernel to download? my kernel version is 3.0.15-I9100BVLPB-CL310231
cheers.
Read the bit in bold read which says 'Help ! Which file do I use ?'. This short section answers your question exactly.
ok well i tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5-PROPER.zip and my phone no longer boots....
tried CF-Root-SGS2_XX_OXX_LPB-v5.2-CWM5.zip and I get the same thing, so im stuck now. great.
I can get into CWM recovery, but I have no idea how to copy the rom I want to use onto the phone when its in recovery mode. This is something that is just not explained anywhere
help?
Right. In order of importance:-
1) No bumping threads within 37 minutes. Not cool. This is not your personal tech support forum.
2) You're having problems. Why ? Who knows. We're not there looking over your shoulder so we have no idea exactly what you did. I suspect you're having problems because you are in too much of a hurry/took shortcuts & didn't do what was suggested immediately after your OP.
3) However...Given the situation you find yourself in, I recommend you do one of two things:-
A) If you are absolutely sure you have CWM Recovery & not Android recovery (I say this because if your phone isn't booting normally, that normally means the flash didn't work & normally CWM wouldn't be successfully installed either), follow whatever instructions the rom you're wanting to flash has.
Every single rom on here has flashing instructions, normally on the first post on the first page of the thread on here devoted to the rom. If you can't be bothered reading those, I can't help you.
or
B) Go to Samfirmware.com. Search for the firmware that was on your phone before you tried to root it. Download this firmware. Flash the firmware you download following the instructions here. If you also end up with a .dll file, bin it. You don't need it. This will give you a clean install of stock. From there, I strongly suggest you read the CFRoot thread very carefully before you attempt to root your phone again. I also strongly recommend you read the Stickies linked to above, so you have some sort of understanding around what's what with this phone.
If you don't, being a betting man, I'll wager there's a fair chance you'll find yourself in the situation you currently find yourself in again (best case scenario), or worst case you'll end up with a 135gm paperweight as many people have on here over the past few days.
It's all up to you now. Your phone's destiny is in your hands.
Thanks for the reply, much appreciated.
Sorry for bumping, I panicked a little when my phone wouldnt boot. I just expected it to work because I have done things like this in the past and never had problems. Im a pretty tech savvy person really, im just new to android.
I wish it was as simple as reading one thread, but there are dozens of different threads on how to root this phone, and different methods, its extremely confusing.
Im downloading the stock kernel now (300+mb for some reason, and its going to take over an hour to download)
Once I get my phone back to normal, I'll read through some more threads and try and get a better understanding on how to root my phone.
I had it rooted properly as the recovery mode stated CWM in the corner, I think the issue I had was not being able to copy the rom I wanted to use, onto the phone, because I dont have an SD card.
Anyway, thanks for the help, and fingers crossed I can at least get my phone to boot again.
Man, I've never come across anything so complicated in all my life lol.
Edit: Sorted! Flashed back to original kernel and its working as it was before I started. Thanks very much for your help mate, and at least now I know how to restore my phone if I mess it up again in the future.
just thought I would update this thread and say I finally accomplished what I wanted.
Incase anyone is wondering, this is what I did:
Restored my phone back to factory settings/firmware/kernel
Booted the phone up, and copied my rom of choice to the internal memory via USB connection, and enabled debug mode.
restarted in download mode and flashed cf-root kernel (ended up with bootloop)
went ahead and installed the rom via clockwork recovery (creating a backup first)
The phone now boots into the rom im using (Resurrection Remix)
So if anyone is a little worried by getting the bootloop (but can still get into clockwork recovery) try flashing your required rom. Your phone may boot fine with new rom anyway. Mine did.

Q: blank screen after T-Mo splash animation, possible to fix without wiping?

Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737

Flashed an incompatible ROM. Able to get into download mode. Now what?

I rooted my sprint Note 3 when I first got it three years ago and flashed it with a custom ROM. I used it for a year and then got a cell phone from work, so I basically stopped using the Note 3 except occasionally. I decided the other day that I wanted to try updating to a newer version of android on the Note 3. It's been a long time since I messed around with rooting, ROMs, and such, and I did not pay close attention to what I was doing and flashed a ROM that was incompatible. When I restarted, I got a Set Warranty Bit Kernel error. I can get the phone into download mode, but I'm unsure of what to do next to get it back to a usable state.
Is there a guide somewhere to walk me through this process?
Thanks!
Solved
Well, I got the phone working again. I basically followed this guide I found. I tried to paste in the link but I'm still too much of a noob. Anyway, it was on android central, and part of the url was how-flash-stock-rom-via-odin-new-interface. Hope that helps someone.
There was one step not covered in that guide - odin kept saying that the md5 value was invalid. I found a youtube video that said to change the extension of the firmware (it was .tar.md5, changed to .tar). After that, it worked and my phone is back.
Is there a guide somewhere to walk me through this process?
Click to expand...
Click to collapse
There's guides everywhere on this site! Just gotta find the right ones lol. Makes it that much better when you finally find em. Next time make a complete backup of your phone first. I like to use TWRP, you can download it directly from the Play Store. I got my Stock Firmware from this archive:
http://samsung-updates.com/device/?id=SM-N900P
Make a backup of that then flash away! It'll be a lot easier/faster to recover with TWRP. What ROM did you flash to yours? Just curious cause every one I've tried had multiple issues to where I wasn't even able to use half my phone smh. Then I root it with CF-Auto:
https://forum.xda-developers.com/showthread.php?t=2466423
Through Odin:
http://odindownload.com/download/#.WYX1A4jyuyJ
Then I make a another separate TWRP backup of my Rooted Stock Phone just in case lol. Lemme know if you run into problems again I'll try to help find it and/or fix it. The more problems I deal with the more I learn! :fingers-crossed:
Might wanna get a USB storage or something too cause ALL these backups take up time and space. (My external SD Card slot hasn't worked for awhile!)... does yours?

Categories

Resources