possible brick please help - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I restored a back i made a few weeks ago, all went well. hit reboot in recovery. Now my tab just hangs on splash screen. i can not get back in to recovery or the download mode. when i power the the tab down and plug it in the battary charge indicator freezes also.
Were do i go from here please help

looks like we're both up the creek without a paddle, bro.
see the rainbow scan lines thread, hopefully we'll both get an answer

Related

[Q] Platypus Boot Looping

Ok so i recently tried to boot The Platypus rom and it had success but now my phone has just been looping from the original sgh screen and then it will flash the Platypus boot and then it will appear for about 3 seconds, after that sometimes in will show CWR and then for a split second the yellow triangle will show up. My phone just keeps doing it over and over. I tried to recover but it says there no recovery
How do i fix this?!
hey, sorry bro..my advice sort of got you here. But from what your describing...if that were to happen to me. I would straight up pull battery, plug in usb cable...hold volume down while re-inserting battery. bam download mode. Back to stock. Repeat from start.
fromthestars said:
hey, sorry bro..my advice sort of got you here. But from what your describing...if that were to happen to me. I would straight up pull battery, plug in usb cable...hold volume down while re-inserting battery. bam download mode. Back to stock. Repeat from start.
Click to expand...
Click to collapse
WOW, I tried to go into download mode 50 times and it never worked, as soon as i read your post and do it exactly as you said it worked
Thanks
EDIT: Ok so by phone desided to do that again and doing the battery pull isnt working :l just loop de loop. When I do try to get into download mode it show the battery with the loading circle and just goes to Platypus and to CWR and loop.

Help!!! My Samsung galaxy player is bricked! (i think)

hello, my name is shahrukh and i need some help. i downloaded animmod (from 4shared) and then i donwloaded busybox. then i pressed blur and then it asked me if i want to reboot it. i pressed yes. this is when the problem starts. It turned off and then it turned on half way and then it turned off. it kept doing that and then i just left it for the night. in the morning it was not doing anything. when i held the power button it turned off and on for like two times and then turned off. i cant even start it up so i have no idea what to do.
i don"t know what to do
please help!!!!
Okay, we need details, describe exactly when "halfway on" is. We need your full model number and rom version (if you know it). Have you tried plugging it in to charge? Does it show anything now that you try to boot it? try holding volume up and powering on to enter recovery menu.
details
ok so when it turns on it says samsung. then after like 10 seconds it turns off. it does that for a few times and then it just goes in a black screen. the model number is YP-G7OC/NAW. when i plug it in to charge it goes on and off two times and then off. if it has low battery it just shows the sign. as for the rom i don't think i have any. i just rooted it using superoneclick. if it goes to recovery mode what do i do?
thanks!
(you got me really fired up when i saw the recovery menu!)
If you can get to recovery menu, try a factory reset, and clear cache. I am not sure if there is a recovery rom for your device, you should check samfirmware.com
tried both of them...no luck. and i couldn't find a recovery rom on samfrimware.com.
Your device has capacitive or mechanical home button?
it has a capacitive home button...the usa version
shahrukhraza said:
it has a capacitive home button...the usa version
Click to expand...
Click to collapse
The phone boots in recovery?
If so, I can investigate a little more what's happening.
I'll try to post a return-to-stock image soon... The problem is that mine is cluttered with crap that the zergRush exploit added (it insisted on installing busybox instead of just rooting...)
(I'm not sure, but I think someone else already posted a stock zImage and system image...)
Here is the post about fixing capacitive buttons. A quick search of forum should have found it.
http://forum.xda-developers.com/showthread.php?t=1421797
Sent from my YP-G70 using Tapatalk
nooooooo!!! you guys have all got it wrong. first of all it doesnt boot in recovery. the only way to get in recovery mode is when it shows the battery sign i hold "up volume"+ power button.and the capaciative button is completely fine. im just stuck in a bootloop (i think) and it has nothing to do with a broken capacitive button! i will try to post a video today to show you guys exactly whats happening.
i kind of had the same problem, one time i thought i had entropy's kernel on and i had CWM well i didn't but i still thought i had so i tried rebooting into recovery using the terminal:
su
reboot recovery
then i turned off and went to this weird recovery menu it had four options, reboot system, apply update from SD card, wipe data partition, and power off and it had a ton of red letters and words saying like, couldn't access data partition or cache partition and couldn't access /data/media, or system, and then i just turned it off because i wouldn't let me choose an option, and then i got stuck in a loop but not during when it says SAMSUNG mine happened during the animation music part that look like fireworks and then SAMSUNG would light up blue then go through it again and 2 more times then go black and i tried flashing the US stock ROM in download mode but still would go through the loop and it doesn't even charge so i got nothing
so did you somehow fix yours? and i never got a recovery menu that showed something about shut down.:confused
Before brick
xxxxxxxxxxxxxxxxx
wait....are you asking me those questions? just to tell you im no developer or something. im just a 12 year old who has his galaxy player stuck in a boot loop. you have to make another thread if you have a problem.
sorry!
Ok. : ) You got it wrong. No problem. His case is different from mine. Just wanted to use her Brick in case. Nothing more. good luck.
I resolve my doubts alone. Nothing that Google does not respond. haha
At least before brick.
ok. let me ask google too xD
anyways..anyone have any idea of how to fix this boot loop?
im trying to do the Linux thing by running the ressurector ans the VM windows the forum is posted under development called hard brick recovery for galaxy 5.0
ok.(i have no idea what you are saying...just saying!)

