Related
All,
I flashed JellyBelly last night, flash the JB bootloader, then the ROM etc...everything was working fine, restored apps via titanium etc...my phone was up and running in JellyBean. I was playing around with it, then notice some apps wasn't starting, media(music) wasn't being scanned so I attempted to reboot into recovery and fix permissions thinking that will fix my problem. Anyways, I rebooted, and was stuck in the Google screen. I took the battery out, got into recovery and tried to dirty flash the rom, it failed. I tried to restore from nandroid i did, and it also failed.
Now all I can get into is to recovery. Seems like everything I tried whether its nandroid or the jellybelly rom, it would fail. Is my SD corrupt? I did attempt to restore from Liquid 1.5, that went through, but when it tried to reboot, it would fail and reboot again and again.
Is my phone dead? What are my options?
Please help!
Thanks!
you are far from dead, as of now. How long did you let it sit? I've done some ROMs where it sat at the Google splash for 5 minutes before it started to boot. I would get the Kies, go into download mode and start from the beginning. That will put it back to how it was straight from the factory (minus the locked bootloader).
I am not familiar with Kies...can you explain a bit?
I googled a bit and found this link for GNex ToolKit V7.4, could this be an option to unbrick my phone?
http://forum.xda-developers.com/showthread.php?t=1400871
leoingle said:
you are far from dead, as of now. How long did you let it sit? I've done some ROMs where it sat at the Google splash for 5 minutes before it started to boot. I would get the Kies, go into download mode and start from the beginning. That will put it back to how it was straight from the factory (minus the locked bootloader).
Click to expand...
Click to collapse
This is a Nexus. We don't use Kies or Odin...
OP, fastboot flash the stock images. Don't use toolkits. If you can get into recovery then you will be able to restore back to stock 100%.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Actually, I am very new to the GNex so I am still figuring out where everything is. Since it's a Nexus device, it may not have a Kies, I just automatically think Kies when I think of any Samsung phone. Somebody will come along that is much more familiar with the GNex than I am and point you in the right direction.
---------- Post added at 01:59 AM ---------- Previous post was at 01:55 AM ----------
martonikaj said:
This is a Nexus. We don't use Kies or Odin...
OP, fastboot flash the stock images. Don't use toolkits. If you can get into recovery then you will be able to restore back to stock 100%.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Yeah, you beat me to it.
Thanks all!! I FINALLY got my phone back. I used the WUG Nexus Root Toolkit. THANK GOD FOR THAT!! Was painless to bring my phone back to stock.
Now I'm going to reflash JellyBelly Again!!
I am currently having trouble with my phone, it works fine as long as i do not turn my phone off. If I turn my phone off it seems to go into a hard brick, and I cannot get back into my phone unless I use a homemade jig to get into download mode and there for getting back to my phone rebooting. I noticed this problem right after I downloaded the teamwin app to update my recovery, but I accidentally choose the "I9300" recovery instead of my phone "I747". That initially put my phone into the first hard brick that I encountered, then with the help with www youtube com/watch?v=y5_yoJilLe0, I was able to get my phone and flash the correct recovery as well as a new rom. So my question is, how can I fix this problem of not turning off my phone and making it go into a hard brick? Any help will be much appreciated, and I am sorry if this is in the wrong place, this is my first post.
I do have a nandroid backup that I have tried and it still has this problem
Further testing I have figured out that I have to have my SD card that has the software to unbrick(using the method in the youtube video) in my phone for it to turn on. With my SD card out it acts just like a hard brick.
Sounds like a bootloader problem...
You probably flashed over sbl1. Its not included in firmware updates so the odin flash will not help.
Thats just a guess though. It depends on what partition the i9300 stores its recovery. It may be a different one from sbl1.
---------- Post added at 04:36 AM ---------- Previous post was at 04:28 AM ----------
Ok, I just checked and you wrote over the rpm partition (mmcblk0p6). This is included in the firmware package so flashing with odin should have fixed it. Did you not flash the firmware? You said you followed a video, but you should use the instructions we have in this forum.
It also helps to know what build your current firmware is.
I need some help with this issue. I was upgrading my phone through kies going from 2.3.5 to 4.1.2 stock, when something happened and the install failed. When the phone boots up, it remains stuck on the Samsung logo, as I figured would happen. I am temporarily using this phone until the end of the year when I get a new phone. My old phone was the GS4G, and I have cyanogenmod 11 installed on it, so I am reletively familiar with installing custom roms, just not interested in doing it on this phone yet.
So.... anyways, I tried to get into download mode, with complete and total success. BUT.... ODIN will NOT recognize the phone. ODIN recognizes my wifes S4 and my old GS4G, no problem. I am able to get into recovery mode as well. And as you guessed it, another BUT....... it will not recognize the SD card so I can't install the zip file from there. The phone had no problems with reading the SD card until I attempted to update the phone, so I know its not the drive slot.
I am at a loss. The recovery mode only shows the files on the internal memory, so if theres a magical way to transfer from the SD card to the internal memory with download mode and recovery mode as being the only options, let me know. I have tried 3 different computers, 15 different installations of the USB drivers, and 6 different SD cards, so I know its not any of those. Also tried 3 different usb cables.
Please advise as I am at a total loss as to what to do. I always knew from my GS4G that if you could get into download mode, you were good. And even if you couldn't get odin to work on it, there were various java scripts that would find ways to work. I have not found any for this phone as of yet, but maybe I missed something.
Thanks for anyone that can help!!
Start with the simple stuff.
Odin won't work if kies is running at all. In fact, easiest thing to do is uninstall Kies . If you MUST have it... later reinstall it.
So get rid of Kies. Then try different Odin versions. 3.04 and 3.07.
---------- Post added at 07:01 PM ---------- Previous post was at 07:00 PM ----------
Another thing is to somehow try another PC.
Thanks for the reply. I will give it a shot and see what happens. I will post results hpefully tomorrow. Just got done with work at the fire house and now lots of housework to do.
I have what's probably a unique situation, though I hope not. For background info, I bought two I747s, one white and one blue, each with issues, but I intended to put parts together to end up with one good one.
When I did a factory reset on the blue one via the recovery menu, it returned a bunch of errors along the lines of "failed to mount /data." Then when it rebooted it would hang on the Samsung logo. Back in recovery mode it returns more of the same errors just booting into recovery mode, and factory reset still returns more of the same errors and doesn't fix anything. I flashed 4.3 with Odin in an attempt to fix it, but I got the boards mixed up, and that one had 4.4 on it, not 4.1 like I thought. I'm pretty sure it's hard bricked now (that whole can't downgrade thing) because it's unresponsive to everything. Though my computer does recognize that it's plugged in, more on that later.
So I figured, fine, I screwed up, I'll just use the other board with 4.1 on it from the white phone. Except when I did a factory reset on that one, it did the exact same thing! Same errors, same problem stuck at the Samsung logo. Except this time I'm not flashing sh*t until I know exactly what I need to do to fix it. In another post where the guy had the same issue with 4.1.1, it was solved by flashing 4.3 with Odin. And another post where the guy had no idea what version he had, he just knew it was lower than 4.3, his problem was also solved by flashing 4.3, But since my last efforts failed miserably, I'm very reluctant to try it until I get some knowledgeable input. I don't remember exactly which version is on there, it's 4.1.something. I'd also prefer not to upgrade beyond 4.1 because I'd like to unlock it and from what I'm reading you can only do it for free if you're on 4.1. So I guess I need a link to an Odin flashable 4.1 package?
As for the poor blue phone that used to have 4.4.something, and was mistakenly flashed with 4.3, I've heard about JTAG but I don't quite understand it, and I'm not sure it would work in my case since a lot of what I'm reading says that bricking which occurs from downgrading is often unfixable. However, Windows recognizes that a device is plugged in when I attach it via USB. It shows up in the Device Manager as QHSUSB_DLOAD. I am currently researching more on this and the method of booting from an SD card, except I don't have an SD card reader at the moment.
Any assistance, advice, links, information, and plain ole encouragement are always welcome and appreciated.
For the phone running 4.1, flash any stock rom in Odin. After flashing, boot into recovery and perform a factory reset, then boot the phone and use the free method to sim unlock. The important thing is to have the stock 4.1.1 dialler in order to access the hidden menu options?
For home hard bricked phone, you will have to try the debrick image method. If it doesn't work, a jtag service should be able to force flash a rom to the phone.
Wow, that was like a crazy fast reply!
What if the phone is 4.1.2? Can I still flash 4.1.1? I'm on the hunt for a 4.1.1 stock rom now.
Yes, you can flash 4.1.1 from 4.1.2.
audit13 said:
Yes, you can flash 4.1.1 from 4.1.2.
Click to expand...
Click to collapse
Apparently not always. I downloaded and flashed 4.1.1 with Oden 3.07, it rebooted, showed the android image like it was updating, progress bar finished, and then it just went blank. Now both phones are in the same condition of being hard bricked and showing QHSUSB_DLOAD in the device manager.
This is strange. I have downgraded approximately 10 i747m phones from 4.1.2 to 4.1.1, unlocked using the free method, and re-flashed back to 4.1.2 after unlocking.
http://forum.xda-developers.com/showthread.php?t=2371897
What options did you check in Odin? Where did you get the 4.1.1 ROM? I ask because the stock ATT 4.1.1 rom was apparently removed from sammobile.com.
How did you confirm that the phone was running 4.1.2?
I checked only auto reboot in Odin.
I found this link sammobile.com/firmwares/database/SGH-I747/ in this thread http://forum.xda-developers.com/galaxy-s3-att/help/downgrade-att-running-stock-4-4-2-rom-t3170938 , 7th post
The download was going absurdly slow, so I googled the exact file name being downloaded which was, I747UCDLK3_I747ATTDLK3_ATT, and found a google drive link at https://drive.google.com/file/d/0B_UTWXKFnZoNVFdSVjJEZlMwZjA/edit which was the first result after searching for the file name if that link doesn't work. I'm downloading the slow one now to compare it to the one I got from google drive.
I'm unsure if the phone was 4.1.1 or 4.1.2, that's why I asked if it's possible to flash 4.1.1 on top of 4.1.2. I was only trying to do a factory reset originally and had no intentions of flashing anything. I just wanted to wipe out all the crap on it from the previous user so I had only glanced at the version out of curiosity to see if it was unlockable via the free method. I remember it was 4.1.something.
I have an SD card reader on order. Hopefully I'll be able to unbrick one of them.
Do you, or anyone else, have any idea why a simple factory reset would cause errors like I described and then hang on reboot? At that point both phones were 100% factory and I hadn't done anything to them except put a battery in them to power them on. I've done a factory reset on four other S3s and this didn't happen.
It is definitely possible to flash 4.1.1 over 4.1.2 because the bootloader could not be downgraded until the mjb version.
That's what I've been reading. So where did I go wrong? Any idea why a factory reset would screw up like that?
Did you confirm the bootloader before flashing?
audit13 said:
Did you confirm the bootloader before flashing?
Click to expand...
Click to collapse
No, because I had no intentions of flashing it when I tried to do a factory reset. Then after that went bad it wouldn't boot, and I don't know how to check the boatloader when a phone will only go into recovery mode.
Where did you see reference to 4.1? It's possible that the modem or baseband was 4.1 but the bootloader was 4.3.
Under about device and then Android version. The one where if you tap it a lot you get the jellybean android that pops up. It wasn't the baseband version because that's a much longer number with the model number in it.
That screen doesn't tell you the bootloader.
As I said, I didn't check for the bootloader version before I ran into trouble because I only wanted to do a factory reset and I didn't intend to flash anything. I wouldn't imagine that it would have a different bootloader than the OS version unless that can happen without any user intervention because the previous owner was only concerned with selfies and games. She certainly didn't modify anything.
I cant explain what happened. This has never happened to me after flashing about 10 phones.
I believe it has something to do with the errors that were produced while trying to do a factory reset. What bothers me is that both phones did the exact same thing. Normally I'd say it was something I did, except that I didn't do anything but put a battery in them, boot up, find lots of junk installed, and then attempt a factory reset. On the first phone, I rebooted into recovery and tried it from there. On the second phone I tried it from inside the OS. Same results on both. The phones ran fine before that.
Any advice on how to do the boot from an SD card, or how to do the JTAG thing? I've been reading a lot but the information jumps around a lot. I'm comfortable with soldering and have an IT background if that helps.
It's possible that the recovery was corrupt or the partitions were corrupt.
Whenever I factory reset a phone, I always boot into recovery to do that, not from within the ROM.
Sounds to me like you did nothing wrong.
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
audit13 said:
Did the previous owner have the phone from the time it was new?
Edit: for the phone that you flashed with 4.1.1, Odin said "pass" in the status window and the it auto rebooted?
Click to expand...
Click to collapse
I don't know for sure if she had it from new. Yes, for both phones Odin said pass in the window and then it rebooted. I had walked away when Odin finished with the first phone. I came back and it was dead. The second one I watched and it showed the android with the wireframe in his guts and the progress bar which moved across, and then it just went blank.
There were error messages about the partitions when I did the factory reset IIRC. Perhaps the recovery or the partition was corrupted like you said. It's just odd that both had the exact same identical problem with the exact same results. That's why I think that it must have been something I did, except that I didn't DO anything other than initiate a factory reset.
I took an i747m and reflashed stock the Telus 4.4.2 ROM.
In download mode, you should see the green Android guy with the words "Downloading...Do not turn off target" and a blue progress bar moving from left to right.
I did not check reset in Odin. Once it finished flashing the ROM, I removed the USB cable, removed the battery, replaced the battery, and booted the phone. I the Android guy with the wire frame for a few seconds, the screen went blank, and the phone started up with the Samsung logo.
Since you were getting errors with mounting the different partitions, you may have needed to flash the PIT and PDA files but I can't really say for sure as I have never encountered this problem.
I normally verify everything before I use Odin because phones that I have been given to fix have had all sorts of weird configurations.
You'll have to try the debrick guide. of use a jtag service. You could also do what I did and that is to look for people with phones that have a damaged screen and buy they at a steep discount.
I have posted about this before, but had no luck in finding help yet. Since then, I have tried many things to revive my S4 Mini, but first some background on what happened: ( The phone was on stock 4.4.2)
The phone was charged overnight, and in the morning after I woke up, as always, I took it off charge and went on Facebook. The phone then freezed and I took the battery out, and tried to restart it. It then just vibrated and nothing happened.
I then tried to boot into recovery, it also just vibrated, but nothing happened.
I then tried to enter download mode, and it worked. I was then somewhat relieved, and then tried to flash a stock rom in Odin. But then Odin gets stuck at Initializing.
I gave up for a few months, and left the phone alone. I then started now recently to try and fix it again.
I have tried flashing the 4 files alone: AP, BL, CSC and CP as well as PIT, and Odin flashing keeps failing.
I have tried using a Debrick.img. The phone does not boot.
The phone cant be hard bricked due to the fact that Download Mode still works, and it still charges. So I dont know what to do anymore?
Is there any hope?
Maybe your emmc get broken
where I can get this 4 files for S4 mini i9190
I need to
Enviado de meu SM-G800H usando Tapatalk
Same problem as OP. Can anyone help me to recover my friends phone. Only download mode working, phone only vibrates.
Sent from my Lenovo A6000/Plus using Tapatalk
jnvdh06 said:
I have posted about this before, but had no luck in finding help yet. Since then, I have tried many things to revive my S4 Mini, but first some background on what happened: ( The phone was on stock 4.4.2)
The phone was charged overnight, and in the morning after I woke up, as always, I took it off charge and went on Facebook. The phone then freezed and I took the battery out, and tried to restart it. It then just vibrated and nothing happened.
I then tried to boot into recovery, it also just vibrated, but nothing happened.
I then tried to enter download mode, and it worked. I was then somewhat relieved, and then tried to flash a stock rom in Odin. But then Odin gets stuck at Initializing.
I gave up for a few months, and left the phone alone. I then started now recently to try and fix it again.
I have tried flashing the 4 files alone: AP, BL, CSC and CP as well as PIT, and Odin flashing keeps failing.
I have tried using a Debrick.img. The phone does not boot.
The phone cant be hard bricked due to the fact that Download Mode still works, and it still charges. So I dont know what to do anymore?
Is there any hope?
Click to expand...
Click to collapse
try to root the phone and install recovery by odin. and find the suitable firmware and flash it. it will work. same was happend to me too.
my phone is GT-9190) S4 mini
---------- Post added at 06:48 AM ---------- Previous post was at 06:40 AM ----------
Hi guys. . When I go into about phone and check for cyanogenmod nightly updates, they show up 3 updates, and when I tap on them and click download, they download. when automatically boot to recovery mode to install, but its not installing and phone restarts to normal mode, saying that to do it manually. my phone firmware was 4.4.2 and I updated to cyanogenmod 11.0. I think I should install the updated recovery?
There are 3 auto update showing in my phone and I have to install all in one by one or only the latest one? for example the updates showing 20160425, 20160426 and 27 is the updates) does the latest nightly update include the bug fixes and stuff from the previous updates, or do I have to download all of them to get all of the fixes and such?
Any help would be greatly appreciated, as these dilemmas make updating Cyanogenmod very cumbersome. Thanks!
---------- Post added at 06:53 AM ---------- Previous post was at 06:48 AM ----------
johnkill_dxb said:
where I can get this 4 files for S4 mini i9190
Click to expand...
Click to collapse
go to www.sammobile.com and find 4.4.2 version from russia. download it and flash it by odin. I did it in my phone and its working fine.