[Q] Bootloader Problem - Galaxy S III Q&A, (US Carriers)

I too was anxious and with odin started to flash a rooted firmware only to find out it was not the proper one. Good news is I still have full access to my phone, I can boot into cw recovery, but I don't have the bootloader option anymore. How can I flash bootloader back to phone with odin? I need a file.

Related

How to unroot/go back to stock completely?

I did my search and I went over some topics and a lot of them say to boot into fast boot. Does that just mean to relock the boot loader and flash the PH85IMG.zip and that's it? Can someone just give my some instructions?
this might help you
nulcon said:
I did my search and I went over some topics and a lot of them say to boot into fast boot. Does that just mean to relock the boot loader and flash the PH85IMG.zip and that's it? Can someone just give my some instructions?
Click to expand...
Click to collapse
ok well all i can tell you is this... download this file http://d-h.st/rfa after you finish downloading my guess is that you have a custom recovery
image on your phone and if you dont install it again for a little... after you downloaded the file and have it on your sdcard boot into recovery
and flash it like you would any custom rom by wiping data, cache, and dalvik...
now you would reboot the phone and you will be on stock ICS from tmobile check if you have root access if you dont then just use
use Amaze_All-In-One_Kit_V3.2 and flash the stock recovery from the top right box and you will be back on stock tmobile unrooted
and with stock recovery mode...
yes to go back to stock without root, you need to first relock your bootloader and then flash the STOCK RUU that you renamed PH85IMG.zip after that you will be back to full stuck, but your bootloader status will say "Relocked"

From CM10 to Stock??

Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
GaryWS said:
Passing my P3 on to my wife and need to get it back to stock.
Got as far as loading the 3.2 firmware from sammobile using fastboot as Odin won't flash.
It recognises an OTA update but fails to download the update. I actually think that it fails to install but in any event it get stuck.
The kernel is still at 2.6.36.3 and baseband is the P7500 one.
I think that the kernel is located in the boot.img but it doesn't look like I am able to overwrite it with fastboot.
The bootloader seems to be replaced but I still have a unlocked bootloader.
Any ideas?
Thanks
Click to expand...
Click to collapse
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
pruano said:
You need to restore the stock recovery as well, ClockworkMod Recovery wont handle OTA updates.
Do fastboot flash recovery [recovery img] to reflash the stock recovery.
To re-lock the bootloader, try fastboot oem lock (not tried).
Note that it appears that even if relocking the bootloader, manufacturers have ways of knowing if the bootloader has been unlocked. However, since the purpose is to give it to someone else with possibly less technical skills (that does not require the feature), a locked bootloader is an added security.
Click to expand...
Click to collapse
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
GaryWS said:
thx pruano, the stock firmware contains a recovery image. This writes ok ... I also tried locking the bootloader - it locks ok but with the same results
It looks like the kernel might be the problem ...
Click to expand...
Click to collapse
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
pruano said:
Did you flashed ALL the imgs (boot.img, recovery.img and system.img) from the PDA archive?
You can always erase/format the partitions with fastboot erase/format [boot|recovery|system] before re-flashing the images... (important note: if you erase/format the boot partition, do not leave recovery without flashing a new boot img).
I would also restore the stock modem (you need the one from P7100BUKE2, as P7100BULB4 does not have it) - for this you will need Odin.
Click to expand...
Click to collapse
Pruano, using fastboot, the erase command seems to work but format does not. Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
and just for interest i had to use: "fastboot flash modem modem.img"
GaryWS said:
Why do you say that I need Odin to flash the modem? I have done this with fastboot previously using "fastboot flash radio modem.img" ...
Edit:and just for interest i had to use: "fastboot flash modem modem.img"
Click to expand...
Click to collapse
Did not know fastboot would recognize that partition, not on the docs.
Always learning.
GaryWS said:
Edit: Pruano, you put me onto the right track. The modem was the problem. Once I got the original modem from P7100BUKE2 installed it all worked fine - even with unlocked bootloader.
Click to expand...
Click to collapse
Yes, unlocked bootloaders do not interfere with OTAs
Regarding the modem, in truth it was a long shot, just a step to restore to pristine state.
The knowledge that the P7500 modem works best with custom ROMs and flashing it as a common procedure is relatively new, no wonder one had to guess that it would interfere with OTAs (as its not obvious, probably the OTA install does some kind of background safety check using the modem firmware as base); good to know for the future.

relock gs4?

ok so i keep trying to return to stock and relock my phone but i flash the factory firmware through odin and it returns the rom to stock but nothing else. bootloader is still the loki unlocked one. i have some kernel file and a recovery file but not real sure where to put it in odin, can someone help me please

[Q]Trying to flash to stock ROM to update bootloader

I want to update my cyanogenmod to lollipop, but the boot-loader isn't supported, so my understanding is that I need to flash to stock, get the ota to update the boot-loader, then I can flash to cyanogenmod. When I try to boot into the stock rom images I have downloaded, I get a red triangle. What am I doing wrong? I am s-on.
Kirov123 said:
When I try to boot into the stock rom images I have downloaded, I get a red triangle. What am I doing wrong? I am s-on.
Click to expand...
Click to collapse
Red triangle is stock recovery. Did you only flash the stock recovery? You need to flash the stock ROM/nandroid and a stock recovery to prepare your phone for an OTA.
But also note, that unless you are really set on keeping your user data, its much easier to just RUU up to Lollipop, as opposed to the method you are doing; which involves finding the right stock ROM, correct stock recovery, then OTA (possibly more than one) installs to get up to Lollipop.
The only downsides to RUU, is that the phone will be wiped (so before RUU, backup anything you want to keep off phone: to the cloud, PC, removable SD, etc.), and if s-on you will need to relock the bootloader to RUU (than unlock bootloader again in order to flash TWRP and custom ROMs).

Houston, we have a problem!

Okay.. So I flashed TWRP recovery to my 7040n with Flashify, but I forgot to unlock my bootloader first, so I consequently ended up breaking my recovery mode. Knowing that you don't need an unlocked bootloader to flash stock images, though, I tried to flash a stock recovery (also via Flashify). Then, when I try to boot into recovery mode, I end up getting my phone stuck in a bootloop. I mean, I can't boot into recovery or ANYTHING! I could try flashing a new ROM and recovery via PC, but I need to know how to flash the files without a working recovery. If I could flash them via ADB/fastboot somehow, PLEASE let me know!

Categories

Resources