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!!!!!!!!!

Completely Bricked?

So I tried to flash the new 2.2 odin file Eugene uploaded. Followed all instructions, flashed back to stock via odin even. Didn't work, odin locked up, now I can't even flash back to stock.
I get the phone and computer screen, then take out the battery, plug in usb, hold up/down and power while putting in the battery, etc... which gets me back to download mode, but can't odin any versions now... they all just sit there.
Any ideas or am I just screwed? I've read and read on tons of threads and they all say if you can get back to download mode, you should be good to go, but not the case here.

I had a similar problem on Eclair 2.1 which was fixed by restarting my laptop

+1 on the above. Also change USB ports. You are not bricked as long as you can get into DL mode.

Make sure you've got odin 1.7
Sent from my SGH-T959 using XDA App

Thanks for the replies. I was at work on my pc there and tried every usb port, reinstalled drivers, rebooted, etc... over and over and over and over... lol. Was getting freaked out.
I had my laptop with but never got the samsung drivers to work on my laptop correctly. And therefore odin doesn't even recognize my phone.
I got home and installed the drivers on my daughters computer running xp and then was able to flash the new leaked 2.2 files through odin first try. I guess something must be jacked up with my work computers drivers, even though I reinstalled them several times. Used the same odin exe, pit and md5 files. So happy it's all good again, I was starting to think it was hosed.

Thats awesome that you got it worked out.
Maybe someone can help me now with my issue??
Mine wont get past the android system recovery with these errors.
E: Cant mount / dev/block/st110
(invalid argument)
E: copy_dbdata_media:cant mount dbdata:
copy default media content failed.
Any ideas??

Ultraman666 said:
Thats awesome that you got it worked out.
Maybe someone can help me now with my issue??
Mine wont get past the android system recovery with these errors.
E: Cant mount / dev/block/st110
(invalid argument)
E: copy_dbdata_media:cant mount dbdata:
copy default media content failed.
Any ideas??
Click to expand...
Click to collapse
Leave the usb plugged in then Hold power down tell it turns off then just hold the volume up and down at the same time. If that doesn't work pull the battery put it back in hold the volume up and down keys and then put the usb in that will get you into download mode for sure ....your welcome
Sent from my SGH-T959 using XDA App

Yep tried that reflashed odin no luck, same issue. Tied to flash Eugenes that wont brick but cant get the Cmd prompt to work with adb reboot. I think I have Android Sdk installed correctly but cant figure that part out. Any more ideas

Ultraman666 said:
Thats awesome that you got it worked out.
Maybe someone can help me now with my issue??
Mine wont get past the android system recovery with these errors.
E: Cant mount / dev/block/st110
(invalid argument)
E: copy_dbdata_media:cant mount dbdata:
copy default media content failed.
Any ideas??
Click to expand...
Click to collapse
Was this after you flashed that leaked odin rom that Eugene posted? If so I think your supposed to choose to reset user data at this point.

No I actually flashed Obsidian V2, tried to do the Voodoo disable (now I know you shouldnt) and install the Core V2 kernel. This is where it left me. I have deleted cache and data and still have the same result.

