I recently went to unlock my phone via Z3X box, my phone was on 4.3 they said to downgrade to 4.1, I followed the steps using Cygwin Terminal in making a custom firmware, I flashed it via Odin and it passed, however was stuck at the Samsung Logo, no usally in this case I would boot into recovery and wipe data and cache, however my Home Button does not work, so I used my Jig to force in to download mode and flashed stock I747m 4.3, went to boot and same thing stuck at the Samsung logo???? any ideas what's wrong here???
mza2k9 said:
I recently went to unlock my phone via Z3X box, my phone was on 4.3 they said to downgrade to 4.1, I followed the steps using Cygwin Terminal in making a custom firmware, I flashed it via Odin and it passed, however was stuck at the Samsung Logo, no usally in this case I would boot into recovery and wipe data and cache, however my Home Button does not work, so I used my Jig to force in to download mode and flashed stock I747m 4.3, went to boot and same thing stuck at the Samsung logo???? any ideas what's wrong here???
Click to expand...
Click to collapse
Tried to factory reset after the 4.3 upgrade? Sounds like you might have borked your EFS partition with the z3x box, if a reset doesn't help...
http://forum.xda-developers.com/showthread.php?t=2471421
Some info from there might be helpful if you are still stuck. I know it is for the Note 3, but many of the same ideas apply, though the mount points are most likely different thus you can't just copy and paste those commands and hope it works (might even make it worse if the partitions are that different).
Is the Home button broken or just stopped working after trying to do this stuff?
Yeah the Home button just doesn't work when you press it that's why I needed the Jig to get in to Download Mode, and the phone was fine after trying with Z3X box it didn't do anything with Samsung tools because I was on 4.3 it started when I created that custom firmware and flashed it, haven't been able to get it to boot since that even with Stock Firmware..
Think you might need to check out this thread then:
http://forum.xda-developers.com/showthread.php?t=2549068
Sounds like an issue with the downgrade / bootloader deal. No Home button sounds like it might really cause some issues here though. Owning a repair shop, I'm pretty familiar with the S3 construction and it's pretty rare that the Home button stops working. Has it been repaired or gotten wet or something?
the phone was water damaged I just replaced the main board with a new one and the phone was fine minus the Home Button, and I have tried the SD card thing about 3 times now and it doesn't do anything???
Related
Help Please...I really need some now.
I had my phone unlocked and everything was fine. I have been updating the resurrection remix roms and enjoying them a lot. I was up to ver. 1.7. The problem is that I had some of the screen issues (fine horizontal lines on the screen) and I decided to get the phone repaired. I just got the phone back today and I noticed that Bell repair shop had wiped everything off my phone and put their stock version of ics on and the phone was no longer rooted. I have been trying to root the phone a few times now through Odin (like I did half a year ago) and at first it failed due to not being able to open the serial port. I opened Kies and the phone connected so I knew the drivers were ok. I tried Odin again and this time it went through and gave me a pass......but on reboot, it just hangs on the Samsung screen and I cannot turn the phone on at all now. I either am stuck on this screen or the CWM screen, but it won't carry out any command ie. power off, open zip from scard etc. I really need some help and quite worried about the phone now.
Please, please help
you allowed usb debugging?, go back to download mode and flash a kernel with root.
Go to download mode and flash a stock kernel. If you are unable to get into download mode because you said that your phone wont accept any commands for example pressing buttons then you could buy an USB jig. This will bring you directly to download mode. That would propably be your last chance.
Then flash a stock kernel back on there. Maybe the exact same which was on there before. Or just flash a stock full ICS Rom.
Frozenthunder said:
Go to download mode and flash a stock kernel. If you are unable to get into download mode because you said that your phone wont accept any commands for example pressing buttons then you could buy an USB jig. This will bring you directly to download mode. That would propably be your last chance.
Then flash a stock kernel back on there. Maybe the exact same which was on there before. Or just flash a stock full ICS Rom.
Click to expand...
Click to collapse
Yahoo!! I finally got the thing unstuck. I tried the Odin procedure again but this time I downloaded a more updated root kernel. It passed, then on bootup it wasn't stuck in space......although it still did not boot up properly. It ended up going just black...with no screen whatsoever. But the CMW program was working though and I was able to do a system restore from a month ago. I was very happy and very lucky I made that backup. Now, not only do I make the Titanium backup, but I also do a backup from the CMW program.....because now I know it's possible to freeze up before I ever get a chance to use Titanium. A good lesson indeed.
I installed Chainfire3D (after hearing good things about it) and then realized the problems it causes, so i deleted the app and then its CF3D drivers from system/lib which didnt work properly anyways. Upon restart device doesnt boot anymore :crying: (welI maybe its on cause the battery generates heat, but its black screen) I also couldnt get titanium backup to work in the past just in case something like this happens cause it was constantly stuck on yahoo finance when backing up.
My main issue is I had alot of things (worth a couple days) installed on my phone, and dont want to lose all of it. Bad thing i didnt realize there is Nanadroid backup (cause its my first android phone) which works unlike titanium quickly and efficiently, but backing things up now after black screen is pointless no? i can acess CWM recovery, but dont want to factory reset yet.
So any way to inject those stupid CF3D drivers via ADB? Or maybe backup everything but that certain system/lib folder?
Edit: i ran into this:
On CF-Root just boot into recovery, ADB shell to it, and type "rootsh" (instead of "su") to have root shell access... if anything goes wrong, just "mount /system" and "/system/lib/cf3d_uninstall.sh" to remove the CF3D driver and restore the old one. Not very likely it will happen, but a good fallback option in case of issues (no need to reflash firmware or restore backup)
Click to expand...
Click to collapse
, unfortunately cf3d_uninstall.sh was one of the files i deleted, but maybe if someone who has Chainfire3D installed on S3 LTE can share that file, i can then inject it and restore the old drivers?
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
white 16GB Tmoble GS3
Actually my current issue is similar, it boots up says galaxy S3 then black screen. I can connect to odin, i can boot into clockwork, and i can flash roms, ODIN says everything is successful after i flash but when it boots it still goes to a black screen. this happened after i flashed a rom(that worked) and flashing a kernel that also previously worked....after that its been stuck....i can flash whatever with success but i cannot seem to get it past that Galaxy S3 screen....
I flashed the new FreeGS3 rom, and the TGST STOCK ICS Alpha37 kernel i cleared caches and wiped davliks not too sure where to go from here.....Do i need factory tmoble GS3 PIT file?
Redsalamander said:
Seems mine suffered a similar fate.
a friend suggested SPB 3D loaded it. It sucked and caused lock-ups and delays. I uninstalled and the phone seemed to be fine after.
I plugged the phone in to charge overnight and about an hour later when going to bed the screen was stuck on the boot-up screen.
has not gone past this since.
Wanted to get the firmware restored and after trying to find a suitable stock one I took it to my SP for repair they tried to flash it but it fails every time, they said the motherboard is toast.
It will boot to flash mode so it can be uploaded but it doesn't work. Odin says no partitions.
Tried Heimdall it detects the phone but it tells me the image is corrupt and I also have no idea how to repair the partition that seems to be lost.
Click to expand...
Click to collapse
Not to offend anyone the Dev app said he wasn't going to support it for the galaxy s3
Sent from my SCH-I535 using xda premium
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Redsalamander said:
Turns out mine was a faulty mainboard after dragging their feet to repair it including a delay due to them wanting to verify warantee with proof of purchase samsung finaly agreed to swap it out for a new one.
Click to expand...
Click to collapse
Well thing is on my end...i didn't flash whatever the OP had flashed. What i DID do though is flash a rom and a kernel on the same cwm event. when it rebooted...it just does this....
i have a backup file....its on my laptop though....with only using odin or cwm how can i push that file onto my phone? My CWM doesnt have USB mount else id just do that.....?
Hello guys, I have (I think) soft bricked my Galaxy S2.
(Details: UK Phone, Carrier was Orange but now I am running 3 on it, official phone model Galaxy I9100T (NFC support iirc) )
Right I am curious bunny hacking away at the phone from the day I bought it, reading pages after pages on different roms and kernel and everything. Finally I settled on CyanogenMod 9 and then went straight to the CM10.1 release. Today Morning I installed the 23/02/2013 CM10.1 realease and then started browsing the XDA forums on whats new. I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
I tried to go "restore" an img I had taken a week ago of the system with CWM but the phone would no longer boot into recovery.
So I went ahead and got all the recovery package (I9100TDULP9_I9100THUTLP7_HUT) to reflash my phone with Odin 3.07.
This is where I hit a brick wall and now I am truly lost at what to do, my computer doesn't recognise the phone (Download Mode). I keep getting "there is a problem with this device" error and the Device manager shows an unknown device connected. So I installed the Samsung drivers from the samsung website with no luck. Still getting unknown device error. So I googled for a solution and the only solution that came up was reformat my PC since it could be a problem within the OS, so I went forward and used two other PC and still getting the error. Please Help SOS.
tl;dr: Getting Device not recognised error when I connect phone to the computer via USB cable.
Thanks in advance to all the knights to my rescue
DNoob92 said:
I came across the Siyah 6.0b kernel release and saw it was compatible with cm10.1, eager and foolish I downloaded the apk without doing any further reading or any instruction, overconfident from all the flashing I have been doing for the past year, flashed the kernel via CWM recovery. Now the phone is stuck in what I assume is a boot loop (again I am pretty noobish).
So What have I tried to fix the soft brick?
Click to expand...
Click to collapse
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
surplus mplieac
crocodilechris said:
Just go to recovery menu (VOLUP+MENU+POWER) and wipe cache and wipe dalvik. That should fix it.
Click to expand...
Click to collapse
I cannot enter Recovery Mode, the screen just goes blank
EDIT: So the only thing that works atm is
1) The battery charge animation (huge green battery in the middle of the screen) when plugged in.
2) Download/Odin mode (which 3 computer refuse to recognise when connected via a USB cable)
EDIT2: The other thing I forgot to mention was, that I have lost the original SII micro USB cable which was black and now I am using the white micro USB cable I received with my Galaxy Note 2.
You could try uninstalling all Samsung-related drivers/software (Ie: Kies), download the Android Naked Driver or the Android ADB Driver (I wish I could recall where I got it from, but it also came with the driver for the Galaxy SII... Sounds like it might be more of a driver issue than it would be a cable issue..
Borrow and S2 cable.
There are a lot of guys having issues with note's cable.
Try a laptop, and install kies on any other pc you try.
Flash siyah v5 instead of flashing v6.
You can relax, if the only thing you did is flash a kernel then there is nothing wrong with your phone.
Try different cables, try Odin 1.85 (that one always worked for me), try different pc's, reinstall drivers, make sure no kies process is running in the background.
First of all thanks for the replies
I couldn't get the drivers working still (after re-installing, installing kies). But while eating lunch I remembered reading about removing battery and pressing the Power button and it doing something I couldn't quite remember. So I thought to myself it wouldn't hurt trying. Did that and the phone Finally booted in recovery mode, I took a breather of relief and than located my previous backup img and restored the phone.
But now a new problem arose, the phone went into SIM lock as soon as it booted and now I guess I have to fix that
Well thanks guys
Quick question guys is SIM network unlock pin basically same unlocking phone form a carrier?
It's asking for a SIM pin or network code?
Get galaxysim unlock by searching xda (free here, paid at play store).
Sent from the little guy
ok so i was running 4.0.3 with no problem until i decided to update to 4.1.2, so after updated finished with no errors i booted the device
the galaxy s2 logo appears the BLACK SCREEN
no boot animation
what i have tried
return to 4.0.3
wipe data
use custom recovery that matches the os version
us custom recovery to format all the partitions
flash using pit file
different version of odin
and thats pretty much all
now even when i return to 4.0.3 it stil wont boot, please help
If the phone won't boot & PC/phone don't recognise each other in Odin, you're pretty much boned. Possibly JTAG, if not service centre (or local mobile shop if no warranty).
it goes into download mode, and recovery, and it boots up, but after the SGS2 logo i get a black screen on any firmware, even gingerbread
and i can still flash using odin and cwm
If it were me, I'd keep trying Odin flashes (even trying random stock roms); often in these situations the first 6 flashes don't work but the 15th actually fixes the problem (I'm using these numbers as an example) for whatever reason.
That's the only way you're fixing it, unless the NAND is borked, which you won't be able to fix. Try Hopper8's 'Odin won't work' thread, there's stuff in there which might help.
Simply_Android said:
ok so i was running 4.0.3 with no problem until i decided to update to 4.1.2, so after updated finished with no errors i booted the device
the galaxy s2 logo appears the BLACK SCREEN
no boot animation
what i have tried
return to 4.0.3
wipe data
use custom recovery that matches the os version
us custom recovery to format all the partitions
flash using pit file
different version of odin
and thats pretty much all
now even when i return to 4.0.3 it stil wont boot, please help
Click to expand...
Click to collapse
Hey this is exactly what happened to my phone, I flased stock 4.1.2, it was working fine but somehow freezing randomly. So I installed latest cwm hoping to fix the freezing problem, the boot animation won't show up after the logo, though I can hear from the speaker sound of the boot animation, and the screen won't seem like turning on (touch buttons not lighting up). Any luck on fixing this problem?
it turns out its was the usb data cable connector, surprised. i dont even know what one has to do with the other, anyways, i had it replaced and it works perfectly
Simply_Android said:
it turns out its was the usb data cable connector, surprised. i dont even know what one has to do with the other, anyways, i had it replaced and it works perfectly
Click to expand...
Click to collapse
Well I re-flashed the stock android 4.1.2 using odin, and everything got back to normal, the screen is working again. Though the phone is still freezing randomly, even after a couple of minutes after booting the phone. However I'm glad to get my phone with the screen working again!
This is my first post to a forum, so please bear with me...
So a few days ago, a friend of mine got a Verizon Samsung Galaxy S4 from someone, for free. He got it for free because the screen's glass is cracked a bit, and the phone is bricked; the previous owner didn't know what to do with it. I decided I would try to fix it, because if I do, I might be able to buy it off him and give it to my little sister, who currently has a dying iPhone 5C.
When I turn on the phone, it boots, showing the samsung logo, showing the red Verizon screen, and playing the boot tune. Then, just when you'd expect it to go to the OS, it shows a screen which at the top reads "Device memory damaged". Below that, it says "The data partition has been corrupted. You need to reset your phone to factory defaults. This will erase all your data." And below that is a button, which says "RESET PHONE". Tapping on it does nothing.
I have worked with android phones before (rooting, ROMs, locked bootloaders, bricked phones; even all these things on a Galaxy Gear smartwatch), and I know what the data partition is. I remembered that the recovery on samsung phones have an option to wipe the data partition. So I tried to access the recovery menu by holding Power, Home, and Vol+ when the phone is off. It doesn't work either . It shows the Andy robot laying on its back with a door open on its belly, with a warning icon popping out. So the recovery is dead...
I thought I could try to fix the recovery by flashing it with Odin :fingers-crossed:; Didn't work. It is blocked because the phone can't verify version . Then, after a little more research, I realized I might be able to fix the recovery by flashing a whole stock ROM. I don't know what firmware the phone is running, because I can't ask the previous owner. So I tried a few KitKat ones, and they were all rejected by the phone. Then I booted the phone back up, and I realized the RESET PHONE button acted like it was part of a Lollipop UI (There is a darker circle that extends from the part of the button where you tap). So I went back into download mode and tried to flash the 2 OTA versions of Lollipop (OC1 and OF1). The error this time was "SW REV. CHECK FAIL : fused : 8 , Binary : 6". This may or may not be the error I got before with the KitKat ROMs. I don't remember, and I'm not at my desktop to try the old ROMs.
After looking up this error, I found no exact results, but there were ones with a similar error. People said that it means a ROM is being flashed that is too old to pass the downgrade prevention system. I've been trying to flash what seems to be the latest firmware revision for this phone (OF1). Any ideas? Are the OSs I'm trying to flash somehow too new for the phone (even though I've tried all of the stock Lollipop ROMs. Should I give the phone back to my friend and tell him it's dead?
Thanks in advance!
I can't post images because I haven't posted here (or on any forum, for that matter) before.
Well, it seems really bad but you can try Samsung Smart Switch or Verizon Wireless Software Upgrade Assistant to repair the phone, else way JTag it's another option
Fuse 8 is OF1
Matthew M. said:
Fuse 8 is OF1
Click to expand...
Click to collapse
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
you probably needed to flash a lowship odin tar and repartition
Legitsu said:
you probably needed to flash a lowship odin tar and repartition
Click to expand...
Click to collapse
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
evanzolman said:
Sorry, what do you mean by "lowship"? I did use a PIT file to repartition, which didn't work, possibly because the OS being flashed with it wasn't being accepted...
Click to expand...
Click to collapse
a normal odin tar will not fix a bad partition regardless of the .pit you need a tar that s a _user_Low_ship todo a full format odin was failing because the partitions where screwed and you weren't using the correct image
go to sammobile.com they have all the s4 all variants roms.
evanzolman said:
Thanks for the info. I tried flashing that version. Didn't work. I ended up taking my own broken S4 I had laying around, which had a smashed screen but a supposedly good Mainboard, and transferred the mainboard to my friend's bricked S4. Now it boots fully, and I made use of my old phone that was laying around.
BTW, do you know where or how you found out which version Fuse 8 represented? I'd like to learn more about this kind of stuff.
Click to expand...
Click to collapse
I am not aware of a definitive guide on the fuses. I found it by trial and error
Envoyé de mon SM-G903F en utilisant Tapatalk