Last night I tried to unroot my phone as the title says. Everything was going fine, and I installed the stock files on Odin. The video I found on it said to select re.Partition and T.Flash on Odin. I did, and now the phone is unresponsive and my phone doesn't show up on my computer. I can't turn it on or use any button combination to turn it on. If I hold the power button my computer makes a connection sound but doesn't show up. Please help.
Go to device manager and check if it finds it at any name. Sometimes bootloader devices are even found as "bacon sandwich" . Well.. most of the time they will be hidden under like "marshall bootloader" or something totally weird that You would not plug into Your computer (bacon sandwich).
As long as it makes sound it's good. It means that the device isn't 100% dead.
Try holding Odin button combination(5-10 seconds) with the phone being plugged in and see if odin detects it or if Your device manager shows something.
The good thing? Just in case if You really killed Your phone, take it back to Samsung and tell them that You left Your phone to charge over night and in the morning it was dead. They should replace it. (Note 7 battery affair might be helpful)
And future advice. Don't use t.flash nor repartition. Although I think that repartition is safe as long as You use pit file. But t.flash NOPE. Unless I know what certain thing does, I don't touch it.
Just to sum it up.
1. See if Your phone is detected in Device manager
1b. See if You can get it to be detected by using Odin button combination.
2. If not take it to Samsung. They should replace it, because it's completely dead. And there's no way for them to check the knox.
3. Never use t.flash or repartition again.
4. If You need any further help just tell me
Good luck.
What video did you watch? Options only need to be changed when you flash TWRP - you need to untick the Auto Reboot to make TWRP stick, even with auto reboot it flashes ok. So basically OPTIONS of Odin is just when you are in deep... Now your phone is definitely hard bricked and I would recommend just go to your seller and ask for a warranty fix... if they cant boot to dl mode they might not even be able to see if your knox is 0x1.
ProtoDeVNan0 said:
Go to device manager and check if it finds it at any name. Sometimes bootloader devices are even found as "bacon sandwich" . Well.. most of the time they will be hidden under like "marshall bootloader" or something totally weird that You would not plug into Your computer (bacon sandwich).
As long as it makes sound it's good. It means that the device isn't 100% dead.
Try holding Odin button combination(5-10 seconds) with the phone being plugged in and see if odin detects it or if Your device manager shows something.
The good thing? Just in case if You really killed Your phone, take it back to Samsung and tell them that You left Your phone to charge over night and in the morning it was dead. They should replace it. (Note 7 battery affair might be helpful)
And future advice. Don't use t.flash nor repartition. Although I think that repartition is safe as long as You use pit file. But t.flash NOPE. Unless I know what certain thing does, I don't touch it.
Just to sum it up.
1. See if Your phone is detected in Device manager
1b. See if You can get it to be detected by using Odin button combination.
2. If not take it to Samsung. They should replace it, because it's completely dead. And there's no way for them to check the knox.
3. Never use t.flash or repartition again.
4. If You need any further help just tell me
Good luck.
Click to expand...
Click to collapse
I found a UMBus Root Bus Enumerator. I don't know if that's something
Bus enumerators are the USB controllers in Your computer so I don't think it is it. Maybe You could find something like "unknown device" or "unknown descriptor" something like that..
Btw. Did You install Samsung drivers? Sometimes devices aren't visible in device manager until You install proper drivers.
If nothing really works then download Smart Switch and then plug Your phone in. It should find it in like a emergency mode hopefully. And if smart switch doesn't detect anything either then just go to the place where You got the phone and they will replace it.
Related
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.
Been back and forth from CM7 , stock, Powerwashed no problems. Until now! Long story short my computer will no longer recognize my phone. I know i need the Nexus drivers since I'm on CM7, So I install Android SDK, download the google drivers, can't even install them since it still doesn't recognize my phone. Odin doesnt work, I can't even go back to stock. What the HECK happened? Doing searches does nothing they all say to install SDK but that doesn't help.
EDIT: Now I'm really screwed, went into recovery and tried to flash the recovery I made when I first installed CM7, phone now won't boot it just goes to the Samsung screen and stays there. With the computer not seeing it I think I'm bricked for good
Grandpa had this same problem when he was well into his 90's. Ya just have to re-introduce them like they're strangers on every meet... posting in the Q&A section wouldn't hurt either.
http://forum.xda-developers.com/showthread.php?t=1271898
have you try enabling DEBUGING MODE under settings, applications, development? That usually helps my PC see the phone
Original Drivers?
OP stated his phone no longer boots, so enabling debugging is not an option now. Given that he's flashed a lot of ROMs, I'd suspect that is already enabled though it is very good advice for those who can get into their settings.
Since you can see the SAMSUNG logo, hopefully you can get it back.
I know you're running a different kernel, mods, etc... but have you tried downloading the original Fascinate drivers?
Here's one place I found them (if they don't work, just search the development forums for several links)
64bit: Drivers HERE --> http://www.wikifilez.com/root files/epic4g/usb_drivers_GalaxyS_x64.zip
32bit: Drivers HERE --> http://www.megaupload.com/?d=NZS8BF7E
1.) Launch ODIN
www.mediafire.com/download.php?73ta726ghelw381
2.) After that, pull the battery AND the SD Card
3.) Plug the cable into one of the back USB ports on your computer (make sure that USB port is working first by hooking up a mouse).
4.) Press (and hold) down the volume down button while connecting the USB cable and continue to hold it until you see a giant yellow triangle
5.) Look in ODIN for the yellow COM port to appear in Odin. If it appears, then you are good to go (jump below and flash back to stock first)
6.) If not, I'd highly recommend finding a friend with an android phone (another Fascinate would be best) and borrowing their USB cable as this sort of problem can easily be caused by a faulty cable. I've used the cable for an Incredible for my phone occasionally.
Once you get it recognized, I'd recommend flashing back to stock following the instructions in this thread http://forum.xda-developers.com/showthread.php?t=1178544
After that, you can get back to custom ROM'ing.
I really hope you get it working, a bricked phone is frustrating.
---------- Post added at 09:08 AM ---------- Previous post was at 08:57 AM ----------
Addendum:
Just a quick addendum to my last post... When going from a really messed up phone back to stock, I highly recommend only flashing via Odin. Do not use PST.
Since I don't have enough posts to reply in the development forum, here's a quick overview.
Download the zip file from the thread linked above, unzip it to get the CI500_VZW_ED05_FROYO_REL.tar.md5 file. Get the PIT file.
1.) Run ODIN
2.) press the PIT button and select the PIT file
3.) press the PDA button and select the tar.md5 file
4.) TRIPLE check that you've chosen PDA and NOT phone
5.) place a check in the reparition box (you will lose all your apps, sorry)
6.) press the START button and wait 5-10 minutes, the phone will automatically turn off once the flash is complete
8.) replace battery, and restart
wait about 4 minutes for the repartition to occur and the phone to boot
If you already knew this, I hope you're not offended!
Thanks and best of luck!
I have spent Hours on this site looking for help with my phone...
I have down loaded app after app. reset factory setting. hard reset the phone. but the fact is my phone will not Root. I am with sask-tel. this all started with me wanting to unlock the phone.
What the phone will do:
down load apps
hook up to wifi
hard factory resets(up and down /power button)
usb debug
but thats it. if I try run a root program it does nothing. if I try to open the tech aids(down and power) nothing happens it says downloading for hours.
I have manually looked for the efs file and SU start commands are not reponding(jack's program for got the name).
Model number
GT-i9000m
firmware 2.3.3
baseband version I9000Ugkg3
kernel version
2.6.35.7-19000ugkg3
[email protected]#2
build number
gingerbread.gkg3
Mobile network type
Umts
yeah soo... please help sorry the post was so long I have no idea what I am doing...lol
Have you checked this thread??
http://forum.xda-developers.com/showthread.php?t=939752
Gti9
UMMM..
gcuchiha said:
Have you checked this thread??
http://forum.xda-developers.com/showthread.php?t=939752
Gti9
Click to expand...
Click to collapse
I did look at but it still does not help me as I am trying to refresh all the software in the phone because some one delete vital file Samung told me the carrier did it and they are the only ones who can fix it. I am really startiung to dislike Sasktel
but I really cant afford to by a new phone that 22 percent, or more, of my monthly income.
keepitsimpleplease said:
but the fact is my phone will not Root. I am with sask-tel. this all started with me wanting to unlock the phone.
Click to expand...
Click to collapse
Flash this rooting kernel using odin and install superuser and busybox from the market
keepitsimpleplease said:
if I try to open the tech aids(down and power) nothing happens it says downloading for hours.
Click to expand...
Click to collapse
If you are trying to get into recovery, it's volume up, power and the home button.
Volume down, power and the home button gives you download mode, so it's normal for it to say "downloading" for hours.
try the file xsenman posted. Put your phone in download mode, open Odin, choose the file under PDA, plug in your phone
(make sure you have the Samsung USB drivers installed) and that the ID:COM box is lit, then flash.
Once it is finished, download Busybox and Superuser from Google Play and you are rooted.
By the way, KG3 is a very difficult ROM to get a rooted kernel for.
Ian
I'll try that....
Thhank you very much... I do hope that it works. I am taking a couple days break from it all. spend 9 hrs yesterday trying to simply diagnose, and for some one whom knows nothing about system programs, or tech access points for the phone I think I have done well for a newbie.
So far all I have been able to do is fix every lag in the phone. lol. thank you for the File link and for the walk through
Quick questions
w98seeng said:
If you are trying to get into recovery, it's volume up, power and the home button.
Volume down, power and the home button gives you download mode, so it's normal for it to say "downloading" for hours.
try the file xsenman posted. Put your phone in download mode, open Odin, choose the file under PDA, plug in your phone
(make sure you have the Samsung USB drivers installed) and that the ID:COM box is lit, then flash.
Once it is finished, download Busybox and Superuser from Google Play and you are rooted.
By the way, KG3 is a very difficult ROM to get a rooted kernel for.
Ian
Click to expand...
Click to collapse
Ian,
How do I insure my "Samsung USB drivers" are installed?
Can you please further explain what you mean by "ID:com box is lit"
Thank you
Re
Samsung drivers are installed together with Samsung Kies. If you already have Kies installed on your computer and it connected successfully at least once before then you have the right drivers.
Now, when flashing anything onto your phone the Kies application must not be running. Make sure you stop it (e.g: by stopping any Kies service from Windows Services).
"ID:COM box is lit" means one of the upper boxes in Odin turns green.
The steps are:
1. Start Odin on your computer and select the PDA and CSC files (you should find more details about what files to flash in other posts)
2. Start your phone in Download mode : Vol. Down + Home + Power until you see Downloadin
3. Connect the USB cable to your phone.
If none of the boxes turn green in Odin you should try different USB ports on your computer. One of them will eventually work.
hey guys is will need some help with this device im not kind of a noobie on this kind of things bcs i been working with several phones, like the veteran xperia10, galaxy ace, motoroi2, etc etc. but never with a tablet
here is what it happens a friend ask me if i can upgrade his sgt-p1010 to a newer version, honeycomb or maybe ics, i´ve read a lot of posts regarding this on how to upgrade it trough odin everything was fine until the reboot of the device, bcs by my mistake i flash a rom of the 7.7" tab and this one is a 7" only now the tab is not turning on, odin is not recognizing it, either samsung kies or the pc. buttons are not responding it wont charge and cant enter to download mode.
I REALLY NEED HELP FROM U GUYS, HOPE U CAN HELP ME
ps. srry for my english :laugh:
This kind of thing can result in the inability to boot which can only be repaired by the use of specific hardware, i.e. this could be a "hard brick". Then again, maybe it can be restored to working order by flashing it again (a "soft brick"). So the very first thing you need to know is, can it get to download mode?
Turn it off, if it's switched on, and charge it for a couple of hours,say four hours. Use the original charger connected to mains. It doesn't matter if it shows anything, or nothing on the screen, let it charge. This is to make sure flashing it won't fail because it doesn't hold a charge.
Now connect it to the PC with the original USB cable. Then after making sure it's switched off, switch it on by pressing the On/Off button, while simultaneously the Volume UP switch. Press them both at the same time, and keep them pressed! If you're lucky you'll get the yellow graphic with the download text. A phone symbol, an !, and a PC symbol is fine too. Even if it doesn't show anything, you may be in download mode, so install the right drivers, and hopefully Odin or Heimdall will recognise is, and will allow you to flash the right ROM.
well i already let it charge for all night long and nothing happens after i perfomed the flashing the screen was totally in black but it doesnt shoes anything i mean the tab was turned on, then apparently batterie dies and after that is not charging. already tried with the heimdall thing but it says that device is not connected.
I think that this is going to be a HARD BRICK
so do u thhink there is another way to solve it?????
or it will be necessary the JTAG stuff???? bcs i dont want to try that it seems that is very difficult to me bcs i dont know nothing about hardware jejejeje
You have installed the Heimdall driver? It's called zadig.exe. Then you have to go to download mode and connect the Tab to the PC with the USB cable. Then Heimdall hopefully will detect the Tab.
If there's no way software will revive the Tab, it's hard bricked and will need hardware to get it working again. There's this guy mobiletechvideos.com who will repair any kind of brick. Basically he uses the JTAG on the board of the Tab and a special box to flash the right ROM to the Tab, even when it's dead. Some here have tried the service, and they say he's quite reliable. Another way is to modify your Tab with Adam Outler's Unbrickable Mod. It's brilliant, you can't soft brick your Tab after that, but it involves soldering very small components on the board of the Tab. The mobiletechvideos guy can do it for you I believe.
Well, I guess you just got a hardbrick .
The only way to fix this problem is go to SAMSUNG SERVICE CENTER.
Sent from my GT-P1000 using xda app-developers app
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!