Database Users

[HELP] Is my vibrant completely bricked?

Not sure if this is the right section or not, but I felt I would get the best response from this forum.
OK.. so I was running euegene's Vibrant6 ROM, but I was having trouble getting any of the lagfixes to work correctly. So I decided to follow the steps outlined in this post: ((apparently I cannot post links))To flash the stock rom and so on. I had never used odin before, but a quick google search found me some directions and it seemed simple enough. So I try to flash with odin and I kept getting stuck at "File analysis.." After disconnecting my phone and trying to restart it, the phone would just go to the screen with the phone + warning sign + a computer. I was able to get back in to download mode from there. Still could not progress past the file analysis. I tried all of the tips outlined in this thread(apparently I cannot post links)) and after reading that last post, I was able to uninstall my previously existing drivers from my moto cliq.
Finally, odin progressed passed the file analysis and was flashing the filesystem.rfs file. I had a nice blue progress bar on the downloading screen, I thought everything was going to be fine. Then my phone went to a blank Blue Screen. The progress bar in odin seemed stalled at about 25%. As this was my first time using odin, I had no idea if this was normal. I let it sit this way for a good 10 - 15 min. No change. At this point I started getting concerned and thinking this can't be normal. I gave it a few more minutes and still no change. Odin was still just sitting there, right about 25% on filesystem.rfs and blank blue screen on the phone. So then I unplugged the phone, pulled the battery and put it back in, expecting that phone - error sign - computer screen again and hoping to reboot the pc and try again. No such luck.
Now my phone will do nothing. Plugged in to the pc with odin running no response whatsoever from the phone. Plugged in to the wall, no response. It's like I'm trying to turn it on without the battery in. I fear the worst and I'm 99.9% sure you guys will just confirm this as I can't get in to ANYTHING. What I would really like to know though is where I went wrong. Is it really normal for an Odin flash to take that long and to sit at that point?
EDIT: Quick follow-up question, and this is probably going to sound completely stupid, but I don't really care: is the "internal sd" an actual micro sd card that can be accessed at all, so that I can at least get my pictures/videos and such off of if I have to get a new vibrant?

this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App

merrifield69 said:
this should be posted in the q/a section
I'm no expert, and I'm not sure what went wrong, but you can try to unplug phone from the USB charger, unplug the battery, put battery back in, hold volume up + volume down and plug back into usb charger (connected to computer) to see if you get a responce from the phone.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.

skoozi said:
Thank you for the quick response. Sorry about the wrong section, wasn't really sure this would fit best. Tried what you said and IT WORKED first try. I'm now in download mode. NOW, I would like to retry the flash with odin, but I also need to know if I'm doing something wrong, or if this was a fluke? Should odin sit at that point (25% flashing filesystem.rfs) for that long with a blue screen on the phone? I was under the impression it should be a pretty fluid and somewhat quick process.
Click to expand...
Click to collapse
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?

cdw9800 said:
when i flashed using odin i didnt seen any blue screen only the download screen wha are ou trying to flash are you sure its for the vibrant?
Click to expand...
Click to collapse
Yes, I downloaded a rar for stock vibrant, it contains :
s1_odin_20100512.pit which i put in the PIT field, and T959UVJFD.tar, which i put in the PDA field
EDIT: this is from the "odin1.0_T959UVJFD_512.pit_rootupdate.rar" which is linked in a few posts in this forum.

yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??

rpesigan6 said:
yeah those are correct. try having re-partition checked because that worked for me. also, make sure you dont have any files on the csc field. are you using the correct drivers on your system??
Click to expand...
Click to collapse
Every time I try it with the re-partition option clicked it seems to hang at this status:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
I am retrying this now, I have a small fraction of the blue progress bar on the "Downloading..." screen on my phone. Neither the device nor odin seem to be doing anything. How long should this normally take?
As far as I know the drivers are correct.. I installed the x64 drivers from the link provided in the informative links sticky in this forum. adb was working fine.. device manager lists the phone as "SAMSUNG USB Composite Device" and Driver details window lists three .sys files w/ version 5.16 built by WinDDK
EDIT: not sure if this helps.. here is screen shot of odin & driver details h**p://i37.tinypic.com/2cn8501.jpg (will not allow me to link or post img)

ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it

rpesigan6 said:
ok instead of flashing the s1_odin_20100512.pit in the PIT field, try flashing the other PIT which should be s1_odin_20100513.pit
THAT IS WITH THE 13, NOT THE 12.
you can find the 13.pit in one of the rar files. look deep into the rar files. im pretty sure you will find it
Click to expand...
Click to collapse
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.