So are you not able to get back into download mode with the three finger death grip? I was always still able to get into download mode by doing the following. Just that odin wasn't working.
Disconnect phone from usb/pc.
Take battery out of phone.
Connect phone to usb/pc cable.
Hold down, vol up and down, and also the power button as you put the battery in. (it's not as hard as it sounds, really haha)
When it starts up you should get the phone connect to pc type screen for a few seconds, and then the screen goes black, right when the screen goes black remove finger from power button only and it should go back to download...
Make sure you have odin open when you start this process and you should be able to flash from there. Good luck, I know it's frusterating.

Followed these steps and I got rid of the error WHEW!!!!!
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!

Ultraman666 said:
Followed these steps and I got rid of the error WHEW!!!!!
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. THIS TIME you want to check the 're-partition' box.
14. Now click start, let it finish, and this time your phone will load up just fine! BAM!
Click to expand...
Click to collapse
Exactly !! + 1

[Q] Double wammy, boot loop and clockwork fail

I am on root on 2.2 with Dk28 and epic all in one.Yesterday I decided I wanted to put baked snack on my phone. Everything went great and was working so i decided to install step 2 to get better battery life and I shut down to boot into clockwork. Therein started my problems. It refused to boot in to clockwork, so i tried to boot back up and it wont get past the Samsung with their .com boot screen (sorry first post cant post the full screen due to url). I have nandroid backups but cant make use of it as clockwork wont boot up. Drivers were originally working fine on my pc but overnight they got screwed up. (they working now on my other pc)Before that i tried to use odin to reset with the .tar file pda method and it said invalid image file and wouldnt work. Please leave suggestions as i dont know where to go next. I am working on a new pc now and will try after download, running dsl and slowgoing. Currently my phone is a break

irule9000 said:
I am on root on 2.2 with Dk28 and epic all in one.Yesterday I decided I wanted to put baked snack on my phone. Everything went great and was working so i decided to install step 2 to get better battery life and I shut down to boot into clockwork. Therein started my problems. It refused to boot in to clockwork, so i tried to boot back up and it wont get past the Samsung with their .com boot screen (sorry first post cant post the full screen due to url). I have nandroid backups but cant make use of it as clockwork wont boot up. Drivers were originally working fine on my pc but overnight they got screwed up. (they working now on my other pc)Before that i tried to use odin to reset with the .tar file pda method and it said invalid image file and wouldnt work. Please leave suggestions as i dont know where to go next. I am working on a new pc now and will try after download, running dsl and slowgoing. Currently my phone is a break
Click to expand...
Click to collapse
Which tar are you flashing..whats the filename?
also have you checked to make sure it downloaded correctly without corruption via md5checksum?

checksum and tar
i used this page i used thread number 794138(cant post links) by whosdaman. I tried using dk28 and di18, Dk28 got checksum and di18 got invalid image. I just downloaded a new tar for dk28 and am currently trying odin on a different computer

Let us know what happens,I'm here to help for atleast 2 more hours.
Sent from my Frankenstein FROYO ROM using XDA App

dk28 got checksum, working on di18, i hate you dsl

irule9000 said:
dk28 got checksum, working on di18, i hate you dsl
Click to expand...
Click to collapse
any updates man?

hash dash invalid
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> SPH-D700-DI18-8Gb-REL.tar.md5 is invalid.
<OSM> End...

Clockwork fixed
Goodnews bad news, I fixed clockwork and flashed clockwork backup, still wont boot tho

irule9000 said:
Goodnews bad news, I fixed clockwork and flashed clockwork backup, still wont boot tho
Click to expand...
Click to collapse
*Assuming that you want to return to the current official build used by sprint which is at this moment DI18*
*Assuming your phone can power up at all (if it doesn't there's a trick you can try for that mentioned elsewhere in the forums)*
*Only use main/direct-to-motherboard USB slot on PC (not on the face of your PC)*
*Only use high quality USB cable shorter than 3' and not the stock cable*
*Make sure SAMSUNG USB drivers are Installed*
*Make sure your battery is more than 50% charged*
1. SD Card is REMOVED, USB is UNPLUGGED and Battery is REMOVED from phone
2. While Phone is UNPLUGGED from USB, place battery in phone
3. Press and Hold the "1" key and Power button together to reach Download Mode
*KEEP USB UNPLUGGED FROM PHONE and phone in Download Mode*
4. Extract and Run Odin3.exe (Ignore the .pit file included in Odin3+v1.61andepic.pit.zip)
*Leave the "PIT" selection empty*
5. In Odin Uncheck "F. Reset Time", make sure "Auto Reboot" is the only box checked
6. In Odin click PDA and select your .Md5 file (SPH-D700-DI18-8Gb-REL.tar.md5)
7. Plug USB in PHONE and wait for yellow COM box highlight to appear in Odin
8. In Odin Press Start and WAIT patiently
Download SPH-D700-DI18-8Gb-REL.tar.md5 from the link on the first page of this thread where it says DI18 Update:
http://forum.xda-developers.com/showthread.php?t=794138
Download Odin from the link on the Wiki --look for "Odin3+v1.61andepic.pit.zip" under where it says "Odin Stock Flashing" at:
http://forum.xda-developers.com/wiki...Stock_Flashing
Download Samsung USB drivers from the link on the first post of this thread:
http://forum.xda-developers.com/showthread.php?t=770388

fck me
I really shouldnt have screwed with odin while tired and pissed. Lost clockwork mod and tried again. Now im stuck with a paperweight that can go into download mode or boot to a screen that shows an old flip phone triangle with an exclamation mark and a pc/laptop. If anyone knows what that means, please post

I've reached that screen 3 times and twice I've been able to get my phone back out of it (not something I'm exactly proud of).
try:
1. Remove sd card and battery and unplug USB
2. While first holding 1+Power button, re-insert the battery
and if that doesn't work try it with the USB first plugged in.
next try
1. remove battery and sd card
2. insert USB
3. press and hold down vol up + vol down (not power) and Replace battery
next try
1. remove battery sd card
2. plug in USB
3. re-insert battery
4. hold power + vol down only
and lastly try
calling sprint or samsung repair as applicable and plead complete ignorance as to how it happened and any knowledge of smart phones and android beyond what's in the basic user manual. Say something like "It was like that when I woke up"
that seems to be the certain solution for this problem from what I've read.

I see ur problem rename ur .tar.md5 file to just .tar you might have to enable extensions to be seen. I don't remember how I did it but I remember googling something like how to enable file extensions. If you successfully rename it you will get a warning and just click ok on it or whatever enables you to change the extension.then use that file in odin.
Sent from my SPH-D700 using XDA App

The flip phone triangle thing was something I had too. Make sure ur tar file is some where around 150mb to 200mb. The first time download my tar it was like 5mb for some reason
Sent from my SPH-D700 using XDA App

I tried the tar thing it worked better but im having issues with drivers and connection issues with odin. Its working better but im getting stuck at pram or something like that

Sry I really can't help you much more. I'm not a dev so I really don't know. I only speak from experience. Also you should be more specific I posted two things about the tar file.
I also checked how big the tar should be and it is 255 mb
Sent from my SPH-D700 using XDA App

i hate my phone
Every time i fix one problem another appears. My computer wont see my phone. The drivers are fine as my brothers epic 4g appears as normal. It seems that something in the phone is messed up. I have no other computer to test it on. Help me fellow xda members, what should i do.

Are you using the same cable thst your brother used? I couldn't get my computer (or a second one ether) until I used my wife's cable.
George
Sent from my SPH-D700 using XDA App

i tried about 5 different cables, but now for some reason im getting the original recovery? to load. Its really wierd, when i leave the phone something happens even when it is off. is there anyway to restore from the original recovery. Is there anyway to mount an sdcard without loading the phone. I dont have clockwork, but i have an update.zip file on my sd and i want to see if it will load anything. Unfortunately i took it out under the directions of someone else and the phone wont remount it. I was wondering if there is a way to trick the phone to remount it allowing to do the update via stock recovery

I'm sure that would be possible via adb...but I'm not well versed in that lol
Does your phone connect to the computer at all anymore?
Sent from my SPH-D700 using XDA App

thank you all the help. You guys were correct, i had an extension problem. After erasing md5 i was able to use odin. This was after i got lucky and my computer saw it as a modem on my much higher quality microusb. Im in the middle of a nandroid restore bringing back from stock di18 to good old dk28. Thanks all for help.

[Q] Stuck with phone ! pc screen. Help?

I was using Odin to install [KERNEL] stock+Voodoo stable 5.x for Vibrant and something went wrong, I'm not sure what but now I am stuck with the phone ! pc screen.
Odin will not recognize that there is a phone there if I just start a download Odin tells me <OSM> All threads completed. (succeed 0 / failed 0)
In another thread (whose fix didn't help me out) I read
masterotaku said:
Because..... "Phone ! PC" is not a hard brick. I've "Phone ! PC" bricked my Vibrant dozens of times.
Glad you've recovered though. It can be a scary screen if you're not used to seeing it!
Click to expand...
Click to collapse
Are there other recovery techniques?

Did you get where it says Download Mode? If not, take the battery out, put it back but don't turn on the phone. Then open Odin load the pit files and pda. The next step with the phone off, hold the volume up and down the same time and plug the usb cable while holding up and down buttons and voila....you will have COM # showing up in your Odin and ready to flash again
Check here :http://forum.xda-developers.com/showthread.php?t=810130&highlight=odin

dany865, following your instructions Odin did recognize that there was a phone attached. 0:[COM5] and I'm flashing the PIT and PDA from the thread you linked me to now. It's a slow moving process!
So slow that I swear it was frozen so I took and chance and closed ODIN, after all what was the worst that could happen I was already staring at a brick, and rebooted the phone. PRESTO, it was back to JI6.
I went straight to MiniKies and put 2.2 on that phone, then spent a bunch of time reinstalling applications and configuring ADWlauncher.
So far all I know for sure that was lost was my finely tuned setup, root access, and a month of SMS messages that were not backed up.
Thank you!

I you are gonna root I would highly recommend to get "Titanium backup pro". It makes the setting up process 10x's faster and has a tin of other great features.

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!