Related
Hi, I started out with a stock tmobile s3 and tried to root it for the first time today, I followed this video
http://www.youtube.com/watch?v=mndQZqom3Ac
which asked me to use this cf-root 6.4
http://forum.xda-developers.com/showthread.php?t=1695238
when I hit start on that .tar file under odin, it failed stating "complete (write)operation failed)
since then, my device would boot with error "firmware upgrade encountered an issue" nothing else would happen.
I tried to go into recovery mode again and this time when I tried to retry the odin tar install, it would give me a new fail of cannot open com3
When I tried to use kies, it would just forever try to connect and never connect. so I couldnt do anything there.
What can I do? I would preferably try to retain all my saved data.
I also suspect my usb port might be faulty, sometimes need to press it in firmly to make the usb mass storage to work properly.
Thanks in advance
What is your Current android version ?
Perseus71 said:
What is your Current android version ?
Click to expand...
Click to collapse
i really didnt note which version i have... noob mistake i kmow. i think it is 4.2...is there any way i can check?
Ok, I totally messed up when I first attempted this. The .tar I used was for an international s3 and I have a tmobile us version!. the OP of the thread says it may even brick my phone if I attempt this on a non international version.
competely my fault, but what should I do to fix this and save my phone?
I cannot connect to kies, reinstalled the drivers and it still wont connect. just gets stuck in "connecting"
The odin now doesnt load a tar because it says "cannot open com3 "
EDIT:
fixed it, odin was not working due to kies running in the background and I finally was able to flash the correct chainfire for my phone
Glad its sorted out. I assume no issues now ?
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.
So This is my first time posting on any forum site for help, and i was refereed to XDA by my roommate. so what happened is a few months ago i asked my roommate to root my galaxy s3 SGH-I747, after he rooted it through odin and all seemed well, BUT we never could get the phone to recognize the root and was still unable to access any root functions. so after a few different attempts we gave up. i assumed that my roommate had removed the root (bad call) but never gave it any thought. a few days ago at&t started bugging me with a software update. i just hit ignore and it would pop up again in a few hours and the icon would never go away. so i gave in and started the update. i didnt pay the phone any attention while it "updated" but later that morning i went to turn it back on and it would get to the Samsung screen then the next screen but after that it goes black and vibrates. i showed it to my roommate and he informed me that it was never restored back to official frimware like i had previously assumed. and that it never should have received the update bc it was still on a custom frimware. we tried flashing the stock frimware back on the phone and every time it would fail the nand write. i believe it was updated to 4.4.2 before i received the update from AT&T and we tried many different ways too restore it i even tried the recovery in Kies 3 but all it says is "connecting" then connection failed. so far nothing has worked. i believe that the update contained android 5.0 and maybe that is the reason none of the other ways we tried worked. i have been researching for hours trying to find a similar case but nothing matches, and i cant find a single working solution that doesn't involve possible making it worse. i can access both the recovery and download modes. please any information or help would be greatly appreciated.
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
audit13 said:
Flash a custom recovery such as Philz Touch via Odin, install cm10.2 via your custom recovery. This should get the phone booted so you can determine the bootloader version on your phone. The NAND error is due to the fact that you are trying to downgrade the bootloader in Odin. Don't flash anything with Odin until you determine the bootloader. Doing so could hard brick your phone.
Click to expand...
Click to collapse
firstly, thanks for the fast help. i did as you advised and flashed philz touch 6.15.4 which is the latest version from what i understand. that worked flawlessly. the problem now, is with cm10.2 every time ive tried to install it i get an error in /storage/sdcard1/cm-10.2.0-d2att.zip.
im sure im doing everything correctly. any ideas?
Try flashing an older CM11 ROM for the d2lte.
audit13 said:
Try flashing an older CM11 ROM for the d2lte.
Click to expand...
Click to collapse
thanks so much man youve been a big help that worked.
So my issue is pretty similar, see what you guys think. i been trying everything i can think of.
i updated from xtrestolite 2.1 to 2.2 with out wiping. everything worked fine except when i would make calls, the other people could not hear me. so i updated the bootloader and modem again (i had done it before) and the problem persisted. i flashed back to stock and was getting stuck at the s6 edge screen. the only way to get around this was and get my phone to boot was to flash aou kernel. i was still having a similar issue with calling so I download a modem from a diffrent server and all of a sudden, it was working again on stock firmware... AWESOME!
now that i had all that done and my phone working as it should, i reset my phone for the first time and i got the FRP lock, wont boot phone because custom kernel. GREAT
I then flashed stock of6 again, the tar ball, and the 4 piece version. no dice
i then found of8, tried to flash that still no dice.
id love to flash twrp and load a rom on, but FRP is a alsjdflajs.
the phone will flash successfully, but upon reboot, it will go into recovery, run its course, reboot, and get stuck that the galaxy s6 edge screen.
i use the vol and power click during recovery to see what its doing and everything seems to go fine. it will then say failed to mount /data. im hoping flashing this with the pit file will work, but i cannot download the pit file from my work computer (hahah its blocks on 4shard and mega).
anyone have any other advice? i will update if i figure it out.
Regards team,
-Mad
p.s. none of this is xtrestolite's fault, that rom has been nothing but good to me.. my phone has been picky though. after 5.1.1 i had to flash a custom kernel in order for the digitizer to function properly.... any help is appriciated guys.
SO UPDATE!
nothing good, i tried the pit with of6 and of8, no dice. still stuck.
anyone got a s6 edge w a broken screen? you can claim it lost for all i care.
no one?
i guess if anything past flash stock firmware people dont know? was hoping for alittle more insight.
im sure if i could flash a kernel i could get it to turn on, but FRP has be at bay...
no help for you bro...Samsung just needs to release there software fixing for this comunity...I'm looking a for a dev to answer my question in this section about just flashing zip files in twrp instead of using odin or whatever other methods that can avoid all these problems that are all similar...hopefully in next few months it will be addressed
Hey mate, try this...
http://forum.xda-developers.com/showthread.php?p=61531848
Sent from my SM-G925T using Tapatalk 2
holy... fu34%# /S45it.... IT BOOT?!
after flashing every firmware 100000 times...
THANK YOU!
I initially used odin to flash OI1 update, after a rom I was using caused problems and I got bootloop. It changed bootloader value to b:3 and I'm unable to downgrade now so I used smart switch which didn't recognize device so used emergency recovery and still bootloop. I have factory reset and wipe cache multiple times along with adb side load and individual flashes of bootloader, modem, kernel, flashed custom kernel and twrp to access fix permissions and to mount partitions with advanced wipe etc and still wont boot past logo. Also during one fix attempt phone said can't mount system.. Idk I'm not understanding where the problem is .everything says successful but I'm still in bootloop. Please help. I've spent hours everyday for the past week searching & trying different things that seem might help so open to any suggestions.
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.