skoozi said:
Unable to find any such file. After some google'ing, I was able to find an s1_odin20100513.pit from the samsungfirmwareworld i9000 forum. tried that with re-partition still checked. Same result. Tried again with re-partition unchecked, it gets to modem.bin, tries to work and then my phone goes to a blank RED screen.
Click to expand...
Click to collapse
a blank red screen? all i can say is possibly try using another windows computer.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B

vibrantFTW said:
I had a similiar issue but mine was worse, I unplugged on accident during a kernal transfer. Get into download mode and keep the phone plugged in while you load ODIN. Then reset the phone back into download by removing the battery with it still plugged in. This should allow you to put the stock firmware back on. Use the 512/tar you already have. It is usually almost always an ODIN problem and not a truly bricked phone. I've ****ed my phone up a LOT and always able to revert after messing with ODIN.
Regards,
B
Click to expand...
Click to collapse
I'm trying to do this, but if I open ODIN with the phone already in download mode, ODIN does not see it. Pulling the battery and putting back in (downloading screen still up during this) does not change that. Maybe I misunderstood?
yes, i did.. likely at 4 am i guess.. so far its gotten past the modem.bin which it hasnt done in a couple hours of messing with this.. now its on filesystem.rfs again and stalling again, only now its only at about 10 - 15% as opposed to the 25% i was getting a couple hours ago before it stalled. This is with re-partition unchecked, btw. With it checked, odin still just sits at do not remove target.

