Related
I tried to unroot my phone via OCLF from the market. It went dark, then got the normal Vibrant screen, the the Galaxy S screen, then it went dark again. Now, it just sits. Black screen. All the buttons at the bottom are lit up. :-/
Anyone?
Silly question, I know. But did you have a nandroid backup, by any chance?
This is probably a last resort, but try boot into recovery and wipe everything. This fix the problem for me, the downside is you lose all you data.
Sent from my SGH-T959 using XDA App
If you are anything like me, recovery didn't work and using Odin and reflashing Stock with repartition didn't work either.
You'll need to use odin to flash Eugenes "Vibrant that doesn't brick" (NO REPARTITION), then use odin again to flash Stock (check repartition this time) and you'll be good to go.
You can try to flash the froyo rom with odin...... I had that same exact problem and this is what fixed it for me. Once froyo us flashed then you can flash whatever rom you want. Hth
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
hospo said:
Ok, I probably should have stated that I'm a complete newby and have no idea what I'm doing. I believe I do have nandroid, but other than that you all are speaking French to me.
Right now I'm in the recover mode (I think). It's hooked up to my computer and I'm in the "Downloading... Do not turn off target!!" mode. This is where I'm stuck...I have no idea where to go from here.
Please talk to me like I'm a 5 year old, because as far as this is concerned, I am!
Oh, and thank you so much for any help you can give me!
Click to expand...
Click to collapse
Well, good news is... you didn't brick your phone, this is recoverable. Best idea would be to search the forums on how to ODIN back to Stock. Theres plenty of posts on how to do it. You should also be able to find this in the tips & tricks threads. Good Luck.
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Kienz said:
Silly question, I know. But did you have a nandroid backup, by any chance?
Click to expand...
Click to collapse
Is it even possible to make a nandroid backup before rooting?
hospo said:
Thank you all for your help! I recovered it!! Seems as though I was just going about it the wrong way!! I got into the actual recovery mode and cleared it all out. Now it's as good as new!
Again, appreciate your help and patience with what I'm sure is the 120,000th post on this subject. ;-)
Click to expand...
Click to collapse
Hey - what does you doing? Please told me, I've the same problem:
If I start the phone with an USB cable and the battery symbol with the running point under this, the PC recognize that something is connected, but Windows found no driver....
How could you could flash the Stackfirmware back, if the recovery and download menu does not work ?
PLS help !!!
Check out this thread http://forum.xda-developers.com/newreply.php?do=newreply&p=8129898
Go to the section where it says "Did You Flash Something Before Disabling Voodoo? 2 Fixes to Help You Out."
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
And do fix #1 it is pretty easy and it wont take you more than 20 minutes.
Let us know if that works
Click to expand...
Click to collapse
If I following the link and the next one, I can read:
Caution!!! You Must be on STOCK Vibrant Rom & NEVER Have Already Flashed the JP3 Froyo Image
Click to expand...
Click to collapse
It isn't -> it's a Firmware for the normal Galaxy (3key)[I'm a idiot]
First,
You must already Have Odin installed & Know how to boot into Down-loader Mode!!
Click to expand...
Click to collapse
Thats also the problem as described in front : I have had no chance to received the DL Mode.. maybe I make something wrong? The phone is booting up till the "S" is there, after that, the screen is black, keys are lightning...
The recovery 3button are blocked from the beginning; the DL Menu - I did not have reached it successfully
The PC recognize, that is something on USB, but not what ... so Odin did not see the Mobile, too.
Well, today I tried setting up ClockworksMod so I could easily backup and restore my phone as needed. (As previous work i had caused issues and it wouldnt reboot until i reinstalled the rom)
Well, clockworkmod recovery would not install through the app, so I installed the image through Odin, and that worked flawlessly. I was able to backup and restore.
After it booted back up I was unable to add a new google account or erase the old one. Factory resetting it would casue it to get stuck in the boot loop again, until i restored it or reflashed.
Eventually I tried flashing another image, with repartition turned on.
Well, without surprise Windows 7 semi crashed and killed Odin.
Now when my phone "turns on" all i see is black. Nothing happens. I cant do any of the 3 button combos to get into Recovery or Download mode
Can anybody help me? I need to get this working ASAP!
Thanks
Edit : I need to check my eyes. I thought you can get into download mode.
If you cannot get to download mode with the 3-button-combo then you'll need a jig.
Intratech said:
If you cannot get to download mode with the 3-button-combo then you'll need a jig.
Click to expand...
Click to collapse
Dosnt that only work if the image of the phone and computer show up on the screen?
Absolutly nothing shows up for me
Can I have your battery cover to keep as a spare.
bncplix said:
Dosnt that only work if the image of the phone and computer show up on the screen?
Absolutly nothing shows up for me
Click to expand...
Click to collapse
You need a jig.
Uhm, why did you check repartition?
Also yes, you will need a jig. That's pretty much the only thing that can get you into download mode in this situation.
Transmitted from a Galaxy far far away via XDA telepathy.
Intratech said:
You need a jig.
Click to expand...
Click to collapse
Okay, going to just order one off ebay.
Will this do? hxxp://cgi.ebay.com/Samsung-i9100-Galaxy-S-II-Download-mode-USB-Dongle-Jig-/250824932406?pt=AU_MobilePhoneAccessories&hash=item3a6654bc36
But actually, it says it has to show one of those two screens, when mine is all black?
geko95gek said:
Uhm, why did you check repartition?
Also yes, you will need a jig. That's pretty much the only thing that can get you into download mode in this situation.
Transmitted from a Galaxy far far away via XDA telepathy.
Click to expand...
Click to collapse
Because it said it was needed for that image i was flashing
bncplix said:
Okay, going to just order one off ebay.
Will this do? hxxp://cgi.ebay.com/Samsung-i9100-Galaxy-S-II-Download-mode-USB-Dongle-Jig-/250824932406?pt=AU_MobilePhoneAccessories&hash=item3a6654bc36
But actually, it says it has to show one of those two screens, when mine is all black?
Because it said it was needed for that image i was flashing
Click to expand...
Click to collapse
It can still work in some cases, lets hope it does in yours.
Did you get that advise about repartitioning from Samfirmware?
Intratech said:
It can still work in some cases, lets hope it does in yours.
Hopefully! I just ordered one
Did you get that advise about repartitioning from Samfirmware?
Click to expand...
Click to collapse
Yes I did, was that something I shouldn't have done?
It sat on repartitioning for about 15 minutes, then windoes said Odin stopped responding and it killed it :/
I've been telling everybody to stop using the .pit files and repartitioning the device for every flash as you're just increasing the possibilities of things going wrong but people don't seem to take notice. Sadly in your case something did go wrong. You only need to use the .pit files and repartition the device if you mess up your partition table.
Those guys at Samfirmware really need to stop telling people to repartition their device for every flash.
Intratech said:
I've been telling everybody to stop using the .pit files and repartitioning the device for every flash as you're just increasing the possibilities of things going wrong but people don't seem to take notice. Sadly in your case something did go wrong. You only need to use the .pit files and repartition the device if you mess up your partition table.
Click to expand...
Click to collapse
Well, lesson learned. Today was the first time I even tried installing another ROM
Thanks for the help
Once my Jig comes in, I'll let you all know how it goes!
check if the phone heatens up extremely as soon as you put the battery in. if yes, thats a really bad sign.
a jig will only help you if you see anything on the screen. if the phone/screen doesn't react to ANYTHING, that's a full brick (happened to me too, jig didn't help, nothing helped, phone was completely dead and i had to send it in. fortunately, they repaired it within warranty).
lazyb2k said:
check if the phone heatens up extremely as soon as you put the battery in. if yes, thats a really bad sign.
a jig will only help you if you see anything on the screen. if the phone/screen doesn't react to ANYTHING, that's a full brick (happened to me too, jig didn't help, nothing helped, phone was completely dead and i had to send it in. fortunately, they repaired it within warranty).
Click to expand...
Click to collapse
See, this is what I was trying to say! I read everywhere that if somethign is on the screen the Jig will work, otherwise it wont. Others are replying to me here saying it should still work for me
I'm not too worried about it. I have 4 of the phones. I work closely with Samsung and they were given to me. It would still be nice if it recovers, so we will see!
i guess in situations where it was reported to work under these conditions the owners didnt fully exploit all different possibilites to get it back on and so they just came up with this false assumption.
nonetheless, it's worth a try. at least, the jig is pretty useful to remove the yellow exklamation mark and to reset the flash counter .
lazyb2k said:
i guess in situations where it was reported to work under these conditions the owners didnt fully exploit all different possibilites to get it back on and so they just came up with this false assumption.
nonetheless, it's worth a try. at least, the jig is pretty useful to remove the yellow exklamation mark and to reset the flash counter .
Click to expand...
Click to collapse
That's another thing I am unsure of, whats the flash counter?
bncplix said:
See, this is what I was trying to say! I read everywhere that if somethign is on the screen the Jig will work, otherwise it wont. Others are replying to me here saying it should still work for me
I'm not too worried about it. I have 4 of the phones. I work closely with Samsung and they were given to me. It would still be nice if it recovers, so we will see!
Click to expand...
Click to collapse
I'm not saying it will work for sure, what I'm saying is depending on the damage done it may still get you into download mode so you can flash the firmware.
bncplix said:
That's another thing I am unsure of, whats the flash counter?
Click to expand...
Click to collapse
to be precise, it's the "custom binary counter" which counts up as soon as you flash something modified manually on your phone. has nothing to do with your problem, though.
We need to find the way to boot the device externally, i.e. bootloader on ext. SDCard or the likes....
Hi,
recently my Nexus 7 got shutdown due to battery over,
and its appeared to be that when i am trying to turn it on it is getting stuck on the google logo stage,
so i have tried getting into recovery mode and doing a factory reset and wipe the device,
but, as soon as i am entering the recovery mode i am getting "booting failed" error and popped again to the boot menu.
i have also tried performing a flush using the SDK but i am unable to unlock the device, no matter how i am trying to.
i am getting an error saying "unlock failed (unknown error)".
So... have anyone encountered such problems and managed to fix it?
help me.. i am desperate
i was actually thinking why haven't i bought an I-pad.. but that thought passed right away
thanks in advance..
Bump
Ranac said:
Hi,
recently my Nexus 7 got shutdown due to battery over,
and its appeared to be that when i am trying to turn it on it is getting stuck on the google logo stage,
so i have tried getting into recovery mode and doing a factory reset and wipe the device,
but, as soon as i am entering the recovery mode i am getting "booting failed" error and popped again to the boot menu.
i have also tried performing a flush using the SDK but i am unable to unlock the device, no matter how i am trying to.
i am getting an error saying "unlock failed (unknown error)".
So... have anyone encountered such problems and managed to fix it?
help me.. i am desperate
i was actually thinking why haven't i bought an I-pad.. but that thought passed right away
thanks in advance..
Click to expand...
Click to collapse
Have you tried nexus root kit ?
Jim Omar said:
Have you tried nexus root kit ?
Click to expand...
Click to collapse
i cant unlock it so i doubt that it will work. :\
Ranac said:
i cant unlock it so i doubt that it will work. :\
Click to expand...
Click to collapse
Nope.. no luck with root kit..
any other suggestions?
Can you get into fastboot?
Use Nexus tools to reflash recovery.
killall said:
Can you get into fastboot?
Use Nexus tools to reflash recovery.
Click to expand...
Click to collapse
Yes i can get it to fastboot but i cant unlock it with any tool.. :\
definitely RMA that...
for no reason, after shutting down due to no power, then brick?
Jomari29 said:
definitely RMA that...
for no reason, after shutting down due to no power, then brick?
Click to expand...
Click to collapse
yep just got brick after no power..
and what is RMA?
Ranac said:
yep just got brick after no power..
and what is RMA?
Click to expand...
Click to collapse
Lol actually didnt know the Acronym. but googled it...
Return merchandise authorization
means RETURN IT!!! demand a replacement, NOT repairs,
boy if they pry that open and find root, your screwed...
Jomari29 said:
Lol actually didnt know the Acronym. but googled it...
Return merchandise authorization
means RETURN IT!!! demand a replacement, NOT repairs,
boy if they pry that open and find root, your screwed...
Click to expand...
Click to collapse
thats ok i did not rooted it :\
Ranac said:
thats ok i did not rooted it :\
Click to expand...
Click to collapse
Amazing, only if Google is here to see this, they would give you a hug...
now its defo RMA, hardware failure, i guess
Jomari29 said:
Amazing, only if Google is here to see this, they would give you a hug...
now its defo RMA, hardware failure, i guess
Click to expand...
Click to collapse
But i was hoping to find a way to fix it without returning it :\
is it possible?
Ranac said:
But i was hoping to find a way to fix it without returning it :\
is it possible?
Click to expand...
Click to collapse
i definitely dont have the answers to that...
but dont worry, someone will know surely know the answer around here...
Can you give me an update what did you do with the tablet?
I also have this issue..
I found a way to get back the operating system but not sure if I should send it back for RMA or not..
I was able to unlock the bootloader via toolkit from there i installed the stock recovery to the system and finally was able to re-install the stock image..
I got a realy strange problem with my D802, this came up out of the blue.
About 2 weeks ago I suddenly lost all network functions, for a few hours, then it came back again. Later I had only 2G and realy bad phone reception. The other morning everything was fine until a few hours later I was offline again. It was just then it came to me to check my imei and it was gone
At the time I was on stock 30B with one of Dorimanx' kernels. I was using this combo for a few days already so neither rom or kernel caused this.
Since this problem occurred I've been busy with this, searching the net, flashing all kinds of KDZ's, Kernels, Roms and what else but to no evail.
I did backup my original EFS partition but restoring doesn't help. been trying to put my imei back with QPST and EFS professional but NOPE!!
Rightnow the issue has changed slightly, when I (re)boot my Device I got no imei but after a while, can be a few minutes or maybe an hour the imei comes back.
I'm out of ideas, hope any of you guys can help :fingers-crossed:. Rightnow my G2 is nothing more then a really small tablet with phone functionality when it feels like it. And I feel like turning it in to a frisbee
I put a logcat from boot there ---> http://pastebin.com/kdR13DaR
Current setup stock 30B, stock Kernel, no Xposed
Thanks in advance
Edit: added last_kms log.
Have you tried flashing a modem? Maybe it could help
Good luck
Sent from my LG-D801
Rachid.Ala said:
Have you tried flashing a modem? Maybe it could help
Good luck
Sent from my LG-D801
Click to expand...
Click to collapse
Yeah tried that also. No luck
Besides: A KDZ comes with the proper modem doesn't it?
Is there a particular piece of hardware that could be damaged or could it be the main board?
All the other stuff is working fine on my phone
Try posting a dmesg taken shortly after boot.
runekock said:
Try posting a dmesg taken shortly after boot.
Click to expand...
Click to collapse
Tnx, will do after work
Bornin said:
Tnx, will do after work
Click to expand...
Click to collapse
Done
That was not exactly what I had in mind. Last_kmsg is the dmesg from before the latest restart. I hope that there might be a telling message during boot, so you need to restart again and capture a current dmesg. You can do that on a command line by typing
dmesg >/sdcard/msg.txt
runekock said:
That was not exactly what I had in mind. Last_kmsg is the dmesg from before the latest restart. I hope that there might be a telling message during boot, so you need to restart again and capture a current dmesg. You can do that on a command line by typing
dmesg >/sdcard/msg.txt
Click to expand...
Click to collapse
Like this?
Bornin said:
Like this?
Click to expand...
Click to collapse
Almost. That wasn't done right after a reboot, so the boot messages are no longer there.
runekock said:
Almost. That wasn't done right after a reboot, so the boot messages are no longer there.
Click to expand...
Click to collapse
sorry it took so long m8.
Yes, the new file is the one I sought. Unfortunately, it didn't tell me what's wrong with your phone. Maybe someone else is more clever...
If you haven't already done so, I suggest you try another sim-card.
runekock said:
Yes, the new file is the one I sought. Unfortunately, it didn't tell me what's wrong with your phone. Maybe someone else is more clever...
If you haven't already done so, I suggest you try another sim-card.
Click to expand...
Click to collapse
bummer, tnx anyway
Perhaps @dorimanx @somboons @SREEPRAJAY @XxZombiePikachu @kingroach @vPro97 @Diechel @d_Schizzo @Eminemiero @krija @AbdulrahmanAmir @natalya @Jerome-X @ahmed534
@blastagator
can look at the logs in OP?
tnx
Get a new sim card.
blastagator said:
Get a new sim card.
Click to expand...
Click to collapse
tnx but I tried that already. the sim is not the issue.
As a matter of fact its not even asking for a sim or giving the "missing sim"notification when it's out.
AbdulrahmanAmir said:
your boot Logs seems okaay refers to the software but the Hardware part of SIM mainly the logical board may leaks or got some electrical hiccups sometimes the OEM get fail in inventing logical board that comes with no IMEI show or even it works but not everytime flash a KDZ and dont root head for your warranty center and they'll change the LOGICAL BOARD you may backup your data before you go
Click to expand...
Click to collapse
Sorry for this awfully late reply mate ?
I got caught up searching for a decent chinese phone to replace this G2, but no winners there Hehe.
I lost my warrantee already because of a screen replacement. So I scored a G2 with broken screen (plus original charger ?) for a few euros to try to swap the motherboard coming weekend ?
Anyone else having this issue? I tried a factory reset on my S8+. I got stuck in the Recovery screen with a dm-verity error. I downloaded the firmware, installed it through Odin3.12.7, rebooted, then got a DRK error. I'm not sure how to get past or fix that? Any experience out there with that?
gm0ney1 said:
Anyone else having this issue? I tried a factory reset on my S8+. I got stuck in the Recovery screen with a dm-verity error. I downloaded the firmware, installed it through Odin3.12.7, rebooted, then got a DRK error. I'm not sure how to get past or fix that? Any experience out there with that?
Click to expand...
Click to collapse
Drk error is usually a very bad sign. After an Odin flash? Sounds like you accidenty clicked efs clear.. j hope I'm wrong avout Tha and if not then pray you have a backup a to restore via Odin. If not it's not looking good.
gm0ney1 said:
Anyone else having this issue? I tried a factory reset on my S8+. I got stuck in the Recovery screen with a dm-verity error. I downloaded the firmware, installed it through Odin3.12.7, rebooted, then got a DRK error. I'm not sure how to get past or fix that? Any experience out there with that?
Click to expand...
Click to collapse
Give this thread a read
https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559
yep this is why you should always back up your efs partition as soon as you are done rooting. without a backup repairing this is going to be very hard.
partcyborg said:
Drk error is usually a very bad sign. After an Odin flash? Sounds like you accidenty clicked efs clear.. j hope I'm wrong avout Tha and if not then pray you have a backup a to restore via Odin. If not it's not looking good.
Click to expand...
Click to collapse
Thanks for the reply. I really don't know what happened. Woke up the other day and it wouldn't send texts. It would receive them, but not send. When I took it to Verizon, they suggested a factory restore, so I started that and that's when the errors began.
What do you mean by having a backup to restore?
moocman42 said:
Give this thread a read
https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559
Click to expand...
Click to collapse
Thank you. I did see that but not much for the S8. The form link he has just errors....similar to my phone haha
djisgod said:
yep this is why you should always back up your efs partition as soon as you are done rooting. without a backup repairing this is going to be very hard.
Click to expand...
Click to collapse
I'm not sure how to do that, but too late now anyways I guess. lol.
So is there even a way to repair this?
gm0ney1 said:
I'm not sure how to do that, but too late now anyways I guess. lol.
So is there even a way to repair this?
Click to expand...
Click to collapse
To be honest I don't know for sure but I don't have a good feeling.b efs contains your IMEI and all other per-phone information necessary to get a device on the network. If it's erased then all that info is gone so if you didn't back it up it's for good.
There are places (some less than reputable, others surely very reputable) that supposedly can repair these in certain cases, but I know nothing more.
Also fyi: if your initial thought is to clone someone else's efs, know that that is quite illegal in just about every country as it amounts to IMEI spoofing
partcyborg said:
To be honest I don't know for sure but I don't have a good feeling.b efs contains your IMEI and all other per-phone information necessary to get a device on the network. If it's erased then all that info is gone so if you didn't back it up it's for good.
There are places (some less than reputable, others surely very reputable) that supposedly can repair these in certain cases, but I know nothing more.
Also fyi: if your initial thought is to clone someone else's efs, know that that is quite illegal in just about every country as it amounts to IMEI spoofing
Click to expand...
Click to collapse
Alright....that's what I was worried about. Thank you for the information. Much appreciated
contact the author of this thread https://forum.xda-developers.com/galaxy-s8/how-to/how-to-fix-imei-drk-issues-t3622559 he has been helping people to try and recover from your situation. his thread is for the s7 but he has been helping s8 guys as well.