[Q] Stuck in weird bootloop.

So I've been using Kang's ICS preview for about a week, and I really liked it, except from some bugs such as freezing after not using it for a few hours.
Today when I got back from school, (not used the tab for 7 hours) I tried to turn it on but I couldnt get past the loading screen, so I turned it off by holding the power button for a few secs.
Now I just cant get it to load up normaly, its just goes to the bootscreen, stucks, then its impossible to turn it off.
I tried going in to CWM and wipe data/cache but that freezes too.
Is there any other way to wipe it and install another rom like Overcome?
Mine did this as well. It would hit the Samsung loading screen and never go any further. I basically had to unroot it and take it back to stock via ODIN. Hopefully this works for you.
Hit up this link and download the big blue link at the top labeled DOWNLOAD:
http://forum.xda-developers.com/showthread.php?t=1474971&highlight=odin
Follow the directions to get into the Download Mode, then jump down the unrooting part.
After its done with the download it will reboot automatically. Soon as it does this make the tablet go into Recovery Mode. It should go through a script and reboot automaticly. Again don't let it boot normally, make it go into Recovery Mode. I think it took a few times for me and then it eventually went into Recovery. I then did a factory reset and rebooted. Now I have an unrooted Samsung firmware. Back to scratch though, but fine with me! I was getting worried I wouldn't be able to get it back.
Oh...and this process will wipe your internal memory as well.

[Q] vibrant boot issue

I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
[email protected] said:
I have a Vibrant that I believe may have hard bricked when odin crashed/froze during last 10% of install and now the phone wont turn on and boot, go into download mode by means of jig, pressing both vol up and down at the same time as the power button or other various jump start methods, as well as wont go into recovery. I've just ordered a new break out jig and I'm curious to see if it will work for this or like my other jig be ineffective. The Vibrant came to me disassembled, and immediately upon reassembly I experienced booting issues with it. Sometimes it would boot up revealing the home screen before it would shut off and others it would barely flash the first splash before shut off. I'd see similar behavior when I attempted to boot to recovery, but then when ever the phone was in download mode it would stay on. I flashed it several times with odin but it would never really stick. The last couple attempts had shown promise when it would start making it further into the boot process before the attempt when odin froze during the install of the rom and I can only think that now it's hard bricked. Now that my friend has brought me his Fascinate that is showing similar characteristics within his phone, I'm hoping for some help with understanding whats causing these problems. His phone wont boot unless it is plugged in, however it will continue to function after unplugging the charger from phone. That just makes me think of the Vibrant and how it would only stay on in download mode, but the 2 situations could be completely unrelated in the cause of the boot issues, if you can please help.
Click to expand...
Click to collapse
I have Jtag solve for Hard brick phone
Please PM me or check out at my signature.

black screen after reboot from recovery mode

Hi,
my galaxy k zoom was booting in loop. After 3 reboots, the recovery mode menu appeared. I chosed to reboot the device. A few error messages appeared in red but I had the time to read. And since that moment, I've a blank screen. I'm unable to access the recovery mode. The combination of the keys doesn't do anything. Any idea anybody ? If only a can have a chance to go back to the recovery mode, I will know what to do next. But I'm stucked
Thanks in advance,
jc
maybe can flash firmware ?
Thanks for your response. In fact, I let this S3 aside for a few weeks and when I came back, I was able to log in again. This happened to me few months ago with this device. That's strange. Maybe a timeout somewhere or something happened when the battery was empty ?
Cheers

Categories

Resources