Long story short, a friend of mine tried to root his Samsung Vibrant while drunk and failed. Well he managed to try and fix it with Odin and somehow managed to install some AT&T software on it. Problem is, now it's stuck in an infinite black loop unless you hold Vol Down+Home+Power. It then comes to a black screen displaying red numbers. I've tried to fix it with Odin v3 but I never gets past the first step. I'm accepting all help and advice.
Confused on how people can screw up rooting this phone. It is literally just one click to root it. What process did you guys use?
Lethal_NFS said:
Confused on how people can screw up rooting this phone. It is literally just one click to root it. What process did you guys use?
Click to expand...
Click to collapse
Yeah I know..he apprently Google searched a method instead using XDA.
I don't know what he used to attempt to hack it but he tried using Odin to fix it but with Samsung Captivate files..
creid2352 said:
I don't know what he used to attempt to hack it but he tried using Odin to fix it but with Samsung Captivate files..
Click to expand...
Click to collapse
wrong section. this goes in q&a...if u can link what he flashed with odin there might be a recovery method. the red letters that pop up say kernel panic? if he flashed the captivate boot.bin he might be ****ed
Go here
http://forum.cyanogenmod.com/topic/6998-howto-recover-from-a-soft-brick-on-your-vibrant/
If that dont work your throw your phone at the wall and get it replaced by tmo.
creid2352 said:
I don't know what he used to attempt to hack it but he tried using Odin to fix it but with Samsung Captivate files..
Click to expand...
Click to collapse
Your buddy used the one-click odin for the captivate. I've helped a friend restore his captivate with that, its nice, but model specific for sure. Your only hope is that the bootloader of the captivate rom allows you to somehow boot the vibrant to dl mode. The following method works on my vibrant and my friends captivate.
Phone off, battery sim and sd cards out, have odin loaded with the pit and tar files for the vibrant.
Plug in usb from pc to phone.
Holding down both volume up and down only, and insert the battery.
This will hopefully get you into download mode, and you can flash the correct rom with the right odin, not the one click.
Hope this helps. This boot method works on both phones to get dl mode. Keeping my fingers crossed for ya.
Ginger Clone's of the World Unite! Via the XDA App
I would try using the froyo that does not brick method. That has got me out of some tough spots. Also use newest version of odin and a 32 bit operating system. Never really bricked if you can get into dl mode
And if it fails keep trying, odin is finicky.
Sent from my SGH-T959 using XDA App
I'm pretty sure it's a Captivate, and NOT a Vibrant. So, stop throwing Vibrant specific fixes at the phone.
So the ROMs that are available are Different. On that note, I have zero useful specifics to share. Sorry, but Good Luck.
a4 moda said:
I'm pretty sure it's a Captivate, and NOT a Vibrant. So, stop throwing Vibrant specific fixes at the phone.
So the ROMs that are available are Different. On that note, I have zero useful specifics to share. Sorry, but Good Luck.
Click to expand...
Click to collapse
op said it was a samsung vibrant that got flashed with a captivate firmware. read....
a4 moda said:
I'm pretty sure it's a Captivate, and NOT a Vibrant. So, stop throwing Vibrant specific fixes at the phone.
So the ROMs that are available are Different. On that note, I have zero useful specifics to share. Sorry, but Good Luck.
Click to expand...
Click to collapse
If it walks like a duck (using odin to flash vibrant specific roms), talks like a duck (I've seen same screen on my vibrant today actually), and op says its a duck (he literally says "samsung vibrant"), then why YELL at people for offering solutions to fix a duck?
Sent from my SGH-T959 using XDA App
New Odin
Does anyone have a link for the new one?
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!
This is as far Odin v1.3 gets..
creid2352 said:
Does anyone have a link for the new one?
Code:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!
This is as far Odin v1.3 gets..
Click to expand...
Click to collapse
Try it again. Close odin, disconnect phone and pull battery. Odin can be tempermental. Reopen odin, reload the files, boot phone to dl mode, and try to hit the start button in odin within about 20 seconds of the com port being recognized. Try to select repartition in this case, so odin knows to set the partitions. If all else fails, search for and use the froyo that doesn't brick method mentioned earlier. If you can boot to dl mode, there is still hope.
Ginger Clone's of the World Unite! Via the XDA App
Got it up and running again, thanks a lot guys or girls. This post can be deleted now.
Good to know, glad you got her runnin. Now tell your buddy, no more drunk flashing, lol.
Ginger Clone's of the World Unite! Via the XDA App
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
Related
Alright, I'll be brief with this...
Have stock Vibrant, OTA killed it, tried master reset, no help, tried Odin, FAILS on factoryfs.rfs, tried 4 other downloads of Odin stock rom, same problem. No SD card, no sim, nothing but phone, battery and usb.
Won't boot, won't turn on, just maybe the backlight turns on to no screen. Figured out how to get it into download mode still, but thats the only thing that I can do.
Now, is there a different ROM that I could use thats had more success? Am I doing something simple wrong? Forgetting something? Is there any help out there for this? Or is my phone just screwed?
Someone said removing the battery for about 1 or 2 minutes works
Did you try to odin the origonal stock firmware first?
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
It's been out for about 2 hours, so I'll give it a try like that....
No dice =/
Oh, didn't mention earlier, also tried the download with and without the battery, still fails at the same point.
fit333 said:
Did you try to odin the origonal stock firmware first?
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Click to expand...
Click to collapse
Yeah, that's all I've been wanting to put back on, but that's the one that keeps failing on me. I', wondering if another Odin ROM might work
And I don't even get the screen anymore that is your avitar fit333
Mage42384 said:
Yeah, that's all I've been wanting to put back on, but that's the one that keeps failing on me. I', wondering if another Odin ROM might work
Click to expand...
Click to collapse
If you followed instructions it WILL flash after a posible fail or two
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Mage42384 said:
And I don't even get the screen anymore that is your avitar fit333
Click to expand...
Click to collapse
Call it nostagia.. only the og rom did that, means your almost there. Lol
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
fit333 said:
If you followed instructions it WILL flash after a posible fail or two
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Click to expand...
Click to collapse
I'll go step by step with what I'm doing, just to make sure.
1-load odin
2-plug usb into phone (no battery yet)
3-hold vol up/down, insert battery (only way i can get into dl mode now)
4-select pit and tar(phone) files in odin, make sure only reboot and time are checked
5-press start and be patient, lol.
Here is my report in Odin
<ID:0/008> File analysis..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.rfs
<ID:0/008> modem.bin
<ID:0/008> factoryfs.rfs
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
fit333 said:
Call it nostagia.. only the og rom did that, means your almost there. Lol
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
Click to expand...
Click to collapse
Hahaha, I wish. That was what I had last night, no screen since.
Oh, and I've tried the update probably 20 times today in hopes, same thing everytime
Have you got odin 1.3 and have you tried eugenes froyo that dosnt brick, its worked magic for me in the past.
Proudly pumped from my vibrating vibrant using the ubiquitous XDA App
1.3 wouldn't work or recognize my phone at all, just using v1.00 that everybody else has been saying to use for it. I'll hunt down 1.3 right now and give that a shot.
Same thing... I'll try eugenes as soon as I get home and on a good connection. Would you be able to post a quick link to the thread with the one that didn't brick for you? Thanks (^_^)
Stick a incense stick beside it, and pray for miracle.
question, did you drop in water before? friend beside me is talking about taking it apart and putting it back together might work. we both fix computers hardware and software debuging.
problems like this, might also be hardware faultyness...just hope it is not that issue...
ekoandrew said:
Stick a incense stick beside it, and pray for miracle.
question, did you drop in water before? friend beside me is talking about taking it apart and putting it back together might work. we both fix computers hardware and software debuging.
problems like this, might also be hardware faultyness...just hope it is not that issue...
Click to expand...
Click to collapse
No water damage, and I've saved phones with it before. Using my storm2 now thanks to being able to pull things apart, lol.
But I was hoping it wouldn't come back as faulty hardware, but it's seeming that way to me =( Of course, I'm already waiting on tmobile for my replacement......I'm 31 on the list, lol, who knows when I'll get that phone...
What ROM are you trying to flash? Have you ever used it before? Could the file be corrupt?
mmas0n said:
What ROM are you trying to flash? Have you ever used it before? Could the file be corrupt?
Click to expand...
Click to collapse
I've downloaded from 5 different sources (at least) the stock 2.1 update 1 that's going around and seems to be working for everybody. I can't find any other rom that I can use with Odin, and I can't get into recovery to try adb (even though when I could, it wouldn't let me overwrite files on the phone)
Is there any other program I could use that utilizes download mode and standard dumps that are posted all over the place? Or is there a way to take those dumps and use them with Odin?
My wife's phone bricked on the OTA
I used this:
http://forum.xda-developers.com/showthread.php?t=803492
What seems different is the first flash (PART 1) with Original.tar I click repartition. That worked fine. Then in part two I didn't click repartition (as stated).
The download in the thread should have it all - including odin.
Also
http://ip208-100-42-21.static.xda-developers.com/showpost.php?p=8734955&postcount=4
SINCE APPARENTLY I WASN'T CLEAR ENOUGH, IF YOU LIVE IN THE UNITED STATES AND ARE ON THE CARRIER VERIZON, USING A GALAXY S FASCINATE I500 DO NOT INSTALL THIS. YOU WILL REGRET IT. END OF DISCUSSION.
I think this is pretty straightforward, thanks to a lovely line dropped to me, we have a leak on our hands It's already running on a few phones at this point it seems, and sounds like a fairly stable release! Currently working on rooting the ***** but it should take me long Energy drink and a couple hours to go.
http://www.megaupload.com/?d=C3DQ1LZF
ROOT INSTRUCTIONS!
Once you have the 2.2 leak installed (It'll probably take a few tries in odin. If odin does NOT recognize the phone, try a different USB cable/port, my old milestone cable didn't work, my actual samsung one did) install the Cyanogen initial kernel from my other rom port using odin (AND the included pit file, natch) and THEN install the update.zip included (Same one as before! yay )
SU works, busybox is included, root is perfect.
God I love friday nights.
Enjoy.
adb push rage.bin and all that good stuff.
Am I the only one with this issue?
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Leave CS..
<ID:0/003> Enter CS for MD5..
<ID:0/003> Leave CS..
It just stays at Leave CS.. and doesn't budge. This is pissing me off >_<
Took a couple flash attempts.
SORRY IM LATE!
Rooted
SIMPLE process too, requires odin because of 3e recovery.
Files and instructions in first post!
Wow this is great for you guys. Can't believe VZW didn't get it first
wizang said:
Wow this is great for you guys. Can't believe VZW didn't get it first
Click to expand...
Click to collapse
Actually, i've been giggling quietly to myself about it all night.
When I was in toronto (The reason this wasn't out at 3pm) I saw someone with a VZW fascinate waiting for a train and almost laughed at them.
Poor guy.
0mega1 said:
Actually, i've been giggling quietly to myself about it all night.
When I was in toronto (The reason this wasn't out at 3pm) I saw someone with a VZW fascinate waiting for a train and almost laughed at them.
Poor guy.
Click to expand...
Click to collapse
Are you really gonna stoop so low as to gloat? Really?
Sent from my ADR6300 using XDA App
Well you guys are on gsm, right? That's probably why you guys got it first. I don't really mind the wait peraonally, and all these leaks make me hopeful. But I wonder why the Telus version is even called Fascinate if it's so different from the other ones.
0mega1 said:
Actually, i've been giggling quietly to myself about it all night.
When I was in toronto (The reason this wasn't out at 3pm) I saw someone with a VZW fascinate waiting for a train and almost laughed at them.
Poor guy.
Click to expand...
Click to collapse
and congratulations, you guys have a phone so popular it doesnt even have its own forum...good job
adrynalyne said:
Are you really gonna stoop so low as to gloat? Really?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Actually, I was trying to inject a little humor.
I can seriously empathize with having a ****ty upgrade path and no carrier support
(I owned a milestone, Droid with an e-fuse, also, a motorola product. )
2.2 first try!!!
Thank you so much OMEGA!!!
Odin is a breeze to use...I don't know why I was so afraid. Downloaded as per your link, then extracted, and placed the .pit, rom and CSC files in the right spot, put the phone into download mode, hit 'start' et viola! 2.2!!!
Now on to root...i'm guessing the kernel goes where the rom should go and the pit file goes exactly where is says...
Then boot into recovery apply: update.zip???
So here's where i'm at so far:
2.2 with ODIN = YES!
Changed kernel (and pit) to cyangen from stock 2.2 with ODIN = YES!
ROOT = NO!
I'm trying to root the phone, but I have some questions if you don't mind OMEGA...
- When I boot into recovery mode, it takes me straight to clockwork recovery...I can't get into standard recovery.
- Fine, i placed the .zip from the OP in this thread in the root of the SD card and renamed it to "update.zip" (Don't worry, i made sure it's not update.zip.zip b
- I choose install .zip from sd card (choose.zip) and it does not work, just hangs
- I also tried apply sdcard:update.zip I get an error message E:can't mount SDCARD:update.zip installation aborted.
Can you help??
Edit: Never mind, problem fixed, thanks!! But one more noob question: Can I install the root .zip just from stock 2.2 or do I need the cyanogen installed first?
I'm not rooted yet. still stock 2.2; I went back to the stock telus rom, reflashed it over the cyangen kernel, as I couldn't get root and wasnt crazy about the home button acting like back..but i digress....
Can you install apk's with andexplorer or any file brower? I tried to install genie widget and HTC_IME keyboard and they both keep FC'ing.. Place the apk in the sd card and choose 'install'.
I want to get root so I can remove some bloat and install apk's with root explorer but will patiently wait for OMEGA to chime in..
Thanks!
nitsuj17 said:
and congratulations, you guys have a phone so popular it doesnt even have its own forum...good job
Click to expand...
Click to collapse
Ever heard of sarcasm???
Have you???
This is nice
Maybe I did something wrong but I have no external sd card at all after installing this its like its not there.....other than that BT hid for my mini keyboard is finally working with psx4droid thru to my tv......FINALLY! Thanks to everyone who got this going..It is way faster online and finally loads full flash sites but I could not get at user string or user agent to change to desktop instead of android even after about:debug and looking for it...first time I have seen that, not that it matters I use Dolphin HD.
adrynalyne said:
Have you???
Click to expand...
Click to collapse
Lol good one...so take a look at my post can you help me out with my root problem?
Are we able to use stock android yet? or is it just limited to TouchWiz still?
Apparently for my phone, when I hold Home + Volume UP + Power, it still gives me the Boot Screen with the triangle.
IT DOES NOT ENTER INTO RECOVERY MODE.
Any suggestion?
try the manover after removing(and putting back offcourse) the battery for a copple of minutes
you mean swapping the battery out and back in for a few times?
keatsan said:
you mean swapping the battery out and back in for a few times?
Click to expand...
Click to collapse
Once is enough but leave it out for a min or two .
jje
tried. didnt work.
I even try to flash with other Roms, but yield no result at all either.
<ID:0/014> Added!!
<ID:0/014> Odin v.3 engine (ID:14)..
<ID:0/014> File analysis..
<ID:0/014> SetupConnection..
<ID:0/014> Initialzation..
<ID:0/014> Get PIT for mapping..
<ID:0/014> Firmware update start..
<ID:0/014> boot.bin
<ID:0/014> NAND Write Start!!
<ID:0/014>
<ID:0/014> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Did you by any chance tick "repartition" in Odin?
If you have, its too late and will need to be returned to samsung for jtag.
If you haven't yet, DO NOT
Sent from my GT-I9100 using xda premium
I'm VERY sure I DID not tick that option.
Are u able to go to download mode? if yes then flash original rom?
Sent from my GT-I9100 using XDA App
Can you now at least boot rom, and if so can you enter cwm Recovery via the advanced power menu or CWM app?
Edit: you haven't given any info in your first post what you were doing or had done prior to the problem? Only what you did after. Could be beneficial. Also what was/is your current config?
Sent from my GT-I9100 using xda premium
tecknil said:
Are u able to go to download mode? if yes then flash original rom?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Yes I can enter download mode, but I couldn't flash any original ROM somehow. Odin always shows fail like the earlier post I've posted.
UpInTheAir said:
Can you now at least boot rom, and if so can you enter cwm Recovery via the advanced power menu or CWM app?
Edit: you haven't given any info in your first post what you were doing or had done prior to the problem? Only what you did after. Could be beneficial. Also what was/is your current config?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
If I'm not mistaken, I try superoneclick. And then it hangs there. From there onwards I couldn't enter Recovery mode. Worst part is, I don't even remember my kernel version or what type of firmware. All I know that it's 2.3.4 android stock.
Maybe ask in the superoneclick thread. Hopefully you'll get more specific answers to your problem. Best of luck.
Sent from my GT-I9100 using xda premium
As you can still get into DL Mode (but can't flash a ROM), how about trying one of Chainfire's rooted modem ?
Can be flashed via Odin & make sure all KIES is closed, as well as anything in PC Task Manager
This will automatically root your device and install the CWM Recovery (not ROM Manager compatible),............... Then you may be able to access Recovery to factory reset / wipe cache & dalvik and try rebooting (which can take up to 5-10mins).
If still no luck, back into CWM Recovery and try flash a custom ROM of your choice (flashable zip, do not extract) straight from the sdcard. Cognition is highly recommended.
As you don't know the original baseband #, not sure which to try, but the first goal would to be able to boot into CWM (since you can't or having trouble flashing with Odin)
Sorry, no more ideas, but if you decide to try, follow his instructions exactly.
I've tried the CF kernels. I've downloaded every single Kernel and flash with it. Still no luck.
But I've send my phone to Samsung Center. Even the technician is puzzled. He'll look into the matter of my phone and solve it in a day time.
I've post updates here once I get back my phone.
You going to have to pay or did you clear rom counter and reset to stock .
jje
Well, I couldn't do anything since I cannot even access to erase any counter number.
Hopefully they STILL don't charge me.
Apparently they called me today, saying my phone would take another day or two.
JJ means the usb jig. Power off phone, insert, boots automatically into DL mode resetting custom counter and removing the warning triangle.
As you don't seem to really know about it, you probably haven't? After reset, you could have just played dumb, claiming it got screwed during a Kies update. Never mind, too late now.
Sent from my GT-I9100 using xda premium
Nope. I didn't bought the USB JIG and I should get one soon. Haha.
OH well, too late for now.
keatsan said:
Nope. I didn't bought the USB JIG and I should get one soon. Haha.
OH well, too late for now.
Click to expand...
Click to collapse
It does seem to be pot luck get the right service guy and he will ignore custom .
jje
I hope he does ignore the custom issue. All the best to me.
I shall post the update once I get back my phone
UPDATE:
I've sent the phone to service on the 26 Sept. And they told me that it'll be ready by 2th Octo. According to the technician, they're waiting for a PART to arrive to be replace. No info was given on what part.
WOW, I didn't know hardware was involved in this case. It's rather rare to me.
UPDATE 2 :
F**KED.
My SGS2 is the i9100G model.
No wonder it stuck at Boot Screen S with Yellow triangle.
FML.
I tried to update my galaxy tab to 3.2 version using the software update menu of the tab (did not use odin or recovery manager). Before, I was using the Starburst ROM.
The updating process did not finish and now when I try to turn on my tab it does not do anything and when I try to charge it it does not display the battery charging icon.
Anything I can do to fix it?
Edit: Managed to display the samsung logo and then blank screen (but the screen is on) and when connected to PC Odin discovers it. Anything I should try here?
If the device is recognized in odin then attempt to flash a stock image.
iOSh8er said:
If the device is recognized in odin then attempt to flash a stock image.
Click to expand...
Click to collapse
How do I go about doing that? Any tutorials? I have used odin to root but not sure on how to go about doing a full flash for my P7510
Originally Posted by iOSh8er
If the device is recognized in odin then attempt to flash a stock image.
Click to expand...
Click to collapse
How do I go about doing that? Any tutorials? I have used odin to root but not sure on how to go about doing a full flash for my P7510
Click to expand...
Click to collapse
Just go to www.samfirmware.com. In the tablet section you will find all the firmwares and tutorials. You will have to register though.
sent from my CM7 nokia 3210
Or search around this forum.
I've answered this question a few times very recently.
One of the threads on this topic should be stickied.
Just want to make everything clear before I go on. My screen is blank (but still on). I am not in real recovery mode but odin detects my tab (possibly because its stuck on installation of 3.2). Is it safe to go on? I do not care about the data on the tab but I do care about its functionality
maximos86 said:
Just want to make everything clear before I go on. My screen is blank (but still on). I am not in real recovery mode but odin detects my tab (possibly because its stuck on installation of 3.2). Is it safe to go on? I do not care about the data on the tab but I do care about its functionality
Click to expand...
Click to collapse
Can you get into download mode?
If so follow the steps here http://forum.xda-developers.com/showthread.php?t=1171089 to return to stock.
**Edit**
Pm me and I'll walk you through it on gtalk.
iOSh8er said:
Can you get into download mode?
If so follow the steps here http://forum.xda-developers.com/showthread.php?t=1171089 to return to stock.
**Edit**
Pm me and I'll walk you through it on gtalk.
Click to expand...
Click to collapse
Afraid I cant go to download mode. Thats my main issue.
Cannot flash from ODIN. This is the output.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
And then does nothing.
maximos86 said:
Cannot flash from ODIN. This is the output.
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
And then does nothing.
Click to expand...
Click to collapse
pm sent... 10char
maximos86 said:
I tried to update my galaxy tab to 3.2 version using the software update menu of the tab (did not use odin or recovery manager). Before, I was using the Starburst ROM.
The updating process did not finish and now when I try to turn on my tab it does not do anything and when I try to charge it it does not display the battery charging icon.
Anything I can do to fix it?
Edit: Managed to display the samsung logo and then blank screen (but the screen is on) and when connected to PC Odin discovers it. Anything I should try here?
Click to expand...
Click to collapse
Just wondering, why would you update to the official 3.2 update after running a custom rom? You should always wait for the rom to update with the latest otherwise.
maximos86 said:
I tried to update my galaxy tab to 3.2 version using the software update menu of the tab (did not use odin or recovery manager). Before, I was using the Starburst ROM.
The updating process did not finish and now when I try to turn on my tab it does not do anything and when I try to charge it it does not display the battery charging icon.
Anything I can do to fix it?
Edit: Managed to display the samsung logo and then blank screen (but the screen is on) and when connected to PC Odin discovers it. Anything I should try here?
Click to expand...
Click to collapse
Have you tried a reset by pressing the on/off button and the left side of the volume button for a few seconds thats how I did mine when mine froze trying to use the 3.2 update.
finally managed to reboot into recovery and flash a rom everything is fixed now. Thank you everyone
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to Q&A
iOSh8er said:
If the device is recognized in odin then attempt to flash a stock image.
Click to expand...
Click to collapse
my computer will recognize my tab in odin, but which file do i use? i am pretty new to this and am a quick learner... any help?
Hey all. There's a lot knowledgeable folks around here, so I thought I'd see if I can get some help on my problem.
I've got a Galaxy Tab 10.1 Wifi (GT-P7510, non-branded, UEKME), that I rooted about two months ago, using the instructions found on the Android Forums (can't post a link, but ti's the basic easy way to root, using Odin3). Not a superuser, but wanted to be able to back up everything. Seemed easy enough and the rooting went fine.
Haven't done anything else to it, aside from installing a few run of the mill apps. It did auto-update a couple of times.
Was working fine, now it just got stuck on this screen with a message:
Code:
ODIN3 Download Mode
(Protocol v2.1)
Reason: No Kernal
Secure Mode: Secure
Check Signature: Check
Custom Binary Download: No (0 counts)
Custom Binary: Samsung Official
Waitting USB Cable...
Downloading...
Do not turn off target!!
Apparently, it went to this screen while I was away. I didn't see it until I picked it up and there it was. It comes to this screen after the Samsung title screen (not the animation) and a VERY quick screen with some red writing (goes by too fast to see what it says).
I tried to follow the original instructions again. Put the tab in download mode (power + volume down), open Odin3, select the md5, and hit start. Get a FAIL with this message:
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery-cwm_4.0.0.4-sam-tab-10.1.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The screen on the tab updates with this:
Code:
WritePArtition: Error to NvStorMgrFileWrite![err:0x30000]
DownloadPartition_odin: Error to WritePartition![err:0x30000]
Tegra_Nand_Write: Error to DownloadPartition_odin![err:0x30000]
That's as far as I've gotten. I noticed the Re-Partition option is not checked in Odin3, and the errors on the tab have to do with partitions... but didn't want to do that if I could eff it up even more.
I'm also wondering if one of the auto-updates didn't muck up the works. Maybe messed with my bootloader? Again, didn't want to go doing dangerous things without some reassurance. Also, I can't get into recovery mode; it just kinda flashes when I hit the button and stays on the option screen for download/recovery.
Any direction on how to proceed?
Any advice would be so great. It's been like this for about a week and I can't find any help. Thanks everyone.
TL;DR: Stuck in Download Mode, get errors on re-root.
This helped me and I've seen it help many others too in similar situations. Since you're stuck in download mode already it might need to be adjusted and followed from somewhere other than the beginning.
Goto http://www.teamovercome.net/p7500/?page_id=5
Towards the bottom of the guide There is a section called Restocking yer system.
Follow that on down.
Make sure you use the files for you device (7500 or 7510).
Make sure you triple check that you follow everything as suggested. The most common one I see missed is the last step of doing a Wipe data/factory reset.
Let us know how it goes, as this keeps us trying to help when we know we're successful.
Sent from my GT-P7510 using XDA Premium HD app
You have an incomplete bootsector the bootloader is broken but ofcourse your recovery is safe. Just flash a stock firmware on top of it, or flash CWM. You don't have to worry about the options being checked as Odin 1.83 onwards fixes this issue.
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Is there any other way to flash my firmware and/or repair my bootsector/bootloader?
Thanks for your help.
stusic said:
Well, I was really hopeful when I read your response and read through the guide, but alas, I still got the FAIL when running Odin.
Aside from the rom, what else is there? I know of bootloaders, but not their function or how they work, and undersstand that loading the incorrect one (or incorrectly) can really make my tab a brick.
Are there any other suggestions?
Thanks for your help so far, maybe we can get this thing working. It's a shame - I've only had it for a couple of months...
Click to expand...
Click to collapse
If you followed what I posted, and triple checked every step and check box in the guide was exactly what you did, then I'm lost for other suggestions. Misledz is on a different time than here, so you can either try my process again, if that's what you used, making sure you do evrything as said in the restocking yer system guide on down or wait for more help.
Yeah, I was hoping because it was a really well written guide with links to the correct files right there that I'd have some luck. The directions are pretty straightforward, so I don't think I missed anything, but I can certainly try again.
Thanks, I'll update in a bit.
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
stusic said:
I think I'm going to have to wait to see if Misledz has any other suggestions - I just tried it again and got the same fail.
Click to expand...
Click to collapse
Sorry that sucks.
Hope Misledz or someone comes along for you.
Best of luck.
Edit: Looking at the Odin repartition error makes me think it may be a full hardware failure issue. But there is still hope with the right files or method for it to be fixed.
I can't find it, but there was another thread here with the same "Reason: No Kernal" error and I think it turned out to be a hardware failure.
Sorry well yeah I've been on offset timezone's and I tend to check this section regularly as I hope to learn more about the tablet In hopes I can get some development done on it.
In the sense I'll assure you that you can't really brick the tablet as they are somewhat hard to brick via software, unless you install a firmware that isn't compatible (Like a 7500 on a 7510) or like wipe the bootloader. Put it this way anything done in download mode is safe.
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Misledz said:
Now to your query. It can't be a hardware issue because as you can see the tablet itself boots perfectly to Odin.
Click to expand...
Click to collapse
That's reassuring.
Misledz said:
I would suggest skipping the v4 of CWM and flash the v5
[http://www.mediafire.com/?6c5tdmds927npdv]
and
http://www.teamovercome.net/p7500/wp-content/plugins/download-monitor/download.php?id=15
Normally errors like this occur only because of cases like ramdisk being different. One is the 5.1 and the other is the 5.5 version, I suggest it's best to try both. I feel you will have better luck testing both. No worries they are both safe and the 4.0.4 has some issues as far as some tablet's are concerned.
Click to expand...
Click to collapse
I notice the second file is in a p7500 directory. I'm guessing this is an all-encompassing directory with p7500 and 7510 files?
EDIT: I see that the file is for all versions (75xx). Thanks.
I'm at work now, but I'll try it when I get home and give an update.
Thanks for taking the time to help me out.
*fingers crossed*
Dammit. No luck.
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
brieuwers said:
Did you already tried flashing with a pit file?
Flash with pit will rebuild your partitions.
When loading pit file repartition will automaticaly be select.
Do not repartion without pit file or your device will become abrick.
After flash with pit file you will see a lot of errors this is normal
And will be fixed after factory reset.
Good luck.
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
If you check out his screen shot posted above it shows he used a pit file at least in one attempt
He's still having issues so your help with this would be and is highly needed and appreciated.
Sent from my GT-P7510 using XDA Premium HD app
I've used the pit file and tar file from the guide that Benzoman directed me to. I also tried using the updated CWMs that were suggested (although a pit file wasn't included).
I had installed the windows drivers a while back, but just installed the Kies. Interestingly, after that, I tried flashing again and, although it still failed, it took a lot longer (as opposed to almost instantly). Almost thought I had it for a second...
Am I right in thinking that I can use the pit file from the guide and the tar file from CWM together?
Slightly off-topic; what's the purpose of flashing a bootloader? That's one thing I haven't tried yet.
Thank you for your continued help. I would have lost all hope by now if it weren't for you and this forum.
So is it all good? I don't tend to like leaving people who need help Especially when it's also educational for me.
Flashing a bootloader wouldn't be advisable cause it may really brick the tab.
You don't really need to pit file as it is used for repartioning, flashing just the PDA is good enough
Misledz said:
So is it all good?
Click to expand...
Click to collapse
No, it's still stuck. It seems like any pit file I try doesn't work, which was why I was asking about the bootloaders (I know it's dangerous, but for all intents and purposes, it's already bricked).
I don't know what else to do; I was hoping the updated CWM would help, but it runs into the same problem the other pda files have. I'd be more than happy to try any other suggestions you may have.
Thanks again.
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
stusic said:
I don't know if it's any help, but I was able to capture the really quick flash of red text as it boots. See attachment.
Click to expand...
Click to collapse
Sorry over my head, but hopefully Someone will look at the error and know what's going on.
Sent from my GT-P7510 using XDA Premium HD app