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.
Related
First let me say that I have searched and searched but have not been able to find anybody talking about the issue my GSM Galaxy Nexus is having.
First thing's first: I'm running the developer preview of Jellybean still, I never got around to re-flashing it. I am not worried about losing any of the data on the phone, instead I'm much more concerned with simply getting the phone back in running order.
I was using the phone, the screen flashed and it rebooted. This was the beginning of my troubles. Ever since then, the phone boots up fine. Within a minute or so of reaching the lock screen, the screen flashes again and it proceeds to reboot. Here's where it gets weird. I've tried countless things, getting more and more serious as time went on. The last thing I've tried is simply fastboot flashing everything, but it doesn't take. I flashed the bootloader, boot, recovery, userdata, radio, system, (not in that order, of course) the whole nine yards, and everything appears to be successful, but it simply doesn't work. After flashing everything, I should not have unread emails on three accounts, an alarm set, the time still configured to 24-hour clock, my apps installed, my home screen organized, etc... I only get a short window each time the phone finishes booting, but it's long enough to tell that it didn't wipe anything. I've tried wiping from CWM and TWRP, but the same thing still happens.
And here's where it gets REALLY weird. I tried 'fastboot oem lock'. It says "Locked" until I reboot, at which point it is once again 'unlocked'.
Flashing my partitions, locking and unlocking, none of it has any effect.
Please, anybody have a clue?
I've been a long-time reader of the forums, but never registered until now for this. I wish I was registering for a happier reason. I'd send it back to Samsung, but I can't even re-lock my bootloader!
EDIT: I forgot to mention, I verified the md5 of the stock (straight from google) rom I was trying to flash, it checked out. I tried the stock ICS rom as well, I couldn't flash it at first because flashing the bootloader and radio didn't stick (surprise surprise) so the "fastboot -w update" didn't recognize them and gave me an error. I flashed the images in the zip manually, but got the same overall effect, nothing sticks, but no errors are generated. Everything appears to work. Also, I tried fastbooting from a different laptop, but nothing happened any different.
It sound like it could be faulty nand memory . If fast boot doesn't work The next step would be trying to flash via odin & if that fails omap flash. Look for the odin & omap links at the bootom of efrant's Android for Galaxy Nexus Guide
agreed, seems likely that is a hw issue. still, it would be nice to try and get omapflash to work. i posted a few links in some other post let me see if i can find it and link it here.
edit: cant seem to find it right now. it was in a thread that the op just had the screen with the pc linking to the phone, not even fastboot (i think)
sent from my i9250
3rdstring said:
It sound like it could be faulty nand memory . If fast boot doesn't work The next step would be trying to flash via odin & if that fails omap flash. Look for the odin & omap links at the bootom of efrant's Android for Galaxy Nexus Guide
Click to expand...
Click to collapse
Just got my hands on my brother's windows box so I could give these a shot. I'd never played with ODIN, but it looked simple enough. I gave it a tarball, it completed flashing successfully ("PASS!"). It all looked good, I got excited, and all for nothing. I was flashing an ICS tar (IMM76D) over a JB installation, and yet after reboot I still had a JB install. I don't know where the ICS went, if it went anywhere. Something weird is obviously going on. Is there a more low-level bootloader I can flash using the "BOOTLOADER" button in ODIN? I used the PDA button as per the tutorials, but, like I said, it didn't help. It flashed bootloader, boot, recovery, system, and radio. How about "PIT"? Is there a PIT tar I can flash? Or anything else, PHONE, CSC, I'll try just about anything.
Another thing I forgot to mention, when writing the system and userdata images in particular, it tends to take a long time. According to ODIN, it took 23:39 I guess (I'm not sure that's the elapsed time, but it sounds about right).
I guess it's on to the OMAP technique , after a little more ODIN research.
bk201doesntexist: At second thought, it seems like something lower-level than ODIN and Fastboot is the problem, since I understand that ODIN works independently of Fastboot to do its job. I suppose that means that it's unlikely ODIN can do anything to help, and I should probably jump straight to OMAP.
EDIT: Just tried the OMAP flash deal, followed by the same ODIN flash I did before. Still no change in anything, really, except that on one of the screens I noticed that it identifies itself as a tuna, when I think it used to say maguro. At first I freaked, thinking that I had just made my phone think it's the VZW version, but then I remembered that's toro, not tuna.
Is anybody comfortable enough to use ODIN to pull a complete dump of everything from the phone, so that I might try flashing that on to see if I can get anywhere? Actually, now that I think about it, I don't know how I would flash that, after all. I don't understand enough about ODIN yet.
I thought it was supposed to be pretty hard to screw up a Galaxy Nexus this bad (assuming that this is my doing, and not a hardware fault). Any more ideas? I'm really not looking forward to calling Samsung with an unlocked bootloader.
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
mozphoto said:
I have been using the i747z ROMs for quite some time and after trying a bunch of other ROMs I always reverted back to theirs. So when their 3.0 version came out with Android 4.3 I installed it, using ClockWorkMod recovery. Right after it installed, CWM displayed a message about the boot loader and to fix it. So I went ahead and did that (Don't really remember what the message was) What I know is that I lost root. Also the phone could not connect to the mobile network, only on Wifi. So this morning, I factory reset the phone again, and attempted to root the phone with Odin with CF-Auto-Root-d2att-d2uc-samsungsghi747 (which I had used when I first rooted the phone). Now the phone doesn't boot past the 2nd samsung logo, it starts out with the Samsung logo with the blue circle around it, then the AT&T Rethink Possible and then the plain white Samsung logo. Also, the LED has a slow blue flicker.
I can get the phone into download mode and I have used Odin to attempt to load the stock firmware and the stock bootloader. But after restarting the phone I can't get past the same screen described above.
I am pretty sure this is not related to the i747z v3.0 ROM but rather something a miss with the order in which things need to start in Android. I have done some reading on that but I am not sure what I need to do to correct this soft brick situation. ( I have googled "soft brick" as well)
Any thoughts would be greatly appreciated!
Click to expand...
Click to collapse
After flashing through odin did you format data?If not try it.
Go into recovery and wipe data.
**SOLVED**
Thanks xXFl4sh, I had tried that.
Solved!
Alright where do I start? How about RTFM Some how I had missed the part about flashing a bootloader and a modem after the ROM. Not recalling having to do that before, I skipped right over it. Once the recovery CWM 6.0.3.1 was finally loaded, getting the flashing the ROM, the bootloader and the modem was easy as usual.
The key was having to use Odin to install a recovery in .tar or .tar.md5 format since I could not access a Recovery Mode on the GS3, as well as a rooted stock image (I used root66_ATT_I747UCDLK3.tar.md5 which is a rooted Android 4.1.1 for AT&T) For the recovery, I couldnt' find a .tar or .tar.md5 for ClockWorkMod (did find a utility to convert it, but didn't want to introduce another variable into the mix) so I used one from Team Win Recovery (v2.6.3.0) and with that I loaded the CWM recovery. Once all of that was in place, I proceed to factory reset, clear data, cache, system and then flash the new ROM, bootloader and modem.
In all of this I learned quite a bit about the whole process and how to narrow down possible resolutions. I still see the "Rom may flash stock recovery on boot" message after flashing either a ROM, bootloader or modem, but just backing out without answering Yes or No seems to work. Also (and this may be related, I don't see the option to restart in recovery from shutdown menu). Don't really know what that's all about for now, and honestly don't want to mess around (at least for a while)
I know the steps are general, but I hope this can help some else if they get their devices in a soft brick situation. As for the i747z v3 ROM with 4.3, I really like it, everything works (Wifi,Blutooth,tethering) and the battery seems good as well.
Thanks!
So basically I was on stock 4.3 TW rom and tried flashing HyperDrive ROM. Everyhting went through but I did get any Data to work for the life of me.
Tried flashing back to a 4.4 GE rom, and got "com.phone.android" crash error right after boot up. Couldn't do anything with the phone at all.
Tried flashing another .zip I had, same thing with the phone.
Tried flashing stock rom throgh Odin, same thing.
Now after a couple other flash tried etc, my whole SDCARD is wiped, and can't use fastboot.
I can get into recovery but thats about it. Tried sideloading a rom with the same com.phone. issue.
About to drown this ****ing thing and use my warranty, at a complete loss now.
re: issues
jzero88 said:
So basically I was on stock 4.3 TW rom and tried flashing HyperDrive ROM. Everyhting went through but I did get any Data to work for the life of me.
Tried flashing back to a 4.4 GE rom, and got "com.phone.android" crash error right after boot up. Couldn't do anything with the phone at all.
Tried flashing another .zip I had, same thing with the phone.
Tried flashing stock rom throgh Odin, same thing.
Now after a couple other flash tried etc, my whole SDCARD is wiped, and can't use fastboot.
I can get into recovery but thats about it. Tried sideloading a rom with the same com.phone. issue.
About to drown this ****ing thing and use my warranty, at a complete loss now.
Click to expand...
Click to collapse
Since you have only posted the issues you are having with your phone but not your
phone's specific model I cannot help you more than the following.
What I can tell you is if you really want to fix the issues you are having you need to forget
about going into recovery mode and instead make sure you can go into "Download Mode".
Once you can get your phone into download mode you will need to find and download the official
stock Odin flash firmware specific to your phones model and flash your phone using Odin.
Good luck!
You've posted in Tmo S4, Nexus 4, i9505 threads at the minimum. Please make sure you're in the right forums. But in any case, you've overwritten many files by doing dirty flashes. Your best bet is to go into download mode (Vol Down + Home + Power), connect phone to computer, open up Odin, select PDA/AP, and then choose the stock file for your phone model and version.
.. slightly off-topic, but.. Isn't a "soft-brick", by definition, fixable? Otherwise it'd be a 'hard-brick'?
coyttl said:
.. slightly off-topic, but.. Isn't a "soft-brick", by definition, fixable? Otherwise it'd be a 'hard-brick'?
Click to expand...
Click to collapse
Soft-brick is exactly what it is, it is a software issue in which case you can usually Odin back to stock and get it working again. A hard-brick is when you can no longer flash any new software onto the phone and the only way to repair it is using a JTAG device which majority of the people don't have. It essentially becomes a paperweight. But all hope is not lost. There is a service that you can send your phone in and for about $25 or so, they will have it fixed and back to you within a week. The company has good reviews so it's worth it if you've bricked your $600 device.
xdapowerapps said:
Soft-brick is exactly what it is, it is a software issue in which case you can usually Odin back to stock and get it working again. A hard-brick is when you can no longer flash any new software onto the phone and the only way to repair it is using a JTAG device which majority of the people don't have. It essentially becomes a paperweight. But all hope is not lost. There is a service that you can send your phone in and for about $25 or so, they will have it fixed and back to you within a week. The company has good reviews so it's worth it if you've bricked your $600 device.
Click to expand...
Click to collapse
Okay, that's what I was thinking. Thanks!
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
GoonReb0rn said:
Hi,
This morning I woke up to see my phone seemingly booting up but after a few minutes I realised that it was stuck on the boot screen. I can only assume something hardware or software related messed up while I was sleeping and now after reading a few threads I am very scared that my phone could possibly be bricked.
First up, I updated to 4.3 from 4.1.2 about 3 weeks and it has been running fine albeit a few annoyances at the new firmware Samsung deployed. To get root I had to install philz_touch_5.11.2 recovery through ODIN and then go into my new recovery to install root through Dr Ketan's Multi Tool which seemed to work well with no problems, it was quite flawless through the whole update. But now I guess something has happened to my phone and that has changed. When I saw it was stuck, I thought that it would be possible to just reflash to stock firmware and that would fix it. It was working up until the point ODIN got "cache.img" which failed the install. Now, I exited ODIN since it didn't work and restarted my phone and tried to flash the stock 4.3 ROM again. This time, immediately I got a screen telling me that there was "no PIT partition"
(Look at the attachment for the screen, I am new so no outside links)
and now I am getting the message on my phone after restarting "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." I am now downloading Kies to try this but does anyone have any suggestions or solutions?
Click to expand...
Click to collapse
Update: I spent the past two days trying to solve this and I'm at a standstill in progress. It seems that my phone was one that suffered SDS with a corrupt eMMC chip so I've lost both my firmware and recovery but I can still get into Download mode. It also seems like I have lost my PIT table and I am just completely unable to flash the PIT file back to the phone for some reason. Does anyone have any ideas on how I could just factory reset my phone or reinstall my partition table so that i can get a simple recovery installed? Please help
Exact same issue!
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
dkinniburgh said:
I know exactly what you are going through!
My phone did the exact same thing back in June. It downloaded the firmware update over wifi, then when it went to install, it restarted to the boot logo, and went no further. I had left it for a number of hours, so time doesn't seem to make any difference.
I've been working on it since the end of July, and haven't been able to find a solution yet.
Click to expand...
Click to collapse
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
GoonReb0rn said:
Yeah, it doesn't seem like time would fix it, so frustrating. Right now I am getting the glass of my Note replaced (it has a slight crack) which apparently voids my warranty when I went into my carrier to organise a replacement. After it's repaired I will take it to another store and try to get it sent off to Samsung, hopefully they are understanding about it and will honour their warranty end as I do believe it was SDS so it would be their fault for using faulty eMMC chips. The only thing I wish I could do it just start over, flash the PIT file so I can just install CWM to see if any of my files are still there. I just want some peace of mind and it seems impossible at this point. I guess it is impossible to flash a PIT when the storage chip is corrupt, sucks to lose all my messages and data, just wish I had a backup in place but it is a good learning experience for the next time I have a functioning phone.
Click to expand...
Click to collapse
I was lucky having most of my info already backed up. I also had just upgraded another line, so I had a new phone to work with. It just sucks having to switch everything over to a new phone, reloading all the apps etc.
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
lsiravi said:
Hi everyone
Long time xda follower, newly registered, since I needed to ask a Q.
I rooted and switched to Lollipop on my ATT S3 (i747) a few months ago, Lately, I've started noticing battery issues as well as network issues with this ROM. I figure it is time for me to go back to stock.
However, if I remember correctly, when I tried previously the phone refused to downgrade back to stock. Kies was helpless because the trip counter had been reset (or something similar).
Please, is there a good how-to on downgrading this phone from Lollipop back to stock? If yes, would someone please point me to it?
Much thanks in advance.
lsiravi
Click to expand...
Click to collapse
lsiravi said:
Hmm.. I am going to give this a try:
http://forum.xda-developers.com/galaxy-s3/general/fix-s3-to-factory-unroot-stock-recovery-t2323847
Click to expand...
Click to collapse
Nope! No go!!
Triangle away reset the counter.
The stock recovery works well. I was able to boot to recovery and wipe the data and all that.
Odin says "SW Revcheck Fail" when trying to download the stock rom.
I rebooted into Lollipop, downloaded Triangle away again and reset the counter. Still Odin fails with the same message.
I tried flashing ROM first then the recovery as it was suggested in that link. Nope. Again "SW Revcheck fail". For the record, my SWREV appears to be 3. It is supposed to be 0. Triangle Away does NOT reset this. It did reset another counter (as reported by Triangle away itself - was 5, got reset to 0).
I remember *this* was the problem previously as well, hence the original Q:
How *do* you get back to stock from Lollipop on the Galaxy S3/ATT?
Meanwhile, although Keis failed to recognize the device, I tried to run a firmware recovery manually. It took a long time and in the end failed. It also messed up the recovery, so I had to flash CW again to make it bootable. I'm still back up with Lollipop at this point, but I don't want Lollipop.
Anyone anything else I can do? Any other guide out there to downgrade?
Thanks again
L
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
audit13 said:
The thread you linked is for the international version of the s3.
Before flashing anything else, you need to confirm the bootloader on your phone to ensure that you don't flash anything that attempts to change the bootloader if your bootloader is mjb or newer.
Click to expand...
Click to collapse
Right. I finally figured it out.
First the 4.1.1 FWs weren't flashing (in other words SW REV CHK FAIL) was basically indicating that my Bootloader was far ahead of the 4.1.1. I dropped 4.1 after I figured that part out.
Next, I tried to flash a 4.4 (UCUFNE-rooted-odex is available as a zip-flash) through CWR, which didn't work (no boot, stuck at splash).
Next I got hold of a 4.3 (UCUEMJB-2024954-REV04-user-low-ship), which successfully flashed through Odin (repartition checked), but there was no sound, IMEI indicated null. Service Mode yielded a blank screen.
I flashed TWRP through Odin (was working on CWR since the beginning) and then flashed the UCUFNE-rooted-odex above on top of 4.3 through TWRP, which was successful, still no sound/IMEI/service mode.
Finally I got hold of the UCUFNE-Modembaseband zip (a small one - 20MB) and flashed that through TWRP. Both sound and IMEI came back.
I'm at 4.4.2 now, but an OTA update from ATT failed (probably because it went through TWRP)
Now I'm back to stock, albeit rooted ROM (because of the Rooted-Odex 4.4 flash), but I am a happy camper.
Thanks to XDA for various bits of info here and there. But essentially *this* is how you go back to stock from Lollipop.
L