Rewriting/Fixing Corrupted Bootloader -Yes, I Went THERE - AT&T, Rogers, Bell, Telus Samsung Galaxy S III

I kinda got confused yesterday between using updated T999 bootloaders or update I747 bootloaders because I had re ODIN'ed my my whole phone via Samsung Provided Bins and that bin contained T999 bootloaders and modem that worked and booted properly on my I747 without any problems. Thing is I decided to update that bootloader and modem to the newest version for T999 which in turn caused my dead GS3. So I'm guessing the problem would be a corrupted bootloader? I have the MSM8960 hex and the MSM8960 BIN, but when I try to program these to my SG3 which is in QHUSB mode, it says the "Cookie (If Present) not received error (QPST 2.7 Build 402). I've been up studying partitions etc etc but I just can't seem to do it. I think I need the partition_boot.xml and the rawprogram0.xml and or patch0.xml IF those were needed (I'm kinda glitchy right now, no sleep -_-) all I need to do is get my phone into regular odin mode so I can flash all the files back to my baby again (Dropbox 50GB +Nandroid TWRP FTW) (And by files, I mean the proper CSC, Bootloaders, Modem, Platform and Partition files I got from Samsung for my unlocked and modded S3.
I'll add the attachments I've used up until now, Including the odin files I've used for turning my phone into an T999 (Should NEVER update that Bootloader with a new T999 one, just a new I747 one LESSON LEARNED)
Dropbox :http://www.dropbox.com/sh/9hpjjj95dtxxx74/acPHV3XqL_
T999_UVDMD5_firmware_v4 is what bricked my phone, I have the flash the files inside this shared dropbox folder (Also in the BOOTLOADER zip of course, before I can get her running again.
Any help getting to rewrite the bootloaders and or getting into ODIN mode? I'm bringing my phone back from hell, really, If I can manage to solve this problem as well, I want to make this into an AIO so everyone who went through the same mistake by off chance can fix this as well.
Any help would be appreciated, I would JTAG, but I don't have the money for it, they aren't hiring 17 year olds around state right now -_- So I guess this would be the opprotunity to help me further my tech knowledge ( I want to do Tech Development like this when I go to college in 2 years )
Thanks

Jtag is the only way I know of, if it's truly hard bricked.

Really?
mrhaley30705 said:
Jtag is the only way I know of, if it's truly hard bricked.
Click to expand...
Click to collapse
I did alot of research and seen that it can possibly be done, but it shows up in QHUSB mode where I heard it's difficult, yet possible to fix, with a few file to make it boot as a USB drive

Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

kennyglass123 said:
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Thank you, I sort of considered it something to work on, instead of it being a question for me to ask, I see otherwise now.

Related

Help rooting GS3 ATT....small detail

I read the how to root thread in this formum to grab the files I need to root the ATT GS3.
I have rooted plenty of phones and familiar with the process.
The image file that the thread lists for ATT GS3 is ATT Stock Download I747UCALG1.
The detail in the phone settings show that the build on my phone is I747UCLEM.
Is this file going to brick my phone, or is there something else I should be downloading or another method to root I can use?
Thanks
ac29593 said:
I read the how to root thread in this formum to grab the files I need to root the ATT GS3.
I have rooted plenty of phones and familiar with the process.
The image file that the thread lists for ATT GS3 is ATT Stock Download I747UCALG1.
The detail in the phone settings show that the build on my phone is I747UCLEM.
Is this file going to brick my phone, or is there something else I should be downloading or another method to root I can use?
Thanks
Click to expand...
Click to collapse
no it will not brick your phone just upgrade it to g1
since you read that next read the rules of posting questions in the q&a and not developtment
OK LETS SEE HERE
DEVELOPMENT IS FOR DEVELOPMENT
Q&A is for QUESTIONS AND ANSWERS
THIS IS A QUESTION
THREAD MOVED...SMH

Is there a way to root with a Mac?

So when i first got my gs3 in august i was able to root with heimdall. Early January i had to have my phone replaced because the speaker was messing up.
Since ive gotten it replaced i have had the most ridiculous time trying to find a way to root it with my mac again. The old process with Heimdall does not work anymore.
And it appears that the only process to work is with Odin. The only issue is i dont have access to a Pc to run odin. Am i correct in assuming that i cannot currently root and push a new recovery with a mac?
Ive tried google, XDA, Rootzwiki, Android central and i cant seem to find much information anywhere...
If i couldnt use the search button properly feel free to flame away but i cant seem to find anyhting.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Hamspiced said:
So when i first got my gs3 in august i was able to root with heimdall. Early January i had to have my phone replaced because the speaker was messing up.
Since ive gotten it replaced i have had the most ridiculous time trying to find a way to root it with my mac again. The old process with Heimdall does not work anymore.
And it appears that the only process to work is with Odin. The only issue is i dont have access to a Pc to run odin. Am i correct in assuming that i cannot currently root and push a new recovery with a mac?
Ive tried google, XDA, Rootzwiki, Android central and i cant seem to find much information anywhere...
If i couldnt use the search button properly feel free to flame away but i cant seem to find anyhting.
Click to expand...
Click to collapse
Gotta use a windows machine, unfortunately I'm in the same boat. I've gotta wait at least another week smh
Sent from my SPH-L710 using Tapatalk 2
kennyglass123 said:
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Click to expand...
Click to collapse
Sorry,
I swore i had it in QandA If you can imagine, last night i had around 20 tabs open trying to find the answer or trying to use old or alternative methods to get a custom recovery. I think i just clicked the wrong tab..
Thankyou though for moving it for me.
@banccalif it looks like i have no choice but to run a virtual machine of Win7 just to get this thing rooted...

Trying to flash a rom

I have sprint gs3 rooted with cwm 6.0.3.1 installed on it. I was trying to flash SuperNexus-2.0-i9300-BUILD4. Zip onto my phone. I recieved an error when it attempted to do the flash. The error was: /tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. This also happens when try to restore a backup not done by rom manager
Please I hope you where not successful at all. You are trying to flash an International rom. Can't you see it says it's for the I9300 not the SPH-L710??? You will brick your phone. Please stop and do about two more Weeks of reading and research.
Sent from the future via Xparent Green Tapatalk 2
Do what Ed says unless you want a $700 paperweight. Would you put Diesel fuel into your gasoline powered car?
Now I understand why carriers are locking the bootloader.
As said above, PLEASE put the phone DOWN and step away from the merchandise....now go read, read, read, and read. You should never flash roms that are not made for your specific device AND carrier. Ever. No exceptions.
Here are two links to with a wealth of information for you and anyone new to rooting and flashing roms:
http://forum.xda-developers.com/showthread.php?t=1726558
and just to drive the subject home, because it is very important:
http://forum.xda-developers.com/showthread.php?t=2156714
There is another thread HERE that you should look over.
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Okikix said:
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Click to expand...
Click to collapse
Use the links above and read Don't worry about the recovery log for now.
Okikix said:
Thank you didn't even notice that. As far as the recovery.log file, what is going on there?
Click to expand...
Click to collapse
as noted above don't worry about that but be thankful you got that error it just might of saved your phone.
Your device still works?!?! You should be thanking the GS3 Gods right now cause someone was looking over your shoulder lol. I seriouslyyyy question how some people here even got through the rooting process successfully... SMH

[Q] Galaxy S3 Bricked or Not?

Hi everyone,
I'm really desperate for any information that can help me. Please be kind here...I haven't done anything techy stuff like this before.
Here's the situation.
My phone was rooted with supersu since I got it (my colleague helped to do it), but due to an issue with my international roaming, I decided after 1 year to try and unroot and upgrade from 4.1.1 to 4.2/3
However, upon unrooting, i found that I could not upgrade due to the count and decided that I had to try and root it again to use triangle away.
Here is where it gets FUBAR.
I ran Odin and flashed the following:
I9305_CWM_Recovery.tar.md5
Samsung-Updates.com-KERNEL-GT-I9305-SIN-I9305XXBMB2-1359977044
My phone was still working then, but I wasn't too sure how to install the binary until many tries later ...
But somehow because I didn't know how to install the binary, I ran the "Auto Root": CF-Auto-Root-t03g-t03gxx-gtn7100.tar.md5
After which, my screen flashed blue ...
When it wouldn't boot up, I flashed:Samsung-Updates.com-KERNEL-GT-I9305-SIN-I9305XXBMB2-1359977044
And did a factory reset.
The hard and soft buttons are working, but the touch screen is dead. Thinking it was a OS issue, I flashed the stock rom: I9305XXALI9_I9305OLBALI8_I9305DXALI7_HOME.tar.md5 1.2Gb file
And right now, no change. Hard and Soft buttons working, touch screen is dead....
Anybody?
Please read forum rules before posting
Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
As long as something is working it is not bricked. A brick means completely dead, like a brick. Perhaps the ribbon cable came loose from the touchscreen.
This is the Sprint US variant S3 section. From everything you posted you have an International model. You are in the wrong section.
Remember search is your best friend, Have a great day!
edfunkycold said:
This is the Sprint US variant S3 section. From everything you posted you have an International model. You are in the wrong section.
Remember search is your best friend, Have a great day!
Click to expand...
Click to collapse
Or he has revealed the root cause of the problem, if he actually does have the Sprint version
Sent from my SPH-L710 using xda app-developers app

[Q&A] Note 4 bootloop after *#9090# menu

Q&A for Note 4 bootloop after *#9090# menu
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Note 4 bootloop after *#9090# menu. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
In response to thread: Note 4 bootloop after *#9090# menu
I had this issue too. I tried several things from flashing the stock firmware to taking it to the Samsung guys at Best Buy and nothing worked. The only solution I got was to send it in to Samsung to get it fixed. That's what I did and they fixed it. I don't have exactly what they did to it on me right now but when I get home, I'll post it. From what I remember though, they changed some hardware parts so I'm assuming the only way to get it fixed right now is to send it in to Samsung. You shouldn't have any problems sending it in since its still under warranty.
Bootloop
Did the same to me, be careful with that menu. Mine was under MFG warranty so AT&T just replaced the phone. No amount the AT&T flashing was working either. My guess is you need the PIT file and such so you can do an Odin flash like Samsung does when the phone is ready for OS.
tonys.94 said:
Did the same to me, be careful with that menu. Mine was under MFG warranty so AT&T just replaced the phone. No amount the AT&T flashing was working either. My guess is you need the PIT file and such so you can do an Odin flash like Samsung does when the phone is ready for OS.
Click to expand...
Click to collapse
Yea i accessed that menu and that's when it happened. For me though, AT&T wouldn't replace it because I bought it off Ebay as manufacturer refurbished.
hi...
i havign the same problem.... is any ways to fix it..... HELP...........
gmadrigal said:
i havign the same problem.... is any ways to fix it..... HELP...........
Click to expand...
Click to collapse
if you were on OC5 firmware before this happened the only way to fix it is warranty service.. Go to an ATT device support center near you and they will swap it out for a new one. I had to do this last week.
DaGODFather10 said:
Yea i accessed that menu and that's when it happened. For me though, AT&T wouldn't replace it because I bought it off Ebay as manufacturer refurbished.[/QUOTE
You may have to wait then until Samsung releases the PIT file or someone can copy it somehow and post it. The PIT file is what is used to repartition the phone's internal storage, preparing it for the OS. It wipes all data except firmware then partitions it for recovery, OS, and such. Then it can write the BL, AP, CP, CSC, etc. I've used that menu before no issues, till about a week ago when I tried it just to check since I haven't used it in awhile. Seems with some of the later builds they broke that menu. Haha. I do apologize but I don't think there will be a way for you to flash it back to normal unless you can find the PIT file for the AT&T Note 4 specific to your current android OS build. I would contact Samsung support see if they can do a warranty exchange with you. Or ask for the PIT file haha, which they won't probably give
Click to expand...
Click to collapse

Categories

Resources