I am not used to Samsung kind of modding and bricked my SM-P905V and it tells me to take it to verizon. I am rooted and would like to take it back to stock cause i dont understand samsung products. Odin mode says official for both but in red says unsupport dev_type and wont boot past the kernel. Please help, I will donate. i didnt moddify system files, i was stupid and flashed a twrp recovery to it threw flashify. if i could get a stock recovery, would it be ok? Locked bootloaders are so redicilous.
Related
Hey Guys,
I want to flash a original stock ROM to flash on my galaxy 3, i am seeing the the stock ROM's on SamMobile but i am super unsure to flash them
What should I do to remove the bootloader for a safe flashing? What files should I delete and how to?
Yea i also want to know how to do that if somebody can please explain this !
You have the Samsung Galaxy S3 ?
You don't want to "remove" any kind of bootloader. Removing the bootloader would cause your phone to not boot up. Sometimes people need to unlock a bootloader, but you shouldn't have to with your phone.
If someone told you to delete the bootloader, they are probably trolling you and want you to break your phone.
Did you get the phone from someone who had already rooted / installed a custom ROM ? If so, I highly recommend wiping EVERYTHING, including recovery so you can get a fresh start and nothing will be left over.
You don't need to do anything to the bootloader for the Samsung Galaxy S3.
You should factory reset and use the computer program Odin to flash stock ROM + recovery. You can find out how to do that in detail in the forum for the Galaxy S3.
Remove boot loader trololol lol sure if you want to hard brick your phone and you have a Samsung they open no unlocking
Sent from my SCH-I500 using Tapatalk 2
He means removing the new bootloader included in recent OTA's from the OTA itself. The new bootloader will up your flash counter just for having a custom ROM on your phone, rather than flashing one.
Trying to help out my friend. He rooted his Galaxy S 4G and was trying out different roms and now it's stuck in recovery. He brought it to me--I can pretty much fix anything Android--I've helped a lot of people on XDA, but this one has completely stumped me.
I've Odin'd several different Official Stock restore packages, recovery packages, etc. Everything has the same effect, no matter the rom or the recovery, the phone will always (re)boot back into recovery. Selecting reboot system reboots it back into recovery. No matter what. I must have flashed Stock via Odin about 10 times today. Same results every time.
Right now it's stuck in the 3e recovery screen. But I can flash a Voodoo recovery, but it still gives the same effect.
Does anyone have any ideas? Is there a bootloader sequence anyone knows about, that he may have changed? Any help is appreciated.
Thanks everyone!
Follow the guide in the second link of my signature to fix.
Awesome! That worked! Followed the guide. I had already flashed stock, but I didn't know you could flash the bootloaders using a .jar package. It worked. I guess he jacked with his bootloaders.
actually, bootloaders would corrupt boot period. You'd be stuck in a "FIRMWARE UPGRADE FLASH FAILED" screen, or phone won't boot period. So, I think I know what the problem was.
When hopping from roms to other roms, specially on Kxx Based Touchwiz roms, your cache tends to get corrupted. Had you reflashed cache.rfs and a stock zImage using heimdall, it'd fix the issue, and data wouldn't vanish.
I decided to give the new CM9 rom a try this morning on my verizon s3. after playing around a little i decided that I liked the stock rooted rom I had before so I was going to return to my nandroid backup. However, CM9 has its own recovery. I flashed my other recover, which was InvisibleK's recovery, which actually boots into a stock rom from recovery but never really goes into the recovery menu. So now I am stuck bootlooping because I think the recovery is trying to boot up but isnt finding the rom becuase I couldnt flash it from the CWM rcover that I was on with CM9. I can get into download mode but of course Odin is not seeing my phone for some reason. Anyone out there have anysuggestions? or did I just make myself a fancy new paperweight?
got odin
i got to odin now. i recognized my phone. I switched usb cords to the one that came with the phone
flashed stock rooted rom no luck
flashed stock rooted rom thought i was in the clear and now its bootlooping at the verizon boot animation. Im pretty sure i just have to factory reset but i cant get into recovery
kulahpac said:
flashed stock rooted rom thought i was in the clear and now its bootlooping at the verizon boot animation. Im pretty sure i just have to factory reset but i cant get into recovery
Click to expand...
Click to collapse
Revert to complete stock with no root, then try to access the samsung recovery and do a factory reset from there.
unrooting brought me back to stock recovery
I finally sbf'ed back to the stock rom and being unrooted must have not allowed the phone to use the recovery I had installed and instead took me to the stock recovery where i was able to factory reset and all is good now. Phew..... that was a close one
thanks skander
Thank you very much. I actually tried that last night. I was getting desperate. wasnt sure if it would work or not but I thought maybe that and if that didnt work i would try flashing a different recovery from adb but i can never get adb to work from my pc. Anyway though, didnt matter. its all good now. Just got root back and learned a valuable lesson. thanks again....
Please Help.
was running hyperdrive rls12 on a verizon sg3.. switched to baked. after that i cant get into recovery. i went all the way back to stock. unrooted and all.than i rooted again and unlocked bootloader i can boot into odin download. i can restart phone into rom. back to stock jellybean.. but every time i try to boot into recovery it says cant boot and puts me back in odin download. i tried through buttons and through rom manager. always the same outcome. phone is usable but i cant flash any new roms if i cant get into recovery. and i always to a clean flash. any ideas
Try flashing the recovery using odin
Thanks doesn't hurt....
ramdesai said:
Try flashing the recovery using odin
Thanks doesn't hurt....
Click to expand...
Click to collapse
Damn i feel dumb. feel like a noob. thanks. dont know why i didnt think of it. do the simple first i guess. thanks again
You are welcome...Happens sometimes... Take a break and then think again..
Hey guys, so I'm a crazy noob at this and I decided to flash a rom on my note 10.1 and was messing with reverting it back to to the stock rom and all of a sudden it got stuck in this boot logo thing and it wont allow me to get past that. I've tried using odin to flash but it wont work, I can get into cwm but I think somethings wrong with it... Any help would be great!
Rocket_bait said:
Hey guys, so I'm a crazy noob at this and I decided to flash a rom on my note 10.1 and was messing with reverting it back to to the stock rom and all of a sudden it got stuck in this boot logo thing and it wont allow me to get past that. I've tried using odin to flash but it wont work, I can get into cwm but I think somethings wrong with it... Any help would be great!
Click to expand...
Click to collapse
can you access CWM?
if so then you can flash a custom rom to the device. if you can enter Odin mode then try to flash the stock rom.
Jtag brick repair
Rocket_bait said:
Hey guys, so I'm a crazy noob at this and I decided to flash a rom on my note 10.1 and was messing with reverting it back to to the stock rom and all of a sudden it got stuck in this boot logo thing and it wont allow me to get past that. I've tried using odin to flash but it wont work, I can get into cwm but I think somethings wrong with it... Any help would be great!
Click to expand...
Click to collapse
I came across this web sight......... They will fix your tabet for $50 MobileTechVideo's
fix
http://forum.xda-developers.com/showthread.php?t=2599294
I posted the solution that works for me in the above thread just follow those directions with
the firmware for your device and you should be good