I had this problem.. what I basically did was:
- Open Odin... add all the PIT and PDA files up (Re-partition UNCHECKED)
- Plug the phone in USB
- When the green battery was on the screen: hold volume buttons (basically.. get into download mode)
- Once in download Odin doesn't detect anything? Unplug USB and replug it back in
- Odin should detect your phone and one of the boxes should be labeled: COM[#]
Any # should be fine as long as you have the proper drivers
Then hit the start button. During this whole process, you should see the Android digging with a blue bar right below it. The screen shouldn't go black, blue, or anything crazy. Just android digging and a blue progress bar.
http://forum.xda-developers.com/showthread.php?t=734475&highlight=Stock Was the thread I used. Download hashtab (google it) and verify that the MD5 checksums are correct, once installed right click the file -> properties -> hashtab and then copy paste the MD5 on that thread an verify that it is correct.
For me the Odin process took less than a minute, the trick for me was to preload everything in Odin before plugging in the phone otherwise it would get stuck.
Personally, I don't think your phone is bricked anyway. Just some technical difficulties with getting Odin to work. The first time around when I was trying out Odin, it was messing up for me. Hope this helps.
Vibrant Drivers: http://forum.xda-developers.com/showthread.php?t=728929 -- If these aren't the set of drivers you're using, then uninstall yours and install this. This one works with no problems.

rpesigan6 said:
a blank red screen? all i can say is possibly try using another windows computer.
Click to expand...
Click to collapse
Was able to try this this morning.. it worked first try. With all the problems I was having, I was dumbfounded with how smooth it went. Don't know what was going on. Thank you all for your help with this

Hey guys, I figured I'll post here since I think I bricked my phone.... I was trying to install Eugene's Vibrant6 and I got stuck on the Vibrant Logo with Samsung at the bottom. I tried to reset with both volume buttons and power button and got to grey battery and nothing else... what can I do? Anyone can help me?
Thanks.

I fear my problem is worse as i was having the same issue with it loading filesystem.rfs and was stalling so i attempted to restart the process and now all that will display on my phone is an image of a cell phone a computer and a yield sign between. Plz help

Sounds like you need to upgrade Odin3 1.0 to Odin3 1.7

Ok i DL'ed Odin3 1.7 and still the same. The vibrant screen doesn't even come up, just an image of a cell phone and a comuter with a yield sign in between.

Start odin on your pc, remove batt, insert USB, hold down volume buttons and pop in the batt. This always gets me into download.
Sent from my SGH-T959 using XDA App

May god bless you and your children, and your childrens children, and their children!!!!!!!!!

problem with sgs firmware update

Hey guys I've been watching this forum for a while now and I need some help.
I searched around and found nothing relevant..
I got the latest kies, finally my sgs connected in kies mode, perfect. Popup for update, okay. Now... The first time i did this it showed me some progress bar which was probably something downloading. After that, the phone simply disconnected. Kies didn't show up anything, just that the phone was no longer linked to kies. The phone still showed the mtp application screen. After a few seconds kies shows 'Connecting...' and recognizes the phone again.
The second time it doesn't even get to the progress bar. When I click update, the phone simply vanishes from the kies screen.
I have not applied any lagfixes or anything, haven't rooted my phone.. Actually a few days ago I made a hard reset and everything is smooth. I just want that froyo already, I'm still running eclair.
Please, if you have a solution post it here, or at least point me in the right direction. I'm pretty much a noob when it comes to phones so.. Any help will be appreciated.

I dont know what to say
U already hard reset the phone.
Check with sgs tools what firmware do you have.
In case you have major issues.
Check the three button combo.
Uninstall kies, hard reset and try again.
Maybe is a usb problem .
How is the mount sd working ?
Sent from my GT-I9000 using XDA App

I had a problem just like this and it turned out to be a faulty USB connection. Try a different lead and USB port on the PC first.

Thanks for your replies guys, but unfortunately I still have a problem.
Reinstalled kies, nothing. Hard reset the phone again. Nothing.
Three button combo working perfectly.
In settings, the firmware seems to be 2.1-update1.
Usb problem, I don't think so. The SD card mode works flawlessly. There's one more thing I noticed. When I plug my phone in kies mode, windows also recognizes the phone, showing it up in my computer. The point is that when kies loses link to the phone, windows still finds the phone to be there, e.g. phone disconnects from kies, but not from windows. That's pretty weird..
You guys have any other suggestions..? What is the risk of flashing my phone manually to 2.2? I wanted to avoid that at all cost.

Kies also does not like the phone to be plugged in via any hub. It is best always to plug direct into a system board USB outlet.

Oh forgot to mention. I was indeed plugging the usb cable into a hub, and tried plugging in directly from the motherboard connectors and still no luck.. No idea what to do next.

Might be worth putting the phone into recovery and going to Tools, Emergency firmware recovery.

Well in the 3-button thingy i only have 'reboot system now', 'apply sdcard:update.zip', 'wipe data/factory reset' and 'wipe cache partition'. Halp plox?

Looks like you are left with two routes .
one take phone to service centre
two flash the phone to upgrade .
If flashing i would go the rom kitchen route .
That is only requiring a USB mass storage mode connection to transfer update file to sd card .
jje

I would try it. What are the risks and what happens if something goes wrong? I read somewhere that if I the 3-button combo is working I have nothing to worry about since I can reflash my phone at any given time. Is that true?

To get into recovery it is Home button. DOWN volume and Power on.
You will see a yellow triangle with "DOWNLOADING" Do not turn off the target. When you have this and have opened Kies just plug the USB in and use the recovery option if you can. As with all flashing there is always a risk so do this if you are prepared to accept this.

I've been doing a bit of research and as I saw around the only way you can mess up your flash is simply by disconnecting the cable when you shouldn't. I never actually saw anyone on different forums that have failed flashing so.. That thing pretty much gave me some courage, like hell..
I found a guide which I think would work:
http://samsunggalaxysforums.com/showthread.php/2921-How-to-use-Odin-to-upgrade-to-Froyo-from-Eclair
Do you think this is okay? Also the guy sais we should check *#1234# for PDA, and mine seems to be I9000XWJFB. He said we 'should be on JM1, JM2, JG1, JF1 etc...'. I assume that my phone falls into that category?
If this guide is erroneous please point me in the right direction, if you could.

Really Bricked my new Galaxy Tab 2 7 inch. I have tried everything :(

Hello, I so hope someone can help. I just updated my galaxy tab 2 7 p113 to Android 4.0.4 UEBLH2. That was done automatically from samsung. I wanted to then install the newest update to 4.1.1 jellybean. So I downloaded it from this link. http://www.trickytweaks.com/update-...ecli4-4-1-1-jelly-bean-ota-test-firmware.html. I put the official Android 4.1.1 UEBLH2 Firmware on my sdcard then held down my power and up volume and installed it. HOWEVER, it never finished installing. Went all the way to the end. Now I HAVE NO USB CONNECTION and NO BOOT UP. Just black Since I dont have usb connection I cant us oden. CAN ANYBODY PLEASE HELP? I still can put files on my micro disk card and then put sd disk in my tab and use the power button up arrow to install something but I tried installing clockwork mod but that did not work. Iam out of ideas. P.S. My tab IS NOT ROOTED. I tried updating back to and original rom 4.04 I download but that did work. Thank you.

I think you need to enter the download mode volume down+power or recovery mode volume up+power to be able to restore the tab
Try multiple times close the tab even with long pressing power then try the button combinations (press both for multiple seconds) and release to see if you could enter any mode
If you reached download mode try flashing stock firmware for your tab specific model 3113 or 3110 or 3100 via odin (install kies and reboot before)
If you reached recovery (stock) then connect with kies and choose recover firmware from kies options (near the word file in top) you should have active internet connection
You could try charging tab even for some hours before trying button cobinations
If not try to return as not rooted so warranty is goood
Sent from Galaxy S2 or Galaxy Tab2

Mohamedselim said:
I think you need to enter the download mode volume down+power or recovery mode volume up+power to be able to restore the tab
Try multiple times close the tab even with long pressing power then try the button combinations (press both for multiple seconds) and release to see if you could enter any mode
If you reached download mode try flashing stock firmware for your tab specific model 3113 or 3110 or 3100 via odin (install kies and reboot before)
If you reached recovery (stock) then connect with kies and choose recover firmware from kies options (near the word file in top) you should have active internet connection
You could try charging tab even for some hours before trying button cobinations
If not try to return as not rooted so warranty is goood
Sent from Galaxy S2 or Galaxy Tab2
Click to expand...
Click to collapse
Yup, this should get you going again. If you can get into download mode, you should be okay. That's what Odin needs.
Download mode is volume down plus power. Then volume up
Recovery mode is volume up plus power.

I want to thank both the posters on trying to help me. I did hold down the power and download button and it went in to the download mode. HOWEVER, since I can not access usb it did not do anything. Just kept saying downloading. As I mentioned in my first post I CAN ACCESS MY SD DISK FILES by doing the power up button thing. Thats the only way I can get files on. But the DOWNLOADING down arrow just does not do anything. hmmmmmmm will keep plugging away.

I can not understand how you can not access usb, is it a lacking driver so download kies and reboot and try connect again ,also try a different usb ports (esp the rear of case) of your computer
Was usb working before the problem?
do you have cwm or stock recovery?
If cwm so download cm10 or cm9 from www.teamhacksung.org and put in usb card and flash but do a cash delete and dalvik delete afterwards not for boot loop
If stock so try stock firmware from www.samfirmware.com (register their first) and put in sd card and try to flash
Sent from Galaxy S2 or Galaxy Tab2

growthweb said:
I want to thank both the posters on trying to help me. I did hold down the power and download button and it went in to the download mode. HOWEVER, since I can not access usb it did not do anything. Just kept saying downloading. As I mentioned in my first post I CAN ACCESS MY SD DISK FILES by doing the power up button thing. Thats the only way I can get files on. But the DOWNLOADING down arrow just does not do anything. hmmmmmmm will keep plugging away.
Click to expand...
Click to collapse
I think you're misunderstanding download mode. When you get the device in download mode, connect it then to the computer, with Odin open. The only reason Odin wouldn't recognize it would be a driver issue. In that case, do as the previous poster stated. When you're in download mode, you're strictly flashing through Odin. You aren't going to see the device as a storage device on the computer. The only way your computer can interact with it at this point is Odin. Via Odin, flash the proper p3113 firmware file from sammobile/samfirmware (will be a large 600mb+ file). Once that's done, you should then be back to completely stock and healthy recovery and ROM. Reboot tab and see what happens. If it boots, and you still want to update, then make sure you get the correct ota for the base file you just flashed (that is, if you're trying to upgrade to say Jellybean). If you need more help always ask, but you should be fine. If I lived nearby I'd do it for you.

All I can say is unbelievable help here! Thank you. I am spending hours on this (plus a fortune on this new Tab 2 7). After studying up I do now understand how Odin works and how grabbing the correct firmware will do the job. HOWEVER (maybe others come across this huge roadblock) nothing can be done with out usb interaction. I DID DOWNLOAD KIES and installed it. But no matter what I do can not get any storage device listed or anything going on between tab and computer. Only thing my Tab does is when I plug it in to the computer via usb is go in to charging mode with the charging icon showing. Loading Odin does not show any connection. I have tried different computer USB plugins, 3 different computers (all I have loaded Kies on). Iam sooooooo close. If only while in the POWER BUTTON DOWN ARROW DOWNLOAD MODE and running ODIN on my computer there would be a connection I would be home free and able to flash firmware.
dictionary said:
I think you're misunderstanding download mode. When you get the device in download mode, connect it then to the computer, with Odin open. The only reason Odin wouldn't recognize it would be a driver issue. In that case, do as the previous poster stated. When you're in download mode, you're strictly flashing through Odin. You aren't going to see the device as a storage device on the computer. The only way your computer can interact with it at this point is Odin. Via Odin, flash the proper p3113 firmware file from sammobile/samfirmware (will be a large 600mb+ file). Once that's done, you should then be back to completely stock and healthy recovery and ROM. Reboot tab and see what happens. If it boots, and you still want to update, then make sure you get the correct ota for the base file you just flashed (that is, if you're trying to upgrade to say Jellybean). If you need more help always ask, but you should be fine. If I lived nearby I'd do it for you.
Click to expand...
Click to collapse

growthweb said:
All I can say is unbelievable help here! Thank you. I am spending hours on this (plus a fortune on this new Tab 2 7). After studying up I do now understand how Odin works and how grabbing the correct firmware will do the job. HOWEVER (maybe others come across this huge roadblock) nothing can be done with out usb interaction. I DID DOWNLOAD KIES and installed it. But no matter what I do can not get any storage device listed or anything going on between tab and computer. Only thing my Tab does is when I plug it in to the computer via usb is go in to charging mode with the charging icon showing. Loading Odin does not show any connection. I have tried different computer USB plugins, 3 different computers (all I have loaded Kies on). Iam sooooooo close. If only while in the POWER BUTTON DOWN ARROW DOWNLOAD MODE and running ODIN on my computer there would be a connection I would be home free and able to flash firmware.
Click to expand...
Click to collapse
How about you just gtalk me, lol. I'll probably reply faster there anyway. deliberation at gmail dot com.

Don't use kies. Install the Samsung driver for mobile phones (Google it).
Sent from my GT-P5113 using Tapatalk 2

Download Mode
growthweb said:
All I can say is unbelievable help here! Thank you. I am spending hours on this (plus a fortune on this new Tab 2 7). After studying up I do now understand how Odin works and how grabbing the correct firmware will do the job. HOWEVER (maybe others come across this huge roadblock) nothing can be done with out usb interaction. I DID DOWNLOAD KIES and installed it. But no matter what I do can not get any storage device listed or anything going on between tab and computer. Only thing my Tab does is when I plug it in to the computer via usb is go in to charging mode with the charging icon showing. Loading Odin does not show any connection. I have tried different computer USB plugins, 3 different computers (all I have loaded Kies on). Iam sooooooo close. If only while in the POWER BUTTON DOWN ARROW DOWNLOAD MODE and running ODIN on my computer there would be a connection I would be home free and able to flash firmware.
Click to expand...
Click to collapse
Once you are in download mode, connect your tab to the computer with the usb connection.....you should see a com xx number pop up in Odin in yellow reporting your device is connected thru a communication port. From there you will be able to choose the file you want as a PDA uncheck everything else...reboot...reset timer....whatever. Just make sure you have the correct firmware. There is a Odin flashback to Stock rom in the development section. Make sure it's for your device. Once you start Odin, should take about 4 mins...disconnect and hold the power button down to reboot. That's it....

Hello Everyone Again, I just want to say thank you for all of you who took the time to help. I hopefully will become knowledgeable enough to help people in the forums as I gain knowledge. I finally did find the solution. I did everything that was mentioned. And no matter what what I did with KIES drivers Samsung usb drivers, etc could not get a connection so I could us Odin to keep me back to the orgiginal 800 mb 4.04 original file. My solution was (as mentioned) I deleted all my windows drivers dealing with usb, kies, etc. Then rebooted. I notice even though I did not have a direct usb connection showing up now Odin was showing a connection! So using Odin I got to restore everything and now back to like new. Lesson learned. Hope this helps others that almost fatally brick their tablets. Thanks again for all our help

growthweb said:
Hello Everyone Again, I just want to say thank you for all of you who took the time to help. I hopefully will become knowledgeable enough to help people in the forums as I gain knowledge. I finally did find the solution. I did everything that was mentioned. And no matter what what I did with KIES drivers Samsung usb drivers, etc could not get a connection so I could us Odin to keep me back to the orgiginal 800 mb 4.04 original file. My solution was (as mentioned) I deleted all my windows drivers dealing with usb, kies, etc. Then rebooted. I notice even though I did not have a direct usb connection showing up now Odin was showing a connection! So using Odin I got to restore everything and now back to like new. Lesson learned. Hope this helps others that almost fatally brick their tablets. Thanks again for all our help
Click to expand...
Click to collapse
Glad you got it sorted.

i jus did the same thing u did
hi how r u doing. i jus did the same mistake u did and i really need your help please

Maxwell255 said:
hi how r u doing. i jus did the same mistake u did and i really need your help please
Click to expand...
Click to collapse
Hi.if u have done the exact same thing then just read the previous page and comments.
Sent from my GT-P3110 using xda app-developers app

Glad to see you resolved your issue. In the future, question/help threads belong in Q&A only.
Thank You.
Because your issue has been resolved...
Thread Closed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.

PeartFan40 said:
Glad to see you resolved your issue. In the future, question/help threads belong in Q&A only.
Thank You.
Because your issue has been resolved...
Thread Closed.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Click to expand...
Click to collapse
Thread is still actually open, lol

Is there any way to save my tablet if there is NO firmware out?
Im talking about the SCH I705, I followed the root guide, and it got ****ed up.
Unable to boot into recovery (it goes to Odin "could not do normal boot.")
Tablet seems unresponsive sometimes (to power on/off)
Will boot cycle occasionally
???????????????????

igotbricked said:
Is there any way to save my tablet if there is NO firmware out?
Im talking about the SCH I705, I followed the root guide, and it got ****ed up.
Unable to boot into recovery (it goes to Odin "could not do normal boot.")
Tablet seems unresponsive sometimes (to power on/off)
Will boot cycle occasionally
???????????????????
Click to expand...
Click to collapse
You have to reflash your tablet using ODIN. It's not that hard. Just follow the second method here (you don't need to download android SDK)
copy this in your navigator bar : rootzwiki . com/topic/37272-verizonsch-i705-root-for-all-current-firmware/ ( delete space around the dot)
Plus, your tab will be rooted.
You're welcome.
P.S : This limitation of URL is annoying as hell.

In need for help with my S4, please

I have the galaxy s4 from sprint (sph-l720). I was having the phone flashed to page plus. something went wrong and he couldnt get it to flash. now the phone won't boot past the samsung screen but, i can get to recovery. I have been searching for days and days on how to figure this out. When i connect it to my computer odin wont recognize the phone in download mode. i have tried to re-install the drivers but they keep failing. my computer does make the sound when i connect the usb and it does attempt to install the drivers but fails. If anyone can help me i would greatly appreciate it. i know time and knowledge is money, i am not looking for a hand out. I am out of options here, please.

1dollarbi11 said:
I have the galaxy s4 from sprint (sph-l720). I was having the phone flashed to page plus. something went wrong and he couldnt get it to flash. now the phone won't boot past the samsung screen but, i can get to recovery. I have been searching for days and days on how to figure this out. When i connect it to my computer odin wont recognize the phone in download mode. i have tried to re-install the drivers but they keep failing. my computer does make the sound when i connect the usb and it does attempt to install the drivers but fails. If anyone can help me i would greatly appreciate it. i know time and knowledge is money, i am not looking for a hand out. I am out of options here, please.
Click to expand...
Click to collapse
Sounds like a couple of things.
First go buy (or use) a brand new usb cable!
A buddy of mine was banning his head trying to connect recently and found his cable was for charging only. And I've had old usb cable s cause a world of frustration.
next uninstall the Samsung drivers and then reinstall them "as administrator".
then go find the full tar of the m f9 Rom not just the firmware but the full tar. its a zip extract it. open up Odin as administrator, put it in the PDA slot. then plug your device in and flash
Sent from my SPH-L720 using XDA Premium 4 mobile app

leaderbuilder said:
Sounds like a couple of things.
First go buy (or use) a brand new usb cable!
A buddy of mine was banning his head trying to connect recently and found his cable was for charging only. And I've had old usb cable s cause a world of frustration.
next uninstall the Samsung drivers and then reinstall them "as administrator".
then go find the full tar of the m f9 Rom not just the firmware but the full tar. its a zip extract it. open up Odin as administrator, put it in the PDA slot. then plug your device in and flash
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
okay i will try the install as admin, guess i missed that and will report back thank you for responding so fast this is driving me crazy

looks like odin still wont show the magic connection

oh and before this happened odin did work fine with this USB that i have (the one that came with the S4)

1dollarbi11 said:
oh and before this happened odin did work fine with this USB that i have (the one that came with the S4)
Click to expand...
Click to collapse
You said you can access recovery..is it a custom recovery? If so flash a stock rom
If not heres a ota mf9 flashed from stock recovery http://androidromupdate.com/2013/07/09/sprint-galaxy-s4-ota-update-l720vpuamf9-stock-via-recovery/
Sent from my SPH-L720 using xda app-developers app

1dollarbi11 said:
oh and before this happened odin did work fine with this USB that i have (the one that came with the S4)
Click to expand...
Click to collapse
Ok uninstall your old sammy driver and install the latest Sammy drivers 'as administrator'.
Make sure your phone is charged to at least 60%. Even if it doesn't turn on plug it in to the wall for a while and let it charge.
Don't connect it to PC yet.
HERE is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the zip and extract the .tar.md5.
Run Odin 'as administrator'. Place tar.md5 into PDA slot of Odin. Odin should look like this If you check on 'repartition or anything you are going to hose your phone...
With Odin open on your PC and your phone still not connected, put it into download mode - Simultaneously Press and Hold [Power][VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode.
NOW plug your phone into the PC [Windows may install additional drivers; hopefully] and see if it shows up in any COM port (doesn't matter which one). If it shows up press start and let it finish. You should then have a stock MF9 working. First boot takes about 5 full earth minutes, let it go for even a little longer if necessary. If it doesn't boot after 10 earth minutes you may have to pulll the battery and then restart it but it should start.
You can then use the CF-Autoroot method to quickly root the phone. Then download goomanager and install a custom recovery and your off to the races.
Good luck.

leaderbuilder said:
Ok uninstall your old sammy driver and install the latest Sammy drivers 'as administrator'.
Make sure your phone is charged to at least 60%. Even if it doesn't turn on plug it in to the wall for a while and let it charge.
Don't connect it to PC yet.
HERE is the FULL system tar. All stock, kernel, recovery, ROM Modem.
Extract the zip and extract the .tar.md5.
Run Odin 'as administrator'. Place tar.md5 into PDA slot of Odin. Odin should look like this If you check on 'repartition or anything you are going to hose your phone...
With Odin open on your PC and your phone still not connected, put it into download mode - Simultaneously Press and Hold [Power][VolDn] until confirmation screen appears
Press [VolUp] to enter Download mode.
NOW plug your phone into the PC [Windows may install additional drivers; hopefully] and see if it shows up in any COM port (doesn't matter which one). If it shows up press start and let it finish. You should then have a stock MF9 working. First boot takes about 5 full earth minutes, let it go for even a little longer if necessary. If it doesn't boot after 10 earth minutes you may have to pulll the battery and then restart it but it should start.
You can then use the CF-Autoroot method to quickly root the phone. Then download goomanager and install a custom recovery and your off to the races.
Good luck.
Click to expand...
Click to collapse
way cool thank you for the write up I am in the process of trying this out. thank you very much

dang still a no go as far as odin seeing the phone. i guess i dont understand why odin was working before but now after reinstalling the drivers several times still cant pick it up.... any ideas? tried different port and new cable. anyone able to check it out remotely?

1dollarbi11 said:
dang still a no go as far as odin seeing the phone. i guess i dont understand why odin was working before but now after reinstalling the drivers several times still cant pick it up.... any ideas? tried different port and new cable. anyone able to check it out remotely?
Click to expand...
Click to collapse
one more silly thing to try.
After your phone is fairly well charged take out the battery for 1/2 hour or more even. I had some issues with other sammy's and doing that worked a few times; think it lets all the capicitors fully discharge on the device.
Put it back in the phone and go straight to download mode. Then start Odin and plug your phone in.
Also did you uninstall the old drivers, reboot, then install the new drivers and then reboot again before trying to connect?

I had this problem as well once. My cure was using Revo or some other advanced uninstaller to remove Samsung Kies, then I reinstalled the Samsung drivers.
However, that is only assuming that your problem is coming from your computer. Sounds like your phone's usb drivers got messed up during the flash. This seems somewhat reasonable to me, as I assume the USB drivers are in /system and the flash would disturb files there.
One other idea: be advised that Download Mode eventually times out. So, if you turn your phone on in Download Mode and leave it there for a while THEN connect it. Odin may not register it because your phone shuts off the download stream after a certain time of inactivity.
Hope this helps.

What are you guys using to unzip this image files, I downloaded like more than 10 stock files, every time I try to unzip them, it says the file is broken. I used 7zip, WinZip. My laptop has windows 7.

You should just have a .zip file that you flash via the recovery interface.
-Mobile post

richardpunch said:
You should just have a .zip file that you flash via the recovery interface.
-Mobile post
Click to expand...
Click to collapse
No, I'm talking about stock images that are in zip or rar files, that I need to unzip to get the the other tar.md5 files to odin, cause my phone is not working anymore. I think it might be my computer, or my internet connection. I don't know, I'm lost

maurogg84 said:
No, I'm talking about stock images that are in zip or rar files, that I need to unzip to get the the other tar.md5 files to odin, cause my phone is not working anymore. I think it might be my computer, or my internet connection. I don't know, I'm lost
Click to expand...
Click to collapse
NO just unzip the zip file.
Download the zip. extract the .tar.md5 file - it's a 2.10GB file after extraction named "L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar.md5" .
Launch Odin 'as administrator' and put that ONE .tar.md5 file in the PDA slot.
Re-read the tips here on the rest.

leaderbuilder said:
NO just unzip the zip file.
Download the zip. extract the .tar.md5 file - it's a 2.10GB file after extraction named "L720VPUAMF9_L720SPTAMF9_L720VPUAMF9_HOME.tar.md5" .
Launch Odin 'as administrator' and put that ONE .tar.md5 file in the PDA slot.
Re-read the tips here on the rest.
Click to expand...
Click to collapse
I used a friend computer, and I was able to unzip the file, I think my computer is corrupting those files some how. Thanks for the help though.

Possibly dead boot MP Rio, Help/Suggestions Please T.T

So apparently, I went home and usually put my phone into my desk.
While I took it from my pocket, I noticed the hardware buttons were lit but no display, I removed the battery to restart, during the week, frozen screen were occurring a dozen times when playing Clash, that though I didn't mind I just said to myself I will reflash the rom in the weekend.
But up to now,
It won't turn on, recovery mode or anything also doesn't work
It wont charge
Tried a new battery but still no luck
I think PC reads it but SPFT wont
Any suggestion on how I can revive my phone?
Attached is the error I get from SPFT

I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.

WalterWh1te said:
I don't own the A120 anymore. That is almost similar to this, as you might know.
Anyway, as nobody has answered your question, I will try to help as much as I can.
Does it give you a haptic feedback(vibration) when you try to power on the device?
Are you saying that it won't turn on completely?
If it is being detected on the computer and not on SPFT, you might want to check with the drivers you have. Do you have the MTK VCOM drivers installed? (I'm not really sure about the name, but it was something like that).
And try flashing the Stock ROM with SPFT with your battery removed from the phone.
Download the drivers.
Connect your phone without the battery and keep your device manager open, if it shows a device with a yellow exclamation mark beside it, right click and click on properties. You will have to do this quickly.
Once that is done, go to driver tab on the properties window. Select Update Driver. Browse my computer and enter the location of your downloaded and unzipped drivers.
(You might get a digital signature error or something similar. I'll tell you how to bypass that in the end. If you get that, go to the end, follow those steps and then come back and do all the steps after the downloading part.)
If the drivers are successfully installed, then unplug your device, run the SPFT and load the Scatter file of the Stock ROM.
Now select Download only and start the download, it will wait for you to connect the phone.
Plug in your phone without the battery. This should initialize the download process.
Now wait for the flash to be completed and if it is successful, take out your phone and boot it. If it boots up, congratulations.
If it does not, flash the same ROM the same way another time and check, if it is still not working, try with Firmware upgrade mode, twice. It should work in those tries.
Digital Signature Error bypassing.
I know only one method which works on Windows 8 and above(Tested).
Hold the Shift key while pressing Reboot.(Yes, you have to reboot your PC)
Once there is a blue screen with options, you should see "Troubleshoot". Select that.
Then Advanced Options and then Start Up settings. Then press Restart.
This will show you a menu with a lot of options. Select the option number which says "Disable Driver Signature Enforcement".
This will log you into the PC normally, but now, you can go back and do all the steps again and you won't get an error.
Cheers!
If this still doesn't help you, let me know on what happens so I can try to get you back your phone. Hope this helps.
Click to expand...
Click to collapse
Thanks bro, but I already gave up and bought a new one because I badly need an android device for my mini accounts in CoC. Haha but I am till trying to revive my Rio during my free time, this has been my phone for 1 1/2 year..
Yes I am aware that Rio is rebranded A120, I also asked from CM12.1 and AOSP LP Wiko Rainbow threads and some suggested help. Tried all that but still same errors.
No, there's no response of any kind including vibration when turning on. Hmn, as per the drivers, I've been using Tinno Driver since the jelly bean era of this phone, no problems or whatsoever from jb to kk to lp using that driver, so I thought there would be no problems. Still no luck in getting success. Using different versions of SPFT, using sp flashable Rio jb, kk, MMX A120 jb, kk, Wiko kk,lp stock roms, still no luck. Tried every port and cord. And I am using the Win7 64bit, I also resorted to MTK drivers, both the preloader and Da. Still.. No luck. Haha. I also tried, download only, format all+download, and firmware upgrade option with every possible combination from above but no success..
Thanks for your answer btw!